[Bug 880240] Re: system doesn't turn off if "sudo halt" is given
Modification in /etc/default/grub takes effect next time OS starts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/880240 Title: system doesn't turn off if "sudo halt" is given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/880240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 880240] Re: system doesn't turn off if "sudo halt" is given
You could try the workaround found in this article: http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze- during-reboots-and-restarts/ "reboot=bios" fixed the shutdown and reboot hangs for me. Run in terminal> sudo nano /etc/default/grub Edit this line and save> GRUB_CMDLINE_LINUX="reboot=bios" Run in terminal> sudo update-grub Restart your PC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/880240 Title: system doesn't turn off if "sudo halt" is given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/880240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881792] Re: System will not power down after shutdown
*** This bug is a duplicate of bug 859075 *** https://bugs.launchpad.net/bugs/859075 You could try the workaround found in this article: http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze- during-reboots-and-restarts/ "reboot=bios" fixed the shutdown and reboot hangs for me. Run in terminal> sudo nano /etc/default/grub Edit this line and save> GRUB_CMDLINE_LINUX="reboot=bios" Run in terminal> sudo update-grub Restart your PC ** This bug has been marked a duplicate of bug 859075 Oneiric does not shutdown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881792 Title: System will not power down after shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/881792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 859075] Re: Oneiric does not shutdown
You could try the workaround found in this article: http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze- during-reboots-and-restarts/ "reboot=bios" fixed the shutdown and reboot hangs for me. Run in terminal> sudo nano /etc/default/grub Edit this line and save> GRUB_CMDLINE_LINUX="reboot=bios" Run in terminal> sudo update-grub Restart your PC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/859075 Title: Oneiric does not shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/859075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002429] Re: Ubuntu 12.04 hangs on shutdown and restart
This article helped me a lot: http://linux.koolsolutions.com/2009/08/04 /howto-fix-linux-hangfreeze-during-reboots-and-restarts/ Instead of using "reboot=pci", I used "reboot=bios" and I added it to GRUB_CMDLINE_LINUX instead of GRUB_CMDLINE_LINUX_DEFAULT Type in a terminal: sudo nano /etc/default/grub find the line: GRUB_CMDLINE_LINUX="" and change it to: GRUB_CMDLINE_LINUX="reboot=bios" perform via the terminal: sudo update-grub Restart your PC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002429 Title: Ubuntu 12.04 hangs on shutdown and restart To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1002429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886438] Re: automatic font color in 3.4.3 is grey instead of black
*** This bug is a duplicate of bug 734428 *** https://bugs.launchpad.net/bugs/734428 Same problem using LibreOffice v3.5.3.2 with Ubuntu 12.04. I just freshly installed my system. And if I print it or export the document to PDF, the gray color is preserved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886438 Title: automatic font color in 3.4.3 is grey instead of black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/886438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 831711] Re: Synaptic incorrectly reports "NOT AUTHENTICATED" for packages
I confirm that the same problem is present in Precise. I just freshly installed a new system, selected dozens of packages in Synaptic, clicked "Apply" button, and the "NOT AUTHENTICATED" issue appeared. I clicked the "Install" button, nothing happened, except an error message about some package that I don't remember. I clicked again on "Apply" and this time everything worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/831711 Title: Synaptic incorrectly reports "NOT AUTHENTICATED" for packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/831711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611459] Re: Bluetooth utility doesn't remember the friendly name after reboot
** Attachment added: "The USB Bluetooth dongle I have the problem with" http://launchpadlibrarian.net/52706553/ebay_bluetooth_dongle.jpg ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52705602/Dependencies.txt -- Bluetooth utility doesn't remember the friendly name after reboot https://bugs.launchpad.net/bugs/611459 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 611459] [NEW] Bluetooth utility doesn't remember the friendly name after reboot
Public bug reported: Binary package hint: gnome-bluetooth I bought one of those USB Bluetooth v2.1 dongle from eBay, to replace my old v1.2 dongle which worked perfectly, and came from eBay too. I plugged it into my PC, turned on my PC, transfered some files from a PDA and talked via a Bluetooth headset, everything worked as expected. However, I'm unable to change the friendly name via the GNOME Bluetooth properties. The name is stuck to "ISSCBTM". In fact, the friendly name reverts to "ISSCBTM" only after a reboot. If I change the friendly name, my Bluetooth devices will see the new friendly name during all my session, but after a reboot, they'll see again the default "ISSCBTM". I tried on both Karmic and Lucid, with the same dongle but with different PCs, and the same thing happens. This didn't happen with my old v1.2 dongle. If I use this new v2.1 dongle with Windows XP or Windows 7, BlueSoleil or built-in driver, everything works perfectly. I can change the friendly name without any troubles, and stays even after a reboot. I found that this same problem happens with Fedora, https://bugzilla.redhat.com/show_bug.cgi?id=551574 ProblemType: Bug Architecture: i386 Date: Thu Jul 29 16:05:53 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2) NonfreeKernelModules: nvidia Package: gnome-bluetooth 2.28.1-0ubuntu2 ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-22.60-generic SourcePackage: gnome-bluetooth Uname: Linux 2.6.31-22-generic i686 XsessionErrors: (gnome-settings-daemon:3201): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:3201): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:3243): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:3235): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (firefox-bin:5519): GLib-WARNING **: g_set_prgname() called multiple times ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Bluetooth utility doesn't remember the friendly name after reboot https://bugs.launchpad.net/bugs/611459 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 526760] Re: Corrupted screen and degraded performance on Savage/IX-MV
** Description changed: Binary package hint: xserver-xorg-video-savage Hi! Just decided to give a try to Ubuntu 10.04 on this Omnibook X3 laptop, and following is what happens. The login screen is corrupted, but if I enter the password it resets to something tartan-like look. After a little while the magic happens and the desktop appears. This after the last update of lucid lynx; until last week everything was a burden, and I was used to switch to console mode with network in order to gain new updates. If I try with GLXINFO or GLXGEARS I get an error and, generally speaking, screen is a little slow. Just to say, everything is fine with ubuntu 9.04 and, if I run "dhry2" benchmark, results between 9.04 and 10.04 kernel are almost identical. I'll attach logs. The error given by glxinfo is l...@ubuntu:~$ glxinfo > glxinfo.txt glxinfo: ../common/drirenderbuffer.c:69: driNewRenderbuffer: Assertion `format == 0x1908 || format == 0x8050 || format == 0x8058 || format == 0x81A5 || format == 0x81A6 || format == 0x81A7 || format == 0x8D48' failed. Aborted (core dump creato) - - Let me know how I can help. If needed I can also take some shots of the login screen with my camera. + Let me know how I can help. If needed I can also take some shots of the + login screen with my camera. Ciao Luca -- Corrupted screen and degraded performance on Savage/IX-MV https://bugs.launchpad.net/bugs/526760 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 33617] Re: [agp] X.org does not initialize screen on IBM T20, T21, T22
Ok, I agree with you. This card is now too old to support. Maybe the PCI enforcement should be implemented then. However, like Tormod said, there should be an option to enable AGP and let some people test it. -- [agp] X.org does not initialize screen on IBM T20, T21, T22 https://bugs.launchpad.net/bugs/33617 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33617] Re: [agp] X.org does not initialize screen on IBM T20, T21, T22
Hmmm, you are still trying to force the driver to use PCI if it is in combination with the T22 Intel AGP bridge? I thought someone could try to fix the source of the problem and try to get back AGP. Forcing the driver to be with PCI, that would be an ugly patch. Is there someone here who is trying to get deep in the AGP problem? -- [agp] X.org does not initialize screen on IBM T20, T21, T22 https://bugs.launchpad.net/bugs/33617 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
