Anno domini 2019 Sat, 21 Dec 12:30:53 -0500
 James D Freels scripsit:
> OK.� Had to reboot with TDM active to uncover this issue.
> 
> When I issue systemd-analyze blame , I get:
> 
> systemd-analyze blame
> Bootup is not yet finished 
> (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
> Please try again later.
> Hint: Use 'systemctl list-jobs' to see active jobs
> 
> Of course later never comes since this step continuously hangs. So 
> taking the suggestion, the output from systemctl list-jobs is:
> 
> JOB UNIT�������������������������������� TYPE� STATE
> 147 getty@...������������������ start waiting
>  � 2 multi-user.target������������������� start waiting
>  � 1 graphical.target�������������������� start waiting
> 129 systemd-update-utmp-runlevel.service start waiting
> 105 plymouth-quit-wait.service���������� start running
> 146 getty.target������������������������ start waiting
> 
> 6 jobs listed.
> 
> So, it appears related to plymouth.� Is plymouth used in TDM?

You can saferly purge all plymouth* packages. It's just eyecandy and a source of interestring problems.

Nik



> 
> Also tried systemd-analyze critical-chain, and get identical output
> 
> Bootup is not yet finished 
> (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
> Please try again later.
> Hint: Use 'systemctl list-jobs' to see active jobs
> 
> 
> On 12/21/19 12:18 PM, James D Freels wrote:
> > This is a great suggestion.� I will give it a try and report back later.
> >
> > On 12/21/19 3:02 AM, Nick Koretsky wrote:
> >> On Fri, 20 Dec 2019 18:52:35 -0500
> >> James D Freels <freelsjd@...> wrote:
> >>
> >>> If I boot up under TDM (after running dpkg-reconfigure tdm-trinity 
> >>> first
> >>> to initiate TDM into the boot sequence), it starts fine, but
> >>> continuously hangs in the main console with one of the infamous systemd
> >>> problems wherein we get the "a startjob is running ..." and it NEVER
> >>> ends until rebooted.� The TDM session appears to run fine, and I can
> >>> login and run TDE fine.� However, because the vt1 console is never
> >>> ending waiting to complete, I have no other VT consoles. Essentially, I
> >>> have NO virtual consoles at all.� Further, computer resources are 
> >>> always
> >>> wasted and never ends waiting for the the startup to completely finish.
> >>> This ONLY happens when booting up with TDM.
> >>>
> >>> I can bootup with LXDM or LIGHTDM and this does not happen. Further, I
> >>> can issue a "systemctl stop lightdm" or "systemctl stop lxdm" 
> >>> (depending
> >>> on which is running from the boot), then issue a "systemctl start
> >>> tdm-trinity" and TDM runs fine and there is not a never ending startjob
> >>> waiting to complete.� So, it appears that TDM does not start in the 
> >>> same
> >>> order of the boot sequence as LXDM and/or LIGHTDM which is causing this
> >>> problem.
> >>>
> >>> It is at this point, where I need some help in how to fix it, and I
> >>> suspect that all debian/buster users may have the same issue, but not
> >>> sure of course.� I hope I can help get his bug fixed before the final
> >>> release of TDE for buster.
> >>>
> >> I dont think its a bug in TDE, this looks like some systemd problem, 
> >> so a
> >> steps to deal with systemd problems has to be followed.
> >> Starting with 'systemd-analyze blame'� and 'systemd-analyze 
> >> critical-chain'.
> >>
> >>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-users-unsubscribe@...
> For additional commands, e-mail: trinity-users-help@...
> Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
> Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> 
> 



-- 
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...