=== jalcine is now known as JackyAlcine === JackyAlcine is now known as jalcine === jalcine is now known as JackyAlcine [11:06] if Xorg crashes without giving you any error messages on screen and takes you back to the login screen, how/where can I look to understand why is this happening? I suppose a bug on the nvidia driver (bug already reported) but I'd like to understand better... [11:36] crashed again :\ [12:26] * jussi waves to Andy80 [12:30] jussi: hi :D [12:30] Andy80: long time no speak :) [12:32] jussi: yeah, how are you? Are we catching up at UDS? [12:32] Andy80: no, not this time :( [12:33] Andy80: busy busy busy with my 3 month old daughter [12:34] anyways, Im off to get candy from the shop... :P [12:34] ;) [12:35] I'm here busy with a Xorg that keep crashing and I don't know how to detect why :( damn it! [17:42] jussi: a bit young for candy isn't she? [17:45] mhall119: my wife? no :P === Guest94473 is now known as JackyAlcine [21:06] Hey, Im having a problem with LightDM acting up on boot. [21:06] When I boot up, LightDM doesnt start. Running LightDM restart lets me launch gnome. [21:06] Any guesses as to why LightDM fails on boot, but without changing anything, a restart fixes it? Im assuming its reading from some other config when being run by me than when being run on boot? Would that make sense? [21:11] bronzdragon: does lightdm start and fail or does it not start at all? [21:13] Im not quite sure. It says in the output it starts [21:13] in what output? [21:14] But its not followed up by any graphics or a message saying it stops. While every other DM starts and stop [21:14] Boot output [21:15] eh, if this is Ubuntu, normally there should be no "boot output" AFAIK? [21:16] Yes, that is correct. I dont get the usual boot messages, but since something fails, I get more messa-- oh wiat, thats the Xorg output I believe, rather than boot messages. Its the first text I see on screen after a boot. [21:16] bronzdragon: are you sure it doesn't start? have you check /var/log/lightdm/ for logs? [21:17] anyway, if it says it starts, it probably at least tries to start, so it's not a problem with the upstart job [21:17] Like I said, it says it starts, but I cant see anything. And it doesnt compalin when I restart it, so I assume it is running. But Ill look at lightdm logs now. Should I pastebin them? [21:19] bronzdragon: did you try switching to other virtual consoles with Alt+Fn? [21:19] Yes, that works. Thats where I run lightdm restart, to have it restart and then work perfectly [21:19] but did you try finding LightDM on one of them? [21:20] http://pastebin.com/gqb8p9Sr [21:20] Could you rephrase that? [21:20] Are you asking if its running anywhere but 7? [21:21] or you didn't get switched to 7 [21:21] bronzdragon: this one isn't really helpful, specially given that you've restarted lightdm so it's a log of a working session [21:21] bronzdragon: check x*log for errors [21:21] When I restart, I get switched to 7 which is where it restarts. [21:21] Right, yes [21:22] Which one of them? There is x0/greeter and x1/greeter [21:22] seems like there is an *.old log too? [21:23] yeah, check their timestamps [21:23] No .olds [21:24] Do you wanna see the earlist? [21:24] bronzdragon: the earliest from this session? [21:25] on my machine some of those logs go back to november ;) [21:25] They all have the same time stamp. But Ill assume the ls -l orders them by seconds too, even though it only tells me minutes. [21:25] kklimonda: I just removed one huge one from November actually ;) [21:25] Oh wait nvm, its ordered by name. Im being silly [21:26] -rw------- 1 root root 5338 2012-04-20 17:56 lightdm.log [21:26] -rw------- 1 root root 7585 2012-04-20 17:56 x-0-greeter.log [21:26] -rw------- 1 root root 1034 2012-04-20 17:56 x-0.log [21:26] -rw------- 1 root root 10480 2012-04-15 22:22 x-1-greeter.log [21:26] -rw------- 1 root root 1061 2012-04-15 22:36 x-1.log [21:27] bronzdragon: paste x-0.log [21:27] `sir! [21:27] * kklimonda is surprised there are no .log.old files [21:27] in pastebin! ☺ [21:27] http://pastebin.com/ncmtjTE7 [21:27] Sorry, figured 5 lines would be fine in here. [21:28] heh, there is nothing there [21:28] bronzdragon: can you reboot, wait for lightdm to fail to start and copy the content of /var/log/lightdm/ somewhere safe? [21:29] Oh yeah, sure. Gimme a minute then. [21:47] Hello again! [21:47] Sorry about taking forever [21:47] I was dumb. Twice [21:48] Archive or pastebins? [21:48] pastebins should be faster [21:48] http://pastebin.com/FfquUgCt [21:49] Lightdm.log [21:49] Oh this one has a bunch of errors! Nice [21:49] http://pastebin.com/vwNuPTPE [21:50] This is 0-greeter. Are the rest of any interest? http://pastebin.com/3kE8s5gn [21:53] bronzdragon: bug 873495 [21:53] Launchpad bug 873495 in lightdm (Ubuntu) "LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed" [Medium,Triaged] https://launchpad.net/bugs/873495 [21:53] bronzdragon: are you running 11.10 or 12.04? [21:53] Whats the command for finding out? [21:53] lsb_release -a [21:54] 11.10 [21:55] bronzdragon: ok, can you test kernel from https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/873495/comments/17 and report back (to the bug report, not here) if it's fixed the issue? [21:55] Ubuntu bug 873495 in lightdm (Ubuntu) "LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed" [Medium,Triaged] [21:55] well, you can also say here, but bug report is more important :) [21:56] Thats the only suggested fix? [21:56] bronzdragon: well, one of the comments suggests that it's a kernel issue [21:56] the patches look.. unrelated, at least their names [21:57] His fix points at the newer kernel version than what Ubuntu has [21:57] bronzdragon: the work around is for lightdm to wait few seconds before starting [21:57] Is that a problem? [21:57] the problem is a race condition between nvidia module creating /dev/nvidiactl and lightdm starting [21:58] I see. That makes sense. Since restarting LightDM magically fixes it [21:58] the workaround is to delay starting lightdm in hope that by doing this we give nvidia enough time to create the file [21:58] How do I make it stall? [21:59] edit /etc/init/lightdm.conf [21:59] add [21:59] pre-start script [21:59] sleep 2 [21:59] Thank you] [21:59] end script [21:59] but testing the kernel would make it possible to fix the actual bug ;) [22:00] Does it matter where it goes? If so, where? [22:01] Before "start on"? [22:01] before script [22:01] after emits [22:02] Thank you again. Ill try this. Also try with the patched kernel and see if that helps [22:02] dont forget revert changes before testing the kernel [22:03] Im not gonna do it natively. Gonna try in a VM. [22:03] it's not going to happen in VM [22:03] the problem is nvidia driver [22:03] Gonna use this exact compu-- oh right yes [22:03] in VM your gpu is virtualized and it won't be using the same nvidia module [22:03] Gonna try it natively then... =P [22:03] Ill remove the line before testing [22:04] you can easily switch between kernels at the boot time [22:04] by pressing left shift [22:04] Yup, thanks [22:04] well see you around [22:17] heh, nvidia binary v [22:18] heh, nvidia binary blob starts too slow? ;) === jalcine is now known as Guest58583