Konqueror/KDE: "media:/" displays UUIDs instead of foldernames

Thanks for submitting this report.

It looks like that this occurred on a pre-release of gutsy. Can you confirm this still occurring on the final gutsy release (using KDE 3.5.8)?

Thanks

I'd love to, but I'm not sure how to reproduce that error - or which logfiles to check for details in case that I run across such a thing again (Sorry, I'm coming from shell-only servers. : ) ).
Any hints?

There's one computer here that's currently running Feisty, so when I upgrade that one to Gutsy, I can post my results (and I'm also planning to setup another machine on a fresh Gutsy, where I can check).

I'm running the regular release of Gutsy with all current updates applied and am experiencing this problem as well.

If there's any information you need, please ask...

Which output do you get when you open these locations:
1) media:/
2) /media

I remember that "media:/" used to work - now (on Feisty) it displays nothing at all - maybe that's related, but I would not know which logfiles to check.

media:/
CDROM (hdc)
Hard Disk (UUID=0f6a0970-3b9b-48db-a132-1e88ec8c15ff)
Hard Disk (UUID=5c026299-b815-45e5-b2b8-7d89c8d8a188)
Hard Disk (UUID=66778b94-a35e-4240-8016-0b5bfad6305c)
Removable Device (UUID=4748-A472)

/media (Some of these are obviously mine)
backup
cdrom(symlink)
cdrom0
data
files
usb
windows

Not sure you'll get any help from that. It sees the devices, but trying to access them under media:/ fails. The harddrive partitions, CD, and flash drive.

Can you make sure that hal is installed and running?

This was quite a while ago... Let's see if we can't close this one soon.

I'm guessing that I had to run /usr/lib/hal/hald-generate-fdi-cache to make the issue go away. I've had to do that various times on Gutsy boxes before Hal worked properly.

I've got a fresh version of Gutsy installing in VMWare right now. I'll let it update completely and reboot to see if the hal issue has been fixed. I'll try to post a reply as soon as possible (updating can take a while).

I had KUbuntu 7.10 and I upgraded to 8.10 using Adept.
Devices in /media (hdd) were appearing with uuid symbols. Accessing them reported "Feature only available with HAL."
I ran /usr/lib/hal/hald-generate-fdi-cache and now devices in /media behave normally.

Possibly related:
After upgrade I could access the mounted CD/DVD just fine (even before running hald-generate-fdi-cache), but ejecting or unmounting the CDrom kept reporting: "kio_media_mounthelper: <<Feature only available with HAL.>>"

This was not solved by running hald-generate-fdi-cache. The problem is still standing.

I can reproduce this bug 100%. Currently running Hardy-updates, Kubuntu latest updates.
After login, I get exactly the same result as Jared for the /media and media:/.
Clicking the CDROM/DVD icon in dolphin under media:/ gives "Feature only available with HAL"
If I then plug in a USB stick, nothing shows up. dmesg shows the USB stick is found

HAL seems to be aware that the USB device has been attached to the system

sudo grep -i hal /var/log/syslog
Mar 4 11:22:24 [EMAIL PROTECTED] NetworkManager: <debug> [1236126144.863420] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_781_5204_200445277202E840F11E').
Mar 4 11:22:25 [EMAIL PROTECTED] NetworkManager: <debug> [1236126145.003961] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_781_5204_200445277202E840F11E_if0').
Mar 4 11:22:30 [EMAIL PROTECTED] NetworkManager: <debug> [1236126150.086713] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_781_5204_200445277202E840F11E_if0_scsi_host').
Mar 4 11:22:30 [EMAIL PROTECTED] NetworkManager: <debug> [1236126150.091106] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_781_5204_200445277202E840F11E_if0_scsi_host_scsi_device_lun0').
Mar 4 11:22:30 [EMAIL PROTECTED] NetworkManager: <debug> [1236126150.104599] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_781_5204_200445277202E840F11E_if0_scsi_host_scsi_device_lun0_scsi_generic').
Mar 4 11:22:30 [EMAIL PROTECTED] NetworkManager: <debug> [1236126150.180943] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/storage_serial_SanDisk_Cruzer_Crossfire_200445277202E840F11E_0_0').
Mar 4 11:22:30 [EMAIL PROTECTED] NetworkManager: <debug> [1236126150.215564] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_uuid_8A8A_FBDC').

Now If I run:
sudo /usr/lib/hal/hald-generate-fdi-cache
(there is no change to the size or md5sum of the /var/cache/hald/fdi-cache after this is run)
and then log out and log back in I can then mount the CDROM/DVD and the USB stick shows up and can be mounted as per normal.

I would like to help solve this bug, but I need some suggestions to give more diagnostic information.

--
Babstar

Hi,

I got the same bug with Kubuntu8.04 x86_64 with all available ubuntu patches applied. This occured a few weeks ago and is still present.

But here is a thing I noted:

Boot my PC to Kubuntu, login with KDM, start konqueror goto 'media:/' and all devices are listed with UUIDs, a double click results in HAL error message mentioned above.
Logoff (close my KDE3.5 session) and login again, open konqueror goto 'media:/' and all devices are listed with labels and can be opened.

I hope, this can give you a clue.
If I shall post any logs, then please contact me.

Hi again,

I must be more precize ...

My PC booted to Kubuntu and I typed in my password in KDM login screen as soon as it was possible, start konqueror, goto 'media:/' and UUIDs.

Then a fresh reboot to Kubuntu, I went into my kitchen to fetch a coffee, Kubuntu's login screen had been there at least for 1 minute in idle time, then login, start konqueror, goto 'media:/' and labels.

So I suspect that something with ?HAL? isn't quite ready if KDM had just started.
It seems to me to be just a timing problem.

Is there a way to keep KDM waiting for HAL to be ready?

Cheers,
Jens

Weird, but it really seems to be related to a racing condition!
Thanks to a post in kubuntuforums (http://kubuntuforums.net/forums/index.php?topic=3095353.msg135670#msg135670), I've tried delaying the startup of kdm to be waaay after hal:

[quote]
cd /etc/rc2.d
sudo rm S13kdm
sudo ln -s ../init.d/kdm S97kdm

# optional: check if the link still points to kdm:
ls -l S97kdm
[quote]

Seems weird, since the order of hal and kdm was probably always like that on my system, and I couldn't think of anything I've changed that could have caused this problem. It appeared out of nowhere.

The media:/ kioslave is no longer present in any supported version of Kubuntu. Since the bug is no longer observable and hal is depreciated anyways, I highly doubt that this will be fixed.