=== lifeless is now known as subunit === subunit is now known as lifeless === eeejay is now known as eeejay_is_afk === zyga-afk is now known as zyga-really-afk [02:35] RAOF: RAOF You're on precise correct? Did you get this error when attempting to run schroot for the first time? E: Access not authorised [02:35] Hm, no I don't. [02:36] Hrm interesting. [02:36] I do however suffer from everything being unbootstrappable at the moment. Damn perl transition! [02:36] you do not have permission to access the schroot service. [02:36] heh right. [02:48] TheMuso: I use http://wiki.debian.org/sbuild as a guide, perhaps you need to sudo sbuild-adduser and then log out and back in [02:49] jbicha: see #ubuntu-devel, worked out the problem. [02:49] Thanks anyway. [02:49] jbicha: Oh and did that vte patch fix your keyboard issue? [02:49] TheMuso: yes, thank you! [02:51] np [02:51] It wasn't my patch, I just grabbit it and packaged it. :) [03:34] RAOF and robert_ancell , you guys have a few minutes for a phone call? [03:34] Yup. [03:36] thanks, RAOF , I'll wait for robert_ancell so we can get a conf call and do it all at once. [03:36] * RAOF goes to find his headset/mic [03:56] jasoncwarner_, hey, just came back [03:56] mumble? [03:56] RAOF: mumble work? [03:57] Allow me to install it… [03:58] RAOF: :/ ;) [03:59] * bryceh waves [04:00] Done. [04:01] RAOF robert_ancell in desktop [04:02] RAOF, microphone settings wrong? [04:02] Urgh. [04:16] RAOF, does X do anything with SIGUSR1? I was thinking we could hack up X to exit without clearing the screen on this signal if not to get the smooth switching working [04:16] I mean SIGUSR2 [04:17] robert_ancell: I don't think SIGUSR2 is used, no. [04:17] Using signals is pretty yuck, but not sure what else to do [04:17] Weren't we going to pass a parameter on startup to make it not clear on shutdown? [04:18] RAOF, yeah, but there is a risk there that when it comes to shutdown I want to you clear up as normal [04:18] or lightdm fails or something [04:18] Right. [04:19] RAOF, actually, do we need it at all? If I start a new X server and wait for the SIGUSR1 signal, then switch to it should there be any flicker? [04:19] Just whatever VT clearing X does normally. [04:20] RAOF, any idea what it does? [04:21] * RAOF plays “empirical testing” [04:22] Answer: there's is a flicker. [04:22] This could surely be eliminated, though. [04:22] but is it required when switching to a text terminal? [04:24] I'm uncertain. I wouldn't think so. [04:26] At least for kms drivers. [04:53] Good morning [04:53] bigon: yep, we discussed that a bit yesterday; most stuff will be blocked by current glib/gtk anyway, and that will land soon === jordan is now known as jordan_ [05:46] RAOF, I've drafted https://wiki.ubuntu.com/X/Blueprints/LtsPointUpdatesForXorg and think it covers everything we've talked about so far. You should probably look it over and add any noteworthy bits you can think of. [05:47] Good idea. [05:49] bryceh: That matches my recollection of the session. [06:01] RAOF, ok good [06:02] so I think the blueprints are all squared away now. === eeejay_is_afk is now known as eeejay [06:32] bryceh: https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-multi-monitor is still in "drafting" state, though} [06:32] ? [06:32] no, "discussion" [06:32] hmm that's not right, one sec [06:33] pitti, ok it's in review state now [06:33] ah, perfect; will look at it ASAP [06:35] ah, looks great, thanks [06:45] robert_ancell: hey Robert, how are you? [06:47] robert_ancell: Hm. Hey, could you confirm this VT switching behaviour? Switching to second or subsequent X servers involves a flash, but switching to the initial X server is seamless. [06:47] robert_ancell: How would I get lightdm to spawn the second and subsequent servers with “-background none”? [06:50] RAOF, oh, do they launch without that? I guess I need to fix the logic then [06:51] robert_ancell: I'm by no means certain that's the (a?) cause of the flashing, but it's an obvious difference between VT7 and the others. [06:52] RAOF, right, I'll investigate tomorrow, we might not need anything special (except when shutting down) [06:57] Hm, yeah. As long as we always log out by starting a server first, then switching to it. [07:05] good morning [07:07] bonjour didrocks [07:13] guten morgen pitti === eeejay is now known as eeejay_is_afk [07:22] RAOF: FYI, I'm looking at merging/syncing libraw; Debian experimental version uses lcms2 now [07:23] looks fine, syncing [07:59] bigon: I was just about to update json-glib, but now saw that you already did it in svn, but not uploaded; anything wrong with it? [08:19] good morning everyone === chrisccoulson_ is now known as chrisccoulson [08:19] hey chrisccoulson [08:19] hi didrocks, how are you? [08:19] chrisccoulson: feeling better than yesterday. Seems even to have a clear brain :) [08:19] and you? [08:21] didrocks, yeah, not too bad thanks. slowly recovering from my ubuflu :) [08:21] :) [08:21] hey chrisccoulson [08:21] chrisccoulson: urgh, still ubuflu? [08:21] hi pitti, how are you? [08:21] pitti, yeah, i've been really bad this time [08:35] Since I've upgraded to the 3.2 set, every time I go to join a new wireless network (ie, I'm a guest in this office today), I get prompted with the "System policy requires you to authenticate in order to change wireless settings" dialog. [08:35] I can only assume it's a policy kit thing, but I added myself to netdev and that didn't help. So I'm wondering what to poke. Any suggestions? [08:36] does ck-list-sessions have an active session for you? [08:45] pitti: checking [08:45] pitti: yes [08:50] morning [08:50] I'll try messing with pkcheck [08:51] AfC, do you have policykit-desktop-privileges installed [08:52] chrisccoulson: checking [08:53] chrisccoulson: _no_ [08:53] So, installing :) [08:53] AfC, that's probably why then :) [08:55] * AfC disconnects and retries [08:55] pitti: re json-glib: ENOTIME :) [08:55] I'll have a look at that today [09:03] chrisccoulson: that seems to have done the trick. Thanks! [09:19] bigon: I can help with build/test/upload if you want me to [09:19] bigon: I just didn't want to step on your toes [09:19] I'm looking at adding ma support [09:20] ah [09:20] pitti: platform sprint is 2012W02, right? [09:20] (good morning,btw) [09:20] hey desrt [09:20] desrt: yep, Jan 09 to 13 [09:20] thanks [09:21] hey bigon, desrt! [09:23] hm, versions.html doesn't get updated [09:23] * pitti checks [09:23] didrocks: good morning [09:25] being in europe makes it quite difficult to talk to robert! [09:26] indeed [09:27] is https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/762167 right? [09:27] Launchpad bug 762167 in light-themes "missing dependency on gtk2-engines-pixbuf" [Undecided,Confirmed] [09:38] hey [09:38] salut seb128, ça va ? [09:38] lut didrocks, ca va ? et toi ? [09:39] seb128: bien, au moins, j'ai un esprit clair aujourd'hui (et plus de fièvre ;)) [09:39] ;-) [09:39] !!!!! [09:40] hi french people :) [09:40] bonjour seb128 [09:40] hey pitti [09:40] hey chrisccoulson [09:40] how are you? [09:40] seb128: FYI, currently debugging why versions.py stopped updating [09:40] i'm good thanks, how are you? [09:40] pitti, when did it stop? [09:40] I did a couple of syncs/merges this morning, and it's out of date [09:40] chrisccoulson, I'm great, thanks [09:40] seb128: ast updated: Wednesday November 16 2011 20:22:50 +0000 [09:41] ok, weird [09:43] didrocks, seems pitti synced dee after all :p [09:43] sorry, was that wrong? we didn't have any more changes, and our package was in fact broken [09:43] we had a debian/patches/debian-changes [09:44] pitti: can you update the vcs as well, please? [09:44] pitti, we had the discussion a few weeks ago, the vcs is full source derivated from the upstream bzr [09:44] yeah, it will probably break it [09:44] pitti, that doesn't play well with direct syncs [09:44] ok, will update our vcs then [09:45] thanks [09:45] I'm still unsure what to do with those [09:45] if you just add the changelog, it should be fine for next iteration [09:45] libindicate is in the same case [09:45] libindicator as well I think [09:45] but if you copy the full source, we can have conflicts at next merge [09:45] didrocks: right, and drop debian-chagnes* (I suppose that's not even in the vcs, though) [09:45] pitti: no, it's not [09:46] pitti: debian-changes is because of cherry-pick upstream [09:46] bzr merge ../ [09:46] from trunk [09:46] so inline changes that are erased at next release by merge-upstream [09:46] but anyway, we told that we won't use source 3 anymore for those bzr-derived packages [09:46] ok, sorry for stomping over this [09:46] yeah, bzr cherrypick and source v3 lead to weirdness [09:47] pitti: no worry :) just update the debian/changelog and not the content itself as i'm afraid of conflicts at next resync [09:47] pitti, thanks for all the updates in Debian and sync! [09:47] de rien :) [09:47] I was in the mood this morning [09:47] currently updating libgnome-keyring [09:47] seb128: yeah, not quite readable for archive admins :/ [09:48] I checked libgnome, we can sync if we don't care about the changed background and sound theme settings [09:48] the latter might still be relevant though for GTK 2 apps [09:48] otherwise they might start producing sound effects again [09:48] I'm not sure whether that's libgnome directly or goes through g-s-d [09:49] pitti, I doubt we have a lot using libgnome still [09:49] we can sync and see if somebody complains [09:50] edubuntu still has it on their images [09:50] I thought "let's just ignore it and have it bitrot" [09:50] :) [09:51] works as well ;-) [09:51] hah [09:52] oh, I think chrisccoulson just volunteered for a few merges with his "hah" [09:52] chrisccoulson, right? ;-) [09:52] lol [09:52] oops, did i just volunteer for some more? ;) [09:54] didrocks: pushed [09:54] pitti: excellent, thanks! [09:54] chrisccoulson, no, no work for you until you get g-s-d fixed ;-) [09:54] * chrisccoulson hides [09:54] chrisccoulson, poke - is it fixed yet - poke -poke :p [09:54] does that still happen in precise? i didn't try suspending since i upgraded yesterday :) [09:55] lol [09:55] chrisccoulson, dunno, I don't suspend a lot at home and I'm still on Oneiric ;-) [09:55] one second, let me try [09:55] chrisccoulson, my tb indicator still get blued when there is no unread message left though! [09:55] I suspended yesterday, and it worked perfectly [09:56] in fact, it was the first time ever when suspend worked correctly with unity and an external monitor [09:56] before I had to ctrl+alt+f1 and -f7 [09:56] pitti: I've pushed my changes for json-glib, if you want to look at them : [09:56] seb128: versions.py> ah, there we go -- LP crash [09:56] :) [09:56] pitti, :-( [09:56] Getting LP bugs... [09:56] lazr.restfulclient.errors.HTTPError: HTTP Error 503: Service Unavailable [09:57] took awfully long, I assume timeout [09:57]

Timeout error

[09:57] yhep [09:57] hmmmm, the bogus battery on resume issue is fixed in precise [09:57] i probably shouldn't have upgraded yesterday ;) [09:57] actually [09:57] i could just use the old kernel :) [09:59] bigon: building locally, to check whether M-A: same is safe for the -dbg (sometimes it isn't) [10:01] seb128: I guess I can apply the same created_since='2011-08-01' trick that I did to apport [10:01] pitti: ah? I was not sure actually [10:01] pitti is on a sync frenzy ;-) [10:01] pitti, wfm [10:02] pitti: how can I check if -ma -dbg pkg are safe? [10:02] bigon: if they only have binaries in /usr/lib/x86.../, it's fine [10:03] bigon: but sometimes -dbg packages have e. g. /usr/lib/debug/usr/bin/foo [10:03] bigon: and these will collide [10:03] ah ok [10:03] bigon: bug not here, that looks fine [10:03] no /bin stuff in it [10:03] yep [10:03] bigon: thanks! [10:05] I'll upload it after my meeting, if you want to give it a functional test [10:10] bigon: seems to work fine here === zyga is now known as zyga-afk [10:22] ah! http://people.canonical.com/~platform/desktop/versions.html [10:22] seb128: ^ [10:24] pitti, \o/ [10:35] * pitti fixes the libunique FTBFS, sorry about that [10:36] LP is down, but the error messages have become much nicer! [10:36] pitti, what error messages? [10:37] seb128: try opening LP [10:37] you see the recent status messages now [10:37] which is really helpful [10:38] ah right [10:41] it's so tempting to move the Conflicts: bamfdaemon (<= 0.2.92-0ubuntu1), libzeitgeist-gio, wncksyncdaemon from libglib2.0-0 to some other package like gvfs or zeitgeist or what not, and sync glib2.0 [10:43] but oh well, I think I'll stop my update/merge/sync mania now and move to lunch and apport :) [10:43] pitti - no, don't remove those :-) [10:43] those packages are quite disruptive if they remain installed ;) [10:44] as i found out last cycle === seif is now known as seifstrup [10:46] gah, launchpad, COME BACK NOW [10:46] chrisccoulson: [not sure if you saw] yes, your solution of installing missing policykit-desktop-privileges has fixed the problem. Thanks! [10:46] AfC, excellent :) [10:47] chrisccoulson: no, not remove -- move to some other package [10:47] chrisccoulson: we need to keep them until after precise indeed [10:48] pitti - ah, ok. i guess that could make sense [10:51] unity/3d is even usable [10:51] but bug 891116 affects my work too often ;( [10:51] hrw: Error: Could not parse data returned by Launchpad: HTTP Error 503: Service Unavailable (https://launchpad.net/bugs/891116) [10:52] pitti, we will not sync glib long, we want 2.31 [10:54] hrw, seems you are the only one to get it, did you tweak your compiz config? [10:55] AfC: stop that. you're making me dizzy. :p [10:55] * AfC hands desrt a glass of water [10:55] particularly since chrisccoulson is on both places :p [10:55] heh [10:55] hmmm [10:56] desrt, stop drinking! [10:56] or drink water [10:56] seb128: but it's coffee [10:56] The following packages have been kept back [10:56] icedtea-netx icedtea-plugin [10:56] isn't that not meant to happen these days? :-P [10:56] desrt, no coffee for you anymore, you had enough! [10:56] it's only my second cup today [10:56] then it's ok ;-) [10:56] i haven't had any! [10:57] but i have had nearly a whole bottle of pepsi max [10:57] chrisccoulson, use dist-upgrade? [10:57] seb128, yeah, that's what i'm using ;) [10:57] not sure pepsi is better than coffee [10:57] yeah, i don't think it's any better [10:58] oh [10:58] launchpad is back! [10:58] i can feel my stomach dissolving away as we speak [10:58] probably should go and make coffee :) [10:58] * desrt sticks with the coffee [10:58] seb128: still no 2.31.0? bad hacker. [10:59] desrt, I was sort of waiting for the eog issue to be fixed [10:59] it is. [10:59] did they not do a release yet? [10:59] hah, icedtea-netx : Depends: icedtea-netx-common but it is not installable [10:59] E: Package 'icedtea-netx-common' has no installation candidate [10:59] iirc they pushed my patch... [10:59] who broke the icedtea package?? :) [10:59] desrt, no they didn't [11:00] chrisccoulson, doko? [11:00] desrt, http://git.gnome.org/browse/eog/commit/?id=ee4f6b27027421ee1e7cb14948f587da83171668 ? [11:00] yes [11:00] seb128, oh, seems he actually fixed it already [11:00] probably that commit should have also bumped the glib depend [11:01] i guess i just need to wait for the publisher [11:01] desrt, so taking that commit on glib 2.30 will lead to issues? [11:01] actually [11:02] yup. [11:02] seb128: in short: i completely buggered it up [11:03] seb128: I did [11:03] i consider the old behaviour to be a very bad bug, and eog's previous code to be a workaround for that mistake [11:03] now the bug is fixed and the workaround _must_ be removed in order for eog to continue working [11:03] which sucks a lot [11:03] but it is as it is [11:03] desrt, I hope we don't have many applications workarounding the old bug :p [11:04] seb128: it only happens when you use gdkthreads [11:04] seb128: ccsm is needed even to set launcher size (32px) and amount of desktops (1x6) [11:04] seb128: and afaik, eog is the only app that i've heard of having trouble with the new glib [11:04] (after we fixed the 2 other actual bugs) [11:04] desrt, yeah, right, we already had those discussions ;-) [11:05] desrt, I'm just pondering what to do with eog and glib now, I guess I will make the new glib breaks eog << before-patch and eog depends on >> new-glib [11:05] seb128: so i don't need to hope :p [11:05] seb128: yes. that's correct. [11:05] sorry for the bumpy ride with glib lately [11:05] fwiw, i expect it to continue to be bumpy in these sorts of ways [11:05] no worry [11:05] small little issues here and there [11:05] that's less cool [11:06] i don't go out of my way to cause problems [11:06] I hoped we would be over the bumpy part of the road ;-) [11:06] well [11:06] with respect to threading, we are [11:06] but who knows what needs to be beaten on next [11:06] desrt, hi [11:06] keep working on gsettings and gmenumodel and we are fine :p [11:06] i'm just saying that if i see a situation like this again in the future, i will probably do the same thing agian [11:07] seb128, hey [11:07] hello ricotz [11:07] and not say "we have to keep it working the broken way" [11:07] ricotz: good morning [11:07] desrt, right [11:07] desrt, well I guess we are mostly fine for this cycle now [11:07] seb128: probably. [11:07] which is what I care about at the moment ;-) [11:07] desrt, seems like problem with the threading tests locking up is getting worse again [11:07] ricotz: the one i was trying to blame on glibc? [11:08] hmm, the one running on a very old kernel [11:08] maybe we can blame the kernel this time :) [11:08] like the launchpad builders running [11:09] which testcase deadlocked? [11:09] one sec [11:09] chrisccoulson, versions says that firefox 9 isn't buddy with armel and powerpc in precise [11:09] i assume this is with the glibc fix already applied? [11:10] TEST: gdbus-threading... (pid=10533) [11:10] heh [11:10] i suspect that's our bug [11:10] s/our/davidz's/ [11:10] ok ;) [11:10] desrt, did you get my post in #gtk+? [11:10] he was making some comments the other day that he's not sure if the testcases are threadsafe [11:10] which is pretty ... unfortunate [11:11] seb128, not sure why, but the armel build was killed 10 hours in [11:11] and powerpc is known broken, but i don't care about that ;) [11:11] ricotz: i did. i didn't understand the problem. [11:11] chrisccoulson, yeah, it seems like somebody rm-ed the build tree [11:11] i wish people would tell me when they kill a build [11:11] it's not causing glib to fail to build...? [11:11] i have no idea why :/ [11:15] hmmm, i'm blocked on https://answers.launchpad.net/launchpad/+question/179038 now. perhaps this is a sign to fix seb128's bugs [11:15] \o/ [11:16] brb, need to switch to the old kernel [11:18] cyphermox, hello :), do you noticed some new fallouts with iwl4965 like having a very untable wlan connection and microcode crashes === davmor2_ is now known as davmor2 [11:44] are there chances to get old alt-tab switching behavior back for 12.04? [11:44] the new switcher looks incredibly awesome... but... [11:45] i constantly loose windows because i fail to notice i want to switch between windows of the same app [11:45] also my little finger starts to hurt since the ~ key's stoke is much smaller than the tab key's stroke on my thinkpad [11:46] so i really develop some resistance to press alt-~ [11:46] another problem: when i accidentally pressed alt-tab instead of alt-~ i now have to tab back to get the window picker to open [11:46] since alt-tab already went to the next window [11:46] it's just not nice. [11:47] despite the gorgeous look [11:48] tbf: hey, I guess those kind of discussions should happen rather on the ayatana mailing list where designers are (I guess there is also #ubuntu-design channel now) [11:50] didrocks: ok, another list to subscribe. :-D [11:50] thanks you anyway. [11:50] yw :) [11:51] tbf, you can re-enable the old switcher in ccsm if you don't like the modern workflow ;-) [11:52] seb128: oh, you can? where? [11:52] tbf, just unset the keybindings for the unity one in the unity ccsm options [11:53] seb128: also i am not generally against change.... actually i love unity (and tell everyone) [11:54] only think that this change was a miss step... maybe there is a reason the old alt-tab behavior got adopted quickly and then didn't get challenged for decades... ? ;-) [11:54] tbf, you can unset the keybinding and activate the static switcher then [11:54] ...checking [11:54] tbf, I'm not sure to understand what your issue is with the new one [11:54] guess i'll also loose the awesome presentation, i guess? [11:55] yes, you will be back to the old compiz code [11:56] seb128: first of all i don't see the use case. why do i want to distinguish at all? what's the benefit encouraging to learn this? [11:56] what is to learn? [11:56] seb128: second i get a huge penalty for using the wrong key [11:56] seb128: when to press alt-tab and when alt-~ [11:56] you can use alt-tab all the time [11:56] just pause on an icon, it will display the different instance [11:57] the delay is a bit long, that's a known issue and will be fixed this cycle [11:57] seb128: no, you cannot. because when you press alt-tab, the focus already went to the next application [11:57] no it doesn't? [11:57] I can press alt-tab, hit esc and keep typing here [11:57] seb128: so you cannot easily alt-tab between two browser windows, mail compositor and message list, and so on [11:58] well you couldn't before either [11:58] the old switcher didn't sort "by application" [11:58] I would argue it's easier to do with the new one since you get a specific keybinding for that [11:59] note that you can change the keybinding in ccsm if you don't like the default one [12:00] seb128: just tried again: switched to evolution. pressed reply button. once the composer appeared i press alt-tab and end in xchat, instead of the message list [12:00] seb128: when i keep tab pressed, then also xchat gets focused === MacSlow is now known as MacSlow|lunch [12:01] that seems a bug [12:01] so to select the message list i'd have to move back and wait until the view zooms [12:02] the "by application" thing is a bit annoying sometimes yes :-( [12:02] hum lunch is ready [12:02] bbiab [12:03] tbf, I'm not saying the new one is perfect btw, some things are nicer some are confusing [12:03] there are some bugs as well that will be fixed this cycle [12:04] maybe caused by the "bias current view port setting"? [12:05] after disabling that setting, alt-tab returns me to the message list [12:05] so maybe "bias current view port" must be done differently? [12:06] seb128: what's the deadline for bugfixes? must decide when to look at this [12:06] or if i'll just file a bug for now [12:06] pitti: do you know which dbus version we'll ship for P? [12:07] kamstrup: well, "know" is a strong word; but unless we have a really strong reason to go to 1.5, 1.4.x [12:07] well... maybe let's file a bug first anyway. [12:07] kamstrup: I don't know whether there will be more bug fix releases after .16, but I guess that wouldn't make a difference? [12:08] pitti: right, it's not a huge deal - but there is some unity stuff that *might* be affected by upgrading to 1.5.6 or later [12:08]