RAOFBah.  Stupid overlayfs!  Let me build mesa!02:47
SarvattRAOF: pfft use schroot04:15
Sarvattit builds fine here04:15
* Sarvatt totally blames his own lack of using mk-sbuild but oh well, it works04:16
Sarvattsoo, instead of blacklisting llvmpipe they will try to fix unity?07:15
Sarvatthttps://bugs.launchpad.net/ubuntu/+source/nux/+bug/926859 noticed the responses when i was going through invalid 12.04 beta targetted bugs this morning07:16
ubottuLaunchpad bug 926859 in unity "llvmpipe software rendering needs blacklisting in unity-support-test" [High,Confirmed]07:16
RAOFIt is apparently pretty much as easy as not abusing GL.07:16
RAOFie: Actually calling GLXSwapBuffers, rather than trying to blit bits of the backbuffer on the frontbuffer.07:17
RAOFJason apparently has that already done, and it works.07:17
Sarvattworks for kvm?07:18
tjaaltonstgraber's comment is valid07:18
tjaaltonindeed, it's killing kvm07:18
RAOFBut that can be trivially worked around by selecting an Ubuntu2D session, right?07:19
Sarvattkvm is the main consumer i would care about, thats problably higher than mgi/savage/etc consumers07:19
tjaaltonRAOF: yeah, but needs manual intervention :)07:20
RAOFHow slow is it in kvm?07:20
* RAOF should give it a whirlygig.07:21
Sarvattif its slow thats ok more worried about not working at all07:21
tjaaltonit's using 50% cpu07:21
tjaaltonnot that nice on the host07:21
Sarvattoh cool07:21
tjaaltonhmm, should try it out on the t23 my parents have, but the usb image I have is probably too old..07:21
Sarvattcrap but working?07:22
broderis kvm enabling all the interesting SSE instructions and so forth within the guest?07:22
* Sarvatt has 1gb free hdd space, cant even screw with kvm atm07:22
brodertjaalton: what happens if you pass, uh, -cpu host07:22
tjaaltonbroder: dunno, stgraber? :)07:23
RAOFtjaalton: I guess that depends on what the default experience should be; do we want people, by default, to have the full Unity experience in their virtualised environment at the cost of speed, or do we want people to opt-in to the full Unity for better default CPU usage.07:23
Sarvattyeah if it works its totally another question, would be good to hear from people who care07:24
Sarvattit wasnt working before07:24
RAOFBlacklisting llvmpipe would result in people being basically unable to test unity3d in kvm.07:24
tjaaltonRAOF: true. and could be that a _fixed_ unity might not consume that much cpu when idling..07:24
broderbah. my precise iso is about 2 weeks old07:26
Sarvattthats ok nithng changed besides desktop crap07:26
Sarvattnothing changed in llvmpipe at least07:26
broderwell, i'm having a hard time managing to start a terminal07:27
RAOFOn unity/llvmpipe?07:27
RAOFI'm not sure if Jason's fix is in the distro yet.07:27
broderi can't tell what's glitch and what's bad performance07:27
RAOFBut everything should basically be working, barring damage events not necessarily resulting in the screen being updated :)07:28
RAOFWhich is a pretty big caveat :)07:28
Sarvattgood point i have no clue either, living off in the driver world but the unity/compix fixes are important to that :)07:31
broderoh! right07:31
broderkvm still has the idiocy to make 128M of ram the default07:31
broderlet's try this again, but this time actually give the VM enough RAM to do anything useful07:32
broderok. kvm -cpu host -m 2048 -cdrom Downloads/my-old-precise.iso07:33
brodercompiz seems to hover at about 20% CPU when i'm just running top in a gnome-terminal07:33
broderbut it jumps to 50% or so if i show and then hide the dash07:34
broderactually, more like 80% if i do it a few times07:34
broderor just drag the gnome-terminal window around a bunch07:35
RAOFYeah, don't show the dash.07:41
RAOFIt'll try to render a gaussian blur of your whole screen.07:42
RAOFThat's not fast on anything that's not massively parallel.07:42
broderdoes SSE4.2 not count?07:42
broderor whatever other fancy instructions i have in my nehalem07:43
ricotzRAOF, hello07:44
broderanyway, my gut is that if we'd be using llvmpipe, we should probably switch to unity-2d by default, but it'd be nice if it was still possible to run unity-3d under llvmpipe for the masochists07:44
broderi'm not totally sure how i would go about swinging that if i was going to try07:44
broderi guess move you could move llvmpipe back to libgl1-mesa-dri-experimental07:45
ricotzRAOF, are you planning another mesa upload soon? could you drop the hard-deps-generation of wayland before that?07:45
RAOFbroder: You'd change the unity-greeter check to start unity2d by default when llvmpipe was present, but not override a manual unity3d selection ;)07:45
RAOFricotz: I'm not planning on another mesa upload immediately; it's beta 1 freeze.  We can certainly do that in the next upload, though.07:46
ricotzRAOF, ok, while using wayland releases instead of snapshot it seems reasonable to drop this restriction from the package07:47
RAOFI agree.07:47
tjaaltonyeah I overlooked that part07:48
ricotzit only creates issues currently07:48
ricotztjaalton, hi :)07:48
tjaaltonricotz: hi, I did notice your ping yesterday, but replied directly to pitti07:49
tjaaltonshouldn't be an issue anymore?07:49
ricotztjaalton, alright, if you update wayland it will be again07:50
tjaaltonricotz: yeah, let's fix mesa first then07:51
ricotztjaalton, ok07:51
tjaaltonhmm, not sure what needs changing though07:53
tjaaltonah it's wayland07:53
tjaalton        dh_makeshlibs -V '$(PACKAGE) (= $(V))' -- -c407:53
RAOFDear autotools: seriously?!08:02
tjaaltonso they say that 0.9 will be the point where no backwards-incompatible changes will be made anymore, but after 0.85 they still might08:02
Sarvatttjaalton: oh with mesa 8.14? cool08:06
Sarvattbasically never, didnt expect any better :)08:06
Sarvattintel guys, living in release+1 forever because who needs anything stable08:07
tjaaltonSarvatt: huh? speaking of wayland here. mesa build-depends on wayland, not the other way around :)08:08
Sarvatttjaalton: who does wayland?08:09
tjaaltonso maybe we need that hard dep until wayland 0.9 is released?08:09
Sarvattdont mind me just complaining08:09
tjaaltonok so we won't drop it ever, thanks for confirming ;)08:09
Sarvatthttp://paste.ubuntu.com/855094/ according to ricotz though08:10
Sarvattthats what we do in edgers then build wayland against it08:12
Sarvatterr build mesa against it08:12
tjaaltonso build mesa every time wayland is updated?08:13
Sarvatttjaalton: what the hell are you doing here btw?08:13
tjaaltonwriting nonsense as always :)08:13
tjaaltonI might ask you the same!08:13
Sarvattnah just one time and it doesnt have a hard dependency08:13
tjaaltonso you don't care about api issues?08:14
Sarvattif theres an api issue mesa gets updated to fix it08:14
Sarvattit wouldnt be an issue in the distro08:14
Sarvattwith released versions of wayland and mesa08:14
Sarvattits an issue with mesa master for at most a week at a time08:15
Sarvattespecially now that theres released versions, the hard dependecies were for when it was the same version but changing which shouldn't happen anymore08:16
tjaaltonyeah well we have stable mesa now, so if wayland changes incompatibly and we update it without the hard dep08:16
tjaaltonoh well08:18
Sarvattand "stable" wayland that wont get touched against in 12.04, we can revisit problems in 12.10 :P08:18
RAOFWhen we're switching to wayland, amiright? :)08:19
Sarvattohyea i forgot08:19
tjaaltonI'll drop it now so we won't forget08:21
Sarvattit'll be fine if we dont touch it again this cycle but might come up again later, screwing up 100+ packages when we update mesa sucks08:22
Sarvattall because of wayland nothing uses or cares about except mesa08:23
tjaaltoni was surprised that it's so tiny08:24
tjaaltonwhere's all the bloat?1!08:24
Sarvattdebian/patches/500_pointer_barrier_thresholds.diff duh08:25
Sarvattjoking, nowhere near as bad as the old 500 xi2 patch08:27
RAOFWE HAVE (mostly, ish) WORKING TESTS FOR 500_pointer_barrier_thresholds!  YAY!08:34
SarvattRAOF: cool, they test twinview too where the problems always are?08:38
RAOFNo, I'm lying.08:41
Sarvatti'm just really surprised considering how much of a hack twinview is :)09:12
Sarvatt(and how much dx seems to use it)09:12
Sarvattbreaking twinview is like the ultimate no-go, i get guaranteed 10 pings the next morning every time someone does something i have no clue about09:14
Sarvattunity-greeter broke with twinview, ok i obviously broke that09:14
Sarvattor have any clue what happened09:15
Sarvattyeah i'm bitter, oh well :)09:16
jcristau"switch to nouveau"09:17
jcristauor does that answer not work? :)09:17
tjaaltonnouveau is seriously lacking on newer hw though :/09:17
tjaaltondualhead might work though09:18
RAOFAlso, power management is a really nifty thing to have.09:18
Sarvattlol power management? how's that nvd0 support coming for year old laptops? 3.5 kernel maybe?09:23
Sarvattat least vesa works in 1.11 still, one benefit to not going to 1.12 in precise09:24
tseliotwho needs power management anyway? It's nice to have something warm beside you in the winter ;)09:24
jcristautseliot: people on the wrong side of the world09:25
jcristau(hi, RAOF)09:25
Sarvatttseliot: whats the weather like where you are now? 22C here in winter, ugh!09:25
RAOFSarvatt: Where are *you* that it's 22C?09:26
tjaalton+-0C here09:26
jcristauwe had -10C a couple weeks ago09:26
SarvattRAOF: i'm in winter09:26
tjaaltonbeen kinda wet the past few days, still lot of show09:27
tjaaltonsnow even09:27
tseliotSarvatt: wow, that's warm. It's 11-14 °C during the day here09:27
RAOFIt tops out at 22Cish *here*09:27
Sarvattthis is the first winter where i didn't see snow ever09:27
Sarvattonly time it snowed was when we were in budapest :)09:28
Sarvatt:)? you skipped out on budapest, bah! :)09:29
Sarvatttseliot: are you going to be in orlando?09:29
tseliotyes, but at least I got hail twice here ;)09:30
tseliotSarvatt: do you mean Oakland?09:30
Sarvatttseliot: wait, are you moving back to OEM/premium? i havent even asked ya yet09:30
tseliotSarvatt: no, I'm not going anywhere09:30
Sarvatttseliot: yeah totally, i keep calling oakland orlando, whats wrong with me09:30
Sarvattreally? ya like it in HWE?09:31
tseliotSarvatt: wrong coast ;). But no, unfortunately I won't be able to attend09:31
tseliotSarvatt: yes, I really like it :)09:31
Sarvattboo, thats 3 you skipped out on in a row! :)09:31
SarvattX team dinner wont be the same09:31
tjaaltonoakland auckland.. only a few km apart09:31
Sarvattour crappy cuban sandwiches and guinness :)09:32
tjaaltoni want to witness tseliot drinking guinness09:32
tseliotSarvatt: yes, well, hopefully I'll be there in October (in Europe, I assume)09:32
tseliottjaalton: oh, you didn't in Dublin. I'll do it again, just for you ;)09:33
tjaaltontseliot: :)09:33
Sarvatttseliot: wait you were in dublin? i dont even remember, they had us segreated off to another floor from the desktop guys09:34
Sarvattbut we shoulda been near you because you were in OEM then09:35
tseliotSarvatt: I spent quite some time in the Desktop team's room though09:35
Sarvattlucky! you got crap done09:35
tseliotSarvatt: yep :)09:36
Sarvatti think tjaalton got the most done in hwe during that sprint because he was sitting at the boring table :)09:39
Sarvattupdated -ati to work on llano09:40
tjaaltonoh I did?09:40
Sarvattyup, i remember asking you to do a git snapshot for that reason09:40
Sarvatti was uh09:40
Sarvattplaying with minimodem09:40
RAOFcnd: Hey, would you be planning to factor out some of the xorg testing fun in utouch-geis and utouch-frame into xorg-gtest?  I'm thinking particularly of the pump event loop thingy, which I want want want right now.09:40
RAOFBecause stupid async!09:41
tjaaltonoh I committed some wayland upstream-ubuntu branch09:41
Sarvattsending 2400 baud messages to other pcs in hopes it'd save me from having to press power thousands of times while state got shoved into the rtc09:41
tjaaltonyeah I remember you playing with it.. funny stuff :)09:42
Sarvatttjaalton: before that i spent 2 months pressing power09:42
Sarvatti was really happy that things might be easier :)09:43
tjaaltonhm no the funny part was manjos irc msg speech synthesizer09:43
tjaaltonminimodem was just cool09:43
Sarvatti still screw with him now with the speech synthizer09:43
Sarvattin #hwe say, I don't like vietnamese women.09:44
tjaaltonrude :)09:44
Sarvatthis wife hears it, yeah :)09:45
Sarvatthe's rude, it's fun screwing with him09:45
Sarvatttseliot: you're realling going to update wl?09:46
Sarvatti wish we could just sync it from debian09:46
Sarvattis dkms still not used in debian?09:46
tseliotSarvatt: if it doesn't break apw's wireless, then yes09:46
Sarvatttseliot: balls, it broke his wireless in october when you tried09:47
tseliotSarvatt: I'm not sure, I haven't used debian since Etch...09:47
Sarvattprobably will break it09:47
tseliot(which I still have somewhere)09:47
tseliotyes, this is why I asked him to test it09:47
Sarvattyea debian wl uses m-a09:47
Sarvattscrew that09:47
Sarvattthey keep it up to date really often though09:48
apwheh ... i have two machines now which can use wl, one now is supported by the main kernel09:48
tseliotso maybe they haven already broken his wireless in Debian ;)09:49
apwbut this other one still needs it09:49
Sarvatt"supported" or supported?09:49
jcristauSarvatt: dkms is used in debian09:49
Sarvattis it?09:49
apwSarvatt, one i use for travel, is on the kernel driver 09:49
apwand is very good09:49
jcristaudunno about wl though09:49
jcristaubut in general, yeah09:49
jcristaui haven't used an oot driver since before dkms existed though :)09:50
Sarvattbrcmsmac spams my dmesg at least 1MB a day09:50
apwheh that doesn't supprise me :)09:50
Sarvatt-rw-r----- 1 syslog adm 9.1M Feb 24 04:50 /var/log/kern.log09:52
Sarvattits all 09:52
Sarvatt[29862.537191] ieee80211 phy0: START: tid 1 is not agg'able09:52
Sarvatt[29867.905498] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU09:52
Sarvattmeans a lot, thanks broadcom09:53
apwthere is indeed a lot of debug level crap emitted at too high a level, thats all the sort of thing that being in staging is meant to beat it out of them09:53
Sarvattjcristau: hmm sounds like our brcmwl-kernel-source could be merged to debian to use dkms instead of m-a then09:54
Sarvattm-a is the devil09:55
jcristauoot drivers are the devil ;)09:55
Sarvattim fine with it but my wife isn't09:55
jcristaubut, yeah.09:55
Sarvattyeah thats true too :)09:55
Sarvattautomatically building with kernel updates instead of manually rebuilding though..09:56
Sarvatttheres a chunk of nics where it has to happen, brcmsmac doesn't cover some crap like macbooks09:57
RAOFDear lord?  Macbooks with poorly supported hardwar?  Now there's a pleasant change of pace.10:00
* apw enjoyed the juxtaposition of "crap" and "macs"10:01
Sarvatt4 people will know what i mean when i call them that next10:02
Sarvatt(yes i picked an arbitraty number)10:03
Sarvatttseliot: brcm-wl from october works fine on my machine, where are you updating to?10:03
* Sarvatt has been manually recompiling against each new kernel10:05
apwSarvatt, i note that the phonetic spelling of that should be see-macs10:05
Sarvatttotally x related10:05
tseliotoh, where10:05
Sarvatttseliot: so i had a problem with your same driver in dkms form that i was compiling manually 5 months ago 10:06
tseliotSarvatt: what problem?10:07
Sarvattit didnt work10:07
Sarvatti'll try the new one10:07
Sarvattthey renamed the driver or something10:08
Sarvatti thing that was the issue i had at the time10:08
Sarvatt5 am10:08
tseliotunfortunately I don't have a device to test the driver any more10:09
Sarvattreally? ok will absoltely test it, grabbing your source from chinstrap10:10
tseliotmy netbook died10:20
Sarvattbroadcom drivers kill it?10:23
Lekensteynhi, any change that https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/931397 will be fixed before the beta?10:27
ubottuLaunchpad bug 931397 in xorg-server (Ubuntu) "Xorg crashes with AutoAddDevices "false"" [High,Confirmed]10:27
jcristausend a patch?10:28
* Lekensteyn is downloading the daily image10:32
Lekensteynbryceh: ping?14:25
LekensteynAny change that 1.11.5 is going to land in Precise?14:42
cndRAOF, yeah, I plan on xorg-gtest being expanded over time14:42
cndthe tricky part is that utouch-evemu is under CLA14:43
cndand some people don't like that14:43
cndbut maybe they won't notice :)14:43
cndI was at the gtk hackfest, and they said they didn't mind it14:43
stgrabertjaalton: I updated bug 92685914:58
ubottuLaunchpad bug 926859 in unity "llvmpipe software rendering needs blacklisting in unity-support-test" [High,Confirmed] https://launchpad.net/bugs/92685914:58
stgrabertjaalton: and I'll bring it up at the release meeting, will also be on the next techboard agenda if llvmpipe hasn't been blacklisted in unity-support-test by then...14:59
LekensteynUbuntu' 1.11.4 != Xorg 1.11.4 right?15:37
=== yofel_ is now known as yofel
technovikingRAOF: ping16:41
tjaaltonstgraber: ok, good to know (didn't read the bug yet)17:03
tjaaltonLekensteyn: right, the input stack is from 1.1217:04
Lekensteyntjaalton: is that
LekensteynI saw that the InputOption type has changed between 1.11.4 and
Lekensteynso, carelessly copying changes breaks things17:09
Lekensteynit's not a key, value, next struct anymore17:10
tjaaltonmerged from master, more likely17:12
bdmurrayRAOF: perhaps a hybrid-gfx tag, set by apport, would be useful?  I'm looking at bug 939283.17:31
ubottuLaunchpad bug 939283 in plymouth (Ubuntu) "[hybrid-gfx] Blank screen on boot due to failure to follow primary framebuffer" [High,New] https://launchpad.net/bugs/93928317:31
brycehLekensteyn, yeah looks like you need cnd to look at that bug #93139718:27
ubottuLaunchpad bug 931397 in xorg-server (Ubuntu) "Xorg crashes with AutoAddDevices "false"" [High,Confirmed] https://launchpad.net/bugs/93139718:27
cndbryceh, yeah18:28
cndI'm subscribed or assigned18:28
cndI think it's a bug introduced by backporting18:28
Lekensteyncnd: are you chase douglas?18:28
cndLekensteyn, yep18:29
cndLekensteyn, you can use "/whois cnd" in the future :)18:29
Lekensteyntrue :)18:30
LekensteynXorg -configure crashes as well18:31
brycehcnd, from comment #2 wondering if it still needs the bits from that duplicateDevice call, which converts the pointer type?18:31
Lekensteynwhen debugging I suggest to build with DEB_BUILD_OPTIONS=noopt or gdb will behave weird when setting some breakpoints18:32
cndLekensteyn, I usually use DEB_BUILD_OPTIONS="noopt nostrip noudev nocheck parallel=<n>"18:33
brycehLekensteyn, thanks for doing the extra gdb legwork btw, not many do, but it helps a lot.18:33
cnd+1 :)18:33
Lekensteynyour welcome, I've received some queries about it from users who have an nVidia Optimus laptop model18:34
Lekensteynthat needs to be fixed ;)18:34
bdmurraybryceh: bug 930004 and bug 930839 are both crashes in xcb during distribution upgrades.18:35
ubottuLaunchpad bug 930004 in update-manager (Ubuntu) "update-manager assert failure: python: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed." [Medium,Confirmed] https://launchpad.net/bugs/93000418:35
ubottuLaunchpad bug 930839 in update-manager (Ubuntu) "update-manager crashed with SIGABRT in __assert_fail_base(): Assertion !xcb_xlib_unknown_req_in_deq failed in dequeue_pending_request" [Medium,Confirmed] https://launchpad.net/bugs/93083918:35
brycehbdmurray, looking18:36
brycehheh, like the description in the latter18:36
bdmurrayyeah, that's a gem18:36
brycehbdmurray, often xcb issues are races in threading behaviors, that can be quite challenging to sort out.  So if there's a set of steps to reproducing it, that'd likely help a good bit.18:39
bdmurraybryceh: is this helpful?18:43
bdmurrayERROR:root:NvidiaDetection returned a error: __init__() got an unexpected keyword argument 'datadir'18:43
bdmurrayMarkUpgrade() called on a non-upgrable pkg: 'brasero'18:43
bdmurrayERROR:root:Upgrading 'brasero' failed18:43
bdmurray[xcb] Unknown sequence number while processing queue18:43
bdmurray[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called18:43
bdmurray[xcb] Aborting, sorry about that.18:43
bdmurraypython: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.18:43
brycehbdmurray, yeah sounding like a client error18:43
brycehlooking in libx1118:44
bryceh"Most likely this is a multi-threaded client and XInitThreads has not been called" sounds relevant (and familiar...)18:45
brycehbdmurray, wonder if it's a protocol mismatch between client app and server?18:49
bdmurrayoh, like if libxcb updated and update-manager hadn't yet?18:50
brycehsomething like that's what I'm wondering.  18:51
brycehas you probably already gathered, this fault is happening during the client polling of the X server, and it gets some response it didn't expect18:52
brycehif we knew roughly how to trigger this bug, we could probably set up xtrace between the client and server to see  what the communication is between them18:52
brycehhere's the test that seems to be failing:18:54
brycehXLIB_SEQUENCE_COMPARE(req->sequence, >=,18:54
bryceh                                       dpy->xcb->pending_requests->sequence)18:54
brycehactually wait, it's not an unknown request but rather an unknown sequence number18:55
brycehnot sure what a sequence number is in this context18:55
brycehso not that, but this:18:56
bryceh(XLIB_SEQUENCE_COMPARE(event_sequence, >,18:56
bryceh                                                  dpy->request)18:56
=== Lekensteyn is now known as Lekensteyn|dinne
brycehbdmurray, ok reading further... bunch of warning text regarding threading18:57
brycehbdmurray, ok yeah so I'll paste the text into the bug report18:57
brycehbdmurray, ok I'm finally remembering.  When we first switched to xcb, we had a huge spate of these types of bugs.  libxcb is more sensitive to how it's called in threading conditions, so the client code needs to be careful to make the calls properly19:00
brycehbdmurray, so the assert that's being tripped is not a bug in X but rather is catching a bug in the client code19:01
brycehat least, I think.19:01
brycehI could be talking out of my ass.  That would hardly be new.19:02
brycehbdmurray, ah, so bug 930004 looks like the threading issue I mentioned19:06
ubottuLaunchpad bug 930004 in update-manager (Ubuntu) "update-manager assert failure: python: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed." [Medium,Confirmed] https://launchpad.net/bugs/93000419:06
brycehbug 930839 may be the mismatched client/server issue I mentioned previously.19:06
ubottuLaunchpad bug 930839 in update-manager (Ubuntu) "update-manager crashed with SIGABRT in __assert_fail_base(): Assertion !xcb_xlib_unknown_req_in_deq failed in dequeue_pending_request" [Medium,Confirmed] https://launchpad.net/bugs/93083919:06
brycehagain though, kinda just guessing here.  Both appear to be client errors that XCB is catching (i.e. both are assertion fails), rather than actual segfaults in X19:07
brycehbdmurray, #901675 is another similar bug in apport19:16
bdmurrayokay, thanks19:18
brycehanother in g-s-d - 83369419:18
brycehbdmurray, ahh https://bugzilla.gnome.org/show_bug.cgi?id=657255#c819:19
ubottuGnome bug 657255 in gsettings "gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:575: _XReply: Assertion `!xcb_xlib_extra_reply_data_left' failed." [Critical,Resolved: fixed]19:19
bdmurrayum, where does that leave us?19:24
brycehbdmurray, can you raise it with the upstream-manager folks to look into?19:26
brycehbdmurray, it's not an X bug19:26
bryceh(I mean, aside from the fact that libxcb is sensitive to threading issues...)19:27
bdmurrayah okay19:27
bdmurraybryceh: but in bug 832513 they say it should be fixed in libglib2.0-019:38
ubottuLaunchpad bug 832513 in GLib "gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:575: _XReply: Assertion `!xcb_xlib_extra_reply_data_left' failed." [Critical,Fix released] https://launchpad.net/bugs/83251319:38
brycehbdmurray, it's not the same bug, just different codebases making similar coding errors and hitting the same assertion19:40
brycehbdmurray, it'd be like two C applications getting the same error message from gcc; it doesn't mean they have the same bug, nor that gcc is broken, just that they both happened to have the same kind of programming error.19:41
bdmurraybryceh: okay, thanks again for the help19:45
brycehbdmurray, sure thing, let me know if you need more help19:52
=== Lekensteyn|dinne is now known as Lekensteyn
=== Lekensteyn is now known as Lekensteyn|off

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