[Bug 1111884] Re: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT
Still happens on current 13.10, all update applied. Sad, after one year... 02:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) ~# uname -a Linux Artemis 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:16:27 UTC 2013 i686 athlon i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884 Title: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 593047] Re: distcc fails to distribute to IPv6 addresses
new version still not available in lucid/updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/593047 Title: distcc fails to distribute to IPv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/distcc/+bug/593047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610869] Re: mountall ignores nofail mount option
"Yust wait long enough, someone will send a patch" Ok, so after 1.5 years here is my solution for the problem. "nofail" wasn't implemented at all, though it is documented. Geee... patch may have side effects but does what it should. Ah and it is against mountall 2.15.3 from Ubuntu 10.04. I don't write "LTS" by intention, because it seems to be completely unsupported. ** Patch added: "reel-mountall-nofail.diff" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/610869/+attachment/2833835/+files/reel-mountall-nofail.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/610869 Title: mountall ignores nofail mount option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/610869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610869] Re: mountall ignores nofail mount option
Using "nobootwait" is not an option to me, because "nobootwait" also causes the system not to wait for the filesystem to be checked. In other words, the fsck is run in background while the boot process continues. This causes other services that depend on that fs to fail. Also "optional" (mentioned in fstab man page) does not work as expected, it also causes Plymouth to stop the boot process and to display the S&M message. I just need an option that causes the boot to continue if a (external USB) device is removed and not to display stupid messages on the console where no display and no keyboard is connected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/610869 Title: mountall ignores nofail mount option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/610869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 474609] Re: nspluginviewer crashed with SIGSEGV in nsPluginInstance::getCurrentPageURL()
*** This bug is a duplicate of bug 463319 *** https://bugs.launchpad.net/bugs/463319 gnash is not installed here, crashes anyway. kubuntu 10.04, KDE upgraded to 4.4.5 Konqueror Version 4.4.5 (KDE 4.4.5) Unter KDE 4.4.5 (KDE 4.4.5) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/474609 Title: nspluginviewer crashed with SIGSEGV in nsPluginInstance::getCurrentPageURL() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnash/+bug/474609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656878] Re: network interface does not come up when configured as "manual"
no, this changed from 8.04 to 10.04 as I was trying to explain. So what is now the intended configuration for bringing up an interface with IPv6 only? The manpage for interfaces doesn't give a hint for this case. If it's not a bug in ifupdown, then it's a bug in the manpage not documenting this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/656878 Title: network interface does not come up when configured as "manual" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/656878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523484] Re: ureadahead requires /var on root filesystem
The fix linked in #29 is better and easier. I don't like to have variable files on / . Thats why we use seperate /var partitions ;) This is the change to the upstart conf: sudo sed -i 's+^start on starting mountall+start on mounted MOUNTPOINT=/var+' /etc/init/ureadahead.conf @Alf Gaida heretic question: is ureadahead installed in Ubuntu Server? ;) But I'm also very disappointed of 10.04. It should not be called LTS, it should be called "Unsupported". I think we can wait until "zappy zebra" for this to be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/523484 Title: ureadahead requires /var on root filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ureadahead/+bug/523484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568180] Re: E: Could not perform immediate configuration on 'bash'.Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
related to #546447 -- E: Could not perform immediate configuration on 'bash'.Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) https://bugs.launchpad.net/bugs/568180 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 568180] Re: E: Could not perform immediate configuration on 'bash'.Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
i think this always happens if you have circular dependencies. e.g. pkg a depends on b, b depends on c and c depends on a. Then first "c" is installed but configuration fails because "a" is (not yet) installed workaround: echo 'APT::Immediate-Configure "false";' > /etc/apt/apt.conf.d/67configure -- E: Could not perform immediate configuration on 'bash'.Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) https://bugs.launchpad.net/bugs/568180 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 656878] [NEW] network interface does not come up when configured as "manual"
Public bug reported: Binary package hint: ifupdown This affects ubuntu 10.04 I configure a network interface as "auto" and "manual" in /etc/network/interfaces . But it is not "up" after a reboot. "ifconfig" does not show it in its list. The thing is, i only need the inet6 (link-layer) address on this interface, nothing else. /etc/network/interfaces: --- 8< --- auto eth0 iface eth0 inet manual --- 8< --- if i do a "ifconfig" the interface is not listed. "dmesg | grep eth" gives me: [1.161468] eth0: RTL8168b/8111b at 0xf806, 00:e0:f4:17:42:a0, XID 9850 IRQ 27 but no "link up" just after a manual "ifconfig eth0 up" the device is listed with ifconfig, has ipv6 address and dmesg says "r8169: eth0: link up" the manpage for interfaces says: "Lines beginning with the word "auto" are used to identify the physical interfaces to be brought up when ifup is run with the -a option." There is no depency on a static address or something else. So this is a bug. The interface is not up. Also, this worked fine with ubuntu 8.04!!! as a workaround in /e/n/i i can say: --- 8< --- auto eth0 iface eth0 inet manual up ifconfig eth0 up --- 8< --- but this should not be the intended method to bring an interface up, is it? Versions: ifupdown 0.6.8ubuntu29.1 (10.04.1) ifupdown 0.6.8ubuntu8 (8.04.4) maybe this is not in ifupdown but somewhere else in upstart/init . ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- network interface does not come up when configured as "manual" https://bugs.launchpad.net/bugs/656878 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 539814] Re: tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels < 2.6.22
This also affects cp and touch from coreutils, maybe others. r...@monster:~# mkdir bla r...@monster:~# cp -a bla blubb cp: preserving times for `blubb': Bad file descriptor r...@monster:~# touch bla touch: setting times of `bla': Bad file descriptor Why ist there still no fix after six months? Had to use the files from debian :( -- tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels < 2.6.22 https://bugs.launchpad.net/bugs/539814 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 249340] Re: Gutsy->Hardy upgrade hangs in localedef
i found out that localedef works well with the old kernel 2.6.22-14 (the original one coming with gutsy) but not the current one -15 in gutsy. Maybe the kernel is messed up? So if all fails and you still have the old kernel on your box, use this one and do the upgrade. -- Gutsy->Hardy upgrade hangs in localedef https://bugs.launchpad.net/bugs/249340 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