[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 136501] KDE locks up when KWallet password dialog pops up while
From:       Tim Middleton <x () vex ! net>
Date:       2007-01-14 3:13:09
Message-ID: 20070114031309.1041.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=136501         
x vex net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  CC|                            |x vex net



------- Additional Comments From x vex net  2007-01-14 04:13 -------
I've had stuff like this happen to me for a long time, but never could put \
my finger on what was causing it. This sounds like it could be it. 

Actually i was just about to report a similar thing that i can reproduce \
100% and also is probably the same thing. 

In Digikam 0.9 there is a "Comments/Tags" side pannel on the thumbnail \
view. If you right click one one of the tags in the list you get a "Tags" \
context menu.  On this context menu is an fly-open menu item "Create Tag \
from Address Book"... which when activated (merely by hovering over) \
attempts to access kaddressbook to then give a submenu of contacts for \
selection. However, what happens on systems (confirmed on both my Gentoo \
box, and my FreeBSD box) is that "KDE Wallet Service" window opens in the \
background (i have kwallet configured on a timeout, so it is often not \
open), and KDE becomes completely unresponsive to clicks or keyboard \
controls. The "KDE Wallet Service" item can be seen highlighted in the task \
bar taunting me... but i can't get to it... or to anything else.

It is possible that it is a flaw in the way Digikam calls kwallet, but even \
if so it seems kwallet shouldn't ever be allowed to lock the entire \
interface like this?

Switching to console and running the following command:

for a in `dcop --user x`; do echo $a; dcop --user x $a >/dev/null; done 

The above look freezes on ResourceKolab-KABC0-#### ... 

Killing that process kills digikam... but i get my UI back when switching \
back to GUI from console. (Likewise, when something like the original \
poster reports happens to me i start killing various konqueror instances \
from console in a similar way... and can usually get the UI back eventually \
without completely restarting... but it's obviously not an optimal \
situation!)


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic