Bug 166298

Summary: Dashboard disappears when KWallet pops up the password dialog
Product: [Unmaintained] plasma4 Reporter: Carsten Niehaus <cniehaus>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DOWNSTREAM    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Carsten Niehaus 2008-07-11 13:07:37 UTC 
Version:            (using KDE 4.0.83)
Installed from:    SuSE RPMs
OS:                Linux

When I start up KDE 4.1 it takes a while until Kopete is active. That means it can take 1 minute until KWallet asks for the password. That is simply because of my slow hardware.

When I open the dashboard (using the "Show Dashboard" feature) the dashboard is hidden again when KWallet pops up. That means that for example the taskbar appears again.

One could argue now that the dashboard is hidden (the computer goes to 'normal mode') once a user-action is needed. OTOH I find this a bit confusing. If this is done by design perhaps the Dashboard should reappear ofter KWallet got its input?
Comment 1 Aaron J. Seigo 2008-07-11 22:23:10 UTC 
yes, this is the intended behaviour right now. it could likely be made better (e.g. by trying to detect whether the window was from plasma or spontaneously appeared, etc)
Comment 2 Nate Graham 2018-06-08 20:36:26 UTC 
Hello!

This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable.

Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham