Bug 379006

Summary:	When KWallet unlocks automatically and programs re-open on boot, programs open before KWallet gets unlocked
Product:	[Plasma] plasmashell	Reporter:	Nate Graham <nate>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	bhush94, nate, plasma-bugs, rdieter
Priority:	NOR
Version:	5.9.4
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Nate Graham 2017-04-20 16:39:41 UTC

Distro: openSUSE Tumbleweed
DE: KDE Plasma 5.9.4

Steps to reproduce:
1. Turn on KWallet's auto-unlocking:
- Make sure your login password the KWallet password match
- Install the PAM KWallet package for your distro (pam_kwallet on openSUSE)
- Edit /etc/pam.d/sddm according to https://wiki.archlinux.org/index.php/KDE_Wallet
2. Store your wifi password in your KWallet
3. Open Firefox and browse the web
4. Restart the machine while Firefox is still open


Expected results:
- By the time Firefox launches, KWallet is unlocked and I'm connected to my Wifi network.


Actual results:
- Firefox opens before KWallet unlocks and has supplied the wifi module with the password; Firefox thinks there's no network connection and has to be restarted before pages will load.

Comment 1 Rex Dieter 2017-04-21 11:53:31 UTC

In my experience, you shouldn't need to restart firefox (reloading pages should be sufficient, it is for me).  Any other behavior is a bug (in firefox), in my opinion.

Comment 2 Rex Dieter 2017-04-21 11:55:35 UTC

In your case, it may help to enable wifi connection option: "all users may connect to this network", then NetworkManager manages the secrets and will enable the connection earlier (during boot process) so it has a better chance of being ready by the time your user session starts.

Comment 3 Nate Graham 2017-04-21 14:15:14 UTC

Sadly something broke with the config and now my wallet doesn't automatically unlock at login anymore. Debugging that first...

Comment 4 David Edmundson 2017-04-23 22:39:13 UTC

> Firefox thinks there's no network connection and has to be restarted before pages will load.

That's not really anything to do with kwallet. 

Even if we blocked waiting on kwallet, it still takes network manager a while to connect; during which firefox could load.

We cannot block session restore until network manager is ready; it'd break far too many other things.

We (Network manager) does broadcast when it does connect, Firefox should detect this and reload itself. Please ask firefox to fix that.

Comment 5 Nate Graham 2017-04-23 23:36:34 UTC

Fair enough. https://bugzilla.mozilla.org/show_bug.cgi?id=1358932