Re: [Bug 99538] Re: Feisty usb stick Cannot eject volume
*** This bug is a duplicate of bug 63090 *** https://bugs.launchpad.net/bugs/63090 It seems the 10-storage-policy.fdi workaround helps, but does not restore the behaviour from Edgy and previous. -- Feisty usb stick Cannot eject volume https://bugs.launchpad.net/bugs/99538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 63090). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 99538] Re: Feisty usb stick Cannot eject volume
*** This bug is a duplicate of bug 63090 *** https://bugs.launchpad.net/bugs/63090 I can confirm the above problem on the release version of Ubuntu 7.04 with a 250 GB external Western Digital hard drive. I don't get the problem with my 128 MB flash drive or my card reader, but when I try to unmount the external HDD (even if nothing is using it), I get the message Cannot eject volume and the volume immediately re-mounts again. sudo eject My Book (as that is the name that comes up for the device) still works. The workaround provided by Martin Pitt allows the volume to umount again, but I do not hear the audible click of the drive (which I assume is the HDD heads parking) that I did with Edgy and previous versions. So, while the workaround lets me unmount the drive again, it does not seem to unmount as cleanly as it did in Edgy and earlier. The device does unmount though, because it no longer appears in the list provided by the mount command. As with Martin Pitt's suggestion (moving the file somewhere else), restoring the Edgy version of the /usr/share/hal/fdi/policy/10osvendor/10-storage-policy.fdi file (which contained many more lines than the Feisty version does) also has the same effect, but, as I said, the unmounting behaviour does not seem as clean as it did in Edgy. Just to reiterate that this problem has only appeared for me in Feisty; in both Dapper and Edgy I don't have the issue. -- Feisty usb stick Cannot eject volume https://bugs.launchpad.net/bugs/99538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 63090). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 99538] Re: Feisty usb stick Cannot eject volume
*** This bug is a duplicate of bug 63090 *** https://bugs.launchpad.net/bugs/63090 ** Changed in: gnome-volume-manager (Ubuntu) Sourcepackagename: None = gnome-volume-manager ** Changed in: gnome-mount (Ubuntu) Sourcepackagename: gnome-volume-manager = gnome-mount -- Feisty usb stick Cannot eject volume https://bugs.launchpad.net/bugs/99538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 63090). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 89008] Re: gdm won't log in with cryptsetup and pam_mount on custom kernel
Yes. On 4/19/07, Sebastien Bacher [EMAIL PROTECTED] wrote: Do you still have the bug? -- gdm won't log in with cryptsetup and pam_mount on custom kernel https://bugs.launchpad.net/bugs/89008 You received this bug notification because you are a direct subscriber of the bug. -- gdm won't log in with cryptsetup and pam_mount on custom kernel https://bugs.launchpad.net/bugs/89008 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 89008] gdm won't log in with cryptsetup and pam_mount on custom kernel
Public bug reported: Binary package hint: gdm Using one of the stock Ubuntu kernels (2.6.17-10-generic or 2.6.17-11-generic), set up an encrypted user with cryptsetup and libpam- mount (to login using user password) using instructions such as these: http://www.pasteserver.net/317 Compile and install a custom kernel (such as the one provided by linux- source or a vanilla kernel). Use current config from /boot if you wish. gdm will not log in the encrypted user on the new kernel, the encrypted volume mounts but there is a black screen and you are returned to the login screen. kdm or xdm both work. Booting the previous kernel and gdm works as expected. ** Affects: gdm (Ubuntu) Importance: Undecided Status: Unconfirmed -- gdm won't log in with cryptsetup and pam_mount on custom kernel https://launchpad.net/bugs/89008 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
