Hello Timo, On jammy, ``` No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy ``` I was able to reproduce the issue using old version of the xorg-server package(2:21.1.4-2ubuntu1.7~22.04.10), for the ones who are curious about the bug, first you need to boot the board with keyboard/mouse connected to usb and display attached and then login as usual. Then remove all usb device and follow the steps in bug description through tty console.
After enabling -proposed and updating xorg-server packages to 2:21.1.4-2ubuntu1.7~22.04.11, I followed the same steps to reproduce the bug. I can confirm that the bug has been fixed with 2:21.1.4-2ubuntu1.7~22.04.11 Thank you all! ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2056331 Title: [SRU] fix suspend/resume when there are no input devices Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Mantic: Fix Committed Status in xorg-server source package in Noble: Fix Released Bug description: [Impact] Bug is impacting the suspend/resume flow when there is no input device connected to machine. xorg hangs in this case. [Where problems could occur] The problem could occur in places where there is no input device connected to the system but a suspend/resume is triggered. [Test Case] * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed) * Update xorg-server to the version in -proposed: sudo apt install -t jammy-proposed xorg-server * Unplug all USB devices such as USB drive, keyboard, mouse, etc. * Set RTC timer and suspend the system via UART console $ echo 8 > /proc/sys/kernel/printk $ sudo rtcwake -v -m no -s 240 $ sudo systemctl suspend [Regression Potential] The patch defines a default behavior in systemd_logind_drop_master function so there is a possibility that there might be a regression that may affect all the systems that utilizes systemd_logind_drop_master ------------------------ Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2056331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
