https://bugs.kde.org/show_bug.cgi?id=466674
Aleix Pol <aleix...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aleix...@kde.org
--- Comment #5 from Aleix Pol <aleix...@kde.org> ---
I've been looking into this. Testing didn't bring any crashes.
While your assessment that it might be the placeholder screen kicking in, at
the moment we are already testing for wl_output being null, which should be a
symptom of the placeholder hitting us.
I've put together the following patch for libkscreen, would you be able to
apply it on top of libkscreen?
To test you can use kscreenlocker like you said. Running
"/usr/lib/libexec/kscreenlocker_greet --testing" will make it possible for you
to reproduce it without being locked out of the session. Thank you!!!
----
diff --git a/src/libdpms/waylanddpmshelper.cpp
b/src/libdpms/waylanddpmshelper.cpp
index 021dbf5..32259e1 100644
--- a/src/libdpms/waylanddpmshelper.cpp
+++ b/src/libdpms/waylanddpmshelper.cpp
@@ -114,8 +114,11 @@ private:
{
QPlatformNativeInterface *native = qGuiApp->platformNativeInterface();
wl_output *output = reinterpret_cast<wl_output
*>(native->nativeResourceForScreen(QByteArrayLiteral("output"), screen));
+ qDebug() << "about to crash?" << screen << output << native;
if (output) {
- m_dpmsPerScreen[screen] = new Dpms(get(output), m_dpms, screen);
+ auto x = get(output);
+ qDebug() << "boom" << x;
+ m_dpmsPerScreen[screen] = new Dpms(x, m_dpms, screen);
}
}
--
You are receiving this mail because:
You are watching all bug changes.
