[00:01] <bryceh> Sarvatt, btw I did another test of installing fglrx with usb keys, after backing off the amount of persistent storage space by 800M.  Still got an error trying to activate the proprietary driver.  Gonna try again with only a 1G persistent partition, which should leave >2G for system files.
[00:02] <Sarvatt> bryceh: it's uninstallable in general because of the second part of that bug, no vmlinuz symlink on the liveusb
[00:02] <bryceh> Sarvatt, ah right
[00:03] <bryceh> bug #557023
[00:03] <Sarvatt> install it via apt-get and you'll see the error about the missing or broken vmlinuz instead of the lzma encoder error when you do have the free space
[00:03] <ubot4> Launchpad bug 557023 in usb-creator (Ubuntu Natty) (and 3 other projects) "update-initramfs: deferring update (trigger activated) / cp: cannot stat `/vmlinuz': No such file or directory (affects: 204) (dups: 159) (heat: 1372)" [High,Triaged] https://launchpad.net/bugs/557023
[00:03]  * Sarvatt pokes the bot
[00:04] <Sarvatt> wooo thats a lot of dupes for a non intel bug!
[00:04] <bryceh> hehe
[00:04] <Sarvatt> oh heck, I completely forgot about the intel SRU!
[00:05] <bryceh> alright let me re-do the bug from scratch with the /vmlinuz symlink manually created.
[00:06] <bryceh> I'm gonna get this class of bug definitively off our plate
[00:06] <bryceh> (if I were less lazy I'd code up a fix it myself)
[00:11] <Sarvatt> bryceh: going to be around tomorrow or are you headed off on vacation too? :)
[00:12] <bryceh> I'm not going on vacation.  I think I might be getting sick though so may or may not be around
[00:12] <bryceh> my son's been sick the past few days and now my wife has it, and I can't imagine that I'll escape unscathed
[00:13] <Sarvatt> yeesh everyone with kids is getting it right now! :)
[00:17] <bryceh> everyone else will get it at the sprint
[00:22] <bryceh> hmm, fglrx successfully installed... but now usb drive no longer boots.  wtf.
[00:23] <bryceh> here we go
[00:24] <bryceh> weird, had to specifically select usb in bios this time
[00:42] <bryceh> ...and it went back to -ati instead of -fglrx.  hrmph
[00:43] <Sarvatt> you installed it with jockey right? update-alternative --list gl_conf?
[00:43] <Sarvatt> update-alternatives rather
[00:45] <Sarvatt> dont get an xorg.conf outside of jockey and I just mentioned doing it via apt-get to see the error is why I ask :)
[00:45] <ScottK> Sarvatt: Please let me know if you need sponsorship/testing for the Intel SRU.
[00:48] <bryceh> yeah, used jockey to install
[00:49] <bryceh>  update-alternative --list gl_conf
[00:49] <bryceh>  /usr/lib/mesa/ld.so.conf
[00:50] <Sarvatt> ScottK: it's going to take an hour or two to review the dupes, get the SRU justification info into the bug and get it packaged properly for -proposed, can I bother you for help with it tomorrow? been trying to get off the PC for 2 hours now
[00:50] <ScottK> Sarvatt: Sure.  I'll be around.
[00:50] <bryceh> fwiw, I'm using an alpha-1 image here
[00:50] <Sarvatt> ScottK: thanks a ton for that!
[00:50] <bryceh> hmm this is also weird
[00:51] <bryceh> did an upgrade via Update Manager
[00:51] <Sarvatt> bryceh: hmm, thats VERY odd
[00:51] <bryceh> failed...  sudo dpkg --config -a shows this error:
[00:51] <ScottK> Sarvatt: Purely selfish.  I live with a teenager who looks at me with sad eyes and asks for a Mac every time her X crashes.
[00:51] <bryceh> dpkg: failed to write status database record blah blah to '/var/lib/dpkg/status': no space on device
[00:52] <bryceh> df -h /var/lib/dpkg/ shows it as 'aufs  1006M' with Use%='-', mounted on /
[00:52] <Sarvatt> ScottK: oh she's getting this bug? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/626967
[00:52] <ubot4> Launchpad bug 626967 in xserver-xorg-video-intel (Ubuntu Natty) (and 2 other projects) "MASTER: Hang in MI_WAIT_FOR_EVENT on framebuffer switch. (affects: 30) (dups: 41) (heat: 320)" [Medium,Fix released]
[00:53] <Sarvatt> I thought she was getting the logout problem
[00:56] <ScottK> Yes.
[00:57] <ScottK> We're getting both Bug #651294 and Bug #660152
[00:57] <ubot4> Launchpad bug 651294 in xorg-server (Ubuntu) (and 1 other project) "X crash on KDM logout (still - yes, really) (affects: 22) (dups: 4) (heat: 118)" [High,Confirmed] https://launchpad.net/bugs/651294
[00:57] <ubot4> Launchpad bug 660152 in xserver-xorg-video-intel (Ubuntu Maverick) (and 1 other project) "The computer logged me out without my permission. (affects: 5) (heat: 73)" [High,New] https://launchpad.net/bugs/660152
[00:57] <ScottK> The first one at least has a workaround.
[00:57] <ScottK> Someone said something about a patch that might help.
[00:58] <Sarvatt> ahh that's a different bug
[00:59] <ScottK> OK.  Can we knock them together into one SRU?
[00:59] <ScottK> That's the one I thought you were doing.
[00:59] <Sarvatt> ScottK: awesome, that patch referenced does indeed look like it'll fix that problem
[01:00] <ScottK> Sarvatt: Right, so if you could include that, I'd be super motivated to help.
[01:00] <Sarvatt> bryceh: what's the status of xorg-server in maverick? did you have a SRU queued?
[01:01] <bryceh> Sarvatt, yep, posted it yesterday, but it's blocked by another sru that's been stuck in the queue since november
[01:01] <Sarvatt> ahh darn, ScottK's bug needs a fix in the server too
[01:02] <ScottK> bryceh: Maybe we should have that one rejected, do just this one and then reupload the other one.
[01:02] <ScottK> The logout one should be very easy to quickly verify
[01:17] <bryceh> alright, I'm officially done with #685017.  I can't figure it out, seems something peculiar with the filesystems.  I've documented as much as I sorted out, and I'm 95% certain it's not the driver's fault.  Someone else will need to figure it out from there.
[01:20] <bryceh> so things will probably improve a smidge once timo comes on
[01:21] <Sarvatt> bryceh: I'm absolutely completely 100% stumped too and have written it off to aufs magic I don't understand at the moment
[01:22] <Sarvatt> last time I successfuly did it that I remember was one of the lucid alpha releases
[01:22] <bryceh> hmm
[01:23] <bryceh> yeah I think it's probably better debugged at this point by someone who understands the filesystem magic more deeply
[03:06] <bjsnider> Sarvatt, my source package keeps freezing at 1k left. it will not finish uploading for some reason. does x-updates still work?
[03:09] <Sarvatt> bjsnider: try upload.ubuntu.com?
[03:09] <Sarvatt> [x-updates]
[03:09] <Sarvatt> fqdn = upload.ubuntu.com
[03:09] <Sarvatt> method = ftp
[03:09] <Sarvatt> incoming = ~ubuntu-x-swat/x-updates/ubuntu
[03:09] <Sarvatt> login = anonymous
[03:09] <Sarvatt> allow_unsigned_uploads = 0
[03:43] <bjsnider> no, didn't work
[03:59] <Sarvatt> wow, it uploaded so slow I didnt even get booted
[04:06] <Sarvatt> uploaded it all to xorg-edgers at any rate, can just rebuild copy them over if you cant get it uploaded
[05:34] <Sarvatt> bryceh: 3 bugs?!
[05:35] <bryceh> Sarvatt, ?
[05:35] <Sarvatt> http://www.bryceharrington.org/X/Reports/ubuntu-x-swat/totals-natty-workqueue.svg
[05:35] <Sarvatt> my mind is blown :)
[05:35] <bryceh> :-)  staying on top of the bug queue is paying off
[05:36] <Sarvatt> yeah thats crazy, post alpha 1 and 3 bugs..
[05:36] <bryceh> *nod*
[05:36] <Sarvatt> hmm then again
[05:36] <Sarvatt> http://www.bryceharrington.org/X/Reports/ubuntu-x-swat/totals-maverick-workqueue.svg
[05:36] <Sarvatt> june 3rd maverick A1
[05:36] <bryceh> yeah was just about to mention that
[05:37] <Sarvatt> guess I was thinking of the lucid chart that started late in the cycle :)
[05:37] <bryceh> the knee in that curve came around 2nd week of august
[05:38] <bryceh> plus, we haven't pulled in all the new X bits and pieces
[05:38] <Sarvatt> week after alpha 3 then
[05:38] <bryceh> most of the bug reports I've seen have ended up being bugs in other non-X things
[05:38] <Sarvatt> yeah true everythings just been juicy bug fixes vs lucid
[05:38] <Sarvatt> err maverick
[05:39] <bryceh> so maybe 50% of the bugs still aren't "fixed", it's just that the bug was misfiled
[05:40] <bryceh> one of the -intel bugs I forwarded upstream today, so not technically fixed, but there's nothing more we can do about it
[05:40] <Sarvatt> yeah, poor unity/compiz stealing all the bugs away :)
[05:40] <bryceh> heh
[05:40] <bryceh> at least it's not exposing new X issues (yet...)
[05:41] <Sarvatt> yeah no clutter abusing glx in painful ways is a huge win :)
[05:42] <bryceh> but my theory is that a lot of bugs that get filed are actually dupes of some underlying issue
[05:42] <bryceh> so one bug closed today may mean 10 or 100 that never get filed tomorrow
[05:44] <bryceh> it'd be cool to show the total bugs in maverick at the corresponding point in time, so we can see for natty how much better we're doing
[07:38] <Sarvatt> bryceh: hah, registered dutch on launchpad already?
[07:44] <bryceh> ok I officially hate how this computer freezes every other day
[07:45] <bryceh> Sarvatt, yeah of course gotta get dutch his launchpad id!
[07:45] <Sarvatt> every other day? on natty!? I've had 6 freezes today already, 2 were kernel panics
[07:46] <bryceh> this is on maverick
[07:46] <bryceh> pondering upgrading it
[07:47] <bryceh> I suspect it might be hw or memory issues; I have lots of weird random firefox crashes too, and it seems like every freeze is different
[07:49] <tjaalton> i might upgrade to natty after the holidays..
[07:49] <bryceh> heya tjaalton
[07:49] <tjaalton> howdy
[07:49] <Sarvatt> just in time for all the really bad breakage to hit!
[07:49] <tjaalton> yeah, lets upgrade everything on 23rd
[07:50] <Sarvatt> well mesa is releasing the day the sprint starts
[07:51] <Sarvatt> bryceh: sorry about the spam, we settled on https://launchpad.net/~canonical-hwe-team/+archive/ppa :)
[09:44] <seb128> hey there
[09:44] <seb128> could someone review the patches on bug #597895?
[09:45] <ubot4> Launchpad bug 597895 in xorg-server (Ubuntu) "X crashes on key press (affects: 4) (heat: 26)" [Undecided,Confirmed] https://launchpad.net/bugs/597895
[09:53] <tjaalton> the later patches should preferably get an upstream review
[09:54] <tjaalton> oops
[09:55] <tjaalton> seb128: i accidentally changed it to incomplete
[09:55] <tjaalton> though I guess it's more accurate since we need bob's reply
[09:55] <seb128> change it back? ;-)
[09:55] <seb128> ok
[09:55] <seb128> well the upstream bug has a commit and has been closed
[09:55] <seb128> not sure if that one could be commited in your vcs
[09:56] <tjaalton> yeah but the lp bug has several patches
[09:56] <seb128> right, I've asked about those
[09:56] <tjaalton> of which a couple are upstream
[09:56] <tjaalton> one is in 1.7-branch, the other is at least in master
[09:57] <tjaalton> i asked him to get peter to review them, since he seems to have been working with him on this
[09:57] <seb128> great, thanks
[10:51] <boneshaker> hello
[10:51] <boneshaker> when i try to send keysequence via xvkbd to client running on Xvfb - it kills Xvfb with fatal io error 11
[10:51] <boneshaker>  with other X servers (not Xvfb) it works fine
[10:51] <boneshaker> any ideas how to make it work on Xvfb? ty in advance
[10:53] <boneshaker> one more detail - it work with Xvfb - if i, before sending keysequence, run x11vnc on it and connect/disconnect to it, then i can send keysequences to client running on Xvfb without errors
[10:54] <boneshaker> Ubuntu 10.4
[16:29] <Sarvatt> awesome, braid and osmos are in the humble indie bundle this time, didn't know braid got a linux port! http://www.humblebundle.com/
[17:17] <gord> Sarvatt, the guy who made braid got annoyed with windows a while back and became an ubuntu convert, thats why we got a port :)
[17:19] <ion> :-)
[17:19] <Sarvatt> gord: I see he's a blob user too :)
[17:20]  * Sarvatt tells everyone to use the windows version in wine on intel
[17:21] <Sarvatt> hitting hardware limitations with the linux port
[17:21] <Sarvatt> i915_program_error: Exceeded max nr indirect texture lookups (8 out of 4)
[17:21] <Sarvatt> i915_program_error: Exceeded max nr indirect texture lookups (8 out of 4)
[17:21] <Sarvatt> i915_program_error: Exceeded max ALU instructions (83 out of 64)
[17:22] <Sarvatt> and s3tc is required, that's going to be a lot of pain for people
[18:28] <seb128> bryceh, could you try to sort out what needs sponsoring or not on bug #597895?
[18:28] <ubot4> Launchpad bug 597895 in xorg-server (Ubuntu Natty) (and 2 other projects) "X crashes on key press (affects: 4) (heat: 26)" [Undecided,Incomplete] https://launchpad.net/bugs/597895
[18:37] <Sarvatt> oh boy that bug, he had one of these super crappy things that was causing it http://www.dealextreme.com/details.dx/sku.16685
[18:37] <bryceh> seb128, I'm out sick today
[18:38] <bryceh> seb128, but looking at the three patches mentioned in his last comment they all look ok to me
[18:38] <bryceh> seb128, 0001 is obviously safe, just a null pointer check
[18:39] <bryceh> master_device.patch is #ifdef'd appropriately to just XDGA. 
[18:40] <bryceh> dix_dont_create_core_motion_events... looks to be an error check for a particular error situation.  That's the only one that looks like it could possibly have side effects
[18:41] <bryceh> seb128, I would suggest doublechecking that they are indeed upstream in xserver git, and if so they should be good to go for natty
[18:41] <Sarvatt> patch 4 caused a few regressions
[18:41] <Sarvatt> http://launchpadlibrarian.net/60381571/dix_dont_create_core_motion_events_for_non_xy_valuators.diff
[18:41] <seb128> bryceh, ok, thanks
[18:42] <Sarvatt> https://bugs.freedesktop.org/show_bug.cgi?id=30267
[18:42] <ubot4> Freedesktop bug 30267 in Input/Core "openarena mouse faliure since dix: don't create core motion events for non-x/y valuators" [Normal,Resolved: fixed]
[18:42] <Sarvatt> plus made the test suite fail
[18:42] <bryceh> Sarvatt, good catch
[18:44] <seb128> Sarvatt, could you comment on the bug to say that
[18:44] <seb128> ?
[18:44] <seb128> thanks ;-)
[18:45] <bryceh> ok, gonna un-irc for a bit
[18:45] <Sarvatt> digging through fedora git to see if they implemented it another way
[18:46] <Sarvatt> oh RHEL6 stuff isn't in git anymore, doh
[18:56] <Sarvatt> trading off fixing things on one specific crazy device that reports voltage as an axis for breaking mouse input in SDL for a large number of people there as-is
[21:04] <bdmurray> could fglrx-installer bugs with a build failure due to "kernel includes .. do not match current kernel" be combined?
[21:16] <Sarvatt_> there could be multiple reasons why they get that message, they could 1) not have headers installed at all 2) have a custom kernel with screwed up versioning 3) have something like generic headers only trying to build a generic-pae module 4) are installing from an older fglrx release that isn't compatible with the utsrelease.h move in 2.6.33 (like say using stock lucid fglrx with a newer kernel)
[21:17] <Sarvatt_> i'm sure i'm forgetting some but thats what I saw from a quick glance at those just now
[21:23] <ilmari> what's the easiest way to test drm-intel-fixes or drm-intel-next on maverick?
[21:27] <ilmari> hm, http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ only has natty kernels
[21:27] <Sarvatt> jeeze, I lost count of how many freezes that was today, alpha nvidia drivers are no joke
[21:28] <Sarvatt> ilmari: for drm-intel-next I believe there is a daily build in the mainline ppa?
[21:28] <ilmari> Sarvatt: only for natty afaict
[21:28] <ilmari> (see the link I just pasted)
[21:28] <Sarvatt> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/
[21:28] <Sarvatt> that just means it has the natty config
[21:28] <Sarvatt> will work fine on maverick
[21:28] <Sarvatt> oh sorry, I didn't see your link, froze right when you asked about the easiest way to test
[21:29] <ilmari> ah
[21:29]  * ilmari gives it a go
[21:32] <ilmari> no luck :(
[21:45] <ilmari> are there no brits in the intel drm development team?
[21:45] <ilmari> it's the bbc iplayer backround that triggers the flickering
[21:47] <Sarvatt> ickle (Chris Wilson) in #intel-gfx is, he has an x201s too which is why it's weird
[21:55] <ilmari> hm, I get "can't send to channel" there
[22:14] <Amaranth> Anyone tried i965g lately?
[22:20] <Dr_Jakob> Amaranth: its dead jim.
[22:24] <Amaranth> Well, there goes the idea of working on GLES stuff on my main computer
[22:25] <Dr_Jakob> the classic driver should support gles
[22:26] <Sarvatt> Amaranth: you have to play with egl env vars to pick egl_dri2 instead of egl_gallium, it defaults to gallium if mesa is built with it
[22:26] <Amaranth> Dr_Jakob: Mesa 7.10-devel implementation error: Incomplete OpenGL ES 2.0 support.
[22:26] <Amaranth> Sarvatt: Oh? Time to dig some more
[22:26] <Sarvatt> EGL_DRIVER=egl_dri2
[22:26] <Sarvatt> oh
[22:27] <Sarvatt> that might be something else, sorry
[22:27] <Amaranth> Sarvatt: Nope, that worked
[22:27] <Sarvatt> ah cool
[22:27] <Amaranth> Before I was getting some assembler debug output
[22:27] <Amaranth> Now I've got something drawing on the screen! Thanks!
[22:28] <Amaranth> Sarvatt: You just saved me from having to ssh to a computer with an nvidia GPU and look at the screen from across the room to see if things work :)
[22:29] <RAOF> :)
[22:30]  * Amaranth tosses that in /etc/environment
[22:33] <RAOF> That shouldn't be *too* hard to fix properly,  I think.
[23:43] <Sarvatt> probably worth repeating here, don't upgrade sudo on natty at the moment :)
[23:43] <ion> Heh, ok
[23:44] <Sarvatt> fun bug https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/690873
[23:44] <ubot4> Launchpad bug 690873 in sudo (Ubuntu) "latest natty sudo upgrade removes admin from /etc/sudoers (affects: 2) (heat: 16)" [Critical,Triaged]