[Bug 2056331] [NEW] [SRU] fix suspend/resume when there are no input devices

Launchpad Bug Tracker 2056331 at bugs.launchpad.net
Fri Apr 12 17:15:42 UTC 2024


You have been subscribed to a public bug by Talha Can Havadar (tchavadar):

[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

** Affects: xorg-server
     Importance: Unknown
         Status: Fix Released

** Affects: xorg-server (Ubuntu)
     Importance: Medium
     Assignee: Talha Can Havadar (tchavadar)
         Status: Fix Committed

** Affects: xorg-server (Ubuntu Jammy)
     Importance: Medium
     Assignee: Talha Can Havadar (tchavadar)
         Status: In Progress

** Affects: xorg-server (Ubuntu Mantic)
     Importance: Undecided
     Assignee: Talha Can Havadar (tchavadar)
         Status: In Progress

** Affects: xorg-server (Ubuntu Noble)
     Importance: Medium
     Assignee: Talha Can Havadar (tchavadar)
         Status: Fix Committed


** Tags: jammy noble patch
-- 
[SRU] fix suspend/resume when there are no input devices
https://bugs.launchpad.net/bugs/2056331
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list