[00:06] <ubotu> New bug: #139505 in ubuntu "dell E1705 will not boot into X from liveCD. (dup-of: 174434)" [Undecided,New] https://launchpad.net/bugs/139505
[00:38] <bdmurray> bryce: I got a weird pending post to the bugsquad mailing list regarding /usr/share/doc/x11-common/copyright
[00:38] <bryce> what about it?
[00:39] <bdmurray>  The                                                    
[00:39] <bdmurray> first part covers changes and additions made in Ubuntu package, the second                                                 
[00:39] <bdmurray> one is for Debian. But the warranty disclaimers in both parts are identical
[00:40] <bdmurray> There is more but that's the relevant bit
[00:59] <bdmurray> bryce: does that mean anything to you?
[01:00] <bryce> well I'd need to see the specific complaint
[01:00] <bryce> the copyright file is just a summary of licensing for the package
[01:01] <bdmurray> okay, I'll just let the post through to the mailing list if that works for you
[01:01] <bryce> fine.  I don't know if I'm on bugsquad though
[01:01] <bryce> probably they should be posting it to the ubuntu-x list.
[01:06] <bdmurray> Do you know why ubuntu-x isn't under the development lists?
[01:07] <bryce> nope
[01:07] <bdmurray> Is it more development related?
[01:13] <bryce> yes
[01:17] <bdmurray> You could submit an RT to get it reorganized at lists.ubuntu.com
[01:21] <bryce> I don't care
[02:00] <ubotu> New bug: #182181 in xserver-xorg-input-mouse (main) "bluetooth mouse does not work" [Undecided,New] https://launchpad.net/bugs/182181
[05:38] <pcjc2> hi
[05:38] <pcjc2> Bryce, people.. does anyone happen to know if the Intel driver crash with something about "repaint cursors" in the backtrace still occurs in Hardy?
[05:38] <bryce> heya pcjc2
[05:38] <pcjc2> I'm not on Hardy yet (and dreading it if EXA can't be sorted really)
[05:39] <pcjc2> But I can mostly reproduce that repaint cursors crash pretty easily
[05:39] <bryce> I had been looking at that bug report earlier today; it's not closed
[05:39] <bryce> I've not tried reproducing it on hardy yet though
[05:39] <pcjc2> No one was able to reliably reproduce it though
[05:40] <bryce> ah
[05:40] <pcjc2> I can get it to fire pretty much about 20% of the time I launch a windows GTK app under wine
[05:40] <pcjc2> not your ideal test case unfortunately, but a start
[05:41] <bryce> pcjc2: which bug# is it?
[05:41] <pcjc2> it sucks muchly.. given I'm trying to use Wine to debug a windows port of some software ;)
[05:42] <pcjc2> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/153466
[05:42] <ubotu> Launchpad bug 153466 in xserver-xorg-video-intel "[gutsy] X crashes randomly - something with cursors? (945GM)" [High,Confirmed] 
[05:42] <pcjc2> launchpad edge is broken though.. had to disable redirect to get it
[05:43] <bryce> ah yeah right
[05:44] <bryce> I was looking at forwarding it upstream, but the bug report doesn't look ripe enough yet
[05:44] <bryce> steps to reproduce, or a more detailed definition would help
[05:44] <pcjc2> Some way to log what wine does to X to kill it might be handy
[05:45] <bryce> the last post put some links in that would be worth investigating (I looked at the first two links, but didn't understand how they were related)
[05:47] <pcjc2> I get http://launchpadlibrarian.net/11305508/100_1241.JPG too
[05:47] <pcjc2> and some full screen apps (eog ?) get very upset running in full screen mode with compiz
[05:48] <pcjc2> but I'm not on Hardy, so I guess this isn't too interesting
[05:56] <bryce> I'm about to post that one upstream; just need to check if it's already reported on fdo
[06:01] <pcjc2> Can I show my ignorance... how do I clone this cvs repo?
[06:01] <pcjc2> http://keithp.com/cvs/xscope/
[06:01] <pcjc2> Can't seem to find any official upstream
[06:02] <pcjc2> no debian package etc..
[06:03] <pcjc2> never mind.. found out.. xmon is the way forward
[06:35] <pcjc2> Bryce.. seems all you have to do is hook up an X11 protocol debugger, and the crash reproducibility will go away ;)
[06:35] <pwnguin> hah
[06:35] <pwnguin> what about gdb?
[06:36] <pcjc2> haven't got my other box on at the moment to try it
[06:36] <pcjc2> But I guess that is another way to attack the problem
[06:36] <bryce> oh yeah I love bugs that go away once instrumentation's attached ^_^
[06:36] <pcjc2> there are backtraces for this crash already...
[06:37]  * pcjc2 wonders if an entire X server can be run under valgrind...
[06:39] <pcjc2> anyway... I should get some sleep.. will debug this more if it bites again
[06:44] <bryce> night
[06:53] <pwnguin> i think you can valgrind x
[06:53] <pwnguin> the debugging x wiki suggested it under advanced
[06:53] <pwnguin> not sure what you'd do
[07:50] <tjaalton> pcjc2: hey, we are still carrying a couple of patches (01_fix_compiz_video.diff, 05_fix_xv_reset.diff) on intel. Are they going to be upstream or not?
[08:08] <tjaalton> https://edge.launchpad.net/obsolete-junk/
[08:08] <tjaalton> haha
[08:08] <tjaalton> I wan't to contribute!
[08:08] <tjaalton> uh, -'
[08:11] <tjaalton> xorg bug count getting close to 200
[08:19] <bryce> heya tjaalton
[08:19] <tjaalton> hi bryce
[08:19] <tjaalton> still up :)
[08:19] <bryce> yeah, it's barely after midnight!
[08:19] <tjaalton> oh right.. I stayed until 3AM
[08:19] <tjaalton> +up
[08:19] <tjaalton> last night that is
[08:20] <bryce> today I worked a good bit on getting the moblin box reinstalled to test the new -psb, but no luck.  Maybe monday
[08:20] <bryce> after that I made good progress getting several -intel bugs upstream
[08:21] <tjaalton> the "3D artifacts" is actually known upstream..
[08:21] <bryce> I suspected it must be
[08:21] <bryce> couldn't locate a bug report for it though
[08:21] <tjaalton> it'll get fixed once cworth get's his stuff finished
[08:21] <bryce> yeah, hmm
[08:21] <tjaalton> and that needs all the flashy stuff that upstream is working on atm
[08:22] <bryce> sounds like it'll end up hardy+1-ish
[08:22] <tjaalton> yep
[08:22] <tjaalton> hopefully!
[08:22] <tjaalton> and not +2
[08:23] <tjaalton> I'm cleaning up the xorg bugs again, goal to get the count closer to 150
[08:24] <bryce> ok, well next task is getting my bug plot tool working with FF3.0.  *sigh*
[08:24] <tjaalton> hehe
[08:34] <bryce> huh, that was easy
[08:35] <tjaalton> bdmurray: the launchpad-janitor is not cleaning up bugs automatically, is it only done periodically and not automatically?
[08:35] <bryce> bdmurray's probably asleep
[08:36] <tjaalton> heh, ok
[09:43] <bryce> here's the ff3 bug - http://bryceharrington.org/drupal/node/28
[09:56] <tjaalton> yeah, I noticed the post
[10:01] <ubotu> New bug: #182237 in linux-restricted-modules-2.6.24 (restricted) "restricted manager does not recognize nvidia 8600M GT on hardy" [Undecided,New] https://launchpad.net/bugs/182237
[10:08] <tjaalton> whoops that's a valid bug, for a change
[10:25] <ubotu> New bug: #182242 in linux-restricted-modules-2.6.24 (restricted) "fglrx driver missing" [Undecided,New] https://launchpad.net/bugs/182242
[10:41] <ubotu> New bug: #182245 in xserver-xorg-video-openchrome (main) "moving cursor over 3D image causes distortion" [Undecided,New] https://launchpad.net/bugs/182245
[10:41] <ubotu> New bug: #182246 in xserver-xorg-video-openchrome (main) "Strange message about drmWaitVBlank openchrome driver" [Undecided,New] https://launchpad.net/bugs/182246
[11:23] <tjaalton> xorg bugs down to 184, need a break ->
[12:48] <tjaalton> whee, less than 1700 bugs in the team packages
[13:46] <ubotu> New bug: #17904 in xserver-xorg-video-s3 (main) "cannot configure X for graphics card with 1MB ram" [Low,Confirmed] https://launchpad.net/bugs/17904
[14:31] <ubotu> New bug: #182301 in xorg (main) "xnest manual page fails to document authentication" [Undecided,New] https://launchpad.net/bugs/182301
[14:42] <jcristau> 182301 should be closed as invalid imo
[14:42] <tjaalton> just did :)
[14:42] <tjaalton> jcristau: thanks for checking the manpage
[14:43] <jcristau> np
[14:56] <tjaalton> heh, at least two old bugs against ati where the reporter was so upset that he bought a nvidia card :P
[16:31] <pcjc2> I'd consider that when buying a new laptop... not impressed with the Intel drivers at the moment!
[16:31] <bdmurray> tjaalton: It is not enabled for the Ubuntu project
[17:38] <tjaalton> bdmurray: ah ok
[17:39] <tjaalton> pcjc2: did you see my question about the patches?
[17:51] <pcjc2> where was that?
[17:51] <pcjc2> ok, I see 01_fix_compiz_video.diff, 05_fix_xv_reset.diff
[17:52] <pcjc2> It wasn't clear... if it was a fix for XXA, they weren't particularly interested
[17:52] <pcjc2> 01_fix_compiz_video.diff forces the texture extension disabled, doesn't it... wasn't one of mine.
[17:52] <pcjc2> Its basically a wontfix since they want eveyone on EXA
[17:53] <pcjc2> it might be worth testing without 05 on Hardy, to see if it has been fixed  more appropriately
[17:56] <tjaalton> ok
[17:56] <Q-FUNK> re
[17:56] <tjaalton> what was the bug #'s for those?
[17:56] <tjaalton> were
[17:57] <Q-FUNK> bryce: would it be possible to merge Bartman's patch to X server and to release to gutsy proposed updates, to allow broader testing?
[17:58] <tjaalton> Q-FUNK: put it in a ppa?
[17:58] <Q-FUNK> tjaalton: that could work too, but won't result in as wide of a testing as needed
[18:01] <tjaalton> well, who uses -proposed?
[18:02] <bdmurray> tjaalton: however there are reports show what would expire and I have some workflows for finding them if you are interested
[18:02] <tjaalton> bdmurray: that would be cool
[18:03] <tjaalton> I find it very confusing, that only sorting the bugs by some other metric than importance shows _less_ bugs
[18:04] <tjaalton> for instance bugs on xorg goes down from 166 to 123
[18:04] <bdmurray> tjaalton: I use bugnumbers from bughelper a lot for querying for bugs.  I'm headed out at the moment but will e-mail you.
[18:05] <tjaalton> bdmurray: excellent, thanks
[18:07] <pcjc2> 05 was #141063
[18:07] <pcjc2> I don't see a bug # for 01_...
[18:08] <pcjc2> it seems this info has been lost in the Debian changelog for the intel 2.2.0 driver
[18:10] <tjaalton> ah, true
[18:11] <tjaalton> but it's not on the changelog of 2:2.1.1-0ubuntu9 either, where it was introduced :)
[18:12] <pcjc2> 05_... had a closes line
[18:12] <pcjc2> 01_... didn't
[18:13] <tjaalton> yep, but if it's carried on the merge diff, those bugs would get another post when the new version is uploaded
[18:13] <tjaalton> although the closes line could be changed to prevent that
[18:14] <tjaalton> s/merge diff/changelog of the new merge/
[18:16] <pcjc2> ok
[18:16] <pcjc2> I think there was a better fix for 05_... which Keith P pointed out
[18:17] <tjaalton> looking at the upstream bug it was committed too
[18:17] <pcjc2> I'm trying to find it... but my various mailboxes are somewhat full. Its likely on a fd.o bug
[18:17] <tjaalton> https://bugs.freedesktop.org/show_bug.cgi?id=12437
[18:17] <ubotu> Freedesktop bug 12437 in Driver/intel "Server  and computer lockup  when trying to play Xv" [Normal,Resolved: fixed] 
[18:20] <tjaalton> at least that's linked from that bug
[18:20] <pcjc2> https://bugs.freedesktop.org/show_bug.cgi?id=12356
[18:20] <pcjc2> https://bugs.freedesktop.org/attachment.cgi?id=12307
[18:20] <ubotu> Freedesktop bug 12356 in Driver/intel "[845] hang after VT switch (was xvideo crashes)" [Normal,Resolved: duplicate] 
[18:23] <pcjc2> Seems that the bug this was a dup of has a better fix, which should be included already
[18:26] <pcjc2> http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commit;h=a2a0821e74a61f53cc7f0c41ce629644ad712114
[18:27] <pcjc2> made it in before 2.2.0
[18:28] <pcjc2> Also..  some of the 855 crash on lid close bugs were addressed here
[18:28] <pcjc2> (Quirk added for Inspiron 510m)
[18:28] <pcjc2> http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commit;h=3c22ed633be2ac96eea7bc533839e956f1f31b84
[18:29] <pcjc2> this is also relevant
[18:29] <pcjc2> http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commit;h=f69b48fe24ef94dac44b8123884ca71df675be4b
[19:00] <ubotu> New bug: #144092 in linux-restricted-modules-2.6.22 "googleearth does not start on gutsy amd64." [Undecided,Invalid] https://launchpad.net/bugs/144092
[19:45] <bryce> tjaalton: wow nice!  xorg New bugs down to 45!!
[19:46] <bryce> open bugs down by half!  niice
[19:50] <bryce> Q-FUNK: I'd like to look at the patch, but if you'd like to upload it to -proposed, that's probably fine
[20:09] <tjaalton> bryce: yeah, it's going pretty well :)
[20:09] <bryce> you were right about that 3D artifacts bug - it got duped up over night
[20:10] <bryce> it suddenly clicked - this is one that the compiz folks were talking to me about at the last conference I think
[20:11] <bryce> you know, in a way I kind of grimace at the fix...  I suspect that yeah, maybe the indirect direct rendering will fix it for -intel, but is this going to be yet another thing that ends up breaking half the other drivers?  :-/
[20:12] <tjaalton> I'm not sure yet..
[20:12] <bryce> maybe I'm just still bitter over needing ttm for fixing the 965 EXA performance stuff ;-)
[20:12] <tjaalton> my problem is that I should probably draw a mind map about all of this, since there's just too much scattered information for my little brain to handle :)
[20:12] <bryce> yeah
[20:12] <bryce> inkscape ftw :-)
[20:13] <tjaalton> I wonder if kernel modesetting is also required, so then we'd need to touch kernel too (and that was turned down at UDS)
[20:14] <bryce> at my last job, my CTO used inkscape for doing his mind maps, which was really awkward, because he'd always come over for bug fixes and tech help, and I'd be thinking, "Er, this is a hobby project... but if you assigned me to work on it I'd love to look at those..."
[20:15] <tjaalton> hehe
[20:15] <tjaalton> I haven't used inkscape for that yet, but "dia" a little
[20:16] <bryce> dia is still good for doing UML diagrams, but at this stage I think inkscape generally is better for most other kinds of technical drawings
[20:32] <tjaalton> yep
[20:33] <tjaalton> hm, I can only save one stock reply with the greasemonkey script
[20:33] <tjaalton> the others aren't saved
[20:49] <bryce> tjaalton: yeah I have problems with it not saving mine either
[20:49] <bryce> tjaalton: in testing it out a bit, I think it saves them permanently only if you exit firefox; if it crashes or gets killed, it definitely doesn't save them
[21:18] <tjaalton> bryce: could be that I haven't restarted firefox in the meantime
[21:19] <bryce> to be honest, I don't use the canned responses script too much since it seems to always forget my settings unexpectedly :-/
[21:20] <bryce> I tried debugging it, but the issue seems to be something inside firefox and/or greasemonkey
[21:20] <tjaalton> ok..
[21:46] <pwnguin> dont take this the wrong way, but i thought inkscape would be usable with a wacom tablet
[21:47] <pwnguin> but i dont think vector art and tablets really work together
[21:47] <bryce> hmm, I've heard inkscapers using it with wacom.  But I know there's some quirks and bugs
[21:47] <bryce> I've not tried it myself though
[21:48] <pwnguin> well, from the name, you'd think it's perfect
[21:48] <pwnguin> but don't worry, just about everything doesn't work optimally with tablets
[21:51] <bryce> as we say, "send in a patch" ;-)
[21:56] <pwnguin> mostly, it's just that it isnt artRage
[21:59] <bryce> artRage?
[22:04] <bryce> dang you've been doing a lot Timo...  I'm just now going through my LP emails and it's like 50% of them are from you!  ;-)
[22:05] <tjaalton> you know the key, it's just beside enter ;)
[22:05] <tjaalton> I need another beer, that wasn't even funny..
[22:06] <bryce> hehe
[22:08] <tjaalton> hmm, I'll try Glenlivet instead
[22:08] <tjaalton> the xorg bugs are getting harder all the time
[22:09] <tjaalton> it's just too tempting to say "whatever.. <invalid>"
[22:09] <tjaalton> or maybe just leave them be for now
[22:18] <bryce> hehe
[22:18] <bryce> I'm starting to assign milestone "Later" for ones I know we can't do anything about and don't expect to see fixed for a while
[22:18] <tjaalton> that's good
[22:21] <bryce> I went through all the milestones yesterday to see if there's any we're on the hook for
[22:22] <bryce> there was only one that I recall, but it was just a sync or merge request
[22:22] <bryce> maybe it's already been closed
[22:22] <tjaalton> maybe the -amd sync, which is done now
[22:23] <bryce> yeah I'm pretty sure it was -amd.
[22:24] <bryce> I saw that Travis also seems convinced we will need to go back to XAA for Hardy
[22:25] <bryce> guess I need to just accept it...  when do you think we'll flip that back?
[22:25] <bryce> I've let Dell and Intel know about the issue, but haven't heard a response from them yet.  Maybe monday.
[22:26] <tjaalton> next week is early enough
[22:26] <tjaalton> I mean there is no rush or anything
[22:26] <bryce> right
[22:26] <tjaalton> before next alpha of course
[22:27] <bryce> will we need to reactivate that XAA patch that was making it impossible for people to turn EXA on?
[22:27] <bryce> maybe if we can avoid that patch, we can at least say that people can choose to opt-in to EXA, and at least that will be a step forward from gutsy
[22:28] <tjaalton> actually, there was one bug that left me wondering.. the server is using i810 by default, and our i810 is the old driver and not a symlink.. so maybe all those who've installed alpha3 are using i810 instead of intel :)
[22:29] <tjaalton> hmm, I don't recall that patch.. was if for the driver or server?
[22:29] <tjaalton> oh you mean the fedora patch for the server?
[22:29] <tjaalton> it's been there since early november
[22:30] <tjaalton> the latest (and possibly final) version of it
[22:30] <bryce> right, that fedora patch for the xserver
[22:31] <tjaalton> yeah people noticed that EXA sucks, so turned XAA on, which had it's own issues without the patch
[22:31] <bryce> yeah I've wondered about the i810 thing too...  I'm also wondering if it would be reasonable for us to find a way to push people over to -intel that are using -i810, without actually going so far as to turn -i810 into a symlink
[22:32] <tjaalton> well, patching the server to use intel by default would be enough
[22:32] <tjaalton> then all new installations would use intel, but people could change back to i810
[22:33] <tjaalton> well, gutsy used intel by default
[22:33] <tjaalton> maybe there's still time for upstream to fix the issues with the older chips
[22:33] <bryce> right, I think we've done that.  I'm thinking more about for people upgrading, who have -i810 listed in their xorg.conf
[22:34] <tjaalton> yep, keeping -i810 would let them keep using it
[22:37] <tjaalton> hmm, I don't have mouse on failsafe
[22:37] <bryce> erf
[22:37] <tjaalton> noticed it yesterday on kvm
[22:37] <tjaalton> and now on real hw
[22:37] <bryce> I need to spend some time working on bulletproof X
[22:37] <bryce> I know we have a pile of bugs reported on it, and I've just been procrastinating 
[22:37] <tjaalton> there are some valid bugs about it
[22:37] <bryce> most should be simple
[22:38] <tjaalton> most hardy ones should be fixed already (debconf keys being dropped etc)
[22:43] <tjaalton> hmm, my 965GM used intel by default, nice
[22:46] <tjaalton> bryce: also, it seems that failsafe defaults to vesa on all archs.. sparc needs sunffb and ppc uses fbdev
[22:46] <bryce> oh interesting
[22:46] <bryce> do we have bugs in about that?
[22:46] <tjaalton> there was a bug about mac mini
[22:47] <bryce> I'll add to my todo list
[22:47] <tjaalton> it's on x-x-v-ati now, since the real bug is why it dropped to failsafe :)
[22:47] <bryce> I think after the developer sprint, in Feb I'll try to set aside 3-5 days to focus on bpx
[22:55] <ubotu> New bug: #182416 in linux-restricted-modules-2.6.24 "bugs in fglrx - blank screen - artifacts" [Undecided,New] https://launchpad.net/bugs/182416
[22:57] <ubotu> New bug: #180409 in linux-restricted-modules-2.6.24 "bugs in fglrx - blank screen - artifacts" [Undecided,New] https://launchpad.net/bugs/180409