https://bugs.kde.org/show_bug.cgi?id=368494
Dave Gilbert <gilbertd+...@treblig.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gilbertd+...@treblig.org
--- Comment #4 from Dave Gilbert <gilbertd+...@treblig.org> ---
The KDE side bug looks the same as:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865001 (which I reported)
and
https://bugzilla.redhat.com/show_bug.cgi?id=1477592
and well, maybe https://bugzilla.redhat.com/show_bug.cgi?id=1406752
In my case the X server is dieing for other reasons ( a qxl bug) and I suspect
that's the same problem with this case; but in either case KScreen shouldn't
be segging. A bit of debug in XRandRScreen::toKScreenScreen and I see that:
#0 XRandRScreen::toKScreenScreen (this=0x559dd8b68980) at
./backends/xrandr/xrandrscreen.cpp:68
screenResources = {d = 0x0}
kscreenScreen = {value = 0x559dd8b78a70, d = 0x559dd8b78b90}
#1 0x00007fe0e9b18aba in XRandRConfig::toKScreenConfig (this=<optimized out>)
at ./backends/xrandr/xrandrconfig.cpp:117
config = {value = 0x559dd8b7ea80, d = 0x559dd8b7eb30}
features = {i = 3}
kscreenOutputs = {d = 0x559dd8b74bb0}
which I guess is because X has died and the screens are well and truly gone.
What's the right level to check for this and clean up?
--
You are receiving this mail because:
You are watching all bug changes.
