I'm running Mint 18.4 Cinnamon on a dual-boot (Mint being my default OS).

When I turn off my pc, the Mint splash screen stays on for a few minutes before my computer shuts down. I've come across a similar issue after restarting my pc.

Any thoughts on this matter?

I think all that splash screen is doing is covering up what is going on in the background, which is spiting out what it is doing to the screen while shutting down your system.

Thank you for your quick reply!

I usually run some kind of heavy programs on my pc like editing over 100 pages in Sribus, while having multiple tabs opened in my web browser + several windows opened in Gimp and Inkscape.

This might be the reason why my computer takes several minutes to shut down after I close down all my programs?

I don't know, maybe, got a turn off your splash screen so you can read your shutdown messages.

I have to admit I'm not sure how to turn off the splash-screen but you could press Ctrl+Alt+F1 and see whether any messages are displayed. As mentioned above it's not likely that the spplash-screen is causiong delays though removing it would, in my opinion, be the right thing to do anyhow since you should then see system messages.

Are you exiting all of these programs before trying shutdown? Or just asking it to shutdown with everything still up?

Try the former and quit everything before you do a shutdown.

Sounds like the splash isn't the issue, just the lengthy shutdown time.

Just an off-topic note that there is no such thing as Mint 18.4.

https://linuxmint.com/download_all.php

Back on topic, I agree that the splash screen is a red herring. It is the time that the system is taking to shutdown that appears to be of concern to the OP.

Can I suggest that the OP reboots their machine, does nothing for a minute or so (just to give the system time to properly start up), then shuts down the system and sees how long this takes compared to normal.

The issue did occure after exiting all programs mentioned before. I will try to turn-off the splash screen and will keep you updated on my shutdown messages and if I'm still experiencing any lenghty shutdown time.

My bad, I'm running Linux Mint 18.3 Sylvia...

I turned off the splash screen. To do so, edit the grub file in /etc/default/:

- Replace "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

by "GRUB_CMDLINE_LINUX_DEFAULT=""

- Save the file and close the editor

- Run sudo update-grub to regenerate the grub config files

I opened all the programs I used to work with and let them run for a while before exiting them.

The shutdown time is now a few seconds. I'm not sure if removing the splash screen did the trick or not though. I will let you guys know if the issue occurs again.

Thank you.

2 members found this post helpful.

Thanks for the update, I have no idea why I didn't think of it last time but, I think. I have used "NoSplash" or similar now I read this.
Now I wonder whether the process to get and display the image may cause a race condition?

Here's an update after the same issue mentioned in the OP occurred today.

This time, my pc never managed to shut down. I'm attaching some screen shots of the error messages. Below is one of them:

"A start job is running for /dev/disk/by partuuid/2f78ab05-7f96-4227-bfbe-936e44945914 (22min 58s / no limit)"

Attached Thumbnails

     

Oh ICU got systemD .. yeah it does that... if a hdd is doing something or something on the system is doing something it just hangs like that (sometimes), it bugs me to no end. I just pull the plug on it sometimes.

you just need to remember what you got running when you shut it down, to then check to see if that was in, in some instances. so Yeah I am definitely not an expert on systemD by no means. that is just me plan of attack on it. just hard shut down it (kick it just to show it who's boss).

with that one check you UUIDs on your fstab and actual drive partition(s) to make sure they match.

(you) I, someone, usually gets them ones when boot up if partitions UUIDs changed and fstab no updated for whatever reasons.

I notice a mention of not being able to activate swap. That suggests to me that your swap may not be allocated correctly or the machine is being told to hibernate. Try disabling swap, perhaps?