Bug 113958 - KDED crashes, probably due to answering opened KWallet access request window
Summary: KDED crashes, probably due to answering opened KWallet access request window
Status: RESOLVED DUPLICATE of bug 113061
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kwallet (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: George Staikos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-06 12:21 UTC by Henk Poley
Modified: 2005-11-13 07:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henk Poley 2005-10-06 12:21:25 UTC
Version:           onbekend (using KDE 3.4.2, Gentoo)
Compiler:          gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)
OS:                Linux (i686) release 2.6.13-suspend2-r4

I'm also having a somewhat related problem that somewhere between Kontact (KMail), Konqueror, Kate and Kopete KDED goes into CPU hogging mode if I don't answer the KWallet password prompt as fast as possible at desktop startup time. If it occurs I then need to kill kded and log out / back in. After which it usually doens't happen again that session.

This crash didn't occur right at startup of the KDE 3.4.2 desktop, but only after I got a prompt that requests if I want to give an application (it was Konqueror I beleive) access to the wallet for once or all the time.

Glad it crashed this time. Since a dead program is a good program. Hope you can see something from the backtrace.

Backtrace:
Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1229276992 (LWP 17016)]
[KCrash handler]
#4  KWalletD::internalOpen (this=0x81b88e8, appid=@0x818c3bc, 
    wallet=@0x818c3c8, isPath=false, w=41943045) at kwalletbackend.h:102
#5  0xb650bffe in KWalletD::doTransactionOpen (this=0x81b88e8, 
    appid=@0x818c3bc, wallet=@0x818c3c8, wId=41943045) at kwalletd.cpp:337
#6  0xb650adc5 in KWalletD::processTransactions (this=0x81b88e8)
    at kwalletd.cpp:152
#7  0xb651169a in KWalletD::qt_invoke (this=0x81b88e8, _id=7, _o=0xbfddf74c)
    at kwalletd.moc:100
#8  0xb730c053 in QObject::activate_signal (this=0x806e698, clist=0x8194670, 
    o=0xbfddf74c) at qconnection.h:56
#9  0xb763fe58 in QSignal::signal (this=0x806e698, t0=@0x0)
    at moc_qsignal.cpp:100
#10 0xb7325bef in QSignal::activate (this=0x806e698) at qsignal.cpp:212
#11 0xb732d293 in QSingleShotTimer::event (this=0x806e670) at qtimer.cpp:286
#12 0xb72b0b3c in QApplication::internalNotify (this=0x0, receiver=0x806e670, 
    e=0xbfddfbc4) at qapplication.cpp:2615
#13 0xb72afedd in QApplication::notify (this=0xbfddfed0, receiver=0x806e670, 
    e=0xbfddfbc4) at qapplication.cpp:2372
#14 0xb7905d24 in KApplication::notify (this=0xbfddfed0, receiver=0x806e670, 
    event=0xbfddfbc4) at kapplication.cpp:549
#15 0xb72a05c9 in QEventLoop::activateTimers (this=0x814e660)
    at qeventloop_unix.cpp:555
#16 0xb725a8c7 in QEventLoop::processEvents (this=0x814e660, flags=4)
    at qeventloop_x11.cpp:389
#17 0xb72c2a98 in QEventLoop::enterLoop (this=0x814e660) at qeventloop.cpp:198
#18 0xb72c2948 in QEventLoop::exec (this=0x814e660) at qeventloop.cpp:145
#19 0xb72b0d71 in QApplication::exec (this=0xbfddfed0)
    at qapplication.cpp:2758
#20 0xb781e580 in kdemain (argc=1, argv=0x805d800) at kded.cpp:897
#21 0xb782b7ce in kdeinitmain (argc=1, argv=0x805d800) at kded_dummy.cpp:2
#22 0x0804ce10 in launch (argc=1, _name=0x804f5ab "kded", args=0x0, cwd=0x0, 
    envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x804f517 "0") at kinit.cpp:626
#23 0x0804eb5b in main (argc=2, argv=0xbfde0314, envp=0xbfde0320)
    at kinit.cpp:1779
Comment 1 George Staikos 2005-11-13 07:43:37 UTC

*** This bug has been marked as a duplicate of 113061 ***