Bug 220778

Summary: kwallet password dialog opens on wrong desktop when multiple konsole instances running
Product: [Applications] kwalletmanager Reporter: Ryan Hill <dirtyepic>
Component: generalAssignee: Michael Leupold <lemma>
Status: RESOLVED WORKSFORME    
Severity: normal CC: cubranic, jpfender, valir
Priority: NOR Keywords: triaged
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Ryan Hill 2009-12-31 09:33:33 UTC
Version:            (using KDE 4.3.4)
Compiler:          GCC 4.4 
OS:                Linux
Installed from:    Gentoo Packages

I have five virtual desktops set up with two konsole instances open.  The first is where I do all my work and is pinned across all desktops, while the second is on desktop 5 and runs irssi.

Often I'm working in one desktop and when committing something to svn the kwalletd notification pops up telling me subversion needs to access the wallet.  The problem is that no matter what desktop I happen to be working on, the password dialog box itself _always_ opens on the desktop with the irssi window instead of the where I ran the command from.

I'm not sure why it consistently picks that one; I've tried moving the irssi window to different desktops but the result is always the same.  There are no special window/application configuration rules enabled for either windows (though i notice the sticky konsole's role is "mainwindow#1" and the second is "mainwindow#2" if that means anything).

I guess this is more of a pet-peeve than anything else, but it's driving me nuts. ;)
Comment 1 Jakob Pfender 2010-01-03 13:18:41 UTC
I'm having a similar problem. I use four workspaces, where #1 is work, #2 is IM, #3 is Amarok and #4 is everything else. I always have KDE start with workspace 2 in focus, because that's where my IM programs autostart. Now, whenever I start Amarok (with workspace 3 in focus), the KWalletManager notification window opens on workspace 2. This is especially annoying since Amarok only starts after I've typed in the password - but since I do that on workspace 2, Amarok then opens on workspace 2 and not 3 like it's supposed to.

I have a feeling that this is related to the fact that I always have my system start on workspace 2 - possibly because the KWalletManager is started in the background and thinks that it's running in that workspace, thus showing all its notifications there as well.

This should be changed to either having the dialogue pop up in the current workspace or (maybe even better) in all workspaces.
Comment 2 Davor Cubranic 2010-08-18 18:11:05 UTC
Similar problem with KDE 4.4.2 (Kubuntu Karmic, 10.04): I have two virtual desktops, and if the system starts in #1, and I switch to #2 and start KMail there, KWalletManager's dialog is invisible because it opens on desktop #1. So I have to switch to that desktop, enter my password, and then switch back to desktop #2 where KMail is running.

What's also curious is that I have the task manager panel set to only show windows from the current desktop, and yet both KWalletManager and KMail will be shown there when they first appear, even though their windows are actually on the other desktop. It's actually kind of useful in this case, but it's almost as if either KWin or the Task Manager knew about this bug and so kludge their behaviour to help the user work around it.
Comment 3 Valentin Rusu 2013-09-03 22:48:58 UTC
Does the new notification system helped solve this problem? Are you now able to see the notification and switch to the password prompt?
Comment 4 Andrew Crouthamel 2018-09-24 02:12:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 02:33:01 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!