[11:25] <pchoo> Hi, Anyone able to help me diagnose an issue I'm having?  I'm on 16.04.1, and recently did a dist-upgrade (a few weeks ago).  Since then when I log out or try to shut down, I end up with a blank screen which has an underscore in the top left, and I am unable to change TTY or interact in any way, the only thing I can do is hold the power button and reboot.
[11:25] <pchoo> I have since done another dist-upgrade to see if that resolves the issue, but I am not too familiar with trouble shooting linux
[11:34] <mgedmin> how long have you waited?
[11:38] <pchoo> I've left it for about 20 minutes before
[11:38] <pchoo> lately I've had less patience as I usually shut down before I have to leave work
[11:39] <pchoo> it only started after I ran dist-upgrade a short while ago.  I intend to do a fresh install with 16.10 at some point, but was going to wait until closer to christmas where we have some down time
[11:40] <pchoo> the only issues I can see on google are to do with booting up, and not with shutting down or logging out.
[11:41] <pchoo> mgedmin: If you've got any advice on what I can look at, or how I can help diagnose what is going on, or any requests for information, please let me know
[11:41] <mgedmin> ok, 20 minutes is overkill
[11:42] <mgedmin> altough... in 16.04 I had poweroffs/reboots taking 15-20 minutes with a black screen
[11:42] <mgedmin> turned out it was swapoff taking this much time
[11:42] <mgedmin> if I opened a terminal and did a 'sudo swapoff -a' before initiating the reboot, then I had to wait maybe 15 minutes for swapoff to do its job, and then the reboot was fast
[11:43] <pchoo> How can I check to see if that's what is causing the issue for me?
[11:43] <pchoo> just try running that in a terminal and see if I can do reboot after?
[11:43] <pchoo> I am using a laptop with optimus, however I am using the intel drivers only right now (I believe)
[11:43] <mgedmin> the way I diagnosed the issue was adding a bunch of debug prints to my init.d scripts (it was before 16.04 and systemd)
[11:44] <mgedmin> with 16.04 there's now /usr/share/doc/systemd/README.Debian.gz that tells you how to diagnose shutdown issues
[11:44] <mgedmin> but I suggest trying a manual sudo swapoff -a before you reboot, to see if it's maybe the same issue
[11:44] <mgedmin> alternatively, before you reboot, check how much swap is in use
[11:45] <pchoo> Ok, thank you, I'll have a quick look at the document, then give that a try
[11:45] <pchoo> ok
[11:45] <mgedmin> if nearly 0, no need to try this, it's a different issue
[11:45] <mgedmin> I used to have ~4 gigs of swap in use
[11:45] <pchoo> KiB Swap: 16658428 total, 16658428 free,        0 used. 13500772 avail Mem
[11:45] <pchoo> That's the line from top
[11:46] <mgedmin> there goes my guess
[11:48] <pchoo> mgedmin: thanks for trying.  I'll have a look at the debug shell
[11:53] <pchoo> mgedmin: well, that didn't work, or rather, I could enter the shell before I tried shutting down, but not after I got the screen with the underscore, and there was no keyboard response from the usb keyboard, nor the laptop keyboard
[11:54] <mgedmin> :(
[11:57] <pchoo> Any other suggestions? Thank you for your help so far
[20:06] <shubham> guys, i seek your help.
[20:06] <shubham> I can't understand the reason why my ubuntu boots sometimes into initramfs prompt.
[20:06] <shubham> then i have to use a manual fsck to /dev/sdaX and it consumes a lot of time
[20:09] <shubham> ?
[20:13] <shubham> @elky there?
[20:13] <meetingology> shubham: Error: "elky" is not a valid command.
[20:13] <shubham> elky: there?
[20:24] <elky> You'll get a better response from #ubuntu where there are more people. Some of them may even be out of bed.
[20:29] <shubham> i am from east so, its already 2:00 in the morning.
[21:09] <shubham> Mia: can you help?
[23:56] <CountryfiedLinux> howdy
[23:57] <CountryfiedLinux> What version of Gnome does 16.04 have?