[Bug 17775] New: kded goes into loop after first kwallet access by kopete

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=17775
Ubuntu | kdelibs-bin

           Summary: kded goes into loop after first kwallet access by kopete
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: kdelibs-bin
        AssignedTo: debzilla at ubuntu.com
        ReportedBy: rob at robhughes.com
         QAContact: kubuntu-bugs at lists.ubuntu.com


Very weird and took me a few weeks (and several deletions of my .kde directory) to figure out. I have "restore previous 
session" selected and enabled the kwallet subsystem, and also have kopete running at logout. Upon logging in again after some 
random number of times (10-20), kded will go to 99-100% cpu utilization, and is in a loop in the automounter accessing my two 
optical drives (hdc and hdd), as soon as kopete accesses kdewalletmanager and I input my kwallet password, then hit enter. If 
I kill and restart kded, then the cpu utilization issue goes away, but I can't get kopete to go online. If I don't kill kded, 
it will just continue in this loop indefinitely, or at least for the two hours I let it go to see if it would ever break out. 
 
I can produce an strace of the issue if it will be helpful. For now, I just don't use kopete. I also wasn't sure which of the 
three modules to file the bug against since it's a very strange and specific interaction required to trigger it. And what 
makes it so frustrating is that this seems to block all further input to kwalletmanager, so I can't start konq, kontact, or 
anything else that accesses kwalletmanager.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.