Bug 315309 - kcm colors crashes when selecting an entry from recent colors
Summary: kcm colors crashes when selecting an entry from recent colors
Status: RESOLVED DUPLICATE of bug 313984
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_colors (show other bugs)
Version: 1.0
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Matthew Woehlke
Depends on:
Reported: 2013-02-17 09:03 UTC by Franz Trischberger
Modified: 2013-02-17 10:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Franz Trischberger 2013-02-17 09:03:17 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.10.00 (Compiled from sources)
Qt Version: 4.8.4
Operating System: Linux 3.7.7-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
* open colors kcm
* go to the colors tab
* click on one of the ColorButtons
* select "* Recent Colors *" palette
* click on one of the xolor boxes
-> crash

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".
[KCrash Handler]
#6  0x00007f8ec5c41801 in QAbstractItemView::mouseReleaseEvent (this=0x1b2a0d0, event=0x7fffbc0281f0) at itemviews/qabstractitemview.cpp:1789
#7  0x00007f8ec61bc1c7 in KColorCells::mouseReleaseEvent (this=0x1b2a0d0, e=0x7fffbc0281f0) at /var/tmp/paludis/kde-base-kdelibs-4.10.0/work/kdelibs-4.10.0/kdeui/colors/kcolordialog.cpp:455
#8  0x00007f8ec5770b42 in QWidget::event (this=0x1b2a0d0, event=0x7fffbc0281f0) at kernel/qwidget.cpp:8375
#9  0x00007f8ec5b2d106 in QFrame::event (this=0x1b2a0d0, e=0x7fffbc0281f0) at widgets/qframe.cpp:557
#10 0x00007f8ec5c4045b in QAbstractItemView::viewportEvent (this=0x1b2a0d0, event=0x7fffbc0281f0) at itemviews/qabstractitemview.cpp:1644
#11 0x00007f8ec4e85cc6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x1c03530, event=0x7fffbc0281f0) at kernel/qcoreapplication.cpp:1056
#12 0x00007f8ec571df9f in notify_helper (e=0x7fffbc0281f0, receiver=0x1c03530, this=0x140c4c0) at kernel/qapplication.cpp:4558
#13 QApplicationPrivate::notify_helper (this=0x140c4c0, receiver=0x1c03530, e=0x7fffbc0281f0) at kernel/qapplication.cpp:4534
#14 0x00007f8ec57240a9 in QApplication::notify (this=<optimized out>, receiver=0x1c03530, e=0x7fffbc0281f0) at kernel/qapplication.cpp:4105
#15 0x00007f8ec6283ca6 in KApplication::notify (this=0x7fffbc028d10, receiver=0x1c03530, event=0x7fffbc0281f0) at /var/tmp/paludis/kde-base-kdelibs-4.10.0/work/kdelibs-4.10.0/kdeui/kernel/kapplication.cpp:311
#16 0x00007f8ec4e85b4c in QCoreApplication::notifyInternal (this=0x7fffbc028d10, receiver=0x1c03530, event=0x7fffbc0281f0) at kernel/qcoreapplication.cpp:946
#17 0x00007f8ec571ef92 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QApplicationPrivate::sendMouseEvent (receiver=0x1c03530, event=0x7fffbc0281f0, alienWidget=0x1c03530, nativeWidget=0x1a46260, buttonDown=0x1c03530, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3173
#19 0x00007f8ec5799d68 in QETWidget::translateMouseEvent (this=0x1a46260, event=<optimized out>) at kernel/qapplication_x11.cpp:4516
#20 0x00007f8ec5798b7a in QApplication::x11ProcessEvent (this=0x7fffbc028d10, event=0x7fffbc028910) at kernel/qapplication_x11.cpp:3639
#21 0x00007f8ec57c01da in x11EventSourceDispatch (s=0x13eea90, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#22 0x00007f8ebf1413b3 in g_main_dispatch (context=0x1402400) at gmain.c:2715
#23 g_main_context_dispatch (context=0x1402400) at gmain.c:3219
#24 0x00007f8ebf141700 in g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x1402400, self=<optimized out>) at gmain.c:3290
#25 g_main_context_iterate (context=0x1402400, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3227
#26 0x00007f8ebf1417c4 in g_main_context_iteration (context=0x1402400, may_block=1) at gmain.c:3351
#27 0x00007f8ec4eb41ef in QEventDispatcherGlib::processEvents (this=0x13bfad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#28 0x00007f8ec57bfe7e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f8ec4e846b2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007f8ec4e84907 in QEventLoop::exec (this=0x7fffbc028ca0, flags=...) at kernel/qeventloop.cpp:204
#31 0x00007f8ec4e895f5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#32 0x0000000000411425 in main (argc=1, argv=0x7fffbc028fd8) at /var/tmp/paludis/kde-base-systemsettings-4.10.0/work/systemsettings-4.10.0/systemsettings/app/main.cpp:49

Reported using DrKonqi
Comment 1 Franz Trischberger 2013-02-17 09:58:13 UTC
Of course this does not happen only with systemsettings, but with EVERY KColorDialog. I even happens after removing .kde/share/config/colors/Recent_Colors.
I can reproduce this on 2 different PCs, with kde-4.9.5 and kde-4.10.0.
Comment 2 Jekyll Wu 2013-02-17 10:18:08 UTC
This should also be fixed by the commit for bug 313984, in 4.10.1

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