MGAA-2012-0217
| Date: | November 6th, 2012 |
| Affected releases: | 2 |
Description:
Due the fact that Mageia 2 supports both systemd and sysvinit boot systems,
it has not yet been fully transitioned away from the deprecated consolekit
system for tracking user sessions. Overall a combination of logind and
consolekit tracking is used in different circumstances.
udev device ACLs are typically handled by logind. In order to ensure
proper ACLs are added to devices, the startx application was modified to
ensure it did not switch away from the active VT which would have caused
their logind session to become inactive and thus deny the user of any
device ACLs. Preventing VT switch means the logind session remains active.
This is only needed by the small minority of users starting their
graphical environment after logging into a text console.
Conversely, polkit only looks for session information in the consolekit
database. When used with startx, a new consolekit session would be started,
but because only one consolekit session can be active at once, the previous
text session would remain active. As a result polkit would only find the
inactive consolekit session and typically deny the user access to any
policy where allow_active = yes. This includes things like mounting
removable media.
In order to resolve these issues and still support both systemd and
consolekit, the following actions were taken.
1. polkit is now packaged to include both logind and consolekit support.
It automatically picks the most appropriate backend depending on
whether the system was booted with systemd or sysvinit.
2. startx was modified to only prevent VT switch when booted under systemd.
With these two changes, startx now works almost as well as a proper
Display Manager for most functions.
Updated Packages:
lib(64)polkit1_0-0.104-4.1.mga2
lib(64)polkit1-devel-0.104-4.1.mga2
lib(64)polkit-gir1.0-0.104-4.1.mga2
polkit-0.104-4.1.mga2
polkit-desktop-policy-0.104-4.1.mga2
xinit-1.3.2-3.1.mga2
References:
https://bugs.mageia.org/show_bug.cgi?id=7593
