Bug 252043 - Meta key causes crash when setting keyboard shortcuts
Summary: Meta key causes crash when setting keyboard shortcuts
Status: RESOLVED DUPLICATE of bug 222189
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 1.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: System Settings Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-22 14:45 UTC by Jorge Adriano
Modified: 2010-11-15 21:40 UTC (History)
2 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 Jorge Adriano 2010-09-22 14:45:53 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.5.1 (KDE 4.5.1) "release 3"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.2-desktop i686
Distribution: "openSUSE 11.3 (i586)"

-- 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".

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[KCrash Handler]
#7  Private (this=0xbfe0e1d8, p=@0x0) at kernel/qvariant.h:352
#8  QVariant::QVariant (this=0xbfe0e1d8, p=@0x0) at kernel/qvariant.cpp:1395
#9  0xb66b4685 in QDBusPendingReplyData::argumentAt (this=0xbfe0e218, index=0) at qdbuspendingreply.cpp:268
#10 0xb75b3308 in argumentAt<0> (seq=..., comp=...) at /usr/include/QtDBus/qdbuspendingreply.h:174
#11 operator QDBusPendingReplyTypes::Select<0, bool, void, void, void, void, void, void, void>::Type (seq=..., comp=...) at /usr/include/QtDBus/qdbuspendingreply.h:184
#12 KGlobalAccel::isGlobalShortcutAvailable (seq=..., comp=...) at /usr/src/debug/kdelibs-4.5.1/kdeui/shortcuts/kglobalaccel.cpp:513
#13 0xb76d24a3 in KKeySequenceWidgetPrivate::conflictWithGlobalShortcuts (this=0x8352650, keySequence=...) at /usr/src/debug/kdelibs-4.5.1/kdeui/widgets/kkeysequencewidget.cpp:539
#14 0xb76d30a4 in KKeySequenceWidget::isKeySequenceAvailable (this=0x8216ca8, keySequence=...) at /usr/src/debug/kdelibs-4.5.1/kdeui/widgets/kkeysequencewidget.cpp:371
#15 0xb76d317e in KKeySequenceWidgetPrivate::doneRecording (this=0x8352650, validate=true) at /usr/src/debug/kdelibs-4.5.1/kdeui/widgets/kkeysequencewidget.cpp:504
#16 0xb76d330f in KKeySequenceButton::keyPressEvent (this=0x8352630, e=0xbfe0e8b4) at /usr/src/debug/kdelibs-4.5.1/kdeui/widgets/kkeysequencewidget.cpp:811
#17 0xb74d3d1c in KKeySequenceButton::event (this=0x8352630, e=0xbfe0e8b4) at /usr/src/debug/kdelibs-4.5.1/kdeui/widgets/kkeysequencewidget.cpp:719
#18 0xb6aa2c64 in QApplicationPrivate::notify_helper (this=0x807fa20, receiver=0x8352630, e=0xbfe0e8b4) at kernel/qapplication.cpp:4302
#19 0xb6aab598 in QApplication::notify (this=0xbfe0e778, receiver=0x8352630, e=0xbfe0e8b4) at kernel/qapplication.cpp:3765
#20 0xb751d361 in KApplication::notify (this=0xbfe0f2bc, receiver=0x8352630, event=0xbfe0e8b4) at /usr/src/debug/kdelibs-4.5.1/kdeui/kernel/kapplication.cpp:310
#21 0xb653ae0e in QCoreApplication::notifyInternal (this=0xbfe0f2bc, receiver=0x8352630, event=0xbfe0e8b4) at kernel/qcoreapplication.cpp:726
#22 0xb6aa03bd in sendSpontaneousEvent (receiver=0x8352630, event=0xbfe0e8b4) at ../../src/corelib/kernel/qcoreapplication.h:218
#23 qt_sendSpontaneousEvent (receiver=0x8352630, event=0xbfe0e8b4) at kernel/qapplication.cpp:5281
#24 0xb6b4fcf3 in QKeyMapper::sendKeyEvent (keyWidget=0x8352630, grab=true, type=QEvent::KeyPress, code=16781600, modifiers=) at kernel/qkeymapper_x11.cpp:1875
#25 0xb6b501c1 in QKeyMapperPrivate::translateKeyEvent (this=0x80b67a8, keyWidget=0x8352630, event=0xbfe0ef5c, grab=true) at kernel/qkeymapper_x11.cpp:1845
#26 0xb6b297ca in QApplication::x11ProcessEvent (this=0xbfe0f2bc, event=0xbfe0ef5c) at kernel/qapplication_x11.cpp:3406
#27 0xb6b53570 in x11EventSourceDispatch (s=0x8082be8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#28 0xb5e2fb49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb5e30350 in ?? () from /usr/lib/libglib-2.0.so.0
#30 0xb5e3060e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#31 0xb6566d4b in QEventDispatcherGlib::processEvents (this=0x8061d78, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#32 0xb6b5319a in QGuiEventDispatcherGlib::processEvents (this=0x8061d78, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0xb653a11d in QEventLoop::processEvents (this=0xbfe0f214, flags=...) at kernel/qeventloop.cpp:149
#34 0xb653a319 in QEventLoop::exec (this=0xbfe0f214, flags=...) at kernel/qeventloop.cpp:201
#35 0xb653ec70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#36 0xb6aa0164 in QApplication::exec () at kernel/qapplication.cpp:3581
#37 0x08056565 in _start ()

Possible duplicates by query: bug 251778, bug 214921.

Reported using DrKonqi
Comment 1 Vitor Boschi da Silva 2010-09-22 15:02:55 UTC
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 2 Dario Andres 2010-11-15 21:40:11 UTC
[Comment from a bug triager]
This issue is being tracked at bug 222189. Merging. Thanks

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