This bug was fixed in the package network-manager -
0.7~~svn20080928t225540+eni0-0ubuntu2
---------------
network-manager (0.7~~svn20080928t225540+eni0-0ubuntu2) intrepid; urgency=low
[ Alexander Sack <[EMAIL PROTECTED]> ]
* remove patches forwarded/applied upstream
- delete debian/patches/80_lp259503_access_to_freed_device_struct.patch
- delete debian/patches/honour_resolvconf_exitcode.patch
- delete debian/patches/lp269010_keyfile_secrets_crash.patch
- update debian/patches/series
* LP: #276253 - NM 0.7 sets hostname to localhost.localdomain instead of
what is in /etc/hostname - we fallback to hostname configured in
/etc/hostname even when no distro specific system plugin is enabled; we
do this for all cases until a proper solution was found.
- add debian/patches/fix_system_hostname.patch
- update debian/patches/series
[ Matt Zimmerman <[EMAIL PROTECTED]> ]
* (apport hook) Use [].append rather than the += operator, to avoid things
like: "InterestingModules: b 4 4" (should be b44)
- update debian/source_network-manager.py
-- Alexander Sack <[EMAIL PROTECTED]> Thu, 02 Oct 2008 20:37:20 +0200
** Changed in: network-manager (Ubuntu Intrepid)
Status: Fix Committed => Fix Released
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
https://bugs.launchpad.net/bugs/276253
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
