You are not logged in.
I recently upgraded to hal-0.5.14-1 and now i get errors saying ck-launch-session: error connecting to ConsoleKit and memory cards wont mount
Rejected send message, 1 matched rules; type="method_call", sender=":1.12" (uid=1000 pid=1195 comm="pcmanfm) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=557 comm="/usr/sbin/hald))
Directory doesn't exist!
I am using compiz as a standalone, this is my ~/.xinitrc
#!/bin/sh
#
setxkbmap -option terminate:ctrl_alt_bksp
exec ck-launch-session ~/.start-fusion.sh
and my ~/.start-fusion.sh
#!/bin/sh
xset m 1 &
numlockx &
xfce4-power-manager &
pcmanfm &
xfce4-panel &
compiz ccp --indirect-rendering
Everything worked fine with the previous hal so i have rolled back in the mean time
Thanks in advance
Edit: funny thing, if i kill x then insert the memory card then log back in it works again
Last edited by guzz46 (2009-12-20 08:44:51)
Offline
Same problem here with:
exec ck-launch-session startlxde
But if I start console-kit-daemon by hand, it's ok. (I put /usr/sbin/console-kit-daemon to /etc/rc.local)
Before upgrade I think hal or dbus autostart console-kit-daemon, but not now.
Offline
You are right that seems to of fixed it, I put /usr/sbin/console-kit-daemon in /etc/rc.local and everythings fine again, thanks
I wounder why its not getting started anymore
Offline
You are right that seems to of fixed it, I put /usr/sbin/console-kit-daemon in /etc/rc.local and everythings fine again, thanks
I wounder why its not getting started anymore
solved, tnx
however, it is ridiculous console-kit-daeomon not starting with hal/dbus...
bug report: http://bugs.archlinux.org/task/17557?pr … t&sort=asc
Last edited by ugaciaka (2009-12-20 10:00:08)
I have never bought on ebay, the macbook I do not like, I do not need facebook or myspace or secondlife
I am not a nerd or lamer or troll or geek or hacker or cracker
and I have never voted to elect berlusconi
Offline
Update to consolekit 0.4.1-2 and it should work fine again. The hal update to 0.5.14 uncovered a bug in consolekit.
Offline
Update to consolekit 0.4.1-2 and it should work fine again. The hal update to 0.5.14 uncovered a bug in consolekit.
Confirmed, consolekit 0.4.1-2 fixes the problem
Thanks that was a quick bug fix
Offline
Hey guys. After the upgrade I can't mount my ipod nano 4th gen anymore.
Dolphin error message:
Some clue?
Last edited by estevao (2009-12-20 15:01:20)
Offline
estevao, see ugaciaka post about adding consolekit to rc.local (as a temporary fix). It seems to work (after added to rc.local and doing a reboot).
--
JSkier
Offline
estevao, see ugaciaka post about adding consolekit to rc.local (as a temporary fix). It seems to work (after added to rc.local and doing a reboot).
read all posts in this thread. especially jgc's post
Give what you have. To someone, it may be better than you dare to think.
Offline
estevao, see ugaciaka post about adding consolekit to rc.local (as a temporary fix). It seems to work (after added to rc.local and doing a reboot).
Hi jskier. I added the line /usr/sbin/console-kit-daemon to my /etc/rc.local file, restarted my computer and the problem still persists.
Thanks.
Offline
jskier wrote:estevao, see ugaciaka post about adding consolekit to rc.local (as a temporary fix). It seems to work (after added to rc.local and doing a reboot).
read all posts in this thread. especially jgc's post
Hi Wonder. I read all posts, but none of them solved my problem.
Thanks.
Offline
Hi Wonder. I read all posts, but none of them solved my problem.
Thanks.
are you sure you have consolekit 0.4.1-2 ? do pacman -Q consolekit
Give what you have. To someone, it may be better than you dare to think.
Offline
estevao wrote:Hi Wonder. I read all posts, but none of them solved my problem.
Thanks.
are you sure you have consolekit 0.4.1-2 ? do pacman -Q consolekit
Yep, i'm running consolekit 0.4.1-2.
[estevao@blackbox ~]$ pacman -Q consolekit
consolekit 0.4.1-2
Thanks in advance.
Offline
wonder wrote:estevao wrote:Hi Wonder. I read all posts, but none of them solved my problem.
Thanks.
are you sure you have consolekit 0.4.1-2 ? do pacman -Q consolekit
Yep, i'm running consolekit 0.4.1-2.
[estevao@blackbox ~]$ pacman -Q consolekit
consolekit 0.4.1-2Thanks in advance.
I've just cobbled through this mess. Automounting of removable media has been broken for me for weeks. It really sucked.
It's now working. I accomplished that by following this thread.
consolekit 0.4.1-2
hal 0.5.14-1
hal-info 0.20091130-1
dbus 1.2.16-1
dbus-core 1.2.16-1
dbus-glib 0.82-2
dbus-python 0.83.0-2.1
I had been trying to repair this without rebooting. I was just stopping/starting kde and hal. Ultimately, I had to reboot the system to get it to work. Perhaps you will find the same. I'm sure I could have tried cycling various components until it started working but a reboot solved it so I don't mind a reboot every few months.
Offline
estevao wrote:wonder wrote:are you sure you have consolekit 0.4.1-2 ? do pacman -Q consolekit
Yep, i'm running consolekit 0.4.1-2.
[estevao@blackbox ~]$ pacman -Q consolekit
consolekit 0.4.1-2Thanks in advance.
I've just cobbled through this mess. Automounting of removable media has been broken for me for weeks. It really sucked.
It's now working. I accomplished that by following this thread.
consolekit 0.4.1-2
hal 0.5.14-1
hal-info 0.20091130-1
dbus 1.2.16-1
dbus-core 1.2.16-1
dbus-glib 0.82-2
dbus-python 0.83.0-2.1I had been trying to repair this without rebooting. I was just stopping/starting kde and hal. Ultimately, I had to reboot the system to get it to work. Perhaps you will find the same. I'm sure I could have tried cycling various components until it started working but a reboot solved it so I don't mind a reboot every few months.
Hi TomB17. I have the same versions of all your packages, and I just restarted my system a couple of minutes ago. Very odd. I'm doing some tests and research right now.
Thanks.
Offline
Any luck, estevao?
I'm running KDE. I also added the consokekit wrapper to my ~/.xinitrc
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
exec ck-launch-session startkde
Offline
Any luck, estevao?
I'm running KDE. I also added the consokekit wrapper to my ~/.xinitrc
#!/bin/sh # # ~/.xinitrc # # Executed by startx (run your window manager from here) # exec gnome-session # exec startkde # exec startxfce4 # ...or the Window Manager of your choice exec ck-launch-session startkde
Hi TomB17. This command line solved the problem, I'm using KDE too. Thanks!
Offline
TomB17 wrote:Any luck, estevao?
I'm running KDE. I also added the consokekit wrapper to my ~/.xinitrc
#!/bin/sh # # ~/.xinitrc # # Executed by startx (run your window manager from here) # exec gnome-session # exec startkde # exec startxfce4 # ...or the Window Manager of your choice exec ck-launch-session startkde
Hi TomB17. This command line solved the problem, I'm using KDE too. Thanks!
I'm using gnome and assumed everyone had ck-launch-session by now Glad it's working for you now.
--
JSkier
Offline
Hi folks
To me this is not solved. When I try to mount a USB hard disk (with KDE 4.3.4), it tries to mount it at some wrong path used by another USB hard disk. Or I have to mount it as root, or even as root it still doesn't work right... pfff I'm really disappointed by this showstopper...
For example, I own a LaCie hard disk (/media/disk), a Iomega one (/media/IOMEGA) and a LaCie mobile disk (no power cable, /media/MobileDisk):
- When I try to mount the Iomega one, it works fine, as normal user;
- When I try to mount the LaCie one, it fails, independently of the fact that the Iomega drive is mounted or not, with the following message:
Unable to run the command specified. The file or folder file:///media/IOMEGA does not exist.
Looks like it wants to mount the LaCie one where the Iomega one is/should be mounted...
- When I connect the LaCie hard disk, the directory /media/MobileDisk
is created, instead of /media/disk
, and when as root I try to manually mount the hard disk, it says:
ntfs-3g: Failed to access volume '/dev/sdb1': No such file or directory
Maybe there's some erroneous entry in some cache or data used by hal/dbus? I don't know how they work and how to activate their logging systems and then where to find the logs...
Maybe there's a way to simply completely wipe out hal/dbus/consolekit/policykit/... configuration data without having to reinstall the complete system?
I have:
hal 0.5.14-1
dbus-core 1.2.16-1
dbus 1.2.16-1
dbus-glib 0.82-2
dbus-python 0.83.0-2
I start KDM using /etc/inittab, as described in the wiki. I've put "/usr/sbin/console-kit-daemon" in /etc/rc.local and have modified /etc/inittab so that it starts kdm with: "x:5:respawn:/usr/bin/ck-launch-session /usr/bin/kdm -nodaemon"!
Is this the right setup, equivalent to the one with xinitrc?
The same setup works fine on my laptop.
I've got the impression that hal/dbus/... confounds my drives and does not know where to mount them...
Downgrading to hal 0.5.13-idontrememberwhatcifer does not solve the issue, the system is kept up to date with "pacman -Syu" about once a day and it still doesn't work...
Some clue?
Thanks and happy new year
Offline