Bug 423173 - Kontact crashes while composing mails with attachment
Summary: Kontact crashes while composing mails with attachment
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-06-18 17:05 UTC by forenkram
Modified: 2022-10-27 05:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description forenkram 2020-06-18 17:05:29 UTC
Application: kontact (5.14.2 (20.04.2))

Qt Version: 5.15.0
Frameworks Version: 5.71.0
Operating System: Linux 5.7.2-arch1-1 x86_64
Windowing system: X11
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Composing mails with pdf attachment
- Unusual behavior I noticed: Kontact crashes after a while. I was able to compose several messages, but kontact kept crashing after a while. 

- Custom settings of the application:
recently readded gmail accounts and aconadi keept asking to login to google. Might be related to that. 
On the other hand, I disabled the gmail authentication resetting the password to PLAIN and kontact keeps crashing

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted

[KCrash Handler]
#4  0x00007f7334e2c355 in raise () from /usr/lib/libc.so.6
#5  0x00007f7334e15853 in abort () from /usr/lib/libc.so.6
#6  0x00007f733506786a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#7  0x00007f7335073d8a in __cxxabiv1::__terminate (handler=<optimized out>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#8  0x00007f7335073df7 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
#9  0x00007f733507409e in __cxxabiv1::__cxa_throw (obj=<optimized out>, tinfo=0x7f72c5391798 <typeinfo for Xapian::DatabaseModifiedError>, dest=0x7f72c4e7f430) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95
#10 0x00007f72c4e13f80 in ?? () from /usr/lib/libxapian.so.30
#11 0x00007f72c4e142be in ?? () from /usr/lib/libxapian.so.30
#12 0x00007f72c4ed7c75 in ?? () from /usr/lib/libxapian.so.30
#13 0x00007f72c4ed8321 in ?? () from /usr/lib/libxapian.so.30
#14 0x00007f72c4ec86e8 in ?? () from /usr/lib/libxapian.so.30
#15 0x00007f72c4e2f475 in Xapian::Database::get_termfreq(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const () from /usr/lib/libxapian.so.30
#16 0x00007f72c538a12b in ?? () from /usr/lib/libKF5AkonadiSearchPIM.so.5
#17 0x00007f72c538a286 in ?? () from /usr/lib/libKF5AkonadiSearchPIM.so.5
#18 0x00007f72c614b065 in ?? () from /usr/lib/libkmailprivate.so.5
#19 0x00007f7335499906 in ?? () from /usr/lib/libQt5Core.so.5
#20 0x00007f73364f6d0d in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/libKF5CoreAddons.so.5
#21 0x00007f73364f782c in KJob::finishJob(bool) () from /usr/lib/libKF5CoreAddons.so.5
#22 0x00007f733548f0b2 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#23 0x00007f7335f30702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#24 0x00007f733546269a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#25 0x00007f7335465183 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#26 0x00007f73354bbbd4 in ?? () from /usr/lib/libQt5Core.so.5
#27 0x00007f73335e643c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0x00007f7333633fa9 in ?? () from /usr/lib/libglib-2.0.so.0
#29 0x00007f73335e5221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0x00007f73354bb211 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#31 0x00007f733546101c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#32 0x00007f73354694a4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#33 0x0000561cc5103163 in ?? ()
#34 0x00007f7334e17002 in __libc_start_main () from /usr/lib/libc.so.6
#35 0x0000561cc51037ae in ?? ()
[Inferior 1 (process 88839) detached]

The reporter indicates this bug may be a duplicate of or related to bug 414838.

Possible duplicates by query: bug 422433, bug 422017, bug 418277, bug 417863, bug 415068.

Reported using DrKonqi
Comment 1 Justin Zobel 2022-10-12 03:50:10 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 2 forenkram 2022-10-12 04:36:28 UTC
(In reply to Justin Zobel from comment #1)
> Thank you for reporting this crash in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the crash with a recent software version?
> 
> If you can reproduce the issue, please change the status to "CONFIRMED" when
> replying. Thank you!

Thank you for replying.
I think the bug does not exist anymore in recent versions.
Cheers
Comment 3 Bug Janitor Service 2022-10-27 05:03:57 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!