Bug 423904

Summary: KMail crashes while gmail-sync
Product: [Applications] kmail2 Reporter: Peter Huyoff <peter.huyoff>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Peter Huyoff 2020-07-05 14:51:00 UTC 
Application: kmail (5.14.2 (20.04.2))

Qt Version: 5.15.0
Frameworks Version: 5.71.0
Operating System: Linux 5.7.5-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

Before this crash, akonadi crashes multiple times. KMail runned then with empty Screen and aconadictl -fsck has corrected a lot of issuses.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=<error reading variable: Cannot access memory at address 0x100>) at /usr/include/c++/10/bits/atomic_base.h:420
#5  QAtomicOps<int>::loadRelaxed<int> (_q_value=<error reading variable: Cannot access memory at address 0x100>) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger<int>::loadRelaxed (this=<error reading variable: Cannot access memory at address 0x100>) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QtPrivate::RefCount::isShared (this=<error reading variable: Cannot access memory at address 0x100>) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101
#8  QList<QWidget*>::append (this=0x100, t=@0x7ffe166e43a0: 0x55a57f76ff70) at ../../include/QtCore/../../src/corelib/tools/qlist.h:622
#9  0x00007ff70b3aeba0 in QWidget::insertAction (this=this@entry=0x55a57f76ff70, before=<optimized out>, before@entry=0x0, action=0x55a57f6352b0) at kernel/qwidget.cpp:3130
#10 0x00007ff70a12c35b in KXMLGUI::ActionList::plug (index=<optimized out>, container=0x55a57f76ff70, this=0x55a57f6868a0) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:45
#11 KXMLGUI::ContainerNode::plugActionList (mergingIdxIt=<synthetic pointer>..., mergingIdxIt=<synthetic pointer>..., state=..., this=0x55a57f7185b0) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:234
#12 KXMLGUI::ContainerNode::plugActionList (this=0x55a57f7185b0, state=...) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:204
#13 0x00007ff70a12c3e1 in KXMLGUI::ContainerNode::plugActionList (this=0x55a57f640700, state=...) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:208
#14 0x00007ff70a12c3e1 in KXMLGUI::ContainerNode::plugActionList (this=0x55a57f686630, state=...) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:208
#15 0x00007ff70a133721 in KXMLGUIFactory::plugActionList (this=0x55a57f8d8c80, client=0x7ff6f0008110, name=..., actionList=...) at /usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory.cpp:574
#16 0x00007ff7091ecf50 in PimCommon::PluginInterface::initializePluginActions (this=0x7ffe166e46f0, prefix=..., guiClient=0x7ff6f0008110) at /usr/src/debug/pimcommon-20.04.2-1.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:168
#17 0x00007ff70bb65900 in KMMainWidget::initializePluginActions (this=0x55a5830f7b30) at /usr/src/debug/kmail-20.04.2-1.1.x86_64/src/kmmainwidget.cpp:4217
#18 0x00007ff70bb6c574 in KMMainWidget::slotShowStartupFolder (this=0x55a5830f7b30) at /usr/src/debug/kmail-20.04.2-1.1.x86_64/src/kmmainwidget.cpp:4121
#19 0x00007ff70a84da31 in QObject::event (this=0x55a5830f7b30, e=0x55a57f7d5220) at kernel/qobject.cpp:1314
#20 0x00007ff70b3780cf in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55a5830f7b30, e=0x55a57f7d5220) at kernel/qapplication.cpp:3671
#21 0x00007ff70a821b0a in QCoreApplication::notifyInternal2 (receiver=0x55a5830f7b30, event=0x55a57f7d5220) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325
#22 0x00007ff70a824531 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55a57ee1a510) at kernel/qcoreapplication.cpp:1815
#23 0x00007ff70a8798c3 in postEventSourceDispatch (s=0x55a57ef37e70) at kernel/qeventdispatcher_glib.cpp:277
#24 0x00007ff70755f2c7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#25 0x00007ff70755f648 in ?? () from /usr/lib64/libglib-2.0.so.0
#26 0x00007ff70755f6ff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#27 0x00007ff70a878f4f in QEventDispatcherGlib::processEvents (this=0x55a57ef3f840, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x00007ff70a8204cb in QEventLoop::exec (this=this@entry=0x7ffe166e4b90, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141
#29 0x00007ff70a828730 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x000055a57ec92386 in main (argc=<optimized out>, argv=<optimized out>) at /usr/include/qt5/QtCore/qcoreapplication.h:116
[Inferior 1 (process 12275) detached]

Possible duplicates by query: bug 422092, bug 421432, bug 420495, bug 419785, bug 418784.

Reported using DrKonqi
Comment 1 Justin Zobel 2022-10-12 03:49:42 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 Peter Huyoff 2022-10-12 03:57:32 UTC 
With the actual version of KMail, this bug doesn't exist.

12.10.2022 05:49:46 Justin Zobel <bugzilla_noreply@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=423904
> 
> Justin Zobel <justin.zobel@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
> 
> --- Comment #1 from Justin Zobel <justin.zobel@gmail.com> ---
> 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!
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 3 Bug Janitor Service 2022-10-27 05:04:12 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 4 Bug Janitor Service 2022-11-11 05:20:54 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!