https://bugs.kde.org/show_bug.cgi?id=446160
--- Comment #2 from dej...@gmail.com ---
I have some deeper insight on what's going on here.
Out of desperation, I've built kwin 5.23.4 (the version I currently have
installed) from sources, and added some more logging in the relevant places, to
see what goes wrong.
Until now, I thought the main problem is this part:
kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
kwin_wayland_drm: No suitable DRM devices have been found
But as it turns out, the actual problem is already this line:
kwin_core: Failed to activate /org/freedesktop/login1/session/_35 session.
Maybe another compositor is running?
It's this method in session_logind.cpp:
static bool activate(const QString &sessionPath)
{
const QDBusMessage message = QDBusMessage::createMethodCall(s_serviceName,
sessionPath, s_sessionInterface, QStringLiteral("Activate"));
// ---- The problem occurs here:
const QDBusMessage reply = QDBusConnection::systemBus().call(message);
// ---- Returns "Interactive authentication required"
return reply.type() != QDBusMessage::ErrorMessage;
}
Rest of the error output (kwin_wayland_drm) is caused simply by the fact, that
because of the failure above, NOOP session is actually injected in the code
instead of the "real" one, and that (understandably) is not even trying to do
anything with the real hardware.
But, what to do about the "Interactive authentication required" thing, I just
don't know...
Does anybody have any idea, please?
--
You are receiving this mail because:
You are watching all bug changes.
