hal not working in kde

JDHarris · n00b Joined: 24 Oct 2004 Posts: 45

I have this same issue as well. Same program versions... It worked up until about a week ago, now the devices are always shown as being unmounted in the media:/ kioslave. If I double click on them, the device gets mounted, but konqueror does not list any files. If I browse directly to the /media/<devName> directory, I can see that the files are all there and it is mounted properly. Would love to get a solution to this issue...

It's also worth noting that this seems to only affect Konqueror and the media:/ kioslave. When I plug in my iPod and double click it in the media:/ kioslave to mount it, amarok is able to connect to the iPod and play music from it. Amarok also shows the correct mount location. But Konqueror still shows the volume as being unmounted and will create new folders in /media every time you double click the device.
_________________
Athlon 64 3500+
2 GB of RAM
2 74GB Raptors RAID 0
nVidia GeForce 6800 GT 256 MB

micmac · l33t Joined: 28 Nov 2003 Posts: 985

Could this be a kernel issue? I'm just thinking. 2.6.19 was released about a week ago, so maybe that's where the trouble comes from. Any of you got the same problems with 2.6.19 and 2.6.18?

genus · n00b Joined: 25 Aug 2004 Posts: 53

anz · Apprentice Joined: 05 Feb 2003 Posts: 279 Location: Vienna

Dear micmac,
I have three gentoo boxes, all running with gentoo-sources-2.6.18-r3. "Only" one has the problems with the automount under kde.
Yesterday I compiled on the trouble computer an older kernel (2.6.16-r9), and the new gentoo-sources-2.6.18-r4 to check - same result as with 2.6.18-r3.
_________________
Greetings from Vienna

julakali · n00b Joined: 27 Mar 2006 Posts: 26

genus:
as you have installed the dbus ~x86 package, did you emerge dbus-qt3-old ?
I guess it is needed...

edit:
i am running 2.6.18-gentoo-r4, my apps are configured as follows:

anz · Apprentice Joined: 05 Feb 2003 Posts: 279 Location: Vienna

Thanks alot, Dear julakali,

I had nothing to loose, so I updated to dbus-1.0.2:

jure1873 · Apprentice Joined: 09 Feb 2006 Posts: 183

hmm went back from stable to unstable and added the libdbus-1.so.2 link and now it's working

I just wish I knew what was wrong...

MAGGETTE · n00b Joined: 01 Jan 2006 Posts: 22

Hi, I've a similar problem

I'm trying to automount an USB pen drive but since I use kde 3.5.5 it's "impossible", the same problem with a SD Card. However CD-Rom automount perfectly.

I'm using

- reiser4-gentoo-sources-2.6.17-r7
- sys-apps/hal-0.5.7-r3
- sys-fs/udev-103
- sys-apps/pmount-0.9.9
- sys-apps/dbus-0.62-r2
- kde-base/kdebase-3.5.5-r1
- USE="... hal ..." on make.conf
- fstab without lines about cdrom, usb, etc...

Before i had ivman, but I've read on the forum that is not necessary.

I've proved to upgrade hal, dbus and pmount but I had the same problem so I've downgrade to stable versions

Could anyone help me?

RoundsToZero · Guru Joined: 17 Nov 2003 Posts: 478 Location: New York, NY

Sorry if this has already been solved for the person who asks, but it's possible that xdm (kdm) could start up before dbus even without parallel startup enabled. When xdm starts, the X server starts right away and you can log in, even before the login prompt would display at the terminal. That is, you could log into KDE while services are still starting.

For me, dbus and hal happen to start before xdm so it's fine. A quick hack would be just to put /etc/init.d/xdm start in /etc/conf.d/local.start (so that xdm definitely starts last). Or you could try an alternative way to change startup ordering. I'm not really sure how it works, other than that the ordering is dependency based. So maybe if you added a hal dependency to the xdm startup script...

Tagx · n00b Joined: 18 Apr 2006 Posts: 61

I tried reemerging dbus, dbus-glib, dbus-qt3-old, hal, and kdebase-kioslaves in that order. I also tried making the symlink but still no luck

psychomunky · Guru Joined: 02 Nov 2004 Posts: 337 Location: Canada

I have had similar problems to these described above. One of the following two solutions (or both) have fixed this for me:

1. revdep-rebuild (usually rebuilds a flaky kdelib)
2. emerge -avC pmount ivman (neither of these packages are needed for kde to automount anymore)

psycepa · Veteran Joined: 27 Dec 2004 Posts: 1637 Location: Poland

Hi
thanks for the tips
they allowed me to get hal to automatically mount cds
but I have another problem
I am using a mobile disk of 80GB which is connected by usb and is detected by the system as /dev/sda1

the problem is that there is a ntfs filesystem (don't ask)
after connecting the device, an icon of a removable media appears on a kde desktop but if I click on it from the user level konquerror says that it cannot enter the /media/disk location

I have tried to add appropriate entry to /etc/fstab but after that the message changed to 'no access' or sth similar (can't translate it 'cause kde gives me messages in my language)

normally I am using ntfs-3g to mount this device and everything works like a charm (ie after mounting it by root I can't access data from the user account but I can easily do it from the root account itself, of course from the commandline)

so here the question appears:
how to force kde to allow common user to acces this disk and how to force hal to mount it using ntfs-3g driver?

I have searched the /etc/ dir but couldn't find any config file, maybe I have just overlooked it, it is quite late here

so I would appreciate any constructive advices

greetingz gentoorianz
_________________
RLUNo. 376073
bo czytac, to trzeba ze zrozumieniem (c) by psycepa
"nigdy nie kloc sie z glupcem, najpierw sprowadzi cie do swojego poziomu a potem pokona doswiadczeniem"
"Life is complex. It has its real and imaginary part."

Clansman · Tux's lil' helper Joined: 10 Jan 2004 Posts: 140

Hi everyone,

Just a follow-up sucess story:
I've been having this problem and I solved it today after a bit of looking around in the forum...

I have dbus-1.0.2, hal-0.5.7.1-r2 and kdebase-kioslaves-3.5.5. Trying to emerge kdebase-kioslaves forced me to downgrade dbus to 0.62, but I didn't want that so I forced the build with --nodeps. It compiled fine, but still no media manager.
Later I tried emerging dbus-qt3-old-0.70 and kdebase-kioslaves became happy with dbus-1.0.2.

I emerged kdebase-kioslaves and did a quick revdep-rebuild to check things, restarted X and voilÃ¡! KDE media manager is back!

Best regards,
_________________
http://www.pjvenda.org

batistuta · Veteran Joined: 29 Jul 2005 Posts: 1384 Location: Aachen

I've read this thread but I'm really confused since people seem to be using different layouts. For example, ivman is since long ago not needed *if* using KDE and I believe Gnome has its own approach as well.

The bottom line, is that I can't mount any removable device in KDE. I don't see anything in /media, no icon in the desktop either. Dmesg reports the device correctly though. I'm running ~x86, and I don't mind downgrading but I haven't read anyone that has identified the 1-x versons as the actual issue.

@headrush: you've mentioned very briefly something about 1-x versions. Was this just a guess or do you think this could be a problem? Thanks

batistuta · Veteran Joined: 29 Jul 2005 Posts: 1384 Location: Aachen

One issue, is that it is not possible to just try reverting to stable for the sake of trying. The problem is that a lot of apps

Clansman · Tux's lil' helper Joined: 10 Jan 2004 Posts: 140

Perhaps this is one case where the same thread has different problems that generate very similar simptoms... maybe we should call Dr. House

*My* problem was the combination and incompatibility between the following packages:
dbus-1.x
kdebase-kioslaves-3.5.5

I solved it by:
emerging dbus-qt3-old-0.70
reemerging dbux-1.x
reemerging hal-0.5.7.1 (just to be on the safe side)
reemerging kdebase-kioslaves-3.5.5

restart xdm (maybe just a session logout and login is enough...)

then, in kde, Control Center -> Peripherals -> Storage Media -> Advanced (tab) there the message "HAL is not available on this system" was gone from the first checkbox description (Enable HAL Backend), meaning that kde knows some hal/dbus system is available.
now it works well. usb flash sticks mount correctly and show up automatically, my usb disk too, cdroms behave the same.

Cheers,
_________________
http://www.pjvenda.org

batistuta · Veteran Joined: 29 Jul 2005 Posts: 1384 Location: Aachen

Thanks Clansman, your approach worked for me as well

Cheers*B

andrewd18 · Posted: Sun Jan 07, 2007 5:53 am Post subject:

I have a similar issue... it's Gentoo Bug #149335. That might help (or at least explain) the PARALELL_STARTUP issues I saw earlier in the thread.
_________________
Keep Your Toolchain Stable! - emwrap.sh

There's no place like ::1

cklimt · n00b Joined: 10 Aug 2004 Posts: 39

I want to report another success story. I followed the anz's instructions and now KDE is working again with hal and is detecting all my removable devices. Thank you very much for the tip!!!

Maybe this problem has to do with dbus changing its API (or ABI, I'm not sure), between the 0.62 and the 1.0 versions.
_________________
"The aim of computing is insight not numbers"

zAfi · Posted: Mon Jan 22, 2007 1:55 pm Post subject:

Yesterday dbus-qt3-old and dbus-1.* went stable...now hal works on my system again and I don't need ivman anymore!

thx @ Clansman!
_________________
Gentoo 2008.0/desktop | Kernel: 2.6.27-tuxonice | Arch: amd64 | KDE 3.5.9 | WU Wien |
----------
Share your kernel information @ http://klive.cpushare.com/

Unlucky_Alf · Tux's lil' helper Joined: 02 Feb 2003 Posts: 92

I had to manually configure ~/.kde/share/config/mediamanagerrc to make it work bacause the options in control center were greyed out. Automounting works ok for my dvdrw. I can mount and unmount it using media:/ in konqueror.

My usb pendrive does automount but only root can unmouint it.
Case 1: If I try to unmount it manually I get "umount: /dev/sda is not in the fstab (and you are not root)".

Case 2: If I right-klick it's icon in media:/ and select "safely remove" it doesn't get unmounted but it's mtab entry is removed. If I try to umount /dev/sda i get "umount: /dev/sda is not mounted (according to mtab)".

zAfi · Posted: Tue Jan 23, 2007 2:19 pm Post subject:

This sounds like ivman running in the background to me. Or do you have fstab entries with wrong permissions set that doesn't allow user to unmount a device?

Did you reemerge kdebase-kioslaves?

If you have ivman running you can either disable it (rc-update del ivman and /etc/init.d/ivman stop) or start ivman as a regular user (and create a symlink to /usr/bin/ivman in the ~/.kde/Autostart folder). (More info at http://gentoo-wiki.com/HOWTO_ivman) But if I was you I'd disable ivman and would prefer a nativ kde solution....but that's up to you. :wink:

Unlucky_Alf · Tux's lil' helper Joined: 02 Feb 2003 Posts: 92

I did re-emerge kdebase/kioslaves, ivman is not installed and I don't have fstab entries for my dvdrw or usb pendrive.

Yukimura · Posted: Tue Jan 23, 2007 7:34 pm Post subject:

Have you tried unemerging and emerging hal? It somehow worked for me.

Unlucky_Alf · Tux's lil' helper Joined: 02 Feb 2003 Posts: 92

I have re-emerged hal, dbus and kdabase-kioslaves many times. Maybe I'll just wait and see if it starts/stops working someday :roll: