Version: (using KDE KDE 3.5.4)
Installed from: Slackware Packages
Can't mount devices using konqueror storage media more than once... if I click on the cdrom icon in the konqueror storage media, it mounts the device and open it, then I go back and right click on the cdrom icon and unmount it, then I click on it again and it keeps loading forever... however I do mounts the device, cause I can see it from console and file manager, once cancelled it doesn't show it as mounted, so there's no way to unmount it but command line...
I'm using slackware 11, not sure if it's a kde only bug or slackware too...
google search returned:
*** Bug 136301 has been marked as a duplicate of this bug. ***
Confirmed for kde 3.5.5 as well (system without hal, kernel 184.108.40.206 or 220.127.116.11)
Errata: I'm not 100% sure of comment #2, sorry
I can confirm it for kde 3.5.5
This also happens on with KDE 3.5.5 on Fedora Core 6.
I get similar behaviour to that described above with the CD drive but there's a more serious problem with USB connected devices.
I have an external hard drive connected via USB. I can mount and unmount the drive once through the USB icon on my desktop. If I try to mount a second time, my system hangs - i.e. the mouse and keyboard are frozen. The only way to recover is to hit the reset button (it's possible that the system would eventually recover but I haven't had the patience to wait it out for more than a minute or so). The drive can be remounted if it's first disconnected and reconnected but that, obviously, should not be required.
here is a snip from the slackware current changelog before version 11.0 was released.
kde/kdebase-3.5.4-i486-7.tgz: Patched to fix media:/ URLs in Konqueror without
I am running slackware 11.0 and have the same problem. mount a cd or dvd view it's contents>unmount>eject>reload>error is now noticed.the media is being mounted according to /etc/mtab and the contents can be viewed in /mnt/cdrom, However the system:/media cdrom icon says it is a unmounted cdrom,click on it and nothing.I thought this was a KDE bug until I noticed the above snip from the slackware current changelog just prior to version 11 release. Perhaps whatever they patched broke
something else. The confusing part is there is a use HAL or not checkbox there why patch (hack) around it or better yet just include HAL and HAL support in
*** Bug 137556 has been marked as a duplicate of this bug. ***
*** This bug has been confirmed by popular vote. ***
The patch that "they" used to fix the media:/ URLs in Slackware was Stephen Kulow's svn commit (backported for 3.5.4) - see http://bugs.kde.org/show_bug.cgi?id=132281 for more information.
As for adding HAL, well, future versions of HAL will require PolicyKit, and PolicyKit requires PAM, and Slackware's not likely to get PAM any time soon. In any event, it's not as simple as it sounds.
I can confirm that this is also present in 3.5.5.
is there any workarounds for this? HAL and slackware are not compatible, and as far as it looks they will not be for a long time... question is, is HAL a requirement in kde? it will be cool to have like a flag in configure script to disable hal support and fall back to old behaviour? not sure if that will be as simple as it sounds (i have no idea about kde internals)
is HAL present in other os? (*bsd, (open)solaris, et cetera?)
If you read the bug report in my previous comment, the question about HAL is already answered. To sum up, no, it's not required. This bug isn't about HAL support at all - I only commented about it above because someone else seemed to have it confused...
I can confirm this bug.
All kio media managers from previous KDE versions until 3.5.3 did worked properly using /etc/fstab entries when kdebase was built without HAL support.
Even in KDE 3.5.5 there is officialy only optional requirement for HAL so it should work without it too.
To clarify the scope of this bug:
It was not present in 3.5.3 (it worked properly), but 3.5.4 broke it - we initially thought it was due to http://bugs.kde.org/show_bug.cgi?id=132281, but even after applying the backported patch, this bug still exists.
Is there anything I can do to help get a better diagnosis of exactly what is causing this? I'd really like to get a patch for this...
*** Bug 144208 has been marked as a duplicate of this bug. ***
When, if ever, is anyoone going to look at this?
Can I help?
Someone talk to me.
For those Slackware users still following this bug, it won't be an issue in Slackware 12.0 (which is just around the corner) - it will have HAL.
For those of you still on 11.0, it seems that you'll have to learn to live with this bug :/
kio media is gone in KDE4.