On Sun, Jun 05, 2011 at 11:03:54PM +0100, Mick wrote:
> Both consolekit and polkit are running. What could be the problem?
>
> $ ps axf | grep polkit
> 8961 pts/1 SN+ 0:00 \_ grep
> --color=auto polkit
> 5678 ? Sl 0:00 /usr/libexec/polkitd
>
> $ ps axf | grep console
> 5594 ? Ssl 0:00 /usr/sbin/console-kit-daemon
> 9088 pts/1 SN+ 0:00 \_ grep
> --color=auto console
>
>
> I'm starting e17 WM running startx on this box, unlike another
> similarly configured machine where mounting devices works fine but I
> start that with /etc/init.d/xdm (kdm).
that console-kit-daemon is running doesn't mean your session is
'registered' with it, you can check with ck-list-sessions
yoyo@tabletka ~ $ ck-list-sessions
Session18:
unix-user = '1000'
realname = '(null)'
seat = 'Seat18'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/ssh'
remote-host-name = ...
is-local = FALSE
on-since = '2011-06-06T07:48:11.669544Z'
login-session-id = ''
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2011-06-01T17:09:37.282998Z'
login-session-id = ''
the defaults for disk mounting should be that only active (local?) sessions
can do it...
here it seems that a normaln console (text) / ssh seesions
are registered in ck through pam, but X session's have to do that
manulally, which i guess is done either in DM's xsession script or in
the startup script of the chosen DE ...
if your session is not thare, then just add ck-launch-session to the
script you use to start the X session (~/.xinitrc in your case i guess, or
the script you specify to startx)
yoyo
