Bug 917054

Summary:	Plasmashell, Krunner crash on dual monitor setup
Product:	[openSUSE] openSUSE Distribution	Reporter:	Daniele Granata <denni.granata>
Component:	KDE Workspace (Plasma)	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P2 - High	CC:	okurz, olli.tuominen, tchvatal
Version:	Leap 42.1
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 42.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Daniele Granata 2015-02-10 08:35:14 UTC

Recently i've upgraded to plasma 5.2 and qt 5.4.
My sandybridge notebook with hd intel have a fullhd monitor connected with HDMI.
Startup takes a while and when the desktop appears I found drkonqui windows of plasmashell and Krunner tell me they have crashed. This appens only on startup because plasmashell restarts automatically with no issue and I was able to use krunner.
The crash happens also if the external monitor was hot plugged or unplugged, in this scenario kwin crashes too.
The crash is reproducible always and is related to Qt5 QScreen::handle() and libqxcb.so.

Krunner and plasmashell will not crash if only the laptop monitor is used.

Comment 1 Olli Tuominen 2015-11-19 07:14:39 UTC

This happens with Leap too.

Application: krunner (0.1)

Qt Version: 5.5.0
Operating System: Linux 4.1.12-1-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc2386d27c0 (LWP 1931))]

Thread 3 (Thread 0x7fc2233e4700 (LWP 1932)):
#0  0x00007fc23437ac1d in poll () from /lib64/libc.so.6
#1  0x00007fc233888422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007fc23388a00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007fc225534c29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007fc234a7155f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007fc2321f00a4 in start_thread () from /lib64/libpthread.so.0
#6  0x00007fc23438304d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc216ff4700 (LWP 1940)):
#0  0x00007fc234376ced in read () from /lib64/libc.so.6
#1  0x00007fc2318cab60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fc231889999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fc231889df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x00007fc231889f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5  0x00007fc234ca2a5b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6  0x00007fc234c49a63 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#7  0x00007fc234a6c84a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x00007fc2371155f8 in ?? () from /usr/lib64/libQt5Qml.so.5
#9  0x00007fc234a7155f in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x00007fc2321f00a4 in start_thread () from /lib64/libpthread.so.0
#11 0x00007fc23438304d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc2386d27c0 (LWP 1931)):
[KCrash Handler]
#6  0x0000000000000000 in ?? ()
#7  0x00007fc234c7e01b in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib64/libQt5Core.so.5
#8  0x00007fc23790a5d0 in ?? () from /usr/lib64/libQt5Quick.so.5
#9  0x00007fc23790a7c9 in ?? () from /usr/lib64/libQt5Quick.so.5
#10 0x00007fc237821f08 in QQuickItemPrivate::refWindow(QQuickWindow*) () from /usr/lib64/libQt5Quick.so.5
#11 0x00007fc237821ec5 in QQuickItemPrivate::refWindow(QQuickWindow*) () from /usr/lib64/libQt5Quick.so.5
#12 0x00007fc237822e3b in QQuickItem::setParentItem(QQuickItem*) () from /usr/lib64/libQt5Quick.so.5
#13 0x00007fc2382d6e38 in PlasmaQuick::Dialog::setMainItem(QQuickItem*) () from /usr/lib64/libKF5PlasmaQuick.so.5
#14 0x00007fc234c7b40f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#15 0x00007fc237c73349 in ?? () from /usr/lib64/libKF5Declarative.so.5
#16 0x00007fc234c7c796 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#17 0x00007fc235bb2e8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#18 0x00007fc235bb7cd8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#19 0x00007fc234c4bba5 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#20 0x00007fc234c4dd67 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#21 0x00007fc234ca35c3 in ?? () from /usr/lib64/libQt5Core.so.5
#22 0x00007fc231889c84 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fc231889ed8 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007fc231889f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007fc234ca2a3c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#26 0x00007fc234c49a63 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#27 0x00007fc234c515d6 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#28 0x0000000000408b36 in main ()

Comment 2 Olli Tuominen 2015-11-19 07:19:13 UTC

I found this one: https://bugs.kde.org/show_bug.cgi?id=343982 which might be related?

Comment 3 Olli Tuominen 2015-12-07 10:52:42 UTC

Quite annoying issue. Can I provide more info which might led to solve this issue?

Comment 4 Tomáš Chvátal 2015-12-07 13:45:37 UTC

To me this looks like duplicate of the following bug

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

Comment 5 Oliver Kurz 2015-12-07 14:18:16 UTC

(In reply to Tomáš Chvátal from comment #4)
> To me this looks like duplicate of the following bug
> 
> *** This bug has been marked as a duplicate of bug 911304 ***

It *could* be a duplicate but as long as the summary line of bug 911304 is so specific (mentioning "yast" and "teamviewer") I have to object closing the current issue. Otherwise this can just confuse more and have other potential bug reports about "krunner crashes" pop up. The reference to upstream bug https://bugreports.qt.io/browse/QTBUG-31354 is very important.

@Tomáš could you rewrite the summary line of this bug, then, accordingly, and close again?

Comment 6 Tomáš Chvátal 2015-12-07 14:25:21 UTC

Done

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

Comment 7 Karl Cheng 2016-11-29 07:04:37 UTC

*** Bug 951528 has been marked as a duplicate of this bug. ***