Summary: | Crash when editing identity | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Côme Chilliet <come> |
Component: | config dialog | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kde.kfoar, l.mester, maql.nju, montel |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Stack trace
Kontact crash log crash dump system and packages info to the crash dump |
Description
Côme Chilliet
2015-10-05 09:06:05 UTC
Note: Adding new identities work, but not if I ask to duplicate the problematic one. It appears as «Come» while I might have put «Côme» intially as the identity name, I don’t remember. Please ask for any other needed information. I need a real backtrace :) Created attachment 94850 [details]
Stack trace
Grr, the bug tracker lost my comment because I attached a file. I was saying the bug report tool is saying my stack trace is useless, and it points to https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports which says using Arch I’d have to build everything from source, which I’d like to avoid. Perhaps qt5.5.0 has a bug because I can't see a kmail bug here. I have encountered the same problem (kmail crashes in most attempts) here with a very similar stack trace that ends up crashing in _gpgme_ath_mutex_lock in libgpgme.so. It might be some rushing conditions there. Considering that we are in a multi-threaded environment, I tried to run kmail with LD_PRELOAD=/usr/lib/libgpgme-pthread.so.11 kmail in Arch Linux and it seems to be solving the problem and all encryption features work fine. I am not sure libgpgme-pthread is the proper library that kmail shall link to though; even in that case the problem can be in cmake or elsewhere. Created attachment 97257 [details]
Kontact crash log
I'm also experiencing this. I've attached my konsole output, since it may provide any helpful information.
It also crashes if I try to create a new identity by copying that identity. I'm using KMail 5.0.2 Created attachment 104303 [details]
crash dump
Created attachment 104305 [details]
system and packages info to the crash dump
kmail crashes at trying to modify an identity. See dump.
Thread 1 "kmail" received signal SIGSEGV, Segmentation fault.
0x00007ffeb5f84184 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
(gdb)
apt-cache policy kmail
kmail:
Installiert: 4:16.04.3-3
apt-cache depends kmail | grep libqt
Hängt ab von: libqt5core5a
Hängt ab von: libqt5dbus5
Hängt ab von: libqt5gui5
Hängt ab von: libqt5network5
Hängt ab von: libqt5widgets5
Hängt ab von: libqt5xml5
apt-file search libQtGui
libqt4-dev: /usr/lib/x86_64-linux-gnu/libQtGui.prl
libqt4-dev: /usr/lib/x86_64-linux-gnu/libQtGui.so
libqtgui4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4
libqtgui4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8
libqtgui4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.7
apt-cache policy libqtgui4
libqtgui4:
Installiert: 4:4.8.7+dfsg-11
apt-cache policy libqt5gui5
libqt5gui5:
Installiert: 5.7.1+dfsg-3+b1
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 haven't experienced this in some time. I assume it's fixed. IMO this ticket can be closed. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Thanks for the update; changing status. |