[Bug 1070893] Re: not all ipv6 addresses are brought up on boot
Won't that create a bunch of eth0:0 eth0:1 eth0:2 interfaces? I want a single interface with multiple addresses (which it partially gives me now) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070893 Title: not all ipv6 addresses are brought up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1070893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070893] Re: not all ipv6 addresses are brought up on boot
Multiple IPv6 addresses don't work with a single eth0 and I don't want hundreds of eth0:99. The up' command is at least partially supported by man interfaces - but it only seems to run the first seven. Bug 508996 seems related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070893 Title: not all ipv6 addresses are brought up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1070893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070893] Re: not all ipv6 addresses are brought up on boot
Aha! I figured it out. The address line configured :7, but then an up command later tried to start 7 again, and it failed with: SIOCSIFADDR: File exists Failed to bring up eth0. Removing the duplicate line fixes the problem. So this issue is more that ifupdown stops processing when it encounters an error, which isn't really a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070893 Title: not all ipv6 addresses are brought up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1070893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070893] [NEW] not all ipv6 addresses are brought up on boot
Public bug reported: I have an /etc/network/interfaces that looks like this: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo eth0 iface lo inet loopback # The primary network interface iface eth0 inet dhcp dns-nameservers 127.0.0.1 iface eth0 inet6 static pre-up modprobe -q ipv6 ; /bin/true address 2001:470:1f1f:2f2f::7 netmask 64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::3/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::4/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::5/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::6/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::7/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::8/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::9/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::b/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::c/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::d/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::a/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::e/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::f/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:1/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:2/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:3/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:4/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:5/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:6/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:7/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:8/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1:9/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:0/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:1/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:2/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:3/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:4/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:5/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:6/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:7/64 up ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2:8/64 On reboot, however, only about the first 6 or so of the IPv6 addresses will be active. I have to manually run the ifconfig commands for the rest, and then restart Apache. This is what I run: r...@drydock.example.com ~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:0c:29:e1:72:26 inet addr:192.168.1.99 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: 2001:470:1f1f:2f2f::3/64 Scope:Global inet6 addr: fe80::20c:29ff:fee1:7226/64 Scope:Link inet6 addr: 2001:470:1f1f:2f2f::7/64 Scope:Global inet6 addr: 2001:470:1f1f:2f2f::5/64 Scope:Global inet6 addr: 2001:470:1f1f:2f2f::4/64 Scope:Global inet6 addr: 2001:470:1f1f:2f2f::6/64 Scope:Global inet6 addr: 2001:470:1f1f:2f2f::2/64 Scope:Global inet6 addr: 2001:470:1f1f:2f2f::1/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:77 errors:0 dropped:0 overruns:0 frame:0 TX packets:88 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14107 (14.1 KB) TX bytes:13114 (13.1 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:61 errors:0 dropped:0 overruns:0 frame:0 TX packets:61 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:19534 (19.5 KB) TX bytes:19534 (19.5 KB) r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::1/64 SIOCSIFADDR: File exists r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::2/64 SIOCSIFADDR: File exists r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::3/64 SIOCSIFADDR: File exists r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::4/64 SIOCSIFADDR: File exists r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::5/64 SIOCSIFADDR: File exists r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::6/64 SIOCSIFADDR: File exists r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::7/64 SIOCSIFADDR: File exists r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::8/64 r...@drydock.example.com ~ # ifconfig eth0 inet6 add 2001:470:1f1f:2f2f::9/64 r...@drydock.example.com ~ # ifconfig eth0 inet6 add
[Bug 1070893] Re: not all ipv6 addresses are brought up on boot
** Package changed: ubuntu = ifupdown (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070893 Title: not all ipv6 addresses are brought up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1070893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Has anyone been able to get this to work on 10.04-1 x64? I had it working in 32 mode, but now I can't seem to get it to work on the Sony VAIO VPCL135FX. My Xorg.log shows: (II) config/udev: Adding input device Nextwindow Fermi Touchscreen (/dev/input/event10) (**) Nextwindow Fermi Touchscreen: Applying InputClass evdev pointer catchall (**) Nextwindow Fermi Touchscreen: Applying InputClass nw fermi (II) LoadModule: nextwindow (II) Loading /usr/lib/xorg/modules/input/nextwindow_drv.so (II) Module nextwindow: vendor=X.Org Foundation compiled for 1.9.0, module version = 0.0.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 11.0 (WW) module ABI major version (11) doesn't match the server's version (7) (**) Option Device /dev/input/event10 (II) Nextwindow Fermi Touchscreen: Using device /dev/input/event10. (**) Option UseTouchHelp 1 (II) Nextwindow Fermi Touchscreen: Using touch help. (**) Option DragThreshold 10 (**) Option RightClickTimeout 1200 (**) Option DoubleClickTimeout 500 (**) Nextwindow Fermi Touchscreen: always reports core events (II) XINPUT: Adding extended input device Nextwindow Fermi Touchscreen (type: TOUCHSCREEN) (II) Nextwindow Fermi Touchscreen: On. (II) config/udev: Adding input device Nextwindow Fermi Touchscreen (/dev/input/js0) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device Nextwindow Fermi Touchscreen (/dev/input/mouse3) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/event2) (**) Macintosh mouse button emulation: Applying InputClass evdev pointer catchall (**) Macintosh mouse button emulation: always reports core events (**) Macintosh mouse button emulation: Device: /dev/input/event2 (II) Macintosh mouse button emulation: Found 3 mouse buttons (II) Macintosh mouse button emulation: Found relative axes (II) Macintosh mouse button emulation: Found x and y relative axes (II) Macintosh mouse button emulation: Configuring as mouse (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5 (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device Macintosh mouse button emulation (type: MOUSE) (II) Macintosh mouse button emulation: initialized for relative axes. (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/event9) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/mouse2) (II) No input driver/identifier specified (ignoring) but nothing seems to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver -- 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
I had this problem, trying to boot Ubuntu 10.04 from a mirrored GPT system, failed until I moved var back to the / partition. Then it worked fine. -- ureadahead requires /var on root filesystem https://bugs.launchpad.net/bugs/523484 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 586611] Re: loggerhead needs a hard dependency on simplejson
Installing python-simplejson fixed this error for me. -- loggerhead needs a hard dependency on simplejson https://bugs.launchpad.net/bugs/586611 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 563191] Re: xorg starts in failsafe mode repeatedly with nouveau
I'm now getting this on a non-Nvidia machine: r...@clientdisplay0018:~# lspci 00:00.0 Host bridge: Intel Corporation 82G35 Express DRAM Controller (rev 03) 00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03) After install from ISO it works fine, but after an apt-get update; apt- get dist-upgrade it stops working and goes into failsafe mode. So far the only way I've found to restore it is to reinstall from the CD and try again. -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] [NEW] xorg starts in failsafe mode repeatedly with nouveau
Public bug reported: Binary package hint: xserver-xorg-video-nouveau My beta 2 install of 10.04 won't do anything but boot into failsafe mode. However, it appears, based on the logs I see in /var/log/Xorg*, that it's not even trying anymore to use nouveau. I tried deleting xorg.conf.failsafe, but it recreates it. Strangely enough, it worked correctly after installing from the CD; but once I updated using apt-get dist-upgrade it no longer will start. There are no obvious errors in Xorg.failsafe.log. All the options provided on the screen seem to do nothing much useful; even telling it to continue in low graphics mode just results in a login prompt. My controller is a: 03:00.0 VGA compatible controller: nVidia Corporation ION VGA (rev b1) could that be related? ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] Re: xorg starts in failsafe mode repeatedly with nouveau
** Attachment added: kernel message log http://launchpadlibrarian.net/44168503/messages -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] Re: xorg starts in failsafe mode repeatedly with nouveau
Here is the failsafe log, but it is probably not very helpful; X doesn't even seem to really try to use nouveau anymore, and there's no Xorg.conf to edit. ** Attachment added: Failsafe log http://launchpadlibrarian.net/44168828/Xorg.failsafe.log -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] Re: xorg starts in failsafe mode repeatedly with nouveau
Removing quiet splash from grub's defaults didn't change this either. -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/44174848/CurrentDmesg.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] Re: xorg starts in failsafe mode repeatedly with nouveau
apport information ** Tags added: apport-collected ** Description changed: Binary package hint: xserver-xorg-video-nouveau My beta 2 install of 10.04 won't do anything but boot into failsafe mode. However, it appears, based on the logs I see in /var/log/Xorg*, that it's not even trying anymore to use nouveau. I tried deleting xorg.conf.failsafe, but it recreates it. Strangely enough, it worked correctly after installing from the CD; but once I updated using apt-get dist-upgrade it no longer will start. There are no obvious errors in Xorg.failsafe.log. All the options provided on the screen seem to do nothing much useful; even telling it to continue in low graphics mode just results in a login prompt. My controller is a: 03:00.0 VGA compatible controller: nVidia Corporation ION VGA (rev b1) could that be related? + --- + Architecture: amd64 + DistroRelease: Ubuntu 10.04 + DkmsStatus: Error: [Errno 2] No such file or directory + GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory + InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100406.1) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu5 + PackageArchitecture: amd64 + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=UUID=78609849-12fc-42ae-b95e-d5f1e6dd28cb ro + ProcEnviron: + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2 + Tags: lucid lucid + Uname: Linux 2.6.32-20-generic x86_64 + UserGroups: + + XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' + dmi.bios.date: 05/08/2009 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 080015 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: To be filled by O.E.M. + dmi.board.vendor: To be filled by O.E.M. + dmi.board.version: To be filled by O.E.M. + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.name: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. + glxinfo: Error: [Errno 2] No such file or directory + system: + distro: Ubuntu + codename: lucid + architecture: x86_64 + kernel: 2.6.32-20-generic ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/44174847/BootDmesg.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] Dependencies.txt
apport information ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/44174849/Dependencies.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] GdmLog.txt
apport information ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/44174850/GdmLog.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] GdmLog1.txt
apport information ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/44174852/GdmLog1.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/44174853/Lspci.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] Lsusb.txt
apport information ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/44174857/Lsusb.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] PciDisplay.txt
apport information ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/44174861/PciDisplay.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/44174863/ProcCpuinfo.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/44174864/ProcInterrupts.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] ProcModules.txt
apport information ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/44174867/ProcModules.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] UdevDb.txt
apport information ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/44174869/UdevDb.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/44174868/RelatedPackageVersions.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] UdevLog.txt
apport information ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/44174949/UdevLog.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] Xrandr.txt
apport information ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/44174987/Xrandr.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] setxkbmap.txt
apport information ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/44174992/setxkbmap.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/44175001/xdpyinfo.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 563191] xkbcomp.txt
apport information ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/44175038/xkbcomp.txt -- xorg starts in failsafe mode repeatedly with nouveau https://bugs.launchpad.net/bugs/563191 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 484677] Re: init: ureadahead-other main process terminated with status 4
I'm seeing this on an Atom 330 processor on an 10.04 upgrade. It stops at the ureadahead line and doesn't continue any further. I will boot a rescue CD and look at /etc/fstab for ideas. -- init: ureadahead-other main process terminated with status 4 https://bugs.launchpad.net/bugs/484677 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 484677] Re: init: ureadahead-other main process terminated with status 4
Ah, my actual problem was caused by bad /etc/fstab entries referring to disks that were not attached; after commenting them out it boots correctly. -- init: ureadahead-other main process terminated with status 4 https://bugs.launchpad.net/bugs/484677 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 226185] Re: update-resolv-conf script does not restore old values
This bug is happening to me on Hardy Heron. I'm using OpenVPN and I need to add a search domain and a dns server line so that the internal VPN hosts will resolve correcty, but when the VPN disconnects the internal nameservers are left in /etc/resolv.con and not refreshed. I'm using wicd instead of Network Manager because Network Manager doesn't remember the wireless settings after reboot. As it is, the system would require a manual interface restart to get the original DHCP information back after the OpenVPN tunnel is taken down. I'm working on how to do this automatically. -- update-resolv-conf script does not restore old values https://bugs.launchpad.net/bugs/226185 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 226185] Re: update-resolv-conf script does not restore old values
Weird. I'm actually getting a different issue now after a reboot cleared things out - the original DHCP hostname and DNS address are staying in resolv.conf, and the new server line is being added. After the OpenVPN tunnel goes down, the VPN server stays in resolv.conf. -- update-resolv-conf script does not restore old values https://bugs.launchpad.net/bugs/226185 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 226185] Re: update-resolv-conf script does not restore old values
This bug is happening to me on Hardy Heron. I'm using OpenVPN and I need to add a search domain and a dns server line so that the internal VPN hosts will resolve correcty, but when the VPN disconnects the internal nameservers are left in /etc/resolv.con and not refreshed. I'm using wicd instead of Network Manager because Network Manager doesn't remember the wireless settings after reboot. As it is, the system would require a manual interface restart to get the original DHCP information back after the OpenVPN tunnel is taken down. I'm working on how to do this automatically. -- update-resolv-conf script does not restore old values https://bugs.launchpad.net/bugs/226185 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 226185] Re: update-resolv-conf script does not restore old values
Weird. I'm actually getting a different issue now after a reboot cleared things out - the original DHCP hostname and DNS address are staying in resolv.conf, and the new server line is being added. After the OpenVPN tunnel goes down, the VPN server stays in resolv.conf. -- update-resolv-conf script does not restore old values https://bugs.launchpad.net/bugs/226185 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 226185] Re: update-resolv-conf script does not restore old values
With wicd this is working correctly, as long as I don't tell OpenVPN to drop privileges to nobody/nogroup (because then running the downscript will fail!). I recommend changing update-resolv-conf's header to mention this gotcha, as such: # Parses DHCP options from openvpn to update resolv.conf # To use set as 'up' and 'down' script in your openvpn *.conf: # up /etc/openvpn/update-resolv-conf # down /etc/openvpn/update-resolv-conf # # You must have resolvconf installed, and OpenVPN will need to run as root to # allow the down script to work; the up script will always run as root # # Used snippets of resolvconf script by Thomas Hood [EMAIL PROTECTED] # and Chris Hanson # Licensed under the GNU GPL. See /usr/share/common-licenses/GPL. -- update-resolv-conf script does not restore old values https://bugs.launchpad.net/bugs/226185 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 184960] Re: Using suspend key results in suspend loop
This CD did suspend, but never recovered. I was not able to get back into the system after suspending without completely powering off. -- Using suspend key results in suspend loop https://bugs.launchpad.net/bugs/184960 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 32752] Re: Dell PERC 2/SC (AMI Megaraid 466(?)) not working
I had a similar issue with 7.10 (installed correctly, wouldn't boot) until I followed RedHat's recommendation and turned off I2O emulation: http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/release- notes/RELEASE-NOTES-x86-en.html -- Dell PERC 2/SC (AMI Megaraid 466(?)) not working https://bugs.launchpad.net/bugs/32752 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 184960] Re: Using suspend key results in suspend loop
Look at Jan 15 15:05:11 and environs: messages.2.gz:Jan 15 15:04:26 tdickson-PC gnome-power-manager: (tdickson) Suspending computer because the suspend button has been pressed messages.2.gz:Jan 15 15:05:11 tdickson-PC gnome-power-manager: (tdickson) Resuming computer messages.2.gz:Jan 15 15:04:48 tdickson-PC gnome-power-manager: (tdickson) Suspending computer because the suspend button has been pressed messages.2.gz:Jan 15 15:05:26 tdickson-PC gnome-power-manager: (tdickson) Resuming computer messages.2.gz:Jan 15 15:05:32 tdickson-PC gnome-power-manager: (tdickson) Suspending computer because the suspend button has been pressed messages.2.gz:Jan 15 15:05:59 tdickson-PC gnome-power-manager: (tdickson) Resuming computer messages.2.gz:Jan 15 15:06:05 tdickson-PC gnome-power-manager: (tdickson) Suspending computer because the suspend button has been pressed ** Attachment added: Messages file containing the issue http://launchpadlibrarian.net/11468368/messages.2.gz -- Using suspend key results in suspend loop https://bugs.launchpad.net/bugs/184960 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 184960] Using suspend key results in suspend loop
Public bug reported: Binary package hint: gnome-power-manager If I suspend Ubuntu 7.10 on 2.6.22-14-generic, when it resumes from suspend, I have about enough time to login before it suspends again. It continues this loop and I have to power cycle the machine to recover (losing anything that was unsaved when it suspended). I will attach dmesg and lspci output along with the pertinant part of the messages file. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- Using suspend key results in suspend loop https://bugs.launchpad.net/bugs/184960 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 184960] Re: Using suspend key results in suspend loop
Here is the lspci -v -v -n -n output. ** Attachment added: lspci -v -v -n -n http://launchpadlibrarian.net/11468417/lspci-vvnn.log -- Using suspend key results in suspend loop https://bugs.launchpad.net/bugs/184960 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 184960] Re: Using suspend key results in suspend loop
Linux tdickson-desktop 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux I don't have a current dmesg output (I'd need to reboot). -- Using suspend key results in suspend loop https://bugs.launchpad.net/bugs/184960 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 184960] Re: Using suspend key results in suspend loop
This machine is an HP Pavilion Elite -- Using suspend key results in suspend loop https://bugs.launchpad.net/bugs/184960 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
