[00:45] Aaah, good. That's not a new crash, just an old one :/ [00:59] I committed a fix for bug 855100 but which series should I push it to? [00:59] Launchpad bug 855100 in totem "python plugins not working" [Undecided,Fix committed] https://launchpad.net/bugs/855100 === eeejay is now known as eeejay_is_afk [01:39] jbicha, what was the reason for holding back totem 3.2? [01:44] it depends on clutter-gst and at least in the past clutter hasn't worked on quite a bit of hardware [01:45] we should get totem 3.2 in the GNOME3 PPA though [01:46] seems to work on nvidia [01:46] so far [01:48] maybe just ARM, I don't really know [01:48] it would be good to figure out before UDS where it works & doesn't work though [01:51] want the scripts so you can build/install it on yours? that would eliminate intel [01:57] bjsnider: yeah you can send me what you've got; I started on totem 3.2 but I didn't get all the way yet [01:58] and you should ask tomorrow what the criteria for joining the GNOME3 team is, as I don't know [02:00] I've heard reports of clutter having problems on ATI in the past, that may be resolved now though. [02:03] I think GNOME Shell fglrx users are still waiting for next month's version to finally get gshell more usable [02:03] that's ridiculous [02:04] but unsurprising [02:17] It of course also means that unless you've got 3D you can't play videos. [02:17] Which is perhaps just a *little* bit aggressive :) [02:25] ah, then there's quite a bit of hardware where 3D isn't working [02:27] Indeed. [02:38] RAOF, they can use something else to play videos [02:38] That's true. [02:38] But the thing we'll pop up by default, and the only video player we install by default, won't work. [02:39] is it going to be substantially different in 6 months? [02:40] We have six months to fix it? :) [02:41] 6 months to get everybody on 3d [02:41] RAOF: llvmpipe ? === smspillaz is now known as smspillaz|o [02:43] bjsnider: Or 6 months to add a non-3d fallback to totem. Or to fix clutter on swrast. [02:43] maybe there's already a fallback [02:43] i haven't tested it === _Tommeh is now known as Tommeh [04:14] Good morning [04:16] Hey pitti. [04:17] Hey pitti! [04:21] hey TheMuso, hey RAOF, how's downunder? [04:22] Damp and cold, apparently. [04:22] More like spring these days thanks. [04:22] Spring is here! [04:22] Yep, warmer weather being the spring I am referring to. :) [04:23] ah, we just turned from "nice summer" to "cold and windy", brrrr [04:24] * ajmitch would like summer to come around a bit faster [04:26] * RAOF would like to be proved wrong about his understanding of gnome-desktop's crtc assignment algorithm [04:29] pitti: what series should I push the totem plugin fix to? [04:29] jbicha: just saw your upstream commit pointer, nice! [04:29] jbicha: oneiric-proposed, please [04:29] jbicha: I can accept it already, so that people can test it [05:04] STACKING!!!!1111 [05:04] smspillaz|o: You're fixing all those problems in an SRU, right? :) [05:09] -.- [05:10] RAOF: its not possible to fix them 'all' unless I can reproduce them 'all' first [05:10] RAOF: though I did give didrocks some patches which fixed a few cases, not sure if that's been uploaded yet [05:11] see here's what sucks about writing window managers [05:11] when you write a normal application and a user reports a bug about how they did something crazy and then it did something crazy in return [05:11] you can just say [05:11] 'dont do that' [05:12] when you write a display server or window manager, what on earth are you supposed to tell the user [05:12] 'dont use your desktop? [05:12] ' === smspillaz|o is now known as smspillaz [05:12] Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 466: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed! [05:12] wonder what's up with that [05:12] * smspillaz reboots [05:19] RAOF: also, whenever someone says the word "stacking" I just think of this http://www.youtube.com/watch?v=U9SEVop9sc0&feature=related [06:15] good morning [06:18] Hey didrocks [06:18] hey RAOF! [06:19] RAOF: I again had a X stopping on too much write [06:19] RAOF: in addition to Xorg.log, I have dmesg output, interested? [06:19] Yes please! [06:20] bonjour didrocks [06:20] good morning pitti! Seems you didn't sleep much, how are you? [06:21] didrocks: I'm fairly well, cold is almost gone [06:21] didrocks: I got 8 hours, from 10 to 6, that's quite enough :) [06:21] pitti: great! you should take some rest though in addition to just answering bugs from 9:30 and starting again at 6:20 :-) [06:22] wow, I'm being watched :) [06:22] We have your best interests in mind :) [06:23] pitti: heh! ;) [06:26] RAOF: http://people.canonical.com/~didrocks/xcrash/ [06:28] didrocks: And that dmesg includes the crash? It's depressingly silent. [06:28] RAOF: well, the "stop" at least, not sure if it's a real crash :) [06:28] but yeah, it contains this "zomg, no more Xorg" [06:30] Bah [06:31] * RAOF hates on Xorg's backtrace handler that we don't quite manage to stop messing up crash dump production. [06:34] At least it seems to be consistently crashing in evdev. I'll think about how best to grab useful state. [06:35] RAOF: keep me posted :) === tkamppeter__ is now known as tkamppeter [07:01] Greetings. [07:11] BigWhale: Greetings, fellow Human! [07:12] Funny thing saying this to a whale :> [07:17] pitti: compiz and compiz-plugins-main into -proposed FYI [07:17] \o/ [07:18] lot of fixes from smspillaz :) [07:19] yay, thanks [07:28] smspillaz: great work, thanks for all these fixes [07:28] :) [07:28] more coming next week :) [07:42] chrisccoulson: You've prodded the bowels of gnome-desktop's RANDR code recently - am I correct in my analysis that it can fail to accept a valid configuration because it's stupid about the restrictions on CRTCs? [08:09] hey [08:09] bonjour seb128 [08:09] hey pitti, how are you? [08:10] seb128: quite well, thanks! [08:10] salut seb128 [08:11] pitti, did you get over your cold? [08:11] lut didrocks [08:11] pitti, it's meeting reminder day! [08:11] seb128: mostly, yes [08:11] seb128: ooh, right [08:11] great ;-) [08:13] ok, proposed is getting quite some activity, I'm torned between testing what will be on the CD or switching to proposed ;-) [08:14] * pitti is on -proposed [08:14] I have my mini10 on a fresh install from this morning without -proposed [08:15] I've my 10v on a fresh install for yesterday afternoon [08:15] and I'm finally enjoying some quiet hours for apport hacking :) [08:15] need to rsync and redo an install today [08:15] pitti, yeah, apport hacking \o/ [08:15] seb128: the bcmwl installation is really great these days, did you notice? [08:15] just bug 872119 which stands between "now" and "perfect" [08:15] Launchpad bug 872119 in ubiquity ""Error occurred while copying the network settings" on bcmwl machine" [Undecided,Confirmed] https://launchpad.net/bugs/872119 [08:15] ev is on it [08:16] pitti, well, I had wifi working on the liveCD for most of the cycle but yesterday's install had no wifi listed in ubiquity [08:16] need to try again [08:16] hm, worked here [08:16] it automagically installed bcmwl at the start of ubiquity [08:17] pitti, right, that's what I mentioned to you at the rally iirc, wifi was working for me on the liveCD this cycle, you didn't believe me by then :p [08:17] well wifi was up but I had no network listed in ubiquity [08:17] seb128: yeah, I didn't realize that we shipped gcc, dkms, toolchain, bcmwl-kernel-source on the desktop CDs [08:17] it didn't pick my ap for some reason [08:18] by maybe it was just being slow to pick it up and I didn't wait or something, I will try again in a few [08:18] I also didn't bother much because I figured most people who install online so I wanted to test an offline install ;-) [08:19] pitti, oh, you improved your sru script to pick names? ;-) [08:20] seb128: yes, it hardcodes "Dear seb, plz test everything, love pitti" [08:20] :p [08:21] morning everyone [08:21] it was done to more clearly point out that we actually expect and appreciate feedback from the original reporters, not (just) QA team [08:21] hey jasoncwarner_ [08:21] oh, a jasoncwarner_ [08:21] let's pretend we are working! [08:21] jasoncwarner_: are you in London now? [08:21] hey seb128 and pitti, how are things? [08:21] jasoncwarner_, working hard!!! ;-) [08:21] pitti: yup! finally made it. boy, I love traveling ;) [08:21] *clickedicklackediclick* [08:21] lol [08:22] * pitti ignores the blatantly huge irony tag there [08:22] jasoncwarner_: had to rebuild during the night, and today's testing again uncovered some warts, but nothing earthshattering so far [08:22] seb128 pitti , how are things looking? [08:22] pitti: oh, ok... [08:23] either of you know how lightdm multi-=monitor is looking? I didn't catch robert this morning [08:23] jasoncwarner_: us having the time and nerve to do bad jokes is usually a good sign :) [08:23] jasoncwarner_, no real surprise desktop wise, we are good, not great but good [08:23] jasoncwarner_, some SRUs start flowing in proposed already [08:23] jasoncwarner_: bryceh did some analysis on http://people.canonical.com/~bryce/ExternalMonitor/results.html [08:23] seb128 pitti cool, I'm going to be putting in some blueprints this week then...get ready for P! [08:23] RAOF, what sort of restrictions? [08:23] hello btw :) [08:23] jasoncwarner_: seems bearable on the lightdm side [08:23] and good morning everyone [08:23] jasoncwarner_, great [08:24] hey chrisccoulson [08:24] hey chrisccoulson, good morning; how are you? [08:24] hi seb128, how are you? [08:24] morning chrisccoulson ! [08:24] hi pitti - i'm good thanks, how are you? [08:24] hi jasoncwarner_, how's london? [08:24] pretty well, thanks [08:26] chrisccoulson, I'm fine, you? [08:26] chrisccoulson: not rainy? ;) seems nice so far. never been here. [08:26] seb128, yeah, good thanks [08:27] jasoncwarner_, oh, it's not raining? [08:27] chrisccoulson: saw the river, london bridge...all good so far [08:27] i guess that's because you're 3 hours away from birmingham! [08:27] chrisccoulson: I know, right? I thought it always rained in london [08:27] bryceh, pitti, jasoncwarner_: just for the record it's likely that login screen and the Unity (GNOME) session should behave differently with multimonitor, lightdm has this point let xorg deal with screens where Unity (GNOME) has gnome-settings-daemon reacting to xorg events [08:27] should->will [08:27] i haven't been to london for years. in fact, i don't think i've been since i joined canonical [08:28] which is a bit strange ;) [08:29] pitti - i fixed ubufox being disabled on upgrade to the firefox beta yesterday, although you'll need to manually reenable it if it's already disabled [08:29] but the new version won't be disabled on upgrade now [08:29] i really don't see the point in this new feature in firefox [08:29] when it's so easy to bypass [08:30] i've already fixed all of our extensions to work around it ;) [08:32] You people are chatty this morning. :> [08:33] not only this morning ;-) [08:33] BigWhale: it's not Internet Relay Silence :) [08:33] pitti, what do you think about bug #840858 [08:33] ? [08:33] Launchpad bug 840858 in gnome-control-center "No obvious way to disable Ubuntu startup sound" [Low,Fix committed] https://launchpad.net/bugs/840858 [08:34] seb128: OK for me for an SRU, although it really feels like a workaround [08:34] it's the last place someone woudl look for sound events [08:35] but at least it's some way, so fine for an SRU [08:35] it is a workaround but Jeremy and some other feels like it's a frequent request and the workaround is better than not having the option [08:35] not a solution for precise, though [08:35] right [08:35] we will [08:35] - turn it off by default in precise [08:35] - change the sound configuration dialog to have a checkbox for turn it on, off [08:36] sounds great [08:36] seb128: do you know if GNOME has a startup sound? [08:36] as there's no option for it, I figure "no"? [08:36] define "GNOME", "GNOME OS"? ;-) [08:36] shell [08:36] upstream gnome 3.2 install, I mean [08:36] well, the autostart is part of libcanberra [08:37] so it's really a matter of how distribution package and ship libcanberra binaries [08:37] perhaps they'll take at least that checkbox then [08:37] there is not a reference GNOME desktop that would allow to answer about what upstream recommends [08:37] yeah, let's see ;-) [08:38] to be honest if we turn it off I don't care much about the checkbox [08:38] not sure how many users actually want a login sound [08:38] same here [08:38] it feels like a thing of the past century [08:39] without mobile devices to annoy your fellows [08:40] heck, we took the systray away, we can certainly get away with killing that effing login sound :) [08:41] ;-) [08:42] I was wondering yesterday if screensavers are from the previous century as well :p [08:42] it's weird, windows8 as well removed the screensaver [08:42] seb128 pitti john and connor said we could remove startup sound [08:43] well, screensavers are useful to not damage physically crt screens [08:43] that's an issue we don't have nowadays [08:43] jasoncwarner_, yeah, we ack-ed that decision and are happy about it, we just missed to do it before uif in Oneiric so we will do in next cycle [08:44] seb128: indeed, and as it's quick to shut down one, contrary to monitor which have to be warmed [08:44] seb128: :) it does feel like "polish" anyway...cleaning it up ;) [08:44] seb128: actually, the indicator icons managed to burn into my TFT; I was quite surprised [08:45] didrocks, well, it's rather than crt screens can get marked if a static image stay for too long, should be the case with tft ones [08:45] though pitti is making me lie apparently now :p [08:46] well, I bought this screen in 2003, it's admittedly not the shiniest one around [08:46] I'm not really using screen savers, if I'm away from the computer for longer than 20 mins or so I just switch it off [08:46] seb128: yeah, the other solution would have been to shutting down tft which takes time as I told, that's what is used for crt now as the screen is disabled quite quickly as it can be brought back quickly [08:47] no reason to waste 30 W [08:47] didrocks: I thought that already happened? [08:47] it does work here (when I forget to turn it off before lunch break or so) [08:47] well anyway it's not a rational thing, some users just like screensavers it seems ;-) [08:48] I'm really unsure we should bring it back though [08:48] well I just don't see it being enough of a priority to get done [08:48] (on this point, its simple enough for me to technically do this, would take me about 15h to get working fully) [08:49] G'morning all. [08:49] smspillaz, well, we are speaking about "hacks", i.e screensaver animations [08:49] yeah, I know [08:49] smspillaz, we still want compiz to do the locking if you can get that done so we can use lightdm as a frontend for lock screen and switch users [08:50] +1 [08:50] well [08:50] * Sweetshark is a bit scared now that he sees on the weekly summary how much he has to do at the Libreoffice conference ... [08:50] now that I come to think of it, I'm not a fan of compiz doing the locking [08:50] hey Sweetshark [08:50] I'm more a fan of [08:50] having the lock screen run a compositor and window manager inside of itself [08:50] Sweetshark: heh, but don't plan to stop sleeping [08:50] which replaces compiz [08:51] but that would be ... difficult to do architecturally [08:51] smspillaz, how would that work? [08:51] right... [08:51] seb128: well, the idea would be that it takes the compositor selection away from compiz so compiz stops doing compositing [08:51] or compiz keeps compositing into an offscreen window [08:51] while the onscreen one is the lockscreen [08:51] or something [08:51] smspillaz, could one process composite different xorg sessions? [08:52] no [08:52] this would be an external process [08:52] maybe I'd need to write it all down one day and nut it out [08:52] but the idea is to have compiz' compositing redirected into an offscreen window [08:52] doesn't seem like a lts cycle thing ;-) [08:52] no, it isnt [08:52] well all we want is to make sure you can't go back from lightdm to open sessions [08:52] and then have the "lock screen" take over the "real" compositing from X [08:52] pitti: I work 24 hours a day and if that isnt enough I'll work nights ... [08:52] one other way would be to make sure you can't vt switch [08:53] seb128: oh, I was thinking more stability [08:53] seb128: like, as in, if you can make compiz crash, you won't have a lock screen [08:53] with this, you are minimizing what can crash [08:53] right [08:53] but its complicated [08:53] let's see what we can get done ;-) [08:53] requires a bit more thought, but I sort of came up with it today in light of the handoff stuff I did a few days ago [08:54] what we don't need is complicated things to add on the compiz list for next cycle :p [08:54] seb128: yeah, it's definitely not for next cycle that for sure [08:54] seb128: however, getting compiz to do the screenlocking is something we can do this cycle [08:54] smspillaz, btw in compiz gsettings in a ready to land state for UDS? [08:54] seb128: since I've already done it ;-) [08:54] would be nice to start by landing that early [08:54] seb128: should be. [08:55] smspillaz, noted for the locking, let's see at UDS what is the compiz list and make sure we don't overcommit [08:55] like if I had my say it would be gsettings and then bug fixing and stabilization for the cycle: p [08:56] hello [09:00] pitti, hi [09:00] hey tkamppeter [09:01] hey rodrigo_ [09:01] hi seb128 [09:09] pitti, seems that the reporter of bug 653132 has disappeared. Can you test it to verify whether it is fixed? On the desktop of a second account try the actions add printer, change options, delete printer and check whether the right things happen when canceling, entering nothing, wronmg, correct credentials, and whether, once correct credentials (the ones of the first user) are entered, the user is not asked for credentials any more un [09:09] til closing s-c-p. [09:09] Launchpad bug 653132 in system-config-printer ""Add Printer" dialog requests root password if user is not in Configure Printers group" [High,Fix committed] https://launchpad.net/bugs/653132 [09:11] tkamppeter: added to my todo list [09:12] pitti, thanks in advance. [09:22] * pitti fixes four year old bug 132904 [09:22] Launchpad bug 132904 in apport "Ignore crashes for programs which got updated in between the crash and reporting" [Medium,Fix committed] https://launchpad.net/bugs/132904 [09:23] pitti: that remidns me [09:24] pitti: is it possible to allow apport to still give you the backtrace (eg, install dbgsym, retrace locally and give it to you) even if you have some outdated packages ? [09:24] smspillaz: apport-retrace doesn't care about outdated packages, you can call that locally [09:24] ah awesome [09:24] smspillaz: oneiric's version even doesn't make a mess out of your workstation, it just works in a temp dir without any root rights [09:25] cool [09:25] yeah, I figured there must have been [09:25] smspillaz: http://www.piware.de/2011/08/apport-retrace-made-useful/ [09:25] since there's nothing more than "hey X crashed" "ooh, can I have a backtrace?" "nope, you have an outdated libnobodycaresabout" "FFFFUUUUU" [09:26] *more annoying than :) [09:26] pitti: <3 [09:27] smspillaz: if you actually want to report that, you can also run APPORT_IGNORE_OBSOLETE_PACKAGES=1 apport-bug /var/crash/... [09:27] (see man apport-bug) [09:27] :) [09:27] smspillaz: bug 75901 is on my precise agenda, too [09:27] Launchpad bug 75901 in apport "Integrate apport-retrace into GUI" [Wishlist,Triaged] https://launchpad.net/bugs/75901 [09:27] that should make it a lot more enjoyable for developers [09:28] pitti: in other news, I fixed the bug in compiz where the apport dialogs would come to the front and then not get focus and then you wouldn't be able to stack your other window on top of them unless you focused the apport dialog first [09:30] nice! I didn't see that for a while, though [09:31] seems current oneiric's version at least made this a whole lot less frequent [09:31] I get that bug often with update-manager [09:32] so yeah for fixing \o/ [09:32] i.e I often run it on an different workspace, click upgrade, go back to where I was and since it's a bit slow I get the "download" dialog on that ws [09:33] which often lands on front and not focussed [09:35] it was a one line typo [09:36] smspillaz, is the fixed in the sru uploaded today? [09:37] should be [09:45] pitti, hey could you please take a look at https://code.launchpad.net/~loneowais/python-distutils-extra/gobject-introspection [09:45] OwaisL: hello [09:45] Hi :) [09:45] OwaisL: that's on my radar, many thanks for this [09:46] Cool, thanks! [09:59] re [09:59] yeah, 'launcher not revealing" issues are fixed with the compiz sru ;-) [10:01] rodrigo_, btw if you didn't notice I'm filling your bug list regularly ;-) [10:02] seb128, yeah, I've seen it :) [10:02] rodrigo_, there are some bug fixes for oneiric but it's mostly next cycle work on g-c-c [10:03] seb128, which one do you refer to? [10:03] rodrigo_, bug fixing or next cycle? [10:03] for next cycle [10:04] rodrigo_, bug #869080 bug #845915 bug #742544 [10:04] Launchpad bug 869080 in ayatana-design "Launcher - Add launcher configuration option to System Settings Appearance dialogue" [Medium,Fix committed] https://launchpad.net/bugs/869080 [10:04] Launchpad bug 845915 in gnome-control-center ""All Settings" is confusing" [Wishlist,Confirmed] https://launchpad.net/bugs/845915 [10:04] Launchpad bug 742544 in gnome-control-center "Launcher is shown on the wrong screen in some multi-monitor setups" [High,Confirmed] https://launchpad.net/bugs/742544 [10:04] ok [10:05] rodrigo_, well it's basically the other items from the google doc we didn't have time for this cycle [10:05] ok [10:05] rodrigo_, i.e having the all settings in the g-c-c shell changed to be location aware, i.e all settings> region [10:05] the xrandr panel has well to be a bit more unity like visually [10:07] * Sweetshark just got the ultimate nerdshirt: GSoC2011 [10:17] rodrigo_, bug #845915 we could perhaps start by opening a bug on bugzilla about it? [10:17] Launchpad bug 845915 in gnome-control-center ""All Settings" is confusing" [Wishlist,Confirmed] https://launchpad.net/bugs/845915 [10:18] seb128, yes, I just want john to do the convincing, he knows better what he wants [10:18] but yes, I'll open the bug myself with his info [10:18] rodrigo_, good luck, design tend to be busy and not know "upstream" well [10:18] i.e I'm not sure that's going to happen [10:19] yeah, I know [10:19] but it's worth trying, you should probably discuss it directly on IRC with John though [10:19] it's a try to not have to be discussing with 2 design teams :) [10:19] not sure that the bug comment will be enough [10:19] seb128, yes, already waiting for him [10:19] ok [10:19] thanks [10:22] rodrigo_, oh, I've also dropped some bugs from your list now [10:22] rodrigo_, i.e g-s-d natty issues that I don't think we will work on now since natty is not a LTS and Oneiric is the current focus [10:22] cool [10:36] smspillaz, the fix for bug #748840 doesn't work or is not enough for the update-manager case [10:36] Launchpad bug 748840 in unity "Windows should not automatically be focused when opened if the focus is on another application" [Critical,Fix committed] https://launchpad.net/bugs/748840 [10:40] seb128: the update-manager case is probably different then === smspillaz is now known as smspillaz|d === MacSlow is now known as MacSlow|lunch === Riddelll is now known as Riddell [11:00] smspillaz|d, ok === smspillaz|d is now known as smspillaz [11:13] did we drop tsclient? [11:14] https://launchpad.net/ubuntu/oneiric/+source/tsclient [11:16] yes [11:17] https://launchpad.net/ubuntu/+source/tsclient/+publishinghistory [11:17] see the first line it has the reason [11:17] Debian bug #547314 [11:17] Debian bug 547314 in ftp.debian.org "RM: tsclient -- ROM: unmaintained, better alternatives" [Normal,Open] http://bugs.debian.org/547314 [11:18] remmina is the recommended option nowadays [11:18] * AlanBell installs [11:20] looks good [11:21] great ;-) [11:34] RAOF: around ? [11:34] actually [11:34] tseliot: around ? [11:34] smspillaz: sure, what's up? [11:35] tseliot: is there an nvidia-glx package thats supposed to exist ? I installed the binary driver to test something but it didn't seem to install nvidia's libgl [11:35] (I've got nvidia-current installed now) [11:35] (at least, I've noticed that I've still got mesa's libgl installed) [11:36] smspillaz: nvidia-current is the only package you need. what's the output of update-alternatives --display x86_64-linux-gnu_gl_conf ? [11:36] hang on [11:37] http://paste.ubuntu.com/705991/ [11:37] (don't see a libgl) [11:37] tseliot: I'm happy to install it from nvidia's website, though I understand that's a slightly more involved process these days [11:38] smspillaz: that would mean breaking your system [11:38] I figured [11:38] * smspillaz remembers the good old days where that actually worked [11:38] tseliot: any ideas then ? [11:38] smspillaz: what does "ldconfig -p | grep GL" say? [11:39] libGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-current/libGL.so.1 [11:39] hm, interesting [11:39] Error: couldn't find RGB GLX visual or fbconfig [11:39] <- at least that's what I get on a simple glxinfo [11:40] so I figure that maybe it's not loading that [11:40] * smspillaz tries LD_PRELOAD [11:40] ooook so it works with LD_PRELOAD [11:40] *shrug* good enough for me [11:41] smspillaz@XPS-UNITY:~$ ldd /usr/bin/glxinfo | grep GL libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f99863db000) [11:41] or I could jump symlink [11:41] *just [11:41] don't do that [11:42] tseliot: don't worry, I used arch linux, I'll be fine [tm] :) [11:42] smspillaz: I'm wondering what the X log says [11:42] tseliot: nothing particularly of interest there [11:42] (no WW or EEs [11:43] tseliot: I'll probably just export the LD_PRELOAD for now. used to switch graphics drvers around tons back in the day, should be fine [11:43] smspillaz: ok, it's still weird though [11:44] * tseliot -> lunch [11:45] tseliot: I compile tons of stuff from source, didn't expect it to all work :) [12:00] * rodrigo_ lunch === MacSlow|lunch is now known as MacSlow [12:33] popey: hey, how are you? did you see my question in bug 795475? [12:33] Launchpad bug 795475 in libimobiledevice "[iOS5 devices do not work] Unhandled lockdown error (-4)" [Undecided,Confirmed] https://launchpad.net/bugs/795475 [12:33] no pitti I hadn't [12:33] * popey looks [12:44]