Summary: | Restart of kontact not possible | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Heiner Markert <mephisto> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | aheinecke, winter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Heiner Markert
2011-06-21 12:56:11 UTC
Andre, Allen any clue about this ? If you can reproduce this reliably this is a good thing, it has been reported to me from some users but only as "sometimes" behavior and we have not found the trigger. It would be very helpful if you could do the following: 1. > Go to you Kontact installation folders /bin directory and start kdebugdialog > and select all debug output there 2. Download DebugView ( http://technet.microsoft.com/en-us/sysinternals/bb896647 ) 3. Start Kontact, start debugview then close kontact and attach the log to this bugreport As workarounds i can offer: a) Start the taskmanager and kill the kontact process manually b) In you Kontact/bin installation folder there is a killkde.bat this will also terminate everything. This might be a duplicate of Bug 222878 https://bugs.kde.org/show_bug.cgi?id=222878 (In reply to comment #2) Unfortunatly, today I was not able to reproduce the bug anymore. Although I did not use my Windows system since writing the bug, besides installing some security updates, the problem seems to have disappeared. When I wrote the report, I tried to reboot my machine two times, and was able to reproduce the behavior reliably. When I am able to reproduce, I will send the requested attachment. However, I have no idea what could have changed on my system. Thank you for the feedback. Feel free to reopen this report when you get more information Hi, after debugging this myself a bit i do not need your debug output anymore Heiner, thanks but i am pretty sure now that i know what happens (But still not why ;) ). There is a hanging job that maintains a reference to the kontact process and thus will stop it from closing. I am now ~90% sure that this is the same problem described in BUG 222878 so i am marking this as duplicate. *** This bug has been marked as a duplicate of bug 222878 *** |