Bug 340663 - Crash when trying to preview the keyboard layout
Summary: Crash when trying to preview the keyboard layout
Status: RESOLVED NOT A BUG
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard_layout (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Andriy Rysin
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-11-05 13:35 UTC by basu123ra
Modified: 2015-01-08 01:11 UTC (History)
0 users

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 basu123ra 2014-11-05 13:35:02 UTC
Application: systemsettings (4.11.12)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.6-2-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

When I tried to preview the current keyboard layout, the system configuration crash completely.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc66eb64800 (LWP 9711))]

Thread 5 (Thread 0x7fc650548700 (LWP 9712)):
#0  0x00007fc664de7408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007fc66c1c2c64 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4
#2  0x00007fc66c1b67ba in  () at /usr/lib64/libQtCore.so.4
#3  0x00007fc66c1c279f in  () at /usr/lib64/libQtCore.so.4
#4  0x00007fc664de30a4 in start_thread () at /lib64/libpthread.so.0
#5  0x00007fc66bb767fd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc64fd47700 (LWP 9713)):
#0  0x00007fc664de7408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007fc66c1c2c64 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4
#2  0x00007fc66c1b67ba in  () at /usr/lib64/libQtCore.so.4
#3  0x00007fc66c1c279f in  () at /usr/lib64/libQtCore.so.4
#4  0x00007fc664de30a4 in start_thread () at /lib64/libpthread.so.0
#5  0x00007fc66bb767fd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fc64f546700 (LWP 9714)):
#0  0x00007fc664de7408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007fc66c1c2c64 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4
#2  0x00007fc66c1b67ba in  () at /usr/lib64/libQtCore.so.4
#3  0x00007fc66c1c279f in  () at /usr/lib64/libQtCore.so.4
#4  0x00007fc664de30a4 in start_thread () at /lib64/libpthread.so.0
#5  0x00007fc66bb767fd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fc64ed45700 (LWP 9715)):
#0  0x00007fc664de7408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007fc66c1c2c64 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4
#2  0x00007fc66c1b67ba in  () at /usr/lib64/libQtCore.so.4
#3  0x00007fc66c1c279f in  () at /usr/lib64/libQtCore.so.4
#4  0x00007fc664de30a4 in start_thread () at /lib64/libpthread.so.0
#5  0x00007fc66bb767fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc66eb64800 (LWP 9711)):
[KCrash Handler]
#5  0x00007fc65078ddc5 in  () at /usr/lib64/kde4/kcm_keyboard.so
#6  0x00007fc650788d85 in  () at /usr/lib64/kde4/kcm_keyboard.so
#7  0x00007fc66c2d81fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4
#8  0x00007fc66d598bb2 in QAbstractButton::clicked(bool) () at /usr/lib64/libQtGui.so.4
#9  0x00007fc66d2fbfe3 in  () at /usr/lib64/libQtGui.so.4
#10 0x00007fc66d2fd153 in  () at /usr/lib64/libQtGui.so.4
#11 0x00007fc66d2fd23c in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib64/libQtGui.so.4
#12 0x00007fc66cf9ec0a in QWidget::event(QEvent*) () at /usr/lib64/libQtGui.so.4
#13 0x00007fc66cf4f76c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#14 0x00007fc66cf55dea in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#15 0x00007fc66dc67bda in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5
#16 0x00007fc66c2c42ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4
#17 0x00007fc66cf555e3 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () at /usr/lib64/libQtGui.so.4
#18 0x00007fc66cfc6c9b in  () at /usr/lib64/libQtGui.so.4
#19 0x00007fc66cfc570c in QApplication::x11ProcessEvent(_XEvent*) () at /usr/lib64/libQtGui.so.4
#20 0x00007fc66cfec5c2 in  () at /usr/lib64/libQtGui.so.4
#21 0x00007fc664b18a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#22 0x00007fc664b18c48 in  () at /usr/lib64/libglib-2.0.so.0
#23 0x00007fc664b18cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#24 0x00007fc66c2f10be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#25 0x00007fc66cfec676 in  () at /usr/lib64/libQtGui.so.4
#26 0x00007fc66c2c2e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#27 0x00007fc66c2c3165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#28 0x00007fc66c2c85b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#29 0x000000000040b4bb in  ()
#30 0x00007fc66bab2b05 in __libc_start_main () at /lib64/libc.so.6
#31 0x000000000040b50c in _start ()

Reported using DrKonqi
Comment 1 Andriy Rysin 2014-11-05 18:21:33 UTC
Unfortunately the stack trace does not have the source information, thes two lines:
#5 0x00007fc65078ddc5 in () at /usr/lib64/kde4/kcm_keyboard.so
#6 0x00007fc650788d85 in () at /usr/lib64/kde4/kcm_keyboard.so 

(and other stack elements #4-#1) would be critical to understand the reason.
Comment 2 Christoph Feck 2014-11-16 10:43:31 UTC
If this crash is reproducible, please install debug information packages for the kde-workspace package and add a better backtrace. For more information, please see https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 3 Christoph Feck 2014-12-12 20:36:23 UTC
To further investigate this issue, KDE developers need the information requested in comment #2. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 Christoph Feck 2015-01-08 01:11:19 UTC
No response, changing status. If you have more information, please add a comment.