[kde] [Bug 335881] New: kwallet dialogs open in background

RJVB rjvbertin at gmail.com
Fri Jun 6 14:36:20 BST 2014


https://bugs.kde.org/show_bug.cgi?id=335881

            Bug ID: 335881
           Summary: kwallet dialogs open in background
    Classification: Unclassified
           Product: kde
           Version: 4.12.5
          Platform: unspecified
                OS: OS X
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: rjvbertin at gmail.com

It's all in the title - every time I need to enter a password to unlock a
kwallet, I have to go grab the dialog from somewhere behind the window
requesting the encrypted information.
This is annoying but becomes problematic when the unlock request does not stem
from an immediate user action, but from a process running in the background.

Reproducible: Always

Steps to Reproduce:
1. Do anything that requires access to a wallet that's currently locked (which
might just be having akonadi services run)
2. Wait until the wallet system posts a password dialog

Actual Results:  
The password dialog opens somewhere behind the current window, on the middle of
the screen (so typically completely hidden by other open windows). KDE's
notification system does post a message, but it only allows to ignore the
request or switch back to the calling application ... which still has the input
focus.

Expected Results:  
The password dialog opens in front, having obtained input focus

See
https://forum.kde.org/viewtopic.php?f=60&t=121478&sid=050a9636469e60976277154d8fc2095f&p=312556#p312536
for a discussion and proposed solutions, including one (a QtKeyChain based
backend) that would provide integration with the OS X password management
system (Keychain).

Additionally, on OS X there are always 2 wallet icons visible in the Dock and
the app switcher (1 for kwalletd, one for the manager). This doesn't make it
easier to switch to the instance that has the dialog open!

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list