Bug 271754

Summary: "Automatic" kded crash caused by double free in kwallet/authinfo
Product: [Frameworks and Libraries] kdelibs Reporter: Emmeran Seehuber <rototor>
Component: kdedAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Emmeran Seehuber 2011-04-26 11:06:15 UTC
Application: kded4 ($Id$)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic x86_64
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:
This crash happens always when I use KDE4. Its just a matter of time before this crash happens in the session.   

This is nothing new to me. I´ve got this problems since KDE 4.4 or somthing like this. It was frequently annoying in Ubuntu 10.10, even with the KDE 4.6 backports (ppa). But in Natty 11.04 it has now become a killer. Kontact/kmail renders unusable because the connections to my local IMAP Server (with selfsigned cert) break all the time and kmail asks my all the time when it tries to do something on the imap server (i.e. displaying emails). I think this is connected with the crash as AFAIK the imap KIO stuff is forked off the kded deamon, isn´t it?

This crash report here is happening while using Gnome. As KDE was not longer usable i migrated my email/organizer stuff to evolution and now use a gnome desktop. I only use kwin, konsole and akregator (since Gnome has AFAIK no usable RSS Reader....; Evolution just does nothing when trying to register my self signed HTTPS-Trac-RSS Feeds). The crash you can see here has been caused by opening akregator and waiting for some minutes...

I think this might be caused by the kwallet file i use. I use KDE since 1.0beta3; I think the last time i erased by .kde dir was at KDE 3.2 time. So my kwallet-file has not been deleted for a long time. And i really dont want to do delete it.

Im using the properitary NVIDIA driver. I even downgraded to use the open source nvidia driver (because some properitary nvidia_tls-libs where in the callstack). But that didnt change anything. 

- Unusual behavior I noticed:
Everything depending on KDED is fucked up... The most annoying thing is: I have some Servers which have selfsigned certs. Everytime Akregator tries to access them it asks me if I trust those servers. And I always say "Permanently" -- but some minutes later I´m asked again. I think this has something to do with the crashed kded. This is annoying, because after having my laptop run over night I have about 200 messages dialogs asking me if i want to trust the server..... I can provide a screenshot of that if you need it :)

Also those message boxes steal the focus from my vmwares, so thats annoying too.

Plese contact me if you need any future infos. The last time KDE was a great experience for me was with KDE 3.5 - which is a pitty given that you put such great effort into KDE.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE-Dienst (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0x7fc61b896780 (LWP 2365))]

Thread 2 (Thread 0x7fc612632700 (LWP 2366)):
#0  0x00007fc619162f03 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fc61657a104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc61657a9f2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc612f91c44 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007fc6165a13e4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fc616c39d8c in start_thread (arg=0x7fc612632700) at pthread_create.c:304
#6  0x00007fc61917004d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fc61b896780 (LWP 2365)):
[KCrash Handler]
#6  0x00007fc6190bdd05 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fc6190c1ab6 in abort () at abort.c:92
#8  0x00007fc6190f6d7b in __libc_message (do_abort=2, fmt=0x7fc6191df400 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007fc619102a8f in malloc_printerr (av=<value optimized out>, p=0x1945e50) at malloc.c:6283
#10 _int_free (av=<value optimized out>, p=0x1945e50) at malloc.c:4795
#11 0x00007fc6191068e3 in __libc_free (mem=<value optimized out>) at malloc.c:3738
#12 0x00007fc5fe65b8ed in KIO::AuthInfo::~AuthInfo (this=0x1951ff0, __in_chrg=<value optimized out>) at ../../kio/kio/authinfo.cpp:128
#13 0x00007fc5fc114866 in ~AuthInfoContainer (this=0x1945de0, key=<value optimized out>, info=...) at ../../kpasswdserver/kpasswdserver.h:81
#14 KPasswdServer::findAuthInfoItem (this=0x1945de0, key=<value optimized out>, info=...) at ../../kpasswdserver/kpasswdserver.cpp:749
#15 0x00007fc5fc114a1c in KPasswdServer::checkAuthInfoAsync (this=0x1945de0, info=..., windowId=0, usertime=<value optimized out>) at ../../kpasswdserver/kpasswdserver.cpp:306
#16 0x00007fc5fc11a2da in KPasswdServerAdaptor::checkAuthInfoAsync (this=0x18edbf0, info=<value optimized out>, windowId=0, usertime=529213) at kpasswdserveradaptor.cpp:57
#17 0x00007fc5fc11a6a5 in KPasswdServerAdaptor::qt_metacall (this=0x18edbf0, _c=<value optimized out>, _id=5, _a=0x7fff3f7680c0) at kpasswdserveradaptor.moc:151
#18 0x00007fc617b609fa in QDBusConnectionPrivate::deliverCall (this=0x15f5e80, object=0x18edbf0, msg=..., metaTypes=..., slotIdx=9) at qdbusintegrator.cpp:942
#19 0x00007fc617b61bb5 in QDBusConnectionPrivate::activateCall (this=0x15f5e80, object=0x18edbf0, flags=497, msg=...) at qdbusintegrator.cpp:852
#20 0x00007fc617b6233a in QDBusConnectionPrivate::activateObject (this=0x15f5e80, node=..., msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1410
#21 0x00007fc617b62578 in QDBusActivateObjectEvent::placeMetaCall (this=0x1ada920) at qdbusintegrator.cpp:1524
#22 0x00007fc61a53049a in QObject::event (this=0x1945de0, e=<value optimized out>) at kernel/qobject.cpp:1226
#23 0x00007fc6198dd9e4 in QApplicationPrivate::notify_helper (this=0x1600fe0, receiver=0x1945de0, e=0x1ada920) at kernel/qapplication.cpp:4462
#24 0x00007fc6198e23aa in QApplication::notify (this=<value optimized out>, receiver=0x1945de0, e=0x1ada920) at kernel/qapplication.cpp:4341
#25 0x00007fc61b297866 in KApplication::notify (this=0x7fff3f768db0, receiver=0x1945de0, event=0x1ada920) at ../../kdeui/kernel/kapplication.cpp:311
#26 0x00007fc61a51c49c in QCoreApplication::notifyInternal (this=0x7fff3f768db0, receiver=0x1945de0, event=0x1ada920) at kernel/qcoreapplication.cpp:731
#27 0x00007fc61a51fc25 in sendEvent (receiver=0x0, event_type=0, data=0x1517890) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#28 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1517890) at kernel/qcoreapplication.cpp:1372
#29 0x00007fc619985a0d in sendPostedEvents (this=0x1518ce0, flags=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#30 QEventDispatcherX11::processEvents (this=0x1518ce0, flags=...) at kernel/qeventdispatcher_x11.cpp:75
#31 0x00007fc61a51b882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#32 0x00007fc61a51babc in QEventLoop::exec (this=0x7fff3f768d40, flags=...) at kernel/qeventloop.cpp:201
#33 0x00007fc61a51fecb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#34 0x00007fc613c69135 in kdemain (argc=1, argv=0x158ccd0) at ../../kded/kded.cpp:925
#35 0x0000000000406dd3 in launch (argc=1, _name=0x40b2d7 "kded4", args=<value optimized out>, cwd=0x0, envc=<value optimized out>, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b15e "0") at ../../kinit/kinit.cpp:746
#36 0x00000000004098fe in main (argc=2, argv=0x7fff3f769ec8, envp=0x7fff3f769ee0) at ../../kinit/kinit.cpp:1861

Possible duplicates by query: bug 268173, bug 263711, bug 257160, bug 256077, bug 243262.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-05-04 16:27:02 UTC

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