Started off here, realized my problem was something else, so figured I’d try under a different title to get more input.
Anyway, here’s the deal. After an update about a week ago, users aren’t able to control the network interfaces. KNetworkManager, KInternet, KWiFiManager… all of them get started with no issues, but if I click on the applets, it won’t show any available interfaces. Best case scenario, the icon will change to show that one is up (like if I boot plugged into an ethernet port), but it won’t let me switch to wifi, or hover to see my IP, or anything like that.
I narrowed it down to a front end/permissions issue. With the help of a poster on my original thread, I have a work-around, but it’s a bit of a hack.
1)log in
2)kill the NetworkManager front-end
3)open a terminal
4)log in as root
5)invoke a NetworkManager front-end
If I invoke KNetworkManager as root, it works perfectly. I’ve tried reverting to older verions (like from the OSS repo instead of Updates) of NetworkManager and older versions of the front-ends, but all give the same result.
In YaST > Network Devices > Network Settings > Global Options, I have it set to “User Controlled with NetworkManager”.
Still not sure what the problem is. I mean, I have it so that it works well enough, but it’s pretty annoying. And my brother’s laptop is having the same problem. Any idea what the cause is?
Many other users are reporting this problem. I haven’t tried your fix yet as I’m a bit paranoid about running something like that in root. Will try it though and see if it works for me.
My problem started as a loss of wireless. Wired ethernet works fine, but I’ve tried manual settings to fix wireless and that didn’t work so I’ve turned “Auto” configure back on.
Right now I’m wondering what the default settings are in the DNS tab of networkmanager are? I checked the first two boxes and also the one at the bottom. Still no luck. Next stop is reboot and try your fix.
This is definitely the issue. If you notice, you cannot add a network or connection using networkmanager in the systray. It tells you to use Yast. You also cannot delete a connection. (all these as user)
Apparently this can be done if you “killall knetworkmanager” and then su (root password) and then “knetworkmanager”
So somewhere in an update yast was changed so that changes made there have no effect in knetworkmanager.
Someone suggested turning off knetworkmanager (“auto”) in Yast and doing it manually. I tried that, but it would only see my etho. Did not even see wlan0.
This is some output I got when I ran knetworkmanager as root earlier and tried (and failed) setup a wireless connection as root. Maybe somebody smarter than me can look at this and tell what is wrong.
peyre@linux-vd0b:~> killall knetworkmanager
peyre@linux-vd0b:~> su
Password:
linux-vd0b:/home/peyre # knetworkmanager
NMSettings::NMSettings
linux-vd0b:/home/peyre # WirelessSecurity::getEnabled false (null)
Activate New
AP linksys_XXX_XXXXX is encrypted
Storage::saveConnection
ConnectionSetting::toSecretsMap
ConnectionSetting::toSecretsMap
ConnectionSetting::toSecretsMap
WirelessSecurity::toSecretsMap
WirelessSecurity::toSecretsMap
IEEE8021x::toSecretsMap
ConnectionSettingsDialogImpl::~ConnectionSettingsDialogImpl
Connection::GetSettings, obj: /org/freedesktop/NetworkManagerSettings/Connection/0
Processing Setting ‘connection’
Attach setting ‘connection’
autoconnect: <bool>false</bool>
id: <string>linksys_XXX_XXXXX</string>
type: <string>802-11-wireless</string>
Processing Setting ‘ipv4’
Attach setting ‘ipv4’
method: <string>dhcp</string>
Processing Setting ‘802-11-wireless’
Attach setting ‘802-11-wireless’
mode: <string>infrastructure</string>
security: <string>802-11-wireless-security</string>
ssid: <list> <byte>108</byte> <byte>105</byte> <byte>110</byte> <byte>107</byte> <byte>115</byte> <byte>121</byte> <byte>115</byte> <byte>95</byte> <byte>83</byte> <byte>69</byte> <byte>83</byte> <byte>95</byte> <byte>54</byte> <byte>50</byte> <byte>49</byte> <byte>48</byte> <byte>49</byte> </list>
Processing Setting ‘802-11-wireless-security’
Attach setting ‘802-11-wireless-security’
group: <list> <string>tkip</string> <string>ccmp</string> </list>
key-mgmt: <string>wpa-psk</string>
pairwise: <list> <string>tkip</string> <string>ccmp</string> </list>
psk: <string></string>
Processing Setting ‘802-1x’
Setting ‘802-1x’ is empty, discarding
Connection::GetSecretsAsync for setting 802-11-wireless-security, id 0
Connection::slotSecretsNeeded 802-11-wireless-security, new: no
WirelessSecurity::toSecretsMap
SendGetSecretsReply1 id 0
SendGetSecretsReply2
Processing Setting ‘connection’
ConnectionSetting::toSecretsMap
Setting ‘connection’ is empty, discarding
Processing Setting ‘ipv4’
ConnectionSetting::toSecretsMap
Setting ‘ipv4’ is empty, discarding
Processing Setting ‘802-11-wireless’
ConnectionSetting::toSecretsMap
Setting ‘802-11-wireless’ is empty, discarding
Processing Setting ‘802-11-wireless-security’
WirelessSecurity::toSecretsMap
Attach setting ‘802-11-wireless-security’
group: <list> <string>tkip</string> <string>ccmp</string> </list>
key-mgmt: <string>wpa-psk</string>
pairwise: <list> <string>tkip</string> <string>ccmp</string> </list>
psk: <string>80c61f471082f93fec6ebc9e3b4f100fc7d5be14ac92819060e4935d2fd5111f</string>
Processing Setting ‘802-1x’
IEEE8021x::toSecretsMap
Setting ‘802-1x’ is empty, discarding
Connection::GetSecretsAsync for setting 802-11-wireless-security, id 0
Connection::slotSecretsNeeded 802-11-wireless-security, new: yes
ConnectionStore::slotSecretsNeeded
Storage::hasSecretsStored
Activate Connection /org/freedesktop/NetworkManagerSettings/Connection/0 on Device /org/freedesktop/Hal/devices/net_00_1d_d9_52_9e_82
Connection::GetSecretsAsync for setting 802-11-wireless-security, id 0
Connection::slotSecretsNeeded 802-11-wireless-security, new: no
WirelessSecurity::toSecretsMap
SendGetSecretsReply1 id 0
SendGetSecretsReply2
Processing Setting ‘connection’
ConnectionSetting::toSecretsMap
Setting ‘connection’ is empty, discarding
Processing Setting ‘ipv4’
ConnectionSetting::toSecretsMap
Setting ‘ipv4’ is empty, discarding
Processing Setting ‘802-11-wireless’
ConnectionSetting::toSecretsMap
Setting ‘802-11-wireless’ is empty, discarding
Processing Setting ‘802-11-wireless-security’
WirelessSecurity::toSecretsMap
Attach setting ‘802-11-wireless-security’
group: <list> <string>tkip</string> <string>ccmp</string> </list>
key-mgmt: <string>wpa-psk</string>
pairwise: <list> <string>tkip</string> <string>ccmp</string> </list>
psk: <string>80c61f471082f93fec6ebc9e3b4f100fc7d5be14ac92819060e4935d2fd5111f</string>
Processing Setting ‘802-1x’
IEEE8021x::toSecretsMap
Setting ‘802-1x’ is empty, discarding
Connection::GetSecretsAsync for setting 802-11-wireless-security, id 0
Connection::slotSecretsNeeded 802-11-wireless-security, new: yes
ConnectionStore::slotSecretsNeeded
Storage::hasSecretsStored
Storage::saveConnections
Storage::saveConnection brXMfPNh3o2wzTAL
ConnectionSetting::toSecretsMap
ConnectionSetting::toSecretsMap
ConnectionSetting::toSecretsMap
WirelessSecurity::toSecretsMap
WirelessSecurity::toSecretsMap
IEEE8021x::toSecretsMap
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 7
Minor opcode: 0
Resource id: 0x3800008
ICE default IO error handler doing an exit(), pid = 3770, errno = 11