[Bug 361689] Re: hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices
So... may I suggest the new hald build be uploaded to the jaunty repository? I've spent the last 3 hours debugging what seemed to be a DBus problem, but turned out to be this. Then I needed to pull the fix from karmic because the fix is not available in the jaunty repo. -- hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices https://bugs.launchpad.net/bugs/361689 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 377474] [NEW] bridge-utils ifupdown script should disable IPv6 address autoconfiguration for underlying interface
Public bug reported: Binary package hint: bridge-utils When an interface is configured for bridging in /etc/network/interfaces, the ifup script should disable IPv6 address autoconfiguration on the underlying physical interface. If this is not done, the interface will autoconfigure the same IPv6 address as the bridge to which it is assigned, resulting in two seperate routes for the same subnet. This results in intermittent connectivity, depending on which route is selected, as only the route through the bridge interface will work. I've fixed this for my machine by adding the following to /etc/sysctl.conf: net.ipv6.conf.eth1.accept_ra = 0 See further information on this issue in the following blog post: http://automatthias.wordpress.com/2008/11/16/bridge-and-ipv6-autoconfiguration/ I'm running a fully updated hardy as of 17/05/2009. ** Affects: bridge-utils (Ubuntu) Importance: Undecided Status: New ** Tags: bridge bridge-utils ipv6 route routing -- bridge-utils ifupdown script should disable IPv6 address autoconfiguration for underlying interface https://bugs.launchpad.net/bugs/377474 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 298857] Re: Provide ease-of-use on larger networks
NetworkManager does not yet support IPv6. I added the gnome bugtracker bug calling for IPv6 support in general to this report. While that bug does not specifically deal with DHCPv6, it is a prerequisite for it, and presumably DHCPv6 support will be added when IPv6 support is finalised. Also, this is not only for larger networks. I run IPv6 on my small local network, and I would like to be able to do DDNS to automatically register IPv6 addresses in DNS like I do for IPv4. It would have to be something that "just works" however, as I don't want to force friends who come over to install extra software on their machines just to get IPv6 connectivity. It would definately be good if ubuntu could finally claim to be fully IPv6-compliant out-of-the-box. It's kind of embarrasing that windows has the edge here. -- Provide ease-of-use on larger networks https://bugs.launchpad.net/bugs/298857 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 298857] Re: Provide ease-of-use on larger networks
** Bug watch added: GNOME Bug Tracker #556915 http://bugzilla.gnome.org/show_bug.cgi?id=556915 ** Also affects: network-manager via http://bugzilla.gnome.org/show_bug.cgi?id=556915 Importance: Unknown Status: Unknown -- Provide ease-of-use on larger networks https://bugs.launchpad.net/bugs/298857 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 366179] Re: Regression: Kernel Panic with bond0 & br0
I am seeing the same problem bridging the e1000e ethernet and IWL4965AGN wireless cards on my laptop. This forces me to use NetworkManager, a very suboptimal solution. For me this is an important issue. I am running jaunty, fully updated as of 12/may 2009. -- Regression: Kernel Panic with bond0 & br0 https://bugs.launchpad.net/bugs/366179 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 366179] apport-collect data
Architecture: amd64 Dependencies: DistroRelease: Ubuntu 9.04 Package: linux None [modified: /var/lib/dpkg/info/linux.list] PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash LANG=en_AU.UTF-8 Uname: Linux 2.6.28-11-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- Regression: Kernel Panic with bond0 & br0 https://bugs.launchpad.net/bugs/366179 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 274409] Re: wget should prefer IPv6 over IPv4
Confirmed in jaunty, the default is still to prefer A records. ** Changed in: wget (Ubuntu) Status: New => Confirmed -- wget should prefer IPv6 over IPv4 https://bugs.launchpad.net/bugs/274409 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 215497] Re: "disable networking" leaves ipv6 enabled
Confirmed in jaunty. This issue makes networkmanager unusable for IPv6 for me. It will set up subnet and default routes on the wired interface, and continue sending packets there even after the cable is unplugged. ** Tags added: jaunty -- "disable networking" leaves ipv6 enabled https://bugs.launchpad.net/bugs/215497 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 268708] [NEW] stunnel4 logrotate script resets connections
Public bug reported: Binary package hint: stunnel4 The script /etc/logrotate.d/stunnel4 is set to rotate stunnel's log files daily. The method used is a hard restart of the stunnel daemon, from reading the init script because stunnel does not offer any way of gracefully reloading. Also according to the init script the problem was reported upstream. Since it's still not fixed I suggest the default settings for stunnel are changed to rotate weekly or monthly as resetting all connections at 6AM every morning gets very annoying. ** Affects: stunnel4 (Ubuntu) Importance: Undecided Status: New -- stunnel4 logrotate script resets connections https://bugs.launchpad.net/bugs/268708 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
