There may be more detail with these two bug reports:
The issue is the upstream changes for the screen auto-rotation impacts the
touchpad on majority of 2-in-1 laptops.
See https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1846 and
I have a Lenovo Yoga 7 Gen7 (14ial7) 12thGen Intel CPU and I am having
the exact same issue. Monitor-sensor reports everything is correct and
yet the rotation doesn't work under Wayland but it does with X.
Only adding a comment here are this is another model number of a 2-in-1
exhibiting this
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 Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
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 Desktop
Packages, 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
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,
@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
@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 Desktop
Packages, 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 Desktop
Packages, which is subscribed
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 Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/969489
Title:
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 Desktop
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
20 matches
Mail list logo
