Bug 328983 - systemsettings crashed in Colors module on ESC from color picker dialog
Summary: systemsettings crashed in Colors module on ESC from color picker dialog
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_colors (show other bugs)
Version: 4.11.3
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Matthew Woehlke
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-12-18 21:29 UTC by Maxym Kit
Modified: 2015-08-21 02:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxym Kit 2013-12-18 21:29:50 UTC
Application: systemsettings (4.11.3)
KDE Platform Version: 4.11.3
Qt Version: 4.8.5
Operating System: Linux 3.11.10-200.fc19.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

1. In Colors module select 'Colors' tab;
2. In list of colors select any color picking button to open color picker;
3. Focus on HTML color input box;
4. Press ESC button;
5. systemsettings crashes with probability ~40%;

The crash can be reproduced sometimes.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fca6b3dc8c0 (LWP 27525))]

Thread 2 (Thread 0x7fca657a2700 (LWP 27526)):
#0  0x0000003af8847bbc in g_main_context_check () from /lib64/libglib-2.0.so.0
#1  0x0000003af884807b in g_main_context_iterate.isra.22 () from /lib64/libglib-2.0.so.0
#2  0x0000003af88481ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00000035655a7166 in QEventDispatcherGlib::processEvents (this=0x7fca600008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x0000003565578ecf in QEventLoop::processEvents (this=this@entry=0x7fca657a1ce0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00000035655791c5 in QEventLoop::exec (this=this@entry=0x7fca657a1ce0, flags=...) at kernel/qeventloop.cpp:204
#6  0x000000356547866f in QThread::exec (this=this@entry=0x1416470) at thread/qthread.cpp:536
#7  0x000000356555a733 in QInotifyFileSystemWatcherEngine::run (this=0x1416470) at io/qfilesystemwatcher_inotify.cpp:256
#8  0x000000356547ad0f in QThreadPrivate::start (arg=0x1416470) at thread/qthread_unix.cpp:338
#9  0x000000318d607c53 in start_thread () from /lib64/libpthread.so.0
#10 0x000000318cef5dbd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fca6b3dc8c0 (LWP 27525)):
[KCrash Handler]
#6  0x0000000000615f40 in ?? ()
#7  0x0000003566e3e040 in QApplication::x11ProcessEvent (this=0x7fffb8cdc380, event=event@entry=0x7fffb8cdbea0) at kernel/qapplication_x11.cpp:3441
#8  0x0000003566e64ea4 in x11EventSourceDispatch (s=0xefbc80, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#9  0x0000003af8847df6 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#10 0x0000003af8848148 in g_main_context_iterate.isra.22 () from /lib64/libglib-2.0.so.0
#11 0x0000003af88481ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#12 0x00000035655a7145 in QEventDispatcherGlib::processEvents (this=0xefa800, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x0000003566e65016 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#14 0x0000003565578ecf in QEventLoop::processEvents (this=this@entry=0x7fffb8cdc280, flags=...) at kernel/qeventloop.cpp:149
#15 0x00000035655791c5 in QEventLoop::exec (this=this@entry=0x7fffb8cdc280, flags=...) at kernel/qeventloop.cpp:204
#16 0x000000356557e45b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#17 0x0000003566dc6cec in QApplication::exec () at kernel/qapplication.cpp:3823
#18 0x000000000040ab5b in main (argc=2, argv=0x7fffb8cdc4c8) at /usr/src/debug/kde-workspace-4.11.3/systemsettings/app/main.cpp:49

Possible duplicates by query: bug 328965, bug 328794, bug 328758, bug 328736, bug 328611.

Reported using DrKonqi
Comment 1 Christoph Feck 2013-12-19 02:20:00 UTC
I tried about 20 times, pressing Esc with focused and/or hovered HTML line edit in color dialog, but got no crash. Does the crash also occur on a freshly created user account? If you use Oxygen widget style, does disabling animations or using a different widget style make a difference?
Comment 2 Maxym Kit 2013-12-19 21:23:56 UTC
I'm using Oxygen widget style. Neither disabling animation nor using different widget style helps. However on a freshly created user accout I was not able to reproduce the crash.
Comment 3 Jeremy Whiting 2015-08-21 02:14:48 UTC
Maxym, if you are still able to reproduce this crash with newer packages reopen this bug. I'll close as it seems you were able to work around it by creating a new user somehow.