CD-ROM eject

On Sun, Jun 26, 2005 at 08:30:15PM +0300, Andrey Andreev wrote:

> Are you trying to eject while Konqueror has the devices tree open?
> That's what I sometimes do and it fails miserably. Try closing all
> Konquerors and eject then.

And probably (as root)
/etc/init.d/famd stop
if you're using any sort of automounting.

Nick


--
To UNSUBSCRIBE, email to debian-kde-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org

Nick Leverton wrote:
> On Sun, Jun 26, 2005 at 08:30:15PM +0300, Andrey Andreev wrote:
>>Are you trying to eject while Konqueror has the devices tree open?
>>That's what I sometimes do and it fails miserably. Try closing all
>>Konquerors and eject then.
> And probably (as root)
> /etc/init.d/famd stop
> if you're using any sort of automounting.

Is it not
/etc/initd/fam stop
?

Regards,

Andro


--
To UNSUBSCRIBE, email to debian-kde-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org

> Hi,
> I have the following problem: ejecting the cdrom fails under KDE with
> "eject failed" message (no matter mounted or unmounted). The only way to
> remove the cd from the drive is to execute the eject command as root. Is
> there any way to fix it?
> When executing the eject command as root the following message is appear:
> "eject: unable to eject, last error: Invalid argument"
> Thanks in advance!

Are you running 2.6 kernel? Which version? Self-compiled or Debian?

This *may* be caused by a problem in 2.6 kernels (fixed in .10 or .11) with
scsi ioctls (although called scsi, these ioctls exist both for IDe and SCSI
devices). The problem was that issuing under user an ioctl which is allowed
only for rw-opened devices on ro-opened device resulted into overwrite of
in-kernel ioctl permission table, causing any futher calls to the same
ioctl as non-root to fail.

Main symptom of that problem was that writing CDs failed, and non-root
ejects on device on which a CD write was attempted also failed.

Some time ago I applied the following patch to the kernel to fix the problem
(found somewhere in LKML and adopted to apply cleanly to what I had):

--- old/drivers/block/scsi_ioctl.c 2005-01-26 22:53:30.000000000 +0300
+++ new/drivers/block/scsi_ioctl.c 2005-01-26 22:53:36.000000000 +0300
@@ -197,10 +197,8 @@
if (type & CMD_WRITE_SAFE) {
if (file->f_mode & FMODE_WRITE)
return 0;
- }
-
- if (!(type & CMD_WARNED)) {
- cmd_type[cmd[0]] = CMD_WARNED;
+ } else if (!(type & CMD_WARNED)) {
+ cmd_type[cmd[0]] |= CMD_WARNED;
printk(KERN_WARNING "scsi: unknown opcode 0x%02x\n",cmd[0]);
}

On newer kernels problem was fixed.
I don't remember if Debian kernel was affected.


--
To UNSUBSCRIBE, email to debian-kde-REQUEST DeleteThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org

Intresting: when I mount, umount and eject when using krusader everything work
just fine. It unlock the door automatically after the disk was umounted.

------- Original message -------
From: Nick Leverton <nick.RemoveThis@leverton.org>
To: debian-kde.RemoveThis@lists.debian.org
Subject: Re: CD-ROM eject
Date: 26 éÀÎØ 2005 19:43
> On Sun, Jun 26, 2005 at 08:30:15PM +0300, Andrey Andreev wrote:
> > Are you trying to eject while Konqueror has the devices tree open?
> > That's what I sometimes do and it fails miserably. Try closing all
> > Konquerors and eject then.
>
> And probably (as root)
> /etc/init.d/famd stop
> if you're using any sort of automounting.
>
> Nick

I use the default 2.6.8-2-686 Debian kernel. I have only a dvd reader.
Since I've found that the krusader filemanager work correctly in that case, I
think this is a bug in konqueror or any other kde utility, because in gnome
it work as it should work.
Well probably gonna use something like "sysctl -w dev.cdrom.lock=0" to fix it
somehow.

------- Original message -------
From: "Nikita V. Youshchenko" <yoush DeleteThis @cs.msu.su>
To: debian-kde DeleteThis @lists.debian.org
Subject: Re: CD-ROM eject
Date: 26 éÀÎØ 2005 20:01
> > Hi,
> > I have the following problem: ejecting the cdrom fails under KDE with
> > "eject failed" message (no matter mounted or unmounted). The only way to
> > remove the cd from the drive is to execute the eject command as root. Is
> > there any way to fix it?
> > When executing the eject command as root the following message is appear:
> > "eject: unable to eject, last error: Invalid argument"
> > Thanks in advance!
>
> Are you running 2.6 kernel? Which version? Self-compiled or Debian?
>
> This *may* be caused by a problem in 2.6 kernels (fixed in .10 or .11) with
> scsi ioctls (although called scsi, these ioctls exist both for IDe and SCSI
> devices). The problem was that issuing under user an ioctl which is allowed
> only for rw-opened devices on ro-opened device resulted into overwrite of
> in-kernel ioctl permission table, causing any futher calls to the same
> ioctl as non-root to fail.
>
> Main symptom of that problem was that writing CDs failed, and non-root
> ejects on device on which a CD write was attempted also failed.
>
> Some time ago I applied the following patch to the kernel to fix the
> problem (found somewhere in LKML and adopted to apply cleanly to what I
> had):
>
> --- old/drivers/block/scsi_ioctl.c 2005-01-26 22:53:30.000000000 +0300
> +++ new/drivers/block/scsi_ioctl.c 2005-01-26 22:53:36.000000000 +0300
> @@ -197,10 +197,8 @@
> if (type & CMD_WRITE_SAFE) {
> if (file->f_mode & FMODE_WRITE)
> return 0;
> - }
> -
> - if (!(type & CMD_WARNED)) {
> - cmd_type[cmd[0]] = CMD_WARNED;
> + } else if (!(type & CMD_WARNED)) {
> + cmd_type[cmd[0]] |= CMD_WARNED;
> printk(KERN_WARNING "scsi: unknown opcode
> 0x%02x\n",cmd[0]); }
>
> On newer kernels problem was fixed.
> I don't remember if Debian kernel was affected.

The 2.6.8 and 2.6.9 kernels were horribly buggy. It's really unfortunate that
Debian decided to keep 2.6.8 for the sarge launch. Hopefully an RC release
later on will switch to a more stable kernel.

Before you try work-arounds for Konqueror, try upgrading to 2.6.10 or 2.6.11.
They're far more stable. (Either the pre-packaged Debian ones or fresh
copies from kernel.org. I prefer the latter, but either should work.)

On Sunday 26 June 2005 02:07 pm, Serja wrote:
> I use the default 2.6.8-2-686 Debian kernel. I have only a dvd reader.
> Since I've found that the krusader filemanager work correctly in that case,
> I think this is a bug in konqueror or any other kde utility, because in
> gnome it work as it should work.
> Well probably gonna use something like "sysctl -w dev.cdrom.lock=0" to fix
> it somehow.

--
Larry Garfield AIM: LOLG42
larry.RemoveThis@garfieldtech.com ICQ: 6817012

"If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an idea,
which an individual may exclusively possess as long as he keeps it to
himself; but the moment it is divulged, it forces itself into the possession
of every one, and the receiver cannot dispossess himself of it." -- Thomas
Jefferson


--
To UNSUBSCRIBE, email to debian-kde-REQUEST.RemoveThis@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.RemoveThis@lists.debian.org

Unfortunately I have some hardware with partially closed-source drivers and
those drivers are incompatible with the 2.6.10 or 2.6.11 kernels (yet?). I've
got a promise from the hardware wendor that the support for the newest kernels
will be added soon (it was a few mounth ago), but there is still no new
drivers and therefore the latest kernels are useless for me.

------- Original message -------
From: Larry Garfield <larry.DeleteThis@garfieldtech.com>
To: debian-kde.DeleteThis@lists.debian.org
Subject: Re: CD-ROM eject
Date: 26 éÀÎØ 2005 21:30
> The 2.6.8 and 2.6.9 kernels were horribly buggy. It's really unfortunate
> that Debian decided to keep 2.6.8 for the sarge launch. Hopefully an RC
> release later on will switch to a more stable kernel.
>
> Before you try work-arounds for Konqueror, try upgrading to 2.6.10 or
> 2.6.11. They're far more stable. (Either the pre-packaged Debian ones or
> fresh copies from kernel.org. I prefer the latter, but either should
> work.)
>
> On Sunday 26 June 2005 02:07 pm, Serja wrote:
> > I use the default 2.6.8-2-686 Debian kernel. I have only a dvd reader.
> > Since I've found that the krusader filemanager work correctly in that
> > case, I think this is a bug in konqueror or any other kde utility,
> > because in gnome it work as it should work.
> > Well probably gonna use something like "sysctl -w dev.cdrom.lock=0" to
> > fix it somehow.
>
> --
> Larry Garfield AIM: LOLG42
> larry.DeleteThis@garfieldtech.com ICQ: 6817012
>
> "If nature has made any one thing less susceptible than all others of
> exclusive property, it is the action of the thinking power called an idea,
> which an individual may exclusively possess as long as he keeps it to
> himself; but the moment it is divulged, it forces itself into the
> possession of every one, and the receiver cannot dispossess himself of it."
> -- Thomas Jefferson

I've set it up in Kcontrol option, but it never shows me a mounted/umounted
devices on the desktop. To be more correct: sometimes it shows and sometimes
not.
I've just tried out kwikdisk and sometimes it's work (50/50%). I've set the
eject command for unmound cd-s and sometimes it work and sometimes not.
It seems the default command for ejecting cd-s (kio_devices_mounthelper) not
work in Debian as it should work.
I have one more question: in gnome when you insert a media cd it starts the
appropriate application (gnome-cd, totem, etc). Is there any settings menu in
kde which will allow to set up similar things. I know how to setup kscd, but
it start playing only if it were previously placed in the systray.
Thanks in advance!

------- Original message -------
From: hacker <golfbuf.DeleteThis@gmail.com>
To: debian kde <debian-kde.DeleteThis@lists.debian.org>
Subject: Re: CD-ROM eject
Date: 27 éÀÎØ 2005 03:47
> On 6/26/05, Serja <mekoc.DeleteThis@inbox.ru> wrote:
>
> I find that if I configure the desktop to have un/mounted devices
> showing, and use these (right click to get menu) to mount and unmount,
> then I have no problem (even if konqueror is still opened to the
> drive). Have you tried this? Also, there's something called kwikdisk
> that works too.
>
> regards,
>
> hacker

I've just executed the "sysctl -w dev.cdrom.lock=0" and now the ejecting work.
It seems that some kde application won't unlock the device even if it's
already unmounted. I've read the kernel documentation and it says that the
applications which uses the cdrom devices should do it with O_NONBLOCK
option. Maybe some kde apps don't do that?

------- Original message -------
From: hacker <golfbuf RemoveThis @gmail.com>
To: debian kde <debian-kde RemoveThis @lists.debian.org>
Subject: Re: CD-ROM eject
Date: 27 éÀÎØ 2005 03:47
> On 6/26/05, Serja <mekoc RemoveThis @inbox.ru> wrote:
>
> I find that if I configure the desktop to have un/mounted devices
> showing, and use these (right click to get menu) to mount and unmount,
> then I have no problem (even if konqueror is still opened to the
> drive). Have you tried this? Also, there's something called kwikdisk
> that works too.
>
> regards,
>
> hacker

On 6/26/05, Serja <mekoc DeleteThis @inbox.ru> wrote:

> Hi,
> I have the following problem: ejecting the cdrom fails under KDE with "eject
> failed" message (no matter mounted or unmounted). The only way to remove the
> cd from the drive is to execute the eject command as root. Is there any way
> to fix it?
> When executing the eject command as root the following message is appear:
> "eject: unable to eject, last error: Invalid argument"
> Thanks in advance!

My girl-friend had the same problem on Sarge with 2.6.8-2-686 and KDE 3.3.x

chmod 4755 /usr/bin/eject

helped. But I'd think about it a moment on a system with untrusted users.

Regards,
Jim

Then should it be reported as a bug? Just because in gnome there is no problem
with eject. And therefore it should not be in kde too.
For now I using the following lines in my sysctl.conf file:
dev.cdrom.autoclose=0
dev.cdrom.lock=0
I know it might be dangerous is used not carefully, but at least there is no
problems with eject anymore.

------- Original message -------
From: Jim MacBaine <jmacbaine.RemoveThis@gmail.com>
To: Serja <mekoc.RemoveThis@inbox.ru>
Subject: Re: CD-ROM eject
Date: 27 éÀÎØ 2005 17:27
> On 6/26/05, Serja <mekoc.RemoveThis@inbox.ru> wrote:
> > Hi,
> > I have the following problem: ejecting the cdrom fails under KDE with
> > "eject failed" message (no matter mounted or unmounted). The only way to
> > remove the cd from the drive is to execute the eject command as root. Is
> > there any way to fix it?
> > When executing the eject command as root the following message is appear:
> > "eject: unable to eject, last error: Invalid argument"
> > Thanks in advance!
>
> My girl-friend had the same problem on Sarge with 2.6.8-2-686 and KDE 3.3.x
>
> chmod 4755 /usr/bin/eject
>
> helped. But I'd think about it a moment on a system with untrusted users.
>
> Regards,
> Jim

On Sunday 26 June 2005 05:46 am, Serja wrote:
> Hi,
> I have the following problem: ejecting the cdrom fails under KDE with
> "eject failed" message (no matter mounted or unmounted). The only way to
> remove the cd from the drive is to execute the eject command as root. Is
> there any way to fix it?
> When executing the eject command as root the following message is appear:
> "eject: unable to eject, last error: Invalid argument"
> Thanks in advance!

I seem to recall people having this problem, and that it was caused by
kio_audiocd. The situation was that if the services sidebar in konqueror was
opened even briefly while in the folder for the mounted cdrom, that
kio_audiocd would somehow grab the device and never let go, even once both
the sidebar and that instance of konqueror were closed. The workarounds
were:

1) Don't open the services sidebar while a cdrom is mounted.
2) Close the konqueror instance, then kill all kio_audio instances.

This is debian bugs #284853, #293494, and #305709 if you want to look in those
for more information.

Josh


--
To UNSUBSCRIBE, email to debian-kde-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org

On Tuesday 28 June 2005 09:42 am, Josh Metzler wrote:
> I seem to recall people having this problem, and that it was caused by
> kio_audiocd.
....
> This is debian bugs #284853, #293494, and #305709 if you want to look in
> those for more information.
>
> Josh

If this is indeed your problem, go vote for kde bug #95676
http://bugs.kde.org/95676

Josh


--
To UNSUBSCRIBE, email to debian-kde-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org