Application: kmail (1.13.5) KDE Platform Version: 4.5.85 (4.6 Beta2) Qt Version: 4.7.1 Operating System: Linux 2.6.37-9-generic x86_64 Distribution: Ubuntu natty (development branch) -- Information about the crash: - What I was doing when the application crashed: Adding a contact by right-clicking on a sender's email address in an email message. System asks to access KWallet (which otherwise seems to work), then crashes after I put the password in. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #6 0x00007f4dfa4bfba5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007f4dfa4c36b0 in abort () at abort.c:92 #8 0x00007f4dfaae07ed in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #9 0x00007f4dfaadea36 in ?? () from /usr/lib/libstdc++.so.6 #10 0x00007f4dfaadea63 in std::terminate() () from /usr/lib/libstdc++.so.6 #11 0x00007f4dfaadebb6 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #12 0x00007f4dfae84692 in QEventLoop::exec (this=0x7fff30338ca0, flags=...) at kernel/qeventloop.cpp:214 #13 0x00007f4dfae889bb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #14 0x0000000000403272 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:156 Possible duplicates by query: bug 259903, bug 259876, bug 259874, bug 259855, bug 259818. Reported using DrKonqi
The KWallet request seems to work; crash now happens after selecting an address book in which to store the contact.
backtrace ?
Also crashes whenever I try to manually enter a contact. I have not yet managed to get one to stick. Representative backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0x7faa1fa5c780 (LWP 4613))] Thread 2 (Thread 0x7fa9f68ed700 (LWP 4663)): #0 0x00007faa1ca7e203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007faa161ec030 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007faa161ec559 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007faa1d1b1f26 in QEventDispatcherGlib::processEvents (this=0x12cce20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417 #4 0x00007faa1d186362 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007faa1d18659c in QEventLoop::exec (this=0x7fa9f68ecda0, flags=...) at kernel/qeventloop.cpp:201 #6 0x00007faa1d09d274 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490 #7 0x00007faa1d16882f in QInotifyFileSystemWatcherEngine::run (this=0x130e930) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007faa1d09fa2e in QThreadPrivate::start (arg=0x130e930) at thread/qthread_unix.cpp:285 #9 0x00007faa166b4971 in start_thread (arg=<value optimized out>) at pthread_create.c:304 #10 0x00007faa1ca8a92d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7faa1fa5c780 (LWP 4613)): [KCrash Handler] #6 0x00007faa1c9d7ba5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007faa1c9db6b0 in abort () at abort.c:92 #8 0x00007faa1cde27ed in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #9 0x00007faa1cde0a36 in ?? () from /usr/lib/libstdc++.so.6 #10 0x00007faa1cde0a63 in std::terminate() () from /usr/lib/libstdc++.so.6 #11 0x00007faa1cde0bb6 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #12 0x00007faa1d186692 in QEventLoop::exec (this=0x7fff299cea80, flags=...) at kernel/qeventloop.cpp:214 #13 0x00007faa1d18a9bb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #14 0x0000000000403ff7 in main (argc=1, argv=<value optimized out>) at ../../../kontact/src/main.cpp:224 No matter where or when I press OK, it bombs for me.
Hej Chris, unfortunately the backtraces are of no help, did you have installed the debug version of the packages? Ciao, Tobias
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!