[Bug 235202] Re: eject command fails with unable to open error
** Changed in: eject (Ubuntu) Status: Incomplete = Fix Released ** Changed in: hal (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/235202 Title: eject command fails with unable to open error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/235202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
Matthew we are wondering if it is still an issue for you? Thank you for telling us! ** Changed in: hal (Ubuntu) Status: New = Incomplete ** Changed in: eject (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/235202 Title: eject command fails with unable to open error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/235202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
It is no longer an issue in Precise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/235202 Title: eject command fails with unable to open error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/235202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
I was going to say that the answer was udisks --eject /dev/whatever , but I noticed that udisksctl (which I think is udisks2 replacement) doesn't have --eject; so I wonder what the right answer is. If udisks is the right way to go these days then perhaps replacing eject my a small shell script to udisks would be reasonable. Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/235202 Title: eject command fails with unable to open error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/235202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
This might be a case of bug #795239, but hard to tell for sure. Take a look and see what you think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/235202 Title: eject command fails with unable to open error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/235202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
I don't think it's the same issue; this one is about how to grant users certain permissions (is that even relevant? are people just supposed to use udisks --unmount /dev/whatever? that's not as simple as eject /mnt/mount-path, since you need to know the device name), and the other is about eject's mechanism for automatically picking the default optical drive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/235202 Title: eject command fails with unable to open error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/235202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
Sorry it took me so long to get back to you on this, I've been busy. - I agree that making eject suid is a suboptimal solution. No argument there. - I believe that eject is different vs. a simple umount. It does something to the USB device, though I'm not sure what. This is best illustrated by plugging in an iPod so that it kicks into disk mode. You'll get a USB mass storage device, and the display will show a little circle with a slash through it (you know, the universal no sign). If, at this point, you unmount it, the circle/slash stays. If you eject it, the circle/slash turns into a check, because it is okay to remove. - In my case, none of these are optical drives, they are all disk or flashed based devices of some type (iPods, SD cards from my camera, external magnetic hard disks, etc.) - Checking in to it, mine get assigned permissions of root:disk. Like the plugdev problem, if I gave every user membership to the disk group, this creates a potential problem. I think that a solution which may work here is a href=https://bugs.launchpad.net/ubuntu/+source/udev/+bug/128257/comments/7;this comment/a from Scott James Remnant, where he suggests letting ConsoleKit handle it. At least in my case, this would work, because I'm at the console poking things. -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
The problem isn't with eject; eject is working properly... I think. The permissions for /dev/sdb1 (on my machine, that's the first USB disk's ID) are 660, and it's owned by root:disk. I can add myself to the 'disk' group, but that gives me raw access to any fixed disk on the system, and I don't think that's a permission that should be tightly bound to being able to safely remove a USB stick. I don't think that eject should be suid root; Ubuntu manages permissions for access to the CD drive by users being in group 'cdrom', and the CD device being mode 660, owned by root:cdrom. The following bit suggests that the disk should belong to the 'root:plugdev' group, which the standard config tools *do* provide access for. http://qblog.remarqs.net/2008/05/13/usb-drive-annoyance-with-kde-and- udev/ If I make USB drive owned by group 'plugdev', I can easily eject it: $ sudo chown root:plugdev sdb sdb1 $ ls sd* -ld brw-rw 1 root disk8, 0 2008-11-24 13:43 sda brw-rw 1 root disk8, 1 2008-11-24 13:43 sda1 brw-rw 1 root disk8, 2 2008-11-24 13:43 sda2 brw-rw 1 root disk8, 5 2008-11-24 13:43 sda5 brw-rw 1 root plugdev 8, 16 2009-01-06 13:48 sdb brw-rw 1 root plugdev 8, 17 2009-01-06 13:48 sdb1 $ eject -v sdb1 eject: device name is `sdb1' eject: expanded name is `/dev/sdb1' eject: `/dev/sdb1' is mounted at `/media/disk' eject: unmounting device `/dev/sdb1' from `/media/disk' eject: `/dev/sdb1' is a multipartition device eject: trying to eject `/dev/sdb1' using CD-ROM eject command eject: CD-ROM eject command succeeded On the other hand, according to bug 128257, the 'plugdev' group is deprecated, since the above configuration means that anyone on the system with plugdev privileges has full access to the USB stick. Perhaps the best solution would be to create the device node either chown'd to or chgrp'd to the primary group of the user on whose behalf it's mounted... but then again, not all USB storage is attached solely for the benefit of a single user, and some *should* actually be chown'd root:disk like any internally-attached device would be. So perhaps the problem is that the system is mounting the USB drive with bad permissions... and perhaps the problem is that eject shouldn't be trying to run 'eject' commands on USB sticks--does the 'eject' command actually do anything that simply unmounting the device doesn't, or is it only sensible for USB-attached optical drives? I'm adding a hal task in case it's their issue, and marking both tasks 'new' for now. ** Changed in: eject (Ubuntu) Status: Incomplete = New -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
This is still an issue. I solved it by making eject setuid. -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
This is true for both Hardy and Intrepid. -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug. -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
Attached ** Attachment added: fstab http://launchpadlibrarian.net/14772961/fstab -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
Thanks, i saw your file, and anything is wrong (but i have a doubt) your Cd is SATA? Because my unit is ATAPI and appears like /dev/hdc ** Changed in: eject (Ubuntu) Sourcepackagename: None = eject -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
The CD is ATAPI, but all cdrom devices I've used in recent history (since early 2.6 series) have been using the new disk abstraction layer and thus appear as SCSI devices. This is increasingly true for ATA hard disks as well - this same desktop has the ATA hard disk showing as sda. Before hardy, it was hda (no physical hardware change has happened). That aside, this is a non-issue here, as I am attempting to eject /dev/sdc2, which is a USB device. The device can be mounted, I can read and write data from/to it, and I can eject it if I do so via sudo. So, the device is actually there and works, and I believe this to just be a permissions problem, which did not occur in gutsy. -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235202] Re: eject command fails with unable to open error
Can you post your file /etc/fstab? Thanks ** Changed in: ubuntu Status: New = Incomplete -- eject command fails with unable to open error https://bugs.launchpad.net/bugs/235202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
