Summary: | kontact crash after strtup problem | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Thomas Janssen <thomasj> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | andresbajotierra, chr.albrecht, cornelis, kavol, majca_j, md2z34, mroeben, null, o-z, rpitney, tjm1983, wolkensprung |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Thomas Janssen
2010-02-11 11:46:14 UTC
Created attachment 41504 [details]
New crash information added by DrKonqi
The situation is the same as previously mentioned. Exists in 4.4.1
*** Bug 226426 has been marked as a duplicate of this bug. *** *** Bug 231111 has been marked as a duplicate of this bug. *** Additional information: same installation, freshly created user, kontact starts fine. Seems to be something per user. Created attachment 42190 [details]
New crash information added by DrKonqi
I booted my computer, logged in, and started Kontact. A message came up saying Kontact may already be running, and offered to either exit or start anyway. I chose to exit, and then it crashed like this.
*** Bug 238551 has been marked as a duplicate of this bug. *** *** Bug 242930 has been marked as a duplicate of this bug. *** *** Bug 236677 has been marked as a duplicate of this bug. *** Created attachment 48595 [details]
New crash information added by DrKonqi
I booted my computer, logged in, and started Kontact. Then I remembered that I had left Kontact running when I last shut down, so it was already trying to start. A window warned me about two copies running, and offered to let me exit. I chose to exit, and got this crash.
Created attachment 48673 [details]
New crash information added by DrKonqi
This time I'm fairly sure that I had closed Kontact before shutting down the computer last time. When I booted the computer and started Kontact, it came up with the same warning message, and gave the same crash when I clicked Exit.
Created attachment 49440 [details]
New crash information added by DrKonqi
Tried to start kontact. It tried to start akonadi but nothing is happening and it is going on forever. Only way to stop this is by killing kontact. Bad thing is that KDE is remembering that kontact was running and so it is trying to start it immedieately after login.
*** Bug 236916 has been marked as a duplicate of this bug. *** *** Bug 233463 has been marked as a duplicate of this bug. *** Created attachment 51630 [details]
New crash information added by DrKonqi
kmail asked me for opening kdewallet, but before entering the password, due to some unresponsiveness I've issued killall kmail, which led to the crash
[Comment from a bug triager] Note that the duplicates on bug 238551 include other patterns in the backtrace like an eventloop caused by "Kleo::KeyResolver::lookupContactPreferences" (so I don't know if the root cause is the same) Regards (In reply to comment #9) > Created an attachment (id=48595) [details] > New crash information added by DrKonqi > > I booted my computer, logged in, and started Kontact. Then I remembered that I > had left Kontact running when I last shut down, so it was already trying to > start. A window warned me about two copies running, and offered to let me > exit. I chose to exit, and got this crash. (In reply to comment #10) > Created an attachment (id=48673) [details] > New crash information added by DrKonqi > > This time I'm fairly sure that I had closed Kontact before shutting down the > computer last time. When I booted the computer and started Kontact, it came up > with the same warning message, and gave the same crash when I clicked Exit. This should be fixed now I think. Seems unrelated to what is reported here. some of the dups are also unrelated (231111...) Changing this bug status, a backtrace obtained after killing an application is not helpful enough (and I think the issue is already fixed now, please retry with kdepim 4.4.9) (In reply to comment #16) > Changing this bug status, a backtrace obtained after killing an application is > not helpful enough (and I think the issue is already fixed now, please retry > with kdepim 4.4.9) Just now, I tried (only once) to reproduce this crash, and the crash didn't happen. Created attachment 60821 [details]
New crash information added by DrKonqi
kontact (4.4.10) on KDE Platform 4.6.3 (4.6.3) "release 4" using Qt 4.7.3
- What I was doing when the application crashed:
The system was starting up afterb a reboot. Akonadi server was taking very long to get started. When trying to run Kontact the crash window was displayed
-- Backtrace (Reduced):
#11 0xb716a297 in operator-> () at /usr/src/debug/kdelibs-4.6.3/kdeui/widgets/kmainwindow.cpp:214
#12 operator* () at /usr/src/debug/kdelibs-4.6.3/kdeui/widgets/kmainwindow.cpp:214
#13 KMainWindow::memberList () at /usr/src/debug/kdelibs-4.6.3/kdeui/widgets/kmainwindow.cpp:1192
#14 0xad8d97d0 in KMKernel::dumpDeadLetters() () from /usr/lib/libkmailprivate.so.4
#15 0xad99433d in kmcrashHandler () from /usr/lib/libkmailprivate.so.4
|