[02:07] <bryceh> sweet:  $ DIST=precise chet version fglrx-experimental-9
[02:07] <bryceh> fglrx-experimental-9  precise  2:9.010-0ubuntu0.1
[09:25] <mlankhorst> nice
[10:03] <mlankhorst> hm when using a version of unreleased debian experimental git, should I have something like 1.0.4-0ubuntu1 for version?
[10:04] <xclaesse> FYI, I reported my Xephyr issue since I did not have answers: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1079096
[10:06] <mlankhorst> xclaesse: there's a upstream bug report for it afaict
[10:06] <xclaesse> it works on f17
[10:07] <xclaesse> not sure which version they have
[10:08] <mlankhorst> great fd.org is having issues all of a sudden
[10:08] <mlankhorst> https://bugs.freedesktop.org/show_bug.cgi?id=54798 probably
[10:09] <mlankhorst> xclaesse: if you want can you test if that patch works so we can include it in the xserver sru?
[10:09] <maxb> mlankhorst: I believe that -0ubuntu1 is correct in that circumstance, yes
[10:10] <xclaesse> mlankhorst, thanks, I'll try the patch and let you know :)
[10:19] <xclaesse> mlankhorst, hm, I've fetched the code with apt-get source xserver-xephyr, then ./autogen.sh --enable-xephyr && make
[10:20] <xclaesse> but I don't see any Xephyr binary
[10:21] <xclaesse> mlankhorst, I applied the patch with patch -p1 < foo.patch, if I do "debuild" will it include the patch in the build?
[10:21] <mlankhorst> yeah
[10:22] <xclaesse> ok, let's see if that works :)
[10:24] <mlankhorst> So uploading to ubuntu is just dput ubuntu.. how anticlimactic
[10:30] <xclaesse> mlankhorst, ok I've installed the new xephyr with sudo dpkg -i ../xserver-xephyr_1.13.0-0ubuntu6_amd64.deb
[10:31] <xclaesse> but still same problem :(
[10:40] <mlankhorst> what if you also add [PATCH] Xephyr: GLX: Support MakeContextCurrent and MakeCurrentReadSGI (on ml) ?
[10:41] <xclaesse> mlankhorst, which ML? I'm no X dev :/
[10:43] <jcristau> xorg-devel
[10:43] <mlankhorst> also an upstream commit it seems
[10:44] <xclaesse> link?
[10:44] <mlankhorst> 11afebc92ce1a7462ff2886286504425b1c8f0ba
[10:47] <xclaesse> ok, compiling
[10:56] <xclaesse> mlankhorst, doesn't change anything :(
[10:56] <xclaesse> mlankhorst, from commit msg they seems to fix virtualbox, but here I'm not using a VM
[10:57] <mlankhorst> it's probably something similar though :/
[10:58] <mlankhorst> what drivers do you use?
[10:59] <xclaesse> intel
[11:03] <mlankhorst> needs some more digging then :/
[11:03] <xclaesse> mlankhorst, btw seb128 has the same issue, so it's not just me. can't you reproduce?
[11:04] <xclaesse> mlankhorst, I'm here if you need info/tests, but tbh I'm not X dev so I cannot tell much :/
[11:04]  * xclaesse just wants to run gnome-shell in xephyr
[11:04] <mlankhorst> want to  become a x dev? :P
[11:05] <xclaesse> not really, thanks :)
[11:05] <xclaesse> can't wait for wayland to replace that aging x server :)
[11:06] <mlankhorst> saying as if age is a bad thing
[11:06] <xclaesse> hehe, fair enough :)
[11:06] <jcristau> you're a wayland dev?
[11:07] <xclaesse> no at all :)
[11:07] <xclaesse> I'm telepathy dev
[11:08] <xclaesse> IM stuff, and gtk/clutter :)
[11:28] <mlankhorst> ugh no idea what xephyr is doing there
[11:31] <jcristau> no glxinfo from the host x on that bug?
[11:36] <mlankhorst> jcristau: argh seems I didn't get log info because server was compiled with disable-debug >:(
[12:06] <mlankhorst> xclaesse: (!!) in ../../../../hw/kdrive/ephyr/ephyr.c:662:ephyrInitScreen: (!!) host x does not support DRI. Disabling DRI forwarding
[12:06] <mlankhorst> :/
[12:08] <mlankhorst> xclaesse: does fedora have a patch to enable dri2 on xephyr, by any chance?
[12:14] <mlankhorst> hm doesn't look like it
[12:42] <xclaesse> mlankhorst, I've no idea... it works on debian as well
[12:42]  * xclaesse should maybe try to install the debian package and see what happens
[12:45] <mlankhorst> yeah fails on x1.13 though
[12:45] <mlankhorst> does the one from precise work on quantal?
[13:00] <xclaesse> mlankhorst, it works !
[13:00] <xclaesse> awesome, that's a good enough solution for my needs
[13:00] <xclaesse> mlankhorst, thanks :)
[13:05] <mlankhorst> blegh it regressed then, don't suppose you want to run a regression test?
[13:09] <mlankhorst> could try if the one from 1.12 works first, debian should have a version there
[13:36] <xclaesse> mlankhorst, FYI, on debian SID  they have xephyr 2:1.12.4-3 and it has glx as well (with llvmpipe it seems)
[13:43] <mlankhorst> yeah probably broken something on 1.13 then :/
[13:50] <mlankhorst> you probably want to file an upstream bug for it on bugs.freedesktop.org, maybe someone looks at it
[19:53] <bryceh> RAOF, when you get in, there's a bunch of nvidia and fglrx packages waiting on SRU review.
[19:54] <bryceh> RAOF, there's still an nvidia -310 driver in NEW for precise-proposed, I don't think we ever figured out why that is still in new
[19:54] <bryceh> RAOF, fglrx-installer-experimental-9 is also in NEW still, although I thought you'd given it a bump the other day?
[19:55] <bryceh> RAOF, in unapproved there is an -updates 304.64, and a couple fglrx -updates as well as jockey
[20:14] <tjaalton> why do the experimental packages have the version number appended?
[20:23] <bjsnider> well, obviously there are going to be more than one type of experimental package
[20:28] <bryceh> tjaalton, right, for nvidia there are going to be multiple lineages in parallel.  If a user installs 310.04 that's going to be unstable, but as it progresses 310.14 up to 310.42 it will become more stable with time.  If we were to automatically bump him to some new experimental driver -342, we'd regress them in stability without their permission
[20:28] <bryceh> for fglrx their numbering system doesn't lend itself to this same scheme, so we're just having one -9 package that's just going to be a grab bag of periodic instability.
[20:30] <bryceh> but who still uses fglrx anyway?  ;-)
[20:33] <tjaalton> bryceh: ok, thanks
[20:33]  * bryceh sends out steam keys
[20:34] <bjsnider> lots of people use fglrx
[20:36] <bryceh> bjsnider, guess we'll find out how many, soon.
[20:36] <tjaalton> i should probably create an account there...
[20:36] <bcurtiswx> ooh steam keys :)
[20:36] <ajmitch> bryceh: you'll have a lot of thankful people for sending keys 
[20:36] <bryceh> btw I set up #ubuntu-steam for folks that might need advice
[20:36] <bjsnider> lots of users were asking about it/complaining about it in +1 before quantal was released
[20:37] <bryceh> bjsnider, of course you know I joke.  But I do think the userbase is trending downward with that driver.
[20:38] <bjsnider> not fast enough. faster, please
[20:38] <bryceh> bjsnider, amd's working on it
[20:38] <jcristau> bryceh: because people use radeon, or because they don't buy amd? :)
[20:38] <bjsnider> ideally the latter
[20:39] <bryceh> jcristau, bit of both I suspect.
[20:39] <bjsnider> it's a decent graphics card for windows though
[20:39] <bryceh> for my (non-gaming) purposes I find the foss driver works fine and seems less buggy compared with fglrx
[20:40] <jcristau> bryceh: ack
[20:40] <ajmitch> for gaming, my last experience of radeon was that it wasn't in the same ballpark
[20:42] <bryceh> I expect for laptops fglrx would be preferred due to better power management
[20:43] <bcurtiswx> laptops for gaming in general is a bad idea
[20:44]  * ajmitch was trying to game on a laptop
[20:44] <ajmitch> it was cooking
[20:44] <bjsnider> are they still infiltrating their way into laptops as a discrete chip?
[20:44] <bcurtiswx> yeah, great heat source.. helps with those winter heating bills ;)
[20:45]  * ajmitch now has a decent desktop & using the nvidia 310.14 driver from quantal-proposed
[20:49] <bcurtiswx> bryceh, confirmed receipt of key :)
[21:55] <mlankhorst> so many double frees inside steam client, it's scary
[21:59] <mlankhorst> then valgrind gave up altogether, ah well
[23:22] <RAOF> bryceh: Pushed nvidia, fglrx out of binary NEW.
[23:23] <bryceh> RAOF, \o/
[23:23] <RAOF> (Had previously pushed them through source NEW)
[23:25] <bryceh> ahh
[23:27] <fagan> Hey all, I have a weird issue on 12.10 installing any of the nvidia drivers, after the reboot the screen is completely off. Like I can only see 1/3 of the desktop. I was using the 310 driver but reinstalled so I know it should work fine. 
[23:28] <bryceh> fagan, weird
[23:28] <fagan> bryceh: yeah thats exactly what I was thinking 
[23:29] <fagan> :)
[23:29] <bryceh> fagan, :-)
[23:30] <bryceh> fagan, no idea offhand; I've not seen that when running 310 myself, but imperfections in the video driver are certainly not unknown
[23:31] <fagan_> firefox crashed :D Is there anything I can do to try get it working?
[23:32] <fagan_> I tried each of the drivers and they all had the same problem. I upgraded the other time so I didn't install from scratch so that might explain why it was working before
[23:32] <bryceh> fagan, dunno, but if you figure out what the problem is let me know so we can investigate getting a fix in for it.  I'd probably first go through the usual troubleshooting techniques for nvidia bugs.
[23:32] <fagan_> Ill have a poke around 
[23:34] <fagan> Here is what the install looks like http://paste.ubuntu.com/1361508/ nothing seems a miss there 
[23:37] <fagan> brb
[23:42] <Sarvatt> fagan: sudo apt-get install linux-headers-3.5.0-18-generic linux-headers-3.5.0-18
[23:55] <bjsnider> linux-headers-generic should be good enough
[23:58] <fagan> Ok so that didn't work still, hmmmmmmm ill try install 304.64 bryceh does the steam beta work with 304.64 or will it complain about not having 310?
[23:59] <fagan> (I want to check if its just a problem with installing through the package manager over the driver themselves not doing something correctly)