Your message dated Tue, 09 Feb 2010 23:27:27 +0100 with message-id <1265754447.17045.14.ca...@mattotaupa> and subject line Re: network-manager-gnome: Does not reconnect on resume after suspend. has caused the Debian Bug report #567217, regarding network-manager-gnome: Does not reconnect on resume after suspend. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 567217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567217 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Subject: network-manager-gnome: Does not reconnect after suspend. Package: network-manager-gnome Version: 0.7.999-2 Severity: normal *** Please type your report below this line *** Dear Debian folks, today I upgraded NetworkManager. It went in two phases. 1. In the morning. $ sudo aptitude safe-upgrade […] $ more /var/log/aptitude […] [AKTUALISIERUNG] libnm-util-dev 0.7.2-2 -> 0.7.999-2 [AKTUALISIERUNG] libnm-util1 0.7.2-2 -> 0.7.999-2 [AKTUALISIERUNG] libsoup-gnome2.4-1 2.29.5-2 -> 2.29.6-1 [AKTUALISIERUNG] libsoup-gnome2.4-dev 2.29.5-2 -> 2.29.6-1 [AKTUALISIERUNG] libsoup2.4-1 2.29.5-2 -> 2.29.6-1 [AKTUALISIERUNG] libsoup2.4-dev 2.29.5-2 -> 2.29.6-1 [AKTUALISIERUNG] network-manager 0.7.2-2 -> 0.7.999-2 [AKTUALISIERUNG] network-manager-dev 0.7.2-2 -> 0.7.999-2 […] Afterward my network was deactivated in the applet. Doing a left click and choosing »ifupdown (eth0)« activated it again. 2. In the evening. […] [AKTUALISIERUNG] network-manager-gnome 0.7.2-2 -> 0.7.999-2 […] I had not problem doing this and it stayed connected. But now I noticed that after a suspend/resume the network kept deactivated. $ more /var/log/daemon.log […] Jan 28 01:19:59 name NetworkManager: <info> Sleeping... Jan 28 01:19:59 name NetworkManager: <info> (eth0): now unmanaged Jan 28 01:19:59 name NetworkManager: <info> (eth0): device state change: 8 -> 1 (reason 37) Jan 28 01:19:59 name NetworkManager: <info> (eth0): deactivating device (reason: 37). Jan 28 01:19:59 name NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 12270 Jan 28 01:19:59 name dnsmasq[1978]: reading /etc/resolv.conf Jan 28 01:19:59 name dnsmasq[1978]: using nameserver x.x.x.y#53 Jan 28 01:19:59 name NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess Jan 28 01:19:59 name avahi-daemon[1967]: Withdrawing address record for x.x.x.x on eth0. Jan 28 01:19:59 name avahi-daemon[1967]: Leaving mDNS multicast group on interface eth0.IPv4 with address x.x.x.x. Jan 28 01:19:59 name avahi-daemon[1967]: Interface eth0.IPv4 no longer relevant for mDNS. Jan 28 01:19:59 name NetworkManager: <info> (eth0): cleaning up... Jan 28 01:19:59 name NetworkManager: <info> (eth0): taking down device. Jan 28 01:19:59 name avahi-daemon[1967]: Interface eth0.IPv6 no longer relevant for mDNS. Jan 28 01:19:59 name avahi-daemon[1967]: Leaving mDNS multicast group on interface eth0.IPv6 with address abcd::abc:abcd:abcd:abcd. Jan 28 01:19:59 name avahi-daemon[1967]: Withdrawing address record for abcd::abc:abcd:abcd:abcd on eth0. Jan 28 01:19:59 name dhclient: receive_packet failed on eth0: Network is down Jan 28 01:19:59 name NetworkManager: <info> (eth0): carrier now OFF (device state 1) Jan 28 01:20:20 name acpid: client 28913[0:0] has disconnected Jan 28 01:20:20 name acpid: client connected from 28913[0:0] Jan 28 01:20:20 name acpid: 1 client rule loaded Jan 28 01:20:20 name NetworkManager: <info> Waking up... Jan 28 01:20:20 name NetworkManager: <info> (eth0): now managed Jan 28 01:20:20 name NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2) Jan 28 01:20:20 name NetworkManager: <info> (eth0): bringing up device. Jan 28 01:20:20 name dnsmasq[1978]: no servers found in /etc/resolv.conf, will retry Jan 28 01:20:20 name NetworkManager: <info> (eth0): preparing device. Jan 28 01:20:20 name NetworkManager: <info> (eth0): deactivating device (reason: 2). Jan 28 01:20:20 name NetworkManager: <info> (eth0): carrier now ON (device state 2) Jan 28 01:20:20 name NetworkManager: <info> (eth0): device state change: 2 -> 3 (reason 40) Doing `sudo invoke-rc.d network-manager` does *not* let me reproduce this, i. e. the applet goes away but I am still connected to the network. I am able reproduce this on two machines. Just to mention it, before the upgrade the system connected just fine after every resume from suspend. Thanks, Paul -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager-gnome depends on: ii dbus-x11 1.2.16-2 simple interprocess messaging syst ii gconf2 2.28.0-1 GNOME configuration database syste ii gnome-icon-theme 2.28.0-1 GNOME Desktop icon theme ii libatk1.0-0 1.28.0-1 The ATK accessibility toolkit ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst ii libdbus-glib-1-2 0.82-2 simple interprocess messaging syst ii libfontconfig1 2.8.0-2 generic font configuration library ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib ii libgconf2-4 2.28.0-1 GNOME configuration database syste ii libglade2-0 1:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.22.4-1 The GLib library of C routines ii libgnome-bluetooth7 2.28.6-2 GNOME Bluetooth tools - support li ii libgnome-keyring0 2.28.2-1 GNOME keyring services library ii libgtk2.0-0 2.18.6-1 The GTK+ graphical user interface ii libnm-glib-vpn1 0.7.999-2 network management framework (GLib ii libnm-glib2 0.7.999-2 network management framework (GLib ii libnm-util1 0.7.999-2 network management framework (shar ii libnotify1 [libnotify1- 0.4.5-1 sends desktop notifications to a n ii libpango1.0-0 1.26.2-1 Layout and rendering of internatio ii libxml2 2.7.6.dfsg-2+b1 GNOME XML library ii network-manager 0.7.999-2 network management framework daemo ii policykit-1-gnome 0.96-1 GNOME authentication agent for Pol ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages network-manager-gnome recommends: ii gnome-bluetooth 2.28.6-2 GNOME Bluetooth tools ii libpam-gnome-keyring [libpam- 2.28.2-1 PAM module to unlock the GNOME key pn mobile-broadband-provider-inf <none> (no description available) ii notification-daemon 0.4.0-2 a daemon that displays passive pop Versions of packages network-manager-gnome suggests: pn network-manager-openvpn-gnome <none> (no description available) pn network-manager-pptp-gnome <none> (no description available) pn network-manager-vpnc-gnome <none> (no description available) -- no debconf information
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
--- End Message ---
--- Begin Message ---reassign 567217 network-manager fixed 567217 0.7.999-3 merge 567217 568784 quit Am Donnerstag, den 28.01.2010, 01:32 +0100 schrieb Paul Menzel: […] > I had not problem doing this and it stayed connected. But now I noticed > that after a suspend/resume the network kept deactivated. > > $ more /var/log/daemon.log > […] > Jan 28 01:19:59 name NetworkManager: <info> Sleeping... > Jan 28 01:19:59 name NetworkManager: <info> (eth0): now unmanaged > Jan 28 01:19:59 name NetworkManager: <info> (eth0): device state > change: 8 -> 1 (reason 37) > Jan 28 01:19:59 name NetworkManager: <info> (eth0): deactivating > device (reason: 37). > Jan 28 01:19:59 name NetworkManager: <info> (eth0): canceled DHCP > transaction, dhcp client pid 12270 > Jan 28 01:19:59 name dnsmasq[1978]: reading /etc/resolv.conf > Jan 28 01:19:59 name dnsmasq[1978]: using nameserver x.x.x.y#53 > Jan 28 01:19:59 name NetworkManager: <WARN> check_one_route(): > (eth0) error -34 returned from rtnl_route_del(): Sucess > Jan 28 01:19:59 name avahi-daemon[1967]: Withdrawing address record > for x.x.x.x on eth0. > Jan 28 01:19:59 name avahi-daemon[1967]: Leaving mDNS multicast group > on interface eth0.IPv4 with address x.x.x.x. > Jan 28 01:19:59 name avahi-daemon[1967]: Interface eth0.IPv4 no > longer relevant for mDNS. > Jan 28 01:19:59 name NetworkManager: <info> (eth0): cleaning up... > Jan 28 01:19:59 name NetworkManager: <info> (eth0): taking down > device. > Jan 28 01:19:59 name avahi-daemon[1967]: Interface eth0.IPv6 no > longer relevant for mDNS. > Jan 28 01:19:59 name avahi-daemon[1967]: Leaving mDNS multicast group > on interface eth0.IPv6 with address abcd::abc:abcd:abcd:abcd. > Jan 28 01:19:59 name avahi-daemon[1967]: Withdrawing address record > for abcd::abc:abcd:abcd:abcd on eth0. > Jan 28 01:19:59 name dhclient: receive_packet failed on eth0: Network > is down > Jan 28 01:19:59 name NetworkManager: <info> (eth0): carrier now OFF > (device state 1) > Jan 28 01:20:20 name acpid: client 28913[0:0] has disconnected > Jan 28 01:20:20 name acpid: client connected from 28913[0:0] > Jan 28 01:20:20 name acpid: 1 client rule loaded > Jan 28 01:20:20 name NetworkManager: <info> Waking up... > Jan 28 01:20:20 name NetworkManager: <info> (eth0): now managed > Jan 28 01:20:20 name NetworkManager: <info> (eth0): device state > change: 1 -> 2 (reason 2) > Jan 28 01:20:20 name NetworkManager: <info> (eth0): bringing up > device. > Jan 28 01:20:20 name dnsmasq[1978]: no servers found in > /etc/resolv.conf, will retry > Jan 28 01:20:20 name NetworkManager: <info> (eth0): preparing device. > Jan 28 01:20:20 name NetworkManager: <info> (eth0): deactivating > device (reason: 2). > Jan 28 01:20:20 name NetworkManager: <info> (eth0): carrier now ON > (device state 2) > Jan 28 01:20:20 name NetworkManager: <info> (eth0): device state > change: 2 -> 3 (reason 40) > > Doing `sudo invoke-rc.d network-manager` does *not* let me reproduce I meant `sudo invoke-rc.d network-manager restart` although `sudo service network-manager restart` seems to be the preferred way. > this, i. e. the applet goes away but I am still connected to the > network. I am able reproduce this on two machines. > > Just to mention it, before the upgrade the system connected just fine > after every resume from suspend. […] Uprading the NetworkManager packages today solved the problem. It seems to be related to this change. * debian/patches/05-ifupdown-allow-hotplug-autoconnect.patch - Set autoconnect=true for devices marked as allow-hotplug in /etc/network/interfaces. (Closes: #568784) Looking at #568784 seems to refer to the same bug and therefore I try to merge both for completeness.
Description: Dies ist ein digital signierter Nachrichtenteil
--- End Message ---
