/srv/irclogs.ubuntu.com/2009/02/09/#ubuntu-x.txt

RAOFOh, balls.04:43
RAOFI'd like to sync a newer nouveau snapshot from Debian (bugfixes, ability to run without kernel component), but that requires libdrm-nouveau1 to be built from libdrm sources.04:45
tjaaltonbryce: thanks!04:52
tjaaltonRAOF: if you'd wrap up a patch for it.. ;)04:52
RAOFtjaalton: libdrm?  I might.04:54
tjaaltonyep04:59
bryceheya tormod 15:18
tormodhi bryce15:18
brycehow goes?15:18
tormodwell, thanks. and quite busy :)15:19
bryceyep, seems to be going around ;-)15:20
tormoddid you look at my logging patch ?15:20
bryceI did, but only briefly (just flew home from sprint in berlin and still a bit jet lagged)15:21
bryceoffhand it looked good, I think it can be done15:21
tormodu-dev sprint?15:21
bryceyep15:21
tormoddid you also go to fosdem?15:21
brycenope15:22
tormodI wanted to go this year, but - too busy15:22
bryceETOOMUCHTRAVEL ;-)15:22
tormodwell I hope you can consider my logging patch, because your log patch... how can I say it?15:23
bryce??15:24
tormodthe log becomes a bit too scrambled15:25
brycescrambled?15:25
tormodmixed up with timestamps everywhere in the middle of lines15:25
brycehrm15:25
tormodmaybe it's a bit ddx dependent, surely looks bad on radeon15:26
tormodsee for example this log with my patch: http://launchpadlibrarian.net/22291743/13.%20Xorg.0.log.patched.WORKING15:27
brycedo you have an example of a bad log?15:28
tormodwas just looking for one, not here. must be some on launchpad?15:29
brycefwiw, I can't actually take credit for the patch - it was written by canonical's oem team.  but definitely something I've wanted in there15:29
jcristaui guess the problem is LogVWrite can be called with something that's not a full line15:32
tormodor worse, there was something written before LogVWrite was called15:32
jcristausame thing :)15:33
tormodjcristau, sort of :) I proposed to move the time stamp to logWriteVerb 15:34
brycejcristau: is x log timestamping something debian would take a patch for?15:34
mnemobryce: any idea when the drm kernel patch for the "temporary intel freezes" will be commited to jaunty? --> https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/320813/15:35
ubottuError: Could not parse data returned by Ubuntu: timed out (https://launchpad.net/bugs/320813/+text)15:35
tormodjcristau: see bug #28578715:35
ubottuError: Could not parse data returned by Launchpad: timed out (https://launchpad.net/bugs/285787/+text)15:36
brycemnemo: yes in fact I talked with Tim about that last week; he's planning on waiting until upstream has reached a final decision on what they're going to take15:36
tjaaltonmnemo: when linus pulls it in his tree15:36
tjaalton(hi)15:36
bryceheya tjaalton15:36
mnemobryce: airlie has sent that patch to linus already15:36
jcristaubryce: i'd rather see it go upstream, i think. debian specific patches -> fail.15:36
tjaaltonmnemo: yes, but linus hasn't pulled that yet15:36
mnemoaah okay15:36
brycejcristau: fair enough15:37
tormodI also think ubuntu-specific X log format = fail15:37
tjaaltonbryce: howdy15:37
tjaaltonI can reproduce the "maxclient patch breaks compiz on nvidia" -bug15:37
brycetormod: then maybe we should drop the patch at beta15:37
brycetjaalton, I see coincidentally ajax has started talk of some XID fixup for 11.115:38
tjaaltonbryce: where's that?15:41
brycetjaalton: xorg-devel@15:41
tjaaltonaww, need to subscribe to that15:42
bryceSubject: XC-MISC / X-Resource / core protocol extension proposal15:42
jcristautormod: seen my reply to your acer quirk patch?15:42
tormodjcristau: yes, saw it, will respond a bit later15:43
jcristauok :)15:43
tormodbryce: apropos X startup performance, I just finished a 55 comment long debugging in bug 319363 - turned out gdm switched to failsafe because the computer took more than 10 seconds to start the mga driver...15:45
ubottuLaunchpad bug 319363 in xorg "Can not get 1024x768 video mode by undetected monitor and Matrox G100 8MB graphics adapter" [Undecided,Confirmed] https://launchpad.net/bugs/31936315:45
tjaaltonhaha15:45
tormod333 P2 that was :)15:45
tormodguess what I feel about failsafeX15:47
brycepatches welcomed15:47
bryceactually that's probably not failsafe-x but rather gdm15:50
bryceif not for failsafe-x, you'd end up on the old ncurses error screen15:50
brycetormod: ok, your log patch fix uploaded15:58
tormodbryce: maybe the timeout in gdm (ok that is gdm's fault I guess) should be scaled with cpufreq :)15:59
jcristautormod: maybe whatever is taking 10 seconds to start X should be fixed...16:01
tormodit's just that failsafeX makes debugging a bit more difficult. Maybe LP could scan the logs and mark them if they are VESA logs.16:01
tormodjcristau: the PC is just that old16:01
brycetormod: in what way does it make it more difficult?  the failsafe-x scripts are quite simple and if there are ways they can be improved, I'd love to hear16:02
tormodit creates misunderstandings in the bug reports - well it could be just me. So many times I have to explain that I don't want that VESA log but I need the other log and the user can't find it or create one and so on.16:05
tjaaltonit's true..16:05
tormodBut I have learned as well: now I ask them to boot with "text" and run xinit16:05
tormodBTW a trick for getting info in the event of a "black screen" for instance: xinit -e 'sh -c "xrandr --verbose > log" '16:07
brycetormod: hrm, but I force that log to Xorg.failsafe.log.  They still include that one?16:07
brycetormod: cool, added to https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen16:09
macothe stuff wgrant was doing with moving features into syndaemon in october, that gets rid of the need for SHMConfig and synclient, right?16:30
maco(at least for the features that have been migrated, i mean)16:34
tormodbryce, did you notice xorg-server build broke?17:11
tormodlibgl1-mesa-dev: Depends: libgl1-mesa-glx (>= 7.3) but it is not going to be installed17:11
tormodoh I guess it only broke on anything !38617:12
brycetormod: no didn't notice that17:13
brycetormod: link?17:13
tjaaltonit has been broken for ports some time now17:15
bryceah ok.  amd64 too?17:15
tjaaltonnothing to see, move along..17:15
tjaaltonno, amd64 is fine17:15
bryceseemed to build ok on amd6417:15
tjaaltonso is armel and lpia17:15
bryceok, yeah I know about those breakages17:15
tormodsorry for the noise, I haven't got xorg-server build reports for a long while :)17:16
bryceok no prob17:17
brycebetter to have a few false alarms than be delayed in solving a build breakage issue17:17
tormodbryce, keeping the log patch until Beta sounds like a good idea17:19
brycetormod: btw I booted with the original log patch and see the issues you described17:22
tormodbryce: you didn't test it before you uploaded it :)17:24
brycetormod: you caught me :-)17:24
tormodok I am not so angry at failsafeX any longer, since the original log should be in that failsafe tarball17:25
bryceat the sprint, with sucky wireless, was hard to do testing17:25
macobut easy to upload big files? ;)17:26
tormodyou have a dev sprint without good internet connection? that's funny17:26
brycemaco: a) .dsc's are small files to upload, and b) I do build and upload on my home machine17:27
tormodprobably to keep you working and not watching youtube17:27
brycetormod: oh it was horrible, I was lucky to be connected most of the time17:27
macoi forgot only the .dsc had to go17:27
macoat uds, you mean?17:27
macotoo many geeks, not enough bandwidth for all of 'em17:27
brycemaco, no dev sprint17:27
bryceyeah partly it was overloaded, partly there weren't enough AP's for all the rooms17:28
brycecan I complain about the chairs too?  sitting in them all week + bad airplane seats on way home = threw out my back yesterday when I got home.  Owwww :-(17:30
* maco hands bryce a cookie17:30
macoand a bag of ice17:30
brycethanks maco :-)17:30
bryceoh on positive note, I got lucky and got to sit in 1st class on trip home.  sat 2 seats away from Clive Owen.  that was cool17:31
macomy version of the equivalent sort of luck is running into Dan Kaminsky on Saturday then having him join my friends and i for drinks in the hotel bar17:44
bryce:-)17:48
macoso uh, any answer to the question i asked before?18:06
brycemaco: I could guess but probably would be wrong18:09
brycemaco: best ask wgrant or tjaalton18:09
macowgrant is /away right now18:09
macooh. both are.18:10
macook, well i *think* based on a conversation i had with wgrant back in oct that thats how it works, i just wanted to double-check18:10
brycemaco: you could email them (or mail ubuntu-x@)18:13
macowell i was asking to double-check something i was going to say on u-d-d, but i just put in a disclaimer that i think that's how it works but wgrant was doing it so he can correct me18:14
macoholy screen artifacts, batman18:16
macoare screen artifacts in kde4 a you-guys thing or kde4-guys thing?18:17
brycedepends18:30
tseliotmaco: it's something they have to deal with in Qt418:39
maxbCould someone consider reverting the "Increase MAX_CLIENTS" xorg-server patch until the problems it causes are worked out? It's the most popular problem in #ubuntu+1 right now. (bug 326344)19:59
ubottuLaunchpad bug 326344 in xorg-server "compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2" [Critical,Confirmed] https://launchpad.net/bugs/32634420:00
anderskPackages with that patch reverted are available in my PPA: https://launchpad.net/~anders-kaseorg/+archive/ppa I have confirmed that the problem is gone with the patch removed. 20:02
maxbWhoops :-) Guess I should have searched all PPAs before uploading to my own20:03
brycemaxb: done22:03
zmiq_hi, I have some trouble with xorg-intel driver, and found a patch that solves it; can anybody apply the patch and recompile for me? I'm using jaunty. Thanks22:53
maxbzmiq_: Would it not make more sense for you to do it locally?23:33
zmiq_any hints about how to do it? Just download everything -devel, apply the patch and make will work?23:59

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