[SOLVED] Neither console, nor policy kits seem to run

Question

I have installed a couple of hours ago compiz standalone, removed any display managers I had before from inittab and now I run it through .xinitrc.
But neither console nor policy kits seem to run or grant privileges to normal users for mounting usb devices or just shutdown, syspend etc.
My .xinitrc:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
# exec gnome-session
# exec startkde
# exec ck-launch-session wm
# exec enlightenment_start
# exec startxfce4
exec ck-launch-session dbus-launch --sh-syntax --exit-with-session $HOME/.xstart
My .xstart:
#!/bin/sh
compiz ccp &
tint2 &
fbxkb &
trayfreq &
volti &
blueman-applet &
wicd-gtk &
parcellite &
fusion-icon -n
My inittab (i reverted back to agetty and see if it works but not):
# /etc/inittab
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
## Only one of the following two lines can be uncommented!
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
#c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
#c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux
#c1:2345:respawn:/sbin/fgetty tty1 linux
#c2:2345:respawn:/sbin/fgetty tty2 linux
#c3:2345:respawn:/sbin/fgetty tty3 linux
#c4:2345:respawn:/sbin/fgetty tty4 linux
# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 38400 hvc0 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/sbin/elsa --nodaemon
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1
#x:5:respawn:/usr/sbin/lxdm >& /dev/null
x:5:once:/bin/su - -- twilight -l -c '/usr/bin/startx -- -nolisten tcp -br -deferglyphs 16 </dev/null >/dev/null 2>&1'
# End of file
ck-list-sessions:
Session1:
unix-user = '1000'
realname = 'Tasos'
seat = 'Seat2'
session-type = ''
active = FALSE
x11-display = ':0'
x11-display-device = '/dev/tty5'
display-device = ''
remote-host-name = ''
is-local = FALSE
on-since = '2011-09-30T20:02:05.547676Z'
login-session-id = ''
No relevant errors found in .xsession-errors:
(lxpanel:11415): Gtk-WARNING **: Unable to locate theme engine in module_path: "thinice",
(pcmanfm:11416): Gtk-WARNING **: Unable to locate theme engine in module_path: "thinice",
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0xa000a4
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0xa000a4
QSystemTrayIcon::setVisible: No Icon set
kdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kbuildsycoca4 running...
kbuildsycoca4(11472) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(11472) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(11472) kdemain: Emitting notifyDatabaseChanged ()
yakuake(11440)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkonsolepart.so"
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.14'
yakuake(11440) KGlobalAccelPrivate::_k_serviceOwnerChanged: detected kglobalaccel restarting, re-registering all shortcut keys
(<unknown>:11498): Gtk-WARNING **: Unable to locate tkded4: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
e to locate theme engine in module_path: "thinice",
(lxterminal:13327): Gtk-WARNING **: Unable to locate theme engine in module_path: "thinice",
(lxsession-logout:13435): Gtk-WARNINGkded4: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
error: client killed
klauncher: Exiting on signal 15
kded4: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
Last edited by twilight0 (2011-11-15 10:16:07)

Answer 1

Never mind it didnt notice the warning here:
wiki wrote:Warning: This method will not use /bin/login or register your session, therefore no session will appear in `who` or `w`. Your session will also not be authorized as 'local' by ConsoleKit, so you will be unable to shutdown/suspend/reboot or mount drives without using sudo or su.
But is there a way after all to run console kit even if the session isn't registered as local?
Last edited by twilight0 (2011-09-30 21:12:09)