** 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
Titl
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:
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
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
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 ejec
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 o
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 pl
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 thi
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
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-
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 receive
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
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 re
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-b
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.
-
15 matches
Mail list logo
