Summary: | Kontact (frameworks branch) crash when Forward mail (only if not from independent window of message) and when "New Mail" | ||
---|---|---|---|
Product: | [Applications] kdepim | Reporter: | desaparecido <luis.davila.pc> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | GIT (master) | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
stdout when click "New Message" icon
stdout when try "forward" (by right-click menu or icon) |
Description
desaparecido
2015-08-08 12:51:14 UTC
Created attachment 93948 [details]
stdout when click "New Message" icon
Created attachment 93949 [details]
stdout when try "forward" (by right-click menu or icon)
if message is open in different windows all works fine
still testing, for the issue "New message", If I launch Kontact and directly choice "New Message", one new windows open (like expected) but if I click in a folder of my e-mail IMAPs accounts (so I view the messages of that folder) and then "New Message", the crash happens. hi, I still having the same issue all this time, testing with the latests commits, trying if something in upstream solve my bug, and the only relevant (launching Kontact in Konsole) message when crash is: log_messagecomposer: RecipientLineFactory::newLine: We can't connect to new line QWidget(0x5588943790e0) *** KMail got signal 11 (Exiting) Segmentation fault (core dumped) I'll build my packages with debug option, but I don't know if I need to build all kdepim packages with "debug" or only kdepim... Someone could help me with that ? I hope with that give more information with a complete "crash report" that only 3 lines. thanks This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input. |