You are not logged in.
Hello,
I have this problem with the new kde 3.4.2 and the 3.4.1-? that was out before it. It was working before that.
The problem is that files/directories are not shown for CDs in the Storage media section of konqueror and once mounted, the device stays busy until konqueror is closed.
In more detail: If I open konqueror in file management mode and go to the services tab -> Storage media, I can see the cd-rom disk. If I click on the icon, it mounts the drive (verified by doing an ls of /media/cdrom before and after) but no files are shown in the konqueror window. I can go to the root folder tab and navigate to /media/cdrom and the files are there and can be copied to disk, etc.
In konqueror (back in services->Storage media) right clicking the icon to eject fails with an error box. If I try to unmount the drive on the command line, I get a 'device is busy' error until I exit konqueror, then it works.
I tried running konqueror from the command line, but it does not show any relevant messages.
I use udev, dbus, hal. No special udev rules or symlinks, just the arch default.
ls -l /dev/hdc
brw-rw---- 1 root optical 22, 0 2005-07-22 04:31 /dev/hdc
...and my user is in the optical group (obvious since I am able to mount/unmount by hand).
Any ideas?
Offline
It works fine here... still using 3.4.1 plus udev, dbus, hal, AND ivman. Nothing special on udev rules as well.
All removable media can be mounted without issues (spare a removable NTFS formatted HD which is recognized as reiserFS and needs special rules to be mounted properly!), and the unmountable audioCD media can be accessed via "audioCD:/".
Do you have any user-defined entries for your optical drives in your /etc/fstab ?
Microshaft delenda est
Offline
Thanks, I will try a new user.
Offline
on my system it works fine with 3.4.2
greetings
tpowa
Offline
FYI just updated to 3.4.2 from testing and had loads of problems (had to uninstall/rebuild krusader, knemo, kio_burn and every other KDE related application) but "audiocd:/" worked fine once konqueror was able to launch (was crashing before removing kio_burn).
Microshaft delenda est
Offline
because a big rebuild is needed for a lot of apps, you need to rebuild all kde/qt apps against 3.4.2 or qt-11
that's the reason i didn't announce on news page
greetings
tpowa
Offline
A major annoyance is that after the upgrade the stock K3B cannot initialize vcdimager anymore...
Maybe more to come, but that was to be expected.
Microshaft delenda est
Offline
k3b from testing?
don't know why
Offline
k3b from testing?
don't know why
Yes, that one... I might try building a subversion snapshot later.
Microshaft delenda est
Offline
vcdxbuild: error while loading shared libraries: libcdio.so.5: cannot open shared object file: No such file or directory
that's the reason for failing, nothing qt related
Offline
Oh, thanks for it.
In the meantime I have built a current SVN snapshot, which built fine, but (of course) didn't take care of the issue.
Any ideas on how to bypass this annoyance? (a symlink, probably?).
PS: ln -s libcdio.so.5 libcdio.so.6.0.0 does not resolve the issue.
Microshaft delenda est
Offline
rebuild vcdimager then it should work again
Offline
OK, I will...
PS: dp's vcdimager PKGBUILD depends on libcdio, and vice versa... bummer.
I compiled libcdio from source without a PKGBUILD succesfully, but then vcdimager fails to spot any libcdio installation at the configure phase, and aborts.
Any ideas?
Microshaft delenda est
Offline
Found a way out...
First I built the newer version of libcdio (just changed the version no. from the PKGBUILD, and removed the vcdimager dependency). Then I built vcdimager (also a newer version) and now K3B sees it.
The reason of the mutual dependency was a cdio patch for vcdimager, which doesn't seeem to be needed anymore.
Of course I still don't know if vcdimager is functional if built that way, but I will soon find out...
Thanks for the help, tpowa.
Microshaft delenda est
Offline
damir updated vcdimager, should be solved that issue
Offline
I see he built 7.22 again... Is there something wrong with 7.23?
Microshaft delenda est
Offline
umm..the original thread was about ivman right..well im facing the same problem as scarecrow...blank konqueror windows in media:/... help please..
im getting tired of ivman breaking with every release of kde/hal/dbus..i tried gnome-volume-manager(cause someone said it will work in kde) but got the same results..are there any other alternatives?thanks for your help..
Offline
I have just tried kdebase 3.4.2-3 from testing and I can report that the konqueror->services->storage media display problem has been solved for me.
Thank you maintainer `none', whomever you are.
Offline
Actually this was a problem in hal, so it wasn't even a bug in KDE.
The problem with hal was that it had a broken patch applied by accident, which broke the mount state for hal devices. Whenever you click something in media:/, it shows up as blank, as hal and KDE don't know the mountpoint then.
Offline
-3 was only to fix a konqui bug that arises on packager ml.
greetings
from packager "none"
Offline
I didn't have the storage problem (anymore...), but kdebase 3.4.2-3 solved other problems for me (being unable to enter some directories from Konqueror, and dog slow audioCD rips via the VFS).
Well done, nonexistent packager!
The only quirk ATM is that kscd does not "see" any audio engine anymore (BTW this also applied for the previous kdebase version), it does read the audioCD and starts playing back, but remains silent...
Since kaffeine, or Amarok works (the latter only with the Arts engine- gstreamer and xine seem unable to use the KDE VFS) this isn't much of a problem, just wondering why kscd can't spot artsd...
Microshaft delenda est
Offline
after a brief hiatus, my long lost friend the "konqueror/hal storage media bug is back"..rejoice!!
blank window on clicking the DVD ROM link..disc gets mounted in media, but does not appear thru the media:/ kioslave. exactly as before.
Offline
Ok after reading bugs.archlinux.org, I changed the kernel back to regular PREEMPT and things seem fine now. tpowa, can you please tell us when this bug is fixed with the "voluntary kernel preemption" option in the kernel? Thanks..
This still doesn't explain why only one of my drives appears in media:/ (only hdc, not hdd)
P.S - The drives dont eject on pressing the eject button..I have to do a eject /dev/hdc to get it to eject, or Rightclick-> Eject in media:/
Offline
sorry i don't know when this is fixed, it was hard to find out that this optin is causing trouble, and it's more a hal than a kde bug.
Offline
who is the hal maintainer? none?
Offline