Version: (using KDE 4.3.1) OS: Linux Installed from: SuSE RPMs I have a Compaq nc6320 notebook which includes a touch pad. If I want to change any mouse property in the KDE system & setting (e.g. doubleclick opens files instead of single click, mouse's layout is left-hand instead of right-hand, etc.) while an USB mouse is plugged into the notebook (i.e. there are more than one mouse devices in the system), the system & settings application crashes immediately. Sometimes the settings I've done come into effect, but seemingly not saved into the configuration. For example I switched to reverse scrolling, applied it, then system & settings crashed. At this point scolling became suddenly reverse in firefox, but after starting system & settings -> mouse settings again (which crashed of course) scrolling become the dafault again. Here is a backlog from the crashed application: Application: Rendszerbeállítások (systemsettings), signal: Segmentation fault [KCrash Handler] #5 0x00007f0d2aa1ac13 in usb_control_msg () from /usr/lib64/libusb-0.1.so.4 #6 0x00007f0d2ac3e06b in ?? () from /usr/lib64/kde4/kcm_input.so #7 0x00007f0d2ac3e336 in ?? () from /usr/lib64/kde4/kcm_input.so #8 0x00007f0d2ac3f94b in ?? () from /usr/lib64/kde4/kcm_input.so #9 0x00007f0d2ac340b5 in ?? () from /usr/lib64/kde4/kcm_input.so #10 0x00007f0d2ac353c2 in ?? () from /usr/lib64/kde4/kcm_input.so #11 0x00007f0d36f3e7a7 in KCModuleProxy::save (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.1/kutils/kcmoduleproxy.cpp:273 #12 0x00007f0d36d0b63c in ModuleView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libsystemsettingsview.so #13 0x00007f0d351a091c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #14 0x00007f0d362eb0a7 in QAbstractButton::clicked(bool) () from /usr/lib64/libQtGui.so.4 #15 0x00007f0d3604cd5b in ?? () from /usr/lib64/libQtGui.so.4 #16 0x00007f0d3604e96b in ?? () from /usr/lib64/libQtGui.so.4 #17 0x00007f0d3604ebb5 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4 #18 0x00007f0d35d54d50 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x00007f0d35d0630c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #20 0x00007f0d35d0d421 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #21 0x00007f0d369008d6 in KApplication::notify (this=0x7fffdbeddce0, receiver=0x8ec2f0, event=0x7fffdbedbdd0) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302 #22 0x00007f0d3518b76c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #23 0x00007f0d35d0ccf0 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4 #24 0x00007f0d35d72d4e in ?? () from /usr/lib64/libQtGui.so.4 #25 0x00007f0d35d71dea in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #26 0x00007f0d35d99b4c in ?? () from /usr/lib64/libQtGui.so.4 #27 0x00007f0d320f4e6e in g_main_dispatch (context=<value optimized out>) at gmain.c:1960 #28 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513 #29 0x00007f0d320f8838 in g_main_context_iterate (context=0x643440, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591 #30 0x00007f0d320f8960 in IA__g_main_context_iteration (context=0x643440, may_block=1) at gmain.c:2654 #31 0x00007f0d351b3ce6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #32 0x00007f0d35d992fe in ?? () from /usr/lib64/libQtGui.so.4 #33 0x00007f0d3518a072 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #34 0x00007f0d3518a444 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #35 0x00007f0d3518c5f9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #36 0x000000000040cbd9 in _start ()
The crash is related to bug 206566.--
*** This bug has been marked as a duplicate of bug 206566 ***