[00:22] <tseliot> slangasek: sure, I'll do it tomorrow in the morning
[00:24] <slangasek> ok
[00:51] <superm1> jbarnes, pong
[02:45] <dhillon-v10> hi all, I am looking at some bugs in the xserver-xorg-video-intel section, and since I have similar drivers I can triage some bugs there, and set their importance, can anyone add me to the team so I can change the importance
[03:07] <bryyce> dhillon-v10, don't worry about setting the importance
[03:11] <dhillon-v10> bryyce, oh okay then :) that makes things easier for me
[03:15] <bryyce> dhillon-v10, help is always appreciated with the bug triaging.  I find I have a lot less time for doing it myself these days but it still needs done
[03:42] <dhillon-v10> bryyce, can you have a look at this: https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/498287 should I ask the user to test against the latest version (2.6.3)
[03:45] <bryyce> dhillon-v10, because a lot of functionality that used to be in xserver-xorg-video-intel has moved to the kernel, it is often not sufficient to just have them test a newer version of that package
[03:45] <dhillon-v10> bryyce, so what do you advice in this case
[03:45] <bryyce> I mean, it couldn't hurt, but it's not likely to give them a fix
[03:46] <dhillon-v10> bryyce, okay :)
[03:46] <bryyce> dhillon-v10, well, first the patches he mentions are already in ubuntu.  So if they didn't fix it for him, then it's something else
[03:47] <bryyce> second, often these bugs are not due to something in the intel driver but due to something elsewhere in the system (the kernel maybe, or gnome-power-manager)
[03:49] <dhillon-v10> bryyce, I think it could be the kernel, because like you said a lot of functionality moved into the kernel so a commit must have broken something
[03:49] <bryyce> it would be interesting to know if it is a regression, and if so, if they can identify which piece of software solves it if downgraded
[03:49] <bryyce> so like booting to an older kernel if they have any in /boot might be interesting.
[03:52] <dhillon-v10> bryyce, ahh it could be a regression introduced by a newer kernel nice :) 
[03:55] <dhillon-v10> bryyce, is this comment enough atm: This could be a regression caused by the kernel so can you try to boot into an older kernel (if you have one present on your system) and see if that solves your problem. Thanks.
[03:55] <bryyce> dhillon-v10, yes; if it does solve it then reassign to linux
[03:56] <dhillon-v10> bryyce, okay
[05:04] <hyperair> can someone help me debug an issue regarding my brightness keys?
[09:49] <BUGabundo_work> morning
[09:50] <bryyce> morning
[09:53] <BUGabundo_work> wb sebner 
[09:54] <BUGabundo_work> wb seb128 
[13:57] <hyperair> is there some kind of libgl breakage?
[13:58] <hyperair> http://pastebin.com/m789c79a6 <-- some guy with a 32-bit mesa-utils on a 64-bit comp
[13:59] <tseliot> hyperair: reinstalling xserver-xorg-core (or simply installing ubuntu5) should do it
[14:00] <tjaalton> ia32-libs isn't updated
[14:00] <tseliot> oh, I didn't read
[14:00] <tseliot> yes, that's broken anyway
[14:00] <hyperair> ah.
[14:00] <hyperair> i see
[14:01] <tseliot> it should be updated as tjaalton said and I should make sure that its libGL* libraries are put in /usr/lib32/mesa
[14:01] <hyperair> i think i provided a patch for that sometime back
[14:01] <hyperair> a very long time back.
[14:01] <tseliot> what kind of patch?
[14:02] <hyperair> one to the upstream, one as a debdiff
[14:02] <hyperair> the upstream went in, the debdiff...
[14:02] <hyperair> kinda died a natural death
[14:02] <tseliot> hyperair: ok but what did the patch do?
[14:03] <hyperair> changed a configure flag
[14:03] <hyperair> the upstream one added a configure flag that changed the DRI drivers' location
[14:03] <hyperair> the debdiff changed the configure flag so that it would install the DRI drivers' location to a place that could be symlinked to /usr/lib32/dri
[14:03] <hyperair> oh wait
[14:04] <hyperair> this is /usr/lib32/dri not /usr/lib32/mesa
[14:04] <hyperair> bug #248392
[14:05] <tseliot> right
[14:05] <tseliot> which is why I asked ;)
[14:05] <hyperair> heh
[14:05] <hyperair> wait, why are stuff being installed to /usr/lib32/mesa?
[14:05] <hyperair> not /usr/lib32?
[14:07] <tseliot> hyperair: because of the new alternatives system. Don't worry, ldconfig will know where to find those libraries
[14:07] <hyperair> ah
[14:07] <hyperair> i see
[14:07] <hyperair> not using rpath i suppose?
[14:08] <hyperair> i remember the ruling about rpath was dropped in one of the more recent debian policies
[14:08] <tseliot> yes, without rpath
[14:08] <jcristau> are you sure the 32bit ld.so can find stuff in /usr/lib32/mesa?
[14:08] <jcristau> when ld.so.conf only says usr/lib/mesa
[14:08] <tseliot> sure, it's patched to work with 32bit libraries
[14:09] <tseliot> jcristau: have a look at my changes to mesa (debian/rules)
[14:09] <jcristau> ok
[14:11] <siretart`> I noticed that with kms, a simple 'xrandr --query' now auto-enables the external monitor on my laptop. is this a known issue?
[14:12] <tseliot> hyperair: can you file a bug report about that, please?
[14:12] <tseliot> hyperair: feel free to assign it to me
[14:12] <hyperair> tseliot: what bug report?
[14:13] <tseliot> hyperair: about the fact that ia32-libs should install libGL* in /usr/lib32/mesa
[14:14] <hyperair> tseliot: i'm not on lucid and am not really sure what's going on at the moment really =\
[14:14] <tseliot> hyperair: ah, ok. Never mind
[14:14] <hyperair> sorry
[14:14] <tseliot> np
[15:06] <Sarvatt> anyone know whats up with libxcb? 2 sync requests closed a fixed for the 1.5 version but we're still at 1.4-1
[15:10] <tjaalton> it's on binary NEw queue
[15:10] <tjaalton> most likely
[15:14] <Sarvatt> thats what i thought because of the libxcb-dri2-0 but i never even saw it on https://edge.launchpad.net/ubuntu/lucid/+queue?queue_state=0&queue_text=
[15:14] <Sarvatt> not sure if thats even the place to look though
[15:28]  * BUGabundo_work waves to Sarvatt 
[16:41] <geser> Sarvatt: grab an archive admin and let him look why the sync fails
[17:32] <afv> hi
[17:32] <afv> i'm getting the message "program: error while loading shared libraries: libGLU.so.1: cannot open shared object file: No such file or directory" when trying to run some apps
[17:32] <afv> locate libGLU: /usr/lib/mesa/libGLU.so.1 and /usr/lib/mesa/libGLU.so.1.3.070700
[17:33] <afv> hmm.. should i symlink that do /usr/lib/libGLU.so.1?
[17:35] <tseliot> afv: please make sure that your system has the latest mesa package
[17:35] <afv> 7.7-0ubuntu4
[17:35] <afv> i'm not using the edgers ppa
[17:36] <tseliot> afv: maybe try to reinstall it and do sudo ldconfig
[17:37] <afv> nop.. :s
[17:38] <tseliot> ?
[17:38] <afv> same problem
[17:38] <afv> dpkg --get-selections | grep mesa: libgl1-mesa-dri, libgl1-mesa-glx, libglu1-mesa, mesa-utils
[17:38] <afv> do i need something else than this?
[17:39] <tseliot> what does this command say? ldconfig -p | grep GL
[17:39] <afv> http://pastebin.com/d773782b6
[17:44] <tseliot> afv: can you file a bug report about it and assign it to me, please?
[17:44] <tseliot> as a quick fix a link to /usr/lib/mesa/libGLU.so.1 in /usr/lib/ should work
[17:45] <tjaalton> yeah the libdir change should be reverted, and install libGLU in /usr/lib again
[17:45]  * tseliot nods
[17:45] <afv> thanks. report it here? https://launchpad.net/ubuntu/+source/mesa/+filebug
[17:46] <tjaalton> though it changes the pkgconfig files then, but I don't know if those are used anyway
[17:46] <tseliot> afv: yes, please
[17:46] <afv> ok. no problem
[17:46] <tseliot> tjaalton: I'll take care of that. After alpha 2, that is
[17:47] <tseliot> afv: BTW what program gave you that problem?
[17:48] <tseliot> (just curious)
[17:48] <afv> blender, mixxx, yofrankie-bge
[17:48] <tseliot> ok
[17:48] <tseliot> just to have some test case
[17:48] <tseliot> cases
[17:49] <tjaalton> tseliot: ok
[17:51] <BUGabundo_work> tseliot: is nvidia better today? can i upgrade, or should i still hold on on it ?
[17:52] <tseliot> BUGabundo_work: sure, it should be safe to upgrade. Note: after the upgrade (just to be safe) reinstall xserver-xorg-core
[17:52] <BUGabundo_work> ok
[17:52] <BUGabundo_work> thanks
[17:53] <tseliot> np
[17:54] <afv> tseliot, https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/506547
[17:55] <tseliot> afv: thanks a lot
[17:55] <afv> no problem. :)
[18:06] <Sarvatt> hmm those work fine here afv
[18:07] <Sarvatt> are you on amd64? using the nvidia blob maybe?
[18:07] <afv> using the nvidia blob
[18:07] <afv> 32bits
[18:08] <afv> they work fine after a ln -s /usr/lib/mesa/libGLU.so.1 /usr/lib
[18:08] <Sarvatt> i think it might be blob specific, not getting any errors on any of my machines not using the blob
[18:08] <tseliot> Sarvatt: that makes sense because the library is in the directory with the stuff installed by mesa
[18:09] <tseliot> but when you switch to nvidia
[18:09] <tseliot> ldconfig point to the directory with the nvidia libraries
[18:09] <afv> hmm.. what's your ls -l /usr/lib/libGLU.so.1 output?
[18:09] <tseliot> points
[18:09] <Sarvatt> ah yeah, so moving libGLU back would fix it there at least
[18:09] <tseliot> I doubt he has any
[18:09]  * tseliot nods
[18:10] <afv> maybe he has one that is there since an older update? :s
[18:11] <afv> i did an ubuntu fresh install yesterday (didn't fresh install since karmic alpha 2.. May last year :p) and maybe that's why i didn't have the file..
[18:11] <Sarvatt> btw we were going to add the drisearchpatch configure flag to mesa now that we're on 7.7 to fix ia32-libs? been fixing it in edgers for a few months now
[18:11] <Sarvatt>         --with-dri-searchpath=/usr/lib/dri:/usr/lib/dri/$(DEB_HOST_GNU_TYPE) \
[18:12] <Sarvatt> (adding that to confflags-dri after         --with-dri-driverdir=/usr/lib/dri \
[18:12] <jcristau> that would need a server change too?
[18:13] <tseliot> for bug #248392 ?
[18:14] <Sarvatt> yeah thats the bug, dont think it needs any server change
[18:16] <Sarvatt> http://old.nabble.com/-Bug-24766--New:-32-bit-libGL.so-searches-for-DRI-modules-in--usr-lib-dri-instead-of--usr-lib32-dri-td26082908.html
[18:17] <tseliot> ok, it seems a good candidate for alpha 3
[18:21] <tseliot> Sarvatt: with that configuration flag, do we still need the symlinks in ia32-libs?
[18:22] <tseliot> http://launchpadlibrarian.net/34815911/debdiff
[18:23] <jcristau> slangasek: so ia32-libs is still not going away? :(
[18:23] <Sarvatt> i dont think so.. hyperair?
[18:23] <tseliot> I guess it's either one way or the other
[18:23] <hyperair> Sarvatt: ?
[18:23] <tseliot> jcristau: how is it going away?
[18:24] <Sarvatt> are the symlinks needed in ia32-libs if we add this --with-dri-searchpath you added to mesa upstream?
[18:24] <hyperair> yes, they're needed.
[18:24] <hyperair> i think.
[18:24] <hyperair> well i could perhaps do --with-dri-searchpath=/usr/lib/dri:/usr/lib32/dri
[18:24] <jcristau> tseliot: how?  by someone removing it from the archive
[18:25] <tseliot> jcristau: interesting implementation ;)
[18:25] <hyperair> Sarvatt: coem to think of it maybe --with-dri-driverdir=/usr/lib32/dri might be the right solution?
[18:25] <tseliot> jcristau: I was asking what the alternative solution was
[18:25] <jcristau> tseliot: same as 5 years ago.  multiarch.
[18:26] <tseliot> jcristau: no doubt on that. Are we going to get that in dpkg?
[18:26] <jcristau> why do you ask me?
[18:26] <tjaalton> it's being worked on, but it was deferred to lucid+1
[18:26] <tseliot> aah, ok
[18:27] <hyperair> and when lucid+1 arrives, it'll be deferreed to lucid+2
[18:27] <tseliot> it's good to read that they're working on it :-)
[18:27] <tjaalton> mvo knows how hard it is to implement ;)
[18:27] <hyperair> and so on.
[18:27] <jcristau> it was deferred to etch+1 :)
[18:27] <tseliot> tjaalton: I bet he does ;)
[18:27] <jcristau> or was it sarge+1
[18:27] <tjaalton> jcristau: heh
[18:27] <tseliot> heh
[18:30] <Sarvatt> oops, need glproto 2.4.11 and dri2proto 2.2 already for mesa master now
[18:30] <hyperair> Sarvatt: ah right i just remembered. the symlinks are required, because the mesa things aren't rebuilt, and we needed some way to standardize the search path even for x64 builds.
[18:41] <tseliot> hyperair: good to know. I would like to fix this after alpha 2
[18:41]  * tseliot > dinner
[18:41] <hyperair> cool
[18:41] <Sarvatt> oh wow, moving the old 40-xserver-xorg-input-wacom.rules down below 65-xorg-evdev.rules was all that was needed to get it working? wasted all that time without knowing how things work and it was so simple :D
[18:41] <ripps> Okay, I think it's final. Plymouth was responsible from keeping my 2.6.32-10 kernel from booting
[18:42]  * hyperair will wait at least until then before upgrading
[18:42] <hyperair> plymouth?
[18:42] <jcristau> Sarvatt: i think it was all ron was missing for a while.  so he was (unknowingly) getting evdev and thought it didn't work quite well enough :)
[18:44] <ripps> I also know that something is wrong with the radeon drivers w/ dri1. Because my X keeps crashing when I try to boot with nomodeset. I can get into xterm and I can see through glxinfo that the right mesa glx is loaded, but once I try to boot into Gnome or Failsafe Gnome, black bars appear and suddenly X restarts.
[19:07] <Sarvatt> hmm [ 3999.496717] (II) intel(0): No memory allocations [ 3999.496901] (EE) intel(0): Couldn't create pixmap for fbcon [ 3074.601783] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id on the latest daily kernel after resume
[19:17] <Duke`> :/
[19:44] <tseliot> Sarvatt: maybe plymouth triggered that
[19:50] <tseliot> i.e. its drm plugin for intel
[20:26] <hyperair> we're using plymouth in lucid now?
[20:26] <BUGabundo> evening
[20:27] <BUGabundo> looks like nvidia aint still ready :(
[20:27] <BUGabundo> can't activate it via jokey
[20:27] <hyperair> nvidia's never ready before the release candidates anyway >_>
[20:27] <hyperair> those slowcoaches
[20:27]  * hyperair sighs
[20:27] <BUGabundo> $ pastebinit /var/log/jockey.log
[20:27] <BUGabundo> http://paste.ubuntu.com/355687/
[20:28] <hyperair> it probably wouldn't build
[20:29] <hyperair> speaking from past bad experiences with nvidia's driver, but then again mine's the 96xx legacy one
[20:29] <BUGabundo> I asked tseliot before coming home if it was fine
[20:29] <BUGabundo> he said so
[20:30]  * hyperair shrugs
[20:30] <hyperair> anyway, it looks like you'er missing the kernel module
[20:30] <hyperair> try poking dkms
[20:31] <BUGabundo> how?
[20:31] <hyperair> umm
[20:31] <hyperair> not sure..
[20:32] <hyperair> dpkg-reconfigure nvidia-<whichdriver>-kernel-source perhaps?
[20:32] <BUGabundo> lets try
[20:32] <BUGabundo> no such package
[20:33] <hyperair> huh
[20:33] <hyperair> you sure?
[20:33] <BUGabundo> $ sudo dpkg-reconfigure nvidia-
[20:33] <BUGabundo> nvidia-173-modaliases      nvidia-185-modaliases      nvidia-common              nvidia-current-modaliases  nvidia-settings
[20:33] <BUGabundo> nvidia-185-libvdpau        nvidia-96-modaliases       nvidia-current             nvidia-glx-185             
[20:33] <hyperair> oho weird.
[20:33] <BUGabundo> $ dpkg -l | grep nvidia | pastebinit  http://paste.ubuntu.com/355696/
[20:34] <hyperair> nvidia-glx-185 depends on nvidia-185-kernel-source
[20:34] <hyperair> er
[20:34] <BUGabundo> there's no such thing in my apt db
[20:34] <hyperair> you don't even have nvidia-glx-185.
[20:34] <hyperair> okay
[20:34] <hyperair> try installing nvidia-glx-185?
[20:34] <BUGabundo> lucid, right?
[20:34] <hyperair> er
[20:35] <hyperair> actually i haven't done this for ages so i don't even remember how the process is supposed to go
[20:35] <hyperair> maybe you should just wait until someone moer familiar turns up =D
[20:35] <BUGabundo> it changed a lot
[20:35] <hyperair> since karmic?
[20:35] <BUGabundo> yep
[20:36] <hyperair> =x
[20:46] <bjsnider> BUGabundo, from tseliot: Jockey is not ready yet (because of a broken dependency on kdebindings).
[20:46] <BUGabundo> BAH
[20:46] <BUGabundo> bjsnider: so what's the manual approch?
[20:48] <bjsnider> the command is in the rues file
[20:48] <bjsnider> i don't have access to it at the moment
[20:48] <bjsnider> everything but glx should be working though
[20:50] <bjsnider> bug 494166
[20:50] <bjsnider> there might be info in there about it
[21:51] <slangasek> jcristau: I don't have time to work on multiarch this cycle; braindmg said he was going to work on the deep structure changes needed in dpkg, but I haven't seen any movement there lately (and haven't had time to check either)
[21:52] <jcristau> ok :/
[23:53] <maxb> Does anyone know if there's a bug filed for the current X doesn't work at all on Intel GPU woes in lucid?
[23:55] <RAOF> I don't know one offhand.  Also, my Intel X works fine; I've clearly dodged the bad upgrade.