(Jaunty) plasmoid-network-manager does not remember configured connection

Bug #335777 reported by Frank
86
This bug affects 11 people
Affects Status Importance Assigned to Milestone
plasma-widget-network-manager (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Jaunty by Michael Calabrese

Bug Description

Binary package hint: plasmoid-network-manager

The plasmoid-network-manager does not remember settings of prior configured wlan connections since about 1 week in jaunty.
How to reproduce:
Install the latest jaunty updates
Remove all hidden config files from home directories
Configure a wlan connection (to a listed SSID) within from the plasmoid or within from kde systemsettings and give this connection a name.
In my case the name was "ZuHause"
Enable password storage and setup kdewallet.

Networkmanager will immediately connect to the network and the applet shows "Connected to ZuHause".
At this time I can disconnect and disable wlan from the applet. Re-enabling the wlan module works fine and the applet shows immediately the configured connection "ZuHause", afterwards. Clicking on "ZuHause", enabled the connection after entering the kdewallet password and work reliably.

Reboot the system

After the reboot the configured connection is shown within kde-systemsettings as "ZuHause" but it does not appear at the plasmoid. The plasmoid show only the SSID which is also "linked" to "ZuHause".
Clicking on the SSID demand for a newly configuration.
So every reboot the connection has to be configured again which results in many entries within kde-systemsettings and kdewallet.

The same happens with installed plasma-widget-network-manager instead of plasmoid-network-manager

uname -a : 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:27:53 UTC 2009 x86_64 GNU/Linux
dpkg -l | grep network

ii avahi-autoipd 0.6.23-4ubuntu3
ii ifupdown 0.6.8ubuntu15
ii iproute 20080725-2
ii iputils-ping 3:20071127-1
ii iputils-tracepath 3:20071127-1
ii libnm-glib0 0.7.1~rc1+20090220-0ubuntu1
ii libnm-util1 0.7.1~rc1+20090220-0ubuntu1
ii libqt4-network 4.5.0~+rc1-0ubuntu1
ii net-tools 1.60-21ubuntu1
ii netbase 4.34ubuntu1
ii network-manager 0.7.1~rc1+20090220-0ubuntu1
rc plasma-widget-network-manager 0.0+svn930811-0ubuntu1
ii plasmoid-network-manager 0.0+svn923467-0ubuntu1
ii tcpdump 3.9.8-4ubuntu1

Frank

Frank (frank-schaeffer)
description: updated
Revision history for this message
Ilja Pavkovic (ipavkovic) wrote :

same for me, stored connections are only reused if they flagged as "Connect automatically". I also see that the MAC address of the access point is NOT stored in the panel. Perhaps this may be a problem?

Revision history for this message
Ilja Pavkovic (ipavkovic) wrote :

I slightly modified applet/interfacegroup.cpp:

QList<AbstractWirelessNetwork*> InterfaceGroup::networksToShow()
{
    QList<AbstractWirelessNetwork*> allNetworks;
    QList<AbstractWirelessNetwork*> topNetworks;

+ kDebug() << "m_wirelessEnvironment->networks() " << m_wirelessEnvironment->networks().isEmpty()
+ << " m_connections " << m_connections.isEmpty();

=> this prints
plasma(7316) InterfaceGroup::networksToShow: m_wirelessEnvironment->networks() false m_connections true

so m_connections seem to be empty. But I have configured connections.

Revision history for this message
panproteus (panproteus) wrote :

Confirming:

1. System-wide connection can be created only with nm-connection-editor (or hand editing config). NM config in the plasmoid does not allow flagging connection as "system-connection"
2. Even if there are system-wide connections defined, NetworkManager widget connects only to those marked with "Connect Automatically". The others are not even listed in the selection list.
3. The plasmoid seems to be not aware of presence of system connections. After the SSID of the connection is selected from the list a new connection dialog pops up (what I noticed, also a new UUID is assigned to every connection in KDE wallet, also a new entry is created containing the PSK).

Versions:

network-manager 0.7.1~rc3-0ubuntu2
plasma-widget-network-manager 0.0+svm930811-0ubuntu1

Revision history for this message
Christophe Olinger (olingerc) wrote :

Question:
So in order to have an automatic connection to a secured WiFi I need to use kdewallet?

Revision history for this message
Christophe Olinger (olingerc) wrote :

Additional comment probably linked to this bug:
At the moment I need to enter my WiFi password at least three times (2 different dialogs) and the connection is not always established.

Revision history for this message
DavidPa0 (dpasero) wrote :

I'm currently testing Kubuntu Jaunty beta and have the same kind of problems.
I do not make use of system wide connection settings.
I basically connect with the plasmoid by selecting a name from the displayed wireless networks list. I then enter the password which is stored in kdewallet.
For some reason, the plasmoid does not manage to reconnect to the same network (automatically or manually) even with no reboot, I am always prompted for the password again.
Settings stored in kdewallet fail to be re-used. If I enter connection settings again, a new entry is inserted in kdewallet.
I would say that something changes that makes the plasmoid lose information about my previous connection settings.

Revision history for this message
Jithin Emmanuel (jithin1987) wrote :

I am also having the same problem.
I have set my wireless connection to auto connect mode. But if I miss the login part ie I didnt type kwallet password for a long time an then I type kwallet password and then try to connect by clicking in the list of connections shown in in plasmoid it does not look up the already stored one. It creates a new configuration.
Result is that wireless tab in Network management has a lot of connections by same name all with same configuration.

Same also applies if some how the power goes off and then comes back and I try to reconnect thorugh the plasmoid it asks to create a new configuration.
I am using plasma-widget-network-manager latest from the repositories.

Revision history for this message
giacof (giacof) wrote :

Confirmed on Kubuntu Jaunty beta.

dpkg -l | grep network-manager
ii network-manager 0.7.1~rc3.2.gitb8fc83a7-0ubuntu1 network management framework daemon
ii plasma-widget-network-manager 0.0+svn930811-0ubuntu2 KDE plasma applet for controlling NetworkMan

Changed in plasma-widget-network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Vladimir Korenev (vkorenev) wrote :

I confirm the bug.
The plasmoid forgets everything I've entered in the Wireless Security tab. A new entries are created in kwallet every time I log in to the same wireless network. These entries contain the correct wep key.

$ dpkg -l | grep network-manage
ii network-manager 0.7.1~rc4-0ubuntu1 network management framework daemon
ii plasma-widget-network-manager 0.0+svn930811-0ubuntu2 KDE plasma applet for controlling NetworkMan

Revision history for this message
Carlos Aguilar (carlos-aguilar) wrote :

Same issue here with kwallet deactivated :
Network manager keeps asking for passwords even if they are stored.

Revision history for this message
starchild7778 (starchild7778) wrote :

I am using Kubuntu 9.04, the final release, not a beta or RC release, and am also having a problem with the network manager plasmoid. Each time I sign in following a reboot, KDE Wallet Manager keeps prompting me for a password, even though I have entered this password many times previously and have selected "Always Allow" for the Network Management utility for access control to kdewallet.

I have no issues in Gnome with the network manager applet. It autoconnects each time I log in.

Revision history for this message
Uwe Mock (u-mock) wrote :

The problem with the NetworkManager plasmoid asking for a password over and over again even though the password is stored in KWallet still exists in Jaunty final. You'll only get a connection if you're lucky.

Revision history for this message
Jithin Emmanuel (jithin1987) wrote :

network manager plasmoid is a joke. It should never have been shipped with jaunty. Use nm-applet if kubuntu users want to have a better user experience and I am pretty sure that , this is not going to be fixed for jaunty.

Revision history for this message
Klaus Layer (klaus-layer) wrote :

With the latest Jaunty updates this issue seems to be fixed in the network managment plasmoid. I no longer experience this problem.

Revision history for this message
Scott Testerman (scott-testerman) wrote :

New version of plasma-widget-network-manager is 0.0+svn966653-0ubuntu0.1.

Please check to see if the same problems still exist. This update has fixed numerous annoyances for me. If you have existing wireless connections defined, you may need to delete them, then log out and back in, before testing.

Revision history for this message
Salze (stefan-sarzio) wrote :

I no longer experience this problem, too, using the same version Scott states.

Revision history for this message
Jithin Emmanuel (jithin1987) wrote : Re: [Bug 335777] Re: (Jaunty) plasmoid-network-manager does not remember configured connection

Yes its fixed in the latest version.

On Sun, Jun 21, 2009 at 12:44 PM, Salze <email address hidden> wrote:

> I no longer experience this problem, too, using the same version Scott
> states.
>
> --
> (Jaunty) plasmoid-network-manager does not remember configured connection
> https://bugs.launchpad.net/bugs/335777
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Thanks
Jithin Emmanuel

P. J. O'Rourke<http://www.brainyquote.com/quotes/authors/p/p_j_orourke.html>
- "If government were a product, selling it would be illegal."

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Great. :)

Changed in plasma-widget-network-manager (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Uwe Mock (u-mock) wrote :

Unfortunately, I was not so successful. Establishing a wireless connection is still a matter of luck with the new version. And what's worse: 3G connections don't work any more; the plasmoid has crashed Plasma a couple of times while creating new 3G connections or trying to connect throug 3G.

So I went back to wicd and umtsmon.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.