[01:14] hey guys [01:14] I was getting a black screen at boot again today [01:14] after 3 attempts booting it finally worked [01:14] any ideas? [03:43] britt, next time it fails grab the gdm logs [03:48] where are the logs held? [03:48] /var/log/gdm [03:49] there are a lot of them in there? Is there any one in particular? [03:49] actually they appear to get rotated, so if you can find the one the corresponded to the black screen [03:49] start with :0.log.* (they are the X server logs) [03:50] grep "(EE)" * [03:52] i'm reading through them now trying to find any mention of the black screen [03:53] well you should be looking for just "error" and/or "(EE)" [03:54] I think I found the ones with the errors [03:55] yeah the one I am looking in has lots of errors reported, whereas the other log files do not [03:55] probably they will all have errors, so make sure they where from about the right time [03:56] they dont have time stamps though [03:56] the file does [03:57] yeah it's the right time [03:57] paste it [03:57] the whole file? [03:57] yeh, to pastebin or something [03:57] kk just a sec [03:59] http://pastebin.com/yA3e91WS [04:02] it took 3 attempts for me to get my computer to boot this last time, and the current log and the 3rd log and greater do not have any noticable errors [04:02] 1 and 2 are just about the same, and I believe each cooresponds to one of the failed attempts to boot, based on the time stamps [04:04] but it looks like that error is occuring on shutdown of the server [04:04] perhaps look in corresponding (via file timestamps) -greeter and -slave.logs [04:05] http://pastebin.com/WJZZZG9W this is one of the logs for a successfull boot. Look where it talks about "Allocate new frame buffer" [04:05] on the failed one it says (II) RADEON(0): Allocate new frame buffer 3840x1088 stride 3840 [04:05] (EE) RADEON(0): failed to set mode: Permission denied(EE) RADEON(0): failed to set mode: Permission denied(II) RADEON(0): VRAM usage limit set to 1864278K [04:05] the successfull one says: [04:05] (II) RADEON(0): Allocate new frame buffer 1920x1088 stride 1920 [04:05] (II) RADEON(0): VRAM usage limit set to 1872054K [04:07] on successfull boots it tries to allocated 1920x1088 stride 1920, on unsuccessfull it tries to allocate 3840x1088 stride 3840 [04:08] wait actually nevermind they both allocate the 2840x1088, however on successfull ones it does get the permission denied error [04:08] except this means something has told/caused the xserver to shutdown, (II) AIGLX: Suspending AIGLX clients for VT switch [04:08] 3840* [04:09] X server appears to be loading fine [04:10] it does. It shows the blue background for about 2 seconds. It then goes to a solid black screen about the time gdm would normally load [04:11] any errors in the :0-greeter.log and -slave.log [04:13] it looks like a lot of errors actually [04:14] http://pastebin.com/55RByh6x [04:16] that is definately an openGL issue, its trying to fallback to the old gtk2 greeter [04:17] it didn't do it until I upgrade to the staging ppa though... [04:17] no other files have changed [04:21] This is a greeter file from a successfull boot [04:21] http://pastebin.com/qSmAnYfu [04:25] its not even trying to load gnome-shell, due to this failure (gnome-session[2287]: WARNING: Session 'gdm-shell' runnable check failed: Timed ou [04:25] yeah on the successfull boots that line isn't there [04:26] which would make sense lol [04:26] on both boot failures it is there and on all successes it isn't [04:30] file a bug against gnome-session [04:30] what should I put in the report? [04:32] damn it wont let me use apport to report it [04:33] is there a manual way to file a bug via launchpad? [04:33] yeh just go to project page [04:33] https://bugs.launchpad.net/ubuntu/+source/gnome-session [04:34] attach that greeter log [04:34] and include the WARNING in the report [04:34] I have to run, will be back later [04:35] ok thanks for the help [04:41] https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1133120 here is the bug report for when you get back [04:41] Launchpad bug 1133120 in gnome-session (Ubuntu) "gnome-session failing to load dude to timeout error on random boots" [Undecided,New] [04:55] jbicha are you around? [05:10] jbicha, just out of interest have you test gdm fallback mode recently? [05:17] darkxst: no, it's harder to test now that we've enabled llvmpipe [05:17] jbicha, I think it might be broken [05:19] darkxst: I'm surprised they didn't remove it yet; it seems they tried to remove every bit of integration with the old fallback mode this cycle [05:21] I don't maintain a project but it seems that deprecating and removing all in the same short cycle is moving a bit too fast but anyway... [05:23] yeh well the fallback stuff ties into a lot of different packages [05:32] hmm it still works when I force the session [05:32] but is failing when britt 'fallsback' to it [05:33] does lightdm work in those cases? [05:34] jbicha, in my case it did, but I had a mesa bug that only affected clutter [05:34] don't know if it works for britt [05:35] because if it lightdm fails too, I blame his drivers [05:37] well it could be many things, but X is starting up fine according to the logs [07:54] ricotz: hey can I ask you a question about fglrx drivers in raring? [07:55] britt, #ubuntu-x is a better place to ask that ;) [07:55] hah yeah, but I specifically wanted to ask you a question ;-) [07:55] and I know you hang out around here [07:55] (and me too lol) [07:55] I can switch over though if that is better [07:56] britt, if you are asking about the xedgers packages, i am not using fglrx i am just updating those to give people a "safe" way to test/use them [17:23] darkxst: ok, I uploaded the gnome-shell/mutter sru, when you get a chance could you add the extra SRU description to bug 1067265 and bug 1132308 [17:23] bug 1067265 in gnome-shell (Ubuntu Quantal) "gnome-shell (3.6) notification bar disappears" [Medium,In progress] https://launchpad.net/bugs/1067265 [17:23] bug 1132308 in gnome-shell (Ubuntu Quantal) "~50px pointer barrier in gnome shell at bottom of primary monitor in raring" [Low,In progress] https://launchpad.net/bugs/1132308 [20:15] jbicha, thanks, updated those 2 [20:16] darkxst: thanks, also for SRUs they want the version number to use a decimal point so that it doesn't conflict with versions in the development release, i.e. 3.6.3-0ubuntu0.1 [20:19] ah right, I should have realised that! [20:26] anyone around? [20:31] yeh [20:42] darkxst: and I copied bits from the NEWS file since some people pick & choose stable updates based on the debian changelog [20:43] darkxst: sorry - what was the last message you got from me? [20:44] spacea, " anyone around?" [20:45] darkxst: i was about to intall gnome remix on my new PC. Is the development still going on? [20:46] spacea, yes, however no ISO's for raring version just yet [20:46] darkxst: would you have any idea what size of updates I am looking for a fresh install of gnome remix 12.10? [20:47] spacea, nope [20:48] darkxst: this might be a very stupid request but could you check via a VM if you have a fast connection? My connection takes 9-12 hours to download the iso [20:48] yay third world country internet [20:49] I have very fast internet, not sure how that will help you? [20:49] If its too big then I will have to go with something else unfortunately :( [20:49] I just need to know the update size after install [20:51] darkxst: Your help would be really appreciated [20:57] darkxst: should I wait around or is that too much to ask? :/ [21:05] spacea, can't check right now [21:05] all right sir [21:10] jbicha, nice work on the tech board email btw [21:19] jbicha: any idea when iso's for 13.04 will be out? [21:20] also I'm super happy to see that 13.04 will have libre office & firefox by default xD thank you!! :) [22:53] gonyere: if we're lucky we'll be official and we can get daily builds without too much work [22:53] otherwise, whenever someone gets around to building the 2 images and checking that they work and then we'll call it an alpha [22:54] robert_ancell: thanks, not much response yet, I'm guessing they'll have questions at Monday's tech board meeting though