[00:03] <phenom> GridCube, I can't seem to find the option in the user config
[00:03] <phenom> I created a lightdm config file however I've been unsuccessful so far.
[00:03] <GridCube> phenom, clic to change the password, you will see a box at the bottom that says something like "don't ask password at login"
[00:04] <phenom> GridCube, Right, I want it to automatically log in, forgoing  any user interaction
[00:04] <GridCube> yes
[00:04] <phenom> I've selected that as my alternative
[00:04] <phenom> However I want it to go from boot to desktop on its own.
[00:04] <GridCube> you can also edit /etc/lightdm/lightdm.conf
[00:05] <GridCube> yes
[00:06] <GridCube> add this lines: autologin-user=phenom  autologin-user-timeout=0
[00:06] <phenom> I did :)
[00:06] <phenom> wait
[00:07] <phenom> I think I messed up
[00:07] <phenom> let me check
[00:29] <phenom> GridCube, I created the file in the wrong directory. I just tried what you posted and then it hung. I had to drop in recovery mode and mount the FS to delete the file. doah.
[00:29] <GridCube> the file already exists
[00:29] <GridCube> you don't ahve to create anything
[00:30] <GridCube> also they are two lines
[00:30] <GridCube> autologin-user=phenom
[00:30] <phenom> Didn't on mine. :/ Doesn't now Lol I rm'd it
[00:30] <GridCube> autologin-user-timeout=0
[00:30] <phenom> Right I got that.
[00:30] <GridCube> and an empty line after that
[00:31] <GridCube> you can only edit the file if you sudo
[00:32] <phenom> within /etc/lightdm/ I have 2 .conf files. lightdm-gtk-greeter.conf and users.conf
[00:32] <GridCube> mmm
[00:33] <phenom> I'm pretty sure I created and deleted the lightdm.conf
[00:33] <GridCube> those are directories
[00:33] <phenom> There is one directory lightdm.conf.d
[00:34] <GridCube> ok create a file lightdm.conf
[00:35] <GridCube> and into it add this: http://pastebin.com/raw/uH6BQr8a
[00:37] <phenom> done
[00:37] <GridCube> reboot
[00:37] <phenom> 10-4 brb
[00:42] <GridCube> :) did it work phenom?
[00:43] <phenom> GridCube, Now that worked!
[00:43] <GridCube> :D
[00:43] <GridCube> wooo!
[00:43] <phenom> GridCube, Many thanks my friend.
[00:43] <GridCube> de nada :D
[15:23] <p00l3> Hello. Is there any solution for fixing crashing thunar after copy-paste action? Found few bug descriptions but latest upates not fixed it yet.
[15:52] <flocculant> p00l3: no solution, no fix
[15:53] <p00l3> aww
[15:57] <p00l3> So what filemanager you recommend?
[16:03] <flocculant> well I've got a whole bunch installed here for testing purposes
[16:04] <flocculant> pcmanfm seems to be the one which works more or less ootb - others need things for some options like open terminal here
[16:22] <Spass> But does it mean Thunar is no longer under active development?
[16:27] <flocculant> Spass: I can't comment - not someone working on Xfce - but not much is happening currently seemingly
[16:27] <flocculant> we're looking at options for us
[16:41] <Spass> I really hope it's just a temporary hiccup and we will see an update soon. I really like Thunar.
[16:41] <Spass> soon = sooner or later
[18:15] <Grumps1944> Help please. I have just attemped to upgrade a laptop from 14.04 to 16.04. The upgrade ran OK and the last time I checked it was installing packages. Next time I checked the machine had powered down. Now it will not boot. In recovery mode it will boot to the login prompt. I  am strickly non tech. Can any one advise.
[18:25] <morf_> Grumps1944: boot to the recovery mode, try "continue running" or something like that you may see some errors ... then if you don't do that again, but select "root console" (or something) and try to check logs from previous boot (/var/log/syslog) look for errors (grep -i error /var/log/syslog)
[18:26] <morf_> ale it's possible boot live cd + check the logs from it
[18:26] <morf_> (boot live cd, mount the disk with broken install and check)
[18:26] <morf_> ale/also
[18:27] <morf_> in worst case i think you can install into the / partition the new ubuntu or reinstall/upgrade from live cd/usb (obivously don't format disk or you will loose the data)
[18:27] <morf_> hope it helps somehow
[18:27] <flocculant> before I tried continue running from recovery - I'd try the dpkg fix option there
[18:28] <morf_> yeah
[18:29] <morf_> honestly i have data on the side, simply install clean os the rest have automated so no biggie
[18:31] <flocculant> Grumps1944: http://i.imgur.com/x0mkgvf.png
[18:32] <flocculant> Grumps1944: during the upgrade - it should have asked you more stuff - so if all you saw was downloads I'd wonder what the last thing it did was
[18:52] <Grumps1944> I've got 16.04 on a usb so can see the syslog. There are plenty of errors. The last one being cannot findSQASHFS superblock on sda3
[18:52] <Grumps1944> Can I reinstall 16.04 without deletimg the user data.
[19:09] <flocculant> Grumps1944: not get anywhere resuming the upgrade from the recovery menu?
[19:10] <flocculant> you can reinstall and not lose /home files - but not sure what you mean by user data
[19:10] <flocculant> though I've not ever done so
[19:11] <flocculant> you'd be better booting the live session - then backup the data to another usb
[19:11] <flocculant> if you mean stuff other than what you might have in your home files, not so sure
[19:19] <Grumps1944>  How do I get to run the recovery menu. When I login as the user in recovery mode I just get the shell prompt. Is there a command to run the recovery menu.
[19:24] <flocculant> Grumps1944: reboot - while booting - press and hold shift key, when you have the grub menu - choose recovery from advanced options
[19:24] <flocculant> then once it's booted to the recovery menu try the dpkg option
[19:25] <flocculant> that said you appear to have issues "cannot findSQASHFS superblock on sda3"
[19:25] <flocculant> could try fsck from that menu too
[19:26] <flocculant> I would seriously suggest booting to the livesession - and getting yourself a backup onto another usb
[19:27] <flocculant> recovery menu looks like this http://i.imgur.com/fF7q6vc.png
[19:30] <Grumps1944> The problem is that when I select recovery from advanced option I do not get the recovery menu. The system loads up to a login prompt, not the menu.
[20:11] <Grumps1944> Signing off now. Thanks for your suggestions.