Your message dated Sat, 16 Aug 2014 21:56:10 +0200 with message-id <20140816195610.gs8...@gnuservers.com.ar> and subject line Re: plasma-widget-networkmanagement: WLAN connection not re-established after resume when using systemd has caused the Debian Bug report #737504, regarding plasma-widget-networkmanagement: WLAN connection not re-established after resume when using systemd 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 ow...@bugs.debian.org immediately.) -- 737504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: plasma-widget-networkmanagement Version: 0.9.0.9-1 Severity: normal Dear Maintainer, when I use systemd as my init system, the Network Manager Applet fails to re-establish the WLAN connection when coming back from suspend to RAM. Steps to reproduce: * Connect to some wireless network * Suspend to RAM * Resume Expected Behaviour: It should ask for the password in order to re-connect to the wireless. Actual Behaviour: It just pretends the connection was still available. This may work out if the machine was suspended for a very short time only and not moved, but if I moved to another room where another AP serves the same SSID, or if the machine was suspended for more than just a few minutes, I have to manually disconnetc and reconnect to the wireless network. I do not know which part of the stack is responsible for this re-connection on resume, hence I reported this in the user-facing component. Kind regards Ralf -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-widget-networkmanagement depends on: ii kde-runtime 4:4.11.3-1 ii libc6 2.17-97 ii libgcc1 1:4.8.2-14 ii libkcmutils4 4:4.11.3-2 ii libkdecore5 4:4.11.3-2 ii libkdeui5 4:4.11.3-2 ii libkio5 4:4.11.3-2 ii libknotifyconfig4 4:4.11.3-2 ii libopenconnect2 5.02-1 ii libplasma3 4:4.11.3-2 ii libqt4-dbus 4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-network 4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-svg 4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-xml 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtcore4 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtgui4 4:4.8.5+git209-g718fae5+dfsg-1 ii libsolid4 4:4.11.3-2 ii libstdc++6 4.8.2-14 ii mobile-broadband-provider-info 20130915-1 ii network-manager 0.9.8.0-5 Versions of packages plasma-widget-networkmanagement recommends: ii kwalletmanager 4:4.11.3-1 ii network-manager-openvpn 0.9.8.4-1 ii network-manager-pptp 0.9.8.4-1 ii network-manager-vpnc 0.9.8.6-1 Versions of packages plasma-widget-networkmanagement suggests: ii kde-workspace-bin 4:4.11.3-3 ii network-manager-openconnect 0.9.8.4-1 -- no debconf information
--- End Message ---
--- Begin Message ---Hi, This problem was a network-manager issue, I think that the latest related issue was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744824 fixed in 0.9.8.8-6. Happy hacking, -- : You are in a dark room with a compiler, emacs, an internet connection, : and a thermos of coffee. : Your move ? Saludos /\/\ /\ >< `/
Description: Digital signature
--- End Message ---