FS#77849 - [xfce4-screensaver] crashes when trying to show lock screen

Attached to Project: Arch Linux
Opened by Jacob Karlsson (Powersource) - Tuesday, 14 March 2023, 12:30 GMT
Last edited by Christian Hesse (eworm) - Monday, 20 March 2023, 15:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

I am able to log in like normal on boot, through the lightdm-slick-greeter. But if I manually lock my screen (not sleep) and then try to wake it again, it's just black, with my spinning cursor on top. Then it goes back to being entirely black after a few seconds, until I wake it again and get the same result.


Additional info:
* package version(s)
lightdm 1:1.32.0-4
lightdm-slick-greeter 1.6.0-1
eos-lightdm-slick-theme 3.2-1
xfce4-screensaver 4.16.0-1

* config and/or log files etc.

This is an excerpt from journalctl. There's a longer excerpt in the attached file.

mar 14 13:04:17.641163 me-lap kernel: traps: xfce4-screensav[76171] general protection fault ip:55fe2080ff71 sp:7ffe506dcfa0 error:0 in xfce4-screensaver-dialog[55fe20808000+b000]
mar 14 13:04:17.649522 me-lap systemd[1]: Created slice Slice /system/systemd-coredump.
mar 14 13:04:17.671742 me-lap systemd[1]: Started Process Core Dump (PID 76197/UID 0).
mar 14 13:04:18.510801 me-lap systemd-coredump[76198]: Process 76171 (xfce4-screensav) of user 1000 dumped core.

Stack trace of thread 76171:
#0 0x000055fe2080ff71 n/a (xfce4-screensaver-dialog + 0xef71)
#1 0x00007f9e0d493afb g_main_context_dispatch (libglib-2.0.so.0 + 0x5aafb)
#2 0x00007f9e0d4f05d9 n/a (libglib-2.0.so.0 + 0xb75d9)
#3 0x00007f9e0d4930cf g_main_loop_run (libglib-2.0.so.0 + 0x5a0cf)
#4 0x00007f9e0d9d8e4f gtk_main (libgtk-3.so.0 + 0x1d8e4f)
#5 0x000055fe20808208 n/a (xfce4-screensaver-dialog + 0x7208)
#6 0x00007f9e0d270790 n/a (libc.so.6 + 0x23790)
#7 0x00007f9e0d27084a __libc_start_main (libc.so.6 + 0x2384a)
#8 0x000055fe208082ce n/a (xfce4-screensaver-dialog + 0x72ce)

Stack trace of thread 76180:
#0 0x00007f9e0d34d0dd syscall (libc.so.6 + 0x1000dd)
#1 0x00007f9e0d4e4ff3 g_cond_wait_until (libglib-2.0.so.0 + 0xabff3)
#2 0x00007f9e0d45df93 n/a (libglib-2.0.so.0 + 0x24f93)
#3 0x00007f9e0d4c3fbb n/a (libglib-2.0.so.0 + 0x8afbb)
#4 0x00007f9e0d4c17c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f9e0d2d2bb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f9e0d354d90 n/a (libc.so.6 + 0x107d90)

Stack trace of thread 76173:
#0 0x00007f9e0d3479df __poll (libc.so.6 + 0xfa9df)
#1 0x00007f9e0d4f053f n/a (libglib-2.0.so.0 + 0xb753f)
#2 0x00007f9e0d491382 g_main_context_iteration (libglib-2.0.so.0 + 0x58382)
#3 0x00007f9e0d4913d2 n/a (libglib-2.0.so.0 + 0x583d2)
#4 0x00007f9e0d4c17c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f9e0d2d2bb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f9e0d354d90 n/a (libc.so.6 + 0x107d90)

Stack trace of thread 76174:
#0 0x00007f9e0d3479df __poll (libc.so.6 + 0xfa9df)
#1 0x00007f9e0d4f053f n/a (libglib-2.0.so.0 + 0xb753f)
#2 0x00007f9e0d4930cf g_main_loop_run (libglib-2.0.so.0 + 0x5a0cf)
#3 0x00007f9e0d6f4e4c n/a (libgio-2.0.so.0 + 0x10fe4c)
#4 0x00007f9e0d4c17c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f9e0d2d2bb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f9e0d354d90 n/a (libc.so.6 + 0x107d90)

Stack trace of thread 76172:
#0 0x00007f9e0d34d0dd syscall (libc.so.6 + 0x1000dd)
#1 0x00007f9e0d4e4a35 g_cond_wait (libglib-2.0.so.0 + 0xaba35)
#2 0x00007f9e0d45dfc4 n/a (libglib-2.0.so.0 + 0x24fc4)
#3 0x00007f9e0d4c343e n/a (libglib-2.0.so.0 + 0x8a43e)
#4 0x00007f9e0d4c17c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f9e0d2d2bb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f9e0d354d90 n/a (libc.so.6 + 0x107d90)
ELF object binary architecture: AMD x86-64
mar 14 13:04:18.541065 me-lap systemd[1]: systemd-coredump@0-76197-0.service: Deactivated successfully.


* link to upstream bug report, if any
Looking for that now
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 20 March 2023, 15:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  xfce4-screensaver 4.18.0-1
Comment by Jacob Karlsson (Powersource) - Tuesday, 14 March 2023, 12:38 GMT
Found an issue about it in their tracker. It seems to have been fixed, now we just need to wait for them to release 4.18.0

https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/119
Comment by Thomas Schuetz (Murray_B) - Tuesday, 14 March 2023, 18:15 GMT
Similar effect with nearly the same journalctl. Additional Info: Downgrading to glib2 2.74.6-1 helps
Comment by Thomas Schuetz (Murray_B) - Tuesday, 14 March 2023, 20:45 GMT
Okay, I tried to patch the sources with the diff from https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/119, that does not seem to work (or I have done it wrong…)
Comment by Jacob Karlsson (Powersource) - Monday, 20 March 2023, 11:58 GMT Comment by Jacob Karlsson (Powersource) - Monday, 20 March 2023, 12:00 GMT
Easiest workaround I've found is, to "unlock" you switch to another session with e.g. ctrl+alt+f2 (ctrl+alt+f7 to go back) and type `killall xfce4-screensaver`

Loading...