Bug 344472 - SystemSettings crashes
Summary: SystemSettings crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_khotkeys (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords: drkonqi
: 355304 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-02-23 03:03 UTC by gahzinia
Modified: 2018-12-01 03:48 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (8.09 KB, text/plain)
2015-08-24 20:35 UTC, Fusl
Details
New crash information added by DrKonqi (7.95 KB, text/plain)
2015-08-27 20:29 UTC, Fusl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gahzinia 2015-02-23 03:03:11 UTC
Application: systemsettings (4.11.15)
KDE Platform Version: 4.14.4
Qt Version: 4.8.6
Operating System: Linux 3.18.6-200.fc21.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I had a keyboard shortcut setup (using launch 3 button to run a custom script). A few weeks ago, I ran yum update, rebooted, and then shortcut quit working. I downgraded the updated packages and was then able to reconfigure the shortcut. A few days ago I ran a yum update again hoping that whatever didn't work had been fixed. I did not reboot and all things kept working. I installed FlightGear and have had a few issues with that where 
$ fgfs --show-aircraft 
will core dump. That happened a year or so ago when I was playing Flight Gear and so that isn't related to the shortcut / yum update / downgrade issues. However, this time when I tried playing the game, the whole system would hang for 10 or 20 minutes and eventually out of memory. Well, while impatiently waiting for it oom or let me do anything (control alt f2-f7 wouldn't even work) I hit control alt backspace a few times and finally had to hold the power button. I think that it was after this that the shortcut quit working again. 
I haven't tried to yum downgrade again yet.

The crash can be reproduced sometimes.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fbc8f4129f1 in KHotKeys::ActionDataGroup::children() const () from /lib64/libkhotkeysprivate.so.4
#6  0x00007fbc8f6615f4 in KHotkeysModel::parent(QModelIndex const&) const () from /usr/lib64/kde4/kcm_hotkeys.so
#7  0x00007fbcb5e176ab in QPersistentModelIndex::parent() const () from /lib64/libQtCore.so.4
#8  0x00007fbcb703d84e in QItemSelection::merge(QItemSelection const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /lib64/libQtGui.so.4
#9  0x00007fbcb7040e44 in QItemSelectionModel::select(QItemSelection const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /lib64/libQtGui.so.4
#10 0x00007fbcb703bd78 in QItemSelectionModel::select(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /lib64/libQtGui.so.4
#11 0x00007fbcb703b0b2 in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /lib64/libQtGui.so.4
#12 0x00007fbcb6fe26e3 in QAbstractItemView::setCurrentIndex(QModelIndex const&) () from /lib64/libQtGui.so.4
#13 0x00007fbc8f65b9d1 in KCMHotkeys::showGlobalSettings() () from /usr/lib64/kde4/kcm_hotkeys.so
#14 0x00007fbcb5e3a25c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4
#15 0x00007fbcb5e18e84 in QAbstractItemModel::reset() () from /lib64/libQtCore.so.4
#16 0x00007fbc8f65c56b in KCMHotkeysPrivate::save() () from /usr/lib64/kde4/kcm_hotkeys.so
#17 0x00007fbc8f65cd9d in KCMHotkeys::save() () from /usr/lib64/kde4/kcm_hotkeys.so
#18 0x00007fbcb869f7a7 in KCModuleProxy::save() () from /lib64/libkcmutils.so.4
#19 0x00007fbcb8474213 in ModuleView::moduleSave(KCModuleProxy*) () from /lib64/libsystemsettingsview.so.2
#20 0x00007fbcb847689a in ModuleView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.31] () from /lib64/libsystemsettingsview.so.2
#21 0x00007fbcb5e3a25c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4
#22 0x00007fbcb714f252 in QAbstractButton::clicked(bool) () from /lib64/libQtGui.so.4
#23 0x00007fbcb6e8f363 in QAbstractButtonPrivate::emitClicked() () from /lib64/libQtGui.so.4
#24 0x00007fbcb6e907a4 in QAbstractButtonPrivate::click() () from /lib64/libQtGui.so.4
#25 0x00007fbcb6e908b4 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQtGui.so.4
#26 0x00007fbcb6b14118 in QWidget::event(QEvent*) () from /lib64/libQtGui.so.4
#27 0x00007fbcb6ac0efc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#28 0x00007fbcb6ac7abf in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#29 0x00007fbcb7a8c86a in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5
#30 0x00007fbcb5e2570d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4
#31 0x00007fbcb6ac711f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /lib64/libQtGui.so.4
#32 0x00007fbcb6b3d532 in QETWidget::translateMouseEvent(_XEvent const*) () from /lib64/libQtGui.so.4
#33 0x00007fbcb6b3bf2c in QApplication::x11ProcessEvent(_XEvent*) () from /lib64/libQtGui.so.4
#34 0x00007fbcb6b63fb4 in x11EventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQtGui.so.4
#35 0x00007fbcac058aeb in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#36 0x00007fbcac058e88 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#37 0x00007fbcac058f3c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#38 0x00007fbcb5e54a1e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#39 0x00007fbcb6b64136 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtGui.so.4
#40 0x00007fbcb5e24261 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#41 0x00007fbcb5e245c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#42 0x00007fbcb5e29ca9 in QCoreApplication::exec() () from /lib64/libQtCore.so.4
#43 0x000000000040a97f in main ()

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

Possible duplicates by query: bug 218447, bug 195232.

Reported using DrKonqi
Comment 1 Fusl 2015-08-24 20:35:44 UTC
Created attachment 94206 [details]
New crash information added by DrKonqi

kcmshell4 (4.14.6) on KDE Platform 4.14.9 using Qt 4.8.6

- What I was doing when the application crashed: / Unusual behavior I noticed:
I also have 2 custom shortcuts configured (Alt+Shift+3 (Alt+ยง) and Alt+Shift+4 (Alt+$)) that stopped working after upgrading the system with the openSUSUE package manager. I entered the system settings and wanted to try if disabling and re-enabling the shortcut fixes this issue and then stumbled upon this bug

-- Backtrace (Reduced):
#6  QList (l=..., this=0x7ffff4028870, this@entry=0x7ffff4028868) at /usr/include/QtCore/qlist.h:122
#7  KHotKeys::ActionDataGroup::children (this=0x40000000000072) at /usr/src/debug/kde-workspace-4.11.20/khotkeys/libkhotkeysprivate/action_data/action_data_group.cpp:147
#8  0x00007f89d6f545e4 in KHotkeysModel::parent (this=0xece2f0, index=...) at /usr/src/debug/kde-workspace-4.11.20/khotkeys/kcm_hotkeys/hotkeys_model.cpp:583
#9  0x00007f89f1ad7bf3 in parent (this=<optimized out>) at kernel/qabstractitemmodel.h:393
#10 QPersistentModelIndex::parent (this=this@entry=0xd9d9a8) at kernel/qabstractitemmodel.cpp:347
Comment 2 Fusl 2015-08-27 20:29:07 UTC
Created attachment 94253 [details]
New crash information added by DrKonqi

kcmshell4 (4.14.6) on KDE Platform 4.14.9 using Qt 4.8.6

- What I was doing when the application crashed:
I tried to work around this bug by re-assigning the shortcut to Print and Shift+Print but this also crashed the application when I clicked save.

-- Backtrace (Reduced):
#6  QList (l=..., this=0x7ffceff36460, this@entry=0x7ffceff36458) at /usr/include/QtCore/qlist.h:122
#7  KHotKeys::ActionDataGroup::children (this=0x40000000000072) at /usr/src/debug/kde-workspace-4.11.20/khotkeys/libkhotkeysprivate/action_data/action_data_group.cpp:147
#8  0x00007fe972a655e4 in KHotkeysModel::parent (this=0x14279a0, index=...) at /usr/src/debug/kde-workspace-4.11.20/khotkeys/kcm_hotkeys/hotkeys_model.cpp:583
#9  0x00007fe98d5e8bf3 in parent (this=<optimized out>) at kernel/qabstractitemmodel.h:393
#10 QPersistentModelIndex::parent (this=this@entry=0x17c7368) at kernel/qabstractitemmodel.cpp:347
Comment 3 Christoph Feck 2015-11-16 01:49:57 UTC
*** Bug 355304 has been marked as a duplicate of this bug. ***
Comment 4 Andrew Crouthamel 2018-11-01 13:40:49 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 gahzinia 2018-11-01 14:04:35 UTC
I don't use the systemsettings too much, so I haven't had any issues recently. Possibly Fusl still does?
Comment 6 Bug Janitor Service 2018-11-16 11:34: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 7 Bug Janitor Service 2018-12-01 03:48:33 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!