#1032039 xorg: xserver fails to recover session after locking (xfce4 / lightdm)

Package:
xorg
Source:
xorg
Description:
X.Org X Window System
Submitter:
Dimitri Chausson
Date:
2023-03-16 10:09:03 UTC
Severity:
normal
#1032039#5
Date:
2023-02-26 21:15:26 UTC
From:
To:
Dear Maintainer,

Xfce is set up to lock the screen after a while. When I want to login again to
get back to the opened session,  I am prompted to type my password (the username
 is already filled). When the enter key is pressed down, a kind of "re-init"
takes place I see the login screen again, but this time, I have to enter my
username + password. I get logged in, but it is a new session.. None of the
applications left open before is active.

I did a diff between both Xorg.*.log file before locking takes place and after,
and the server crashes in-between: the trace is as follows:
----begin----
[  5346.907] (II) VESA(0): Setting up VESA Mode 0x1D4 (1920x1200)
[  5346.908] (EE)
[  5346.908] (EE) Backtrace:
[  5346.908] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x556f389e2cf9]
[  5346.908] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f382885af90]
[  5346.909] (EE) 2: /lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_get_info+0x2ad) [0x7f38292cffdd]
[  5346.909] (EE) 3: /usr/lib/xorg/modules/libint10.so (xf86int10Addr+0x72a) [0x7f38281a0f1a]
[  5346.909] (EE) 4: /usr/lib/xorg/modules/libint10.so (xf86int10Addr+0x7834) [0x7f38281a8024]
[  5346.909] (EE) 5: /usr/lib/xorg/modules/libint10.so (xf86ExecX86int10+0x45) [0x7f382819f995]
[  5346.909] (EE) 6: /usr/lib/xorg/modules/libint10.so (VBESetVBEMode+0x76) [0x7f382819c486]
[  5346.909] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  5346.909] (EE) 7: /usr/lib/xorg/modules/drivers/vesa_drv.so (?+0x0) [0x7f3828592200]
[  5346.910] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  5346.910] (EE) 8: /usr/lib/xorg/modules/drivers/vesa_drv.so (?+0x0) [0x7f3828592405]
[  5346.910] (EE) 9: /usr/lib/xorg/Xorg (xf86AllocateLinearOffscreenArea+0x1497) [0x556f388b6127]
[  5346.910] (EE) 10: /usr/lib/xorg/Xorg (xf86VTEnter+0x81) [0x556f388aee31]
[  5346.910] (EE) 11: /usr/lib/xorg/Xorg (WakeupHandler+0xb3) [0x556f38874243]
[  5346.910] (EE) 12: /usr/lib/xorg/Xorg (WaitForSomething+0x198) [0x556f389dc6b8]
[  5346.910] (EE) 13: /usr/lib/xorg/Xorg (SendErrorToClient+0x113) [0x556f3886f473]
[  5346.910] (EE) 14: /usr/lib/xorg/Xorg (InitFonts+0x3bc) [0x556f388736cc]
[  5346.910] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7f382884618a]
[  5346.911] (EE) 16: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) [0x7f3828846245]
[  5346.911] (EE) 17: /usr/lib/xorg/Xorg (_start+0x21) [0x556f3885cb71]
[  5346.911] (EE)
[  5346.911] (EE) Segmentation fault at address 0x0
[  5346.911] (EE)
Fatal server error:
[  5346.911] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  5346.911] (EE)
[  5346.911] (EE)
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
[  5346.911] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  5346.911] (EE)
----end------

Hopefully, you can help me, I can provide more information if needed,

Thanks for your work,

Dimitri

#1032039#10
Date:
2023-03-16 10:04:36 UTC
From:
To:
Dear Maintainer,
I tried to add source line information to the Xorg backtrace:

fdd in inl at /usr/include/x86_64-linux-gnu/sys/io.h:83  (pci_device_linux_sysfs_read32+93)
f1a in x86emuOp_in_word_AX_DX at ../../../../../../hw/xfree86/int10/../x86emu/ops.c:10364
024 in X86EMU_exec at ../../../../../../hw/xfree86/int10/../x86emu/decode.c:135
995 in xf86ExecX86int10 at ../../../../../../hw/xfree86/int10/xf86x86emu.c:39
486 in VBESetVBEMode at ../../../../../../hw/xfree86/int10/vbe.c:473
200 in VESASetMode at ../../src/vesa.c:1247
405 in VESAEnterVT at ../../src/vesa.c:1166
127 in CMapEnterVT at ../../../../../../hw/xfree86/common/xf86cmap.c:475
e31 in xf86VTEnter at ../../../../../../hw/xfree86/common/xf86Events.c:456
243 in WakeupHandler at ../../../../dix/dixutils.c:427
6b8 in WaitForSomething at ../../../../os/WaitFor.c:210
473 in Dispatch at ../../../../dix/dispatch.c:492
6cc in dix_main at ../../../../dix/main.c:272

The used kernel version is not from current testing.
Could that be the reason why the vesa driver
gets selected at all in the first place?


Kind regards,
Bernhard