Home Home > 2010 > 06 > 07 > Hacking for Freedom
Sign up | Login

Hacking for Freedom

June 7th, 2010 by

Hi developers!

These are first hours of hackweek. A lot of people in Novell and in the community are starting to work on different projects. What can I give for free software in this week? Sure, my favorite project is NetworkManagement.

As you can see, NetworkManagement don’t work well. For example, it can’t see WiFi connection and don’t show wired connetcion. Yes, right now we have one bug with module “networkmanagement”.

This module must be loaded after start NetworkManagement, but this is not happening :(

If you check it, you will see:

anaumov@pizza:~/plasma/networkmanagement> qdbus --system org.freedesktop.NetworkManagerUserSettings
Service 'org.freedesktop.NetworkManagerUserSettings' does not exist.

Why it’s happening? Problem is in connection between plasmoid and deamon NM (via DBus).

anaumov@pizza:~/plasma/networkmanagement> qdbus org.kde.kded /kded loadModule networkmanagement
true
anaumov@pizza:~/plasma/networkmanagement> qdbus --system org.freedesktop.NetworkManagerUserSettings
/
/org
/org/freedesktop
/org/freedesktop/NetworkManagerSettings
/org/freedesktop/NetworkManagerSettings/0
/org/freedesktop/NetworkManagerSettings/1
/org/freedesktop/NetworkManagerSettings/2
/org/freedesktop/NetworkManagerSettings/3
/org/freedesktop/NetworkManagerSettings/4
/org/freedesktop/NetworkManagerSettings/5
/org/freedesktop/NetworkManagerSettings/6
/org/freedesktop/NetworkManagerSettings/7
/org/freedesktop/NetworkManagerSettings/8
anaumov@pizza:~/plasma/networkmanagement>

So, now we can see WiFi interface:

And WiFi interface can see WiFi connections:

Good, but this works not automaticly. It’s first what I want to hack on this week.

And what do you want to do on this week? ;)

Both comments and pings are currently closed.

5 Responses to “Hacking for Freedom”

  1. Your copy of the Networkamangement plasmoid is pretty old! Try the latest from trunk, most problems have been fixed there.

  2. I’m just fine with you working on network management stuff – esp if you can get things like bluetooth/usb tethering to work :D

    Otherwise, it mostly needs stability, good looks, ease of use and ‘just works’ (as automatic as possible – eg if I want to connect to a network, it’s OK to ask for a password, NOT let me choose between WPA/WEP and all that stuff).

  3. Raymond Wooninck

    This issue mentioned in this blog was something that I also was experiencing. I even reported it as a KDE bug for sebas, but after checking a couple of other bug reports, it appeared that this strange behavior is caused by an outdated libdbusmenu-qt. It seems that all plasmoids in the systray are using this new program and the latest KDE SC 4.5 snapshots require the latest version (0.3.3). If you are using the packages from KDE:KDE4:Unstable then you should be able to upgrade. This solved the bug for me.

    The source repo you mentioned is correct and the only one.

  4. I hope we’ll be finally able to use knetworkmanager to actually connect to WiFi. Connection added in connection editor differs with connection available to chose inside the applet by name, security etc. So settings may be saved in different placed, what actually sucks.

    Also, I’ve been experiencing NM’s stupid behaviour: I had to wait after computer startup about a minute or select connection by hand to get connected. Just wrong.