Takes long time to log outrestart/shutdown/

Hi amigos,

My Leap takes long time to log out, reboot or shut down,
Some times it takes 3~5 minutes, and some times maybe more (and as I can’t wait more, I have to press ctrl+backspace twice to restart X server)
I don’t have any problem with hibernation and sleep, and the issue is only when I want to leave my working session.
Also it boots very quickly.

any help will be appreciated :wink:

There have been other threads on this. I’ll quote the advice that Marcelovborro gave on the forum in November. It worked for me (though it didn’t for some others apparently).

.*… It took a 90 seconds timeout waiting a zombi process everytime it turned off the machines. The problem was google chrome. It never kills the “Chrome_ProcessL” process when you exit it. Doing a killall -9 Chrome_ProcessL solved my problem. I am thinking about adding a cron task to kill Chrome_ProcessL periodically since it seems to not affect the running session of google chrome.

If you use sddm as your display manager, switch to kdm. Made a big difference on my system.

Hi Jenspen and thanks for your reply,

So what should i really do? kill chromium process before login out or reboot?
and what did you do that works.

Thanks

Hi swannema and thanks for your reply,

I did that, and I’ll tell you the result :wink:

Thanks

Can you please post the results of the following command:

systemd-analyze blame

Hi lightblue, have you checked that** your particular problem is caused by the chrome (or chromium) process?** When you hit the Escape key while waiting for shut down do you get a message that “a stop job is running” and a countdown of 1 minute and 30 seconds? If that is the case, then I’d strongly suspect that it is at least one Chrome_ProcessL that is holding up the shutdown.

Personally, I use a terminal to “killall -9 Chrome_ProcessL” before every shut down. Or you could run a chron task periodically as was also suggested. Killing the Chrome or Chromium ProcessL is not going to kill Chrome or Chromium, just some associated processes whose nature I researched but can’t remember.

At least, if you will be able to eliminate Chrome_ProcessL as the problem.