Package: network-manager Version: 1.0.2-2 Severity: normal Dear Maintainer,
I have network-manager installed. My box has one wired network connection that has static address in /etc/network/interfaces and to my understanding it is not managed by network-manager but instead ifupdown-scripts or something that is run from init-scripts. My /etc/NetworkManager/NetworkManager.conf looks like [main] plugins=ifupdown,keyfile [ifupdown] managed=false after todays upgrade 1.0.0-5 -> 1.0.2-2 some gnome-related programs (evolution, in particular) started to report that the network of the machine is in "offline state" and refused to do anything over network. In practice this renders evolution useless. In /var/log/messages there is lines that might be related: May 12 21:31:41 fisuvaan gnome-session[5987]: Gjs-Message: JS LOG: Removing a network device that was not added ... May 13 22:21:54 fisuvaan gnome-session[7809]: (gnome-shell:7895): libnm-glib-WARNING **: Device activation failed: (4) Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. and in /var/log/daemon.log it is said: May 13 22:34:09 fisuvaan NetworkManager[1361]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so May 13 22:34:09 fisuvaan systemd[1]: Started Enable support for additional executable binary formats. May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so May 13 22:34:10 fisuvaan speech-dispatcher[1867]: Starting Speech Dispatcher: speech-dispatcher[Wed May 13 22:34:10 2015 : 199020] speechd: Speech Dispatcher 0.8 starting May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> WiFi enabled by radio killswitch; enabled by state file May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> WWAN enabled by radio killswitch; enabled by state file May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> WiMAX enabled by radio killswitch; enabled by state file May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> Networking is enabled by state file May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> (lo): link connected May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> (lo): carrier is ON May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1) May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0 May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> (eth2): link connected May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> (eth2): carrier is ON May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> (eth2): new Ethernet device (driver: 'r8169' ifindex: 2) May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> (eth2): exported as /org/freedesktop/NetworkManager/Devices/1 May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> startup complete May 13 22:34:10 fisuvaan NetworkManager[1361]: <info> NetworkManager state is now CONNECTED_GLOBAL ... May 13 22:34:15 fisuvaan NetworkManager[1361]: <info> ModemManager disappeared from bus May 13 22:34:15 fisuvaan systemd[1]: Started Modem Manager. May 13 22:34:15 fisuvaan NetworkManager[1361]: <info> ModemManager available in the bus Problem was "fixed" by saying # /etc/init.d/network-manager stop # update-rc.d network-manager remove but I suspect there are debian users who don't know how to do that and instead seek problems inside evolution or other affected program. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser 3.113+nmu3 ii dbus 1.8.16-1 ii init-system-helpers 1.23 ii isc-dhcp-client 4.3.1-6 ii libbluetooth3 5.23-2+b1 ii libc6 2.19-18 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt20 1.6.3-2 ii libglib2.0-0 2.44.0-2 ii libgnutls-deb0-28 3.3.15-2 ii libgudev-1.0-0 215-17 ii libmm-glib0 1.4.0-1 ii libndp0 1.4-2 ii libnewt0.52 0.52.17-1+b1 ii libnl-3-200 3.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm0 1.0.2-2 ii libpam-systemd 215-17 ii libpolkit-agent-1-0 0.105-8 ii libpolkit-gobject-1-0 0.105-8 ii libreadline6 6.3-8+b3 ii libsoup2.4-1 2.48.0-1 ii libsystemd0 215-17 ii libteamdctl0 1.17-1 ii libuuid1 2.25.2-6 ii lsb-base 4.1+Debian13+nmu1 ii policykit-1 0.105-8 ii udev 215-17 ii wpasupplicant 2.3-2 Versions of packages network-manager recommends: ii crda 3.13-1 ii dnsmasq-base 2.72-3.1 ii iptables 1.4.21-2+b1 ii iputils-arping 3:20121221-5+b2 ii modemmanager 1.4.0-1 ii ppp 2.4.6-3.1 Versions of packages network-manager suggests: pn avahi-autoipd <none> pn libteam-utils <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
