[07:21] <zleap> back
[07:23] <zleap> so 18.04 stops loading at the point where it is loading the user manager for pid 120
[07:24] <zleap> i have no idea how to do all the previously mentioned systemd stuff
[07:54] <brobostigon> morning boys and girls.
[10:10] <zmoylan-pi> that was a long night... listening to bird song across the world... can't wait for next year...
[10:19] <SuperEngineer> !patience | zmoylan-pi
[10:19] <SuperEngineer> please wait for next year
[10:19] <SuperEngineer> next year may not be online right now
[10:19] <SuperEngineer> :D
[10:21] <SuperEngineer> [I hear next year usually comes online only after new year's eve has gone off line
[11:28] <fujisan> sup popey and ikonia
[14:33] <zleap> just a question on ubuntu not being able to boot, it stops when loading user manager
[14:33] <zleap> as the system is dual boot I can view the file system ubuntu is installed to from my mint install,  what should i look for on the ubuntu file system to try and narrow down (or for people to help me do that) what the issue may be ?
[14:34] <penguin42> hmm what's 'user manager'
[14:35] <zleap> when booting ubuntu,  i can press esc and get messages during boot
[14:35] <zleap> however when it gets to user manager for pid 120 the system just hangs
[14:35] <zleap> oddly the live cd works fine,  it is just post install it has failed
[14:35] <zleap> i can also boot fine with recovery mode
[14:36]  * penguin42 isn't sure what 'user manager' is
[14:36] <zleap> neither am i
[14:37] <zleap> i am just trying to copy the message i get
[14:37] <zleap> however there 'has' to be a log of this somewhere on the file system it is a case of finding  that then copying the info to pastebin or somewhere to help
[14:39] <Guest32919> Hi guys. Just installed ubuntu 18.04 and find that image scan for linux is not identifying my epson printer anymore. It worked fine on earlier versions of ubuntu. Did a bit of googling but no much help. it says sane change has brken soem thrid party scanner drivers on launchpad. Can  some one guide me in the right directions. thanks
[14:39] <Guest32919> zleap,
[14:39] <penguin42> zleap: If you can boot into recovery you can try journalctl -b-1  to get the log of messages from the last boot
[14:40] <zleap> thanks
[14:43] <zleap> is there anything specific i should be lookinng for int eh log
[14:43] <penguin42> the thing that made it break :-)
[14:43] <zleap> ok
[14:45] <zleap> i will give that a go,  brb
[14:50] <Nokaji> That's a point, my 16.04 hasn't performed any upgrade to 18.04 - I guess it is in my settings, somewhere
[14:52] <Nokaji> I have selected: Notify me of a new ubuntu version "for long term support versions"
[14:56] <penguin42> yeh but they don't normally enable lts upgrades until a bit later for stuff to shake out
[15:07] <Nokaji> Ah, okay ... it's not just me then
[15:07] <Nokaji> maybe I can/should wait, then ... hopefully not too long though
[17:32] <zleap> ok back,  i decided to re install 18.04 and still get the same error
[17:32] <zleap> started session c1 of user gdm
[17:32] <zleap> started user manager for uid 120
[17:33] <zleap> after which system stops repondingm but I can reboot with ctrl-alt-sysrq RSEIUB
[17:33] <zleap> so there may be some kernel magic I can use to do something other than reboot the system
[17:39] <penguin42> zleap: Can you ctrl-alt-f2/f3 at that point to get a text console ?
[17:43] <zleap> i will try later, i need to reboot for that
[17:44] <zleap> i am sure I ahve tried and it failed but if I manage that, i will see if I can log in
[17:45] <penguin42> zleap: My guess would be that it's a graphics driver choking when it tries to start up the graphics
[17:45] <zleap> so why do I get a live session ok
[17:45] <penguin42> yeh, good question
[17:46] <zleap> ill grab a netbook and instal on there,  it will be slow but just to figure out if there is an issue with the install media
[17:47] <zleap> is there a list of key bindings similar to ctrl-alt-sysrq RSEIUB
[17:47] <zleap> not sure exactly what to search for for that
[17:47] <penguin42> not sure; there's two separate things there
[17:48] <penguin42> the alt-sysrq stuff is documented somewhere, but that's quite separate to the virtual console switching
[17:48] <zleap> yeah but if there is a sysrq thing to release the keyboard it may then allow me to use alt-f2 etc if it doesn't work initially
[17:49] <penguin42> note ctrl-alt-f2 or try f3) - you shouldn't need any other keys for that unless it's very very hung
[17:50] <zleap> yeah
[17:52] <zleap> https://linuxconfig.org/how-to-enable-all-sysrq-functions-on-linux#h6-the-sysrq-magic-key
[17:54] <zleap> no idea what that page is doing,  trying to print it and it says it can't print as it page still loading
[17:54] <zleap> i want to just print to pdf for reference
[18:00] <zleap> ok i need to do some reading in
[18:00] <zleap> https://www.mjmwired.net/kernel/Documentation/sysrq.txt
[18:00] <zleap> to figure out what i am doing with alt-sysrq,  as a few things are not enabled
[18:00] <zleap> i am guessing having 256 in there enables everything
[18:01] <penguin42> zleap: it takes a special value of '1' to enable everything
[18:01] <zleap> ah ok
[18:02] <zleap> right now it is 176  so 128+32+16 debugging dumps, sync reboot power off
[18:02] <zleap> so if I edit https://www.mjmwired.net/kernel/Documentation/sysrq.txt and use 1 is that safe / recommended
[18:08] <zleap> penguin42: got documentation printed off,  so some light reading for later :D
[18:09] <zleap> back shortly