[00:47] <ubotu> New bug: #182284 in xserver-xorg-video-intel (main) "no direct rendering after upgrade to hardy" [Undecided,New] https://launchpad.net/bugs/182284
[00:49] <ubotu> New bug: #187281 in xserver-xorg-video-ati (main) "Graphic problems with ATI" [Undecided,New] https://launchpad.net/bugs/187281
[04:02] <ubotu> New bug: #189147 in xorg (main) "X display freezes, slowly fades to black (video included)" [Undecided,New] https://launchpad.net/bugs/189147
[06:26] <ubotu> New bug: #189167 in mesa (main) "Missing glClipPlane support in r300" [Undecided,New] https://launchpad.net/bugs/189167
[08:53] <ubotu> New bug: #120619 in xorg (main) "[Gutsy] invalid resolution detected resulting in BIG fonts on i915" [Undecided,New] https://launchpad.net/bugs/120619
[09:00] <Company> hrm, everybody asleep here, too
[09:00] <Company> i'm wondering who to poke about https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/147846
[09:00] <ubotu> Launchpad bug 147846 in xserver-xorg-video-ati "resolution out of sync with version 2:1.3.0.0.dfsg-12ubuntu8" [High,Incomplete] 
[09:33] <tjaalton> Company: do you have a radeon or intel?
[09:38] <Company> tjaalton: radeon
[09:39] <Company> tjaalton: (last reply to that bug is mine)
[09:39] <tjaalton> yes I noticed
[09:40] <tjaalton> try the driver from http://wiki.ubuntu.com/XorgOnTheEdge
[09:40] <Company> radeonhd or ati?
[09:40] <tjaalton> ati
[09:42] <Company> brb (hopefully ;))
[09:45] <Company> logging out and back in should be enough to restart X, right?
[09:45] <tjaalton> perhaps
[09:46] <tjaalton> I'm not sure what the gdm default is
[09:46] <Company> i got to see the console in between
[09:46] <tjaalton> I reckon it didn't help?
[09:46] <Company> nope
[09:47] <Company> still the same issue: garbled screen andmanually having to xrandr without seeing a lot
[09:47] <tjaalton> ok, please open a new bug and attach your logfile and config.
[09:47] <Company> half of that is easy - i have no config :)
[09:48] <tjaalton> ok
[09:50] <Company> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/189198
[09:50] <ubotu> Launchpad bug 189198 in xserver-xorg-video-ati "r100 video comes up garbled" [Undecided,New] 
[10:00] <tjaalton> Company: umm, on the other bug you said that resolutions such as 1920x1200 worked right? I'm not sure how 446Xpro is able to do that..
[10:00] <Company> tjaalton: i can definitely see it
[10:00] <tjaalton> it's not a widescreen monitor..
[10:01] <Company> i know
[10:01] <ubotu> New bug: #189198 in xserver-xorg-video-ati (main) "r100 video comes up garbled" [Undecided,New] https://launchpad.net/bugs/189198
[10:01] <Company> it looks pretty stretched and is flickering, but the image is vivible
[10:01] <tjaalton> the log shows that it's using 16x12, and you listed that as working?
[10:03] <Company> it's using 1600x1024, no?
[10:04] <Company> i was assuming that it does that, because the other modes work when i xrandr to them
[10:05] <tjaalton> you listed 1600x1024 as working too
[10:06] <Company> wait, i did?
[10:06] <tjaalton> WORKS: 1920x1200, 1600x1200, 1600x1024...
[10:06] <Company> i messed that up when copy/pasting, i'm sorry
[10:06] <tjaalton> hmm, indeed it is trying to use 16x10
[10:07] <Company> yep, 1680x1050 works
[10:07] <Company> looks ugly, but works
[10:07] <tjaalton> what if you generate the config? 'dpkg-reconfigure xserver-xorg'
[10:08] <tjaalton> I meant it's using 1600x1024
[10:08] <Company> right
[10:08] <Company> i was just checking what i'd written in the bug
[10:08] <tjaalton> ah
[10:09] <Company> can i dpkg-reconfigure while X is running?
[10:09] <tjaalton> yes
[10:09] <tjaalton> it doesn't probe or anything
[10:12] <Company> hrm, the xorg.conf doesn't contain anything important
[10:12] <Company> just "configured device" for everything and a keyboard layout
[10:12] <tjaalton> right
[10:12] <tjaalton> that's enough
[10:13] <Company> alright
[10:13] <tjaalton> ..for now
[10:13]  * Company tries
[10:15] <Company> same problem
[10:16] <tjaalton> ok, so you can force the resolution using these instructions: http://wiki.debian.org/XStrikeForce/HowToRandR12
[10:16] <tjaalton> "forcind a preferred mode"
[10:18] <Company> yeah, that was pretty much what i was doing - i had set a preferred resolution on gnome login which caused an xrandr to 1280x1024
[10:18] <tjaalton> it would be cool if you could report this upstream
[10:19] <Company> but the new gnome stopped auto-xrandr'ing
[10:21] <Company> what's the preferred irc channel for poking upstream people?
[10:21] <tjaalton> #xorg-devel
[10:22] <tjaalton> ask agd5f (some US timezone though..)
[10:23] <Company> will do
[10:24] <tjaalton> hmm, actually he's real name is alex deucher, so maybe he's German after all :)
[10:24] <Company> he works for ati now, so he probably is us-based nonetheless ;)
[10:25] <tjaalton> true
[10:27] <Company> gutsy shipped xorg 1.4?
[10:28] <Company> hrm shouldn't matter, because it was caused by that patch removal
[10:28] <tjaalton> nope, 1.3
[10:29] <tjaalton> yes, that patch basically forced the setting, which is equivalent to the PreferredMode
[10:36] <Company> freedesktop.org 14383
[10:38] <tjaalton> excellent
[10:40] <tjaalton> added a comment about the driver version
[10:41] <Company> i'll try poking agd5f tonight or tomorrow
[10:42] <tjaalton> ok, cool
=== seb128_ is now known as seb128
=== seb128_ is now known as seb128
=== imbrandon is now known as imbrandon_
=== mvo__ is now known as mvo
[16:40] <Q-FUNK> http://people.ubuntu.com/~bryce/Uploads/xorg-server_1.4.1~git20080118-1ubuntu3_source.changes
[16:40] <Q-FUNK> is there a source tarball for this?
[16:40] <Q-FUNK> I was gonna add bartman's vcons patch and upload to my PPA, but no source tarball found.
[16:41] <tjaalton> Q-FUNK: I'm about to upload a new merged version
[16:41] <tjaalton> with your patches
[16:41] <Q-FUNK> oh
[16:41] <tjaalton> that version was never uploaded
[16:42] <Q-FUNK> including the vcons patch attached to 180742 ?
[16:43] <Q-FUNK> there's a total of 3 patches against x86emu from Bart.  2 are attached to 140051 and 1 to 180742.
[16:43] <tjaalton> that's not included, the first two are
[16:43] <Q-FUNK> ok
[16:43] <Q-FUNK> can you check that third one, before you upload?
[16:45] <tjaalton> better to test that separately?
[16:46] <Q-FUNK> hmm ok
[16:46] <Q-FUNK> I guess I'll make my PPA packages from your current upload.
[16:46] <Q-FUNK> which version is it?
[16:47] <tjaalton> the one that'll hit the archive in 10min :)
[16:47] <tjaalton> 2:1.4.1~git20080131-1ubuntu1
[16:49] <Q-FUNK> ok :)
[16:50] <Q-FUNK> how often is the PPA build queue processed, again?
[16:50] <tjaalton> every 30min/1h or so
[16:50] <tjaalton> dunno
[16:50] <Q-FUNK> source was just accepted by PPA, but no binaries yet
[16:51] <Q-FUNK> ah ok
[17:13] <tjaalton> bryce: ok, xorg-server uploaded with those patches
[17:14] <tjaalton> now home ->
[17:35] <bryce> thanks
[17:35] <Q-FUNK> tjaalton: kiitos tästä.
[17:35] <Q-FUNK> one worry less for Hardy
[17:52] <tjaalton> if it doesn't break anything :)
[17:55] <tjaalton> bryce: maybe we should take a look at the fedora displayconf tool if dc-g isn't going to cut it anymore? looks like it has accumulated ~150 bugs so far
[17:57] <bdmurray> bryce: Is there a master bug for touchpad scrolling?
[17:58] <tjaalton> yep
[17:58] <tjaalton> bdmurray: ^^ :)
[17:59] <tjaalton> bug 173411
[17:59] <ubotu> Launchpad bug 173411 in xorg "[Hardy][Regression] Touchpad vertical scroll does not work" [Medium,Confirmed] https://launchpad.net/bugs/173411
[18:00] <bdmurray> tjaalton: thanks!
[18:07] <bryce> tjaalton: really?  I looked at it a couple weeks ago but wasn't that impressed
[18:11] <ubotu> New bug: #186899 in ubuntu "Scrolbar of my hp dv9646 laptop mouse doesn't work on Hardy (dup-of: 173411)" [Undecided,Triaged] https://launchpad.net/bugs/186899
[18:13] <tjaalton> bryce: oh ok, what's it called? I'll dig it up to convince myself that it sucks :)
[18:13] <bryce> system-config-display iirc
[18:14] <bryce> here are some (early) mockups of what they're working on to gain xrandr support - http://www.gnome.org/~clarkbw/designs/monitor-resolution-settings/
[18:15] <tjaalton> yeah, that's the one
[18:16] <bryce> I think the layout that glatzor and mpt put together is a bit more usable.  I do want to have a graphical screen layout tool some day, but I've seen other prototypes I like better
[18:16] <tjaalton> ok I won't spend any time on that right now
[18:16] <bryce> so far, grandr's layout tools is the most interesting, however it takes up a lot of space
[18:16] <tjaalton> but we still need a tool which touches xorg.conf, imho
[18:17] <bryce> http://fedoraproject.org/wiki/Features/RandrSupport
[18:17] <bryce> here's a screenshot:  http://www.redhat.com/magazine/014dec05/features/multihead/
[18:18] <bryce> yes I agree we need something which can manipulate xorg.conf, and I'm a bit uncertain about what to do there
[18:18] <bryce> there's three use cases I see
[18:18] <bryce> 1.  bulletproof-x mode (a xrandr gui presumably won't cut it here)
[18:19] <bryce> 2.  altering the Virtual settings to allow different layouts (but maybe this could simply be a script)
[18:19] <bryce> 3.  general xorg.conf customization
[18:20] <bryce> I don't know though --- given my experience seeing how hard it's been for dcg to chase xorg.conf as it's format evolves, this seems like a really hard problem, and these three use cases don't represent as huge of an amount to gain, assuming people will be able to do more using xrandr now
[18:21] <jcristau> pyxf86config sounds nicer than shell to manipulate xorg.conf
[18:39] <tjaalton> bryce: speaking of 1., do we want to get a recent -ati snapshot in? I'm tired of those r5xx bugs which fail to load vesa :)
[18:39] <bryce> tjaalton: yeah probably a good idea; I've sort of lost track of where -ati is at since our last release
[18:40] <tjaalton> bryce: deep in the snapshot-land :)
[18:40] <bryce> hrm
[18:40] <tjaalton> or -jungle
[18:40] <tjaalton> jcristau: I'll take a look at pyxf86config
[18:41] <tjaalton> bryce: they do support accelerated 2D for r5xx, and maybe for r6xx too
[18:42] <bryce> tjaalton: well, I'd like to avoid the situation we were in last time where we were putting out new -ati's right up until freeze...  the vesa issue is minor compared with some bugs we could risk unearthign
[18:42] <bryce> tr/gn/ng/
[18:42] <tjaalton> currently r5xx-> can't get X up because of that, so it's not that minor :)
[18:42] <bryce> tjaalton: maybe ask alex about any release plans for the month?
[18:43] <tjaalton> yeah, good point
[18:45] <tjaalton> a coworker has a Thinkpad T-series with a recent ati card on it, so I could try some dailies on it every now and then
[18:45] <bryce> yes that's a really good idea
[18:45] <bryce> I think ScislaC may also be open to doing some testing, although usually he focuses on fglrx
[18:48] <tjaalton> I'd like to personally see a machine failing to boot a livecd, otherwise it's much harder to fix anything
[18:49] <bryce> I think you might be the only person wishing for that ;-)
[18:49] <tjaalton> hehe :)
[19:31] <ubotu> New bug: #189343 in linux-restricted-modules-2.6.24 (restricted) "DRI doesn't work with fglrx 8.01" [Undecided,New] https://launchpad.net/bugs/189343
[20:32] <ubotu> New bug: #187588 in xorg (main) "[hardy] wrong screen resolution on laptop HP nw8440" [Undecided,Incomplete] https://launchpad.net/bugs/187588
[21:37] <bryce> tjaalton: I started that page on hardy driver status I mentioned the other day - https://wiki.ubuntu.com/X/Drivers
[21:38] <bryce> so far just -intel; going to do -fglrx after lunch
[21:38] <bryce> if you could, please review it and correct any inaccuracies - this is mostly taken from feedback from your testing, so I may have made mistakes in capturing it correctly
[21:40] <tjaalton> bryce: ok, I'll have a look
[21:43] <tjaalton> bryce: yep, looks good
[22:07] <bryce> great
=== seb128_ is now known as seb128
[22:11] <bryce> on to -fglrx
[22:12] <tjaalton> for some reason it seems to _require_ forcing 24bit mode on...
[22:14] <bryce> huh
[22:14] <bryce> what other issues?  I owe AMD a top 5 bug list, so if you have issues in mind I'll collect 'em
[22:15] <tjaalton> DRI doesn't work for everyone etc
[22:16] <tjaalton> look at the l-r-m-2.6.24 bug list
[22:18] <bryce> ok
[22:27] <bryce> tjaalton: there doesn't seem to be that many fglrx errors in the lrm-2.6.24 bug list
[22:27] <bryce> about a dozen
[22:29] <tjaalton> right, but even more puzzling ones :)
[22:30] <tjaalton> but the fact is that not that many get past the broken-X phase
[22:30] <tjaalton> I guess..
[22:30] <tjaalton> the bug list for 2.6.22 is more impressive
[22:38] <bryce> could be
[22:38] <bryce> will many of the 2.6.22 bugs still be relevant though?
[22:42] <tjaalton> some of them will
[22:42] <tjaalton> don't know the percentage, but some of them are already running the latest driver(s)
[22:42] <tjaalton> those could be moved to .24
[23:13] <bryce> heya tormod
[23:14] <tormod> hi bryce
[23:15] <bryce> how things going tormod?
[23:17] <tormod> fine thanks. trying to not fall sick, flu all over Europe it seems.
[23:17] <bryce> erf
[23:17] <tormod> did you see my e-mail reply with another small patch?
[23:17] <bryce> yes
[23:17] <bryce> I'll add it in now
[23:18] <tormod> you can also remove the '/.git.*/' from -i I think, just -i removes all git/svn/etc
[23:20] <bryce> ok done and pushed :-)
[23:20] <tormod> my plans (some time) would be to rearrange the script in modules so it can be used as a shell library if needed.
[23:21]  * bryce nods
[23:21] <tormod> for instance build binaries, then change a few things for backports, build again (without downloading from git every time)
[23:22] <bryce> I got completely sidetracked by ubuntu-mobile stuff there around the holidays so haven't had time to work on the driver builder infrastructure more, but if/when I do, it'd be helpful to have the script modularized
[23:22] <bryce> I did take a shot at adding support for mesa before the holidays, but it never worked
[23:23] <bryce> I had the changes queued up in my tree (thus my procrastination merging more changes), but I think mesa just may be too complicated for it, so I just tossed that work for now.
[23:25] <tormod> is the ubuntu mesa maintained in git?
[23:28] <bryce> no
[23:29] <bryce> just xorg and xorg-server are in git for ubuntu so far
[23:29] <tormod> I guess it would be the next candidate.
[23:30] <bryce> possibly; although it's not a package we tend to do a lot of work on - I think we mostly just sync to debian
[23:30] <tormod> that's the tendency for all xorg*, luckily
[23:31] <bryce> right.  xorg and xserver are the two main pieces where we have a significant amount of non-syncable / ubuntu-specific stuff
[23:32] <bryce> I've thought a bit that maybe one or two of the drivers would be next on the list, but typically what changes we make to drivers gets taken upstream swiftly so we rarely have more than a couple patches against them at a time
[23:33] <bryce> tormod: hey did you see we got 100% caught up the other day on New bug triage for the major xorg bits? :-)
[23:33] <bryce> (well major aside from the binary drivers)
[23:34] <tormod> wow that's great
[23:34] <bryce> tormod: http://people.ubuntu.com/~bryce/Plots/
[23:35] <bryce> things have crept up a bit since then but not much ;-)
[23:35] <tormod> looks good :)
[23:36] <tormod> and displayconfig-gtk needs some love... any new plans for it?
[23:36] <bryce> indeed; I've been working on a replacement for it the last couple days
[23:36] <tormod> link?
[23:36] <bryce> http://bryceharrington.org/files/screenrez_6.png
[23:37] <tormod> xrandr-aware I hope?
[23:37] <bryce> right
[23:37] <bryce> my code branch is at https://code.launchpad.net/gnome-control-center
[23:38] <bryce> it won't edit xorg.conf though, so we may still need a solution for that.
[23:38] <tormod> btw, are we gonna update -ati soon, or wait for Debian (or for 6.8...)?
[23:38] <bryce> tjaalton and I were just talking about that earlier
[23:39] <tormod> the support for X1?00 cards would obsolete many vesa bugs...
[23:39] <bryce> it would be nice to not get stuck in a situation like last time where we were pushing new -ati's up until the last minute before release
[23:39] <bryce> right
[23:39] <bryce> I think tjaalton is going to check with alex about release plans in the near future
[23:40] <bryce> tormod, have you tested against newish -ati snapshots?  How is it doing?
[23:40] <tormod> well it just got better and better :)
[23:40] <bryce> heh
[23:41] <tormod> works well, and I ask people to test it whenever I can in bug reports.
[23:42] <tormod> I am a little afraid Alex doesn't have a release plan, as in planning wrt time
[23:42] <ubotu> New bug: #189415 in xorg (main) "[Hardy] X serveur restart randomly with nvidia propriotary driver" [Undecided,Incomplete] https://launchpad.net/bugs/189415
[23:43] <bryce> hmm
[23:43] <bryce> since Hardy is an LTS release, it would be a bit uncomfortable shipping an -ati snapshot...
[23:44] <tormod> it seemed to settle and I was waiting for a release, then he merges atombios, same again, then he adds something else...
[23:45] <bryce> have you suggested to him that it would be good to put out a release before merging more stuff?
[23:45] <tormod> it would be better than 6.6.3 I guess ;)
[23:45] <jcristau> the ati driver tends to have never-ending release candidate series these days
[23:46] <tormod> hmm no I haven't. I am maybe not the one to tell him. jcristau?
[23:50] <jcristau> you could just pick whatever goes into F9 :)
[23:51] <tormod> true enough