[00:29] <tedg> So, the synaptics driver has this feature where it's supposed to read changes do the xorg.conf file.
[00:30] <tedg> How does that work?  Can all the drivers work that way?  Do they?
[00:30] <tedg> Does xorg.conf get parsed for every driver?
[00:30] <bryce> tjaalton: apparently bdmurray was planning on scheduling a bug hug day for xorg next week, but between our efforts, our untriaged bug count dropped too low.  heh.
[00:32] <bryce> tedg: that might be a Q for mjg
[00:32] <bryce> that may be the hack he did during Gutsy to get the touchpad configuration stuff working nicely
[00:34] <tedg> I was more curious from the perspective of, can I put it on the TODO list to have the wacom driver do it ;)
[00:34] <tedg> I'd really like plug'n'play tablet support.
[00:37] <bryce> tedg: I believe that's in the pipeline, if it's not available already in hardy
[00:48] <tedg> It didn't work for me in Hardy if it's supposed to.
[00:48] <tedg> The only thing I had to do is comment some xorg.conf options though.
[00:48] <tedg> Now it works really well.  I unplugged my mouse.
[01:09] <bryce> ohh, I think I recall seeing a bug about interference between mouse and synaptics
[02:11] <ubotu> New bug: #181914 in xorg (main) "default X configuration assumes wacom hardware" [Undecided,New] https://launchpad.net/bugs/181914
[03:42] <pwnguin> ^ doesn't hardy drop xorg.conf by default?
[05:45] <ubotu> New bug: #181935 in linux-restricted-modules-2.6.24 (restricted) "package xorg-driver-fglrx 8.443.1-1 failed to install/upgrade: intentando sobreescribir `/usr/bin/amdcccle', que está también en el paquete fglrx-amdcccle" [Undecided,New] https://launchpad.net/bugs/181935
[07:15] <ubotu> New bug: #181943 in xorg (main) "[Gutsy] X11 random crash," [Undecided,New] https://launchpad.net/bugs/181943
[07:20] <tjaalton> bryce: hehe
[07:20] <tjaalton> pwnguin: no
[07:26] <tjaalton> oh I love those "random crash" bugs
[07:39] <pwnguin> well my crash is clearly repeatable
[07:55] <bryce> "Hey, I'm having a random crash, can you fix? kthxbye"
[07:56] <pwnguin> well, at least you're paying attention
[07:56] <pwnguin> i havent been able to get any results from filing a bug upstream
[08:00] <tjaalton> pwnguin: ah the xkbLeds bug?
[08:00] <tjaalton> *LED
[08:02] <pwnguin> yea
[08:04] <pwnguin> im not sure how to fix the code, as where it appears is dead simple, but i have no idea where all the code that produced the null pointer is called from
[08:18] <tjaalton> pwnguin: you might have better luck with #xorg-devel :)
[13:39] <tjaalton> mvo: there was this strange upgrade failure where xserver-xorg-core.list got strangely corrupted (with data which looks like from Packages file).. is it something that warrants further investigation?
[13:40] <tjaalton> bug 181530
[13:40] <ubotu> Launchpad bug 181530 in xkbset "package xkbset None [modified: /var/lib/dpkg/info/xkbset.list] failed to install/upgrade: il file con la lista dei file del pacchetto `xserver-xorg-core' contiene un filename vuoto" [Undecided,Incomplete] https://launchpad.net/bugs/181530
[13:40] <ubotu> New bug: #182003 in linux-restricted-modules-2.6.24 (restricted) "nvidia driver unable to load on clean 7.10 install" [Undecided,New] https://launchpad.net/bugs/182003
[13:40] <tjaalton> reinstalling xserver-xorg-core helped there
[13:40] <mvo> tjaalton: if its a isolated thing, then its likely that its some HW issue on the machine, most corruptions on the dpkg level seems to be caused by bad ram 
[13:41] <mvo> tjaalton: (this is the dpkg level)
[13:41] <tjaalton> ok, I'll close it then, and ask the reporter to run memtest
[13:42] <mvo> thanks
[13:42] <tjaalton> thanks
[13:42] <tjaalton> :)
[13:46] <mvo> tjaalton: just to confirm, we will not get a new xserver for hardy that support redirected direct rendering? that means under compiz we have all the nice glx artifacts ?
[13:47] <tjaalton> right
[13:47] <tjaalton> it would touch too many pkaces
[13:47] <mvo> meh, ok. thanks. that means the compiz team needs to think about some stragegy to deal with it
[13:47] <tjaalton> places
[13:48] <tjaalton> I think this was discussed at UDS
[14:43] <Ng> I just upgraded my gutsy laptop to hardy and I've noticed X is using EXA by default now (intel driver, 855gm chipset), but some things feel a lot slower
[14:43] <Ng> scrolling specifically
[14:43] <tjaalton> yep'
[14:43] <tjaalton> see bug 177492 :)
[14:43] <ubotu> Launchpad bug 177492 in xserver-xorg-video-intel "EXA is balls-achingly slow" [High,Confirmed] https://launchpad.net/bugs/177492
[14:45] <Ng> haha, nice subject
[14:46] <tjaalton> so, put 'Option "AccelMethod" "XAA"' to the driver section for now
[14:47] <Ng> now I have to write a driver section! ;)
[14:47] <Ng> but ta. shame that the fix won't be able to be in hardy, but nevermind
[14:47] <Ng> I noticed a comment on that bug about losing video with XAA - do they mean Xv?
[14:48] <Ng> that used to work ok in gutsy with XAA
[14:48] <jcristau> with compiz?
[14:48] <Ng> well ;)
[14:48] <tjaalton> it's the other way around, and only with 965 I think
[14:48] <Ng> actually it did kind of work with compiz, but it was entirely black&white for some reason
[14:48] <Ng> I never really dug into that one
[14:48] <jcristau> (i guess compiz on i855 would probably be balls-achingly slow anyway)
[14:48] <tjaalton> oh, I don't know what keybuk refers to
[14:49] <tjaalton> ah
[14:49] <Ng> jcristau: not so much
[14:49] <Ng> jcristau: sure the thing isn't going to be playing quake3 any time soon, but a sane selection of compiz plugins is actually pretty speedy, mostly because it's only doing 1024x768 I suspect
[14:49] <jcristau> ok, cool
[15:02] <Ng> yeah much faster back in XAA, but Xv is entirely broken now
[15:03] <tjaalton> ok, so it's not just 965 :/
[15:03] <Ng> gstreamer-properties died from a BadAlloc error when I ran the test
[15:04] <tjaalton> nice..
[15:13] <Ng> much as I like xv, I have a tiny screen that I almost never use for video anyway, and I scroll an awful lot
[15:13] <Ng> so scrolling wins ;)
[15:13] <tjaalton> does video work without Xv
[15:13] <tjaalton> ?
[15:17] <Ng> yep
[15:18] <tjaalton> cool
[15:18] <Ng> I'll try and remember to flip back to EXA quickly to make sure that video works there too
[17:35] <tjaalton> right, at least cirrus doesn't start in the new world order
[17:35] <tjaalton> "Mode pool is empty"
[17:45] <ubotu> New bug: #182062 in xmodmap "IBM Thinkpad T61 key slash/question doenst works in Gutsy" [Undecided,New] https://launchpad.net/bugs/182062
[17:49] <tjaalton> it needs modelines, which seems a bit odd
[17:55] <tjaalton> modelines, defaultdepth and Modes, duh
[21:06] <pwnguin> well crap, xorg-devel is like half ubuntu devs
[21:10] <bryce> heh
[21:10] <bryce> you say that like it's a bad thing...?  ;-)
[21:11] <pwnguin> also bryce, i read your blog
[21:12] <pwnguin> on the subject of library versions and fixes, why not use branches?
[21:12] <pwnguin> you've already migrated to bzr
[21:12] <pwnguin> for inkscape
[21:13] <bryce> no we still use svn
[21:13] <bryce> we only migrated the bug tracker
[21:13] <pwnguin> oh
[21:13] <bryce> we have used branches in the past, but find they grow stale and don't get adequate testing.
[21:13] <pwnguin> well, it still has "very cheap branching"
[21:13] <pwnguin> ;)
[21:14] <pwnguin> well, that'd sorta be the point
[21:14] <bryce> to not get adequate testing?
[21:14] <pwnguin> dev branch updates the libraries
[21:14] <pwnguin> the other branches would attempt to pull in fixes without touching version dependencies
[21:15] <pwnguin> the other branches would naturally die off as people prefer to simply update lib dependencies
[21:17] <pwnguin> it'd be easier to do with bazaar, if it lets you track distro patches
[21:20] <bryce> could be
[21:20] <bryce> I suspect it's more likely we'd move to git than bzr, but currently it sounds like most developers favor staying with the status quo,
[21:21] <bryce> we've set up svn->bzr and svn->git interfaces, so those passionate about git and bzr are fairly happy, and those who wish to stick with svn are happy
[21:21] <bryce> I would expect changing at this point would result in some becoming unhappy, and few becoming more happy than they already are
[21:22] <monkee_of_evil> Allo
[21:23] <monkee_of_evil> Has anyone had any luck here getting a triple monitor setup working with Ubuntu?
[21:23] <bryce> I'd like to see us move to bzr, but don't really have a strong preference; I've not gathered sufficient convincing arguments to make me want to push for it yet
[21:23] <bryce> monkee_of_evil: I have had some limited successes
[21:24] <monkee_of_evil> I've got these 2 widescreen acer monitors and a single Sceptre monitor ( none-widescreen )
[21:24] <pwnguin> i suppose it just makes more sense in the general perspective; if you have bzr/git and binary distros using your stuff -- you can keep lib version ifdefs out of the tree
[21:24] <bryce> monkee_of_evil: If you're using Feisty or earlier Ubuntu, you can use Xinerama to do it
[21:24] <monkee_of_evil> I'm on Gutsy
[21:24] <bryce> monkee_of_evil: however from Gutsy forward, most drivers have switched to xrandr, which does not handle multiple graphics cards so well
[21:24] <monkee_of_evil> damn
[21:24] <bryce> it won't be 'til Hardy+1 that the issue is straightened out
[21:24] <pwnguin> i havent really used either bzr or git
[21:24] <tjaalton> well, ati and intel
[21:25] <tjaalton> and experimental mga
[21:25] <pwnguin> matrox?
[21:25] <tjaalton> rigt
[21:25] <tjaalton> +h
[21:25] <bryce> tjaalton: and nv since g80
[21:25] <tjaalton> yep
[21:25] <monkee_of_evil> Yeah... I've got an older ATI dualy & an onboard intel chipset
[21:25] <tjaalton> but nvidia binary can do silly stuff
[21:25] <bryce> monkee_of_evil: I have gotten triple screen working with non-merged displays
[21:25] <bryce> so like you have :0.0 and :0.1
[21:26] <bryce> that was on -ati, and I found it too buggy to actually use (mouse would get stuck, etc.)
[21:26] <monkee_of_evil> hmm
[21:26] <bryce> that was on Gutsy with -ati 195 iirc; it might have gotten better since
[21:26] <tjaalton> ati upstream supports zaphod mode again
[21:26] <monkee_of_evil> It will automatically do it's thing and clone my desktop to the two widescreens in Gutsy
[21:27] <tjaalton> so it should work on current hardy
[21:27] <monkee_of_evil> What sucks for me is that I've got that RV700 or some crap for my ATI card, so the official binaries don't work
[21:27] <bryce> http://bryceharrington.org/Photos/X/
[21:29] <monkee_of_evil> I tried configuring X to get it going and the only thing i can make it do is show a black screen for 2/3 of the screen on my center monitor ( the one plugged into the intel card ) then for the rest of the screen you see these multi-color stripes
[21:29] <monkee_of_evil> and you can see this blurr where the mouse moves
[21:29] <monkee_of_evil> then on the wide screens both of them are blank except for the top left where it shows the part numbers of the monitor
[21:29] <monkee_of_evil> It's the weirdest thing
[21:30] <monkee_of_evil> can't wait for better monitor support
[21:31] <monkee_of_evil> Bryce: nice screenshots
[21:31] <monkee_of_evil> err
[21:31] <monkee_of_evil> pictures actually
[21:31] <monkee_of_evil> but w/e
[21:32] <bryce> w/e ?
[21:33] <pwnguin> w/e is often "whatever"
[21:33]  * bryce shrugs
[21:33] <monkee_of_evil> pwnguin got it
[21:33] <pwnguin> more importantly, that's gnome+konsole
[21:34] <pwnguin> and.. xmms?
[21:36] <bryce> pwnguin: if you're trying to give me a hard time, won't work ;-)
[21:37] <monkee_of_evil> I like xmms
[21:37] <pwnguin> i think if you try harder, you could put in an enlightenment app too ;)
[21:37] <monkee_of_evil> Fluxbox ftw
[21:37] <monkee_of_evil> :)
[21:38] <pwnguin> xmms is like the worst of all worlds. terrible UI that mimics winamp. horrible playlist UI, weak playlist tools...
[21:38] <tjaalton> and yet something that actually worked all these years :)
[21:39] <pwnguin> thats about all it has =(
[21:39] <tjaalton> heh
[21:39] <bryce> if you must know, I used to use KDE, and wrote scripts to automate konsole placement using dcop.  I've since rewritten the code for gnome-term, but those photos were taken before that.
[21:40] <pwnguin> interesting. is the placemnt script a matter of which screen?
[21:40] <bryce> I've tried both KDE and GNOME music apps and generally find them inadequate
[21:40] <monkee_of_evil> yeah.. I fucking hate Rythmbox
[21:40] <monkee_of_evil> Listen isn't much better
[21:40] <bryce> I put in a bunch of bugs on rhythmbox before giving up on it
[21:41] <monkee_of_evil> Too bad foobar doesn't run natively
[21:41] <monkee_of_evil> although it runs decently under wine
[21:41] <tjaalton> I used KDE in -98 when I installed linux (SuSE 5.3) for the first time
[21:42] <bryce> pwnguin: no, my set up has a virtual screen so I just specify the x,y coordinates that'd put them on the right screen
[21:42] <bryce> it's pretty trial-and-error, and different for KDE and GNOME
[21:42] <pwnguin> anyways, i didnt mean to start an involved flamewar, just poking some fun ;)
[21:42] <bryce> :-P
[21:43] <tjaalton> I use rb happily at work, but it's far from perfect
[21:43] <bryce> I'm just irritable due to all the UME stuff at the moment, don't mind me
[21:43] <tjaalton> hehe
[21:43] <pwnguin> tjaalton: i wish it would let me choose a different playlist to default to on startup
[21:43] <pwnguin> i filed a wishlist bug in LP and someone appears to have run with it, we'll see where that goes
[21:44] <tjaalton> ah, I just plug in my iPod and let it play random
[21:44] <pwnguin> i dont own one of those
[21:44] <pwnguin> but its nice to be able to filter by rating etc
[21:44] <tjaalton> I got it just because it's the only brand that has any sort of gadgets for cars
[21:45] <tjaalton> http://www.last.fm/user/tepsipakki
[21:45] <pwnguin> i actually used rhythmbox to come up with a playlist for my crappy car stereo to put on CD
[21:45] <pwnguin> 700 megs of mp3s at bitrate 300 or less sorted by rating
[21:46] <tjaalton> now I use banshee to sync the iPod, and the next version should finally fix the UI so I can choose by genre
[22:21] <bryce> dah, LP is going offline
[22:24] <jcristau> tjaalton: will you report the bug about i810preinit not setting depth to 16 to bugzilla, or shall i?
[22:26] <tjaalton> jcristau: you can do it, it was your idea anyway :)
[22:27] <tjaalton> jbarnes knows about it already though
[22:27] <jcristau> yeah i've read that
[22:28] <tjaalton> right, he'd prefer to have the patch on b.fd.o
[22:28] <jcristau> a bz report is safer than a mention on irc :)
[22:28] <tjaalton> of course, and you can't track bugs outside bz
[22:28] <tjaalton> er, patches
[22:28] <tjaalton> or both actually
[22:29] <tjaalton> ffs, launchpad maintenance break
[22:40] <jcristau> tjaalton: what's your bz email again?
[22:40] <tjaalton> tjaalton+freedeskto at cc.hut.fi
[22:40] <tjaalton> freedesktoP
[22:43] <jcristau> thx
[22:44] <jcristau> there. #14032
[22:44] <tjaalton> thanks
[22:44] <jcristau> np
[22:45] <tjaalton> so you tried it as well?
[22:45] <jcristau> didn't have time to test the patch yet, no
[22:45] <tjaalton> well, it works
[22:46] <jcristau> but i don't see why it wouldn't work when X -depth 16 does
[22:47] <jcristau> pretty busy at work this week, plus my debian time was taken by other stuff...
[22:48] <tjaalton> don't worry, a couple of guys already proved it working :)
[22:49] <jcristau> cool
[22:56] <tjaalton> woohoo, at least one bug fixed by switching to openchrome, bug 180841
[22:57] <ubotu> Launchpad bug 180841 in mesa "glXDestroyContext causes segmentation fault with Via Unichrome graphics" [Undecided,Incomplete] https://launchpad.net/bugs/180841
[23:08] <bryce> nice
[23:09] <tjaalton> although it was quite unclear which version he was using before, and I think via/openchrome both share the same mesa driver
[23:59] <ubotu> New bug: #182100 in linux-restricted-modules-2.6.24 (restricted) "ATI Catalyst 7.12 conflict with Screen Resolution" [Undecided,Incomplete] https://launchpad.net/bugs/182100
[23:59] <tjaalton> sigh