Bugzilla – Bug 561095
knetworkmanager no longer in startup after toggling from traditional method with ifup
Last modified: 2011-12-08 18:51:37 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.260.0 Safari/532.5 As knetworkmanager was not obeying the default connection and always using system connection, I thought of switching to traditional method from yast. After some days I switched back to knetworkmanager but it doesn't start in startup. I always have to start manually. Reproducible: Always Steps to Reproduce: 1. Open yast network management. 2. Switch to traditional method. 3. Save. 4. Switch back to knetworkmanager. Actual Results: knetworkmanager doesn't start in startup. Expected Results: knetworkmanager should start automatically on change.
The situation has worsen now. After trying above steps, it gives error that no network is running. knetworkmanager is rendered useless now. It doesn't detect any network. I verified that NetworkManager is running. It shows following in NetworkManger log. Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> starting... Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> Trying to start the modem-manager... Apr 18 10:40:19 Ruchir-Linux NetworkManager: Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list. Apr 18 10:40:19 Ruchir-Linux NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> Found wlan radio killswitch rfkill0 (at /sys/devices/platform/dell-laptop/rfkill/rfkill0) (driver dell-laptop) Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> WiFi disabled by radio killswitch; disabled by state file Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> WWAN enabled by radio killswitch; enabled by state file Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> Setting system hostname to 'Ruchir-Linux.site' (from system configuration) Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> (eth1): driver supports SSID scans (scan_capa 0x01). Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> (eth1): new 802.11 WiFi device (driver: 'wl') Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/0 Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> (eth0): carrier is OFF Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> (eth0): new Ethernet device (driver: 'r8169') Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> modem-manager is now available Apr 18 10:40:19 Ruchir-Linux NetworkManager: <WARN> default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> Trying to start the supplicant... Apr 18 10:40:19 Ruchir-Linux nm-dispatcher.action: nm_dispatcher_action: Invalid connection: '(null)' / 'connection setting not found' invalid: 1 Apr 18 10:40:19 Ruchir-Linux NetworkManager: <info> (eth1): supplicant manager state: down -> idle Apr 18 10:40:19 Ruchir-Linux nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/netcontrol_services' exited with error status 127.
- konfirm: even putting knetworkmanager in autostart doesn't work - starting knetworkmanager per mouse click from menu/icon does work
Possible dupe 595432 with troubleshooting
Same problem under openSUSE 11.3.
seems a dup of bug 595432 In case it is not: knetworkmanager is unmaintained and will not receive any non-security updates anymore. You can update your KDE and use plasmoid-networkmanagement. *** This bug has been marked as a duplicate of bug 595432 ***