Bug 414032

Summary:	Labplot crash
Product:	[Applications] LabPlot2	Reporter:	gojgl <bojan007>
Component:	general	Assignee:	Alexander Semke <alexander.semke>
Status:	RESOLVED DUPLICATE
Severity:	crash	Keywords:	drkonqi
Priority:	NOR
Version First Reported In:	2.7.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	attachment-26393-0.html

Description gojgl 2019-11-11 16:18:42 UTC

Application: labplot2 (2.7.0)

Qt Version: 5.13.1
Frameworks Version: 5.64.0
Operating System: Linux 4.12.14-lp151.28.25-default x86_64
Distribution: "openSUSE Leap 15.1"

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

start application, crash immediately afterwards
crash again on restart, several times

The crash can be reproduced every time.

-- Backtrace:
Application: LabPlot (labplot2), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fec99896940 (LWP 6562))]

Thread 2 (Thread 0x7fec7af55700 (LWP 6565)):
#0  0x00007fec9248a19b in poll () from /lib64/libc.so.6
#1  0x00007fec8cb901a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fec8cb902bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fec9453577b in QEventDispatcherGlib::processEvents (this=0x7fec74000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007fec944d5c4a in QEventLoop::exec (this=this@entry=0x7fec7af54c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x00007fec942f110a in QThread::exec (this=<optimized out>) at thread/qthread.cpp:531
#6  0x00007fec90dfcdb5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x00007fec942f28b2 in QThreadPrivate::start (arg=0x7fec91074d80) at thread/qthread_unix.cpp:360
#8  0x00007fec92185569 in start_thread () from /lib64/libpthread.so.0
#9  0x00007fec924949ef in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fec99896940 (LWP 6562)):
[KCrash Handler]
#6  0x00007fec96ab5421 in ?? () from /usr/lib64/libKF5ConfigWidgets.so.5
#7  0x00007fec945085cf in QtPrivate::QSlotObjectBase::call (a=0x7ffd9768d600, r=0x55e42b322ff0, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#8  QMetaObject::activate (sender=sender@entry=0x55e42b2e7bd0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=<optimized out>, argv@entry=0x0) at kernel/qobject.cpp:3789
#9  0x00007fec94508b77 in QMetaObject::activate (sender=sender@entry=0x55e42b2e7bd0, m=m@entry=0x7fec96042720 <QMenu::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3660
#10 0x00007fec95acdd00 in QMenu::aboutToShow (this=this@entry=0x55e42b2e7bd0) at .moc/moc_qmenu.cpp:270
#11 0x00007fec95ad2657 in QMenu::popup (this=0x55e42b2e7bd0, p=..., atAction=atAction@entry=0x0) at widgets/qmenu.cpp:2360
#12 0x00007fec95ad4ff4 in QMenu::internalDelayedPopup (this=0x55e42b18cf90) at widgets/qmenu.cpp:3616
#13 0x00007fec94508fcb in QObject::event (this=this@entry=0x55e42b18cf90, e=e@entry=0x7ffd9768dbf0) at kernel/qobject.cpp:1282
#14 0x00007fec9599c49b in QWidget::event (this=this@entry=0x55e42b18cf90, event=event@entry=0x7ffd9768dbf0) at kernel/qwidget.cpp:9405
#15 0x00007fec95ad9dab in QMenu::event (this=0x55e42b18cf90, e=0x7ffd9768dbf0) at widgets/qmenu.cpp:3029
#16 0x00007fec9595b03c in QApplicationPrivate::notify_helper (this=this@entry=0x55e42af0f3f0, receiver=receiver@entry=0x55e42b18cf90, e=e@entry=0x7ffd9768dbf0) at kernel/qapplication.cpp:3703
#17 0x00007fec95962640 in QApplication::notify (this=0x7ffd9768dfa0, receiver=0x55e42b18cf90, e=0x7ffd9768dbf0) at kernel/qapplication.cpp:3449
#18 0x00007fec944d7ae8 in QCoreApplication::notifyInternal2 (receiver=0x55e42b18cf90, event=0x7ffd9768dbf0) at kernel/qcoreapplication.cpp:1095
#19 0x00007fec94534be9 in QTimerInfoList::activateTimers (this=0x55e42aff0b50) at kernel/qtimerinfo_unix.cpp:643
#20 0x00007fec945353b1 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#21 0x00007fec8cb8fe87 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fec8cb90230 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fec8cb902bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007fec9453575f in QEventDispatcherGlib::processEvents (this=0x55e42afe9420, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#25 0x00007fec944d5c4a in QEventLoop::exec (this=this@entry=0x7ffd9768de40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#26 0x00007fec944defc0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1403
#27 0x000055e429ee6ca3 in ?? ()
#28 0x00007fec923bcf8a in __libc_start_main () from /lib64/libc.so.6
#29 0x000055e429ee91fa in _start ()
[Inferior 1 (process 6562) detached]

Possible duplicates by query: bug 413345, bug 412455, bug 412296, bug 411883, bug 411375.

Reported using DrKonqi

Comment 1 Alexander Semke 2019-11-12 20:44:47 UTC

(In reply to gojgl from comment #0)
> start application, crash immediately afterwards
> crash again on restart, several times

Does this really happen on start or only when you go to the Settings/ColorTheme menu as described in bug 412455.

Comment 2 gojgl 2019-11-13 06:51:08 UTC

Created attachment 123882 [details]
attachment-26393-0.html

Yes, you are right. I checked again and it crashes on Settings/ColorTheme.

On Tue, 12 Nov 2019 at 21:44, Alexander Semke <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=414032
>
> --- Comment #1 from Alexander Semke <alexander.semke@web.de> ---
> (In reply to gojgl from comment #0)
> > start application, crash immediately afterwards
> > crash again on restart, several times
>
> Does this really happen on start or only when you go to the
> Settings/ColorTheme
> menu as described in bug 412455.
>
> --
> You are receiving this mail because:
> You reported the bug.

Comment 3 Alexander Semke 2019-11-13 11:43:51 UTC

(In reply to gojgl from comment #2)
> Created attachment 123882 [details]
> attachment-26393-0.html
> 
> Yes, you are right. I checked again and it crashes on Settings/ColorTheme.
Thanks for the confirmation. I'll mark this bug report as a duplicate of another  report we have already. We'll check this. Please avoid using this sub-menu until then. Thanks again for your feedback.

*** This bug has been marked as a duplicate of bug 412455 ***