the problem was with plymouth!!!

tdm and plymouth (boot splash screen, in ubuntu) are in conflict.
plymouth doesn't shutdown, blocks the ttys and consumes ~5% of CPU (on my machine). plymouth hasn't crashed.

the command, responds that it's running.
sudo plymouth --ping && echo plymouth is running || echo plymouth NOT running

you can stop it in a normal session with this command
sudo plymouth --quit

you can also, deactivate the splash option in grub

edit /etc/default/grub
change this line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT=""
save
and run
sudo update-grub

(Linux mint 18.2 Mate 64bits)

but it looks like it is not a TDE problem - correct?

can this be closed please?

.... yea, my previous comment was a bit unclear.

tdm fails to shutdown plymouth...
It's indeed a bug in tdm.

I have observed similar behavior, when processes at startup do not complete.
After going back from systemd to init behavior is normal.

Can you verify all processes are completed  at startup - I am sure you are using systemd, so try journalctl.

IMO it is problem between systemd and perhaps tde, perhaps not

regards

It seamed to work fine with lightDM with TDE and MATE.

login in MATE with tdm gives the same behavior.
plymouth is still running and messes things up.

I don't think that's a systemd issue
(this time :p)

"TDM fails to shutdown plymouth" - I can confirm this issue, I guess it's a TDM issue. Debian 9 Stretch, TDE 14.0.5 testing.

OK, but I use Stretch with plymouth and TDE (I use the dev branch 14.1 and no systemd as init proc) and I do not have this issue.
I had it twice when using systemd, because startup processes get delayed by systemd. After waiting for some time (systemd times out the startup processes) the rest of the startup actions complete and login prompt on console comes back.

It might be TDE, so could you please provide a way to reproduce it also try alternatively without systemd

ii  systemd                               232-25+deb9u1                               amd64        system and service manager
ii  systemd-shim                          10-3                                        amd64        shim for systemd
ii  sysv-rc                               2.88dsf-59.9                                all          System-V-like runlevel change mechanism
ii  sysvinit-core                         2.88dsf-59.9                                amd64        System-V-like init utilities
ii  sysvinit-utils                        2.88dsf-59.9                                amd64        System-V-like utilities


ii  libplymouth4:amd64                    0.9.2-4                                     amd64        graphical boot animation and logger - shared libraries
ii  plymouth                              0.9.2-4                                     amd64        boot animation, logger and I/O multiplexer
ii  plymouth-themes                       0.9.2-4                                     amd64        boot animation, logger and I/O multiplexer - themes
ii  plymouth-x11                          0.9.2-4                                     amd64        boot animation, logger and I/O multiplexer - X11 renderer


ii  tdebase-trinity                       4:14.1.0-0debian8.0.5+eko3                  all          base components from the official TDE release

".. could you please provide a way to reproduce it also try alternatively without systemd"

@deloptes@yahoo.com
Just proceed a fresh Debian 9 Stretch, TDE 14.0.5 testing, and Plymouth installation and set a Plymouth theme.

It's obviously systemd related, as it appears to be a conflict of TDM and Plymouth systemd service. As mentioned above, other display managers, for ex. lightDM, work fine with Plymouth.

Thanks,

I have experienced the same. I don't recall how it was solved, but there was simple solution to it.

Anyway thank you for the information, if you have a solution, post a patch here.

regards

Added to R14.0.6 bug list

Created attachment 2916 [details]
allow systemd to call plymouth-quit.service

Hello,

Conflicts line in /lib/systemd/system/tdm.service prevents sytemd to call  plymouth-quit.service

Removing or commenting it allows plymouth to terminate, and system to behave as expected.
Tested on debian stretch.

Hope this can help

Indeed I agree because the "After" directive tells systemd to quit the tde.service after getty@tty7.service and plymouth-quit.service, which are mentioned in the "Conflict" directive.

I'm on Debian 10 beta with Plymouth disabled and showing all startup messages through kernel boot arguments, and Trinity R14.0.7 preliminary stable builds, and am able to see that systemd is "waiting for boot process to finish" or something along those lines. I too get no text mode consoles, only blinking cursors.

My only other Debian 10 installation (which I can't currently access as of posting this comment) uses either SDDM or GDM, but not TDM, so I decided to look through the source code for SDDM and found some extra things in their systemd service file (compared to the patch submitted by Bastien) which can be found here: https://github.com/sddm/sddm/blob/v0.18.1/services/sddm.service.in

However, based on the Debian edit of the same source file that I saw, I believe that the Debian version of SDDM starts up on tty7 instead of the upstream setting of tty1, however, it's easier for me to link to the upstream file rather than the Debian file.

Created attachment 3026 [details]
tdm_ServiceAsSDM.patch

The patch of switching TDM in the SDDM mode and I have no conflicts with Plymouth here.

The patch also fixes of Plymouth freeze in waiting of the finish when the file /var/log/boot.log can grow and devour all available disk space on systems with small disks and working 24/7.

I am trying to reproduce this problem but I can't.
Debian boookworm, systemd, plymounth and some theme selected.
Can anyone point me what else is required to reproduce it?

https://mirror.git.trinitydesktop.org/gitea/TDE/tdebase/pulls/247

This is a proposed fix. Could someone help verifying it works fine? I occasionally have the system to hangup during shutdown, but I can't do that systematically, so on my side I can only wait for a couple of weeks and check I don't have any more hang up. If someone can reproduce the issues systematically, it would be great if he/she could test the above proposed fix.

By the way, thanks all the people in this bug report for comments and suggestions.

I found a way to test it systematically. PR has been merged.

Created attachment 3046 [details]
tdm_ServiceAsSDM.patch

The problem is actual one for Debian 9, then I again have  updated the SDM mode patch for that!

In TDE14.1 the bug became even worse, that is the system often hangs at the exit on the black screen even with the SDM patch!!!

Shat is SDM BTW.
I've been using 14.1 for the past 3 years on several machines and with the fix in the systemd service file it never caused a problem.
Are you sure it is caused by tdm.service? Are you running X on tty1/7?

generally speaking the systemd issue of hanging system is caused by various services that do not stop properly. The default timeout for systemd AFAIR is 1,5min. You can reduce the value and will have the system shut down faster.

BR

(In reply to deloptes from comment #21)
> Shat is SDM BTW.

I have applied the SDM patch after get the first hang.

> I've been using 14.1 for the past 3 years on several machines and with the
> fix in the systemd service file it never caused a problem.
> Are you sure it is caused by tdm.service? Are you running X on tty1/7?

The problem was appeared for me just after updating to 14.1 of two fine working Debian 11 system on 14.0.13 and on different hardware.

> generally speaking the systemd issue of hanging system is caused by various
> services that do not stop properly. The default timeout for systemd AFAIR is
> 1,5min. You can reduce the value and will have the system shut down faster.

Today I have seen already a dead hang, not at typical 1 ... 1.5 minutes.

did you press ESC and had a look where it hangs?

I mean I am not sure what exactly are the steps to reproduce
 1. you shut down
 2. TDE exits 
 3. it hangs in plymouth
 4. press ESC and see what service is causing the issue

or have a look at the journal

(In reply to deloptes from comment #23)
> did you press ESC and had a look where it hangs?
There is no reaction at pressing ESC and if with the SDM patch I see the kernel messages, without the patch I see only blinking cursor.

> I mean I am not sure what exactly are the steps to reproduce
I have had reproduction of the problem only two times after your last comment, when after the first reproduction I removed the SDM patch for see the blinking cursor.

(In reply to deloptes from comment #23)
> did you press ESC and had a look where it hangs?
And the sequence is:
1. shut down
2. TDE exits
3. the completely black screen is appeared with blinking cursor in the top left angle, where ESC doesn't work and what can last from 20 seconds and up to infinity  (one time).
4. the plymoth splash screen is appeared after from 20 seconds or never and power off

For example see this file — http://ftp.oscada.org/Misc/VID_20230723_161513.mp4

Your access to the server resources is FORBIDDEN, due to you are detected as an attacker!!!
If that is wrong, please write a claim EMail for removing your IP from the black list.
Sorry for the inconvenience!

(In reply to deloptes from comment #27)
> Your access to the server resources is FORBIDDEN, due to you are detected as
> an attacker!!!
Sorry, I have opened the access!