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

"Secrets / KDE Daemon" dialog - Why?

Page 1 of 1 (6 posts)

Tags: None
(comma "," separated)
lphilpot
Registered Member
Posts
34
Karma
0
OS

"Secrets / KDE Daemon" dialog - Why?

Wed Jul 10, 2013 1:44 am
(KDE 4.10.4 on an ASUS K55N laptop, Fedora 18 64-bit)

In the past few days, I've seen this dialog:

Image

If that link doesn't work, it says: "Secrets for Altair - KDE Daemon" on the titlebar and "The network Altair requires authentication" (my wifi network is 'altair'). There's a field for a passphrase and OK/Cancel buttons. The dialog is preloaded with the correct passphrase and clicking OK dismisses it without error. I've only seen this after unlocking the laptop after a few hours away from it. Even while the dialog is visible, wireless networking is still working and active.

I have no idea what's triggering this. It may not be KDE; I found a few Google hits pointing to NetworkManager, but aside from the appearance of the dialog, everything appears to be working properly.

Any pointers?

Thanks!
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: "Secrets / KDE Daemon" dialog - Why?

Thu Jul 11, 2013 7:33 am
One possibility is that your wireless connection goes down after KDE itself has been frozen as part of the suspend process. As a result of this, KDE receives a large storm of network status change events, causing KDE to believe an authentication issue exists. Meanwhile NetworkManager itself successfully reconnects to your wireless network.

When you accept that dialog, KDE Network Management then detects it is already successfully connected to that network and takes no further action.

Just to verify it is not caused by excess network profiles lingering in your user account, can you try under a new user please?

KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
lphilpot
Registered Member
Posts
34
Karma
0
OS

Re: "Secrets / KDE Daemon" dialog - Why?

Thu Jul 11, 2013 11:41 am
I can try another user, but I have no power management enabled - No automatic suspend / hibernate, etc. In fact, it's specifically disabled, since I don't like my computers to go to sleep. And, I've not changed any of those settings, but this has just started happening. Is there a log that would show wireless (re)connects? /var/log/messages, or something more specific?

Thanks.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: "Secrets / KDE Daemon" dialog - Why?

Thu Jul 11, 2013 9:48 pm
I see. The exact log it would be recorded in is distribution specific unfortunately. Some have NetworkManager reporting to /var/log/messages, others have it going to a specific /var/log/NetworkManager, etc.

Another theory is that there is a momentary network connection disruption - which causes it to attempt to reconnect. While this initially fails, it later succeeds (even though it should wait due to needing an updated password - but it is likely there is a timeout involved here).

KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
lphilpot
Registered Member
Posts
34
Karma
0
OS

Re: "Secrets / KDE Daemon" dialog - Why?

Fri Jul 12, 2013 2:26 am
I took a look at the messages log and there are tons of repeating entries like this (ethernet addresses manually obscured) :

Jul 7 03:56:24 regulus kernel: [108953.747266] cfg80211: Calling CRDA to update world regulatory domain
Jul 7 03:56:24 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: completed -> disconnected
Jul 7 03:56:24 regulus kernel: [108953.756810] cfg80211: World regulatory domain updated:
Jul 7 03:56:24 regulus kernel: [108953.756819] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jul 7 03:56:24 regulus kernel: [108953.756824] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:56:24 regulus kernel: [108953.756830] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:56:24 regulus kernel: [108953.756834] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:56:24 regulus kernel: [108953.756838] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:56:24 regulus kernel: [108953.756843] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:56:24 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Jul 7 03:56:25 regulus kernel: [108954.845317] wlan0: authenticate with xx:xx:xx:xx:xx:xx
Jul 7 03:56:25 regulus kernel: [108954.864077] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
Jul 7 03:56:25 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Jul 7 03:56:25 regulus kernel: [108954.867917] wlan0: authenticated
Jul 7 03:56:25 regulus kernel: [108954.869122] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
Jul 7 03:56:25 regulus kernel: [108954.872805] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=0 aid=2)
Jul 7 03:56:25 regulus kernel: [108954.872906] wlan0: associated
Jul 7 03:56:25 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: authenticating -> associated
Jul 7 03:56:25 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Jul 7 03:56:25 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Jul 7 03:57:02 regulus kernel: [108991.284054] cfg80211: Calling CRDA to update world regulatory domain
Jul 7 03:57:02 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: completed -> disconnected
Jul 7 03:57:02 regulus kernel: [108991.292636] cfg80211: World regulatory domain updated:
Jul 7 03:57:02 regulus kernel: [108991.292643] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jul 7 03:57:02 regulus kernel: [108991.292647] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:57:02 regulus kernel: [108991.292651] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:57:02 regulus kernel: [108991.292655] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:57:02 regulus kernel: [108991.292659] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:57:02 regulus kernel: [108991.292662] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 7 03:57:02 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Jul 7 03:57:03 regulus kernel: [108992.383074] wlan0: authenticate with xx:xx:xx:xx:xx:xx
Jul 7 03:57:03 regulus kernel: [108992.401958] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
Jul 7 03:57:03 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Jul 7 03:57:03 regulus kernel: [108992.403954] wlan0: authenticated
Jul 7 03:57:03 regulus kernel: [108992.405076] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
Jul 7 03:57:03 regulus kernel: [108992.408688] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x411 status=0 aid=2)
Jul 7 03:57:03 regulus kernel: [108992.408768] wlan0: associated
Jul 7 03:57:03 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: authenticating -> associated
Jul 7 03:57:03 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Jul 7 03:57:03 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed

I did a quick bit of Googling, but so far without much to tell. But, it looks like a non-KDE issue, so I'll continue to look.

Thanks.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: "Secrets / KDE Daemon" dialog - Why?

Fri Jul 12, 2013 3:53 am
This definitely looks like a problem with either NetworkManager or wpa_supplicant. Based on the below message, it looks like wpa_supplicant is giving up on the connection for some reason - which might explain in part why it immediately prompts you for the password.
Code: Select all
Jul 7 03:57:02 regulus NetworkManager[731]: <info> (wlan0): supplicant interface state: completed -> disconnected

KDE Sysadmin
[img]content/bcooksley_sig.png[/img]

Page 1 of 1 (6 posts)

Bookmarks


Who is online

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