Can't reproduce this, I use dbus-0.35.2 though. Would it be possible for you
to downgrade to 0.35.2 and see if you still experience this? That might be
dbus signals, but that could be something specific to your plateform...

I tried it with dbus-0.35.2 (also dbus-0.50) and got the same result. The devices are detected, shown in the "Storage Media"-applet and when I click on one of them they also get mounted. The icons in the "Storage Media"-applet are never changed to the "mounted" ones and the file manager shows e.g. "media:/sdb1" forever but no content. 
How can I get more information from the system?

When you upgrade or downgrade your dbus on your Gentoo, are the kdelibs rebuilt?

After downgrading I have recompiled kdelibs and kdebase - without any luck.

I'm also on Gentoo. On my system mounting usb sticks works fine. But I had to emerge pmount. In gentoo's hal-0.5 ebuilds fstab-sync is no longer built, so kde can't simply run mount since fstab info is missing. With pmount however devices can be mounted without a configuration line in fstab. KDE knows about pmount, but of course it needs to be installed...

Then that's a Gentoo specific problem, the missed a depend for pmount somewhere.

pmount is installed, I've just forgotten to write it in the orginal bug report.
As I wrote in the bug report the devices get mounted (the pmount ones and the fstab ones) but the content is never shown through the media io-slave.
I have also tried to recompile my whole system - without success.

Hmm, well, just for reference:
emerge -pv pmount hal dbus kdebase udev
[ebuild   R   ] sys-apps/pmount-0.9.3-r3  +crypt 0 kB
[ebuild   R   ] sys-apps/hal-0.5.4  -debug -doc -pam_console -pcmcia 0 kB
[ebuild   R   ] sys-apps/dbus-0.36.2  +X -debug -doc +gtk -mono -python +qt 
+xml2 0 kB
[ebuild   R   ] kde-base/kdebase-3.5_beta1  +arts +cups +debug +hal +ieee1394 
+java -kdeenablefinal -ldap +lm_sensors -logitech-mouse -openexr +opengl +pam 
-samba +ssl -xinerama +zeroconf 0 kB
[ebuild     U ] sys-fs/udev-068-r1 [068] (-selinux) -static 0 kB

Did you compile kdebase and kdelibs with USE="debug"? Perhaps running 
konqueror from a konsole provides some useful info.

I get the follwing output if I run konqueror from a konsole (when I try to browse my root disk through the media io-slave)


konqueror: emit m_extension->openURLRequest( media:/sda2,)
konqueror: KonqMainWindow::slotOpenURLRequest frameName=
konqueror: KonqMainWindow::openURL (from slotOpenURLRequest) url=media:/sda2
konqueror: KonqMainWindow::openURL : url = 'media:/sda2'  serviceType=' req=[]' view=0x82a4828
konqueror: trying openView for media:/sda2 (serviceType )
konqueror: setLocationBarURL : url = media:/sda2
konqueror: KonqMainWindow::setLocationBarURL: url = media:/sda2
konqueror: Creating new konqrun for media:/sda2 req.typedURL=
konqueror: KonqMainWindow::openView media/hdd_unmounted media:/sda2 0x82a4828 req:[forceAutoEmbed]
konqueror: changeViewMode: serviceType is media/hdd_unmounted serviceName is  current service name is konq_iconview
konqueror: Switching view modes...
konqueror: Trying to create view for "media/hdd_unmounted"
konqueror: konq_iconview : X-KDE-BrowserView-AllowAsDefault is valid : true
konqueror: KonqView::changeViewMode. Reusing service. Service type set to media/hdd_unmounted
konqueror: KonqView::openURL url=media:/sda2 locationBarURL=media:/sda2
konqueror: KonqMainWindow::setLocationBarURL: url = media:/sda2
konqueror: KonqMainWindow::setCaption(media:/sda2)
libkonq: ## addToHistory: media:/sda2 Typed URL: media:/sda2, Title:
konqueror: KonqMainWindow::openView ok=true bOthersFollowed=false returning true
konqueror: KonqMainWindow::slotRunFinished()
konqueror: KonqView::slotCanceled

I'd need kdeinit output too. Just launch a konsole, then launch kdeinit in it, and finally konqueror in the same konsole. The output will be more informative for me.

Ok, here is the output. If you need the whole output from kdeinit and konqueror please let me know.

konqueror: emit m_extension->openURLRequest( media:/sda2,)
konqueror: KonqMainWindow::slotOpenURLRequest frameName=
konqueror: KonqMainWindow::openURL (from slotOpenURLRequest) url=media:/sda2
konqueror: KonqMainWindow::openURL : url = 'media:/sda2'  serviceType=' req=[]' view=0x8267b80
konqueror: trying openView for media:/sda2 (serviceType )
konqueror: setLocationBarURL : url = media:/sda2
konqueror: KonqMainWindow::setLocationBarURL: url = media:/sda2
konqueror: Creating new konqrun for media:/sda2 req.typedURL=
media kioslave: MediaProtocol::stat: media:/sda2
media kioslave: MediaImpl::statMedium: sda2
media kioslave: MediaProtocol::createMedium
media kioslave: url = media:/sda2, mime = media/hdd_unmounted
konqueror: KonqMainWindow::openView media/hdd_unmounted media:/sda2 0x8267b80 req:[forceAutoEmbed]
konqueror: changeViewMode: serviceType is media/hdd_unmounted serviceName is  current service name is konq_iconview
konqueror: Switching view modes...
konqueror: Trying to create view for "media/hdd_unmounted"
konqueror: konq_iconview : X-KDE-BrowserView-AllowAsDefault is valid : true
konqueror: KonqView::changeViewMode. Reusing service. Service type set to media/hdd_unmounted
konqueror: KonqView::openURL url=media:/sda2 locationBarURL=media:/sda2
konqueror: KonqMainWindow::setLocationBarURL: url = media:/sda2
konqueror: KonqMainWindow::setCaption(media:/sda2)
libkonq: ## addToHistory: media:/sda2 Typed URL: media:/sda2, Title:
konqueror: KonqMainWindow::openView ok=true bOthersFollowed=false returning true
konqueror: KonqMainWindow::slotRunFinished()
media kioslave: MediaProtocol::listDir: media:/sda2
mount: Laut mtab ist /dev/sda2 schon auf / eingehängt
mount ist fehlgeschlagen
media kioslave: MediaImpl::slotMountResult
konqueror: KonqView::slotCanceled

Same here. Using the same setup, albeit with gcc 4.0.2. I've kept up-to-date with kdelibs and kdebase svn, but the problem is still there: the device gets mounted with pmount, but konqueror stays on media:/sda1 (for example), the logo spinning like if it were loading some web page, and it does not show the actual content of the device. If I hit the stop button and refresh the page I get an error message saying that the mounting failed because the device is already mounted.

pmount works ok from the command line. No strange messages in the logs from hal or dbus. It seems like a KDE specific problem. I upgraded Hal from 0.4.x to 0.5.x when I updated kde to 3.5_beta1, could it be that there are some stale config files from hal 0.4.x that are giving problems?

I'm installing 3.5_beta2 right now, but I'm almost certain the problem will still be there :(

I still can't reproduce this one... It looks like you never get the signal from HAL indicating that the medium is mounted (hence why konqui is waiting endlessly). Are you sure you've built against the right HAL and DBUS versions?

Kevin:

Yes, I'm pretty sure about the correct hal and dbus versions. I've just checked headers and libraries on my system, and it does not seem there are relics from previous installations.

Just a long shot, but could this be related to the qt version and the qt-dbus bindings? I'm using qt 3.3.5, FWIW.

Could be an issue in the qt-dbus binding indeed... That's clearly a signal that disappear somewhere in the stack.

I have installed gnome 2.12 with g-v-m (1.5.3 ?) and got nearly the same error - so this seems to be a dbus/hal problem and not a kde specific problem. 
However, I pretty sure that dbus/hal is installed and configured properly. 

Kevin:

Are some paths for dbus hardcoded into the media:/ ioslave? I'm asking this because Gentoo recently changed the dbus socket location from

/var/run/dbus/system_bus_socket

to

/var/lib/dbus/system_bus_socket

This broke some apps (for example the powersave daemon from SuSE, which I tried to install last week).

No it isn't, we don't use the gory details of DBUS directly, we use an API on top. So it might be an issue in the DBUS qt binding.

This bug looks more and more as an INVALID to me... really tied to packaging issues, maybe with a bug in the HAL or DBUS bindings we use.

*** Bug 114733 has been marked as a duplicate of this bug. ***

Closing this bug is fine by me, as I think this is a hal/dbus/whatevery bug and not a kde specific one.
The hal-device-manager shows the property of all my mounted partitions/devices as "volume.is_mounted = false" - independent from having a fstab entry or being mounted by pmount.

Ok, thanks you a lot for this confirmation. I was more and more sure it was a HAL/DBUS/Packaging related issue. It's an INVALID then.