[Mageia-dev] ConsoleKit vs systemd session tracking for Mageia 2
Guillaume Rousse
guillomovitch at gmail.com
Sun Feb 26 22:47:42 CET 2012
Le 23/01/2012 15:51, Olav Vitters a écrit :
> FYI,
>
> A bunch of GNOME modules now have --enable-systemd configure flags. This
> will make them use systemd instead of (deprecated ConsoleKit) to track
> login sessions.
>
> I made a tracker bug on GNOME Bugzilla:
> https://bugzilla.gnome.org/show_bug.cgi?id=systemd
>
> Modules I noticed (and added to the tracker bug):
> - NetworkManager
> - gnome-settings-daemon
> - gnome-session
> - gnome-control-center
> - gnome-packagekit
> - system-monitor
>
> And related to systemd:
> - gnome-control-center (timedated)
> This just relies on the daemon to be there; systemd doesn't need to
> be running (99% sure of this), the daemon is part in the systemd
> tarball.
> We do need to ensure Mageia 2 always has timedated. This is used to
> change the timezone and so on btw.
>
>
> These seem to be compile time checks. Meaning: if --enable-systemd is
> added to ./configure, the functionality won't work on sysvinit. I am not
> sure exactly what will break under sysvinit. The bugreports to contain
> some discussion though.
I don't know if you performed some actual changes, but I'm facing
painful session start issue now:
https://bugs.mageia.org/show_bug.cgi?id=4708
--
The higher the "higher-ups" are who have come to see your demo, the
lower your chances are of giving a successful one
-- Fundamental Law of Thermodynamics n°4
More information about the Mageia-dev
mailing list