Bug 343422 - SEGFAULT as soon as I hit "Back" button after opening the Display Manager
Summary: SEGFAULT as soon as I hit "Back" button after opening the Display Manager
Status: RESOLVED DUPLICATE of bug 344651
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_sddm (show other bugs)
Version: 5.2.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-27 23:31 UTC by Alexander Nestorov
Modified: 2015-04-25 08:54 UTC (History)
1 user (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 Alexander Nestorov 2015-01-27 23:31:31 UTC
systemsettings5 SEGFAULTs as soon as I hit the "Back" button after opening the "Display Manager" module.

Reproducible: Always
Comment 1 Alexander Nestorov 2015-01-28 00:10:26 UTC
Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe4e68f57c0 (LWP 2356))]

Thread 3 (Thread 0x7fe4d4018700 (LWP 2357)):
#0  0x00007fe4e307d44d in poll () from /usr/lib/libc.so.6
#1  0x00007fe4e152d9f2 in ?? () from /usr/lib/libxcb.so.1
#2  0x00007fe4e152f56f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x00007fe4d69f83f9 in ?? () from /usr/lib/qt/plugins/platforms/libqxcb.so
#4  0x00007fe4e36f35ee in ?? () from /usr/lib/libQt5Core.so.5
#5  0x00007fe4e0ca8314 in start_thread () from /usr/lib/libpthread.so.0
#6  0x00007fe4e308624d in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fe4bcf01700 (LWP 2373)):
#0  0x00007fe4e307f193 in select () from /usr/lib/libc.so.6
#1  0x00007fe4e3870b31 in ?? () from /usr/lib/libQt5Core.so.5
#2  0x00007fe4e36f35ee in ?? () from /usr/lib/libQt5Core.so.5
#3  0x00007fe4e0ca8314 in start_thread () from /usr/lib/libpthread.so.0
#4  0x00007fe4e308624d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fe4e68f57c0 (LWP 2356)):
[KCrash Handler]
#5  0x00007fe4c6552c5e in QQuickItemPrivate::addToDirtyList() () from /usr/lib/libQt5Quick.so.5
#6  0x00007fe4c6552d08 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /usr/lib/libQt5Quick.so.5
#7  0x00007fe4c655ce85 in ?? () from /usr/lib/libQt5Quick.so.5
#8  0x00007fe4e390e4ba in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#9  0x00007fe4c655ba0b in QQuickItem::event(QEvent*) () from /usr/lib/libQt5Quick.so.5
#10 0x00007fe4e4d7bd8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#11 0x00007fe4e4d81370 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#12 0x00007fe4e38dda9b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#13 0x00007fe4e38dfadb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#14 0x00007fe4e3934c83 in ?? () from /usr/lib/libQt5Core.so.5
#15 0x00007fe4e078ba0d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0x00007fe4e078bcf8 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x00007fe4e078bdac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0x00007fe4e3935077 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#19 0x00007fe4e38db532 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#20 0x00007fe4e38e2f0c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#21 0x000000000040e64c in main ()
Comment 2 David Edmundson 2015-01-28 14:39:43 UTC
Works here, what's your Qt version?
Comment 3 Alexander Nestorov 2015-01-28 20:57:26 UTC
I'm not qt5 (5.4.0-3)
Comment 4 Alexander Nestorov 2015-01-29 14:25:10 UTC
Oops, typo... I'm on qt5 (5.4.0-3)
Comment 5 Alexander Nestorov 2015-02-02 02:18:29 UTC
Do you need more info or can this bug be confirmed?
Comment 6 Christoph Feck 2015-02-15 16:25:54 UTC
Thanks for the update, changing status.
Comment 7 Alexander Nestorov 2015-02-15 16:32:50 UTC
Hold on. I can't reproduce this  anymore with latest updates from Arch.
(KDE Frameworks 5.6.0 + systemsettings5 5.2.0 + Qt 5.4.0-3)
Comment 8 Alexander Nestorov 2015-02-21 03:56:39 UTC
Nope, ignore my last comment. I still can reproduce it.
I couldn't reproduce it with Nouveau, but I can with NVIDIA drivers.
Comment 9 Christoph Feck 2015-04-25 08:54:20 UTC

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