With the latest version from git, I noticed a strange behavior of the displaymanager. I tried lightdm and also KDM, but both gave the same effect. When the displaymanager is active, I couldn't switch to any other virtual console and upon logon, the KDE splash screen was displayed with graphic artifacts (lines, etc). Once the KDE loaded, the screen became garbled and unusable.
Checking various components, I found out that it was plymouth that was causing this behavior. It seems that the displaymanager was not able to detect that plymouth was running or couldn't kill it. (I couldn't validate this, as I couldn't switch to a different virtual console).
I tried to bisect the git commit that caused this effect and started with the official tarball of 0.8.7. On openSUSE, the only added patch were the three commits regarding(related) using sockets instead of the pid-file. Rebuilding plymouth locally, I found that the commit to have a second start of plymouthd finish silently (and successfully) is causing this effect.
Reverting back to having EX_UNAVAILABLE as a returnvalue, resolved the indicated issues.
The KDM patch used is the same one as Fedora is using and I believe that lightdm is using a similar approach. I didn't had GDM installed, but all three of them are using plymouth --ping to detect if plymouth is running.
Any chance you could attach the output of
from when its sitting in the broken state ?
Unfortunately the system is inaccessible at that moment. None of the virtual terminals seem to be working and the graphical session ends up in a non-usable session.
Sorry about this.
we're seeing this in fedora now too:
I've fixed it with this commit I believe:
But i'm still getting a separate occasional hang up which I believe to be a GDM problem. I'm investigating it now.
on Mar 27, 2017 at 02:54:00.
(provided by the Example extension).