Your message dated Tue, 26 Sep 2023 23:03:30 +0200
with message-id <3599975.hdfAi7Kttb@treadstone-71>
and subject line
has caused the Debian Bug report #834535,
regarding plasma-nm: isn't able to coexist with wicd-kde
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.)
--
834535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-nm
Version: 0.9.3.4-2
Severity: important
Debian jessie. Simplified bug report.
plasma-nm depends on network-manager, but does not conflict with
wicd-kde, or the other way around. So, one ends up with the two
packages competing/raceing with eachother. Very shaky wireless
authentication process.
Purging both plasma-nm and network-manager and keeping wicd-kde
(0.3.1-1) cleans up the mess. I do prefer using wicd over nm.
Any chance getting things back to order? /var/log/wicd/wicd.log shows
mostly:
2016/08/16 19:02:38 :: attempting to set hostname with dhclient
2016/08/16 19:02:38 :: using dhcpcd or another supported client may work better
2016/08/16 19:02:39 :: attempting to set hostname with dhclient
2016/08/16 19:02:39 :: using dhcpcd or another supported client may work better
2016/08/16 19:03:23 :: setting automatically reconnect when connection drops 1
2016/08/16 19:03:23 :: Setting dhcp client to 0
2016/08/16 19:03:23 :: setting wired interface eth0
2016/08/16 19:03:23 :: setting wireless interface wlan0
2016/08/16 19:03:23 :: setting wpa driver nl80211
2016/08/16 19:03:23 :: setting use global dns to 0
2016/08/16 19:03:23 :: setting backend to external
2016/08/16 19:03:31 :: Invalid network mode string, ignoring!
2016/08/16 19:03:38 :: Connecting to wireless network AP
2016/08/16 19:03:38 :: attempting to set hostname with dhclient
2016/08/16 19:03:38 :: using dhcpcd or another supported client may work better
2016/08/16 19:03:38 :: attempting to set hostname with dhclient
2016/08/16 19:03:38 :: using dhcpcd or another supported client may work better
2016/08/16 19:03:39 :: Putting interface down
2016/08/16 19:03:40 :: Releasing DHCP leases...
2016/08/16 19:03:40 :: attempting to set hostname with dhclient
2016/08/16 19:03:40 :: using dhcpcd or another supported client may work better
2016/08/16 19:03:40 :: Setting false IP...
2016/08/16 19:03:40 :: Stopping wpa_supplicant
2016/08/16 19:03:40 :: Flushing the routing table...
2016/08/16 19:03:40 :: Putting interface up...
2016/08/16 19:03:42 :: Generating psk...
2016/08/16 19:03:42 :: WARNING: PSK generation failed! Falling back to
wireless key.
2016/08/16 19:03:42 :: Please report this error to the wicd developers!
2016/08/16 19:03:42 :: Attempting to authenticate...
2016/08/16 19:04:18 :: wpa_supplicant authentication may have failed.
2016/08/16 19:04:18 :: connect result is failed
2016/08/16 19:04:18 :: exiting connection thread
2016/08/16 19:04:20 :: Sending connection attempt result bad_pass
but sometimes success:
2016/08/16 19:04:20 :: Autoconnecting...
2016/08/16 19:04:20 :: No wired connection present, attempting to autoconnect
to wireless network
2016/08/16 19:04:20 :: trying to automatically connect to...AP
2016/08/16 19:04:20 :: Connecting to wireless network AP
2016/08/16 19:04:20 :: attempting to set hostname with dhclient
2016/08/16 19:04:20 :: using dhcpcd or another supported client may work better
2016/08/16 19:04:21 :: attempting to set hostname with dhclient
2016/08/16 19:04:21 :: using dhcpcd or another supported client may work better
2016/08/16 19:04:22 :: Putting interface down
2016/08/16 19:04:22 :: Releasing DHCP leases...
2016/08/16 19:04:22 :: attempting to set hostname with dhclient
2016/08/16 19:04:22 :: using dhcpcd or another supported client may work better
2016/08/16 19:04:23 :: Setting false IP...
2016/08/16 19:04:23 :: Stopping wpa_supplicant
2016/08/16 19:04:23 :: Flushing the routing table...
2016/08/16 19:04:23 :: Putting interface up...
2016/08/16 19:04:23 :: attempting to set hostname with dhclient
2016/08/16 19:04:23 :: using dhcpcd or another supported client may work better
2016/08/16 19:04:24 :: attempting to set hostname with dhclient
2016/08/16 19:04:24 :: using dhcpcd or another supported client may work better
2016/08/16 19:04:33 :: WARNING: Timed out waiting for interface to come up
2016/08/16 19:04:33 :: Generating psk...
2016/08/16 19:04:33 :: WARNING: PSK generation failed! Falling back to
wireless key.
2016/08/16 19:04:33 :: Please report this error to the wicd developers!
2016/08/16 19:04:33 :: Attempting to authenticate...
2016/08/16 19:04:36 :: Running DHCP with hostname max
2016/08/16 19:04:36 :: attempting to set hostname with dhclient
2016/08/16 19:04:36 :: using dhcpcd or another supported client may work better
2016/08/16 19:04:36 :: Internet Systems Consortium DHCP Client 4.3.1
2016/08/16 19:04:36 :: Copyright 2004-2014 Internet Systems Consortium.
2016/08/16 19:04:36 :: All rights reserved.
2016/08/16 19:04:36 :: For info, please visit https://www.isc.org/software/dhcp/
2016/08/16 19:04:36 ::
2016/08/16 19:04:36 :: Listening on LPF/wlan0/be:ef:de:ad:be:ef
2016/08/16 19:04:36 :: Sending on LPF/wlan0/be:ef:de:ad:be:ef
2016/08/16 19:04:36 :: Sending on Socket/fallback
2016/08/16 19:04:36 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67
interval 5
2016/08/16 19:04:36 :: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
2016/08/16 19:04:36 :: DHCPOFFER from 192.168.x.y
2016/08/16 19:04:36 :: DHCPACK from 192.168.x.y
2016/08/16 19:04:37 :: bound to 192.168.x.z -- renewal in 404977 seconds.
2016/08/16 19:04:37 :: DHCP connection successful
2016/08/16 19:04:37 :: not verifying
2016/08/16 19:04:37 :: Connecting thread exiting.
2016/08/16 19:04:40 :: Sending connection attempt result success
Not until I had a look at /var/log/daemon.log:
Aug 16 19:22:59 debian NetworkManager[2959]: <error> [1471368179.222482]
[supplicant-manager/nm-supplicant-interface.c:856] interface_add_cb(): (wlan0):
error adding interface: wpa_supplicant couldn't grab this interface.
Aug 16 19:22:59 debian NetworkManager[2959]: <info> (wlan0): supplicant
interface state: starting -> down
Aug 16 19:22:59 debian wpa_supplicant[6439]: ctrl_iface exists and seems to be
in use - cannot override it
Aug 16 19:22:59 debian wpa_supplicant[6439]: Delete '/run/wpa_supplicant/wlan0'
manually if it is not used anymore
Aug 16 19:22:59 debian wpa_supplicant[6439]: Failed to initialize control
interface '/run/wpa_supplicant'.#012You may have another wpa_supplicant process
already running or the file was#012left by an unclean termination of
wpa_supplicant in which case you will need#012to manually remove this file
before starting wpa_supplicant again.
I realized that _is_ the problem.
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Closing this as wicd-kde is dead upstream and has not been available in
Debian for quite some time.
--
Med vänliga hälsningar
Patrick Franz
--- End Message ---
