Hello everyone,

I upgraded by Debian 8 system to a Debian 9 a few months back and everything has been just fine until a couple of weeks. The past 5-6 shutdowns have been taking a long time like 5 minutes. I looked at the /var/log/messages and the only message that looks really odd is:

Jan 13 13:47:06 homecomputer gnome-session[1267]: gnome-session-binary[1267]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

This was around the last time I tried to turn it off. Any ideas if this is the problem and how to solve this? I wonder why this showed up all of a sudden.

Thanks in advance.

Did the system displays all messages when it's shuting down?

Thanks for the response. Almost all the messages in /var/log/messages are actually with respect to startup rather than shutdown. These were the last messages before my next startup the next day which I is why I zoomed in on them. But it is just my guess that they are shutdown messages while they might not be. Are shutdown logs saved anywhere? Or can I save them anywhere to see what is failing to close?

Thanks again.

i'm sorry i cannot help you!

but this message:
is very likely harmless, pertaining to the user interface only, no connection to systemd shutdown processes.

You should activate displaying of messages of shutdown(sadly it seems that Debian takes the wrong path of hiding things like other mainstream distributions) to see wich step takes time.

I have these kind of problems when a samba share is mounted. To solve it I put a corresponding umount command in a script called at shutdown. There must be other solutions using systemd.

Will have to find out how to turn on the shutdown messages. As for a Samba server, I don't think I have one. I have an Apache server running as I use my local machine to try out Wordpress themes. Do you think that might be a problem? Anyway, will get back to you soon.

Thanks for the responses.

^ it is likely to be network related, but without additional information there's nothing to say.

archwiki has very good articles on systemd: https://wiki.archlinux.org/index.php/Systemd

Some advice on increasing logging verbosity...

https://wiki.debian.org/systemd#syst...up_or_shutdown

Analyze the end of the pager from last boot...
or last 300 messages perhaps...

Thanks for the responses.

During the last shutdown, I noticed a message:

"Performing apt-get update and cleanup"

This is where the system stood still for a long time. So I am guessing it is either trying to connect to the server and could not or else something else happened. So now I guess I need to figure out which conf file has this setting and turn it off.

Performing apt-get update at shutdown is nonsense!

So, I uninstalled unattended-upgrades and still it hangs. But now I saw this other message:

A stop job is running on MySQL community server [../10 min]

So it waits for 10 minutes and then kills it. I found this link:
https://askubuntu.com/questions/8920...erver-on-ubunt

Apparently, I need to shut down mysql first. Also, I noticed another problem which the last poster on the thread pointed out. My system clock at startup is one hour ahead. This I think messes up the mysql time. Suggested to run dpkg-reconfigure tzdata.

Will shutdown mysql tonight first and check. Then try out the time reconfiguration. Hopefully, getting closer ...