Bug 222189 - SystemSettings crashed while editing Input Actions / KMix crashes when editing global shortcuts [QVariant, QDBusPendingReply, KGlobalAccel::isGlobalShortcutAvailable, KKeySequenceWidgetPrivate::conflictWithGlobalShortcuts]
Summary: SystemSettings crashed while editing Input Actions / KMix crashes when editin...
Status: REOPENED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: shortcuts (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: HI crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 228841 238196 247508 251777 252043 259786 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-01-11 09:34 UTC by Chris Gibbs
Modified: 2023-03-21 03:33 UTC (History)
14 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Trying to assign a shortcut to the Hyper Key (2.75 KB, image/png)
2021-02-11 07:29 UTC, wilo108 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Gibbs 2010-01-11 09:34:26 UTC 
Application that crashed: systemsettings
Version of the application: 1.0
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-3.slh.1-sidux-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
I was editing Input Actions to add quick keyboard shortcuts in "Preset Actions" - adding a shortcut to launch Iceweasel using the keybinding meta+w, but it kept showing up as gibberish (squares of differeing sizes) followed by a comma, then Meta+W,Meta+ ...

Soon after this, the application crashed, with the following output.

 -- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[KCrash Handler]
#5  Private (this=0x7fff5e953b80, p=...) at ../../include/QtCore/../../src/corelib/kernel/qvariant.h:343
#6  QVariant (this=0x7fff5e953b80, p=...) at kernel/qvariant.cpp:1371
#7  0x00007f25e942ec3c in QDBusPendingReplyData::argumentAt (this=0x7fff5e953bf0, index=<value optimized out>) at qdbuspendingreply.cpp:268
#8  0x00007f25ea949904 in argumentAt<0> (seq=<value optimized out>, comp=<value optimized out>) at /usr/include/qt4/QtDBus/qdbuspendingreply.h:174
#9  QDBusPendingReply<bool, void, void, void, void, void, void, void>::operator bool (seq=<value optimized out>, comp=<value optimized out>) at /usr/include/qt4/QtDBus/qdbuspendingreply.h:184
#10 KGlobalAccel::isGlobalShortcutAvailable (seq=<value optimized out>, comp=<value optimized out>) at ../../kdeui/shortcuts/kglobalaccel.cpp:483
#11 0x00007f25ea9c10f1 in KKeySequenceWidgetPrivate::conflictWithGlobalShortcuts (this=0x1e43570, keySequence=...) at ../../kdeui/widgets/kkeysequencewidget.cpp:513
#12 0x00007f25ea9c2214 in KKeySequenceWidget::isKeySequenceAvailable (this=0x1e386b0, keySequence=...) at ../../kdeui/widgets/kkeysequencewidget.cpp:358
#13 0x00007f25ea9c22d3 in KKeySequenceWidgetPrivate::doneRecording (this=0x1e43570, validate=true) at ../../kdeui/widgets/kkeysequencewidget.cpp:490
#14 0x00007f25ea9c247e in KKeySequenceWidget::qt_metacall (this=0x1e386b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5e953e10) at ./kkeysequencewidget.moc:94
#15 0x00007f25e90f0df2 in QMetaObject::activate (sender=0x1e435a0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x60fdc0) at kernel/qobject.cpp:3112
#16 0x00007f25e90eb353 in QObject::event (this=0x1e435a0, e=0x0) at kernel/qobject.cpp:1074
#17 0x00007f25e9cac01d in QApplicationPrivate::notify_helper (this=0x1804ca0, receiver=0x1e435a0, e=0x7fff5e9544c0) at kernel/qapplication.cpp:4065
#18 0x00007f25e9cb407a in QApplication::notify (this=0x7fff5e954820, receiver=0x1e435a0, e=0x7fff5e9544c0) at kernel/qapplication.cpp:4030
#19 0x00007f25ea903e06 in KApplication::notify (this=0x7fff5e954820, receiver=0x1e435a0, event=0x7fff5e9544c0) at ../../kdeui/kernel/kapplication.cpp:302
#20 0x00007f25e90dbc9c in QCoreApplication::notifyInternal (this=0x7fff5e954820, receiver=0x1e435a0, event=0x7fff5e9544c0) at kernel/qcoreapplication.cpp:610
#21 0x00007f25e91082c6 in QCoreApplication::sendEvent (this=0x1808230) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#22 QTimerInfoList::activateTimers (this=0x1808230) at kernel/qeventdispatcher_unix.cpp:580
#23 0x00007f25e9104658 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#24 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#25 0x00007f25e5aa68fe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x00007f25e5aaa2b8 in ?? () from /lib/libglib-2.0.so.0
#27 0x00007f25e5aaa3e0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x00007f25e910439c in QEventDispatcherGlib::processEvents (this=0x17d8e60, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#29 0x00007f25e9d42f1f in QGuiEventDispatcherGlib::processEvents (this=0x7fff5e953b80, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x00007f25e90da562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#31 0x00007f25e90da934 in QEventLoop::exec (this=0x7fff5e954770, flags=...) at kernel/qeventloop.cpp:201
#32 0x00007f25e90dcba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x000000000040cbb9 in _start ()

Reported using DrKonqi
Comment 1 Christian Herzberg 2010-02-28 02:57:37 UTC 
This bug may be a duplicate of or related to bug 228841
Comment 2 Christoph Feck 2010-03-02 04:24:06 UTC 
*** Bug 228841 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2010-05-20 19:35:22 UTC 
*** Bug 238196 has been marked as a duplicate of this bug. ***
Comment 4 Nicolas L. 2010-08-12 14:18:48 UTC 
*** Bug 247508 has been marked as a duplicate of this bug. ***
Comment 5 Dario Andres 2010-11-15 21:35:32 UTC 
[Comment from a bug triager]
From bug 251777:
-- Information about the crash:
Setting the VolumeDown shortcut to win-D produced resulted in a box showing
"[][][][][]" where all symbols were boxes and some were superscript. That is,
the shortcut setter thought I was pressing the key "[][][][][]". Setting
VolumeUp to win-F produces the same box. I can only assume that "[][][][][]" is
synonymous with the win key. This is what xev outputs:

KeyRelease event, serial 33, synthetic NO, window 0x2600001,
    root 0x1ad, subw 0x0, time 12854160, (145,1), root:(1801,24),
    state 0x40, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

After doing this twice, kmix always crashes.
Comment 6 Dario Andres 2010-11-15 21:36:02 UTC 
*** Bug 251777 has been marked as a duplicate of this bug. ***
Comment 7 Dario Andres 2010-11-15 21:40:02 UTC 
From bug 252043:
-- Information about the crash:
- How to reproduce:
Edit -> New -> Command Shortcut -> URL -> Trigger (tab)
Shortcut : press Meta Alt (conflic with hotkeys message), cancel
Shortcut : press Meta Alt (crash, as soon as you press Meta)
- Also weird:
pressing the Meta key, shows some weird square symbols instead of "Meta".
...
Tried on my box (KDE 4.5.1), Fedora 13 64 bits and it worked fine. Meta is
correctly displayed and there's no crash.
Comment 8 Dario Andres 2010-11-15 21:40:12 UTC 
*** Bug 252043 has been marked as a duplicate of this bug. ***
Comment 9 Jorge Adriano 2010-11-15 21:50:23 UTC 
Note regarding the bug I reported. I cannot reproduce this crash anymore:

(In reply to comment #7)
> From bug 252043:
> -- Information about the crash:
> - How to reproduce:
> Edit -> New -> Command Shortcut -> URL -> Trigger (tab)
> Shortcut : press Meta Alt (conflic with hotkeys message), cancel

No error message. 

> Shortcut : press Meta Alt (crash, as soon as you press Meta)

And there is no crash anymore. 

> - Also weird:
> pressing the Meta key, shows some weird square symbols instead of "Meta".

This still happens.

J.A.

> ...
> Tried on my box (KDE 4.5.1), Fedora 13 64 bits and it worked fine. Meta is
> correctly displayed and there's no crash.
Comment 10 Myriam Schweingruber 2010-12-15 02:52:56 UTC 
*** Bug 259786 has been marked as a duplicate of this bug. ***
Comment 11 Andrew Crouthamel 2018-10-31 03:57:25 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 12 Bug Janitor Service 2018-11-15 10:32:42 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 13 Bug Janitor Service 2018-11-30 03:46:46 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!
Comment 14 wilo108 2021-02-11 07:29:20 UTC 
Created attachment 135589 [details]
Trying to assign a shortcut to the Hyper Key
Comment 15 wilo108 2021-02-11 07:30:36 UTC 
> > - Also weird:
> > pressing the Meta key, shows some weird square symbols instead of "Meta".


> This still happens.

I"m seeing this behaviour today on Plasma 5.20.5.  Can this be reopened?
Comment 16 Mosin 2021-04-25 02:59:27 UTC 
(In reply to wilo108 from comment #14)
> Created attachment 135589 [details]
> Trying to assign a shortcut to the Hyper Key

The issue with hyper has been happening to me for a long time on multiple systems. I'd like for this issue to be reopened and renamed since there's no crash.
Comment 17 Daniel 2022-02-09 01:34:10 UTC 
(In reply to Mosin from comment #16)
> The issue with hyper has been happening to me for a long time on multiple
> systems…
Same for me. I am using a custom symbols-file in /usr/share/X11/xkb/symbols/ based on the us intl layout which is working as expected but in Plasma. I put the Hyper_L symbol to all eight levels of caps lock. It automatically works the same as Meta (aka Super, not Alt!) does but adding new shortcuts does not work.

The systemsettings do not crash but the input breaks after hitting the capslock-key and saves to the `~/.config/kglobalshortcutsrc` look like
> switch-to-activity-4e86aa4e-0a7c-4a4b-82b8-c6298a5a46f9=ៀ?,none,Switch to activity
This shortcut does not work (and should not as the Meta-Behaviour is copied and opens the application dashboard)
Comment 18 Keith Ferney 2022-05-05 22:42:15 UTC 
(In reply to wilo108 from comment #15)
> > > - Also weird:
> > > pressing the Meta key, shows some weird square symbols instead of "Meta".
> 
> 
> > This still happens.
> 
> I"m seeing this behaviour today on Plasma 5.20.5.  Can this be reopened?

I'm also seeing this behavior on Plasma 5.25.4
Comment 19 Daniel 2022-05-06 07:56:27 UTC 
This has to be resolved in Qt, see https://bugreports.qt.io/browse/QTBUG-61301?focusedCommentId=388466