Bug 353557 - Crash when editing identity
Summary: Crash when editing identity
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: config dialog (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-05 09:06 UTC by Côme Chilliet
Modified: 2021-01-09 16:16 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Stack trace (9.05 KB, text/plain)
2015-10-05 12:56 UTC, Côme Chilliet
Details
Kontact crash log (2.18 KB, text/x-log)
2016-02-17 09:31 UTC, Ovidiu-Florin BOGDAN
Details
crash dump (26.06 KB, text/plain)
2017-03-01 17:01 UTC, Mester
Details
system and packages info to the crash dump (10.29 KB, text/plain)
2017-03-01 17:10 UTC, Mester
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Côme Chilliet 2015-10-05 09:06:05 UTC
When I click on my default and only identity and click modify, it crashes

This happens each time so I can’t edit its settings anymore.

Reproducible: Always

Steps to Reproduce:
1. Go to configuration dialog
2. Select the identity
3. Click «Modify»

Actual Results:  
crash


Application: kmail (5.0.1)

Qt Version: 5.5.0
Operating System: Linux 4.2.2-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Backtrace:
A useful backtrace could not be generated
Comment 1 Côme Chilliet 2015-10-05 09:09:35 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.
Comment 2 Laurent Montel 2015-10-05 11:56:39 UTC
I need a real backtrace :)
Comment 3 Côme Chilliet 2015-10-05 12:56:45 UTC
Created attachment 94850 [details]
Stack trace
Comment 4 Côme Chilliet 2015-10-05 12:58:10 UTC
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.
Comment 5 Laurent Montel 2015-10-08 06:52:25 UTC
Perhaps qt5.5.0 has a bug because I can't see a kmail bug here.
Comment 6 Qianli Ma 2015-10-22 16:10:46 UTC
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.
Comment 7 Ovidiu-Florin BOGDAN 2016-02-17 09:31:19 UTC
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.
Comment 8 Ovidiu-Florin BOGDAN 2016-02-17 09:33:43 UTC
It also crashes if I try to create a new identity by copying that identity.
I'm using KMail 5.0.2
Comment 9 Mester 2017-03-01 17:01:50 UTC
Created attachment 104303 [details]
crash dump
Comment 10 Mester 2017-03-01 17:10:08 UTC
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
Comment 11 Justin Zobel 2020-12-17 05:26:54 UTC
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.
Comment 12 Ovidiu-Florin BOGDAN 2020-12-17 09:38:50 UTC
I haven't experienced this in some time. I assume it's fixed. IMO this ticket can be closed.
Comment 13 Bug Janitor Service 2021-01-01 04:35:19 UTC
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!
Comment 14 Christoph Feck 2021-01-09 16:16:17 UTC
Thanks for the update; changing status.