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 SIGS
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 a
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
** 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.launchpa
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 &
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 sambashar
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
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.lau
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
