Bug 297481 - Switching from the mouse to the joystick settings caused it to crash
Summary: Switching from the mouse to the joystick settings caused it to crash
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_joystick (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-04 17:01 UTC by Simon Reed
Modified: 2018-03-22 00:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Reed 2012-04-04 17:01:11 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-17-generic x86_64
Distribution: Ubuntu 11.10

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

I was going through the system settings, had looked at the mouse settings and clicked on the joystick icon.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[KCrash Handler]
#6  setText (atext=..., this=0x0) at /usr/include/qt4/QtGui/qtablewidget.h:192
#7  JoyWidget::checkDevice (this=0xd671f0) at ../../../../kcontrol/hardware/joystick/joywidget.cpp:351
#8  0x00007fb40010c01c in JoyWidget::qt_metacall (this=0xd671f0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffab828570) at ./joywidget.moc:79
#9  0x00007fb4233b7eba in QMetaObject::activate (sender=0xd7b0e0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#10 0x00007fb4233bb789 in QObject::event (this=0xd7b0e0, e=<optimized out>) at kernel/qobject.cpp:1181
#11 0x00007fb42402c474 in notify_helper (e=0x7fffab828ad0, receiver=0xd7b0e0, this=0x857690) at kernel/qapplication.cpp:4486
#12 QApplicationPrivate::notify_helper (this=0x857690, receiver=0xd7b0e0, e=0x7fffab828ad0) at kernel/qapplication.cpp:4458
#13 0x00007fb4240312e1 in QApplication::notify (this=0x7fffab828dd0, receiver=0xd7b0e0, e=0x7fffab828ad0) at kernel/qapplication.cpp:4365
#14 0x00007fb424d41466 in KApplication::notify (this=0x7fffab828dd0, receiver=0xd7b0e0, event=0x7fffab828ad0) at ../../kdeui/kernel/kapplication.cpp:311
#15 0x00007fb4233a4afc in QCoreApplication::notifyInternal (this=0x7fffab828dd0, receiver=0xd7b0e0, event=0x7fffab828ad0) at kernel/qcoreapplication.cpp:787
#16 0x00007fb4233d1d62 in sendEvent (event=0x7fffab828ad0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#17 QTimerInfoList::activateTimers (this=0x84ed60) at kernel/qeventdispatcher_unix.cpp:603
#18 0x00007fb4233cf514 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#19 0x00007fb4204eca5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fb4204ed258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fb4204ed429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fb4233cfed6 in QEventDispatcherGlib::processEvents (this=0x828a10, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007fb4240d410e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007fb4233a3cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007fb4233a3ef7 in QEventLoop::exec (this=0x7fffab828d60, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007fb4233a8789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#27 0x000000000040a7c5 in main (argc=5, argv=0x7fffab829098) at ../../../systemsettings/app/main.cpp:49

This bug may be a duplicate of or related to bug 276847.

Possible duplicates by query: bug 276847.

Reported using DrKonqi
Comment 1 David Edmundson 2018-03-22 00:51:55 UTC
Plasma 4 is closed for crash fixes, closing