Version: (using KDE 4.3.0) Compiler: gcc version 4.4.1 [gcc-4_4-branch revision 149935] (SUSE Linux) from SuSE 11.2 milestone 6 OS: Linux Installed from: SuSE RPMs How to reproduce: - Open "Personal Settings (Configure Desktop)" - Choose "Keyboard & Mouse" - Choose "Mouse" - Change anything so "Apply" is active - Press "Apply" - Crash! Comments: - Settings are applied for this session (in my case: left handed mouse) - Settings are not kept for next session (have to reconfigure again, including crash) - System is installed fresh - 100% reproducible - Maybe some USB issue related to my mouse. System is "stock" SuSE 11.2 milestone 6 with KDE4 4.3.0. Saw no similar bug report, so I guess this will also affect SuSE 11.2 later than milestone 6. Trace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #5 0x00007f920531c464 in usb_close () from /usr/lib64/libusb-0.1.so.4 #6 0x00007f920553f3c5 in ?? () from /usr/lib64/kde4/kcm_input.so #7 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #8 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #9 0x00007f9214001551 in QStackedWidget::~QStackedWidget() () from /usr/lib64/libQtGui.so.4 #10 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #11 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #12 0x00007f921400f8e1 in QTabWidget::~QTabWidget() () from /usr/lib64/libQtGui.so.4 #13 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #14 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #15 0x00007f92055352c5 in ?? () from /usr/lib64/kde4/kcm_input.so #16 0x00007f9214e45484 in KCModuleProxy::deleteClient() () from /usr/lib64/libkutils.so.4 #17 0x00007f9214e45ea6 in KCModuleProxy::~KCModuleProxy() () from /usr/lib64/libkutils.so.4 #18 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #19 0x00007f9213c59883 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #20 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #21 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #22 0x00007f9214031211 in QScrollArea::~QScrollArea() () from /usr/lib64/libQtGui.so.4 #23 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #24 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #25 0x00007f9214836a9e in ?? () from /usr/lib64/libkdeui.so.5 #26 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #27 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #28 0x00007f9214839c21 in KPageWidget::~KPageWidget() () from /usr/lib64/libkdeui.so.5 #29 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #30 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #31 0x00007f9214c119c3 in ModuleView::~ModuleView() () from /usr/lib64/libsystemsettingsview.so #32 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #33 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #34 0x00007f9214001551 in QStackedWidget::~QStackedWidget() () from /usr/lib64/libQtGui.so.4 #35 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #36 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #37 0x00007f9214001551 in QStackedWidget::~QStackedWidget() () from /usr/lib64/libQtGui.so.4 #38 0x00007f92130a499c in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #39 0x00007f9213c59d23 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #40 0x00007f92148da397 in KMainWindow::~KMainWindow() () from /usr/lib64/libkdeui.so.5 #41 0x00000000004090a9 in _start ()
The report is probably related to the backtrace in bug 203317. The crash is related to some USB input device (I think the Mouse settings check for special options in Logitec mouses). Can you confirm that ? Thanks
Yes, the mouse in question is indeed a Logitech mouse. Dmesg output: usb 1-6.1: New USB device found, idVendor=046d, idProduct=c00e usb 1-6.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-6.1: Product: USB-PS/2 Optical Mouse usb 1-6.1: Manufacturer: Logitech usb 1-6.1: configuration #1 chosen from 1 choice input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:12.2/usb1/1-6/1-6.1/1-6.1:1.0/input/input0 generic-usb 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:12.2-6.1/input0 usb 1-6.2: new low speed USB device using ehci_hcd and address 4 I also tried my other mouse: usb 1-6.1: New USB device found, idVendor=046d, idProduct=c01b usb 1-6.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-6.1: Product: USB-PS/2 Optical Mouse usb 1-6.1: Manufacturer: Logitech usb 1-6.1: configuration #1 chosen from 1 choice input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:12.2/usb1/1-6/1-6.1/1-6.1:1.0/input/input6 generic-usb 0003:046D:C01B.0005: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:12.2-6.1/input0 ...but unfortunately, it's also a Logitech. Omitting the monitor hub inbetween didn't help, neither did connecting both at the same time. Although the dump is somewhat different: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #5 0x00007f5389473c13 in usb_control_msg () from /usr/lib64/libusb-0.1.so.4 #6 0x00007f53896974e8 in ?? () from /usr/lib64/kde4/kcm_input.so #7 0x00007f538969758d in ?? () from /usr/lib64/kde4/kcm_input.so #8 0x00007f538969897d in ?? () from /usr/lib64/kde4/kcm_input.so #9 0x00007f538968d0b5 in ?? () from /usr/lib64/kde4/kcm_input.so #10 0x00007f538968e3c2 in ?? () from /usr/lib64/kde4/kcm_input.so #11 0x00007f539610b647 in KCModuleProxy::save() () from /usr/lib64/libkutils.so.4 #12 0x00007f5395ed85fc in ModuleView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libsystemsettingsview.so #13 0x00007f539436f91c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #14 0x00007f53954b80a7 in QAbstractButton::clicked(bool) () from /usr/lib64/libQtGui.so.4 #15 0x00007f5395219d5b in ?? () from /usr/lib64/libQtGui.so.4 #16 0x00007f539521b96b in ?? () from /usr/lib64/libQtGui.so.4 #17 0x00007f539521bbb5 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4 #18 0x00007f5394f21d50 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x00007f5394ed330c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #20 0x00007f5394eda421 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #21 0x00007f5395acd5d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #22 0x00007f539435a76c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #23 0x00007f5394ed9cf0 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4 #24 0x00007f5394f3fd4e in ?? () from /usr/lib64/libQtGui.so.4 #25 0x00007f5394f3edea in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #26 0x00007f5394f66b4c in ?? () from /usr/lib64/libQtGui.so.4 #27 0x00007f53912c4d6e in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f53912c8738 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f53912c8860 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007f5394382ce6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x00007f5394f662fe in ?? () from /usr/lib64/libQtGui.so.4 #32 0x00007f5394359072 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #33 0x00007f5394359444 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #34 0x00007f539435b5f9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #35 0x000000000040cbd9 in _start () Interestingly, in Yast the mouse module doesn't start! It says "starting module mouse", then a window with some progress bar loads some stuff, then the window disappears and that's it. Would it help to file this bug at Suse or the USB subsystem?
Mh, you could file a bug in Suse bugtracker about the Yast thing. About this report: - could you please install the "kdebase4-workspace-debuginfo" packages, repeat the crash and paste a new backtrace here ? It should be complete this time. Thanks
Now I installed Suse milestone 7 with KDE 4.3.1-1.5-x86_64 - which gives exactly the same behaviour but some hope also (see bottom). I found kdebase4-workspace-devel-debuginfo and installed it, but the crash is exactly the same as the last one, with symbols missing in kcm_input and libQtGui.so.4. Then I installed a heap of kde debug and debuginfo packages, but the missing symbols in libQtGui are still there. I found no obvious other debuginfo packages, so maybe the existing ones are incomplete (especially as there are other symbols which are found in libQtGui). The configured debug repository is http://download.opensuse.org/debug/distribution/11.2/repo/oss/ The mouse module can not be seen in Yast (although yast2-mouse is installed), so I can't file a bug report for this issue. BUT: I tried to attach gdb, and when starting systemsetting from the console it said: libusb couldn't open USB device /dev/bus/usb/001/003: Permission denied. libusb requires write access to USB device nodes. When the permissions of the device are changed from 664 to 666 before starting of systemsettings, "apply" doesn't crash any more! Guess that' a SuSE issue then? Or maybe write access is not really needed in this case?
The last information about the shell output message is really important. I'm not an expert about this so I can't judge if it is a OpenSuse problem, or a configuration one. I leave this to the maintainer. Thanks!
Has this been reported to Novell's bugzilla? It looks like a problem in libusb. Note that for openSUSE, there are now debuginfo and debugsource packages. To create better backtraces, please install debugsource, which also pulls in debuginfo automatically. Debug packages for Qt are called libqt4-debugsource.
Thanks for the tips! Unfortunately, searching for "debugsource" reveals no packages related to kde or qt either. So I think the theory that some already installed package just doesn't contain all symbols for libQtGui. Or is there any other explanation why some symbols are there for libQtGui.so, some not? I have the installation source http://download.opensuse.org/debug/distribution/11.2/repo/oss/ which I believe is correct as I can see quite a heap of debugsource and -info packages. Can any KDE expert confirm that systemsettings-mouse in KDE 4.3.1 needs write access to the USB mouse device? Then it is clearly a permission issue on Novell's side...
It's kdebase4-workspace-debuginfo (not -devel-) I have it and -debugsource from the factory repo (download.opensuse.org/factory/debug). libqt4-debuginfo has the debug symbols for QtGui.
Thanks for the precise specification of the debuginfo packages! I downloaded them from http://download.opensuse.org/factory/repo/debug/suse/x86_64/ and although they seem to be valid for Suse 11.2 rc1, they installed well on Suse 11.2 milestone 7, so here's the new trace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #5 0x00007f0b35968c13 in usb_control_msg () from /usr/lib64/libusb-0.1.so.4 #6 0x00007f0b35b8c4e8 in ?? () from /usr/lib64/kde4/kcm_input.so #7 0x00007f0b35b8c58d in ?? () from /usr/lib64/kde4/kcm_input.so #8 0x00007f0b35b8d97d in ?? () from /usr/lib64/kde4/kcm_input.so #9 0x00007f0b35b820b5 in ?? () from /usr/lib64/kde4/kcm_input.so #10 0x00007f0b35b833c2 in ?? () from /usr/lib64/kde4/kcm_input.so #11 0x00007f0b454917a7 in KCModuleProxy::save() () from /usr/lib64/libkutils.so.4 #12 0x00007f0b4525e58c in ModuleView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libsystemsettingsview.so #13 0x00007f0b436f391c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #14 0x00007f0b4483d0a7 in QAbstractButton::clicked(bool) () from /usr/lib64/libQtGui.so.4 #15 0x00007f0b4459ed5b in ?? () from /usr/lib64/libQtGui.so.4 #16 0x00007f0b445a096b in ?? () from /usr/lib64/libQtGui.so.4 #17 0x00007f0b445a0bb5 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4 #18 0x00007f0b442a6d50 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x00007f0b4425830c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #20 0x00007f0b4425f421 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #21 0x00007f0b44e52eb6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #22 0x00007f0b436de76c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #23 0x00007f0b4425ecf0 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4 #24 0x00007f0b442c4d4e in ?? () from /usr/lib64/libQtGui.so.4 #25 0x00007f0b442c3dea in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #26 0x00007f0b442ebb4c in ?? () from /usr/lib64/libQtGui.so.4 #27 0x00007f0b40647d5e in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f0b4064b728 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f0b4064b850 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007f0b43706ce6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x00007f0b442eb2fe in ?? () from /usr/lib64/libQtGui.so.4 #32 0x00007f0b436dd072 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #33 0x00007f0b436dd444 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #34 0x00007f0b436df5f9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #35 0x000000000040cbd9 in _start () Unfortunately, not all symbol are defined now, but the situation improved and I hope it's more helpful now. Anyway, I think it's better to post this before I install 11.2-rc1 tomorrow and the error is gone :)
@Walter: the important information is still missing :-\ . Why are you downloading the debuginfo packages manually? Aren't they in the standard repositories ? (they should be) Thanks
All right, new round: the bug is also present in Suse 11.2-rc1. When enabling the "debug" repository, I still don't get kdebase4-workspace-debuginfo and libqt4-debuginfo. So I installed the ones I already downloaded, and they seem to match the versions: # rpm -q -a | grep workspace kdebase4-workspace-4.3.1-6.1.x86_64 kdebase4-workspace-debuginfo-4.3.1-6.1.x86_64 # rpm -q -a | grep libqt4 libqt4-debuginfo-4.5.3-2.1.x86_64 libqt4-4.5.3-2.1.x86_64 I also downloaded libqt4-debuginfo from http://download.opensuse.org/factory/repo/debug/suse/x86_64/ again, but no difference. So here's the current dump: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #5 0x00007f7abd2e8c13 in usb_control_msg () from /usr/lib64/libusb-0.1.so.4 #6 0x00007f7abd50c4e8 in LogitechMouse::updateResolution (this=0x9bad70) at /usr/src/debug/kdebase-workspace-4.3.1/kcontrol/input/logitechmouse.cpp:256 #7 0x00007f7abd50c58d in LogitechMouse::resolution (this=0x9bad70) at /usr/src/debug/kdebase-workspace-4.3.1/kcontrol/input/logitechmouse.cpp:240 #8 0x00007f7abd50d97d in LogitechMouse::applyChanges (this=0x0) at /usr/src/debug/kdebase-workspace-4.3.1/kcontrol/input/logitechmouse.cpp:207 #9 0x00007f7abd5020b5 in MouseSettings::apply (this=0x9ab120, force=32) at /usr/src/debug/kdebase-workspace-4.3.1/kcontrol/input/mouse.cpp:834 #10 0x00007f7abd5033c2 in MouseConfig::save (this=0x7fd730) at /usr/src/debug/kdebase-workspace-4.3.1/kcontrol/input/mouse.cpp:579 #11 0x00007f7ac92907a7 in KCModuleProxy::save() () from /usr/lib64/libkutils.so.4 #12 0x00007f7ac905d63c in ModuleView::qt_metacall (this=0x81f560, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff3b8ba0a0) at /usr/src/debug/kdebase-workspace-4.3.1/build/systemsettings/core/ModuleView.moc:89 #13 0x00007f7ac74f2f7c in QMetaObject::activate (sender=0x8488c0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xe) at kernel/qobject.cpp:3113 #14 0x00007f7ac863ce07 in QAbstractButton::clicked(bool) () from /usr/lib64/libQtGui.so.4 #15 0x00007f7ac839ec0b in ?? () from /usr/lib64/libQtGui.so.4 #16 0x00007f7ac83a081b in ?? () from /usr/lib64/libQtGui.so.4 #17 0x00007f7ac83a0a65 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4 #18 0x00007f7ac80a6cf0 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x00007f7ac80582ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #20 0x00007f7ac805f3c1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #21 0x00007f7ac8c528d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #22 0x00007f7ac74ddd9c in QCoreApplication::notifyInternal (this=0x7fff3b8bc6d0, receiver=0x8488c0, event=0x7fff3b8ba7c0) at kernel/qcoreapplication.cpp:610 #23 0x00007f7ac805ec90 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4 #24 0x00007f7ac80c4cfe in ?? () from /usr/lib64/libQtGui.so.4 #25 0x00007f7ac80c3d9a in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #26 0x00007f7ac80ebb6c in ?? () from /usr/lib64/libQtGui.so.4 #27 0x00007f7ac4447dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f7ac444b7a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f7ac444b8d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007f7ac7506356 in QEventDispatcherGlib::processEvents (this=0x617af0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:328 #31 0x00007f7ac80eb31e in ?? () from /usr/lib64/libQtGui.so.4 #32 0x00007f7ac74dc6d2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #33 0x00007f7ac74dcaa4 in QEventLoop::exec (this=0x7fff3b8bc620, flags=) at kernel/qeventloop.cpp:201 #34 0x00007f7ac74dec59 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #35 0x000000000040cbd9 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.1/systemsettings/app/main.cpp:51 Now some libusb symbols are resolved, and some libQtGui ones, but 5 libQTGui ones are still missing. I guess that's all I can do up to now, hoping that it can be resolved before release.
I can confirm everything works fine after doing a chown -R root:users on /dev/bus/usb. Before it always crashed. I think systemssettings should check write permissions first and generally there should IMO be no need to write there when changing the cursor theme.
Unfortunately, the same situation exists for the symbols with Suse 11.2 final. 5 libQtGui symbols are missing in the stack trace, so I guess it makes no sense to post it again. On the other hand, it should be pretty easy to reproduce on any system with complete debug symbols: just remove write permisson of the usb device and call systemsettings to produce a complete stack trace.
*** Bug 215709 has been marked as a duplicate of this bug. ***
*** Bug 215710 has been marked as a duplicate of this bug. ***
*** Bug 215716 has been marked as a duplicate of this bug. ***
*** Bug 215724 has been marked as a duplicate of this bug. ***
*** Bug 215922 has been marked as a duplicate of this bug. ***
*** Bug 216358 has been marked as a duplicate of this bug. ***
SVN commit 1055888 by cfeck: Handle failure of usb_open() Fixes crashes when no permission to access USB mouse device. Also initialize some needed member variables to 0. BUG: 206566 M +12 -3 logitechmouse.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1055888
SVN commit 1055890 by cfeck: Handle failure of usb_open() (backport r1055888) CCBUG: 206566 M +12 -3 logitechmouse.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1055890
*** Bug 210582 has been marked as a duplicate of this bug. ***
*** Bug 210346 has been marked as a duplicate of this bug. ***
If anyone gets a crash from usb_close() or usb_control_msg inside kcm_input.so in KDE Workspace 4.3.4 or in trunk after r1055888, then it is either an upstream bug (libusb not handling failure somewhere), or an downstream bug (e.g. openSUSE setting wrong permissions on device files).
*** Bug 203317 has been marked as a duplicate of this bug. ***
*** Bug 217182 has been marked as a duplicate of this bug. ***
*** Bug 214839 has been marked as a duplicate of this bug. ***
*** Bug 217779 has been marked as a duplicate of this bug. ***
*** Bug 219096 has been marked as a duplicate of this bug. ***
*** Bug 219342 has been marked as a duplicate of this bug. ***
*** Bug 220618 has been marked as a duplicate of this bug. ***
*** Bug 222279 has been marked as a duplicate of this bug. ***
The current KDE SC 4.3.4 openSUSE packages from STABLE do NOT include the fix yet, the packages are apparently build from a version a bit earlier than 4.3.4 tag number. I added a comment to the downstream bug report https://bugzilla.novell.com/show_bug.cgi?id=546221 and hopefully the official update packages will have the fix.
*** Bug 224735 has been marked as a duplicate of this bug. ***