[Bug 283316] Re: CD-ROM tray closes automatically after eject
My ASUS SATA drive model is DRW-20B1LT, using 32-bit Intrepid. -- CD-ROM tray closes automatically after eject https://bugs.launchpad.net/bugs/283316 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 283316] Re: CD-ROM tray closes automatically after eject
I had this problem with my IDE drive, a GSA-4167B by LG, when I first installed Intrepid. It went away after one of the updates, but not the same updates others reported at the time. I have since replaced this with an ASUS SATA drive. When I did this, the problem returned more consistently. It was much more of a problem because this drive's tray moves more quickly! One of the updates about 1-2 weeks ago seems to have fixed this for now. So I have used two different brands of drive with two different interfaces. Hope this has helped by adding to anecdotal evidence. -- CD-ROM tray closes automatically after eject https://bugs.launchpad.net/bugs/283316 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 303199] Re: virtualbox-ose-modules broken AGAIN
Using module-assistant auto-install isn't working with the current virtualbox-ose-source package. Auto-install is expecting to find the virtualbox sources under /usr/src and doesn't, so fails. The file list reveals that the sources are not being placed where auto-install expects them: http://packages.ubuntu.com/intrepid/all/virtualbox-ose-source/filelist Here is the output I get: # *** start output Updated infos about 1 packages Getting source for kernel version: 2.6.27-9-generic Kernel headers available in /usr/src/linux-headers-2.6.27-9-generic Creating symlink... apt-get install build-essential Reading package lists... Done Building dependency tree Reading state information... Done build-essential is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Done! unpack The source tarball could not be found! Package virtualbox-ose-source not installed? Running m-a -f get virtualbox-ose-source may help. /usr/share/modass/packages/default.sh build KVERS=2.6.27-9-generic KSRC=/usr/src/linux KDREV=2.6.27-9.19 kdist_image find: `/usr/src/modules/virtualbox*': No such file or directory # *** end output There's an ncurses dialogue in the middle somewhere, allowing me to view a build log, which only has an entry telling me logging is being started in /var/cache/modass/virtualbox-ose- source.buildlog.2.6.27-9-generic.1230206467. I selected Continue in this case. Something seems wrong here. Is there a safe workaround if a proper fix is not simple? -- virtualbox-ose-modules broken AGAIN https://bugs.launchpad.net/bugs/303199 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 136702] Re: nautilus 'replace file' dialog box could give more information
I don't use KDE, but I like very much that its file manager (what's it called this week?) has this kind of attention to detail. It impressed me the minute I saw it. Of course users can't make an informed decision without access to relevant information. Perhaps if the concern is the delay required to gather this information, it could be hidden behind a more details toggle (one like that used in the GNOME update manager and others) and only generated on request. -- nautilus 'replace file' dialog box could give more information https://bugs.launchpad.net/bugs/136702 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 155461] Re: Upgrade problems Feisty - Gutsy
*** This bug is a duplicate of bug 134858 *** https://bugs.launchpad.net/bugs/134858 Me three on this experience. Thanks for saving me a lot of typing, Chris. :~) Though the upgrade so far seems to have worked (I had to leave the machine unattended again), I'm still a little nervous about a failure in authenticaton-related packages. I didn't reinstall libpam0g, but gdm logins and sudo are going fine. BTW, if libpam0g was left in an unusable state last time I tried upgrading, it probably explains why I couldn't get out of screenlock on my first upgrade attempt. (https://bugs.launchpad.net/ubuntu/+source /gnome-screensaver/+bug/146412/comments/3) (@Rog,Luis: The duplicate status seems wrong to me, too.) Hope this is helping someone. -- Upgrade problems Feisty - Gutsy https://bugs.launchpad.net/bugs/155461 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146412] Re: gnome-screensaver-dialog never shows up
I had a similar experience upgrading. I'm not entirely sure if the bug is the same, so this comment might warrant its own bug identifier. Here's the whole story. I've never done a successful upgrade from either CD or online, so I completely copied my root and home partitions to a spare disk before doing anything. I've safely reverted to Feisty thanks to the GPartEd Live CD. I issued sudo update-manager -d. (BTW I intended to do this before the official release, but the partition copying took too long). I chose to upgrade. Estimated time of several hours — stupid time to do it, really. Closed all of my desktop apps as advised. Went to sleep. Next morning my screensaver was on, but I only received the unlock dialogue for less than a second before it disappeared. Logged into a terminal, looking for a process to kill. Unable to kill gnome-screensaver, and couldn't find any other processes which looked right. I restarted X with ctrl-alt- backspace. This is where I have to admit that my recollection is less clear. I certainly wasn't able to load my complete desktop. On one try, I remember getting everything except the GNOME panels. I didn't think to try another WM. I gave up and restored because I needed to use the machine. I did capture some details but absent-mindedly blew them away when I restored my home partition! Kernel is 2.6.20-16-generic, Athlon 2000 processor, Nvidia card without proprietary driver, Metaballs screensaver. Can provide any further system details you think might be relevant. I think if this is reproducible in the upgrade context then it is a serious bug. At the very least, the upgrade might offer to disable the screensaver if this avoids the problem, and if it can't be readily solved by other means. I can imagine that a relatively new user going through his/her first upgrade would be considerably less impressed with Ubuntu after b0rking their machine like this in an upgrade. Apologies for longwindedness, hope it helps, and happy to provide further diagnostic info. -- gnome-screensaver-dialog never shows up https://bugs.launchpad.net/bugs/146412 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92452] Re: Akregator loses all rss feeds after update [feisty]
I can confirm I just lost about half my folders. Not happy (why is importance Undecided?). Didn't do any dist-upgrades. Running Ubuntu Feisty. Host had been up for several weeks. Powered off with akregator running, and then restarted. Have done this before without issues. If you need any other specific info, happy to supply, but struggling to think of anything noteworthy that might help reproduce. HTH somehow. -- Akregator loses all rss feeds after update [feisty] https://bugs.launchpad.net/bugs/92452 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
