Bug 677339

Summary: knetworkmanager lists garbage in the Connections-list (after suspend/resume)
Product: [Fedora] Fedora Reporter: Otso Helenius <fedora>
Component: kde-plasma-networkmanagementAssignee: Rex Dieter <rdieter>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: dcbw, kevin, ltinkl, mmcgrath, rdieter, roland.wolters, smparrish, thomasj
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kde-plasma-networkmanagement-0.9-0.35.20110221.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-03 02:59:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
incorrect entries in the plasmoid list
none
knetworkmanager plasmoid switching wireless on and off none

Description Otso Helenius 2011-02-14 12:48:09 UTC
Created attachment 478618 [details]
incorrect entries in the plasmoid list

Description of problem:

the network manager plasmoid in KDE lists a huge amount of wired connections with the name "unknown". it also shows two wireless connections whose name begin "No such object path '/org/k...". clicking on them does not do anything.
also some of my wireless networks are listed twice on the list.

when i open the "manage connections" window, i see three wireless networks (the three i use) and no wired connections (just as it should).

i have not done any configuration (except adding the three wireless networks and their keys), the superfluous entries have appeared without my interference.

Version-Release number of selected component (if applicable):

Fedora 14 x86_64 KDE spin, KDE 4.5.5
kde-plasma-networkmanagement 0.28.20101011.fc14
NetworkManager 0.8.1
knetworkmanager-libs 0.28.20101011.fc14

How reproducible:

not sure, and i don't have an idea how to get rid of the entries (i haven't tried deleting ~/.kde etc.)

Additional info:

i have attached a screenshot to show the incorrect behaviour

Comment 1 Rex Dieter 2011-02-14 14:09:12 UTC
I colleague of mine experienced this too (@ fudcon), but only after a suspend/resume cycle of his laptop.  you too?

Comment 2 Otso Helenius 2011-02-16 17:59:32 UTC
Yes, I can confirm this happens after resuming the computer from sleep, not after a cold boot or relogin.

Comment 3 Rex Dieter 2011-02-16 18:08:05 UTC
Thanks, updating summary.

Comment 4 Otso Helenius 2011-02-16 22:31:51 UTC
As an addition to the bug, the plasmoid gets caught in a strange loop sometimes when resuming. dmesg is filled with:

ADDRCONF(NETDEV_UP): wlan0: link is not ready

and the plasmoid switches wireless on and off completely amok. I have attached a gif animation showing its behaviour. If there's any need I can try to debug (given instructions) or file a bug also at bugs.kde.org.

Comment 5 Otso Helenius 2011-02-16 22:33:41 UTC
Created attachment 479229 [details]
knetworkmanager plasmoid switching wireless on and off

Comment 6 Dan Williams 2011-02-17 16:47:39 UTC
First thing to check is when you see bogus APs in the list, run:

nm-tool

and see what it says for APs.  That tool will list exactly what NetworkManager is exposing over D-Bus.  If that list differs from what GUI tools say then the GUI tool has some bug in the caching logic it's using.  nm-tool (or nmcli) allow you to figure out where to point the blame.

There's a small possibility that NM isn't sending the right D-Bus signals out when removing APs from the scan list, but I'm fairly sure that's not the case.  So lets start with nm-tool...

Comment 7 Otso Helenius 2011-02-17 19:30:36 UTC
after suspend/resume, the GUI is listing 20 "Unknown" wired connections. it is also listing my own wireless network three times, and one additional hidden wireless network. when pressing "Show More..." it shows also the ~20 networks that nm-tool is listing.

the list shown with nm-tool seems consistent before and after resume (before suspend 20 networks, after resume 21 networks, it varies due to bad signal strength with some networks).

 normally after logging in only known networks are listed. 

i guess this shows with a pretty good confidence which one is the real culprit.

btw, should i file a bug at bugs.kde.org as well at this point?

Comment 8 Rex Dieter 2011-02-17 19:53:43 UTC
Probably so.

In the meantime, I'll see about whipping up a snapshot build to test further.

Comment 9 Rex Dieter 2011-02-17 21:15:38 UTC
Here's something to try, kde-plasma-networkmanagement-0.9-0.34.20110217.fc14 scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2847385

Comment 10 Lukáš Tinkl 2011-02-20 16:11:33 UTC
FWIW, after a quick check, this build fixes it for me

Comment 11 Otso Helenius 2011-02-21 11:19:57 UTC
Same here, it seems like the issue is fixed with the version 0.34 Rex provided. I tested it a few times and have not managed to reproduce the unknown connections it was listing earlier.

Thank you!

Comment 12 Fedora Update System 2011-02-22 14:20:43 UTC
kde-plasma-networkmanagement-0.9-0.35.20110221.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9-0.35.20110221.fc15

Comment 13 Fedora Update System 2011-02-22 14:21:22 UTC
kde-plasma-networkmanagement-0.9-0.35.20110221.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9-0.35.20110221.fc14

Comment 14 Fedora Update System 2011-02-22 14:22:08 UTC
kde-plasma-networkmanagement-0.9-0.35.20110221.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9-0.35.20110221.fc13

Comment 15 Fedora Update System 2011-02-22 18:49:21 UTC
kde-plasma-networkmanagement-0.9-0.35.20110221.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update kde-plasma-networkmanagement'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9-0.35.20110221.fc14

Comment 16 Fedora Update System 2011-03-03 02:59:10 UTC
kde-plasma-networkmanagement-0.9-0.35.20110221.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 17 Fedora Update System 2011-03-04 09:52:55 UTC
kde-plasma-networkmanagement-0.9-0.35.20110221.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 18 Fedora Update System 2011-03-04 09:56:06 UTC
kde-plasma-networkmanagement-0.9-0.35.20110221.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.