** Changed in: devicekit-disks (Ubuntu Karmic)
Status: Fix Released => New
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This appears to be an ill advised 'fix' and some consideration should be
given to reverting the 02 patch.
While it will work as intended some some combinations of hardware types
and configurations it by no means works on all and most likely not even
the majority.
Can confirm with what Mr. Gardner
i have done abit more testing with regard to this problem.
in the test i used an audio-cd, dvd-video, dvd-data disc (win 7 disc),
and cd data disc (ubuntu 9.10 & ubuntu 9.04 discs)
this is the behaviour of these discs.
-the audio cd will mount and play in app and then unmount and eject with the
sorry but this still doesn't seem to work for me.
when i insert a dvd-video and then stop watching it and close totem and press
the eject button on the drive nothing happens. i still have to open nautilus
and unmount/eject from there.
--
can't eject unmounted cdrom with hardware button
https://
** Changed in: devicekit
Status: In Progress => Fix Released
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I also have confirmed that eject now works as expected. Thanks for the
quick response and obvious hard work.
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I confirm that now eject works as expected.
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
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.
This bug was fixed in the package devicekit-disks - 007-1ubuntu1
---
devicekit-disks (007-1ubuntu1) karmic; urgency=low
* Upload current Debian git head to pick up recent bug fixes.
* debian/rules: Enable quilt patch system. Add quilt build dependency.
* Add 01-mkfs-tempdir.patc
** Changed in: devicekit
Status: Won't Fix => In Progress
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Patch sent upstream for review.
** Changed in: linux (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu)
Assignee: Andy Whitcroft (apw) => (unassigned)
** Changed in: devicekit-disks (Ubuntu Karmic)
Status: In Progress => Fix Committed
--
can't eject unmo
Discussion result in upstream bug:
--
I think the kernel defaults should lock all used drives by default, and should
not be touched at bootup, and thhings like liveCD rootfs and similar setups
should not be unlocked by a global default setting.
I think we might want to
I can see no upstream commits changing this default at this time. Nor
any specific change between v2.6.31 and v2.6.32-rc1 which would account
for this working there. Does anyone have a pointer to the relevant
discussion.
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad
If the upstream default is changing and we are going to smash it in
userspace unconditionally it seems reasonable to change this in the
kernel to me. Do we have the upstream commit yet?
** Changed in: linux (Ubuntu Karmic)
Importance: Undecided => Low
** Changed in: linux (Ubuntu Karmic)
So, procps wouldn't work due to module loading race conditions.
Preferably this should just be changed in the kernel (waiting for Kernel
team input), if not,I'll hack it into devkit-disks.
** Package changed: procps (Ubuntu) => devicekit-disks (Ubuntu)
** Changed in: devicekit-disks (Ubuntu)
Kernel team, are you fine with making this change in karmic? (Switching
the default value of /proc/sys/dev/cdrom/lock to 0). They are currently
discussing making that change upstream.
If not, I'll hack it into a sysctl script somewhere, but it'd be both
subject to race conditions (see previous com
if this is fixed in kernel 2.6.32 are we going to get this kernel in
karmic, as this will be a major usability bug, especially for new users
or users not use to linux.
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification bec
This may be a duplicate of this bug:
https://bugs.launchpad.net/ubuntu/+source/devicekit-disks/+bug/438065
Seems like a kernel bug, fixed in 2.6.32...
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a m
** Changed in: devicekit
Status: Confirmed => Won't Fix
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
On Tue, 2009-09-29 at 20:21 +, Maxim Levitsky wrote:
> However, the procps upstart job is currently running before modules are
> loaded by udev, thus this doesn't work.
>
If we want to change the default, we should just change that in the
kernel
affects linux
Scott
--
Scott James Remnant
@Martin Pitt:
I have tried your suggestion, but it doesn't work.
Here I have my own made kernel, and cdrom driver is compiled as a module
(sr_mod)
I think ubuntu also has sr_mod as a module.
However, the procps upstart job is currently running before modules are
loaded by udev, thus this doesn'
So, according to the upstream discussion David Zeuthen recommended to
just not lock CD-ROM trays by default. Kernel/userspace already handles
prematurely removed USB storage devices reasonably, and with read-only
devices like CD-ROMs it is even less of an issue. So we should just set
/proc/sys/dev/
** Changed in: devicekit-disks (Ubuntu)
Status: Confirmed => Triaged
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
So this is two bugs interealeved.
One is that nautilus keeps the cdrom device open (test it with fuser).
This is fault of brasero, I will open a seperate bug about that.
As a workaround, rename
mv /usr/lib/nautilus/extensions-2.0/libnautilus-brasero-extension.so
/usr/lib/nautilus/extensions-2.0/
For the workaround, you need to logout/login or kill nautilus for
changes to take effect (remember desktop windows is managed by nautilus,
and btw its address is x-nautilus-desktop://)
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug
** Changed in: devicekit
Status: Unknown => Confirmed
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
** Bug watch added: freedesktop.org Bugzilla #24052
https://bugs.freedesktop.org/show_bug.cgi?id=24052
** Also affects: devicekit via
https://bugs.freedesktop.org/show_bug.cgi?id=24052
Importance: Unknown
Status: Unknown
--
can't eject unmounted cdrom with hardware button
https:/
I can eject the drive when it is unmounted, but no attempt is made to unmount
it if it _is_ mounted.
9.04 didn't have this behavier
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bug
I believe devicekit-disks is responsible for this, like with bug 417964.
Updating affected package.
** Package changed: nautilus (Ubuntu) => devicekit-disks (Ubuntu)
** Changed in: devicekit-disks (Ubuntu)
Status: Incomplete => Confirmed
--
can't eject unmounted cdrom with hardware butto
Pretty much reproducible. Nothing specific is required - just insert the
disk, unmount it from computer location and push eject button to see
that nothing happens. Additional annoyance is that unmount requires
authorization. Anything else I can turn on to debug this misbehaviour?
kern.log
Jul 14
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: nautilus (Ubuntu
not confirming the issue there, unmount in the nautilus computer
location and eject works
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28869769/Dependencies.txt
--
can't eject unmounted cdrom with hardware button
https://bugs.launchpad.net/bugs/397734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
32 matches
Mail list logo
