HAL issues with KDE 3.5.4

micmac · l33t Joined: 28 Nov 2003 Posts: 996

Hi all,

I've emerged KDE 3.5.4 and HAL is kinda not working right now. This is what I did:

- added hal to USE
- recompiled kioslaves with the new flag
- added hald and dbus to the default runlevel and rebootet

In KDE control center in the storage device settings I see "activate HAL", but it's greyed out, I can't activate it. Before I started using HAL it said that HAL wasn't supported. Now it seems it is but I can't use it.

Also, with 3.5.2 I was able to mount devices by right-clicking on the icons on my desktop and using "mount device". Now I get a message telling me that this function is only available through HAL. Looking at my desktop just this minute all my device icons are vanished.

I'm not complaining, because 3.5.4 isn't marked stable. But if someone has an idea what's happening I'd like to hear it.

Thanks
micmac

baobei · n00b Joined: 10 Jul 2006 Posts: 20 Location: Canada, Eh

Hi,

emerge -av --newuse --deep world

However, this might update too much for ya.

If it does, I think you will need to rebuild

kdebase-kioslaves
kdemultimedia-kioslaves

Or failing that...
kdebase-meta
kdemultimedia-meta

I always use the -av option for emerge so I can see exactly what will happen before it happens.

See how it goes.

baobei · n00b Joined: 10 Jul 2006 Posts: 20 Location: Canada, Eh

p.s. Sorry, i didnt see how many posts you have. I should pay more attention to that. I'm sure you knew what i suggested already. :oops:

kmare · Posted: Thu Aug 03, 2006 12:02 am Post subject:

I'm having the same problem (if i understood correctly what yours is). The only devices i see under the media:// slave, are the already mounted one. It'll find whatever device i plug, but not the unmounted partitions i have on my hard disks, so i can't mount them from there. It must be a kde 3.5.4 problem as before it was working just great. If anyone as a suggestion/solution, it'd be much appreciated...

thanx
_________________
Never argue with an idiot. They will only pull you down to their level, then beat you with experience.

micmac · l33t Joined: 28 Nov 2003 Posts: 996

@baobei: no worries

@kmare: Seems we're not alone, I just talked to some other folks in #kde on freenode and the one who uses KDE 3.5.4 has the same issue (greyed-out checkboxes). I found a workaround, though. Log out, enter console, edit ~/.kde3.5/share/config/mediamanagerrc to enable/disable HAL/CD polling support.

How about one of us writes a bug report?

Cheers
micmac

VoVaN · Posted: Thu Aug 03, 2006 10:51 am Post subject:

Vlad.Sharp · Posted: Thu Aug 03, 2006 10:52 am Post subject:

Same problem here. Just emerged --update kde-meta and no HAL support: "[ticked] Enable HAL Backend (No support for HAL on this system" in KDE Control Center -> Peripherals -> Storage Media

Here's the emerge --info (if anyone needs it):

kmare · Posted: Thu Aug 03, 2006 12:10 pm Post subject:

micmac · l33t Joined: 28 Nov 2003 Posts: 996

micmac · l33t Joined: 28 Nov 2003 Posts: 996

micmac · l33t Joined: 28 Nov 2003 Posts: 996

Bug report

roderick · Posted: Fri Aug 04, 2006 3:35 pm Post subject:

I have the same issue. All was working correctly up until I emerged 3.5.4

I have the following relevant packages:

sys-fs/udev-086
sys-apps/hal-0.5.5.1-r3
sys-apps/dbus-0.62
sys-apps/pmount-0.9.6

and have built all KDE 3.5.4 packages with USE="hal" set in make.conf.

Is there a possible issue with KDE 3.5.4 and the revs os packages I have? They worked fine in 3.5.3.

As well, if I insert my USB stick the icon appears just fine, but when I click to open (i.e. it attempts to mount device) I get the following popup error dialog:

"Method "Mount" with signature "ssas" on interface "org.freedesktop.Hal.Device.Volume" doesn't exist"

So, something is broken, possibly with the Hal backend in either not having a new enough Hal or in changes to it via KDE.
_________________
If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/

roderick · Posted: Fri Aug 04, 2006 6:54 pm Post subject:

Sorry to double post.

It would seem that my problem (popup error) was that I needed HAL >= 0.5.7 and not 0.5.5.1 which I was using.

KDE should have indicated HAL 0.5.7 was a requirement for KDE 3.5.4 to work (unless it truely is a bug).

I likely still have the grey box issue. I'll test shortly.
_________________
If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/

psk31 · Posted: Fri Aug 04, 2006 7:13 pm Post subject:

I just moved to 3.5.4 and now I'm getting a permissions error when I attempt to mount my fd0 using the floppy desktop icon. It worked perfectly under 3.5.3. Can still mount the floppy fine using the mount cmd or via KwikDisk. Also, fyi, I am running hal-0.5.7-r3, so not likely the problem.
??
psk31

roderick · Posted: Fri Aug 04, 2006 7:57 pm Post subject:

I have Hal 0.5.7-r1. Not sure it matters between revs in this case.

What exact error message are you getting? Are you using pmount at all? I use pmount and hal/kde supports it nicely. I use pmount 0.9.6 and you need to be a member of the group plugdev.

Oh, for everyone else, still have the grey boxes.. grr...
_________________
If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/

psk31 · Posted: Fri Aug 04, 2006 11:42 pm Post subject:

Yes, am using pmount-0.9.11
I have myself in the plugdev group as well (just checked).
Selecting the "floppy drive" desktop icon now brings up a konq window but also a konq error window indicating "Permissions denied". If I right click on the icon and attempt to "mount' I get same konq permissions error.
Now if I open /media, all thats shown is cdrecorder and sda1 (no floppy). As i said, I can mount the floppy manually as root (current login) so it seems to be something involving konqueror or kde in general.
Somethings changed between 3.5.3 and 3.5.4.

nabla² · Apprentice Joined: 17 May 2005 Posts: 280

psk31 · Posted: Sat Aug 05, 2006 12:50 am Post subject:

Further error info;
If I jump to an <ctrl+alt>f1 screen - I see the following error recorded;

kastorff · Posted: Sat Aug 05, 2006 1:30 am Post subject:

psk31 · Posted: Sat Aug 05, 2006 4:47 am Post subject:

Ok, I disabled fd0 in fstab and your right, I can now mount the floppy using the desktop icon. HOWEVER its still broke. Konqueror opens but does not display the contents of the floppy as in past versions. Rather, its showing, Location: media:/0 ..so you still have to go into the media folder and select floppy to open the disk. Also, for some strange reason hal keeps creating new floppy entries under /media each time I mount fd0. I'm up to floppy-5 and can't seem to get rid of them (even after umounting them manually).
I've noticed that the desktop floppy icon does not change to the mounted symbol, nor does it allow you to umount the drive once its been mounted. So not sure whether to leave fd0 out of the fstab at this point if its going to be fixed (bug?) or run with it as is.
Hopefully this will be addressed soon.

edit: On second thought this is no good. Went back to the fd0 entry in fstab. Otherwise I had no other way of mounting a floppy other than hiting the desktop icon.

ATS · n00b Joined: 24 Apr 2004 Posts: 46

Did anyone get past the "Permission Denied" message?
I'm battling that one right now. Odd thing is that my USB-stick does work properly.

Logge · Posted: Sun Aug 06, 2006 8:01 pm Post subject:

I did get passed the "Permission denied" message by commenting out the line in fstab corresponding to the USB-storage disc that wasn't mounting as user. Just like psk31 did. The problem by doing that is that it could make it troublesome to mount it from ie the console because there is no line for it in /etc/fstab.

I think there will be a fix for this pretty soon... Apparently there was a problem like this when Gnome 2.14 was released if i'm not mistaken.

//Logge
_________________
I never stop to amaze about the advanced features of the human body's simplicity

kmare · Posted: Wed Aug 09, 2006 6:08 pm Post subject:

*bump*
hmm anyone found a fix/patch yet?
_________________
Never argue with an idiot. They will only pull you down to their level, then beat you with experience.

z4Rilla · Apprentice Joined: 22 Dec 2003 Posts: 291 Location: EU

hi,
I got the following to work:
1. When an usb stick is plugged in or disc is inserted into the drive an appropiate icon appears in media:/ and on desktop
2. Devices can still be mounted via mount (entries in /etc/fstab can be used)
3. Clicking on icons in media:/ is mounting the device

And heres what I did:

reemerging kdebase-kioslaves-3.5.4 with hal USE flag enabled
emerging hal and dbus
adding
Code:

<allow send_destination="org.freedesktop.Hal"/>
<allow receive_sender="org.freedesktop.Hal"/>

to the policy part of /etc/dbus-1/etc/dbus-1/system.conf
starting dbus and hal
Code:

rc-update -a dbus default
rc-update -a hald default
rc
adding user to group plugdev
Code:

gpasswd -a <user> plugdev
inserting/plugin mountable device should now produce an icon in media (see 1.)
if 3. is not yet available do the following for each device:
- take a look at what device kde tries to mount (which media:/X is opened by clicking on the icon in media:/)
  this is especially important if you have used symlinks like /dev/dvd before. These are ignored.
- Edit the appropiate fstab entry so it looks like this:
  Code:
  
  /dev/X /media/X auto noauto,users 0 0
  (further opts may be added)
- create the mount point in /media:
  Code:
  
  mkdir /media/X
  chgrp plugdev /media/X
  chmod g+rwx /media/X

versions:

knizek · Posted: Thu Sep 07, 2006 9:54 pm Post subject:

Two options worked for me to work-around the issue:

a) have an fstab entry with "users" option to allow any user to mount and umount the device. However, this requires that you populate fstab with any possible dev entry (sda, sda1, sda2, sdb, sdb1, etc. depending on types of usb accessory) and also create the respective mount points. Then, mounting works from console or via KDE pop-up window after pluging-in the device.

b) I prefer ivman. It is possible to run /etc/init.d/ivman + additional ivman started once a user logs in (e.g. ~/.kde/Autostart/ivman). The system wide /etc/init.d/ivman can be setup to wait for the user's ivman to mount the device. Once the device is mounted by user's ivman, you can confirm the pop-up window of KDE. Un mounting via KDE works fine, since the device was mounted by the same user. The caveat of this approach is that only one user should run ivman - if more of them do at the same time, it is not clear, which will be the successfull one who actually mounts the device - that is usually not an issue for a desktop computer. I have setup ivman to use pmount and /usr/bin/pmount, pmount-hal, pumount have root:plugdev owners and permission execute as user (suid).

Ivman has another advantage - it creates mount point directory using the name of the device (e.g. /media/camera, media/my_flash, etc.), while kde uses the /dev entry (e.g. media/sda1).
_________________
--
Milan Knizek
knizek (@) volny (.) cz
http://milan-knizek.net