Summary: | kMail crashes when opening a new main window if the original (first) main window has been closed | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Gunter Ohrner <kdebugs> |
Component: | UI | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REOPENED --- | ||
Severity: | crash | CC: | abyss.7, davidbryant, eddie.howson, felixelens, johannes.willkomm, kde, kdenis, rodney.baker, stakanov.s |
Priority: | NOR | ||
Version: | 5.2.3 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Gunter Ohrner
2014-10-16 08:55:56 UTC
The feature to be able to open multiple mail windows has simply been removed from kMail to get rid of bugs like this... So technically it's not fixed, but it also cannot be reproduced any more... *** Bug 375330 has been marked as a duplicate of this bug. *** *** Bug 341712 has been marked as a duplicate of this bug. *** *** Bug 341938 has been marked as a duplicate of this bug. *** *** Bug 346257 has been marked as a duplicate of this bug. *** *** Bug 342329 has been marked as a duplicate of this bug. *** *** Bug 349178 has been marked as a duplicate of this bug. *** *** Bug 347236 has been marked as a duplicate of this bug. *** *** Bug 357150 has been marked as a duplicate of this bug. *** Actually, this bug was reported for much more recent versions, although the way to trigger it is not the same. I think I have a rough idea what happened: When a new KMail instance is created, its KMSystemTray is created as a copy from another KMSystemTray. This class has a raw d-pointer, but no copy control. Now when one of the instances is destroyed, the other has a dangling d-pointer. That's just an educated guess, though. I'm still very confused by the gigantic pim codebase, so I might have missed several important details. The duplicate bug 375330 was reported for 5.2.3. Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. I'm not using kMail any more since a few years, as it was just too unreliable. More than once I had the problem that I suddenly ended up with a non-working email program after upgrades to a KDE bugfix or next stable release due to some obscure Akonadi and other problems. However, as far as I remember, the feature "File->New->Main Window" was removed from kMail alltogether to "fix" other issues the occured in relation to multiple main windows. As I was used to work with those before, it was quite a set-back back then. So maybe the original issue here is not relevant any more at all, although I don't know about the issues Dennis mentioned in Comment 10 in 2017 - so not sure if this could be closed as "worksforme" or whatever... I think this problem has been fixed. I'm using Gentoo Packages, KMail 5.16.3, Plasma 5.21.5, Frameworks %.82.0, Qt 5.15.2. The menu item "File --> New --> Main Widow" has been removed. Simply starting KMail, then saying "kmail" in a terminal window won't fire up a second instance of the program. But "d-bus-launch kmail" will start a second (and a third) instance of the program. I fiddled around with this for a bit, and could not get any of the instances of KMail to crash. I could navigate to different folders / messages. I ran "qps" (traces process ids, like a GUI version of "top"). I saw multiple instances of the akonadi server running, which might eventually cause a problem. Memory usage was pretty high. Killing the extra instances of kmail left "phantom" instances of akonadi hanging around ... I'm too lazy to try killing them one by one, so will probably just reboot to clean up the process tree.. The only really odd thing I noticed is that the system tray icon was not recreated when I opened a second main KMail window. And if I "quit" from the system tray, the second instance of KMail keeps on running. Does anybody have any objection to marking this bug "resolved"? |