Summary: | Kontact crashed while trying to reply to email | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Adam Jimerson <vendion> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | CONFIRMED --- | ||
Severity: | crash | CC: | asturm, kde, mail, openmail+kde, sven |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
Stacktrace from just launching Kmail |
Description
Adam Jimerson
2022-02-09 16:06:08 UTC
Created attachment 146521 [details]
New crash information added by DrKonqi
kontact (5.19.2 (21.12.2)) using Qt 5.15.2
- What I was doing when the application crashed:
Pressed 'a' to reply to everybody on a selected E-Mail in kmail component.
Since then I can no longer start kontact, it immediately crashes. However, when I restart akonadi, I get notifications about new E-Mails, and KOrganizer works.
Starting kmail directly also crashes.
- Custom settings of the application:
Gentoo Linux with gcc-11.2.1 and Qt-5.15.2
I have rebuilt everything needed for kontact plus kontact itself and have restarted the computer several times.
The odd thing is, that Kontact worked just fine like every day.
However, I have removed ~/.local/share/akonadi/db_data a week ago and have had akonadi recreate it. Everything worked just fine, so I doubt this could be the issue.
-- Backtrace (Reduced):
#6 QString::QString(QString const&) (other=<optimized out>, this=<optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/move.h:104
#7 std::_Head_base<4ul, QString, false>::_Head_base(QString const&) (__h=<optimized out>, this=<optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/tuple:193
#8 std::_Tuple_impl<4ul, QString>::_Tuple_impl(QString const&) (__head=<optimized out>, this=<optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/tuple:435
#9 std::_Tuple_impl<3ul, QString, QString>::_Tuple_impl(QString const&, QString const&) (__tail#0=<optimized out>, __head=<optimized out>, this=<optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/tuple:284
#10 std::_Tuple_impl<2ul, QString, QString, QString>::_Tuple_impl(QString const&, QString const&, QString const&) (__tail#1=<optimized out>, __tail#0=<optimized out>, __head=<optimized out>, this=<optimized out>) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/tuple:284
Interesting... Adams and my crash happened about around the same time, yesterday... Both go through (Adam) KMComposerWin::slotRecipientAdded(MessageComposer::RecipientLineNG*) (this=0x562d31d2fe70, line=<optimized out>) at kmail-21.12.2/src/editor/kmcomposerwin.cpp:3776 ( me ) KMComposerWin::slotRecipientAdded(MessageComposer::RecipientLineNG*) (this=0x556321561410, line=<optimized out>) at kmail-21.12.2/src/editor/kmcomposerwin.cpp:3776 Then (Adam) QGpgME::QGpgMEAddUserIDJob::start(GpgME::Key const&, QString const&, QString const&, QString const&) (this=0x562d32e9f830, key=..., name=..., email=..., comment=<optimized out>) at qt/src/qgpgmeadduseridjob.cpp:82 ( me ) QGpgME::QGpgMEAddUserIDJob::start(GpgME::Key const&, QString const&, QString const&, QString const&) (this=0x55632406a610, key=..., name=..., email=..., comment=...) at qgpgmeadduseridjob.cpp:82 Before that the stack consists of: (shortened) #33 src/widgets/widgets/qlineedit.cpp:318 #34 src/klineedit.cpp:371 #35 src/pimcommonakonadi/addressline/addresslineedit/addresseelineedit.cpp:249 #36 src/recipient/recipientline.cpp:169 #37 src/recipient/recipientline.cpp:135 #38 src/libkdepim/multiplyingline/multiplyinglineeditor.cpp:50 #39 src/recipient/recipientseditor.cpp:102 I think that this is an odd stack for an application startup. When I start KMail only, it also crashes and consists of this in the stack trace: (I have reformatted the lines to point at what DrKonqi presented me in red) #20 0x00007f1649f142af in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x560d43431dd0, m=m@entry=0x7f1649067800 <MessageComposer::RecipientLineNG::staticMetaObject>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x0) <=== argv=0x0 ? marked red by DrKonqi at src/corelib/kernel/qobject.cpp:3946 #21 0x00007f1648f5be03 in MessageComposer::RecipientLineNG::countChanged() (this=this@entry=0x560d43431dd0) at messagecomposer/src/KF5MessageComposer_autogen/LXYSN6NNNG/moc_recipientline.cpp:481 #22 0x00007f1648fb4ffe in MessageComposer::RecipientLineNG::analyzeLine(QString const&) (this=0x560d43431dd0, text=<optimized out>) at messagecomposer/src/recipient/recipientline.cpp:120 Why does starting kmail call the message composer at all? I ran "akonadictl fsck" and it found some items to clean up and scheduled some re-indexing. When the indexing agent finished, another run of "akonadictl fsck" did not find any issues. Kontact/Kmail are still crashing when starting. Once thing I forgot to mention: The crash happens even before a window shows up. I have resolved my issue: Nothing I found on the internet worked. Then I stumbled about a several year old post, where someone on a Kubuntu system suggested to purge sonnet. So I unmerged (deinstalled) kde-frameworks/sonnet-5.90.0 from my system. As several other packages where linked against /usr/lib64/libKF5SonnetCore.so.5.90.0 and /usr/lib64/libKF5SonnetUi.so.5.90.0, the Gentoo build manager Portage kept those libraries nevertheless. There is a special install target to rebuild those packages ("emerge @preserved-rebuild"), which I ran. It did not only re-install sonnet, but also rebuilt kde-frameworks/ktextwidgets-5.90.0 kde-apps/kpimtextedit-21.12.2 kde-apps/kanagram-21.12.2 kde-plasma/kdeplasma-addons-5.24.0 kde-plasma/kmenuedit-5.24.0 kde-plasma/plasma-desktop-5.24.0 kde-apps/libksieve-21.12.2 kde-apps/messagelib-21.12.2 kde-apps/ktp-text-ui-21.12.2 kde-apps/parley-21.12.2 kde-frameworks/khtml-5.90.0 kde-frameworks/ktexteditor-5.90.0 and finally: kde-apps/kmail-21.12.2 The next time I tried to start Kontact, it showed up, and opened dozens of windows with an empty e-mail to the person I originally tried to reply to. After I had closed (and discarded) all these windows, everything seemed to be fine. I am still testing, but it seems Kontact is back to normal. Oh boy I did not realize that reporting this crash via drkonqi would put the whole stacktrace in the body instead of an attachment... Either way I'll try and provide some additional information on top of the excellent work that Sven did. > When I start KMail only, it also crashes and consists of this in the stack trace After giving up on launching Kontact yesterday, I also tried just launching Kmail2 as a standalone and it crash as well. Both Kontact and Kmail2 segfaults before any window appears but after the launch feedback animation is triggered. So it must be happening very ealier in the execution of Kontact (or maybe even Kmail2 and it is killing Kontact with it). Question for the devs: Between my testing and Sven's it sounds like I may have incorrectly reported this and the real issue is Kmail2 and Kontact is just an innocent by standard being brought down with Kmail? > However, when I restart akonadi, I get notifications about new E-Mails Interestingly, the new E-Mail notification continued to work for me without having to restart akonadi, and it is working today after a full system reboot. Note, I have not tried uninstalling Sonnet like Sven has. Created attachment 146532 [details]
Stacktrace from just launching Kmail
This is the stacktrace I get when I just launch Kmail instead of Kontact.
If you want to start kmail/kontact again, you have to remove ~/.local/share/kmail2/autosave/ It saves the broken state and tries to restore it at start up. It's also not related to all email accounts, some just work like usual. (In reply to lod from comment #7) > If you want to start kmail/kontact again, you have to remove > ~/.local/share/kmail2/autosave/ > > It saves the broken state and tries to restore it at start up. It's also not > related to all email accounts, some just work like usual. Confirmed, this does allow me to launch Kontact/Kmail again. Should there be a guard against this causing Kmail/Kontact from segfaulting if it is unable to restore from whatever is stored there? Y'all have generated encryption keys in your “Identity”? If I set "no key" in the cryptography tab of my Identity, I can replay to mails again. This is probably the same bug as #449898 The issue just got fixed for me with a new Arch Kmail build: https://github.com/archlinux/svntogit-packages/commit/668bbeacd97d8f4cc0ec46a17198840e0fb39bc0 |