/srv/irclogs.ubuntu.com/2012/03/20/#ubuntu-x.txt

cndRAOF, I'm about to upload xorg-gtest 0.2.0 to precise (\o/)01:08
RAOFWooo!01:08
cndI now have no reservations about the MIR01:08
RAOFI'll address the final gtest MIR comment today.01:09
cndRAOF, oh, I didn't notice any MIR comments for gtest01:09
cndRAOF, do you have the bug #?01:09
RAOFhttps://bugs.launchpad.net/ubuntu/+source/gtest/+bug/94957501:09
ubottuLaunchpad bug 949575 in gtest (Ubuntu) "[MIR] gtest" [Undecided,Incomplete]01:09
RAOFJust to run the tests during the build.01:09
cnddoh, I need to change libxorg-gtest-dev from arch any to arch all01:12
Sarvattmultiarch certainly made local testing annoying, purging all my humble bundle games every time i want to test local libdrm/mesa builds without using a ppa :)01:47
Sarvattsince i dont have :i386 versions built too01:47
* Sarvatt starts not caring about making .deb's of upstream crap he tests01:48
* RAOF just builds i386 versions, too.01:50
Sarvattoh thats a blast with mesa on laptops01:57
Sarvattwould be nicer if we didn't support 8 and 16 bit versions of osmesa to cut the build time in half though :)02:06
cndRAOF, ok, finally got xorg-gtest uploaded after needing a few more changes02:07
RAOFWootness.02:07
=== JanC_ is now known as JanC
tjaaltonhmm, want an intuos5S, the intuos4L is too big09:26
tjaaltondriver support missing, will add it09:26
=== chrisccoulson_ is now known as chrisccoulson
Sarvattbryceh: i'm so confused about https://launchpad.net/ubuntu/+source/mesa/7.11-0ubuntu3.1 -- you added an intel patch instead of the nouveau fix? :P15:17
Sarvattbryceh, RAOF: we have to be super careful with intel cherry-picks in mesa now, the symlinks are dereferenced for the tarballs so when we add a patch touching src/mesa/drivers/dri/intel/* it has to be duplicated out to the other places like src/mesa/drivers/dri/i96515:40
Prf_JakobSarvatt: symlink derefes sounds like a bug.16:45
Prf_JakobSarvatt: I'll do the release today btw.16:45
Prf_JakobAs soon as I get a review on a patch.16:45
tjaaltonit's different in 8.016:45
Prf_JakobAh ok16:45
tjaaltoni guess the tarball has the same symlinks16:46
tjaaltonwhereas 7.11 didn't, so we had to do tricks in order to build a source package from git16:46
tjaaltonsince dpkg-source refuses to work if a real file changed to a symlink16:47
ricotztjaalton, hi17:04
tjaaltonricotz: yo17:07
ricotztjaalton, the #debian-gnome guy really hoping for libwacom soon ;) they are already doing gnome 3.3/3.417:08
tjaaltonricotz: and ready to sponsor it?17:09
ricotzyeah, mbiebl would upload it17:09
brycehSarvatt, actually, looks like I got two bugs transposed.17:09
tjaaltonricotz: so you filed the ITP?17:10
ricotztjaalton, you want to join #debian-gnome17:10
tjaaltonoh I do? :)17:10
ricotztjaalton, no, i havent17:10
tjaaltonwhat's 659700 then17:10
Sarvattbryceh: i'm in the process of working up a SRU for https://launchpad.net/~sarvatt/+archive/sru6 , is it ok if I just remove it from this one? this one will be verified really fast even though its large, its affecting every ivybridge system QA is running tests against17:11
tjaaltonoh it was me17:11
tjaaltonhehe17:11
ricotz;)17:11
brycehSarvatt, that's fine17:11
Sarvattbryceh: that patch you added for src/mesa/drivers/dri/intel needs to be duplicated into src/mesa/drivers/dri/i965 and src/mesa/drivers/dri/i915 if appropriate to get used though17:15
Sarvattbecause of that symlink problem in 7.1117:15
brycehSarvatt, right, but I'm not sure the patch should be sru'd17:16
brycehSarvatt, it's for 757906, whose oneiric task is set to wontfix17:17
brycehmm, think maybe it shouldn't have been set to wontfix though.17:30
=== yofel_ is now known as yofel
Sarvatthmm our mesa debs are .gz19:29
Sarvattwe used lzma for 7.1119:29
Sarvatt        dh_builddeb -s -- -Zlzma19:30
Sarvattvs19:30
Sarvatt        dh_builddeb $(foreach pkg,$(dbgpkg),-p$(pkg)) -- -Zxz19:30
Sarvatt        dh_builddeb $(foreach pkg,$(otherpkg),-p$(pkg))19:30
Sarvattthat might explain the lack of size difference even though all the dri1 stuff was dropped back when i compared it19:33
Sarvatt-rw-r--r-- 1 sarvatt sarvatt 2.9M Mar 20 15:46 data.tar.xz19:47
Sarvatt-rw-r--r--  1 sarvatt sarvatt 5.5M Mar 20 15:28 data.tar.gz19:47
Sarvattthats a huge chunk of livecd space19:47
Sarvattjust for libgl1-mesa-dri19:48
Sarvatt-rw-r--r-- 1 sarvatt sarvatt 2.9M Mar 20 15:48 data.tar.lzma19:49
Sarvattso lzma that doesnt need a pre-depends diff for every package, or xz which does? :P19:51
albert23does deb compression matter on a live cd, as the package is installed?19:52
Sarvattgood point, dont think it does outside of alternate, i've just always gone under the impression that the compressed deb size is how much approximately is going to be used there but that doesn't make sense :)19:55
brycehshould we be thinking about pulling in the libX11 1.5 release with keith's fix for those xcb sync bugs?21:44
tjaaltonsure, better than a beta21:46
tjaaltonor rc21:46
RAOFYeah, probably a good idea.21:57
brycehwould likely make seb128 happy21:57
seb128\o/21:58
seb128that would be great21:58
seb128would that fix all the XAlloc assert bugs?21:59
seb128_XAllocID21:59
brycehseb128, it may; it's not widely tested yet tho afaict21:59
FernandoMiguelOlá22:00
brycehseb128, technically I think the bugs are caused by client apps that are using libxcb in non-threadsafe ways22:02
mlankhorstprobably22:02
brycehseb128, libxcb is advertised as a single-threaded lib, so when multi-threaded clients use it, they have to be careful.22:02
brycehseb128, so I'm not sure if keith's patch is a true fix or may be just papering over bad client coding.22:02
brycehbut... if it stops the asserts...22:03
seb128bryceh, I doubt any "client" use xcb22:03
seb128but maybe a gtk or cairo bug...22:03
jcristauerr22:03
brycehseb128, well, they do via libx1122:03
seb128like "use it directly"22:03
brycehah, right22:04
seb128bryceh, they use gtk,cairo22:04
jcristauusing libxcb in a multi-threaded app is very much ok.22:04
RAOFxcb is lovingly threadsafe, what with all the cookies and all.22:04
brycehseb128, also fwiw where we've seen this in other apps (there was one in apport a few weeks back), the issue was able to be resolved in the client itself.22:05
RAOFDoesn't Keith's patch fix a deadlock in libx11?  I'm not sure that's hugely likely to fix the XAllocID asserts.  But it might, things are madness.22:05
jcristauRAOF: it does.22:06
jcristau(only fix a deadlock)22:06
RAOFWhich is certainly a fix we want; deadlocking apps isn't exactly brilliant behaviour :)22:07
brycehok, so seb128 go back to being sad22:07
seb128:-(22:08
mlankhorst:-o22:08
jcristaudoes seb128 have a reproducer for his bug?22:08
brycehbug #95022222:09
ubottuLaunchpad bug 950222 in libx11 (Ubuntu) "eog crashed with SIGABRT in __assert_fail_base()" [Medium,New] https://launchpad.net/bugs/95022222:09
jcristauclosed worksforme :)22:10
seb128jcristau, no, we just get hundred of XAllocID assert in random GNOME component and I've no clue what info would be useful since they seem random, no user come with a way to trigger them22:10
seb128jcristau, bug #90568622:11
ubottuLaunchpad bug 905686 in libx11 (Ubuntu) "nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed." [High,Triaged] https://launchpad.net/bugs/90568622:11
seb128bug #50706222:11
ubottuLaunchpad bug 507062 in libx11 (Ubuntu Lucid) "synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed." [High,Triaged] https://launchpad.net/bugs/50706222:11
seb128jcristau, so bug got so dupped you can't open them without getting launchpad to timeout half the time22:11
tjaaltonthere was one bug that looked similar which was a flaw in glib22:13
tjaaltonfixed last fall i think22:13
jcristauit's breaking single threaded apps?22:15
jcristaulooks like https://launchpadlibrarian.net/37855577/ThreadStacktrace.txt only has 1 thread22:16
brycehseb128, I think a lot of those shouldn't have been all duped together.  Just because they trigger the same assert doesn't mean it's the same bug.22:18
seb128bryceh, I would be glad to have any clue how to figure that, what to do with them22:21
brycehseb128, well what I do is look in libx11:src/xcb_io.c and grep for the assertion that the bug hit.22:22
brycehseb128, often times the XCB guys have left comments explaining what the assertion means22:22
brycehseb128, and for many of these bugs, that reveals a coding error somewhere in the client22:23
brycehjcristau and RAOF said above that xcb works fine in multithreaded apps, but from all the bugs you and I have seen where xcb assertions get tripped, it seems very sensitive to threading issues in clients.22:25
jcristauthese asserts are in xlib22:25
jcristaunot xcb22:25
bryceh __assert_fail_base (fmt=0xb75b1698 <Address 0xb75b1698 out of bounds>, assertion=0x76ad79 "ret != inval_id", file=0x76acea "../../src/xcb_io.c", line=528, function=0x76adfe "_XAllocID") at assert.c:9422:26
brycehjcristau, xcb_io.c is not xcb?22:26
jcristauthat's in xlib22:26
brycehjcristau, yes, in libx11:src/xcb_io.c like I said22:28
seb128those XAllocID assert a probably the number 1 bug we get through desktop22:28
seb128and I've no clue what's the issue or how to debug it22:28
seb128and it's clients apps all being buggy, or gtk, or x11 or whatever22:28
brycehseb128, do you see the issue as being random, or do you know of reliable ways to reproduce it?22:34
brycehit/them?22:34
RAOFWhoopsie doesn't yet have any ability to do fancy client stuff yet, does it?22:34
seb128bryceh, random, I never hit those bugs22:34
brycehseb128, I've hit one once, but never reproduced.22:35
Sarvattthey're all drawing theme stuff after an app crash while using murrine or clearlooks from a quick look at the bug reports across the other distros22:36
brycehseb128, that particular instance I believe was when I was in the middle of upgrading stuff, and wondered if it might have been due to an underlying library getting changed out.22:36
Sarvattmaybe we only notice it more because of ambiance? :)22:36
seb128Sarvatt, could be22:37
seb128then you have bugs like bug #94808922:39
ubottuLaunchpad bug 948089 in gnome-settings-daemon (Ubuntu) "gnome-settings-daemon crashed with SIGABRT in __assert_fail_base()" [Low,New] https://launchpad.net/bugs/94808922:39
seb128assert !xcb_xlib_threads_sequence_lost22:39
seb128I'm pretty sure that one happens when the session doesn't close properly22:39
seb128i.e gnome-session or xorg segfault22:39
seb128I wonder if the XAllocID one is a similar red herring22:40
RAOFEntirely possible.22:44
seb128bryceh, RAOF: what about bug #92637922:48
ubottuLaunchpad bug 926379 in mesa (Ubuntu) "compiz crashed with SIGSEGV in intel_miptree_release()" [Critical,Triaged] https://launchpad.net/bugs/92637922:48
seb128that got enough dups that launchpad timeout to open it22:48
brycehseb128, it's unrelated to the assert bugs.  There's a patch to add logging, which has been run and given, so waiting on upstream for a fix22:50
brycehseb128, a few more folks testing that and providing logs might help22:51
seb128bryceh, yeah, I know it's not related to the assert, but that one is concerning because it keeps collecting dups every day on unity22:51
seb128ok22:51
seb128so "needs info"22:51
seb128that seemed like something we should tackle for beta222:52
brycehyeah22:53
brycehseb128, I guess the thing blocking it currently is that it's hard to reproduce synthetically22:56
brycehor I should say, developers haven't reproduced it synthetically22:56
RAOFNone of us have been able to reproduce it, have we?22:57
Sarvattnever22:58
RAOFBecause this would sound like a job for apitrace™, even though the actual windows would be blank.22:58
Sarvattoh the mesa bug22:59
RAOFYeah, the mesa bug.22:59
Sarvattsorry, i just popped back on for a minute and thought people were talking about the _XAllocID assert22:59
RAOFNope :)22:59
brycehSarvatt, seb128 advanced the topic ;-)23:00
Sarvatttjaalton said he hit that one23:00
Sarvatthttps://bugs.freedesktop.org/show_bug.cgi?id=4673923:01
ubottuFreedesktop bug 46739 in Drivers/DRI/i965 "[snb-m-gt2+] compiz crashed with SIGSEGV in intel_miptree_release()" [Critical,New: ]23:01
cndbryceh, I was promised warmer weather this time of year... :(23:22
Sarvattcnd: lets trade, too freaking hot23:23
cndSarvatt, fine by me :)23:23
cndSarvatt, what have your highs been?23:23
Sarvatt87 yesterday23:24
cndwow23:24
Sarvatt75 or 80 today, im not sure23:24
cndSarvatt, you've seen the temperature map of the US, right?23:24
Sarvatti'm jealous every time i look at the portland weather in the indicator23:25
Sarvattrain rain rain rain rain snow snow rain snow rain snow, highs in the 40's :P23:25
cndI hope you're not serious...23:25
Sarvatt100%23:25
brycehcnd, heh who promised you nice weather in Portland in March?23:26
cndbryceh, no one promised nice weather, but this is awful23:26
cndthis would be understandable in january23:26
brycehcnd, yep.  March is the worst in portland23:26
cndbut not in spring23:26
cndand I'm fine with the rain23:26
cndit's just these frigid temperatures23:26
Sarvattcnd: where did you move from?23:26
cndSarvatt, columbus, oh23:27
brycehthe snow is a bit unusual, but depressing rain is all about March in portland23:27
cndmeh, rain is fine23:27
cndif it were in the 50s or 60s I'd have no complaints23:27
brycehs/depressing/depressing and cold/23:27
brycehin grade school and middle school I used to have to walk to piano lessons and home in this weather (~2 miles).23:28
brycehbuilds character (and makes you want to own a car)23:28
cndheh23:28
brycehcnd, it'll turn around come april.  We probably won't get "nice" days until May tho23:29
cndcool23:29
cndwell, we're not too far from april :)23:29
brycehyep23:29
brycehin May, this thing people call  "the Sun" sometimes shows up.  Usually high up in the sky.  Keep an eye out for it.23:30
Sarvattmy office is like 15 degrees warmer than the rest of the house and hot even with the ac blasting, thats why i'm jealous :)23:30
brycehSarvatt, I can turn every computer on in my office right now, and not get roasted out23:31
brycehI can even put on t he projectors, but then I do need to crack a window23:31
* RAOF drops off his car for a service.23:32

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