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

Daniel van Vugt 2056331 at bugs.launchpad.net
Fri Mar 8 01:51:35 UTC 2024


** Also affects: xorg-server (Ubuntu Noble)
   Importance: Medium
       Status: Triaged

** Also affects: xorg-server (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Changed in: xorg-server (Ubuntu Jammy)
       Status: New => In Progress

** Changed in: xorg-server (Ubuntu Noble)
       Status: Triaged => In Progress

** Changed in: xorg-server (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: xorg-server (Ubuntu Jammy)
     Assignee: (unassigned) => Talha Can Havadar (tchavadar)

** Changed in: xorg-server (Ubuntu Noble)
     Assignee: (unassigned) => Talha Can Havadar (tchavadar)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
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:
  In Progress
Status in xorg-server source package in Jammy:
  In Progress
Status in xorg-server source package in Noble:
  In Progress

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




More information about the Ubuntu-sponsors mailing list