You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Thursday, July 21st 2005, 4:07pm

quick browser & umount

hi all,
i have a quickbrowser pointed to / in the panel. After i browse the /media/cdrom (where, of course, the /dev/cdrom is mounted), it results impossible to umount the device. from a shell, the error is (as you can expect)

Source code

1
2
3
4
sku@skuro:~$ umount /dev/cdrom
umount: /media/cdrom0: device is busy
umount: /media/cdrom0: device is busy
sku@skuro:~$


the only way i have to umount the cd is to kill kicker -> umount -> restart kicker

it's pretty annoying, there's a solution for this?

thank you (and please excuse me for my ugly english...)

sku
Utente Debian SID
Registered Linux User #372086

This post has Super Cow Powers

2

Thursday, July 21st 2005, 4:55pm

semi-resolved

as a workaround, i am using a button to launch `dcop kicker Panel restart` that seems to work.

i hope there's a more direct solution for the problem
Utente Debian SID
Registered Linux User #372086

This post has Super Cow Powers

anda_skoa

Professional

Posts: 1,273

Location: Graz, Austria

Occupation: Software Developer

  • Send private message

3

Friday, July 22nd 2005, 1:26pm

RE: semi-resolved

This happens because some process is monitoring a directory on the CDROM.

You could try uninstalling famd (I think the real problem is the dnotify implementation of the Linux kernel, but you can't remove that one :))

Cheers,
_
Qt/KDE Developer
Debian User

4

Friday, July 22nd 2005, 3:19pm

famd is not installed, i guess the problem resides elsewhere... thank you for the tip!!
Utente Debian SID
Registered Linux User #372086

This post has Super Cow Powers

julot

Beginner

Posts: 3

Location: Bogotá, Colombia

  • Send private message

5

Saturday, July 23rd 2005, 5:32pm

you should try the command fuser

fuser /dev/cdrom

it shows the pid of the processes using that file (device)

6

Sunday, July 24th 2005, 7:35am

i know which app lock the device: kicker

i was hoping that disabling its sort of cache that cause the lock was possible... :(
Utente Debian SID
Registered Linux User #372086

This post has Super Cow Powers