Summary: | Global Keyboard Shortcuts in KDE Control Module crashes after typing search term and pressing "Enter" | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | anidev <anidev.aelico> |
Component: | kcm_keys | Assignee: | Michael Jansen <kde> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | cfeck, genjet, jlp, lfpg.dev, mail, nate, niklas, oded, theo.costea, zorael |
Priority: | NOR | ||
Version: | 4.10.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
anidev
2011-06-05 19:57:53 UTC
Does the crash also happen if you use a different widget style, such as Plastique? It could be related to Oxygen (animations). Reproducible using both Cleanlooks and Plastique styles. Created attachment 62154 [details]
New crash information added by DrKonqi
kcmshell4 () on KDE Platform 4.6.4 (4.6.4) using Qt 4.7.2
- What I was doing when the application crashed:
I opened Global Keyboard Shortcuts kcm module, selected a different component and then hit close.
- Custom settings of the application:
I'm running KDE with the graphics system set to raster.
-- Backtrace (Reduced):
#6 isWidgetType (this=0x1ac2c50) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:156
#7 QWidget::ensurePolished (this=0x1ac2c50) at kernel/qwidget.cpp:9602
#8 0x00007f788257e877 in QWidgetPrivate::activateChildLayoutsRecursively (this=0x1af10b0) at kernel/qwidget.cpp:7354
#9 0x00007f788257e89f in QWidgetPrivate::activateChildLayoutsRecursively (this=0x1a948f0) at kernel/qwidget.cpp:7367
#10 0x00007f788257e89f in QWidgetPrivate::activateChildLayoutsRecursively (this=0x1a944e0) at kernel/qwidget.cpp:7367
*** Bug 282879 has been marked as a duplicate of this bug. *** Created attachment 68397 [details]
New crash information added by DrKonqi
kcmshell4 () on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0
- What I was doing when the application crashed:
I used "search" in Global Keyboard Shortcuts. I then changed some shortcut and pressed Enter for OK .
-- Backtrace (Reduced):
#6 isWidgetType (this=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:146
#7 QWidget::ensurePolished (this=0x1580730) at kernel/qwidget.cpp:9704
#8 0x00007f93b77c1d84 in QWidgetPrivate::activateChildLayoutsRecursively (this=0x15ac2c0) at kernel/qwidget.cpp:7456
#9 0x00007f93b77c1dac in QWidgetPrivate::activateChildLayoutsRecursively (this=0x1558a80) at kernel/qwidget.cpp:7469
#10 0x00007f93b77c1dac in QWidgetPrivate::activateChildLayoutsRecursively (this=0x1558880) at kernel/qwidget.cpp:7469
*** Bug 293950 has been marked as a duplicate of this bug. *** *** Bug 294170 has been marked as a duplicate of this bug. *** *** Bug 310832 has been marked as a duplicate of this bug. *** Created attachment 75842 [details]
New crash information added by DrKonqi
kcmshell4 () on KDE Platform 4.9.90 using Qt 4.8.4
- What I was doing when the application crashed:
Using KDE 4.9.90 (4.10 beta2), Qt 4.8.4
It is every time reproducible here by simply opening the dialog and then closing it again (Ok, Cancel or ESC), nothing else is required to make it crash.
-- Backtrace (Reduced):
#6 isWidgetType (this=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:146
#7 QWidget::ensurePolished (this=0x8eab90) at kernel/qwidget.cpp:9729
#8 0x00007f3c9a115414 in QWidgetPrivate::activateChildLayoutsRecursively (this=0x99bea0) at kernel/qwidget.cpp:7470
#9 0x00007f3c9a11543c in QWidgetPrivate::activateChildLayoutsRecursively (this=0x87d660) at kernel/qwidget.cpp:7483
#10 0x00007f3c9a11543c in QWidgetPrivate::activateChildLayoutsRecursively (this=0x87d320) at kernel/qwidget.cpp:7483
I guess this can be changed to confirmed. I also get the crash on Gentoo with KDE SC 4.10.1 and Qt 4.8.4 I do not get the crash. Jure, is it reproducible? If yes, does it also happen if you use a different widget style, such as Cleanlooks? *** Bug 332061 has been marked as a duplicate of this bug. *** Can't reproduce it anymore on 4.12.3 using the regular Oxygen style. Seems fixed now. |