[01:48] <wgrant> I wonder if we might want to add a button in the recovery mode menu to remove ~/.config/monitors.xml.
[01:54] <james_w> wgrant: good idea
[01:54] <james_w> wgrant: or maybe make it automatic
[01:54] <wgrant> I'm for now just going to add that hint to X/Config/Resolution.
[01:54] <wgrant> james_w: How could it be automatic?
[01:55] <wgrant> g-display-properties also needs to prompt before it sets a res permanently. I wonder where that feature went...
[01:55] <james_w> don't add a button, just rm the file when recovery mode starts up
[01:55] <james_w> yeah, it will be a false positive from time to time, but not that often will it?
[01:56] <james_w> upstream didn't like the prompt so they dropped it, and we never resurrected the patch
[01:56] <wgrant> It would be a bit strange to have simply booting into recovery mode fix the problem.
[01:56] <wgrant> Eww.
[01:56] <wgrant> They didn't like it!?
[01:56] <james_w> apparently
[01:56] <wgrant> If they won't fix it, I will.
[01:56] <james_w> I think there's a bug open on it
[01:56] <james_w> there's certainly a launchpad one
[02:37] <bryce> yeah I like the idea of something to remove monitors.xml
[02:37] <bryce> I'm not sure about removing it automatically vs. a button
[02:38] <wgrant> I've only had to advise a few people on ubuntuforums about it so far.
[02:38] <wgrant> Far more common are the complaints about the removal of displayconfig-gtk.
[02:39] <bryce> heh, people are actually complaining about that?
[02:39] <bryce> I wonder if the number of those complaints outweigh the number that were complaining of its brokenness
[02:39] <wgrant> It is by far the most common complain on ubuntuforums.
[02:39] <wgrant> s/complain/complaint/
[02:40] <wgrant> I'm hoping your X/Config/Resolution will help.
[02:41] <bryce> I hope it does too, and I also hope users will assist in improving the docs
[02:42] <bryce> even better would be if they helped tseliot build on x-kit
[02:43] <bryce> but I can understand many probably lack the time/tech to do that, so at least working on docs would be a good way to help their fellows out
[02:44] <wgrant> We really need more people from somewhere.
[02:46] <bryce> yep
[02:47] <bryce> I used to participate in ubuntuforums myself a while back, but there's only so many info streams I can keep up
[02:47] <bryce> +with
[02:48] <bryce> plus even though I was trying to focus discussions towards constructive testing, it ended up people kept using/hijacking the thread for bug reporting
[02:49] <bryce> wgrant: well the good news is that since I started, we seem to have accumulated +1-2 active ubuntu-x techies per release
[02:50] <bryce> wgrant: I've really appreciated having your involvement lately, it's a big help
[02:50] <wgrant> bryce: I try to track the devel forum to watch things that might crop up, but it gets insane at about T-2weeks.
[02:50] <wgrant> Hah. I've been very little help in Intrepid, but I'll be better for Jaunty.
[02:50] <wgrant> Exams finish in two weeks, then 3.5 months off.
[03:04] <bryce> superm1: we've got EPR's!  :-)  https://bugs.edge.launchpad.net/fglrx/+bugs
[03:04] <bryce> wgrant: kewl :-)
[03:05] <bryce> wgrant: can you point me at some of the displayconfig-gtk complaints?  I skimmed around but didn't spot them
[03:05] <bryce> I did see some issues relating to resolutions
[03:05] <wgrant> Well, there are lots relating to resolutions.
[03:05] <wgrant> Lots and lots and lots.
[03:06] <wgrant> And a fair few about displayconfig-gtk. I'll dig some up soon.
[03:06] <bryce> great thanks
[03:13] <wgrant> http://ubuntuforums.org/showthread.php?t=965866, http://ubuntuforums.org/showthread.php?t=964212, http://ubuntuforums.org/showthread.php?t=966429, http://ubuntuforums.org/showthread.php?t=96426 are some recent ones.
[03:13] <wgrant> There are more in the intrepid forum itself.
[03:17] <wgrant> Is the proper solution to work out what's wrong with their EDID and quirk it? Or are people just going to have to continue to set things manually?
[03:39] <bryce> thanks
[03:40] <bryce> if we can solve it with quirks, that's the ideal
[03:40] <bryce> there will be some cases that are unquirkable though
[03:41] <bryce> and some (hopefully rare) cases where EDID is not available at all, that they'll have to configure manually
[03:42] <wgrant> Of course.
[03:45] <bryce> yep, so all of these sound like invalid EDID situations
[03:48] <wgrant> Is there anything better than get-edid | parse-edid?
[03:48] <bryce> 194760 is the master
[03:49] <bryce> I'd love to know how to close that one
[03:49] <wgrant> bug #194760
[03:49] <ubottu> Launchpad bug 194760 in xorg-server "EDID fail" [High,Triaged] https://launchpad.net/bugs/194760
[03:50] <bryce> ddcprobe is another way to get monitor settings
[03:50] <bryce> xrandr --verbose also prints EDID
[03:50] <wgrant> I couldn't work out how to get xrandr's EDID output into parse-edid.
[03:53] <wgrant> Wait, so that bug is about the monitor not reporting an EDID at all?
[03:53] <wgrant> Ah, no.
[03:53] <wgrant> It's just a bit confusing and long.
[03:54] <bryce> parse-edid works only on the raw binary produced by get-edid.  I don't know if xrandr's edid can be put into it, but it'd require converting it to binary
[03:54] <wgrant> I tried converting it to binary, but it still didn't work. Mrh.
[03:59]  * wgrant needs to learn more about X video stuff eventually.
[05:09] <wgrant> bryce: Why isn't X/Config/* on help.u.c?
[05:18] <bryce> wgrant: I want to keep the X documentation organized in one place
[05:24] <wgrant> bryce: Ah, but user docs are meant to be on help.u.c/community.
[05:25] <bryce> then they should write them
[05:25] <bryce> if I have to write them, then they're going on wiki.ubuntu.com where I can maintain them all together easily
[05:25] <wgrant> Ahh.
[05:25] <wgrant> I see.
[07:29] <tjaalton> hmm so there are two hotels being used during UDS? wiki talks about Wild Palms and the invitation mentions Domain Hotel
[07:36] <wgrant> tjaalton: I've only heard about the latter.
[07:38] <tjaalton> wgrant: maybe it's booked already, and Wild Palms is for non-sponsored guests.. who knows
[07:38] <wgrant> That's quite possible.
[07:39] <wgrant> I wonder when they're going to assign rooms.
[07:45] <wgrant> Is in mildly active Ubuntu X person not going to UDS?
[09:07] <wgrant> bryce: Erm, X has EDID issues.
[09:07] <wgrant> http://ubuntuforums.org/showthread.php?t=969014
[09:07] <wgrant> That EDID looks fine.
[09:07] <wgrant> But X gives a dodgy res.
[09:09] <wgrant> Oh. Hmm.
[09:09] <wgrant> I was looking at the wrong monitor's xrandr output. Damn.
=== mvo_ is now known as mvo
[20:52] <superm1> bryce, wgrant, update to the proposed kernel and that keyrepeating issue affecting dell laptops should be handled
[20:52] <superm1> (there is still something wrong with the OSD, but far less critical)
[20:53] <bryce> superm1: excellent
[20:53] <bryce> superm1: did you see my message about getting bug #'s from intel on the 4 upstreamed bugs?
[20:53] <bryce> er
[20:53] <superm1> s/intel/AMD/
[20:53] <superm1> yeah
[20:53] <bryce> s/intel/amd/
[20:53] <superm1> that's great to hear
[20:53] <superm1> so every public release we'll be able to close out the appropriate ones etc
[20:54] <bryce> yep
[20:54] <superm1> i anticipate there will be a demand for backports too for some of these, and i think the way the driver package is put together now, backports are feasible
[20:54] <superm1> eg into the backports repo
[20:55]  * bryce nods
[20:56] <bryce> unfortunately, I also noticed on at least a couple of these bugs, that the activity on the issue stirred up users to start posting questions about unrelated issues to them
[20:57] <superm1> well i think you run into that everywhere though when too many people subscribe to a bug
[20:58] <superm1> eg bug 59695
[20:58] <ubottu> Launchpad bug 59695 in dell "High frequency of load/unload cycles on some hard disks may shorten lifetime" [Low,Confirmed] https://launchpad.net/bugs/59695
[21:10] <pwnguin> sigh
[21:10] <pwnguin> something x related seems to be causing kernel panics
[21:19] <bryce> superm1: yeah could be