Bug 398363

Summary: Network manager loses credentials info
Product: [Plasma] plasmashell Reporter: Marcin Bajor <marcin.bajor>
Component: Networks widgetAssignee: Jan Grulich <jgrulich>
Status: RESOLVED FIXED    
Severity: normal CC: ego, justin.zobel, vkrevs
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Edit connection with empty fields
Edit connections window
Connection info after restart services
connections_wrong_selections
Plasma logs

Description Marcin Bajor 2018-09-07 15:17:05 UTC
Created attachment 114827 [details]
Edit connection with empty fields

Sometimes plasma-nm loses all connection info.
When I click "connect" to WiFi network a window with empty fields is displayed (edit-wifi.png attachment), but when I click on "Edit connections" some fields are filed (connections.png attachment) without password.
For other WiFi connections(with password only) plasma-nm asks for password but is not able to connect.
All passwords are stored in kwallet.
I can't connect to other wired networks too. Click on "connect" does nothing.

Plasma network manager loses all connection info and passwords.

Command:
$sudo systemctl restart network NetworkManager
or restart of computer sometimes resolves the problem (connection_info_after_restart_services.png attachment)
Comment 1 Marcin Bajor 2018-09-07 15:17:38 UTC
Created attachment 114828 [details]
Edit connections window
Comment 2 Marcin Bajor 2018-09-07 15:18:30 UTC
Created attachment 114829 [details]
Connection info after restart services
Comment 3 Marcin Bajor 2018-09-07 15:44:04 UTC
When applet crashes I've noticed that sometimes details of selected connection are from different connection (connections_wrong_selections atachment)
Comment 4 Marcin Bajor 2018-09-07 15:44:21 UTC
Created attachment 114830 [details]
connections_wrong_selections
Comment 5 Marcin Bajor 2018-09-07 15:44:37 UTC
Created attachment 114831 [details]
Plasma logs
Comment 6 Marcin Bajor 2018-09-07 15:49:07 UTC
This often happens when I switching wired cable in my laptop. I have to work with multiple wired networks.
Comment 7 Christian Kalkhoff 2018-09-08 13:28:39 UTC
I can confirm this behaviour, yet I am not able to reproduce. But it might be related to connections to different networks over LAN.

I will try to gather more information next time it occurs to me.
Comment 8 Justin Zobel 2020-11-01 04:14:24 UTC
(In reply to Christian Kalkhoff from comment #7)
> I can confirm this behaviour, yet I am not able to reproduce. But it might
> be related to connections to different networks over LAN.
> 
> I will try to gather more information next time it occurs to me.

Christian were you able to reproduce this one?
Comment 9 Christian Kalkhoff 2020-11-01 08:41:16 UTC
Thanks for asking, no it didn't happen to me again.
Comment 10 Justin Zobel 2020-11-01 08:46:15 UTC
(In reply to Christian Kalkhoff from comment #9)
> Thanks for asking, no it didn't happen to me again.

Thanks for the update, I'll close this ticket but if the issue returns don't hesitate to open a new one.
Comment 11 Ben Cooksley 2024-12-23 18:26:00 UTC
Bulk transfer as requested in T17796