[03:36] so did anybody upgrade successfully from 12.04 to 14.04 recently? [03:37] yep [03:37] well, maybe a couple of months ago on my laptop [03:37] ajmitch_: and you didn't run into anything major? [03:38] only issue I really had was the apache2 configs [03:38] it seemed to work out alright [03:38] the only thing was I switched back to the free radeon driver before upgrading, iirc [03:39] ibeardslee: yeah, i saw that upgrading from wheezy to jessie as well [03:39] since I knew fglrx wouldn't support it in 14.04 & the free driver is much better now [03:39] my experience upgrading to 14.04 was truly miserable though [03:39] i can no longer log into unity/gnome-shell/xfce :( [03:39] does X start at all? [03:40] and i can't figure out where it's going wrong [03:40] ajmitch_: yeah, X works fine. if i use kdm, i can get a gnome-terminal using the failsafe mode and then start gnome-shell from there [03:40] no weird permissions in $HOME ? [03:41] however, if i log into a xfce/unity/gnome session directly, it accepts my password, blanks the screen, then goes right back to lightdm/gdm/kdm [03:41] i tried creating a new user and it does the same thing [03:41] ~/.xsession-errors would usually help, I remember I'd have issues like that when the disk was full [03:41] it's a truly frustrating bug [03:42] but I doubt the upgrade would have completed if that was the case [03:42] yeah, my .xession-errors is bitching about an error in /usr/bin/lightdm-something but it's not exactly verbose [03:43] it's also bitching about xmodmap not being able to find a file [03:43] i'm wondering what actually gets run when lightdm starts a gnome or unity session [03:43] pastebin it [03:44] ajmitch_: the error? [03:44] yeah, if you can [03:45] someone might have a clue :) [03:45] i don't have that computer with me here and the upgrade apparently also broke fwknopd :( [03:45] ah [03:45] though that's not surprising as it went from 1.x to 2.x, i probably need to redo its config [04:19] hmm that sounds like a problem I'd seen with the .Xauthority file .. somehow root owned it, and the user couldn't write to it. [04:24] ibeardslee: yeah, hence me asking about weird permissions [04:26] ahh, yeah. for some reason it was the only file that was 'mangled' [04:29] I couldn't remember which of the files it would have been [04:36] ibeardslee: that (or a stray .xsession) is what i suspected, but create a brand new user account didn't help [04:37] i wonder what's different between a kdm failsafe session and a normal one [08:26] is trusty still using upstart or has it moved to systemd already? [08:28] it looks like my session problems are due to the PATH not being set properly [08:29] the error from ~/.xsession-errors: /usr/sbin/lightdm-session: 5: exec: init: not found [08:29] with the full command line being: exec init --user [08:30] where "init --user" is set by /etc/X11/Xsession.d/99upstart (which assumes that /sbin/ is in the path) [09:12] fmarier: I think it's still using upstart [09:12] no trusty boxes handy to be atm I don't think [09:13] oh wait, I updated this box... [09:15] I appear to have a mix of upstart and systemd on this box :S PID 1 is /sbin/init provided by 'upstart' (dpkg -S /sbin/init) though [09:16] yeah, there are bits of systemd in 14.04, but apparently the full switch is scheduled for 16.04 (according to the interwebs at least) [09:17] 2016(!) oh I bet Lennout(sp?) is laughing at that :P [09:18] (I just happen to remember the way SystemD was pushed as the best next thing in Fedora/etc) [20:09] morning [20:11] morning [20:19] morena [20:35] morning