Jump to content

So I installed the latest Mint Cinnamon distro and actually like it a lot, and runs quite well on my laptop. Only downside is that whenever I shut it down or run sudo shutdown now it freezes the screen and hangs for a solid minute and a half to two minutes before actually shutting off. Quite annoying because I’m at Uni, so I really don’t want to shut my laptop down early at the end of class or sit there for awhile during shutdown at the end. Any possible solutions? Also I’m half way debating just switching to arch Linux as well, if that’ll fix my issue... I’ve got elementary on my old laptop and that works quite well, so possibly that os is a consideration. Lol 

Spoiler

 

LTT's Fastest single core CineBench 11.5/15 score on air with i7-4790K on air

Main Rig

CPU: i7-4770K @ 4.3GHz 1.18v, Cooler: Noctua NH-U14S, Motherboard: Asus Sabertooth Mark 2, RAM: 16 GB G.Skill Sniper Series @ 1866MHz, GPU: EVGA 980Ti Classified @ 1507/1977MHz , Storage: 500GB 850 EVO, WD Cavier Black/Blue 1TB+1TB,  Power Supply: Corsair HX 750W, Case: Fractal Design r4 Black Pearl w/ Window, OS: Windows 10 Home 64bit

 

Plex Server WIP

CPU: i5-3570K, Cooler: Stock, Motherboard: ASrock, Ram: 16GB, GPU: Intel igpu, Storage: 120GB Kingston SSD, 6TB WD Red, Powersupply: Corsair TX 750W, Case: Corsair Carbide Spec-01 OS: Windows 10

 

Lenovo Legion Laptop

CPU: i7-7700HQ, RAM: 8GB, GPU: 1050Ti 4GB, Storage: 500GB Crucial MX500, OS: Windows 10

 

 

Link to comment
https://linustechtips.com/topic/969614-linux-mint-shutdown-hang/
Share on other sites

Link to post
Share on other sites

This used to be a common bug, if im not mistaken the system waits for something before shutting down which never happens.

what kernel are you on?

either look for what is causing it to wait and solve it or mess with the system.conf and user.conf files.

 

Edit. A bypass used to be turning off network and signing off before shutting down (works in most cases)

Link to post
Share on other sites

16 hours ago, nrzn said:

This used to be a common bug, if im not mistaken the system waits for something before shutting down which never happens.

what kernel are you on?

either look for what is causing it to wait and solve it or mess with the system.conf and user.conf files.

 

Edit. A bypass used to be turning off network and signing off before shutting down (works in most cases)

Kernel is 4.15.0-33-generic

 

i tried turning off networking and shutting down and it was still slow af. 

Spoiler

 

LTT's Fastest single core CineBench 11.5/15 score on air with i7-4790K on air

Main Rig

CPU: i7-4770K @ 4.3GHz 1.18v, Cooler: Noctua NH-U14S, Motherboard: Asus Sabertooth Mark 2, RAM: 16 GB G.Skill Sniper Series @ 1866MHz, GPU: EVGA 980Ti Classified @ 1507/1977MHz , Storage: 500GB 850 EVO, WD Cavier Black/Blue 1TB+1TB,  Power Supply: Corsair HX 750W, Case: Fractal Design r4 Black Pearl w/ Window, OS: Windows 10 Home 64bit

 

Plex Server WIP

CPU: i5-3570K, Cooler: Stock, Motherboard: ASrock, Ram: 16GB, GPU: Intel igpu, Storage: 120GB Kingston SSD, 6TB WD Red, Powersupply: Corsair TX 750W, Case: Corsair Carbide Spec-01 OS: Windows 10

 

Lenovo Legion Laptop

CPU: i7-7700HQ, RAM: 8GB, GPU: 1050Ti 4GB, Storage: 500GB Crucial MX500, OS: Windows 10

 

 

Link to post
Share on other sites

17 hours ago, Br3tt96 said:

So I installed the latest Mint Cinnamon distro and actually like it a lot, and runs quite well on my laptop. Only downside is that whenever I shut it down or run sudo shutdown now it freezes the screen and hangs for a solid minute and a half to two minutes before actually shutting off. Quite annoying because I’m at Uni, so I really don’t want to shut my laptop down early at the end of class or sit there for awhile during shutdown at the end. Any possible solutions? Also I’m half way debating just switching to arch Linux as well, if that’ll fix my issue... I’ve got elementary on my old laptop and that works quite well, so possibly that os is a consideration. Lol 

There is for some reason a process which does not shut down properly and systemd waits minutes before killing it. You should give us some logs...Anyway a workaround for shutting down the computer immediately is to press Ctrl+alt+canc a lot of times until you'll see on the screen "forcing shutdown" or something similar

Link to post
Share on other sites

Just now, Lukyp said:

There is for some reason a process which does not shut down properly and systemd waits minutes before killing it. You should give us some logs...Anyway a workaround for shutting down the computer immediately is to press Ctrl+alt+canc a lot of times until you'll see on the screen "forcing shutdown" or something similar

How would I get logs for that? As soon as I shut it down it freezes the screen for the duration of the shutdown time 

Spoiler

 

LTT's Fastest single core CineBench 11.5/15 score on air with i7-4790K on air

Main Rig

CPU: i7-4770K @ 4.3GHz 1.18v, Cooler: Noctua NH-U14S, Motherboard: Asus Sabertooth Mark 2, RAM: 16 GB G.Skill Sniper Series @ 1866MHz, GPU: EVGA 980Ti Classified @ 1507/1977MHz , Storage: 500GB 850 EVO, WD Cavier Black/Blue 1TB+1TB,  Power Supply: Corsair HX 750W, Case: Fractal Design r4 Black Pearl w/ Window, OS: Windows 10 Home 64bit

 

Plex Server WIP

CPU: i5-3570K, Cooler: Stock, Motherboard: ASrock, Ram: 16GB, GPU: Intel igpu, Storage: 120GB Kingston SSD, 6TB WD Red, Powersupply: Corsair TX 750W, Case: Corsair Carbide Spec-01 OS: Windows 10

 

Lenovo Legion Laptop

CPU: i7-7700HQ, RAM: 8GB, GPU: 1050Ti 4GB, Storage: 500GB Crucial MX500, OS: Windows 10

 

 

Link to post
Share on other sites

11 minutes ago, Br3tt96 said:

How would I get logs for that? As soon as I shut it down it freezes the screen for the duration of the shutdown time 

Mint like Ubuntu should store the logs in /var/logs.

Honestly for this particular issue I would check the dmesg, which should be stored on kern.log, just look at the clock... There will be more sessions.

I don't remember exactly how systemd shutdown logging works, you can try journalctl command which should store logs from there, I don't know if there can be some parameters for further information. I'm not into a Linux system currently so I cannot check 

Link to post
Share on other sites

14 hours ago, EPENEX said:

It could be systemd hanging up. Edit /etc/systemd/system.conf and change the time out to something like 5 seconds

DefaultTimeoutStopSec=5s

Didn’t work. I edited it via sudo nano /etc/system/system.conf 

Spoiler

 

LTT's Fastest single core CineBench 11.5/15 score on air with i7-4790K on air

Main Rig

CPU: i7-4770K @ 4.3GHz 1.18v, Cooler: Noctua NH-U14S, Motherboard: Asus Sabertooth Mark 2, RAM: 16 GB G.Skill Sniper Series @ 1866MHz, GPU: EVGA 980Ti Classified @ 1507/1977MHz , Storage: 500GB 850 EVO, WD Cavier Black/Blue 1TB+1TB,  Power Supply: Corsair HX 750W, Case: Fractal Design r4 Black Pearl w/ Window, OS: Windows 10 Home 64bit

 

Plex Server WIP

CPU: i5-3570K, Cooler: Stock, Motherboard: ASrock, Ram: 16GB, GPU: Intel igpu, Storage: 120GB Kingston SSD, 6TB WD Red, Powersupply: Corsair TX 750W, Case: Corsair Carbide Spec-01 OS: Windows 10

 

Lenovo Legion Laptop

CPU: i7-7700HQ, RAM: 8GB, GPU: 1050Ti 4GB, Storage: 500GB Crucial MX500, OS: Windows 10

 

 

Link to post
Share on other sites

4 hours ago, Br3tt96 said:

Didn’t work. I edited it via sudo nano /etc/system/system.conf 

You could try journalctl command with those parameters: 

journalctl -b -2 

Which should show the current bootup systemd logs and the one before, so make sure you do that right after a fresh reboot, if needed use pastebin

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×