I tested the ppa in comment #5, and I note the following changes. Environment is a docked laptop with 2 external displays.
When the laptop is removed from the dock (external displays disconnected), I no longer receive a segfault for plasmashell, but the panel does not automagicailly resize to the new resolution. When the external displays are reconnected, plasmashell segfaults (same as previous/xenial behavior). I think this issue is resolved in QT5.5, but not specific to this bug/patch. Atleast I don't have to restart plasma every time I dock/undock, but behavior is still less than optimal. Progress though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1548766 Title: Plasma crashes when the monitor is disconnected (when it sleeps, in some cases) Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: I'm reporting this on behalf of a coworker who has a 4K monitor, which disconnects whenever it sleeps. Older monitors didn't do that; but Qt 5.5 tries to be honest about it: the QScreen is destroyed whenever its corresponding monitor is disconnected, QGuiApplication::primaryScreen() returns null, and so on. KDE developers have been complaining. So in Qt 5.6 we made it keep the last-remaining QScreen as a fake instance, whenever the last monitor is disconnected. The main patch is here https://codereview.qt-project.org/#/c/138201/ You might need to cherry-pick that (a094af001795c9651b299d700a992150d1aba33a in qtbase) for as long as you are shipping Qt 5.5, to get Kubuntu behaving decently. It's relevant on Ubuntu 16.04. Too bad that Ubuntu LTS is not shipping the LTS Qt 5.6 release, but I know we are behind on our release schedule. Some users have also reported that their laptop's screen disconnects when it sleeps. And I have often experienced 5.5-based builds of Creator crashing or disappearing when I switch machines on my KVM. So, sorry that we didn't fix it sooner. It was my mistake for believing that modeling disappearing screens "correctly" was a good idea: it turned out to be a platform inconsistency which developers were not ready for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1548766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
