Bug 352774 - System settings crashed when going to Display settings then going back to system settings
Summary: System settings crashed when going to Display settings then going back to sys...
Status: RESOLVED DUPLICATE of bug 343543
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.3.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-09-15 21:55 UTC by Alexandre
Modified: 2015-09-23 14:57 UTC (History)
0 users

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 Alexandre 2015-09-15 21:55:45 UTC
Application: systemsettings5 (5.3.2)

Qt Version: 5.5.0
Operating System: Linux 4.1.6-200.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

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

Opened system settings through KRunner
Click on Display and Monitor
Click on Back button
crash

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f3828776700 (LWP 11438)):
#0  0x0000003f988f72fd in poll () at /lib64/libc.so.6
#1  0x0000003f9bc0a182 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f3828775c40) at /usr/include/bits/poll2.h:46
#2  0x0000003f9bc0a182 in _xcb_conn_wait (c=c@entry=0x2603c90, cond=cond@entry=0x2603cd0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459
#3  0x0000003f9bc0bc77 in xcb_wait_for_event (c=0x2603c90) at xcb_in.c:648
#4  0x00007f3829354999 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#5  0x0000003cf62a254e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#6  0x0000003f98c07555 in start_thread () at /lib64/libpthread.so.0
#7  0x0000003f98902b9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f382fef9880 (LWP 11437)):
[KCrash Handler]
#5  0x00007f38341fed20 in QQuickWindow::maybeUpdate() () at /lib64/libQt5Quick.so.5
#6  0x00007f38341eb503 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () at /lib64/libQt5Quick.so.5
#7  0x00007f38341f844d in QQuickItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /lib64/libQt5Quick.so.5
#8  0x0000003cf64b3021 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#9  0x00007f38341f553b in QQuickItem::event(QEvent*) () at /lib64/libQt5Quick.so.5
#10 0x00007f38355764ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#11 0x00007f383557b976 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#12 0x0000003cf648361b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#13 0x0000003cf6485a16 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5
#14 0x0000003cf64d9983 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5
#15 0x0000003f9a449a8a in g_main_context_dispatch (context=0x7f3820001710) at gmain.c:3122
#16 0x0000003f9a449a8a in g_main_context_dispatch (context=context@entry=0x7f3820001710) at gmain.c:3737
#17 0x0000003f9a449e20 in g_main_context_iterate (context=context@entry=0x7f3820001710, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808
#18 0x0000003f9a449ecc in g_main_context_iteration (context=0x7f3820001710, may_block=1) at gmain.c:3869
#19 0x0000003cf64d9d8f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#20 0x0000003cf6480daa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#21 0x0000003cf6488e6c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#22 0x000000000040eb1b in main ()

Possible duplicates by query: bug 352402, bug 351786, bug 348782, bug 348517.

Reported using DrKonqi
Comment 1 Christoph Feck 2015-09-23 14:57:14 UTC

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