/srv/irclogs.ubuntu.com/2011/05/05/#ubuntu-x.txt

RAOFbryceh: The “stuff->foo” idiom in X protocol handlers is common - one of the macros involved in unpacking the proto buffer defines & populates it.00:27
RAOFThat freaked me out as well when I started looking at the protocol dispatch code :)00:28
bjsniderRAOF, do you suppose mono is dead now?00:33
RAOFNo.00:33
RAOFI understand that there's quite a healthy revenue stream coming from the various Mono* frameworks for smartphones, there are paid mono developers in Europe, and at worst, it's all open source and quite a lot of people care about it.00:34
bjsnideryeah but it's not the same without any support from novell00:37
RAOFI'll wait until there's actual news that Attachmate is shuttering the Mono* work before worrying *too* much about Attachmate shuttering the mono team. :)00:39
bjsniderhow can they continue the mono work if they fired the whole team?00:39
RAOFWhere's the suggestion that they fired the whole team?00:43
RAOFLast I heard was “consolidating in Europe, letting go some US developers”00:44
bjsniderthe phoronix story said 30 mono developers01:13
raevolany tips on configuring an 11.04 xorg.conf for dual head? i forgot to back up my old one and can't remember the black magic i used to get it working before02:37
raevolhttp://pastebin.com/zhm8JZKh02:37
raevolis what i have, but no dice02:38
RAOFraevol: Generally I don't bother with an xorg.conf and just let the DE tools set up dual-head.02:45
raevolDE?02:46
raevoldesktop environment?02:46
RAOFYeah.02:46
raevoli'm running xfce so i don't have those tools02:46
RAOFFailing that, http://tinyurl.com/yuftlh02:46
raevolyea that's the guide i just used, no luck02:46
raevoli wish there wasa way to generate an xorg.conf from a xrandr setup02:47
raevoldo you know if my xorg.conf should be in /etc or /etc/X11?02:48
raevolseems to load it either way02:50
brycehshould be in /etc/X11, although xserver checks a variety of paths02:55
raevolok02:56
raevolhmm, using that guide, my xorg.0.log says "no monitor specified for screen0"02:57
raevolappears that guide is out of date02:57
brycehRAOF, one advantage to using xorg.conf might be that the server initializes as multihead, so your screens would be set up earlier than if you let gnome-desktop do it post-init03:07
Takyoji[laptop]Any way that I can help with debugging this bug? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/76368803:36
ubot4`Launchpad bug 763688 in xserver-xorg-video-intel (Ubuntu) (and 1 other project) "[915GM] S-video output doesn't work in Natty (i386) (affects: 10) (heat: 242)" [Medium,Confirmed]03:36
Takyoji[laptop]of which I'm affected by03:37
brycehTakyoji[laptop], install xdiagnose, run sudo xdiagnose, switch on graphics debug messages (the first checkbox).  Reproduce the bug, then collect output of dmesg, post to the bug. 03:39
brycehTakyoji[laptop], assuming it's not obvious what's wrong, the next step after that is to forward the bug upstream to bugs.freedesktop.org, sending dmesg, Xorg.0.log, and xrandr output03:40
Takyojialright03:55
tjaaltonso -mouse/-keyboard are for !linux, which means we can drop them from ubuntu by now, because evdev is used by default since intrepid07:48
tjaalton?07:48
tjaaltoncan't think of any other usecase for them07:48
tjaaltonbut people keep on filing bugs against them07:49
tjaaltonwhen they should've filed against -evdev07:49
brycehtjaalton, yep07:49
tjaaltonalso, should we review the list of ubuntu patches on xorg-server next week?07:50
tjaaltonhm07:50
tjaaltonmaybe a new session for "removing cruft & patch review"07:51
tjaaltonor cram them into an existing one07:51
tjaaltondunno how much time this would need07:51
RAOFI'd like that.07:52
brycehI could easily imagine us needing ~5 min per patch, so that could add up to a whole session07:52
RAOFGo over xserver & mesa.  We might as well schedule a session for it, even if we don't use up the whole time.07:52
tjaaltonyeah07:53
brycehdon't forget there'll be a sprint not too far afterwards07:53
tjaaltoncruft removal fits in the general planning session i guess07:53
brycehit's possible you may prefer having that discussion at the sprint when you're not quite as session-slammed07:53
tjaaltonbryceh: right, but it's too late for pushing the valid patches upstream07:54
brycehfair enough07:54
brycehalso, I won't be attending the sprint, so if you need my input then uds would be better07:54
tjaaltonok07:57
tjaaltonhmm, I'll check the release schedule for 1.1107:59
brycehsome portion of the xserver patches are just adding null pointer checks.  between apport and arsenal I'm confident we'd be able to quickly notice the crashes those fixed if they came up again so I'd be ok with us just blindly dropping them and see what happens.  I'm fairly sure all were forwarded upstream and got fixed in more intricate ways subsequently (worth doublechecking)08:02
brycehthere's another portion which were driven by dx team needs which I don't even know for sure are still valid... like the bgnone stuff08:03
tjaaltoni dropped one which got marked fixed upstream in a different way08:03
tjaaltonbut yeah08:03
brycehtseliot was a bit more tied into that stuff08:03
tjaaltonwe'll see then :)08:03
brycehtjaalton, anyway whatever patches remain should be renumbered from 100.08:04
brycehoh, there's also a handful from cnd for input stuff, although he's been good about ensuring those get sent upstream for the most part08:04
tjaaltonbryceh: maybe so that 1xx is for patches never meant upstream, 2xx those that are targeted upstream, and then 3xx for backports?08:05
tjaaltonor somesuch08:05
brycehyeah, sounds like a good scheme08:05
tjaaltonyeah the input stuff should get in 1.11, i hope08:05
brycehonly catch might be if a 1xx ubuntu-specific patch depended on a 3xx backport patch or something08:06
brycehbut that sort of situation is probably going to be exceedingly rare08:07
tjaaltongood thing quilt doesn't care how they are named, just what order they have on the list .)08:07
tjaalton:)08:07
brycehheh, that's true08:07
tjaaltonso the merge window for 1.11 closes on 27th08:56
tjaaltonwhich means having a review session next week would probably make sense09:01
=== thade_w is now known as Alexia_Death_
=== debfx_ is now known as debfx
=== yofel_ is now known as yofel
=== ScottK2 is now known as ScottK
=== JanC_ is now known as JanC
Sarvattwell thats a fun change to wake up to, mesa requires glproto 1.4.13, xserver 1.10.x doesn't build against glproto 1.4.13 :)15:22
AzelphurHmm, I'm having fun with my computers text rendering atm http://dl.dropbox.com/u/3832397/screenshots/May%202011/2011-05-05-155649_3840x1200_scrot.png16:01
Azelphurany ideas what would cause that? it seems to affect everything16:02
AzelphurX session restart time I guess \o/16:05
=== yofel_ is now known as yofel
Sarvattif anyone needs drm-intel-next for testing - http://kernel.ubuntu.com/~sarvatt/drm-intel-next/20:21
brycehSarvatt, btw that's also built by the kernel team - http://kernel.ubuntu.com/~kernel-ppa/mainline/20:52
bryceh(although looks like it hasn't been updated in a while...)20:52
Sarvattbryceh: yeah its pointing at ickle's drm-intel-next and keithp took over maintainership of it20:53
brycehah20:53
Sarvattplus this one has all the ubuntu specific patches so I have a functional touchpad and junk :P20:53
brycehapw, ^^  need to repoint the git tree on drm-intel-next20:53
Sarvattpinged him this morning, pretty sure he's gone already20:54
brycehwell, no hurry.20:55
brycehSarvatt, remind me we should snag a kernel guy next week about this20:55
Sarvattbryceh: hopefully http://translate.google.com/#en|hu|give%20me%20a%20guinness%0A is all the hungarian I need :)21:58
brycehheh21:59
brycehguessing a beer run on Monday will be on the agenda22:00
bjsniderspend all day debating which beer it will be and who will get it22:00

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!