Skip to main content
36 events
when toggle format what by license comment
Sep 24, 2021 at 17:00 answer added Thomas Stöckel timeline score: 0
Jul 30, 2021 at 12:09 answer added Glyn Adgie timeline score: 0
May 14, 2020 at 23:48 answer added Frank Awadi timeline score: 0
Aug 11, 2019 at 10:52 answer added ArianJM timeline score: 2
Mar 16, 2019 at 21:40 comment added Santi This and the beep are the 2 most annoying things about linux
Jan 24, 2019 at 21:50 answer added mzuther is on OpenAI strike timeline score: 43
Aug 3, 2018 at 9:15 answer added prosoitos timeline score: 1
Apr 25, 2018 at 18:55 answer added stueja timeline score: 2
Feb 13, 2018 at 7:15 answer added Dennis Cote timeline score: 4
Jan 20, 2018 at 2:03 review Close votes
Jan 22, 2018 at 0:35
Jan 20, 2018 at 1:47 history edited Jeff Schaller CC BY-SA 3.0
grammar tweaks
Dec 13, 2017 at 12:36 answer added not2qubit timeline score: 3
Sep 15, 2016 at 8:27 comment added user190055 For me the Private Internet Access VPN client software turned out to be the cause (on Ubuntu 16.04), as suggested here
Jul 23, 2016 at 3:39 history edited dmn CC BY-SA 3.0
Added a note at the end.
Jul 21, 2016 at 9:07 answer added MightyPork timeline score: 57
Jun 29, 2016 at 22:04 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
May 19, 2016 at 20:49 answer added Diego Juliao timeline score: 5
Apr 4, 2016 at 13:25 history tweeted twitter.com/StackUnix/status/716980020535754752
Apr 3, 2016 at 9:15 comment added n.st @macnguyen Sorry, I want thinking correctly. Remember how the dmesg output contained messages from after the stop job? The script from "Diagnosing Shutdown Problems" runs after the 90 second timer has ended and the session has been killed forcibly, so of course loginctl can't find it. I don't know a better solution off the top of my head, though...
Apr 3, 2016 at 1:49 history edited dmn CC BY-SA 3.0
deleted 7 characters in body
Apr 3, 2016 at 1:23 comment added dmn @aurelien @n.ts I have store loginctl session-status c2 to shutdown-log, but there is nothing in it. So I change loginctl session-status c2 by systemd-cgls. You can see the new log in Addition 2.
Apr 3, 2016 at 1:21 history edited dmn CC BY-SA 3.0
added 738 characters in body
Apr 2, 2016 at 20:01 comment added n.st @aurelien Is it always c2 that's causing the timer on shutdown? If so, you could follow Diagnosing Shutdown Problems again and store loginctl session-status c2 instead of dmesg.
Apr 2, 2016 at 19:40 comment added aurelien @n.st yep, but I have just one scope on all machine never two like that
Apr 2, 2016 at 19:18 comment added Natecat github.com/systemd/systemd/issues/2691 This may be relevant
Apr 2, 2016 at 18:42 comment added n.st @aurelien Have you checked loginctl session-status c2 yet?
Apr 2, 2016 at 17:44 comment added Runium You might get a (temporary) fix by this hack: Create /etc/sysctl.d/50-coredump.conf with contents: kernel.core_pattern=core , ref: github.com/systemd/systemd/issues/1615#issuecomment-203507283
Apr 2, 2016 at 17:26 history edited dmn CC BY-SA 3.0
added 9 characters in body
Apr 2, 2016 at 17:17 history edited dmn CC BY-SA 3.0
added 9 characters in body
Apr 2, 2016 at 17:15 comment added dmn @aurelien Here is the output of who: the 1st line thuyenarc pts/0 2016-04-02 22:26 (:0) and the 2nd line thuyenarc pts/1 2016-04-03 00:15 (:0)
Apr 2, 2016 at 17:14 comment added dmn @n.st I can't get into tty when the message pops up.
Apr 2, 2016 at 16:58 comment added aurelien you can use dpaste.com or any type of paste tool to link your log (emacs have a dpaste plugin you can nstall if you need)
Apr 2, 2016 at 16:56 comment added aurelien what does who command say when you are logged in?
Apr 2, 2016 at 16:49 comment added n.st To check what's running in that ominous session c2 that isn't terminating on its own, use loginctl session-status c2. I'm not sure if you can still switch to a getty during shutdown, but try hitting Ctrl+Alt+F2 when "A stop job is running …" pops up. If that works, you'll get a login prompt and will be able to use loginctl command. If you don't get a login prompt, follow the same steps you used for dmesg, but store the output of loginctl session-status c2 instead. (That's all assuming that it's always "c2" that's hanging, not another session each time.)
Apr 2, 2016 at 16:46 comment added n.st Unfortunately the dmesg output you pasted isn't very informative — it shows the WiFi disconnecting when you hit the shutdown button (3048 seconds after system bootup) and then nothing until the 1m30s timer expires and the system continues shutting down (at 3139 seconds).
Apr 2, 2016 at 16:23 history asked dmn CC BY-SA 3.0