https://bugs.kde.org/show_bug.cgi?id=340014
Denis Kurz <kde...@posteo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |kde...@posteo.de
Resolution|WONTFIX |---
Version|4.14.1 |5.2.3
Ever confirmed|0 |1
--- Comment #10 from Denis Kurz <kde...@posteo.de> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
