Hi,
I am running a multiseat system and I am used to be simultanously logged in either the two seats (two different KDE sessions) with the same username.
Either KDE sessions use a custom $KDEHOME just to be sure not to mess around with configs and such.

After upgrade to Ubuntu Quantal (and consequent upgrade to KDE4.9.2) I am no more able to mount/umount removeable devices from within the device notifier in the second opened (in time) session.
This seems very odd to me because if I type

Code: Select all

udisksctl mount -b /dev/usbstick

from either sessions, the device get mounted successfully, so it seems something related to KDE/(dbus?).

Don't know if this could be a distribution specific or an upstream issue, any clue?

Can you check (using ck-list-sessions) to see which session the system believes is active? It is probable that the permission to mount/unmount disks is restricted to the active session.

bcooksley wrote:Can you check (using ck-list-sessions) to see which session the system believes is active? It is probable that the permission to mount/unmount disks is restricted to the active session.

And that's indeed the case. Session2 (actually the second seat) doesn't have any physical input device attached since keyboard and mice are shared between the two seats via synergy. Session73 (first seat) is the synergy server, Session2 the client. Didn't found a better way to achieve input sharing, maybe I'll try with xinput.

Is there a way to force a CK session to be active ?

Code: Select all

$ ck-list-sessions
Session73:
        unix-user = '1000'
        realname = 'Francesco'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ':0'
        x11-display-device = '/dev/tty7'
        display-device = ''
        remote-host-name = ''
        is-local = TRUE
        on-since = '2012-11-09T02:45:48.773438Z'
        login-session-id = '4294967295'
Session2:
        unix-user = '1000'
        realname = 'Francesco'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ':1'
        x11-display-device = '/dev/tty8'
        display-device = ''
        remote-host-name = ''
        is-local = TRUE
        on-since = '2012-10-31T00:41:33.162937Z'
        login-session-id = '4294967295'


This explains it perfectly - as UDisks will only perform actions for those users who are authorised by PolKit - which is set to only permit mounting or unmounting of disks by the active user.

I'm not sure if there is a way to forcibly set a particular session as active unfortunately though, you may wish to read the ConsoleKit documentation though - as that may indicate a possible solution.

That's good to know. I'll dig into consolekit documentation.