Bug 210582

Summary:	Change mouse pointer failure
Product:	[Applications] systemsettings	Reporter:	Reinout <resteven>
Component:	kcm_mouse	Assignee:	Marie Loise Nolden <nolden>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Reinout 2009-10-14 19:26:05 UTC

Application that crashed: systemsettings
Version of the application: 1.0
KDE Version: 4.3.1 (KDE 4.3.1) "release 3"
Qt Version: 4.5.2
Operating System: Linux 2.6.31-10-desktop x86_64

What I was doing when the application crashed:
When changing the mouse pointer pressing the apply button results into a crash. The changes are not stored. I have an mx510 logitech usb mouse (although I don't see why my mouse would have anything to do with this crash).

 -- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f6edeba9c13 in usb_control_msg () from /usr/lib64/libusb-0.1.so.4
#6  0x00007f6ededcd4e8 in ?? () from /usr/lib64/kde4/kcm_input.so
#7  0x00007f6ededcd58d in ?? () from /usr/lib64/kde4/kcm_input.so
#8  0x00007f6ededce97d in ?? () from /usr/lib64/kde4/kcm_input.so
#9  0x00007f6ededc30b5 in ?? () from /usr/lib64/kde4/kcm_input.so
#10 0x00007f6ededc43c2 in ?? () from /usr/lib64/kde4/kcm_input.so
#11 0x00007f6eee6347a7 in KCModuleProxy::save() () from /usr/lib64/libkutils.so.4
#12 0x00007f6eee40163c in ModuleView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libsystemsettingsview.so
#13 0x00007f6eec89691c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#14 0x00007f6eed9e10a7 in QAbstractButton::clicked(bool) () from /usr/lib64/libQtGui.so.4
#15 0x00007f6eed742d5b in ?? () from /usr/lib64/libQtGui.so.4
#16 0x00007f6eed74496b in ?? () from /usr/lib64/libQtGui.so.4
#17 0x00007f6eed744bb5 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007f6eed44ad50 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007f6eed3fc30c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00007f6eed403421 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#21 0x00007f6eedff68d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#22 0x00007f6eec88176c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#23 0x00007f6eed402cf0 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4
#24 0x00007f6eed468d4e in ?? () from /usr/lib64/libQtGui.so.4
#25 0x00007f6eed467dea in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4
#26 0x00007f6eed48fb4c in ?? () from /usr/lib64/libQtGui.so.4
#27 0x00007f6ee97eae6e in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#28 0x00007f6ee97ee838 in ?? () from /usr/lib64/libglib-2.0.so.0
#29 0x00007f6ee97ee960 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#30 0x00007f6eec8a9ce6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00007f6eed48f2fe in ?? () from /usr/lib64/libQtGui.so.4
#32 0x00007f6eec880072 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#33 0x00007f6eec880444 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#34 0x00007f6eec8825f9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#35 0x000000000040cbd9 in _start ()

This bug may be a duplicate of or related to bug 206566

Reported using DrKonqi

Comment 1 Dario Andres 2009-10-16 22:54:52 UTC

As you are using a Logitech USB mouse, a specific configuration module is enabled. It seems to be crashing when trying to access some option of the USB device. So it is relevant. https://bugs.kde.org/show_bug.cgi?id=206566#c9 has the same crash but I'm not really sure if the root cause is the same as in bug 206566. Thanks

Comment 2 Ben Cooksley 2009-10-21 06:15:22 UTC

Reassigning

Comment 3 Christoph Feck 2009-11-29 00:22:27 UTC


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