problems unmounting folder with spaces

[Manuel López-Ibáñez]

Binary package hint: kdebase

I have an usb drive that becomes mounted into /media/SGTL MSCN
When clicking on "Safely Remove" I always get an error message from kio_media_mounthelper

Unfortunately, the device system:/media/sdb1 (/dev/sdb1) named 'SGTL MSCN' and currently mounted at /media/SGTL MSCN could not be unmounted. Unmounting failed due to the following error:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Moreover, programs still using the device have been detected. They are listed below. You have to close them or change their working directory before attempting to unmount the device again.
                     USER PID ACCESS COMMAND
/media/SGTL MSCN: root 1 ....m init
                     root 2563 ....m udevd
                     root 4248 ....m getty
                     root 4249 ....m getty
                     root 4251 ....m getty
                     root 4253 ....m getty
                     root 4255 ....m getty
                     root 4256 ....m getty
                     root 4514 ....m acpid
                     root 4633 ....m syslogd
...

If I do "sudo lsof | grep media", there is no process holding back the directory. Eventually, the drive gets unmounted and the icon disappears. Weird.

[Manuel López-Ibáñez (manuellopezibanez)]

Perhaps the warning is strange is because of the folder with spaces, not sure about that. But the reason why the message appears seems to be that the device is still writing (and it takes a while). When it finishes, it umounts without further interaction.

[Yuriy Kozlov (yuriy-kozlov)]

There's been some improvement in showing progress for syncing and umounting removable devices. Can you see if you still have this problem in Kubuntu Hardy?

[Manuel López-Ibáñez (manuellopezibanez)]

I confirmed that this is not due to spaces, but because of a busy device. I won't be able to test Hardy soon, so I will close this bug report. If I find the issue in Hardy again, I will open a new report with up to date info.