[08:07] bryce: exactly my point. it's just too easy to let xorg get filled up [08:07] tjaalton: yep I agree [08:07] tjaalton: today I've been really taking advantage of my busted up jaunty desktop [08:08] "advantage" :) [08:08] I had this weird mouse cursor flickering in firefox, found a patch for it that solved it, and uploaded :-) [08:08] oh taht [08:08] that [08:08] so you didn't use git then, because it has the tip of 1.6 branch ;) [08:09] which fails to build a source package because of change xquartz stuff [08:09] changeD [08:09] nah, I looked at the real patch but it looked pretty involved, so just put in the much simpler workaround patch for the time being [08:09] don't think 1.6-branch has it yet [08:10] yeah, doesn't sound like it. So when it does, we can drop this patch. [08:10] just wondering what to do in git [08:11] the workaround patch has been working perfectly so far for me [08:12] also sorted out a bug where right clicking on urls in gnome apps wasn't loading right in firefox [08:12] that turned out to be a glib bug. I made a workaround patch but didn't root-cause it [08:12] ok, has worked for me [08:13] it seems to have something to do with gvfs [08:13] maybe something isn't quite kosher with my setup [08:14] anyway, whatever, another annoyance eliminated :-) [08:21] good :) [08:39] afk, to the skating rink -> [08:40] * bryce chuckles [08:40] sounds fun [10:05] yep, it was [10:05] it's across the street, so easy to go to :) === seb128_ is now known as seb128 [11:04] bryce: ati dithering stuff regression on intrepid, bug 314326 [11:04] Launchpad bug 314326 in xserver-xorg-video-ati "new radeon and ati libraries dont work with my X1300 " [Undecided,New] https://launchpad.net/bugs/314326 [16:09] bryce, is AMD aware of any ABI problems that will be happening for jaunty so that they have time to plan appropriately? [17:03] tseliot: could you look to bug #314406? it's g-s-d crashing in jaunty due to your change [17:03] Launchpad bug 314406 in gnome-desktop "xrandr plugin of g-s-d crashes on startup" [Medium,Confirmed] https://launchpad.net/bugs/314406 [17:03] * tseliot has a look at the report [17:06] seb128: ok, I think I know how to fix it. When do you need the fix? [17:07] tseliot: no hurry there is not so many jaunty users yet [17:07] seb128: ok, I'll add it to my todo list. Thanks for reporting [19:42] superm1: AIUI yes they are [22:14] tjaalton: I've modified the colorization and accounting on http://bryceharrington.org/X/PkgList/versions_current.html a bit, to better distinguish better when we're in sync with debian, but they're behind upstream (since there's so many packages in that state currently) [22:15] (gets rid of a lot of red for us :-) ) [22:18] Is it intentional that xft 2.1.13-2 was synced rather than merged into Jaunty? The sync dropped two patches that I believe are still needed (bug 305399). [22:18] Launchpad bug 305399 in xft "xft 2.1.13-2 sync dropped libXft-2.1.10-lcd-filter-3.patch" [Undecided,New] https://launchpad.net/bugs/305399 [22:24] andersk: thanks, I'll upload [22:29] bryce: so lime means that we are in sync with debian but not upstream, and blue means we are not in sync? [22:30] with either [22:31] (still tinkering with colors a bit) [22:32] tjaalton: correct [22:32] I'm adding another color to distinguish between needing merges vs. syncs to experimental [22:33] also I corrected needs-merge vs. needs-sync; for some reason I'd not gotten the logic right for ubuntu packages [22:34] while I'm at it, any other change requests for this page? [22:35] nothing I can think of [22:39] actually, blue means we're not in sync with experimental [22:39] dark blue means we need to merge with experimental, light blue means we just need to sync [22:39] red/orange means we need a merge/sync with unstable === federico1 is now known as f_away [22:57] yeah, didn't notice it was explained at the bottom