Bug 346335

Summary: System Settings crash while editting Global Keyboard Shortcuts
Product: [Applications] systemsettings Reporter: Peter Cordes <peter>
Component: kcm_khotkeysAssignee: Michael Jansen <kde>
Status: RESOLVED DUPLICATE    
Severity: crash CC: christiandehne, eboracus, kozlik, nxiv, rahulprabhakarddun, sander, spengy, Tanktalus
Priority: NOR Keywords: drkonqi
Version: 5.2.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi

Description Peter Cordes 2015-04-18 13:20:18 UTC
Application: systemsettings5 (5.2.2)

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

-- Information about the crash:
- Custom settings of the application:

Added 
> Switch to Screen 0 = Meta+Shift+1
> Switch to Screen 2 = Meta+Shift+2  (I only have 2 screens, but I misclicked / forgot I'd started at 0.) 

I had compositing toggled off at the time, in case that matters.

I'm on a fresh install of Kubuntu 15.04.  I even moved aside my old dotfiles, so I don't have any old cruft causing problems.

- What I was doing when the application crashed:

I think I was trying out the keybinds to see if they did anything.  (They don't seem to, maybe because I have "focus follows mouse".  I was messing with this in the first place because I was looking a way to get "Window to Next Screen" but without changing focus.) 

So I think I had the default/custom radiobutton thing showing for the Switch to Screen 2 action, and maybe have hit escape or something by accident.  I think I saw a "are you sure you want to leave without applying?" dialog.  This is when System Settings crashed.

I can't reproduce it, but it may be that I just can't remember exactly what I did.

The crash does not seem to be reproducible.

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

Thread 4 (Thread 0x7f2af3ade700 (LWP 31071)):
#0  0x00007f2b00ac98dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f2afede3b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f2afede564f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f2af6029099 in QXcbEventReader::run (this=0x24beaf0) at qxcbconnection.cpp:1105
#4  0x00007f2b0114ab0e in QThreadPrivate::start (arg=0x24beaf0) at thread/qthread_unix.cpp:337
#5  0x00007f2afdcfd6aa in start_thread (arg=0x7f2af3ade700) at pthread_create.c:333
#6  0x00007f2b00ad4eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f2ae4820700 (LWP 31072)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f2ae785d4fb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x00007f2ae785cc87 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x00007f2afdcfd6aa in start_thread (arg=0x7f2ae4820700) at pthread_create.c:333
#4  0x00007f2b00ad4eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f2a927fb700 (LWP 24309)):
#0  0x00007f2afd8237a4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f2afd7de6f9 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f2afd7dee37 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2afd7df242 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f2acfa49ae6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x00007f2afd805955 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f2afdcfd6aa in start_thread (arg=0x7f2a927fb700) at pthread_create.c:333
#7  0x00007f2b00ad4eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f2b04362780 (LWP 31070)):
[KCrash Handler]
#6  QString (other=<error reading variable: Cannot access memory at address 0x73006e006f006b>, this=this@entry=0x7fffef6454d0) at ../../include/QtCore/../../src/corelib/tools/qstring.h:811
#7  QLabel::text (this=0x73006e006f0063) at widgets/qlabel.cpp:322
#8  0x00007f2b0331f741 in ShortcutEditWidget::setKeySequence (this=0x3691eb0, activeSeq=...) at ../../src/kshortcuteditwidget.cpp:187
#9  0x00007f2b013b935a in call (a=0x7fffef645620, r=0x7f2afe83a550 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, this=0x3037a50) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#10 QMetaObject::activate (sender=0x7f2afe83a550 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffef645620) at kernel/qobject.cpp:3702
#11 0x00007f2b013ba057 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f2afe839a00 <KGlobalAccel::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffef645620) at kernel/qobject.cpp:3582
#12 0x00007f2afe61e764 in KGlobalAccel::globalShortcutChanged (this=<optimized out>, _t1=0x3808970, _t2=...) at ./moc_kglobalaccel.cpp:158
#13 0x00007f2afe625da4 in KGlobalAccelPrivate::updateGlobalShortcut (this=0x25e5840, action=0x3808970, actionFlags=..., globalFlags=(unknown: 62479488)) at ../../src/kglobalaccel.cpp:320
#14 0x00007f2afe62685d in KGlobalAccel::setShortcut (this=0x7f2afe83a550 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, action=0x3808970, shortcut=..., loadFlag=KGlobalAccel::Autoloading) at ../../src/kglobalaccel.cpp:631
#15 0x00007f2a942780fc in KGlobalShortcutsEditor::KGlobalShortcutsEditorPrivate::loadComponent (this=0x7fffef6454d0, componentPath=...) at ../../../kcms/keys/kglobalshortcutseditor.cpp:624
#16 0x00007f2a9427a1e7 in KGlobalShortcutsEditor::load (this=0x2855000) at ../../../kcms/keys/kglobalshortcutseditor.cpp:464
#17 0x00007f2b02c67219 in KCModule::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at moc_kcmodule.cpp:107
#18 0x00007f2b013ba73a in QObject::event (this=this@entry=0x2b9f420, e=e@entry=0x27415d0) at kernel/qobject.cpp:1245
#19 0x00007f2b021b8377 in QWidget::event (this=0x2b9f420, event=0x27415d0) at kernel/qwidget.cpp:9083
#20 0x00007f2b02174b2c in QApplicationPrivate::notify_helper (this=0x24a3b10, receiver=0x2b9f420, e=0x27415d0) at kernel/qapplication.cpp:3720
#21 0x00007f2b0217a000 in QApplication::notify (this=0x7fffef646280, receiver=0x2b9f420, e=0x27415d0) at kernel/qapplication.cpp:3503
#22 0x00007f2b01388c2b in QCoreApplication::notifyInternal (this=0x7fffef646280, receiver=0x2b9f420, event=event@entry=0x27415d0) at kernel/qcoreapplication.cpp:935
#23 0x00007f2b0138ac9b in sendEvent (event=0x27415d0, 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=0x24a2d60) at kernel/qcoreapplication.cpp:1552
#25 0x00007f2b0138b298 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410
#26 0x00007f2b013e1843 in postEventSourceDispatch (s=0x24fe8f0) at kernel/qeventdispatcher_glib.cpp:271
#27 0x00007f2afd7dec3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f2afd7def20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f2afd7defcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f2b013e1c57 in QEventDispatcherGlib::processEvents (this=0x24f2480, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#31 0x00007f2b013863e2 in QEventLoop::exec (this=this@entry=0x7fffef646160, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#32 0x00007f2b0138e02c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#33 0x00007f2b01baf31c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#34 0x00007f2b021707a5 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-05-31 14:15:14 UTC
*** Bug 348249 has been marked as a duplicate of this bug. ***
Comment 2 Christoph Feck 2017-01-04 14:51:23 UTC
*** Bug 357862 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2017-06-26 16:40:40 UTC
*** Bug 381338 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2017-06-26 16:43:01 UTC
*** Bug 368017 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2017-06-26 16:43:27 UTC
*** Bug 373517 has been marked as a duplicate of this bug. ***
Comment 6 Sander 2017-09-25 10:36:37 UTC
Created attachment 108006 [details]
New crash information added by DrKonqi

kcmshell5 (5.10.5) using Qt 5.9.1

- What I was doing when the application crashed:
I opened up Global Shortcuts by searching this through the start menu. Following that I clicked on the component System Settings Module and here I selected Log out, clicked on None and entered the key combination Meta+L after which the crash occured. 

- Custom settings of the application:
Log Out was already set to Custom without a key combination (None). I think I crashed before but cannot seem to reproduce it after crashing.

- Extra info:
After the crash the new key combination seemed to have been set up. The key combination was set in the System Settings Module.

-- Backtrace (Reduced):
#6  0x00007fb88ad2e0b0 in QLabel::text() const () from /usr/lib64/libQt5Widgets.so.5
#7  0x00007fb8893552d6 in ShortcutEditWidget::setKeySequence (this=0x55732d913eb0, activeSeq=...) at /usr/src/debug/kxmlgui-5.37.0/src/kshortcuteditwidget.cpp:192
[...]
#9  0x00007fb8841ad544 in KGlobalAccel::globalShortcutChanged (this=this@entry=0x7fb8843c7590 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, _t1=<optimized out>, _t1@entry=0x55732d7a7a50, _t2=...) at /usr/src/debug/kglobalaccel-5.37.0/build/src/KF5GlobalAccel_autogen/include/moc_kglobalaccel.cpp:162
#10 0x00007fb8841affa7 in KGlobalAccelPrivate::_k_shortcutGotChanged (this=<optimized out>, actionId=..., keys=...) at /usr/src/debug/kglobalaccel-5.37.0/src/kglobalaccel.cpp:480
[...]
#12 0x00007fb8841bb4ce in OrgKdeKGlobalAccelInterface::yourShortcutGotChanged (_t2=..., _t1=..., this=<optimized out>) at /usr/src/debug/kglobalaccel-5.37.0/build/src/kglobalaccel_interface.moc:267
Comment 7 Christoph Feck 2017-11-10 01:28:57 UTC
*** Bug 386392 has been marked as a duplicate of this bug. ***
Comment 8 Ebo 2017-11-14 17:00:43 UTC
Created attachment 108862 [details]
New crash information added by DrKonqi

systemsettings5 (5.11.3) using Qt 5.9.2

KDE Plasma Version: 5.11.3

- What I was doing when the application crashed:

Freshly rebooted system, first act carried out...
Opened System Settings -> Global Shorcuts (from 'Frequently Used:' list)
  -> Opened Plasma shortcuts list
  -> Clicked on "Activate Application Dashboard Widget"
  -> Clicked on "Custom: None" and entered 'Alt + F1'
  -> Popup appeared (as expected) asking confirmation to override already assigned shorcut - clicked "Reassign" to confirm
  * Crash occurred

-- Backtrace (Reduced):
#5  0x00007ff8ba550ed0 in QLabel::text() const () at /usr/lib/libQt5Widgets.so.5
#6  0x00007ff8bba62797 in  () at /usr/lib/libKF5XmlGui.so.5
[...]
#8  0x00007ff8b5ab0505 in KGlobalAccel::globalShortcutChanged(QAction*, QKeySequence const&) () at /usr/lib/libKF5GlobalAccel.so.5
#9  0x00007ff8b5ab3694 in  () at /usr/lib/libKF5GlobalAccel.so.5
[...]
#11 0x00007ff8b5abf557 in  () at /usr/lib/libKF5GlobalAccel.so.5
Comment 9 Christoph Feck 2017-12-20 18:15:35 UTC
This could be fixed by commit for bug 387307. If this still occurs after Plasma 5.12 release late January, please add a comment.

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