[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#252571: marked as done (konqueror doesn't end process, so CD won't unmount)

Your message dated Sun, 14 Mar 2010 18:12:27 -0400
with message-id <9f694b821003141512u657a7b9ejbae59f8e55b33fe9@mail.gmail.com>
and subject line Closing bug # 252571
has caused the Debian Bug report #252571,
regarding konqueror doesn't end process, so CD won't unmount
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

252571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252571
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: konqueror
Version: 4:3.2.2-1

I think konqueror is locking up my CD drive because it doesn't end a process properly when it should. I get this when I do the following:

1) I have a link to my cd drive on my kde desktop
2) I have a CD in the drive
3) right-click on the desktop link, choose "open" (this will mount /cdrom and then open konqeror showing the contents of the CD)
4)  close that konqeror session
5) try to unmount /cdrom (I use the right-click -> unmount on the desktop link again)
6) it won't unmount because the device is busy.
7) it won't unmount forever until you reboot the computer

What took me awhile to figure is that if I open kde system guard there's still a konqueror process running even though I closed that konq window that was looking at the cd contents. If I kill that process I can then unmount the CD. presumably that process is locking the drive. I don't think that process should still be there - it should go when you close that window.



--- End Message ---
--- Begin Message ---
According to upstream, this has been fixed since version 4.3.1.
See https://bugs.kde.org/78322
Closing this report

--- End Message ---

Reply to: