Bugzilla – Bug 949978
kde applications crash with dual displays
Last modified: 2016-02-01 18:35:05 UTC
User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16 Build Identifier: please note that the component probably should be "kde5 workspace", but that was missing in the list. with a single display, kde operates ok. very often, when another display is attached, plasma-desktop crashes. both konsole and kwrite also crash at seemingly random times (for example, after the second display is attached for the first time, moving konsole to the second display and attempting to select text in it immediately crashes). as second display is attached and removed, and applications used, they crash often, although at other times they work just fine during the same operations. quite a blocker for people who use second display sometimes, there seem to be a few kde bugreports : https://bugs.kde.org/show_bug.cgi?id=340267 https://bugs.kde.org/show_bug.cgi?id=341497 (and a gazillion of bugreports marked as duplicates of it) https://bugs.kde.org/show_bug.cgi?id=345544 an ubuntu bugreport : https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1450137 these reports seem to point at the problem being in qt, and there's a whole bunch of even more upstream reports in qt : https://bugreports.qt.io/browse/QTBUG-42985 https://bugreports.qt.io/browse/QTBUG-46024 https://bugreports.qt.io/browse/QTBUG-47041 https://bugreports.qt.io/browse/QTBUG-47385 according to some of the reports, at least a few problems should be fixed in latest qt 5.5, although, according to some, not all of them. in any case, it might be a good idea to upgrade to qt 5.5.0 for leap, possibly 5.5.1, if it comes out in time - if not, patches for those crashes would have to be backported... Reproducible: Sometimes
(In reply to Rihards Olups from comment #0) > in any case, it might be a good idea to upgrade to qt 5.5.0 for leap, > possibly 5.5.1, if it comes out in time - if not, patches for those crashes > would have to be backported... Leap does already contain Qt 5.5.0, with some added patches: * Tue Aug 18 2015 hrvoje.senjan@gmail.com - Added patches from upstream: ignore-disabling-of-outputs-in-the-middle-of-the-mode-switch.patch (qtbug#44158, qtbug#46786, qtbug#46822) when-a-screen-comes-back-online-the-windows-need-to-be-told-about-it.patch (qtbug#47041) Could you please try again with the 42.1-Current repo and see whether you still have problems? Changing the main repo URL to http://download.opensuse.org/distribution/leap/42.1-Current/repo/oss/ and running "zypper dup" should be enough, but you should stop AppArmor before the upgrade ("rcapparmor stop") or the system will crash (known kernel problem, already fixed).
thanks for the suggestion. did the upgrade. while the plasma-desktop crash seems to be gone, individual applications still crash if external display is attached/removed or its resolution changed. as before, this does not happen always, but it took me just some 3 minutes of playing around to crash konsole & kwrite at the same time... unfortunately, after the upgrade suspend/sleep from the menu stopped working, wifi does not work, kded5 crashes every now and then and kdinit5 crashes upon login. kde5 seems to be great in many ways, but i'll go back to 4 for now and won't be able to test this further for some time :)
(In reply to Rihards Olups from comment #2) > unfortunately, after the upgrade suspend/sleep from the menu stopped > working, wifi does not work, kded5 crashes every now and then and kdinit5 > crashes upon login. kde5 seems to be great in many ways, but i'll go back to > 4 for now and won't be able to test this further for some time :) You might have been bitten by two issues at the same time: the Qt 5.5, which was updated, as well as pulseaudio that crashed kded5, kdeinit and some other related processes. Qt5.5 as well as PA have been fixed and I think there is a good chance that the issues might be gone for you too. Can you please re-test and verify?
thanks for the information. unfortunately, at this time i don't have a possibility to test this. i will try to find a way, but can't promise anything in near future.
IMHO I can reproduce the issue. It is related to https://bugreports.qt.io/browse/QTBUG-42985 and no update seemed to help so far. It is either "switching screens", "connecting/disconnecting screens" or "pulling out of docking station" causing the problem under certain circumstances or seemling sporadically. I guess needs a bit more time for testing as this can not be always reproduced easily.
Dupe of the following bug, lets just keep only one around :) *** This bug has been marked as a duplicate of bug 911304 ***