can't unlock and xfce4-screensaver-dialog segfaults if weston running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xfce4-screensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
laptop running xubuntu 22.04.4, logged into xubuntu session.
xfce4-screensaver 4.16.0-1
weston 9.0.0-4ubuntu1
firefox 125.0.3-1 (snap)
Run firefox.
In terminal: tail -f /var/log/syslog
In another terminal: weston
Lock the screen by hotkey calling: xflock4
Press key to bring up dialog but only black shows - can see backlight periodically turning on/off and flashes of cursor when pressing keys.
Ctrl-Alt-F1; login; pkill weston; Alt-F7 back to locked session.
Now unlocking works normally again.
However, after unlocking, many firefox empty windows have been created.
/var/log/syslog shows new output:
May 9 02:02:55 hostname kernel: [387457.737377] xfce4-screensav
May 9 02:02:55 hostname kernel: [387457.737387] Code: 57 82 fc ff 49 8b 9c 24 70 01 00 00 48 85 db 74 4e 49 89 c5 eb 0a 0f 1f 44 00 00 48 85 db 74 3f 48 8b 2b 48 89 de 48 8b 5b 08 <48> 8b 45 08 48 85 c0 74 e8 4c 39 e8 7f e3 49 8b bc 24 70 01 00 00
May 9 02:02:55 hostname xfce4-screensav
May 9 02:02:57 hostname kernel: [387459.627666] xfce4-screensav
May 9 02:02:57 hostname kernel: [387459.627676] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff
May 9 02:03:01 hostname kernel: [387464.025803] xfce4-screensav
May 9 02:03:01 hostname kernel: [387464.025813] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff
May 9 02:03:03 hostname kernel: [387466.135825] xfce4-screensav
May 9 02:03:03 hostname kernel: [387466.135837] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff
May 9 02:03:07 hostname kernel: [387469.786031] xfce4-screensav
May 9 02:03:07 hostname kernel: [387469.786041] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff
May 9 02:03:08 hostname kernel: [387471.125899] xfce4-screensav
May 9 02:03:08 hostname kernel: [387471.125909] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff
May 9 02:03:09 hostname wireplumber[2810]: [string "policy-
May 9 02:03:09 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:09 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:09 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:09 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:10 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:13 hostname wireplumber[2810]: SPA handle 'api.bluez5.
May 9 02:03:13 hostname wireplumber[2810]: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported.
May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.
May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.
I discovered that invoking weston as `weston --socket=something` prevents the segfaults.
But perhaps there should be some code in the screensaver to detect this problem and prevent the crash?