A bug somewhere, but I can't figure where (CD copying)
Hi everyone, I'm confused by the following problem: If I 1) mount a CD-ROM by clicking on the device icon on the desktop. 2) Copy the data from that CD to hard disk with cp from the command line (in a konsole that was NOT started from the konqueror window with the CD ROM). 3) The CD is dodgy and there are i/o errors in the copy. 4) Close the konqueror window that is viewing the CD (via control-Q or the menu). It is then not possible to unmount or eject the CD-ROM. fuser -mav /cdrom1 tells me that a kdeinit process still has the cd or something on it open. Killing that kdeinit process kills most of my konqueror filemanager windows showing that it is konqueror and not konsole that is holding the cd device. If there are no i/o errors there is no problem. I'm using KDE 3.3.2 from Sarge on x86. Does anyone have any clues as to which component is likely to be at fault? James -- ++---+-+ | James Tappin | School of Physics Astronomy | O__| | [EMAIL PROTECTED] | University of Birmingham | -- \/` | | Ph: 0121-414-6462. Fax: 0121-414-3722 | | ++-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A bug somewhere, but I can't figure where (CD copying)
On Wed, 6 Apr 2005, James Tappin wrote: Hi everyone, I'm confused by the following problem: If I 1) mount a CD-ROM by clicking on the device icon on the desktop. 2) Copy the data from that CD to hard disk with cp from the command line (in a konsole that was NOT started from the konqueror window with the CD ROM). 3) The CD is dodgy and there are i/o errors in the copy. 4) Close the konqueror window that is viewing the CD (via control-Q or the menu). It is then not possible to unmount or eject the CD-ROM. fuser -mav /cdrom1 tells me that a kdeinit process still has the cd or something on it open. Killing that kdeinit process kills most of my konqueror filemanager windows showing that it is konqueror and not konsole that is holding the cd device. If there are no i/o errors there is no problem. I'm using KDE 3.3.2 from Sarge on x86. Does anyone have any clues as to which component is likely to be at fault? Anytime this happens to me (using Sid's KDE)... # lsof /cdrom ...says that famd is holding onto the mount point... # /etc/init.d/fam stop ...releases it. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A bug somewhere, but I can't figure where (CD copying)
On Wednesday 06 April 2005 16:28, Bruce Sass wrote: On Wed, 6 Apr 2005, James Tappin wrote: I'm using KDE 3.3.2 from Sarge on x86. Does anyone have any clues as to which component is likely to be at fault? Anytime this happens to me (using Sid's KDE)... # lsof /cdrom ...says that famd is holding onto the mount point... # /etc/init.d/fam stop ...releases it. I had this problem too! Removing fam solved it. Btw, is KDE using fam actually? If so, what does it? But I think the problem, James reported, has nothing to do with fam. I have the same effect without fam installed on Sarge! -- Georg Prager EM: georg.prager [at] wing.at PGP: B83D58DA pgpU6uMedTyIb.pgp Description: PGP signature
Re: A bug somewhere, but I can't figure where (CD copying)
Dnia roda, 6 kwietnia 2005 18:12, Georg Prager napisa: On Wednesday 06 April 2005 16:28, Bruce Sass wrote: On Wed, 6 Apr 2005, James Tappin wrote: I'm using KDE 3.3.2 from Sarge on x86. Does anyone have any clues as to which component is likely to be at fault? Anytime this happens to me (using Sid's KDE)... # lsof /cdrom ...says that famd is holding onto the mount point... # /etc/init.d/fam stop ...releases it. I had this problem too! Removing fam solved it. Btw, is KDE using fam actually? If so, what does it? It uses it if fam is running. If not, it just uses dnotify directly. But I think the problem, James reported, has nothing to do with fam. I have the same effect without fam installed on Sarge!
