jdd composed on 2016-02-04 20:38 (UTC+0100):

I have a problem that hit me specially because I just did some edits on my config and so had to reboot often.

I get this message:

"a stop job is running for X Display manager"

with a 95s (1:35 mn) counter.

This is a recurrent problem (?), found everywhere on the net, but with no visible solution. I had it today both with Leap and 13.2 (same computer, of course different disk/partition). Some time ago I had the same, but at start.

I wondered if it was not some fsck?

Many people seems to think it's a systemd bug, but as we can find post on the subject for the two last years at least, I'm unsure of that.

does somebody have an explanation or a fix?

I can't count the times I've seen reboot/shutdown delays due to "a stop job is running...". X Display Manager is just one. A session for root is another. Problems with mismatches between fstab and existing filesystems is another. Many times CAD is of no use, and power button or reset switch are required to make anything happen. There are other examples that don't immediately come to mind, but all AFAICT began after systemd replaced sysvinit. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org