Bug 132255

Summary: systemsettings crashes choosing "Regional & Accessibility" -> "Keyboard Shortcuts" -> "Command Shortcuts"
Product: [Unmaintained] kcontrol Reporter: Sebastian Richter <srichter>
Component: kcmkhotkeysAssignee: Simon Edwards <simon>
Status: RESOLVED FIXED    
Severity: crash CC: eljefedelito, pth, rakuco, rdieter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sebastian Richter 2006-08-11 13:41:06 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    Unlisted Binary Package
OS:                Linux

I use the packages provided through:

deb http://kubuntu.org/packages/kde-354 dapper main

Choosing "Regional & Accessibility" -> "Keyboard Shortcuts" -> "Command Shortcuts" in systemsettings, systemsettings crashes reproducable. It is not a problem of khotkeys I think, because it works if I use kcontrol instead of systemsettings.

Here is the backtrace (I deleted duplicated lines of "(no debugging symbols found)", sorry).

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
           [...]
[Thread debugging using libthread_db enabled]
[New Thread -1232550208 (LWP 4603)]
(no debugging symbols found)
           [...]
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb68de9a1 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb68e02b9 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb68d7f51 in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb624e455 in KHotKeys::init_global_data ()
   from /usr/lib/libkhotkeys_shared.so.1
#11 0xb62b7c59 in KHotKeys::khotkeys_init ()
   from /usr/lib/kde3/kcm_khotkeys.so
#12 0xb62b7ca1 in khotkeys_init () from /usr/lib/kde3/kcm_khotkeys.so
#13 0xb5af8f52 in KHotKeys::init () from /usr/lib/kde3/kcm_keys.so
#14 0xb5af9004 in KHotKeys::getMenuEntryShortcut ()
   from /usr/lib/kde3/kcm_keys.so
#15 0xb5b07a24 in AppTreeView::fillBranch () from /usr/lib/kde3/kcm_keys.so
#16 0xb5b07c4f in AppTreeView::fill () from /usr/lib/kde3/kcm_keys.so
#17 0xb5b07c94 in CommandShortcutsModule::showing ()
   from /usr/lib/kde3/kcm_keys.so
#18 0xb5b1655e in CommandShortcutsModule::qt_invoke ()
   from /usr/lib/kde3/kcm_keys.so
#19 0xb70aceb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb746228c in QTabWidget::currentChanged () from /usr/lib/libqt-mt.so.3
#21 0xb71fcd0f in QTabWidget::showTab () from /usr/lib/libqt-mt.so.3
#22 0xb746242a in QTabWidget::qt_invoke () from /usr/lib/libqt-mt.so.3
#23 0xb70aceb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#24 0xb70ad7c8 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#25 0xb7461a59 in QTabBar::selected () from /usr/lib/libqt-mt.so.3
#26 0xb71f9fed in QTabBar::setCurrentTab () from /usr/lib/libqt-mt.so.3
#27 0xb71f6f22 in QTabBar::mousePressEvent () from /usr/lib/libqt-mt.so.3
#28 0xb70e764e in QWidget::event () from /usr/lib/libqt-mt.so.3
#29 0xb71f916f in QTabBar::event () from /usr/lib/libqt-mt.so.3
#30 0xb7042e56 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#31 0xb70433e0 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#32 0xb77d87ab in KApplication::notify () from /usr/lib/libkdecore.so.4
#33 0xb6fd41c5 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#34 0xb6fcf873 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#35 0xb6fcdd59 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#36 0xb6fe74db in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#37 0xb705b947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#38 0xb705b86a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#39 0xb7041965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#40 0x0805db80 in QPtrDict<QStringList>::deleteItem ()
#41 0xb68caea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#42 0x080579e1 in ?? ()
Comment 2 jg 2006-08-30 23:00:18 UTC
Those links seem unrelated, the callstack is different in their crash.

The KDE crash handler is not very clear, it seems the actual application which crashed was: KDE Daemon (kded) SIGSEGV  Why dont they put this info at the top of the backtrace log!?

JG
Comment 3 jg 2006-08-30 23:02:29 UTC
Oops, posted my comment into the wrong window. Please ignore my comment.
Comment 4 Bram Schoenmakers 2006-11-22 20:52:49 UTC
*** Bug 137704 has been marked as a duplicate of this bug. ***
Comment 5 Pino Toscano 2008-06-08 10:53:59 UTC
*** Bug 140717 has been marked as a duplicate of this bug. ***
Comment 6 Pino Toscano 2008-06-08 10:54:28 UTC
*** Bug 132254 has been marked as a duplicate of this bug. ***
Comment 7 Raphael Kubo da Costa 2009-05-19 23:31:23 UTC
Closing, as it seems to have been fixed according to the first link in comment 1.