Bug 162367 - GUI bug in systemsettings causes repeatable crash
Summary: GUI bug in systemsettings causes repeatable crash
Status: RESOLVED DUPLICATE of bug 154647
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keys (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Ellis Whitehead
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-20 18:50 UTC by Brian Vuyk
Modified: 2008-06-08 16:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
systemsettings-glitch-1.jpg (41.29 KB, image/jpeg)
2008-05-23 14:50 UTC, Brian Vuyk
Details
systemsettings-glitch-2.jpg (68.18 KB, image/jpeg)
2008-05-23 15:00 UTC, Brian Vuyk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Vuyk 2008-05-20 18:50:51 UTC
Version:            (using KDE 4.0.4)
Installed from:    Ubuntu Packages
OS:                Linux

I've found a repeatable bug in systemsettings.

Steps to Reproduce:
********************

1. Open systemsettings
2. Double Click 'Keyboard and Mouse'
3. Click the 'Keyboard Shortcuts' item in the left sidebar
4. Double click on one of the listed shortcuts
5. Change the 'KDE Component' selection above to another item

6. GLITCH SHOULD BE VISIBLE

7. Double Click another shortcut.

8. It should crash here.

Expected behaviour:
********************

It should not crash
Comment 1 FiNeX 2008-05-20 23:00:16 UTC
cannot reproduce on r809608
Comment 2 Michael Pyne 2008-05-23 03:10:43 UTC
Also cannot reproduce, r810995.
Comment 3 FiNeX 2008-05-23 09:55:31 UTC
@Ellis: on the sixth point you write about glitches, could you post a screenshot? Moreover if you can reproduce the crash you should post the backtrace following the instruction on:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(remember that backtrace without debug information are useless).

Thanks
Comment 4 Brian Vuyk 2008-05-23 14:50:58 UTC
Created attachment 24913 [details]
systemsettings-glitch-1.jpg
Comment 5 Brian Vuyk 2008-05-23 15:00:01 UTC
Created attachment 24914 [details]
systemsettings-glitch-2.jpg
Comment 6 Brian Vuyk 2008-05-23 15:01:12 UTC
Screenshots of graphical glitch attached.

systemsettings-glitch-1 shows the glitch. Basically, I expanded the 'Block Global Shortcuts' dropdown, then changed the KDE component to 'plasma'

systemsettings-glitch-2 shows the glitch after switching back to 'kwin' as the KDE component.

Following these two steps, I can crash the desktop in two ways:

With Desktop Effects, it crashes if I dbl-click 'Block Global Shortcuts' again. Without desktop effects enabled, it crashes after the window is closed.

I will provide backtraces with proper debug information after the -dbg libraries are installed. I have a poor connection, so I was hoping someone else could reproduce and post the proper info...



Comment 7 Brian Vuyk 2008-05-23 17:02:07 UTC
Now with backtrace goodness:

(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb652aa00 (LWP 16282)]
[KCrash handler]
#6  0xb776a9ba in ?? () from /usr/lib/libQtGui.so.4
#7  0xb7a5eacb in QHash<QPersistentModelIndex, QWidget*>::findNode (
    this=0xbf9d9474, akey=@0x82b7890, ahp=0x680073)
    at /usr/include/qt4/QtCore/qhash.h:841
#8  0xb776b72e in ?? () from /usr/lib/libQtGui.so.4
#9  0xbf9d9474 in ?? ()
#10 0x082b7890 in ?? ()
#11 0x00680073 in ?? ()
#12 0x00000000 in ?? ()
#0  0xb7f0d410 in __kernel_vsyscall ()
Comment 8 Brian Vuyk 2008-05-23 17:04:22 UTC
different backtrace from another crash:

(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6565a00 (LWP 16296)]
[KCrash handler]
#6  0xb7f48410 in __kernel_vsyscall ()
#7  0xb6f98085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6f99a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7df8a75 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7df8b38 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7df8cd5 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7a59f1d in KShortcutsEditorDelegate::itemActivated (this=0x82cbdd0, 
    index=@0xbfc48f90)
    at /build/buildd/kde4libs-4.0.3/kdeui/dialogs/kshortcutsdialog.cpp:244
#13 0xb7a5a071 in KShortcutsEditorDelegate::qt_metacall (this=0x82cbdd0, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfc4949c)
    at /build/buildd/kde4libs-4.0.3/obj-i486-linux-gnu/kdeui/kshortcutsdialog_p.moc:79
#14 0xb7ec7cf4 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb7ec88c2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb7733fd3 in QAbstractItemView::activated () from /usr/lib/libQtGui.so.4
#17 0xb777c09c in QTreeView::mouseDoubleClickEvent ()
   from /usr/lib/libQtGui.so.4
#18 0xb733efbd in QWidget::event () from /usr/lib/libQtGui.so.4
#19 0xb7633433 in QFrame::event () from /usr/lib/libQtGui.so.4
#20 0xb76b951f in QAbstractScrollArea::viewportEvent ()
   from /usr/lib/libQtGui.so.4
#21 0xb773f248 in QAbstractItemView::viewportEvent ()
   from /usr/lib/libQtGui.so.4
#22 0xb77772f3 in QTreeView::viewportEvent () from /usr/lib/libQtGui.so.4
#23 0xb76ba715 in ?? () from /usr/lib/libQtGui.so.4
#24 0x082ba5a0 in ?? ()
#25 0xbfc49d18 in ?? ()
#26 0xbfc49998 in ?? ()
#27 0xb72f5242 in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
Backtrace stopped: frame did not save the PC
#0  0xb7f48410 in __kernel_vsyscall ()
Comment 9 Michael Jansen 2008-06-08 16:40:18 UTC
I fixed this on trunk. I guess it is part of 4.1.

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