I've installed Evolution 3.44.1-0ubuntu1 from the proposed updates and
text now displays background as expected. This is resolved for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969251
Title:
Hi,
Sure, the output is as follows:
gsettings get org.gnome.desktop.interface gtk-theme
'Yaru-blue-dark'
gsettings get org.gnome.desktop.interface color-scheme
'prefer-dark'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Evolution-3.44.0-1ubuntu1 in Jammy proposed fixes the issue.
** Changed in: webkit2gtk (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967020
Title:
This is not a bug rather a regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969251
Title:
Evolution dark background in HTML message (Jammy 22.04)
To manage notifications about this bug
This bug may be related to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1272001
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969251
Title:
Evolution dark background in HTML message
Attached crash file.
** Attachment added: "_usr_bin_evolution.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+attachment/5581391/+files/_usr_bin_evolution.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Apr 19 16:00:48 ROC-Cube systemd[4105]:
app-gnome-org.inkscape.Inkscape-29481.scope: Consumed 25.374s CPU time.
Apr 19 16:00:51 ROC-Cube kernel: [ 2524.702434] evolution[28125]: segfault at 0
ip 7f6cf7dc4536 sp 7ffc3fc482e8 error 4 in
libwebkit2gtk-4.0.so.37.56.4[7f6cf7872000+2739000]
Actually, a correction. Evolution starts fine but if I go to type an
email (or reply) the editor window is blank. Closing the new or reply
message window THEN crashes Evolution.
** Attachment added: "image832.png"
I'm also having this with Jammy. I am using Wayland with the AMD opensource
GPU drivers.
The following appears in syslog:
Apr 19 15:45:56 ROC-Cube kernel: [ 1629.677203] evolution[23936]: segfault at 0
ip 7fef9c195536 sp 7ffe2be1cf88 error 4 in
One quick question.
On 21.10 the preview rendered with a white background even when using a dark
theme.
Please see the attached.
And thanks for looking at this bug/question. I appreciate it. :)
G.
** Attachment added: "White background previously with 21.10"
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969251
Title:
Evolution dark background in HTML message (Jammy 22.04)
To manage notifications about this bug go to:
Public bug reported:
When using a dark theme in Jammy (22.04) beta, Evolution will display a
dark background with black text for HTML emails in the message preview.
Previously in Impish, the background was white with dark text.
This only occurs when using a dark theme, If you use a light theme,
Hi,
Sorry for the delay in getting back to you.
As mentioned, adding the absolut path to my auto.DataVol1 file has fixed the
issue for me.
I think it would be preferably to add files to nsswitch.conf rather than
looking for conf entries in /etc/sssd.
For me, the only thing inside /etc/sssd is a
Andreas,
As per comment #25, I've added the absolute path to auto.DataVol1 in
/etc/auto.master as I can confirm it working.
With you comment on having:
automount: sss [NOTFOUND=continue] files
as part of /etc/nsswitch.conf, I suggest that to not break people's existing
configs, that this may be
Hi,
Well this explains why this is starting to happen:
https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity-1/+merge/390221
They're adding Active Directory to the new user creation in the
installer.
There's also a design doc that explicitly mentions SSSD:
Same here aas in comment #15. I didn't have SSSD installed prior to the
upgrade and it was "ubuntu-desktop-minimal" that pulled SSSD in. Not
only did it break my automount but also login and sudo would take about
a 4 seconds delay to succeed - as I guess it was trying to auth via SSS.
Grepped
I wouldn't suggest that SSSD has anything done particularly for AutoFS
but I would make a case for the package maintainers having a default
/etc/sssd config file(s) that if nothing else has options
commented/hashed out and ready ti be uncommented and used. This would
be much like how *insert your
Understood.
I guess the last thing I can do here is take the 20.04 VM I've made and
upgrade it to Groovy to see if SSSD is installed as a dependancy of
something else.
I'll do that over the next day or two.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After doing a fresh install of 20.04 in a VM and then installing autofs, I've
concluded that SSSD isn't needed for my setup.
This does leave the question why SSSD was installed and if it was installed
upon upgrade to Groovy.
Either way, it seems that when SSSD is installed (either on 20.04 or
I installed 20.04 fresh in a Gnome Boxes VM and installed autofs (sudo apt-get
install autofs).
SSSD was not installed as a dependancy.
Then, I installed SSSD (sudo apt-get install sssd) just to see what
/etc/sssd looked like and it's actually the same. there's no config file
under /etc/sssd and
Nope, there's no files under /etc/sssd and I didn't touch this directory
when upgrading to the Groovy daily image. When I have a moment, I'll
install 20.04 in a VM for a comparison of what should be in /etc/sssd
But as far as /etc/nsswitch.conf goes:
# /etc/nsswitch.conf
#
# Example
I never looked at SSD closely prior to upgrading from 20.04 to 20.10 so I don't
know what was there before as it 'just worked'.
Presently though, the only thing under /etc/sssd is an empty conf.d
(/etc/sssd/conf.d) directory.
I did reinstall the SSSD packages after upgrade to 20.10 however the
Trying to restart SSSD give the following errors with journlctl -xe:
The job identifier is 11972 and the job result is failed.
Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD Sudo Service
responder socket.
░░ Subject: A start job for unit sssd-sudo.socket has failed
░░ Defined-By:
Public bug reported:
Using the same automount config from 20.04, Groovy Gorilla fails to automount
mount points with SSD errors such as the following:
-From journalctl -xe:
Sep 25 04:04:43 ROC-Cube systemd[1]: Stopping Automounts filesystems on
demand...
░░ Subject: A stop job for unit
Additional points:
* Able to always reproduce
* Able to manually mount volumes (doing so as temp workaround)
dpkg -l sssd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err:
Public bug reported:
Running 19.04 beta on a Microsoft Surface Pro 3.
Screen resolution 2160x1440 works in normal landscape mode (Docked mode)
however if I rotate the device 90* clockwise or counter-clockwise, the screen
resolution doesn't change to 1440x2160. The screen actually rotates
I can confirm that removing the extraneous Indicator packages does the
job.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714504
Title:
App indicator is not always displayed
To manage
Since it works under Wayland and not under X, should this be tagged Xorg
rather than Wayland?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714504
Title:
App indicator is not always displayed
To
The same is happening for me with the Synology Cloudstation Client and
additionally, Cadence, the Jackd manager app. Also only happening under X and
not Wayland.
This was actually working before Ubuntu got it's hands on it so it was a recent
update. The version on Gnome Extensions I assume has
Public bug reported:
Referring to this bug: https://github.com/ValveSoftware/steam-for-
linux/issues/3506
The only option to get games working again is to take the libdrm-intel
2.4.56 lib files from the .deb and copy them to your local steam install
as an override for 2.4.60 system lib.
**
Since updating this morning, my Trusty install is now showing:
Apr 4 17:03:26 Gavin dbus[848]: [system] Activated service
'org.freedesktop.login1' failed: Cannot launch daemon, file not found or
permissions invalid
libpam-systemd-204-5ubuntu16
Also can't mount external drives and anything else
I was indeed suffering from
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302264
They have patched systemd-services and things are working again for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that the fix is working for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302264
Title:
systemd-logind assert failure: error.c:319: Assertion failed in
nih_error_get:
Hi,
I've removed 3.12.0-031200-generic and that fixed the issue. I then
went on to do a clean install just for the peace-of-mind that my system
doesn't have any left-overs from all the up/cross-grading of packages in
my attempt to stabilse things.
Now on a fresh install and I am still seeing
@Clint
I'm happy to participate in collecting the data on a quiet day over the
Christmas break when I don't really need to use my computer for any real
activity. Are you talking about a debug-level log of X or something
similar?
Tell me what you would like to see and I'll strip the '-d' from the
I thought I'd try stripping the config back to the original without the
'-d' in the 'exec lightdm -d' line and after six reboots, not one
failure. I'll leave the config in its original state now and if/when the
symptoms reappear, I'll grab all the logs and post them up here.
--
You received this
@Pieter
I agree, it is not a fix (well, a permanent and proper one anyway) but
it does suggest that it's a race condition and that it is in the Binary
itself and not the /etc/init/lightdm script as some of the other
potential fixes have tried to remedy.
--
You received this bug notification
@Joseph S,
I'm installaing 3.7.0-7.15
(https://launchpad.net/~francisbrwn9/+archive/kernels/+build/4065747) in
an effort to solve another problem so I will let you know how this
Kernel goes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Errata: Wrong Kernel link. It should be https://launchpad.net/~xorg-
edgers/+archive/ppa/+build/4065823. It's the Kernel that is part of
xorg-edgers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Joseph,
Well there's no difference by using the xorg-edgers Kernel:
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.407752] usb 3-4: new full-speed USB
device number 3 using xhci_hcd
Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426452] usb 3-4: New USB device
found, idVendor=046d, idProduct=c52b
Dec
@Joseph,
Ok, I've now installed the Kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.7-raring/ and I am still getting the exact same error
messages. The device will always work if I hotplug once booted.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm installaing 3.7.0-7.15 (https://launchpad.net/~xorg-
edgers/+archive/ppa/+build/4065823) in an effort to solve another
problem so I will let you know how this Kernel goes. It's the Kernel
that is part of xorg-edgers.
Well there's no difference by using the xorg-edgers Kernel:
Dec 17 04:32:54
Ok, I've now installed the Kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.7-raring/ and I am still getting the exact same error
messages. The device will always work if I hotplug once booted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Daniel (internalkernel)
Just confirming so it isn't lost in the midst, you changed
'exec lightdm'
to
'exec lightdm -d'
and now you are getting Lightdm performing correctly each time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the exact same hardware as the OP and the same symptoms. Is there
any information I can submit to progress this bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028806
Title:
This bug has a lot of information in it and it is still marked as
incomplete. I am happy to help contribute information to progress this
report. Just let me know what information is required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In the /etc/init/lightdm.conf I've changed
exec lightdm
to
exec lightdm -d
as a way to catch some extra debugging information in the lightdm log file and
lo, now it never fails.
Hmmm, I wonder if writing debug information as slowed things down just enough
to avoid a race condition inside the
We need to get this bug assigned and marked with priority. This problem
when in the hands of a non-technical Ubuntu user will not go to and TTY
to run 'sudo lightdm'. A non-technical user would just say that its
broken and install another OS. This bug is going to cause customer
attrition if it
Actually, manually running sudo lightdm does no always work for me
either. I'm starting to wnder if this is fixable by modifying the init
scripts or whether the problem is deeper in LightDM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've tried adding and stopped udevtrigger and sleep x and both work
more often than not but it is still unreliable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969489
Title:
lightdm tries (and
After a surprising 5 successful restarts with 'sleep 6' added into
/etc/init/lighdm.conf file, I thought that some recent updates might
have fixed it. I've kept an eye on the updates that were being applied
and they don't look to be related but hey, the proof was in the pudding
- five successful
Ok all, I've done some digging around it Lightdm is trying to start
before UDEV reports the graphics devices as being ready. Please see
#969489
By adding 'and stopped udevtrigger to lightdm.conf has fixed the issue
for me.
/etc/init/lightdm.conf:
start on ((filesystem
and runlevel
All,
There is a lot more heat in #1066410 but not as much progress as I've
seen here. I've suggested that #1066410 is marked as a duplicate of this
ticket and those people come here and mark it as affecting them also.
--
You received this bug notification because you are a member of Ubuntu
It certainly looking like some kind of race condition when SSDs are involved.
Adding a sleep x command doesn't help no matter how many seconds I tell it to
sleep for.
Also starting lightdm manually (instead of using the init script) more often
fails than succeeds. This confirms for me that it
54 matches
Mail list logo
