https://bugs.kde.org/show_bug.cgi?id=344813
Daniel Vrátil <dvra...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version Fixed In| |5.5.5
Resolution|--- |FIXED
Latest Commit| |http://commits.kde.org/libk
| |screen/d3c0b50e3b23c4f4839f
| |15dda3af4361939ae484
Status|UNCONFIRMED |RESOLVED
--- Comment #7 from Daniel Vrátil <dvra...@kde.org> ---
Git commit d3c0b50e3b23c4f4839f15dda3af4361939ae484 by Daniel Vrátil.
Committed on 13/02/2016 at 14:25.
Pushed by dvratil into branch 'Plasma/5.5'.
XRandR: handle changeOutput() without CRTC better
It is possible that XRandROutput counterpart to KScreen::Output does not have
a CRTC set while the KScreen::Output reports itself as enabled. This leads to
changeOutput() hitting an assert, because we assumed that such case can never
happen. Now we know it can, so instead when changeOutput() is called for an
output without CRTC, we fallback to calling enableOutput().
FIXED-IN: 5.5.5
M +2 -2 backends/xrandr/xrandrconfig.cpp
http://commits.kde.org/libkscreen/d3c0b50e3b23c4f4839f15dda3af4361939ae484
--
You are receiving this mail because:
You are watching all bug changes.
