This forum has been archived. All content is frozen. Please use KDE Discuss instead.

NetworkManager Plasmoid stopped displaying wifi networks

Tags: None
(comma "," separated)
User avatar
tobik
Registered Member
Posts
72
Karma
0
EDIT: Ok, it seems to me now, that NM Plasmoid stopped displaying networks at all. However it is able to connect to networks which have been already used and are defined in the settings. I am not able to connect to any new wifi network. Gnome's nm-applet works flawlessly.

--

Hi, I am experiencing a really weird problem with NetworkManager Plasmoid. I recently came to McDonalds and tried to connect to their public wifi but the wifi didn't even appear in the list of networks around me. Actually the list was completely empty (besides <hidden network>). I opened settings and tried to add the network manually using some settings dialogs and the network was there! So I added it and confirmed, but the Plasmoid still wasn't displaying it and wasn't able to connect. Then I tried nm-applet (Gnome front end for NetworkManager) and it worked like a charm. It found the wifi and connected properly.

Now I am sitting on the bus, there is also a free wifi and the situation is completely same like at McDonalds. I had to use nm-applet to connect. Funny is, that when I connect using nm-applet, NetworkManager Plasmoid properly shows that I am connected, but it still doesn't display any networks. Also funny is, that NM Plasmoid works without any problem at home or at school where I am connecting to WPA-protected networks. WEP protected networks work also good. So I guess this is affecting only public wifi networks. I thought it could be some kind of security measure which has to be turned of but I couldn't find anything in the settings.

I am using KDE 4.6.0, openSUSE 11.4.
krat3r
Registered Member
Posts
2
Karma
0
OS
Open Yast -> [Network Settings] -> tab [Global Settings]

And change the field "Network Setup Method" from
- "User Controlled with NetworkManager"
to
- "Tradicional Method with ifup"
and apply.

Afterwards change it back to "User Controlled with NetworkManager"

It worked for me with a similar problem.
User avatar
tobik
Registered Member
Posts
72
Karma
0
Thank you but it didn't work. The list of available wireless lans is still empty. Since this works in nm-applet and not in plasmoid, I guess it's a problem of the plasmoid. I tried fresh KDE profile but also no results.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Unusual. Did you perform any update to your system which may have introduced this problem? Also, check /var/log/messages or /var/log/NetworkManager or /var/log/daemon.log for any messages relating to NetworkManager which may indicate why it isn't scanning for networks.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
tobik
Registered Member
Posts
72
Karma
0
I found this in /var/log/messages:
Code: Select all
Mar 29 08:54:10 redBook nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Mar 29 08:53:51 redBook NetworkManager[22129]: <error> [1301381631.753969] [nm-manager.c:1368] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name



And same lines in /var/log/NetworkManager. /var/log/daemon.log doesn't exist on my computer.

However as I wrote before, nm-appler or even pure KDE configuration dialog for adding wifis manually are scanning just fine! So NetworkManager can't be that broken and the problem must be in NetworkManager Plasmoid or somewhere between them.

And yes, I am afraid I performed some updates recently and some NetworkManager stuff was also included. However it was standard OpenSUSE update process so I had no reason not to trust it. Anyway this weird behavior could be just a bug. I tried to run new KDE profile with empty settings but it also didn't help.
User avatar
tobik
Registered Member
Posts
72
Karma
0
I returned back to standard KNetworkManager Applet. The UI is not so fancy but at least scanning works :-) I wish there would be something like nm-applet in KDE. nm-applet is simple, absolutely stable and imho much more ergonomic than NM Plasmoid or Applet. But it looks alien of course.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
A functioning network management applet requires that you enable the KDE Network Management service, which runs in kded4 usually. This is controlled in System Settings. Once you enable it, you cannot use the standalone KNetworkManager application.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
tobik
Registered Member
Posts
72
Karma
0
Chmm, I'm now a little bit confused. I always thought that KNetworkManager and NetworkManager Plasmoid are just similar frontends for networking in KDE. It looks like that at least. They use the same dialogs and settings in System Settings and when I switched from Plasmoid to KNM. my configuration (wifi networks, passwords, certificates...) didn't disappear, it was preserved. So I guess they must use the same storage, the same KDE backend. Or is there something more different than just UI?
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
KNM was meant as a stop-gap solution until the plasmoid was in better shape (in earlier days, the plasmoid was out right unusable). Nowadays it's been deprecated and no new updates will be made AFAIK.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
User avatar
tobik
Registered Member
Posts
72
Karma
0
Well since KNM works wine and Plasmoid doesn't for me, I'll stick with KNM. Maybe in the future I'll try Plasmoid again to see whether to problem was fixed or not.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]