Bug 346186 - clicking systemsettings icon from the left panel (centered) crashed system settings. another click and it opens properly.
Summary: clicking systemsettings icon from the left panel (centered) crashed system se...
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.3.0
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi, triaged
: 345075 345759 346724 347261 348427 351909 354631 354973 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-04-14 19:50 UTC by Simon Andric
Modified: 2022-09-04 10:20 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Andric 2015-04-14 19:50:39 UTC
Application: systemsettings5 (5.2.2)

Qt Version: 5.4.1
Operating System: Linux 3.19.0-13-generic x86_64
Distribution: Ubuntu Vivid Vervet (development branch)

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

hello!

clicking systemsettings icon from the left panel (centered) crashed system settings. another click and it opens properly. this has happened only once to me for now, and on a newly installed daily image vivid-desktop-amd64.iso from 14-4-2015.

durin installation i turned on updating, but i didnt update after install (yet).

nice day Simon :)

ps. i also chose breze dark theme.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Sistemske nastavitve (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f139918f780 (LWP 1779))]

Thread 4 (Thread 0x7f1389ebf700 (LWP 1780)):
#0  0x00007f13958f68dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f139463bb72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f139463d64f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f138c40a099 in QXcbEventReader::run (this=0x24b2680) at qxcbconnection.cpp:1105
#4  0x00007f1395f77b0e in QThreadPrivate::start (arg=0x24b2680) at thread/qthread_unix.cpp:337
#5  0x00007f13935556aa in start_thread (arg=0x7f1389ebf700) at pthread_create.c:333
#6  0x00007f1395901eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f137a966700 (LWP 1781)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f137d9a34fb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x00007f137d9a2c87 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x00007f13935556aa in start_thread (arg=0x7f137a966700) at pthread_create.c:333
#4  0x00007f1395901eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f136142b700 (LWP 9879)):
#0  0x00007f139307b789 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f1393036dbd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f1393037242 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f1354557ae6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007f139305d955 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f13935556aa in start_thread (arg=0x7f136142b700) at pthread_create.c:333
#6  0x00007f1395901eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f139918f780 (LWP 1779)):
[KCrash Handler]
#6  0x00007f1396fcc4fd in maybeTopData (this=<optimized out>) at ../../include/QtWidgets/5.4.1/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:937
#7  QWidget::windowHandle (this=0x2584020) at kernel/qwidget.cpp:2570
#8  0x00007f1396fd3911 in QWidget::activateWindow (this=<optimized out>) at kernel/qwidget.cpp:12561
#9  0x00007f13961e635a in call (a=0x7fff66d17990, r=0x7fff66d183f0, this=0x250f540) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#10 QMetaObject::activate (sender=sender@entry=0x24fe770, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff66d17990) at kernel/qobject.cpp:3702
#11 0x00007f13961e7057 in QMetaObject::activate (sender=sender@entry=0x24fe770, m=m@entry=0x7f13980d0d00 <KDBusService::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff66d17990) at kernel/qobject.cpp:3582
#12 0x00007f1397ecb727 in KDBusService::activateRequested (this=this@entry=0x24fe770, _t1=..., _t2=...) at moc_kdbusservice.cpp:191
#13 0x00007f1397ec8186 in KDBusService::Activate (this=0x24fe770, platform_data=...) at ../../src/kdbusservice.cpp:191
#14 0x00007f1397ecb513 in KDBusServiceAdaptor::qt_metacall (this=0x24feb90, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff66d17b40) at kdbusservice_adaptor.moc:137
#15 0x00007f13992db5c7 in QDBusConnectionPrivate::deliverCall (this=0x2584020, object=0x250f540, msg=..., metaTypes=..., slotIdx=0) at qdbusintegrator.cpp:993
#16 0x00007f13992dfefc in QDBusConnectionPrivate::activateCall (this=0x2584020, this@entry=0x24f8f70, object=0x24feb90, flags=273, msg=...) at qdbusintegrator.cpp:898
#17 0x00007f13992e09bb in QDBusConnectionPrivate::activateObject (this=0x24f8f70, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1460
#18 0x00007f13992e27fe in QDBusActivateObjectEvent::placeMetaCall (this=0x45bf330) at qdbusintegrator.cpp:1582
#19 0x00007f13961e773a in QObject::event (this=0x24fe770, e=<optimized out>) at kernel/qobject.cpp:1245
#20 0x00007f1396fa0b2c in QApplicationPrivate::notify_helper (this=0x2497680, receiver=0x24fe770, e=0x45bf330) at kernel/qapplication.cpp:3720
#21 0x00007f1396fa6000 in QApplication::notify (this=0x7fff66d183f0, receiver=0x24fe770, e=0x45bf330) at kernel/qapplication.cpp:3503
#22 0x00007f13961b5c2b in QCoreApplication::notifyInternal (this=0x7fff66d183f0, receiver=0x24fe770, event=event@entry=0x45bf330) at kernel/qcoreapplication.cpp:935
#23 0x00007f13961b7c9b in sendEvent (event=0x45bf330, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x2496db0) at kernel/qcoreapplication.cpp:1552
#25 0x00007f13961b8298 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410
#26 0x00007f139620e843 in postEventSourceDispatch (s=0x24e21d0) at kernel/qeventdispatcher_glib.cpp:271
#27 0x00007f1393036c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f1393036f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f1393036fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f139620ec57 in QEventDispatcherGlib::processEvents (this=0x24e0230, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#31 0x00007f13961b33e2 in QEventLoop::exec (this=this@entry=0x7fff66d182d0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#32 0x00007f13961bb02c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#33 0x00007f13969db31c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#34 0x00007f1396f9c7a5 in QApplication::exec () at kernel/qapplication.cpp:2956
#35 0x000000000040eebc in main (argc=1, argv=<optimized out>) at ../../app/main.cpp:54

Reported using DrKonqi
Comment 1 Christoph Feck 2015-04-16 19:31:52 UTC
Do you remember which pages you visited? Or is this reproducible?
Comment 2 Simon Andric 2015-04-28 23:27:28 UTC
hello!

  i didnt visit any pages --- it means on internet, i just clicked on the system settings icon which i put in the left empty panel :-)

reproducible...am... i didnt see this again, but its also true right now i have a bit of a problem logging in plasma (#346778) so i use razor qt...

nice day

Simon :-)
Comment 3 Christoph Feck 2015-05-09 19:38:04 UTC
*** Bug 347261 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2015-05-09 19:38:25 UTC
*** Bug 346724 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2015-05-09 19:38:46 UTC
*** Bug 345759 has been marked as a duplicate of this bug. ***
Comment 6 Christoph Feck 2015-05-09 19:39:07 UTC
*** Bug 345075 has been marked as a duplicate of this bug. ***
Comment 7 Christoph Feck 2015-05-31 14:04:01 UTC
*** Bug 348427 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2015-09-03 09:38:32 UTC
*** Bug 351909 has been marked as a duplicate of this bug. ***
Comment 9 Albert Astals Cid 2015-09-26 11:39:56 UTC
Sorry i have trouble understanding what you mean by "clicking systemsettings icon from the left panel (centered) crashed system settings."

Does it mean:
 * You had systemsettings open and clicked somewhere? (where?)
 * You did not have systemsettings open and clicked somewhere to open it? (where?)
Comment 10 Christoph Feck 2015-11-16 01:32:43 UTC
*** Bug 354631 has been marked as a duplicate of this bug. ***
Comment 11 Christoph Feck 2015-11-16 01:33:08 UTC
*** Bug 354973 has been marked as a duplicate of this bug. ***
Comment 12 Andrew Crouthamel 2018-09-25 21:48:30 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 set the bug status 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 13 Andrew Crouthamel 2018-10-27 02:15:59 UTC
Dear Bug Submitter,

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!