[00:01] <bryceh> bdmurray, aha, awesome
[00:02] <bdmurray> bryceh: its not a good solution but something to get the data right now
[00:02] <bryceh> bdmurray, do you think this issue is important enough to put in for alpha-2?
[00:03] <bdmurray> bryceh: I forget it doesn't block bug reporting for X right?
[00:03] <bryceh> bdmurray, not that I know
[00:03] <bryceh> actually it might for some cases
[00:05] <bryceh> bdmurray, I take it you're alluding to say, "Dummy, people being unable to report bugs kinda undermines the whole idea of having an alpha release"
[00:06] <bdmurray> bryceh: well more like "If it prevents getting useful data then yes its important for A2"
[00:06] <bdmurray> bryceh: or if it makes people goto +filebug instead of using ubuntu-bug ;-)
[00:08] <bryceh> bdmurray, how's this look:
[00:08] <bryceh>         if os.path.lexists('/usr/lib/nux/unity_support_test'):
[00:08] <bryceh>             try:
[00:08] <bryceh>                 ust = command_output_quiet([
[00:08] <bryceh>                     '/usr/lib/nux/unity_support_test', '-p'])
[00:08] <bryceh>                 ust = ust.replace('\x1b','').replace('[0;38;48m','').replace('[1;32;48m','')
[00:08] <bryceh>                 report['UnitySupportTest'] = ust
[00:08] <bryceh>             except AssertionError:
[00:08] <bryceh>                 report['UnitySupportTest'] = 'FAILED TO RUN'
[00:09] <bdmurray> testing it without the work around - I can still report a bug
[00:10] <bdmurray> but that looks fine to me
[00:10] <bryceh> alrighty
[00:16] <bryceh> bdmurray, uploaded
[00:16] <bryceh> might be too late for alpha-2 but we'll see
[00:17] <bdmurray> have you thought about moving the hook to a "smaller" package at all?
[00:21] <bryceh> the xorg package is actually quite small
[00:21] <bryceh> but yeah I've thought of maybe moving this apport hook and the intel gpu hook (and maybe the old bulletproof-x bits) out into a separate package
[00:22] <bryceh> -ENOTIME ;-)
[00:22] <bryceh> if nothing else, doing so would help to minimize our diff against the debian upstream packages.
[00:22] <bryceh> but I think there might also be some potential for shared code between the three scripts
[00:25] <bdmurray> I thought the 'Unsupported Ubuntu Release' bit would be good in apport proper
[00:26] <bryceh> bdmurray, thanks yeah I think so too
[00:27] <bryceh> there is some logic for figuring out what kind of regression the bug is, which I think might be a bit better than what's in the kernel apport hook as it has less user prompting
[00:28] <bryceh> feel free to cherrypick.
[00:28] <bryceh> I eventually plan to try submitting some of it back to apport, if/when we ever get caught up on the X bugs
[00:34] <bryceh> RAOF, I'm losing steam as EOD approaches but have hammered the tip off of Spikey McSpike - http://www.bryceharrington.org/X/Reports/ubuntu-x-swat/totals-natty-workqueue.svg
[00:35] <bryceh> RAOF, if you get a chance today could you look at bugs #707236 and #710961 - two corruption regression bugs
[00:35] <ubot4> Launchpad bug 707236 in xserver-xorg-video-intel (Ubuntu Natty) (and 2 other projects) "corruption in xchat-gnome window (affects: 3) (heat: 26)" [High,Confirmed] https://launchpad.net/bugs/707236
[00:35] <ubot4> Launchpad bug 710961 in xserver-xorg-video-intel (Ubuntu) "[i945gm] Screen Corruption with new Xorg stack (affects: 2) (heat: 14)" [Undecided,New] https://launchpad.net/bugs/710961
[00:35] <RAOF> Certainly.
[00:35] <bryceh> thanks, I'm going to try focusing on forwarding the new bugs and patches upstream tomorrow.
[00:36] <bryceh> if there's any you already have an inkling about please put a comment on them - here's a report that might be easier to work from: http://blumonc/Arsenal/Reports/ubuntu-x-swat/workqueue-natty.html
[00:37] <RAOF> blumonc?
[00:37] <bryceh> dah
[00:37] <bryceh> http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/workqueue-natty.html
[00:38] <bryceh> if there's any you want to look into yourself, assign yourself and I'll skip upstreaming them for now
[00:38] <RAOF> Ok.
[00:40] <bryceh> the couple tagged iso-testing and pcert are also probably high priorities for us
[02:22] <RAOF> Ok, I think I'm closing in on bug #707236.  Interested parties should try reverting 1ba983034 from xserver-xorg-video-intel. :)
[02:22] <ubot4> Launchpad bug 707236 in xserver-xorg-video-intel (Ubuntu Natty) (and 2 other projects) "corruption in xchat-gnome window (affects: 3) (heat: 26)" [High,Confirmed] https://launchpad.net/bugs/707236
[03:09] <Amaranth> RAOF: Yeah, that looks likely
[03:10] <RAOF> Well, not only likely, but reverting it fixes emacs for me.
[03:10]  * Amaranth kicks qwest
[03:10] <Amaranth> I may not be able to test for a while, internet is like dialup with slightly better ping right now
[03:11] <RAOF> Yay.
[03:12] <RAOF> Anyway, I'm working out whether that commit was always broken, or is interacting with the damage updates in Xserver 1.10
[03:16] <Amaranth> yay it sped up, building now
[03:21] <Amaranth> test
[03:21] <Amaranth> hrm, need a long line first
[03:21] <Amaranth> test again
[03:21] <Amaranth> yay
[03:21] <Amaranth> RAOF: Confirmed, that fixes the problem
[03:21] <RAOF> Amaranth: Nifty.
[03:21] <Amaranth> hmm, got an apport report for memcheck-amd64
[03:21] <Amaranth> that's scary
[03:24] <Amaranth> odd that regular xchat didn't have the problem, I guess they've gotten out of sync
[03:25] <RAOF> Maybe.  Emacs has a similar problem.
[03:25] <RAOF> It's probably only things which draw in specific ways.
[04:01] <RAOF> Hm, no.
[04:01] <RAOF> Looks like that commit is just broken.
[04:43] <bjsnider> Amaranth, i have been trying to tell you that xchat is better
[04:44] <Amaranth> bjsnider: Oh no, I used it for a couple hours to see if it had gotten better
[04:44] <Amaranth> It's ugly
[04:44] <bjsnider> what?
[04:45] <Amaranth> It doesn't sort networks alphabetically, uses colors instead of icons to represent incoming messages, you have to show the user list to see the lag stats, and I always had to right click a URL to open it
[04:46] <bjsnider> wow
[04:46] <bjsnider> all of the things you just mentioned would irritate me in reverse
[04:47] <bjsnider> i find the colors better for incoming messages than the icons in xchat-gnome
[04:47] <bjsnider> i don't want every stray click opening a url
[04:47] <bjsnider> the networks don't have to be sorted at all
[04:48] <bjsnider> i thought your original objection to it was that it didn't have support for any gnome themes and so forth.
[07:09] <Amaranth> bjsnider: Not themes, integration (using gconf, HIG, etc)
[07:19] <LLStarks> stupid question. is it possible to have a task started in an ssh session continue after that session ends?
[07:22] <soren> LLStarks: Not really on-topic in here, but look at nohup's man page.
[08:48] <ara> bryceh, hello!
[08:49] <bryceh> ara, hi
[08:50] <ara> bryceh, we got a similar bug about xorg crashing for intel during ubiquity installation
[08:50] <ara> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/708744
[08:50] <ubot4> Launchpad bug 708744 in xorg (Ubuntu) "Xorg segfaults during installation process (affects: 1) (heat: 10)" [High,Triaged]
[08:50] <ara> we opened a new one, but it seems to be quite similar to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/705078
[08:50] <ubot4> Launchpad bug 705078 in xserver-xorg-video-intel (Ubuntu) "Xorg crashed with SIGSEGV in pixman_image_set_has_client_clip() (affects: 9) (dups: 2) (heat: 64)" [High,Fix released]
[08:52] <bryceh> ara, what I think would help would be to gather a full backtrace
[08:52] <bryceh> ara, I can look into it more tomorrow; it's late for me
[08:52] <ara> bryceh, sure, good night!
[08:52] <bryceh> ara, probably what I should do is figure out how to reproduce it on my own hardware
[08:53] <bryceh> ara, any tips on how to reproduce it could probably help
[08:53] <bryceh> ara, ultimately I suspect that the crashes are symptomatic of a deeper issue at work, which remains mysterious
[08:54] <bryceh> ara, I'm also somewhat wondering if it may be a peculiarity of the testing environment, because I've not seen similar reports from ordinary users installing normally
[08:54] <ara> bryceh, no idea, for us it always happens (using a preseeded installation over the network)
[08:54] <bryceh> it makes me wonder if this is dependent on some characteristic of how these tests are being installed
[08:55] <ara> bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/706117 contains the preseed file
[08:55] <ubot4> Launchpad bug 706117 in ubiquity (Ubuntu) "Installation fails using preseed file and network install (affects: 1) (heat: 10)" [Undecided,New]
[08:55] <ara> it may help you trying to reproduce it
[08:56] <seb128> bryceh, hey, thanks for the dx reports
[08:56] <seb128> bryceh, thanks for sending the email to the list as well
[08:57] <bryceh> ara, unfortunately I don't know how to make use of "preseed files" - if you can explain further on the bug report it might help me
[08:57] <bryceh> seb128, heya, yep glad they're of use
[08:58] <ara> bryceh, sure, will do 
[08:59] <seb128> bryceh, do you think having a summary of natty tasks would be useful as well?
[08:59] <seb128> it's a bit similar to the milestoned list
[09:05] <bryceh> seb128, you mean bug tasks targeted to a particular release, yeah I think that could be of use
[09:07] <bryceh> seb128, I don't have that hooked up yet though
[09:07] <seb128> bryceh, right, I wanted the milestone list to build a list of things we (desktop or contributor) should work on if they want to help unity
[09:07] <seb128> but I figure that "bugs that would be nice to fix for natty" are either milestoned or have a natty task
[09:07] <bryceh> seb128, could you file a bug against arsenal requesting this?  It can be done but might take a bit before I get to it.
[09:07] <seb128> so we might still miss the ones without a milestone
[09:08] <seb128> bryceh, ok, will do
[09:08] <bryceh> seb128, yeah agreed
[09:08] <seb128> the workaround would be milestone all the bugs we are about for beta or natty
[09:08] <seb128> are->care
[09:08] <bryceh> I've been lucky with xorg to not have so many bugs (yet) to need to filter on that, but for unity I can see that would be quite handy
[09:09] <bryceh> seb128, btw with the 'workqueue' report, a technique for managing it is to be very aggressive at setting bugs to Incomplete.  Since the report excludes bugs waiting on responses, that can help keep the report useful.
[09:10] <bryceh> plus it has the pleasant side effect of making reporters feel they're getting quick responses ;-)
[09:17] <bryceh> night (dead tired)
[09:20] <seb128> bryceh, right, thanks for the hint, 'night!
[13:52] <mvo> hey guys, anyone minds if I upload http://paste.ubuntu.com/561936/ ? (xserverxorg-video-intel)
[13:55] <tjaalton> mvo: pretty sure it's ok
[17:33] <alf_> Hi! I am using the xorg-edgers PPA. For r600 the classic driver is the default for GL, although when running GLES2 apps the gallium driver is used.
[17:35] <alf_> The problem is that when forcing gallium (ForceGallium="true" in xorg.conf) GLES2 apps now complain with "libEGL warning: DRI2: could not open  (No such file or directory)"
[17:36] <alf_> GLES2 apps run fine with gallium when not forcing it in xorg.conf
[17:36] <alf_> Any ideas?
[17:37] <Sarvatt> EGL_DRIVER=egl_gallium yourapp work?
[17:38] <Sarvatt> there has been a bunch of changes for the egl stuff recently in 7.11 and i haven't had time to fix it all up
[17:39] <alf_> Sarvatt: http://paste.ubuntu.com/562094/
[17:40] <alf_> it uses the softpipe, while when not forcing gallium it correctly uses the hardware driver
[17:41] <Sarvatt> its because we're renaming the dri2 driver name for the forcegallium thing
[17:42] <Sarvatt> (to r600g)
[17:42] <Sarvatt> natty mesa doesn't work either right?
[17:43] <alf_> Sarvatt: haven't checked, I was following the +gallium PPA before and now switched to the main xorg-edgers one
[17:52] <Sarvatt> hmm, looking at it I'm not sure how to fix that
[17:55] <Sarvatt> alf_: to work around it you could just drop forcegallium and make /usr/lib/dri/r600_dri.so the gallium version
[17:58] <bryceh> RAOF, another funky upgrade blockage - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/712640
[17:58] <ubot4> Launchpad bug 712640 in xorg-server (Ubuntu) "package xserver-xorg-core 2:1.9.0.902-1ubuntu4 failed to install/upgrade: ErrorMessage: installing xserver-xorg-core would break existing software (affects: 1) (heat: 6)" [Undecided,New]
[18:05] <Darxus> How much of wayland's dependencies made it into alpha 2?  Should a pre-BGRA version build and work, but not the latest with BGRA?
[18:05] <Darxus> And is it appropriate for me to ask here?
[18:07] <bryceh> Darxus, some deps didn't make it; I've been waiting on cairo in particular which is still tbd
[18:08] <Darxus> Thanks.
[18:08] <bryceh> it was my goal to have it all in by alpha-2 but just didn't have time, too many other priorities
[18:09] <Darxus> I understand.
[18:11] <Darxus> I appreciate that it's on your list.  And I'll care more when wayland is actually usable :)
[18:12] <jcristau> that'll take a while
[18:14] <Darxus> jcristau: Yup.
[18:44] <alf_> Sarvatt: Yes, I think I'll do that and keep the old version around to use it with LIBGL_DRIVERS_PATH if needed
[18:44] <alf_> Sarvatt: though it complicates upgrading as I have to do this everytime I upgrade :(
[18:44] <Sarvatt> yeah :(
[18:45] <Sarvatt> I'm not sure how to fix it properly, it's broken in natty too from what I can see
[18:45] <Sarvatt> need to make the r600 gallium driver accept a r600g dri driver name too
[18:47] <alf_> Sarvatt: was the idea of having an r600_dri symlink to either r600c or r600g considered as a solution to gallium vs mesa selection?
[18:48] <alf_> I mean gallium vs classic
[18:50] <Sarvatt> yeah it was but no one wanted to implement all the extra complexity in the mesa packages and you lose the ability to have automatic fallbacks to the other driver if you switch to UMS for example
[18:51] <Sarvatt> that option is starting to grow on me though :)
[18:52] <jcristau> what about just shipping one driver?
[18:53] <jcristau> and if you want ums, then tough, you don't get 3d.
[18:53] <Sarvatt> next cycle
[18:53] <jcristau> k
[19:50] <Q-FUNK> howdy! seems that X upgrade from maverick barfs majorly.
[19:51] <Q-FUNK> everything correctly depends upon video driver 9, but dpkg refuses to deconfigure older drivers during the upgrade, because it would break them
[19:54] <Q-FUNK> seems that we need to remove xserver-xorg-video-v4l before we do anything else
[22:00] <RAOF> Woot!  Intel corruption fixed.
[22:00] <Q-FUNK> RAOF: where? :)
[22:01] <RAOF> Upstream, and cherry-picked by mvo.
[22:04] <Q-FUNK> nice
[22:04] <Q-FUNK> already in natty?
[22:53] <bryceh> yep
[23:22] <bdmurray> bryceh: xorg package hook has CompositorRunning and CompisitorRunning keys in it
[23:23] <bryceh> heh
[23:25] <bdmurray> also I'm not sure report[compiz_version] gets set anywhere
[23:25] <bryceh> fixed the misspelling
[23:26] <bryceh> yeah that should just be 'compiz_version', darn