Your message dated Thu, 25 Oct 2018 08:16:45 +0200
with message-id <[email protected]>
and subject line Re: network-manager: fails to re-establish system connections
after using physical RF KILL switch
has caused the Debian Bug report #596380,
regarding network-manager: fails to re-establish system connections after using
physical RF KILL switch
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.)
--
596380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596380
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.8.1-2+b1
Severity: normal
Some laptops, like my Lenovo, have a physical RF kill switch. It is a nice
feature
on a plane etc, but network-manager cannot handle its use.
If I switch off the wireless from the physical switch, and then back on, nm is
sometimes
unable to re-establish the (system) connection. It does not happen on each
switch, but
once it happens, it keeps on happening until nm is restarted.
All I get is two lines in syslog:
NetworkManager[24082]: <info> (wlan0): supplicant interface state: starting ->
ready
NetworkManager[24082]: <info> (wlan0): device state change: 2 -> 3 (reason 42)
Restarting network-manager solves the problem, but that is ridiculous since
the whole point of using nm in the first place is to remove the necessity to
have
root access to reconfigure networks. (This particular connection needs to be
system
connection, though.)
Cheers,
Juha
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages network-manager depends on:
ii adduser 3.112 add and remove users and groups
ii dbus 1.2.24-3 simple interprocess messaging syst
ii isc-dhcp-client 4.1.1-P1-9 ISC DHCP client
ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst
ii libdbus-glib-1-2 0.88-2 simple interprocess messaging syst
ii libgcrypt11 1.4.5-2 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.24.1-1 The GLib library of C routines
ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr
ii libgudev-1.0-0 161-1 GObject-based wrapper library for
ii libnl1 1.1-5 library for dealing with netlink s
ii libnm-glib2 0.8.1-2+b1 network management framework (GLib
ii libnm-util1 0.8.1-2+b1 network management framework (shar
ii libpolkit-gobject-1-0 0.96-2 PolicyKit Authorization API
ii libuuid1 2.17.2-3.1 Universally Unique ID library
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
ii udev 161-1 /dev/ and hotplug management daemo
ii wpasupplicant 0.6.10-2 client support for WPA and WPA2 (I
Versions of packages network-manager recommends:
ii dns 2.55-1 A small caching DNS proxy and DHCP
ii ipt 1.4.9-1 administration tools for packet fi
ii mod 0.4+git.20100624t180933.6e79d15-1+b1 D-Bus service for managing modems
ii net 0.8.1-1 network management framework (GNOM
ii net 1:0.9~svn1141976-1 KDE system tray applet for control
ii pol 0.96-2 framework for managing administrat
ii ppp 2.4.5-4 Point-to-Point Protocol (PPP) - da
Versions of packages network-manager suggests:
pn avahi-autoipd <none> (no description available)
-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
/etc/NetworkManager/dispatcher.d/01ifupdown changed:
if [ -z "$1" ]; then
echo "$0: called with no interface" 1>&2
exit 1;
fi
export IFACE="$1"
export LOGICAL="$1"
export ADDRFAM="NetworkManager"
export METHOD="NetworkManager"
export VERBOSITY="0"
case "$2" in
up)
export MODE="start"
export PHASE="post-up"
exec run-parts /etc/network/if-up.d
;;
down)
export MODE="stop"
export PHASE="pre-down"
exec run-parts /etc/network/if-down.d
;;
pre-up)
export MODE="start"
export PHASE="pre-up"
exec run-parts /etc/network/if-pre-up.d
;;
post-down)
export MODE="stop"
export PHASE="post-down"
exec run-parts /etc/network/if-post-down.d
;;
vpn-up)
echo 'VPN - Doing nothing'
;;
*)
echo "$0: called with unknown action \`$2'" 1>&2
exit 1
;;
esac
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 10 Sep 2010 21:36:23 +0100 =?utf-8?b?SnVoYSBKw6R5a2vDpA==?=
<[email protected]> wrote:
> Package: network-manager
> Version: 0.8.1-2+b1
> Severity: normal
>
>
> Some laptops, like my Lenovo, have a physical RF kill switch. It is a nice
> feature
> on a plane etc, but network-manager cannot handle its use.
>
> If I switch off the wireless from the physical switch, and then back on, nm
> is sometimes
> unable to re-establish the (system) connection. It does not happen on each
> switch, but
> once it happens, it keeps on happening until nm is restarted.
>
> All I get is two lines in syslog:
>
> NetworkManager[24082]: <info> (wlan0): supplicant interface state: starting
> -> ready
> NetworkManager[24082]: <info> (wlan0): device state change: 2 -> 3 (reason 42)
>
> Restarting network-manager solves the problem, but that is ridiculous since
> the whole point of using nm in the first place is to remove the necessity to
> have
> root access to reconfigure networks. (This particular connection needs to be
> system
> connection, though.)
If the driver/hardware uses the rfkill framework provided by the kernel,
NM should work as expected and notice rfkill changes.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
