Hi,
On 15 September 2011 13:41, Matthias Clasenmatthias.cla...@gmail.com wrote:
gdbus introspect --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1
Hmm that does not seem to offer either a method to get the active session,
nor a method to go from a pid (the pid of
On 16 September 2011 13:17, Hans de Goede hdego...@redhat.com wrote:
Hmm, I cannot find this in gnome-settings-daemon-3.1.91
git master, sorry.
Richard.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
Hi,
On 09/14/2011 04:40 PM, Tomasz Torcz wrote:
On Wed, Sep 14, 2011 at 04:26:20PM +0200, Hans de Goede wrote:
Currently the linux spice-vdagent is using ConsoleKit to
figure out (for the first seat, it assumes a vm is single seat):
1) Which session is active (including notification of when
On 15 September 2011 13:41, Matthias Clasen matthias.cla...@gmail.com wrote:
gdbus introspect --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1
FWIW, so gnome-settings-daemon could track the active console I added
ConsoleKit support in an abstract way, on the logic
Hi,
The spice guest agent for Linux consists of a system level
process (a daemon) and a per session process (started for
each active xsession).
Currently the linux spice-vdagent is using ConsoleKit to
figure out (for the first seat, it assumes a vm is single seat):
1) Which session is active
On Wed, Sep 14, 2011 at 04:26:20PM +0200, Hans de Goede wrote:
Currently the linux spice-vdagent is using ConsoleKit to
figure out (for the first seat, it assumes a vm is single seat):
1) Which session is active (including notification of when this changes)
2) Which session each session
