[00:29] So, the synaptics driver has this feature where it's supposed to read changes do the xorg.conf file. [00:30] How does that work? Can all the drivers work that way? Do they? [00:30] Does xorg.conf get parsed for every driver? [00:30] 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] tedg: that might be a Q for mjg [00:32] that may be the hack he did during Gutsy to get the touchpad configuration stuff working nicely [00:34] 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] I'd really like plug'n'play tablet support. [00:37] tedg: I believe that's in the pipeline, if it's not available already in hardy [00:48] It didn't work for me in Hardy if it's supposed to. [00:48] The only thing I had to do is comment some xorg.conf options though. [00:48] Now it works really well. I unplugged my mouse. [01:09] ohh, I think I recall seeing a bug about interference between mouse and synaptics [02:11] New bug: #181914 in xorg (main) "default X configuration assumes wacom hardware" [Undecided,New] https://launchpad.net/bugs/181914 [03:42] ^ doesn't hardy drop xorg.conf by default? [05:45] 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] New bug: #181943 in xorg (main) "[Gutsy] X11 random crash," [Undecided,New] https://launchpad.net/bugs/181943 [07:20] bryce: hehe [07:20] pwnguin: no [07:26] oh I love those "random crash" bugs [07:39] well my crash is clearly repeatable [07:55] "Hey, I'm having a random crash, can you fix? kthxbye" [07:56] well, at least you're paying attention [07:56] i havent been able to get any results from filing a bug upstream [08:00] pwnguin: ah the xkbLeds bug? [08:00] *LED [08:02] yea [08:04] 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] pwnguin: you might have better luck with #xorg-devel :) === seb128_ is now known as seb128 [13:39] 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] bug 181530 [13:40] 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] 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] reinstalling xserver-xorg-core helped there [13:40] 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] tjaalton: (this is the dpkg level) [13:41] ok, I'll close it then, and ask the reporter to run memtest [13:42] thanks [13:42] thanks [13:42] :) [13:46] 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] right [13:47] it would touch too many pkaces [13:47] meh, ok. thanks. that means the compiz team needs to think about some stragegy to deal with it [13:47] places [13:48] I think this was discussed at UDS [14:43] 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] scrolling specifically [14:43] yep' [14:43] see bug 177492 :) [14:43] Launchpad bug 177492 in xserver-xorg-video-intel "EXA is balls-achingly slow" [High,Confirmed] https://launchpad.net/bugs/177492 [14:45] haha, nice subject [14:46] so, put 'Option "AccelMethod" "XAA"' to the driver section for now [14:47] now I have to write a driver section! ;) [14:47] but ta. shame that the fix won't be able to be in hardy, but nevermind [14:47] I noticed a comment on that bug about losing video with XAA - do they mean Xv? [14:48] that used to work ok in gutsy with XAA [14:48] with compiz? [14:48] well ;) [14:48] it's the other way around, and only with 965 I think [14:48] actually it did kind of work with compiz, but it was entirely black&white for some reason [14:48] I never really dug into that one [14:48] (i guess compiz on i855 would probably be balls-achingly slow anyway) [14:48] oh, I don't know what keybuk refers to [14:49] ah [14:49] jcristau: not so much [14:49] 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] ok, cool [15:02] yeah much faster back in XAA, but Xv is entirely broken now [15:03] ok, so it's not just 965 :/ [15:03] gstreamer-properties died from a BadAlloc error when I ran the test [15:04] nice.. [15:13] 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] so scrolling wins ;) [15:13] does video work without Xv [15:13] ? [15:17] yep [15:18] cool [15:18] I'll try and remember to flip back to EXA quickly to make sure that video works there too [17:35] right, at least cirrus doesn't start in the new world order [17:35] "Mode pool is empty" [17:45] New bug: #182062 in xmodmap "IBM Thinkpad T61 key slash/question doenst works in Gutsy" [Undecided,New] https://launchpad.net/bugs/182062 [17:49] it needs modelines, which seems a bit odd [17:55] modelines, defaultdepth and Modes, duh [21:06] well crap, xorg-devel is like half ubuntu devs [21:10] heh [21:10] you say that like it's a bad thing...? ;-) [21:11] also bryce, i read your blog [21:12] on the subject of library versions and fixes, why not use branches? [21:12] you've already migrated to bzr [21:12] for inkscape [21:13] no we still use svn [21:13] we only migrated the bug tracker [21:13] oh [21:13] we have used branches in the past, but find they grow stale and don't get adequate testing. [21:13] well, it still has "very cheap branching" [21:13] ;) [21:14] well, that'd sorta be the point [21:14] to not get adequate testing? [21:14] dev branch updates the libraries [21:14] the other branches would attempt to pull in fixes without touching version dependencies [21:15] the other branches would naturally die off as people prefer to simply update lib dependencies [21:17] it'd be easier to do with bazaar, if it lets you track distro patches [21:20] could be [21:20] 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] 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] I would expect changing at this point would result in some becoming unhappy, and few becoming more happy than they already are [21:22] Allo [21:23] Has anyone had any luck here getting a triple monitor setup working with Ubuntu? [21:23] 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] monkee_of_evil: I have had some limited successes [21:24] I've got these 2 widescreen acer monitors and a single Sceptre monitor ( none-widescreen ) [21:24] 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] monkee_of_evil: If you're using Feisty or earlier Ubuntu, you can use Xinerama to do it [21:24] I'm on Gutsy [21:24] monkee_of_evil: however from Gutsy forward, most drivers have switched to xrandr, which does not handle multiple graphics cards so well [21:24] damn [21:24] it won't be 'til Hardy+1 that the issue is straightened out [21:24] i havent really used either bzr or git [21:24] well, ati and intel [21:25] and experimental mga [21:25] matrox? [21:25] rigt [21:25] +h [21:25] tjaalton: and nv since g80 [21:25] yep [21:25] Yeah... I've got an older ATI dualy & an onboard intel chipset [21:25] but nvidia binary can do silly stuff [21:25] monkee_of_evil: I have gotten triple screen working with non-merged displays [21:25] so like you have :0.0 and :0.1 [21:26] that was on -ati, and I found it too buggy to actually use (mouse would get stuck, etc.) [21:26] hmm [21:26] that was on Gutsy with -ati 195 iirc; it might have gotten better since [21:26] ati upstream supports zaphod mode again [21:26] It will automatically do it's thing and clone my desktop to the two widescreens in Gutsy [21:27] so it should work on current hardy [21:27] 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] http://bryceharrington.org/Photos/X/ [21:29] 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] and you can see this blurr where the mouse moves [21:29] 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] It's the weirdest thing [21:30] can't wait for better monitor support [21:31] Bryce: nice screenshots [21:31] err [21:31] pictures actually [21:31] but w/e [21:32] w/e ? [21:33] w/e is often "whatever" [21:33] * bryce shrugs [21:33] pwnguin got it [21:33] more importantly, that's gnome+konsole [21:34] and.. xmms? [21:36] pwnguin: if you're trying to give me a hard time, won't work ;-) [21:37] I like xmms [21:37] i think if you try harder, you could put in an enlightenment app too ;) [21:37] Fluxbox ftw [21:37] :) [21:38] xmms is like the worst of all worlds. terrible UI that mimics winamp. horrible playlist UI, weak playlist tools... [21:38] and yet something that actually worked all these years :) [21:39] thats about all it has =( [21:39] heh [21:39] 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] interesting. is the placemnt script a matter of which screen? [21:40] I've tried both KDE and GNOME music apps and generally find them inadequate [21:40] yeah.. I fucking hate Rythmbox [21:40] Listen isn't much better [21:40] I put in a bunch of bugs on rhythmbox before giving up on it [21:41] Too bad foobar doesn't run natively [21:41] although it runs decently under wine [21:41] I used KDE in -98 when I installed linux (SuSE 5.3) for the first time [21:42] 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] it's pretty trial-and-error, and different for KDE and GNOME [21:42] anyways, i didnt mean to start an involved flamewar, just poking some fun ;) [21:42] :-P [21:43] I use rb happily at work, but it's far from perfect [21:43] I'm just irritable due to all the UME stuff at the moment, don't mind me [21:43] hehe [21:43] tjaalton: i wish it would let me choose a different playlist to default to on startup [21:43] i filed a wishlist bug in LP and someone appears to have run with it, we'll see where that goes [21:44] ah, I just plug in my iPod and let it play random [21:44] i dont own one of those [21:44] but its nice to be able to filter by rating etc [21:44] I got it just because it's the only brand that has any sort of gadgets for cars [21:45] http://www.last.fm/user/tepsipakki [21:45] i actually used rhythmbox to come up with a playlist for my crappy car stereo to put on CD [21:45] 700 megs of mp3s at bitrate 300 or less sorted by rating [21:46] 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] dah, LP is going offline [22:24] tjaalton: will you report the bug about i810preinit not setting depth to 16 to bugzilla, or shall i? [22:26] jcristau: you can do it, it was your idea anyway :) [22:27] jbarnes knows about it already though [22:27] yeah i've read that [22:28] right, he'd prefer to have the patch on b.fd.o [22:28] a bz report is safer than a mention on irc :) [22:28] of course, and you can't track bugs outside bz [22:28] er, patches [22:28] or both actually [22:29] ffs, launchpad maintenance break [22:40] tjaalton: what's your bz email again? [22:40] tjaalton+freedeskto at cc.hut.fi [22:40] freedesktoP [22:43] thx [22:44] there. #14032 [22:44] thanks [22:44] np [22:45] so you tried it as well? [22:45] didn't have time to test the patch yet, no [22:45] well, it works [22:46] but i don't see why it wouldn't work when X -depth 16 does [22:47] pretty busy at work this week, plus my debian time was taken by other stuff... [22:48] don't worry, a couple of guys already proved it working :) [22:49] cool [22:56] woohoo, at least one bug fixed by switching to openchrome, bug 180841 [22:57] Launchpad bug 180841 in mesa "glXDestroyContext causes segmentation fault with Via Unichrome graphics" [Undecided,Incomplete] https://launchpad.net/bugs/180841 [23:08] nice [23:09] although it was quite unclear which version he was using before, and I think via/openchrome both share the same mesa driver [23:59] 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] sigh