https://bugs.kde.org/show_bug.cgi?id=340267
--- Comment #30 from Dainius Masiliūnas <past...@gmail.com> --- (In reply to michael from comment #29) > > Does it mean, it won't be fixed in 5.5, which probably means it won't be > fixed in OS 42.1, due to a major software update? Possibly. It certainly won't be fixed by Qt devs, although the patch could perhaps be backported by distributions. Again, see this: https://bugreports.qt.io/browse/QTBUG-42985 > Actually, I do not only have this reproducible crash with DP, I also have > occasionally problems with HDMI, which after resuming from suspend stays > black. But switching to another windowmanger, like gnome or entlightment, > everything works pretty well. > > For this reason I have switched the windowmanager, also because KDE5 plasma > has a bug which prevents to restore the complete desktop state, which is > also yet not resolved. Yes, this is also not surprising. It's a Qt bug, it affects the whole of Qt. The bug is that whenever a monitor disappears (gets turned off or disconnected), QScreen becomes a null pointer, and Qt crashes on itself. So it's not specific to DisplayPort (aside from the fact that turning off the screen when on DisplayPort makes it disappear), and using non-Qt window managers obviously means you're not affected. -- You are receiving this mail because: You are watching all bug changes.
