[Bug 933626] Re: acpi-support should use ck-list-sessions to determine active X display and X user
Ayan George
ayan.george at canonical.com
Tue Apr 3 18:52:43 UTC 2012
** Tags added: blocks-hwcert-enablement
** Changed in: acpi-support (Ubuntu)
Milestone: None => oneiric-updates
** Description changed:
SRU Justificaiton
-----------------
Impact:
This bug impacts all Oneiric systems which use LightDM and are affected
by lp870297 (Lightdm logins not being logged in wtmp).
In Oneiric, acpi-support depends on wtmp entries to determine the active
console with getXconsole and getXuser. Since LightDM doesn't write to
wtmp, this affects all systems that use acpi-support scripts to handle
ACPI hotkey events -- including yet to be released hardware in the
enablement/certification queue.
Fix:
The fix is to backport the changes made in Precise to Oneiric. This
includes implementing getXuser and getXconsole with ConsoleKit (ck-list-
sessions).
Patch:
This change is already in acpi-support .139:
- http://launchpadlibrarian.net/95198647/acpi-
+ http://launchpadlibrarian.net/95198647/acpi-
support_0.138_0.139.diff.gz
I've attached a debdiff that backports that change to acpi-support .139
in Oneiric.
Regression Potential:
There should be very little potential for regression. In fact, this
should fix machines affected by lp87029, including OEM systems.
+
+ This has been tested using the following PPA:
+
+ https://launchpad.net/~ayan/+archive/acpi-support-sru
------------------------
The acpi-support scripts use 'ps' and 'who' output to determine the
current active X display and X user (in getXconsole and getXuser).
Currently, LightDM does not write to utmp so 'who' does not output the
correct information breaking getXconsole and getXuser.
ConsoleKit properly maintains the state of the console and probably
should be used instead.
I've attached a patch that re-implements getXconsole and getXuser by
calling ck-list-sessions.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to acpi-support in Ubuntu.
https://bugs.launchpad.net/bugs/933626
Title:
acpi-support should use ck-list-sessions to determine active X display
and X user
Status in “acpi-support” package in Ubuntu:
Fix Released
Bug description:
SRU Justificaiton
-----------------
Impact:
This bug impacts all Oneiric systems which use LightDM and are
affected by lp870297 (Lightdm logins not being logged in wtmp).
In Oneiric, acpi-support depends on wtmp entries to determine the
active console with getXconsole and getXuser. Since LightDM doesn't
write to wtmp, this affects all systems that use acpi-support scripts
to handle ACPI hotkey events -- including yet to be released hardware
in the enablement/certification queue.
Fix:
The fix is to backport the changes made in Precise to Oneiric. This
includes implementing getXuser and getXconsole with ConsoleKit (ck-
list-sessions).
Patch:
This change is already in acpi-support .139:
http://launchpadlibrarian.net/95198647/acpi-
support_0.138_0.139.diff.gz
I've attached a debdiff that backports that change to acpi-support
.139 in Oneiric.
Regression Potential:
There should be very little potential for regression. In fact, this
should fix machines affected by lp87029, including OEM systems.
This has been tested using the following PPA:
https://launchpad.net/~ayan/+archive/acpi-support-sru
------------------------
The acpi-support scripts use 'ps' and 'who' output to determine the
current active X display and X user (in getXconsole and getXuser).
Currently, LightDM does not write to utmp so 'who' does not output the
correct information breaking getXconsole and getXuser.
ConsoleKit properly maintains the state of the console and probably
should be used instead.
I've attached a patch that re-implements getXconsole and getXuser by
calling ck-list-sessions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/933626/+subscriptions
More information about the foundations-bugs
mailing list