[00:21] <desrt> mterry: http://paste.ubuntu.com/809211/
[00:21] <desrt> mterry: that's base64'd xz'd text
[00:23] <mterry> desrt, got it
[00:23] <desrt> i did a brief check that there is no key material in there
[00:23] <desrt> if i'm wrong, please let me know :)
[00:24] <mterry> desrt, error indeed says "bad key"  (I was expecting a more esoteric gpg error, since we treat them all the same and maybe something weird was going on).  This looks like you're not using the same key
[00:25] <mterry> desrt, did you enter in the password each time before, or did you have DD remember the password?
[00:26] <desrt> i entered it each time
[00:26] <desrt> but i'm rather certain that i'm getting it correct
[00:26] <desrt> could it be that somehow the key-hashing algorithm changed between versions of DD/duplicity/gpg?
[00:27] <mterry> desrt, I don't believe so.  Certainly not in DD/duplicity.  gpg's default symmetric algorithm is CAST5 I believe
[00:27] <desrt> very very odd.
[00:27] <mterry> I would be surprised if that changed?  Maybe it does between distros?
[00:27] <desrt> i use the same passphrase as the harddrive encryption password for my laptop
[00:27] <desrt> so i'm rather certain i haven't forgotten it
[00:27] <desrt> and it started happening exactly when i switched to ubuntu
[00:28] <mterry> desrt, one thing you could do is take DD/duplicity out of the loop
[00:28] <mterry> desrt, and decrypt a file directly
[00:28] <mterry> let me look up the line
[00:28] <mterry> gpg --multifile --decrypt duplicity-full.20110127T131352Z.vol1.difftar.gpg (for example)
[00:28] <mterry> desrt, ^
[00:29] <desrt> will that leave the original untouched?
[00:29] <mterry> desrt, yeah it will make a non-.gpg file
[00:29] <mterry> that's what the --multifile does (as well as allowing multiple arguments)
[00:31] <desrt> yup.  that worked on the server using what i believe to be my passphrase
[00:31] <desrt> let me copy it over to an ubuntu machine and try
[00:31] <desrt> also works on ubuntu
[00:33] <mterry> OK, so good...
[00:33] <mterry> So that makes me think that we are trying to decrypt either a corrupted local copy or passing the wrong passphrase to duplicity
[00:34] <desrt> perhaps i should blow away my .cache?
[00:34] <mterry> desrt, Sure.  Move it away, and let's see if that helps.
[00:35] <desrt> no help
[00:35] <desrt> very odd
[00:35] <desrt> gonna eat dinner now
[00:35] <desrt> back in a bit
[00:35] <mterry> k
[00:39] <mterry> desrt, next thing to do is to take duplicity out of the equation and run "/usr/bin/duplicity --exclude=/home/desrt/jhbuild --exclude=/home/desrt/.mozilla/firefox/default/Cache --exclude=/home/desrt/.cache --exclude=/home/desrt/Downloads --exclude=/home/desrt/.local/share/Trash --exclude=/home/desrt/.xsession-errors --exclude=/home/desrt/.thumbnails --exclude=/home/desrt/.gvfs --exclude=/home/desrt/.adobe/Flash_Player/AssetCache --exclude=/home/
[00:39] <mterry> desrt/.cache/deja-dup --exclude=/home/desrt/.cache --include=/home/desrt --exclude=/sys --exclude=/proc --exclude=/tmp '--exclude=**' --dry-run --gio --volsize=25 / sftp://velocity.lan/home/desrt/backup/moonpix --verbosity=9 --gpg-options=--no-use-agent --archive-dir=/home/desrt/.cache/deja-dup"
[00:58] <desrt> mterry: christ...
[01:01] <desrt> mterry: so i figure that it may be the case that somehow one of the files in this directory has a different key than the rest
[01:02] <mterry> desrt, did that command work?
[01:02] <desrt> mterry: no.
[01:02] <desrt> gpg: decryption failed: bad key
[01:02] <desrt> [01:03] <mterry> desrt, the most recent manifest file
[01:04] <mterry> is the one kicking up the error
[01:08] <desrt> mterry: let me check
[01:09] <desrt> mterry: indeed
[01:09] <desrt> mterry: the most recent manifest fails to decrypt
[01:09] <desrt> mterry: also worth noting that it's a full (not incremental backup)
[01:09] <desrt> i have a theory: perhaps i fat-fingered the password on the last successful backup and because it was a full backup, it didn't need to decrypt any of the incrementals
[01:10] <desrt> ie: any password would be allowed
[01:10] <mterry> desrt, that's a good theory
[01:10] <desrt> probably should add some extra checks for that
[01:12] <desrt> meanwhile i'm just gonna blow away my backup dir and start over
[01:19] <mterry> desrt, yeah, a check would be good.  I think most users just click 'remember password' so it's less of an issue
[01:20] <desrt> i sort of like the password dialog
[01:20] <desrt> it gives me a chance to stop the backup if it's a bad time
[01:20] <desrt> or plugin to wired if i'm on wifi
[01:20] <mterry> desrt, note that the notification will let you delay/skip the backup too
[01:21] <mterry> but yeah
[01:21] <desrt> ya... it doesn't really hang around, though
[01:24] <mterry> desrt, it doesn't?  i thought gnome shell kept it
[01:26] <desrt> maybe?
[01:26] <desrt> i think the backup goes ahead without waiting, though?
[01:26] <desrt> to be honest, i guess i don't really know
[01:28] <desrt> i'll see what happens next time :)
[01:31] <mterry> desrt, it does go ahead.  but it'll take a few minutes before the backup actually start as it begins with a file scan
[01:32] <mterry> plus, if it does start and you stop it, no big deal
[01:32] <desrt> good to know
[01:54] <desrt> mterry: do you want a bug?
[01:54] <mterry> desrt, sure
[01:57] <desrt> https://bugs.launchpad.net/deja-dup/+bug/918489
[01:57] <ubot2> Launchpad bug 918489 in deja-dup "dejadup allows bad passphrase on full backup" [Undecided,New]
[02:01] <mterry> desrt, thx!
[04:16] <robert_ancell> RAOF, does this look like an X issue? https://launchpadlibrarian.net/84275438/DSCN0231.JPG  (it's two X servers running on different monitors, see bug 885394)
[04:16] <ubot2> Launchpad bug 885394 in unity-greeter "Greeter screen resolution too small for USB monitors (multiseat)" [Undecided,New] https://launchpad.net/bugs/885394
[04:18] <RAOF> robert_ancell: Possibly?
[04:19] <robert_ancell> RAOF, well, I'm about to assign it to you guys.  As I don't pick the resolution it's either a misconfigured X or the X server is not reporting the correct values to unity-greeter
[04:19] <RAOF> Yeah, that seems likely.
[04:20] <RAOF> The gnome-settings-daemon error message suggests that something's trying to set a resolution of 1x1, so there's *something* broken somewheer :)
[04:20] <robert_ancell> yeah, it could be g-s-d of course :/
[05:17] <BigWhale> Good morning.
[05:36] <pitti> Good morning
[05:36] <pitti> tkamppeter: thanks, pulled cups
[07:14] <didrocks> good morning
[07:15] <didrocks> hey RAOF, I tried to start my kernel with iommu=no, but as before, the nvidia driver is loaded, but I can't access to my second display (got the same error than yesterday when starting nvidia-settings)
[07:15] <RAOF> Hm.
[07:15] <RAOF> Log time!  /var/log/Xorg.0.log is the first candidate.
[07:16] <pitti> hey didrocks
[07:16] <didrocks> guten morgen pitti
[07:16] <didrocks> RAOF: the candidate is here: http://paste.ubuntu.com/809403/, I repeat the candidate is here :o)
[07:19] <RAOF> Hm.  And what does starting nvidia-settings say?
[07:19] <didrocks> RAOF: it's totally insulting me with http://paste.ubuntu.com/809407/ :)
[07:21] <RAOF> Aaah.  Hm.
[07:21] <RAOF> I don't really have much to say.  It looks like the nvidia driver just isn't probing your outputs correctly? /-?
[07:22] <RAOF> Oooh, time to leave for dinner.
[07:22] <didrocks> RAOF: enjoy
[07:23] <didrocks> I should then just restart on older kernel?
[07:23] <didrocks> (this started with monday's upgrade)
[07:25] <RAOF> Does it work on an older kernel?
[07:26] <didrocks> RAOF: I tried on the previous kernel (I think we just had one update recently), and unfortunatly, it didn't
[07:27] <didrocks> ohoh nvidia-current:i386 (285.05.09-0ubuntu1, 290.10-0ubuntu1)
[07:29] <RAOF> We may have a winner there :){
[07:29] <RAOF> (Now *really* dinner)
[07:29] <didrocks> RAOF: for some sort of "win", indeed :)
[07:29] <didrocks> RAOF: enjoy, trying to downgrade now
[07:29] <pitti> didrocks: are you actually running i386?
[07:30] <didrocks> pitti: yes
[07:30] <didrocks> shocking, isn't it? ;)
[07:30] <pitti> yeah, I thought most devs ran 64 bit
[07:31] <rickspencer3> hi pitti and didrocks, good morning
[07:31] <pitti> bonjour rickspencer3, ca va?
[07:31] <rickspencer3> ca va bien, et toi?
[07:31]  * rickspencer3 turns off French responder bot
[07:31] <didrocks> bonjour rickspencer3
[07:31] <rickspencer3> pitti, didrocks easy travels back from BP?
[07:32] <didrocks> rickspencer3: yeah, was uneventful :)
[07:32] <didrocks> how was the opera?
[07:32] <pitti> rickspencer3: je sui bien, merci! still cooling my cheek, but the tooth pulling went pretty well
[07:32] <rickspencer3> didrocks, the opera was really cool
[07:32] <rickspencer3> pitti, tooth pulling? did I miss something?
[07:32] <pitti> rickspencer3: yeah, had a calm train ride; frankly, I think on the two train rides I got more stuff done than in the whole week in between ;)
[07:33] <pitti> rickspencer3: got two wisdom teeth pulled out, was about time
[07:33] <pitti> the other two in a few weeks
[07:33] <rickspencer3> pitti, well, I hope the procedures go without too much pain!
[07:33] <didrocks> pitti: are you still eating at the banana level or you are able to start eating something more consistent?
[07:34] <pitti> didrocks: had some potatoes with zucchini yesterday :) (soft cooked, of course)
[07:34] <didrocks> :)
[07:34] <didrocks> rickspencer3: did you like Vienna, is it a nice city?
[07:34] <pitti> still being cautious, but don't worry, I won't starve
[07:34] <didrocks> heh ;)
[07:34] <pitti> rickspencer3: ah, you went to Vienna? nice
[07:34] <rickspencer3> didrocks, from the little that I saw, I thought Vienna was quite nice
[07:34] <pitti> rickspencer3: we spent a couple of days there in summer 2010, gorgeous city
[07:35] <rickspencer3> pitti, didrocks well, it was solid meetings early morning to late evening (if you include our dinners)
[07:35] <didrocks> ok, so you couldn't really enjoy the city…
[07:35] <pitti> both architecturally, culturally (Hundertwasser, Prater), and of course you just gotta love their cuisine and all those huge deserts they are making
[07:35] <pitti> rickspencer3: ah, too bad; QBR or so?
[07:35] <didrocks> pitti: it's on my personal list of city to visit. Thanks for confirming it worths it :)
[07:36] <rickspencer3> pitti, it was old managers meeting with new managers to try to quickly induct them
[07:36] <pitti> didrocks: http://piware.de/fotos/Donauradtour-Sep10/, 32 onwards
[07:36] <pitti> didrocks: it was the end of our bike tour along the Danube, we spent three days there
[07:40] <ricotz> jbicha, ping
[07:40] <didrocks> pitti: looks really nice, indeed :)
[07:41] <pitti> didrocks: we spent a whole day in Schönbrunn alone (the castle), it has a huge garden with a zoo etc.
[07:41] <smspillaz> didrocks: I fixed the opacity bug
[07:41] <smspillaz> not sure if someone has approved my merge yet though
[07:42] <BigWhale> Latest Oneiric updates broke my app ...
[07:42] <didrocks> pitti: waow, a zoo in a castle?
[07:42] <BigWhale> I think.
[07:42] <pitti> didrocks: well, not in the building, just in the area
[07:42] <didrocks> smspillaz: you proposed a merge against 4.0 and trunk?
[07:42] <didrocks> pitti: ah ok ;)
[07:42] <smspillaz> yes
[07:42] <pitti> didrocks: that's a whole suburb by itself
[07:43] <didrocks> interesting
[07:43] <pitti> didrocks: we also went to the castle kitchen where they demoed how they make the famous Apfelstrudel
[07:44] <didrocks> smspillaz: https://code.launchpad.net/~smspillaz/unity/unity.fix_912682/+merge/89109 and https://code.launchpad.net/~smspillaz/unity/4.0_fix_912682/+merge/89114, isn't it,
[07:44] <didrocks> pitti: oh, this is not specific to Berlin, there is a Vienna favor?
[07:44] <pitti> didrocks: Berlin?
[07:45] <smspillaz> https://code.launchpad.net/~smspillaz/unity/4.0_fix_912682/+merge/89182
[07:45] <smspillaz> yes
[07:45] <didrocks> smspillaz: you can merge https://code.launchpad.net/~smspillaz/unity/4.0_fix_912682/+merge/89182 to 4.0? As the trunk version was accepted…
[07:45] <pitti> didrocks: it origins from Vienna; perhaps you are mixing it up with the "Berliner", which is like more doughnut-like?
[07:46] <smspillaz> great
[07:46] <didrocks> pitti: oh, I was not well informed then, I guess agateau told me that Apfelstrudel was typical of Berlin ;)
[07:46] <pitti> didrocks: http://en.wikipedia.org/wiki/File:Berliner-Pfannkuchen.jpg is the Berliner
[07:46] <didrocks> pitti: incoming SRU fix ^
[07:47] <didrocks> pitti: no, it wasn't that
[07:47] <pitti> didrocks: ah, please build with -v to include the previous changelog
[07:47] <didrocks> pitti: with great pleasure!
[07:47] <didrocks> smspillaz: ping me once merged!
[07:47] <didrocks> smspillaz: thanks a bunch for the fix :)
[07:47] <smspillaz> oh, there's another fix for another regression too
[07:47] <smspillaz> hang on
[07:48] <smspillaz> or rather, it wasn't really a regression, just weird behaviour exposed by some other code
[07:48] <smspillaz> but it has a bug report and all
[07:48] <didrocks> https://code.launchpad.net/~smspillaz/unity/unity.fix_881190_918360/+merge/89181 ?
[07:48] <smspillaz> yep
[07:48] <smspillaz> you're sharper than me :)
[07:49] <didrocks> smspillaz: hum, but that's not a regression, so can be in a further SRU. Let's try to only fix the first one
[07:49] <didrocks> wdyt?
[07:49] <smspillaz> I don't think we've gotten any reports on that yet, but I think it can be tripped over
[07:50] <smspillaz> didrocks: its a regression from the fix to make sure that all windows don't unminimize when closing one of them
[07:50] <smspillaz> "regression"
[07:50] <didrocks> smspillaz: yeah, nobody got it from now and as we want to release the SRU soon (and I didn't get this case in trunk as well), I think it's safer to separate them
[07:51] <smspillaz> ok
[07:51] <smspillaz> errr
[07:51] <smspillaz> didrocks: ok. We'll need to revert the fix to make sure that all windows don't unminimize when you close one thats minimized then
[07:52] <smspillaz> since this crash is definitely easy to reproduce by doing that in this case
[07:53] <didrocks> smspillaz: it's already reverted in 4.0
[07:53] <smspillaz> it isn't
[07:53] <smspillaz> dbarth reverted the wrong thing
[07:53] <didrocks> dbarth did it
[07:53] <didrocks> urgh
[07:53] <smspillaz> yeah, he didn't get the right revision
[07:53] <didrocks> he reverted 2 commits
[07:53] <smspillaz> he reverted the one to make it so that opening a window didn't unshowdesktop
[07:53] <smspillaz> really ?
[07:53] <smspillaz> hmm
[07:54] <didrocks> yeah, IIRC
[07:54] <didrocks> smspillaz: so the crash is easy to reproduce? at the time, you told it was a rare race ;)
[07:54] <smspillaz> different crash
[07:54] <smspillaz> which was actually a hang
[07:54] <smspillaz> and I'm not sure what the status of that is since I still can't reproduce it, but at least with this merge it shouldn't enter those codepaths anymore
[07:55] <smspillaz> I never got a full trace for that, so I'll never know
[07:55] <didrocks> anyway, mterry tried the SRU proposed and couldn't reproduce the crash, same with seb
[07:55] <didrocks> and they got it 100% of the time before
[07:55] <didrocks> so, let's try to keep the impact minimal
[07:55] <didrocks> and just have your additional fix
[07:56] <smspillaz> hang on
[07:56] <smspillaz> didrocks: ok, so
[07:58] <smspillaz> didrocks: he didn't revert the one that was causing the bug
[07:58] <smspillaz> or at least, it says in the logs he did, but I know for a fact that's not the offending commit :)
[07:59]  * didrocks sigh
[07:59] <smspillaz> didrocks: so what to do: unrevert the revert and revert the right one, or just revert the right one and leave the other one reverted
[08:00] <smspillaz> didrocks: that would be 1722
[08:02] <didrocks> pitti: ok, let's advise for relaunching a 7-day testing period then
[08:02] <didrocks> smspillaz: unrevert the revert and revert the right one please
[08:02] <didrocks> smspillaz: then, look if we got the bugs # right
[08:03] <didrocks> smspillaz: please add a test case too to https://bugs.launchpad.net/unity/+bug/912682
[08:03] <ubot2> Launchpad bug 912682 in unity/4.0 "Compiz add transparency to titlebar along with the panel" [High,In progress]
[08:04] <smspillaz> ok
[08:04] <smspillaz> didrocks: that would essentially mean that the showdesktop one hasn't received any testing, but I guess with 7 days it will be tested again
[08:05] <didrocks> smspillaz: do you have the bug #?
[08:05] <smspillaz> yes, hang on
[08:05] <smspillaz> Fixes LP #871801 and LP #899932
[08:05] <ubot2> Launchpad bug 871801 in unity "window management, alt-tab - After using 'show desktop' to minimise all windows, opening any new window also incorrectly restores all the minimised windows " [High,Confirmed] https://launchpad.net/bugs/871801
[08:05] <ubot2> Launchpad bug 899932 in unity "Raising an app from launcher after ctrl+alt+d raise all other apps (dup-of: 871801)" [Medium,Triaged] https://launchpad.net/bugs/899932
[08:05] <didrocks> yeah, it's not tested yet: http://people.canonical.com/~ubuntu-archive/pending-sru.html
[08:06] <smspillaz> fun. leave it reverted then ?
[08:06] <didrocks> smspillaz: no, as we reset for 7 days, we can keep it
[08:06] <didrocks> I told dbarth to not do the SRU that particular days…
[08:07] <smspillaz> didrocks: ok, I'll unrevert that and revert the other one
[08:07] <didrocks> smrevertaz: thanks
[08:09] <smrevertaz> didrocks: hmm, I'm rusty on my bzr foo. if I wanted to revert 1722 that would be bzr merge -r1723..1722 right ?
[08:10] <smrevertaz> it just says that nothing changed if I do that, but the diff suggests otherwise
[08:10] <didrocks> smrevertaz: I think it's bzr merge -r 1722..1721 rather
[08:10] <smrevertaz> that reverts a bunch of other stuff
[08:10] <smrevertaz> then again, this is a merge commit
[08:10] <didrocks> you want to go from rev 1722 to rev 1721
[08:10] <smrevertaz> I'll try and find the individual revision
[08:10] <didrocks> normally I bzr diff to confirm
[08:11] <smrevertaz> indeed, bzr diff show the right thing, but then actually doing the merge changes other things
[08:12] <smrevertaz> I miss the ability to do git revert foo
[08:34] <Sweetshark> moin!
[09:13] <tjaalton> new lightdm doesn't let me in
[09:14] <tjaalton> console login is fine
[09:17] <didrocks> just saw someone else on the french forum blaming the new unity-greeter as well
[09:17] <tjaalton> another user account is fine
[09:17] <didrocks> just the guest account worked apparently
[09:18] <didrocks> you have another account working, just the id=1000 oesn't?
[09:18] <tjaalton> didrocks: right
[09:18]  * didrocks takes his netbook and upgrade
[09:19] <tjaalton> auth.log shows auth error from pam_unix, which is weird
[09:19] <didrocks> maybe we should raise the revert policy :)
[09:21] <seb128> hey
[09:21] <didrocks> salut seb128, ça va?
[09:21] <seb128> lut didrocks, nickel, et toi?
[09:21] <tjaalton> how does the account service figure out the background of a user account?
[09:21] <tjaalton> just thinking how well it works with networked drives
[09:21] <didrocks> seb128: ça va :)
[09:21] <didrocks> tjaalton: I think you can disable it
[09:22] <tjaalton> didrocks: ok good
[09:22] <seb128> tjaalton, g-c-c write it there when you change your background
[09:22] <seb128> that's an option as well as didrocks said
[09:22] <tjaalton> still thinking of those poor admins at the uni :)
[09:22] <tjaalton> options are good
[09:22] <seb128> ;-)
[09:22] <agateau> seb128: hey, my favorite lightdm packager!
[09:22] <seb128> lut agateau
[09:23] <seb128> did you find new ways to break lightdm today? ;-)
[09:23] <agateau> of course!
[09:23] <didrocks> yeah, seems it's broken :)
[09:23] <agateau> seb128: I noticed two problems with current lightdm package...
[09:23] <didrocks> (well, unity-greeter is)
[09:23] <seb128> didrocks, oh? segfault? I didn't install the new one yet but the ppa version worked for me
[09:24] <seb128> agateau, hit me!
[09:24] <agateau> seb128: liblightdm-qt has been renamed upstream from liblightdm-qt-1 to liblightdm-qt-2, I suppose packages should be renamed
[09:24] <seb128> DOH
[09:24] <didrocks> seb128: 2 people (one on the french forum and tjaalton) reports that they can't log in with their main acount
[09:24]  * Sweetshark thanks his inet provider for given him his daily disco right after the "g'morning" on IRC was send out.
[09:24] <seb128> didrocks, due to the greeter update today? or due to lightdm update yesterday?
[09:25] <seb128> didrocks, does it work for anyone? /me updates...
[09:25] <didrocks> seb128: I don't know, on the french forum, they blame unity-greeter
[09:25] <didrocks> seb128: I'm upgrading my netbook right now
[09:25] <didrocks> (can't reboot on my laptop)
[09:25] <seb128> it's a bit weird because the greeter doesn't handle authentification I think
[09:25] <Sweetshark> Exciting news: LibreOffice 3.4.5 available for oneiric from the PPA!
[09:25] <seb128> tjaalton, ^
[09:25] <didrocks> seb128: they may be wrong, can be lightdm :)
[09:25] <seb128> didrocks, it would be less of a surprise ;-)
[09:26] <seb128> didrocks, it's only one account they can't log in? i.e other accounts work?
[09:26] <tjaalton> yep, uid 1001 works
[09:26] <tjaalton> at least here
[09:26] <didrocks> seb128: seems t be userid=1000, but need to confirm
[09:26] <didrocks> to*
[09:26] <didrocks> on the french forum, the guy has a guest account and can log with it
[09:27] <tjaalton> guest login works here too
[09:27] <tjaalton> seb128: also, login from the console works with the "main" account
[09:28] <seb128> tjaalton, can you add your lightdm.log after a failed login? did it start with the lightdm update from yesterday? or the greeter update today?
[09:31] <tjaalton> seb128: http://paste.ubuntu.com/809478/
[09:32] <tjaalton> failing and a successful one after that
[09:33] <seb128> tjaalton, did you update unity-greeter yet?
[09:33] <seb128> tjaalton, so failing and working on the same user right?
[09:33] <seb128> [+1.58s] DEBUG: pam_start("lightdm", "tjaalton") -> (0x24aa120, 0)
[09:34] <seb128> [+1.58s] DEBUG: pam_set_item(0x24aa120, 3, ":0") -> 0 (Success)
[09:34] <seb128> [+1.58s] DEBUG: pam_authenticate(0x249f050, 0) -> 7 (Authentication failure)
[09:34] <seb128> was that autologin?
[09:34] <tjaalton> this is with the new unity-greeter yes
[09:34] <tjaalton> no different users
[09:34] <tjaalton> note how the other one has a failure as well
[09:34] <tjaalton> auth fail
[09:34] <seb128> yeah
[09:35] <tjaalton> no autologin
[09:35] <seb128> tjaalton, did you have the issue yesterday? i.e with the new lightdm but without unity-greeter?
[09:35] <tjaalton> didn't login then
[09:36] <tjaalton> trying the old greeter
[09:36] <seb128> thanks
[09:36] <tjaalton> had it on the local mirror :)
[09:36] <tjaalton> yep, wokrs
[09:36] <tjaalton> works
[09:37] <seb128> weird
[09:39] <seb128> oh
[09:40] <seb128> tjaalton, didrocks: be careful, by default the new unity-greeter gives you an english keymap
[09:40] <seb128> which might lead to enter wrong passwords
[09:40] <didrocks>  seb128: oh, that's maybe the issue there
[09:40] <seb128> I've to type qwerty
[09:40] <seb128> or to use the indicator to select a french keymap
[09:40] <tjaalton> ahah
[09:40] <seb128> I reported the issue to mterry and robert_ancell at the rally
[09:41] <didrocks> I bet a lot of people won't be able to log in then
[09:41] <seb128> didrocks, can you follow up on the forum asking if they use the indicator to set the keyboard back to french if that works?
[09:41] <didrocks> seb128: yeah, doing that now
[09:41] <seb128> didrocks, well, the greeter as a keyboard selector
[09:41] <agateau> hiding the password is not user friendly, we should make it clear text!
[09:41] <seb128> but yeah, it's confusing
[09:41] <seb128> agateau, ;-)
[09:41] <seb128> agateau, what is your second bug? do you want to fix the soname one?
[09:41] <seb128> agateau, I can review, sponsor your work
[09:42] <agateau> seb128: I sent you a MR for it already
[09:42] <agateau> seb128: the second bug is that we have no more source package for lightdm-gtk-greeter
[09:42] <rickspencer3> chrisccoulson, what should I do with a chromium crash report that someone logged? is there someone to assign it to?
[09:42] <seb128> lol, poor chrisccoulson ;-)
[09:42] <agateau> seb128: it has been moved to another project, but there is no packaging branch for it
[09:43] <seb128> agateau, ok, great, reviewing it in a bit
[09:43] <seb128> agateau, right, did robert roll a tarball? are you interested to package it?
[09:43] <agateau> seb128: if you apt-get source lightdm-gtk-greeter, you get lightdm source code, which does not contain the greeter anymore
[09:43] <rickspencer3> chrisccoulson, oh dang, it's private too :/
[09:43] <rickspencer3> seb128, I'm not going to assign it to him, I just want to know what to do with it
[09:43] <rickspencer3> seb128, any ideas?
[09:43] <seb128> rickspencer3, "nothing", we don't have a chromium maintainer
[09:44] <agateau> seb128: there is a tarball, I can look into packaging it
[09:44] <seb128> rickspencer3, recommend the user to run firefox or chrome
[09:44] <seb128> agateau, \o/ I'm happy to sponsor that for you
[09:44] <rickspencer3> seb128, okay, I'll just drop in that note
[09:44] <tjaalton> seb128: changing to fi worked for me
[09:44] <seb128> tjaalton, excellent
[09:44] <tjaalton> should use the system default though
[09:44] <chrisccoulson> rickspencer3, i'm not sure. i don't think anybody is watching chromium bug reports
[09:45] <rickspencer3> chrisccoulson, ok, thanks
[09:45] <tjaalton> XKBLAYOUT from /etc/default/keyboard
[09:45] <chrisccoulson> it's hard enough keeping on top of the 1000's of open firefox and thunderbird bug reports ;)
[09:45] <seb128> didrocks, tjaalton: https://bugs.launchpad.net/bugs/915468
[09:45] <ubot2> Launchpad bug 915468 in lightdm "the unity-greeter keyboard's selection doesn't respect the user config" [Undecided,New]
[09:46] <chrisccoulson> amyway, good morning desktop team :)
[09:46] <seb128> hey chrisccoulson, how are you? I hope today is less ping crazy that yesterday for you ;-)
[09:46] <seb128> though it seems it started before you said hi :p
[09:46] <chrisccoulson> seb128, yeah, i might sign out of IRC for a bit ;)
[09:47] <chrisccoulson> or open my IRC client on another machine
[09:47] <seb128> chrisccoulson, just turn off notify-osd and indicator integration
[09:47] <seb128> and let it sit on its own workspace
[09:48] <chrisccoulson> ah, that's quite a good idea
[09:50] <tjaalton> seb128: confirmed and bumped the priority
[09:51] <seb128> tjaalton, thanks
[10:04] <didrocks> pitti: pushed the new SRU with the additional fix + the revert of revert + the real revert of the crash. Done!
[10:07] <agateau> we put reverts in your revert so you can revert while reverting
[10:07] <mvo> pitti: is there a way to ask cups if there is a configured printer? I'm working on the HW profile code for s-c currently and it seems (given network printers and such) its more relevant to know if there is a configured printer than a actually attached printer
[10:09] <didrocks> agateau: I'm just reverting what you are telling :)
[10:09] <agateau> didrocks: to much recursivity for me, my brain stack is full!
[10:09] <agateau> *too
[10:10]  * didrocks flushes
[10:10] <agateau> :)
[10:10] <pitti> mvo: yes, libcups has nice APIs for that; simplest is to call lpstat -p
[10:10] <didrocks> ok, rebooting now that I downgraded nvidia, let's see if I can get back my second monitor :)
[10:10] <pitti> mvo: there should be some d-bus API these days, too, let me check
[10:11] <mvo> pitti: oh, sweet
[10:11] <pitti> mvo: hm, can't find it on d-bus
[10:12] <mvo> pitti: no worries, lpstat -p if fine
[10:12] <mvo> pitti: I also found python-cups that I check out now
[10:12] <pitti> mvo: that'd works, too, of course
[10:15] <mvo> thanks a bunch!
[10:17] <didrocks> RAOF: so, downgrading fixed it. How can I help you reporting the issue to nvidia?
[10:19] <pitti> mvo: btw, is there still a chance to get a new apt by alpha-2, to avoid the multiarch breakage for upgrades?
[10:19] <pitti> or too many problems in trunk?
[10:21] <mvo> pitti: its a bit of a hole currently, most stuff is fixed now, but the new handling of dpkg in debian broke it for us
[10:21] <mvo> pitti: I *think* I can just revert that change and we should be good
[10:21] <pitti> mvo: new handling of dpkg?
[10:21] <mvo> pitti: well, the debian dpkg expects different args than the ubuntu one (for multiarch packages)
[10:21] <pitti> we have the same dpkg version as sid
[10:22] <mvo> pitti: rather unfortunate
[10:22] <pitti> oh
[10:22] <mvo> pitti: right, but sid does not do multiarch at all
[10:22] <mvo> pitti: but its a good point, we are >< close, so I think I have a look at reverting this one commit for now
[10:23] <pitti> mvo: thanks so much
[10:25] <chrisccoulson> hmmm, why do only finnish people need to install a separate extension for spell checking in firefox?
[10:29] <pitti> chrisccoulson: I think it's because libvoikko does some clever things about picking apart the grammar, presumably Finnish needs that much more than other languages
[10:29] <chrisccoulson> ah, ok
[10:29] <pitti> i. e. a mere dictionay comparison would give poor results
[10:29] <pitti> IANAFS, of course :)
[10:29] <chrisccoulson> yeah, i was just curious
[10:30] <chrisccoulson> i wonder how unpopular i would be if we made finnish people install mozvoikko from addons.mozilla.org instead?
[10:30] <pitti> chrisccoulson: if that happens automatically, it should not have any visible change?
[10:30] <pitti> chrisccoulson: I thought that's what that bug was all about
[10:31] <pitti> I certainly think it's the right thing to migrate that plugin, too
[10:31] <chrisccoulson> pitti - ah, we're only doing that for lucid and maverick though
[10:32] <pitti>  mozvoikko | 2.0.1-0ubuntu1 |       precise | source, all
[10:33] <pitti> chrisccoulson: ^ it seems precise is now arch:all (was any until oneiric), a new version, and  still in the archive
[10:33] <pitti> chrisccoulson: doesn't that work with ffox 9/10 any more?
[10:34] <pitti> chrisccoulson: but aside from this, if you plan to remove the extension from teh archive, how hard would it be to apply the migration for upgrades to precise and further as well? we might always remove move extensions in teh future, after all
[10:34] <chrisccoulson> yeah, that's a good point. there isn't really a migration path if we remove an extension from the archive
[10:35] <chrisccoulson> i'd prefer to not support my addon migration code for 5 years though. it was already a bit of a pain to make it work right ;)
[10:36] <pitti> chrisccoulson: would it be more robust to only keep it for a whitelisted set of addons? precise might then have mozvoikko only
[10:37] <pitti> chrisccoulson: so for LTS->LTS upgrades you rely on people installing firefox 10 on lucid first, and doing the migration there? (seems ok to me)
[10:49] <RAOF> didrocks: You can run nvidia-bug-report.sh and attach it to a bug; then ping Alberto :)
[10:49] <didrocks> RAOF: should I run the buggy package version for this?
[10:49] <RAOF> didrocks: Yes
[10:50] <didrocks> RAOF: ok, will do it later then! Thanks :)
[10:51] <seb128> RAOF, hey, there is a new colord upstream version showing on version if you feel bored and want to update it in Debian some day ;-)
[10:52] <RAOF> seb128: Yup, saw it; I'm subscribed to the list.
[10:52] <seb128> ok, great
[10:52] <RAOF> I'll get around to it sometime.  Maybe the weekend.
[10:52] <seb128> RAOF, did you have a nice trip back btw? I think I didn't say hello yet this week
[10:52] <RAOF> Oh, you've not heard of my awesome trip back?
[10:53] <seb128> RAOF, no!
[10:53] <RAOF> As I say, it was *fantastic*
[10:53] <RAOF> I got upgraded to Business from Singapore to Melbourne, which was very nice.
[10:53] <seb128> oh, nice, so actually good ;-)
[10:54] <RAOF> Of course, this was after QF10 was delayed for 13 hours in Heathrow, so we spent the night in a crappy hotel outside the airport, and then because it was late I missed the last plane to Hobart and so spent Monday night in a much nicer hotel in Melbourne.
[11:01] <ricotz> seb128, hello
[11:01] <seb128> RAOF, doh, so yeah, they partially made up for what they screwed ;-)
[11:01] <seb128> hey ricotz
[11:02] <ricotz> seb128, i think as long no main package needs a newer clutter/cogl we should keep 1.8.x for now
[11:02] <ricotz> seb128, 1.9.4 was released but has huge issues
[11:02] <seb128> ricotz, oh why? (it's fine with me but you usually push for the newest crack ;-)
[11:03] <seb128> ok, good to know
[11:03] <ricotz> also updating cogl will result in a whole transtion which needs to get every package using clutter to be rebuilt
[11:03] <seb128> I'm happy to stay on 1.8, I don't think we will have any need to update soon
[11:03] <ricotz> so if 1.9.x will be an option i would be happy to update it only once
[11:04] <mvo> heh :) sane-find-scanner thinks my phone is a scanner - fun!
[11:04] <ricotz> seb128, what i mean libs like libcogl5 and libcogl7 are co-installable but breaking each other
[11:05] <ricotz> seb128, i guess i will add this flag to the packaging to prevent having two versions
[11:06] <ricotz> seb128, i am not sure if cheese or gnome-games will need it though
[11:06] <seb128> ricotz, co-installable but breaking each other -> not nice
[11:06] <ricotz> (a newer clutter i mean)
[11:06] <seb128> let's see
[11:07] <seb128> we can figure it out if,when they do
[11:07] <ricotz> seb128, yeah, app build against an older cogl running with a newer clutter are seqfaulting
[11:08] <Sweetshark> ricotz: seen the LO3.4.5 updates? I subscribed you to the bug as you were not on IRC
[11:08] <ricotz> seb128, so i guess it is better to still wait some time
[11:08] <ricotz> Sweetshark, yeah, thanks
[11:09] <ricotz> Sweetshark, btw, why arent you using the debian tarballs?
[11:09] <Sweetshark> @all: <general note>I will be on vacation for two weeks starting tomorrow evening. So anything urgent should be discussed until then.</general note>
[11:09] <ricotz> Sweetshark, ... instead of patching it to the new version
[11:10] <Sweetshark> ricotz: better to debdiff and review for SRU if there is no "hidden" change"
[11:10] <ricotz> Sweetshark, hmm, i see
[11:11] <ricotz> seb128, could you take care of https://bugs.launchpad.net/ubuntu/+source/clutter-gst/+bug/918574 ?
[11:11] <ubot2> Launchpad bug 918574 in clutter-gst "Sync clutter-gst 1.4.6-1 (main) from Debian unstable (main)" [Undecided,New]
[11:12] <seb128> ricotz, can do yes
[11:12] <ricotz> thanks
[12:06] <seb128> lunch, bbiab
[12:21] <Sweetshark> pitti: uploading 3.4.5-0ubuntu1 for oneiric-proposed to chinstrap ....
[12:41] <chrisccoulson> hmmm, another week, another firefox and thunderbird release
[12:42] <Sweetshark> pitti: done. but I first want to check the identical ppa release for the l10n in calc formulas bug ...
[12:43] <seb128> chrisccoulson, they like to keep you busy ;-) though I guess it's mostly trivial packaging work between those versions?
[12:44] <chrisccoulson> seb128, yeah, mostly. the packaging work is done a few weeks in advance ;)
[12:45] <seb128> Sweetshark, the calc non localized function names bug is still not fixed? be careful, you might get an user riot at your door ;-)
[12:47] <pitti> Sweetshark: so want me to wait with reviewing/accepting until you are done with that?
[12:47] <Sweetshark> seb128: it was fixed with the ppa build package and then broke again with the SRUed version but from the exact same source package ...
[12:47] <Sweetshark> pitti: yes
[12:47] <pitti> ack
[12:48] <seb128> Sweetshark, seems like a side effect of pkgbinarymangler or something?
[12:48] <pitti> that only removes .mo files and some documentation, though; not sdf files
[12:48] <seb128> Sweetshark, did you try to do a ppa build with a build-depends on pkgbinarymangler and see if that screws it?
[12:49] <seb128> pitti, what else is different between ppa and archive builders?
[12:49] <pitti> not that much; pkg-create-dbgsym, different kernel
[12:49] <Sweetshark> pitti: https://launchpad.net/~libreoffice/+archive/ppa/+build/3103553 <- ppa build, ETA: rsn
[12:50] <pitti> a binary debdiff might show more?
[12:50] <seb128> Sweetshark, what binary has those translated function names?
[12:50] <pitti> i. e. compare the .debs from the PPA and oneiric-propsoed
[12:52] <seb128> I will try to have a look see if I can figure something
[12:52] <pitti> seb128: any reason that librsvg was updated in ubuntu only, and not in debian?
[12:52] <seb128> that bug really sucks, it seems it's a blocker for some schools or public offices deployments in non english countries
[12:53] <seb128> pitti, I'm still unsure what Debian is doing with GNOME 3.3
[12:53] <seb128> they are still working in 3.2
[12:53] <pitti> oh, is 2.35 a GNOME 3.3 thing?
[12:53] <seb128> but I guess it could go to experimental
[12:54] <seb128> pitti, yes
[12:54] <Sweetshark> seb128, pitti: if the ppa l10n build is good, IMHO we should upload the oneiric-proposed one. but we should check it for the error before verification-done.
[12:54] <pitti> Sweetshark: right, and run debdiff to see whether any files are missing in the ubuntu build
[12:56] <seb128> Sweetshark, what binary is involved in the calc functions translations? i.e where should I look for errors or differences?
[12:57] <Sweetshark> seb128: libsc*.so, I guess ..
[12:58] <seb128> Sweetshark, the translations are in the .so?
[12:58] <Sweetshark> seb128: ah, no.
[13:02] <Sweetshark> seb128: its in one of forde.res foruide.res scde.res in /usr/lib/libreoffice/basis3.4/program/resource
[13:04] <seb128> Sweetshark, ok, I will try to have a look, it's still buggy in precise
[13:05] <seb128> Sweetshark, it's not a nice bug for Ubuntu since it's basically a stopper for deployments in non english speaking countries
[13:05] <seb128> Sweetshark, seems we start having some bad press around it for taking months to not fix it :-(
[13:06] <Sweetshark> seb128: huh? I checked on the last precise upload and didnt see the problem there.
[13:08] <seb128> Sweetshark, using SOMME(1;2) in my calc returns a #NAME?
[13:08] <seb128> Sweetshark, using SUM works
[13:09] <seb128> but I will check my install maybe I'm missing a langpack or something
[13:11] <Sweetshark> seb128: works here with the build from the ppa for oneiric
[13:11] <Sweetshark> seb128: works here with on precise ...
[13:11] <seb128> Sweetshark, ok, probably a local issue, I will try on a clean install ;-)
[13:12] <Sweetshark> seb128: although maybe I have local packages installed on precise.
[13:12] <seb128> Sweetshark, let me try with a fresh install and come back to you
[13:12] <Sweetshark> seb128: k
[13:16] <Sweetshark> seb128: I would really hope this not to show up in precise anyone as we have no seperate -l10n source package anymore.
[13:17] <seb128> Sweetshark, it was due to the 10n? the fact that the same build works in a ppa and is buggy in oneiric-proposed makes me think it could be something on the builders...
[13:20] <Sweetshark> seb128: I havent found the root cause. But doing two builds with different configure flags and hoping stuff copied from one to the other would work was never an supported upstream scenario.
[13:26] <Sweetshark> pitti: anyway as the 3.4.5 ppa build looks good l10n-wise (and precise is a independant story), pls upload to oneiric-proposed ...
[13:28] <seb128> hey mterry, had a nice trip back?
[13:28] <mterry> seb128, yeah, it was fine
[13:28] <mterry> seb128, how you doing?
[13:29] <seb128> good, I got over my ubuflu ;-)
[13:31]  * Sweetshark was ubunflufree this time (and had some real good time on saturday night in Budapest)
[13:31] <Sweetshark> (well, Sunday morning)
[13:31] <seb128> lucky you ;-)
[13:32]  * mvo is almost recovered from ubuflu
[13:34] <Sweetshark> seb128: completely reinstalled libreoffice on precise, still works
[13:36] <seb128> Sweetshark, ok, you should probably close bug #873702 then ;-) I will tell you how it works for me once I'm done with my reinstall
[13:36] <ubot2> Launchpad bug 873702 in libreoffice "some function names in Calc appear in english others in local language (mixed up) " [High,Fix committed] https://launchpad.net/bugs/873702
[13:39] <davidcalle> Hello desktop folks. I'm looking for Alvaro Lopez Ortega (alobbs, I believe), do you know when he will be around?
[13:53] <pitti> Sweetshark: uploaded
[13:54] <Sweetshark> seb128: the formula names are in for<lang>.res and are thus used from from libforl<platform>.so
[14:02] <seb128> Sweetshark, ok, you are right, works fine on precise
[14:05] <Sweetshark> wtf? LibreOffice 3.5 is still building on armel (for six days now) ...
[14:06] <pitti> Sweetshark: perhaps it does build all the l10n stuff there?
[14:06] <Sweetshark> pitti: nope
[14:06] <Sweetshark> pitti: hmm
[14:07] <micahg> you have about 550MB of compressed sources...seems to make sense
[14:08] <seb128> Sweetshark, ok, I can confirm that "libreoffice-l10n 1:3.4.4-0ubuntu1" in oneiric-proposed is buggy
[14:08] <seb128> but 1:3.4.5-0ubuntu1~ppa1 is fine
[14:27] <pitti> hey cyphermox, good morning
[14:27] <cyphermox> pitti:  hey
[14:27] <cyphermox> good morning
[14:28] <pitti> cyphermox: I was recently reviewing the pm-utils hooks, and found this gem: /usr/lib/pm-utils/sleep.d/55NetworkManager
[14:28] <cyphermox> fun
[14:28] <pitti> cyphermox: it dbus-sends network-manager to sleep and wakeup before suspend/after resuming
[14:28] <pitti> cyphermox: that looks like an ancient hack to me, do you happen to know if it's still needed?
[14:29] <cyphermox> I think it is
[14:29] <pitti> cyphermox: it doesn't even seem to work any more
[14:29] <seb128> Sweetshark, do you know how are "for<lang>.res" build?
[14:29] <cyphermox> afaics it' s what would tell NM to not turn the interfaces completely off or something, I'd need to revisit the code though
[14:29] <pitti> cyphermox: there are no sleep and wake methods, just a Sleep(boolean)
[14:30] <cyphermox> pitti: no?
[14:30] <seb128> Sweetshark, the oneiric-proposed version indeed has only english words where the ppa version is correct
[14:30] <cyphermox> ah, guess you may be right, but it' s not breaking things either so far
[14:30] <pitti> cyphermox: anyway, I'll run some more thorough tests for this
[14:30] <cyphermox> shouldn' t we be seeing a failed in the pm-utils logs?
[14:30] <Sweetshark> http://www.webupd8.org/2012/01/libreoffice-345-available-to-install-in.html <- woha, now that was quick!
[14:31] <pitti> Having NetworkManager put all interaces to sleep...Failed.
[14:31] <pitti> cyphermox: ^
[14:31] <pitti> Having NetworkManager wake interfaces back up...Failed.
[14:31] <pitti> cyphermox: which made me ask whether we should fix the hook, or just get rid of it, as apparently NM is getting by just fine
[14:32] <pitti> cyphermox: at least I never had a problem with wifi or eth not reconnecting after suspend; did you see that in bug reports?
[14:32] <pitti> cyphermox: and running the sudo dbus-send command gives me
[14:32] <pitti> Error org.freedesktop.DBus.Error.UnknownMethod: Method "sleep" with signature "" on interface "org.freedesktop.NetworkManager" doesn't exist
[14:33] <pitti> cyphermox: so I wanted to just drop the hook and avoid wasting cycles, unless you say that we should fix it instead?
[14:34] <cyphermox> pitti:  we should just get rid of it, yes
[14:34] <pitti> cyphermox: ack, thanks
[14:34] <cyphermox> was that shipped by pm-utils?
[14:34] <pitti> it still is
[14:34] <pitti> fixing it in debian git now
[14:34] <cyphermox> ok
[14:35] <pitti> s/fixing/dropping/
[14:48] <Sweetshark> pitti: for bug 917153 i will try to create a fixed package still, but even if I upload that tomorrow, I wouldnt be around to fix stuff
[14:48] <ubot2> Launchpad bug 917153 in libreoffice "failed to upgrade from oneiric to precise: /usr/lib/libreoffice/program/unopkg.bin: error while loading shared libraries: libicule.so.48: cannot open shared object file: No such file or directory" [High,Confirmed] https://launchpad.net/bugs/917153
[14:49] <pitti> Sweetshark: so, tomorrow is your last day, and then 14 days skiing?
[14:49] <Sweetshark> pitti: hmm, I mean bug 916726 which is likely the same root cause anyway ...
[14:49] <ubot2> Launchpad bug 916726 in libreoffice "Drop extra Java dependencies from 3.5.0~beta2-2ubuntu3" [High,Triaged] https://launchpad.net/bugs/916726
[14:49] <Sweetshark> pitti: yes
[14:50] <pitti> Sweetshark: uh, these two don't seem closely related?
[14:50] <Sweetshark> pitti: so the alpha2 milestone can really hold reasonably.
[14:51] <seb128> didrocks, ok, https://launchpad.net/~ubuntu-desktop/+archive/daily has nux and unity rebuilt with glew1.6
[14:51] <Sweetshark> pitti: I would propose I do a ppa upload and leave it to your discretion to include that into main
[14:51] <Sweetshark> (while I am gone)
[14:51] <didrocks> seb128: unity needed the rebuilt at the end?
[14:51] <seb128> didrocks, so I upgraded my box, removed libglew1.5, and works fine
[14:52] <didrocks> seb128: ok, I'm testing on my netbook
[14:52] <seb128> didrocks, yes, it has a depends on libglew1.5 and I wanted to remove the lib from my system to be sure
[14:52] <didrocks> (intel)
[14:52] <didrocks> seb128: you know what, just sent an email, perfect timing!
[14:52] <seb128> chrisccoulson, pitti, mterry, cyphermox: testing of https://launchpad.net/~ubuntu-desktop/+archive/daily would be welcome
[14:52] <seb128> it's basically precise unity rebuilt with glew1.6
[14:53] <seb128> it was buggy some cycles ago but we want to try again, seems the issues got fixed since, at least it worked for me with that version
[14:53] <pitti> seb128: adding/upgrading
[14:54] <seb128> pitti, danke
[14:54] <Sweetshark> pitti: and yes, I think they are related: there is a postinst in -common script using unopkg (which is in -common). however unopkg is a wrapper script around unopkg.bin (from -core), so this cant work out because -core depends on -common. Because of the wrong order in executing postinsts various things can go wrong (missing a lib, or missing the infra to determine the language)
[14:55] <pitti> Sweetshark: right, but that seems unrelated to pulling in extra dependencies like -java-common
[14:55] <Sweetshark> pitti: doh!
[14:55] <Sweetshark> pitti: E_TOO_MANY_BUGS
[14:56] <didrocks> hum, 404 on the ppa, interesting
[14:56] <mterry> seb128, sure
[14:56] <seb128> Sweetshark, ok, I stop there, I will wait for the proposed build and diff build logs, the for<lang>.res are buggy confirmed by running "strings" on them, it seems like they didn't import the translations on the builders for some reason
[14:56] <seb128> didrocks, wfm
[14:57] <didrocks> weird :/ tried 3 times
[14:57] <seb128> didrocks, typoed the source?
[14:57] <Sweetshark> pitti: bug 916291 and 917153 are likely dupes. bug 916726 should be rather quickly fixable indeed.
[14:57] <ubot2> Launchpad bug 916291 in libreoffice "failed to upgrade from Oneiric to Precise: ERROR: Cannot determine language! - exit status 134" [High,Confirmed] https://launchpad.net/bugs/916291
[14:57] <ubot2> Launchpad bug 917153 in libreoffice "failed to upgrade from oneiric to precise: /usr/lib/libreoffice/program/unopkg.bin: error while loading shared libraries: libicule.so.48: cannot open shared object file: No such file or directory" [High,Confirmed] https://launchpad.net/bugs/917153
[14:57] <ubot2> Launchpad bug 916726 in libreoffice "Drop extra Java dependencies from 3.5.0~beta2-2ubuntu3" [High,Triaged] https://launchpad.net/bugs/916726
[14:57] <didrocks> seb128: I add-apt-repository
[14:57] <didrocks> seb128: and it gave me the ppa info
[14:58] <seb128> mterry, btw some user "fail to log in" with the new unity-greeter (turned out they got confused by the wrong keyboard layout)
[14:58] <didrocks> oh
[14:58] <didrocks> oneiric
[14:58] <didrocks> I'm on precise, wth?
[14:58] <seb128> didrocks, mvo's bug? ;-)
[14:58] <mterry> seb128, well, it's so pretty now that I'm sure they didn't mind staying in the greeter longer.  :)  hmm, how did it go wrong?
[14:58] <mterry> bug numbers?
[14:58] <didrocks> seb128: yeah, maybe :)
[14:59] <seb128> mterry, well same bug that the one I complained about at the rally, somewhat the greeter keyboard indicator default to "en" rather than the system or user layout
[14:59] <seb128> mterry, bug #915468
[14:59] <ubot2> Launchpad bug 915468 in lightdm "the unity-greeter keyboard's selection doesn't respect the user config" [High,Confirmed] https://launchpad.net/bugs/915468
[15:00] <mterry> seb128, oh right
[15:00] <seb128> mterry, it's easy to work around once you notice that your keyboard layout is wrong, it's just that most users type their password and don't look at the screen
[15:00] <mterry> right
[15:00] <seb128> so they go "wth, login stopped working"
[15:05] <didrocks> ok, it seems to be working well ;)
[15:05] <seb128> didrocks, \o/
[15:05] <didrocks> and definitively that hardware failed before
[15:06] <seb128> didrocks, do you want to upload that so we don't mix that change with another transition or compiz,unity updates?
[15:06] <didrocks> seb128: my netbook has the same card as your netbook, not sure if you tested there or your laptop
[15:06] <didrocks> seb128: definitively
[15:06] <seb128> didrocks, I tested on my laptop (i5 integrated video)
[15:06] <didrocks> let's wait for pitti's result
[15:06] <didrocks> ok, so we will have at least 3 cards (and one at least, failed before)
[15:06] <seb128> which had the issue as well in the past
[15:06] <didrocks> oh 2 then :)
[15:06] <pitti> restarting my desktop session to test the glew1.6 builds
[15:09] <nessita> mterry: THANK YOU (I've been waiting on that sponsorship for over a month!)
[15:09] <didrocks> oh krita is in main and still depends on 1.5
[15:09] <mterry> nessita, :)
[15:10] <seb128> didrocks, well I guess it's not for a good reason
[15:10] <seb128> i.e simple rebuild should do
[15:10] <didrocks> seb128: no, probably just a rebuild
[15:10] <didrocks> yep
[15:10] <seb128> didrocks, I don't like that pitti is not coming back :p
[15:11] <didrocks> yeah, same here :/
[15:11] <didrocks> or maybe he just playing fun with us :)
[15:15] <didrocks> let's say he's hit by the unity-greeter issue and don't think about changing its keyboard :)
[15:15] <didrocks> his*
[15:20] <pitti> seb128, didrocks: utter fail here, need some time to crawl out of that
[15:20] <pitti> seb128: might not be the glew thing, though
[15:20] <pitti> both lightdm and sessino are totally black
[15:20] <seb128> pitti, did you update anything else?
[15:20] <pitti> yes, some things
[15:20] <pitti> gdk-pixbuf trigger segfaulted
[15:21] <seb128> if it's happening on lightdm so it's likely not unity
[15:21] <pitti> and trying to reinstall it, apt says "no filename"
[15:21] <pitti> on text console now, trying to find my way out of this
[15:21] <seb128> urg
[15:21] <seb128> well I guess if the gdx-pixbuf trigger segfaulted you go no image loader working
[15:21] <seb128> which might lead to lightdm and session to be unhappy
[15:22] <pitti> yes
[15:22] <pitti> seb128: when I dpkg -i that binary, it consistently segfautls
[15:22] <didrocks> doesn't sound pleasing :/
[15:22] <pitti> do you get this as well?
[15:22] <seb128> pitti, which one? gdk-pixbuf?
[15:22] <pitti> seb128: oh, I bet it's due to the new librsvg
[15:23] <seb128> pitti, try downgrading librsvg2-common? or rm /usr/lib/arch/...svg.so
[15:23] <didrocks> sounds a possible guilty guy, indeed :)
[15:23] <pitti> seb128: yes, I'll do that once I'm back
[15:23] <pitti> I need to go to the dentist again, back later this evening
[15:23] <pitti> then I'll re-test the PPA
[15:24] <pitti> seb128: in the meantime, perhaps you can investigate and revert librsvg?
[15:24] <pitti> it's certainly a "omg total failure" case
[15:24]  * pitti -> off
[15:24] <seb128> pitti, see you
[15:25] <seb128> pitti, well "wfm"
[15:25] <seb128> so I would like to see if anyone else get the issue
[15:25] <seb128> could others try the librsvg2 update?
[15:25] <didrocks> pitti: see you, hope you don't get more hurt
[15:25] <didrocks> seb128: doing
[15:26] <seb128> didrocks, thanks
[15:29] <didrocks> rebooting see you soon (or not!) :)
[15:35] <seb128> didrocks, \o/
[15:35] <didrocks> seb128: wfm
[15:35] <seb128> pfiou
[15:35] <seb128> i386 or amd64?
[15:35] <didrocks> indeed, pfiou ;)
[15:35] <didrocks> i386
[15:35] <seb128> somebody on amd64? ;-)
[15:35] <seb128> chrisccoulson, mterry, cyphermox, ?
[15:35] <didrocks> yo uare on amd64, isnt it?
[15:35] <seb128> no
[15:35] <seb128> but pitti is
[15:35] <didrocks> oh?
[15:36] <mterry> i386
[15:36] <chrisccoulson> hi seb128
[15:36] <didrocks> I was thinking you were only eating amd64 :)
[15:36] <seb128> chrisccoulson, mterry: could you guys update your librsvg and make sure it doesn't make the gdk-pixbuf trigger segfault?
[15:36] <seb128> it did for pitti and made his machine un-usable, the "no loader" break the greeter and the desktop it seems
[15:37] <seb128> just trying to see if that's amd64 specific or pitti specific (he had to run to the dentist)
[15:37] <chrisccoulson> seb128, you're asking me to deliberately break my machine? ;)
[15:37] <seb128> chrisccoulson, I'm providing you entertainment! you were complaining about how stable precise is ;-)
[15:37] <cyphermox> seb128: sure, soon
[15:37] <chrisccoulson> ok, upgrading now
[15:37] <cyphermox> seb128: about the update to daily, right?
[15:38] <seb128> cyphermox, could you guys update your librsvg and make sure it doesn't make the gdk-pixbuf trigger segfault?
[15:38] <seb128> cyphermox, but I welcome unity testing as well
[15:38] <ricotz> seb128, oh really, is librsvg breaking things? :\
[15:39] <seb128> ricotz, <pitti> seb128, didrocks: utter fail here, need some time to crawl out of that ... gdk-pixbuf trigger segfaulted
 seb128: when I dpkg -i that binary, it consistently segfautls
[15:39] <chrisccoulson> i guess if nautilus restarts fine afterwards, that i'm not getting the same crash?
[15:39] <seb128> ricotz, it's unsure it's librsvg
[15:39] <ricotz> :(
[15:39] <seb128> chrisccoulson, well, if librsvg install fine it's probably ok
[15:39] <chrisccoulson> yeah, seems to be ok here
[15:39] <seb128> chrisccoulson, you can try to install --reinstall libgdk-pixbuf I guess
[15:39] <ricotz> i guess i already updated and i am on amd64
[15:39] <seb128> ok
[15:39] <seb128> so only pitti so far
[15:40] <chrisccoulson> 2.35.0-0ubuntu1 ?
[15:40] <chrisccoulson> ok, will try that too
[15:40] <seb128> that's better than breaking everybody ;-)
[15:40] <seb128> chrisccoulson, yes
[15:40] <ricotz> i havent logged out yet though
[15:40] <ricotz> and i am not using lightdm
[15:41] <ricotz> but applications behaving normally
[15:41] <chrisccoulson> ok, that seems to still be working ok
[15:41] <chrisccoulson> although i've only tested by restarting nautilus
[15:41] <chrisccoulson> but i can browser svg's ;)
[15:41] <chrisccoulson> *browse
[15:42] <seb128> chrisccoulson, ricotz: well pitti couldn't run the gdk-pixbuf trigger, it segfaults for him
[15:42] <seb128> if the debs install file for you, it's likely fine
[15:42] <seb128> will need to wait for him to be back and provide a stacktrace
[15:43] <ricotz> alright
[15:43] <chrisccoulson> seb128, do you fancy fixing a compiler bug for me? https://launchpadlibrarian.net/90342632/buildlog_ubuntu-lucid-amd64.thunderbird-trunk_12.0~a1~hg20120118r9213.84699-0ubuntu1~umd1~lucid_FAILEDTOBUILD.txt.gz
[15:43] <chrisccoulson> thanks ;)
[15:43] <seb128> chrisccoulson, lol, no!
[15:43] <chrisccoulson> heh
[15:43] <seb128> chrisccoulson, I tried do you look at libreoffice for Sweetshark today and I've to build webkit next
[15:43] <seb128> enough slow to build stuff for today :p
[15:44] <ricotz> seb128, you a like libx11 bug instead?
[15:44] <seb128> ricotz, I'm fine thanks ;-)
[15:47] <cyphermox> seb128: ii  librsvg2-2                    2.35.0-0ubuntu1 ?
[15:47] <seb128> cyphermox, yes
[15:47] <seb128> well librsvg2-common rather
[15:47] <cyphermox> I didn't notice breakage when I upgraded
[15:47] <cyphermox> also rebooted since, not sure if that would trigger doom
[15:48] <seb128> cyphermox, ok, thanks
[15:48] <seb128> well seems it's only pitti, which is good
[15:50] <didrocks> (but if someone wants to test the unity in the ppa as well
[15:50] <didrocks> cyphermox: chrisccoulson ? ^
[15:51] <cyphermox> didrocks: yes, soon
[15:51] <cyphermox> actually, wth, I'll try it now
[15:51] <chrisccoulson> didrocks, in a bit :)
[15:52] <didrocks> thanks guys :)
[15:53] <cyphermox> brb, rebooting
[15:57] <didrocks> why people are taking time to reboot when installing the new unity? :)
[16:08] <dobey> chrisccoulson: hey, when an extension or plug-in gets upgraded, shouldn't firefox show the "restart your browser" strip? i just got an upgrade to flash but firefox isn't suggesting a restart
[16:09] <cyphermox> didrocks: it works great
[16:09] <cyphermox> sorry, I was fighting a very different problem\
[16:09] <didrocks> phew, you almost killed me :)
[16:09] <didrocks> thanks cyphermox!
[16:09] <seb128> didrocks, want me to do the uploads to precise?
[16:09] <didrocks> seb128: do you have a branch (if not, no worry, not long to do)
[16:09] <cyphermox> fwiw, my system is intel, amd64
[16:09] <didrocks> or do them if you want :)
[16:11] <seb128> didrocks, well I can do them if you want, I've no vcs ready but it's trivial enough, I'm done with the stuff I was doing so I can do that before starting something else
[16:12] <didrocks> seb128: sounds good, proceed please! thanks :)
[16:12] <seb128> didrocks, yes sir ;-)
[16:12] <seb128> yw
[16:31] <BigWhale> What happens in LTS, stays in LTS ...
[16:31] <BigWhale> :>
[16:56] <mterry> didrocks, I was going to push in a patch to compiz that just fixes some typos.  But I see there's been a change sitting in the packaging branch for over a month about fglrx?  Is that safe to push in with my change?
[16:57] <desrt> seb128: hey
[16:57] <didrocks> mterry: no, it's not
[16:57] <didrocks> mterry: there will be an update next week
[16:57] <didrocks> mterry: so you can stage your changes there
[16:57] <desrt> seb128: gnome-settings-daemon was doing 3 dconf writes on startup.  they're gone now.
[16:57] <mterry> didrocks, is that going to sync from upstream?
[16:57] <desrt> seb128: gnome-shell still has one outstanding, but obviously that doesn't impact you
[16:57] <desrt> seb128: so anything left should be in unity&friends
[16:58] <mterry> didrocks, because I think upstream has the typos fixed in trunk
[16:58] <seb128> desrt, great, thanks, I will backport that patch
[16:58] <didrocks> mterry: hum, what do you need, the typo is not on the packaging?
[16:58] <desrt> seb128: i already stuck it on the gnome-3-2 branch
[16:58] <seb128> desrt, excellent
[16:58] <mterry> didrocks, no.  just some "bunding" words instead of "binding".  Not usually worth worrying about, but a user went to the trouble of making a patch
[16:59] <didrocks> mterry: oh, in that case, poke directly smspillaz about them
[16:59] <mterry> didrocks, but they are fixed already upstream
[16:59] <didrocks> upstream integration is better :)
[16:59] <mterry> didrocks, I'm jsut asking if next update will be an upstream release too
[16:59] <didrocks> oh, we will get it next week then
[16:59] <didrocks> yeah :
[16:59] <didrocks> :)
[16:59] <mterry> didrocks, cool, will comment in the bug then and reject the branch
[16:59] <didrocks> thanks mterry :)
[17:12] <dobey> ricotz: around?
[17:12] <ricotz> dobey, yes
[17:12] <dobey> ricotz: hey. are you maintaining the rhythmbox packaging in debian now?
[17:13] <ricotz> dobey, no
[17:14] <dobey> ricotz: ah ok. there are some "small" packaging structure changes i'd like to make.
[17:15] <ricotz> dobey, might be worth to get them into debian too though
[17:15] <dobey> ricotz: it would i think.
[17:16] <dobey> i'll make the changes in PPA to test them first
[17:16] <ricotz> ok
[17:21] <seb128> dobey, what sort of changes?
[17:21] <seb128> like new binaries?
[17:22] <seb128> dobey, but yeah, better to send them to Debian
[17:22] <dobey> new binaries, and moving a few files within existing binaries; to make life easier for plug-in packages
[17:22] <seb128> ok
[17:23] <dobey> and yeah, i want to get them in debian
[17:23] <seb128> you can start with an Ubuntu merge request if you want a first review before sending to Debian
[17:24] <dobey> sure. well, i'll start with my PPA, then the merge requests :)
[17:32] <seb128> Riddell, Sarvatt: ok, unity seems to be fixed with glew1.6, I've uploaded updates to use that version
[17:32] <seb128> Riddell, so feel free to to promote glew1.6, demote,delete 1.5
[17:32] <seb128> bryce, ^
[17:33] <Riddell> just saw it come through on component mismatches
[17:33] <seb128> Riddell, yeah, I just noticed, that nux was depwaiting when checking if it built yet
[17:33] <seb128> Riddell, should I promote 1.6 then?
[17:34] <Riddell> seb128: I guess the MIR question is what does it take to demote 1.5 and who's going to do it
[17:35] <seb128> Riddell, nothing, we can delete 1.5, we just created that package in ubuntu for unity
[17:35] <Sweetshark> where do I find the desktop cd seeds?
[17:36] <Riddell> seb128: more than nothing http://paste.kde.org/189236/
[17:36] <seb128> Sweetshark, https://wiki.ubuntu.com/SeedManagement
[17:36] <seb128> Riddell, source in main using it: avogadro calligra koffice
[17:37] <seb128> Riddell, so it should be easy to demote
[17:37] <Riddell> seb128: what about those python things?
[17:38] <Sweetshark> seb128: tnx
[17:38] <Riddell> (I'm in a meeting can't investigate much myself)
[17:38] <seb128> Riddell, those are in universe
[17:38] <seb128> Riddell, the 3 I listed are the ones in main
[17:38] <seb128> Riddell, koffice should be a build-depends libglew1.5-dev -> libglew-dev, that's what Debian did
[17:38] <seb128> Riddell, I guess the other ones are in the same cases
[17:41] <Riddell> koffice can go once I test calligra upgrades and I'll fix calligra
[17:41] <seb128> Riddell, thanks
[17:57] <nessita> hello all! any idea why I can not resize windows in unity 3d (precise installation)?
[17:59] <seb128> hey nessita
[17:59] <nessita> hola seb128!
[17:59] <seb128> nessita, what do you mean? when happens when you try?
[17:59] <seb128> do you get decorations around those, like the bar at the top with the close etc button?
[18:00] <nessita> seb128: when I move the cursor close to a window edge, the cursor does not change to "resize" mode
[18:00] <nessita> seb128: even if I drag the window border, nothing happens
[18:00] <seb128> nessita, can you move things?
[18:00] <nessita> seb128: and yes, I have windows decorations with the 3 buttons, and I can move windows
[18:00] <seb128> nessita, what about the bottom right corner? does resizing there work?
[18:01] <nessita> seb128: maximize/minimize works
[18:01] <seb128> nessita, what about alt-middleclick-dnd?
[18:01] <nessita> seb128: hum... I can resize this window (pidgin chat), but no the gnome-terminal window
[18:02] <seb128> weird
[18:02] <nessita> seb128: alt-middleclick-dnd?
[18:02] <seb128> nessita, that's another way to resize
[18:02] <nessita> seb128: wanna a screencast of this?
[18:02] <seb128> i.e you press alt on the keyboard, click with the middle mouse button and while it's pressed move
[18:02] <seb128> that should resize as well
[18:03] <seb128> nessita, does it do it all the time or only in this session?
[18:03] <seb128> you can try to compiz --replace
[18:03] <seb128> to restart compiz
[18:03] <nessita>  seb128: all the time in this cmputer which I run unity 3d
[18:03] <seb128> is that specific to some softwares? like can you resize gedit?
[18:04] <nessita> seb128: I can resize firefox, trying gedit
[18:04] <nessita> can resize gedit
[18:05] <nessita> seb128: hum, I had a custom size set on the terminal. But I always had one... and before I was able to resize
[18:05] <nessita> I unset the custom size and resizing is allowed
[18:05] <seb128> dunno then
[18:06] <seb128> either compiz,unity changed or g-t did
[18:06] <nessita> seb128: but, for example, with size unset, if I open a fresh terminal, move it to the right so it resizes to the half of the screen, I can no longer resize it
[18:07] <nessita> and that happens with every windows
[18:07] <nessita> window*
[18:11] <seb128> nessita, right, that's a bug with the grid
[18:12] <nessita> seb128: I see
[18:12] <nessita> seb128: have the link at hand?
[18:12] <seb128> nessita, click on the right button in the wm bar to workaround it
[18:12] <seb128> i.e undo the grid
[18:13] <nessita> seb128: nice :-)
[18:16] <seb128> nessita, I don't find the bug number but I'm pretty sure JohnLea reported the issue
[18:17] <nessita> seb128: good to know. Thanks!
[18:17] <seb128> yw
[18:24] <dobey> seb128, ricotz: any idea why rhythmbox packaging in ubuntu has Build-Depends on a bunch of foo-doc packages now?
[18:24] <seb128> dobey, because debian --enable-gtk-doc I guess
[18:25] <seb128> we can probably drop that if the html are shipped with the tarball
[18:26] <dobey> seb128: it needs the gstreamer api docs for --enable-gtk-doc?
[18:27] <seb128> dobey, I think it needs the api of things it refers to for cross referencing links to be working
[18:27] <dobey> hmm
[18:27] <dobey> ok
[18:27] <seb128> dobey, so I guess some api point to gstreamer apis
[18:27] <seb128> it wouldn't be the end of the world if you drop those in your ppa
[18:29] <ricotz> seb128, proper cross referencing is nice, there is no need to drop those build-deps
[18:29] <dobey> seb128: i was just wondering why they were there now. it seemed odd is all
[18:29] <seb128> ricotz, well it can be spared for a local build
[18:30] <seb128> I often drop stuff like documentation build when I work on a package to spend less time rebuilding
[18:30] <seb128> dobey, ok
[18:30] <ricotz> seb128, right
[18:35] <stgraber> mterry: is there a clean way for flavours to override unity-greeter.conf?
[18:36] <stgraber> mterry: I just noticed the new unity-greeter breaks upgrade for at least Edubuntu because Edubuntu updates unity-greeter.conf with our own config (yeah, I know it's bad)
[18:36] <mterry> stgraber, I think so...  ?  let me look real quick else robert-ancell would know
[18:38] <mterry> stgraber, oh, I was thinking of lightdm.  For unity-greeter, no I don't think so.  I think Robert's thinking was that derivatives could have their own greeter?
[18:39] <stgraber> mterry: ok, I'll look at having edubuntu-artwork divert it or something like that. We use unity-greeter but with a different wallpaper and logo.
[18:59] <stgraber> mterry: the easy solution out of our problems (at least for Edubuntu) will be for me to push a new edubuntu-artwork restoring unity-greeter.conf to the original, then divert it and put our own in its place
[18:59] <stgraber> mterry: then add a versioned conflict in unity-greeter to force edubuntu-artwork to upgrade before unity-greeter
[19:00] <mterry> stgraber, :-/  sorry this is so hard.  I wonder...  Since unity-greeter is gtk-based, why it doesn't use gsettings, which derivatives could override easily
[19:01] <stgraber> mterry: I agree shipping a .override file would be much easier :)
[19:02] <stgraber> I still need to cleanup my mess though (I should have done the divert to start with, messing with a conffile from another package is really bad and shouldn't have be done to start with)
[19:05] <Beret> hey guys
[19:05] <Beret> qq
[19:05] <Beret> I'm seeing the same changes in the ubuntu mono font in precise that the guy on the desktop list noted
[19:05] <Beret> I don't see a bug listed in LP
[19:05] <Beret> anyone know anything about that?
[19:16] <Laney> 1
[19:16] <Laney> oops
[19:46] <dobey> why would i use foo (>= ${gnome:Version}), foo (<< ${gnome:NextVersion}) ?
[19:51] <seb128> dobey, because GNOME might break stuff between series and you want to say that's version in the same serie are ok but when the next serie start updates should be in sync
[19:51] <seb128> it's like "it's ok to get any 3.2 version but 3.4 might break so we will check that and be restrictive by default)
[19:52] <dobey> but if the dependency is on a binary package, created by the same control file, isn't it better to just use (= ${source:Version}) ?
[19:52] <dobey> especially in the case of foo depending on foo-data?
[19:53] <seb128> dobey, well, it has issues for arch all,any mismatch, it makes i.e armel build fail during the time i386 built and armel is building
[19:54] <seb128> because the -common is usually arch all built on i386
[19:54] <seb128> when you get the new version the armel binary which is arch any and depends on source:Version stop having a matching common and can't be installed
[19:55] <dobey> ugh
[20:01] <desrt> seb128: you're doing it wrong:
[20:01] <desrt> [org.gnome.desktop.background]
[20:01] <desrt> show-desktop-icons=true
[20:02] <desrt> (and i'm not sure how to do it right)
[20:03] <desrt> seems like this sort of setting is the kind of thing we want to be configured conditional on the session type :/
[20:07] <desrt> seb128: it's almost like you should have a separate DCONF_PROFILE that patches these changes in for the unity session
[20:15] <pitti> seb128: back for some mins
[20:15] <seb128> desrt, yeah, I know I'm doing it wrong, I welcome better ways though
[20:15] <pitti> seb128: so, this keeps amazing me; I downgraded libxml2, which was a likely candidate
[20:15] <seb128> pitti, heh, I'm just back from dinner
[20:16] <desrt> seb128: DCONF_PROFILE=unity is my best suggestion
[20:16] <pitti> but still segfaulting with downgraded libxml2 and downgraded librsvg
[20:16] <seb128> pitti, do you have a bt?
[20:16] <seb128> pitti, nobody else is getting the issue, I asked around when you left
[20:16] <seb128> pitti, we got i386 and amd64 tester
[20:16] <seb128> no bug report or user complain on IRC either
[20:17] <seb128> desrt, yet another Xsession hackish script?
[20:17] <pitti> ok, if it's just me, I'm relieved
[20:17] <pitti> will figure this out tomorrow morning then
[20:17] <desrt> seb128: it's actually a pretty nice setup.. then each desktop gets its own set of defaults, plus if the user sets it explicitly, it gets used
[20:17] <desrt> seb128: you could add it in to one of the many others :)
[20:17] <seb128> pitti, well it might not be "only you", it might be "german amd64 users" or something, I would still like to know what's the issue
[20:17] <seb128> pitti, but it's not "the rest of the world" ;-)
[20:18] <seb128> desrt, I'm trying to get ride of those hacks
[20:18] <pitti> seb128: not very useful: http://paste.ubuntu.com/810009/
[20:18] <seb128> desrt, relying on the session you pick is wrong, it means that people using a custom session starting gnome-shell will get it wrong
[20:18] <desrt> seb128: i think at the end of the day you should aim to have exactly 1 of them
[20:18] <desrt> seb128: this is pretty much the XDG_CURRENT_DESKTOP discussion, isn't it?
[20:19] <seb128> desrt, right
[20:19] <desrt> seems that battle is long lost
[20:19] <desrt> GNOME_ME_HARDER, dude
[20:19] <seb128> lol
[20:19] <desrt> environment variables are awesome
[20:19] <seb128> you still need something setting them
[20:19] <seb128> pitti, not very useful no :-(
[20:19] <desrt> you're going to find yourself minus some UBUNTU_MENUPROXY and plus some GTK_MODULES soon
[20:20] <seb128> pitti, you run doko's ppa right? was that a new libc?
[20:20] <pitti> seb128: yes, but since last week
[20:20] <seb128> pitti, well maybe something in that librsvg update doesn't like the new libc?
[20:20] <pitti> seb128: but why would it still crash with librsvg and libxml downgraded?
[20:20] <seb128> pitti, just trying to think what could be different in your case
[20:20] <pitti> I checked all dependencies of librsvg2-2 and -common
[20:20] <seb128> hum, good point
[20:21] <seb128> what did you upgrade before the issue started?
[20:22] <seb128> desrt, how would the profile stuff work?
[20:22] <pitti> everything since this morning, didn't restart my session until 16:16 CEST, at which point I got it
[20:22] <pitti> (that was when you asked me to try the PPA)
[20:22] <desrt> seb128: pretty trivially: create /etc/dconf/db/unity.d/somefile with your dconf overrides in it
[20:23] <desrt> then /etc/dconf/profile/unity with the lines "user\nunity\n"
[20:23] <desrt> then run 'dconf update'
[20:23] <desrt> then set DCONF_PROFILE=unity
[20:23] <seb128> pitti, there were not so many updates today
[20:23] <seb128> pitti, nothing obvious I can spot
[20:23] <pitti> http://paste.ubuntu.com/810014/
[20:24] <pitti> oh, a new GTK
[20:24] <desrt> any "pure" vendor patch like changing the wallpapers and so on stays a vendor patch
[20:24] <desrt> and "we're half-forking gnome to use as the basis of the unity desktop" sort of behaviour goes in the dconf database
[20:24] <seb128> pitti, new gtk is a one liner reverting a properties change on gtkwindows
[20:24] <seb128> pitti, not likely to make gdk fail on loaders
[20:24] <pitti> seb128: I guess I'll run through the list and play downgrading bisect until I find the culprit
[20:25] <seb128> pitti, you might have local corruption as well I guess
[20:25] <seb128> desrt, not sure it's worth the effort ;-)
[20:26] <pitti> so, good night everyone!
[20:26] <desrt> seb128: it's some pretty low effort :p
[20:26] <desrt> pitti: n8
[20:26] <seb128> pitti, 'night
[20:27] <seb128> desrt, btw I'm glad I didn't listen to you, new g-c-c pulls clutter in and new clutter seems a disaster, leading to g-c-c not starting for some people and other fun ;-)
[20:27] <desrt> seb128: oh.  they fixed that already
[20:27] <desrt> ebassi figured out the problem this morning
[20:27] <seb128> right
[20:27] <seb128> still it was broken for a few days
[20:28] <seb128> well mostly teasing you but I'm glad I can focus on fixing old bugs rather than fighting such issues
[20:28] <seb128> it would have take a day of my time for nothing (i.e be back where we were before the issue, just dealing with updates for the sake of updating)
[20:38] <jono> are Precise users not seeing the date/time indicator?
[20:38] <jono> it is not displaying on my system
[20:39] <seb128> jono, works for me and we got no report about it, is indicator-datetime installed?
[20:40] <jono> seb128, odd, it wasn't
[20:40] <jono> I wonder what removed it
[20:41] <seb128> jono, well I guess you don't use debian based distro for long enough to read dist-upgrades output before pressing "y" :p
[20:41] <jono> seb128, I usually check that, but I wonder what removed it
[20:41] <jono> odd
[20:41] <seb128> I wonder if we should make people type "I know I'm screwing my system but I'm so cool I don't care" ;-)
[20:41] <seb128> jono, well for sure you dist-upgraded and say yes to get it removed
[20:42] <seb128> jono, we don't remove packages without asking ;-)
[20:42] <jono> seb128, I understand this, but why would another package remove it?
[20:42] <jono> I never intentionally removed it, so some package must have requested it's removal
[20:42] <jono> irrespective of whether I saw that it was going to be removed, I don't get why it was removed in the first place
[20:42] <seb128> jono, because there were some e-d-s soname changes and during transition if you want the new lib you need to remove stuff not rebuilt yet
[20:43] <jono> seb128, ahhh gotcha
[20:43] <seb128> jono, but I'm half joking, we should really make dist-upgrade harder, it keeps bitting people and not only newbies
[20:44] <seb128> we should make people type something actually like "yes I want to uninstall the stuff listed there and I know what I'm doing"
[20:44] <jono> seb128, I am not sure that is needed
[20:44] <jono> but I agree that we should highlight removals more clearly
[20:44] <seb128> jono, well, I'm open to other suggestions
[20:45] <jono> I was surprised because I have never seen a package such as that removed
[20:45] <jono> traditionally, most dist-upgrades add to the system, not remove packages
[20:45] <seb128> jono, but see you got very confused and we can't call you a new user ;-)
[20:45] <seb128> jono, you got lucky so far it seems ;-)
[20:45] <jono> seb128, well, I got confused because my experience stepped outside of my normal experience of doing dist-upgrades
[20:45] <seb128> some people got unity installed during the rally because they dist-upgraded before unity-2d was built
[20:46] <jono> anyway, I guess it is what it is
[20:46] <seb128> installed -> uninstalled
[20:46] <jono> thanks for the help, seb128
[20:46] <seb128> jono, yw
[20:47] <mdeslaur> seb128: the problem is the "packages to be removed" part is listed first, and gets scrolled off the terminal screen
[20:47] <chrisccoulson> that's the best way isn't it? we all love a surprise :-)
[20:48] <mdeslaur> chrisccoulson: I call it "dev release roulette"
[20:48] <chrisccoulson> "which packages will the upgrade remove today? ooooh, xorg. Yippee!!"
[20:49] <desrt> mterry: hey
[21:56] <stgraber> mterry: apparently diverting conffile is buggy (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363524)...
[21:57] <ubot2> Debian bug 363524 in dpkg "Problem diverting conffile" [Normal,Open]
[21:57] <stgraber> mterry: any chance you can switch unity-greeter to gsettings? :)
[21:59] <stgraber> mterry: to workaround the bug, I'll ship /etc/lightdm/edubuntu-greeter.conf, divert unity-greeter.conf and make it a symlink to edubuntu-greeter.conf, that "should" work but it'd be nice the situation improved a bit soon :)
[22:12] <mterry> desrt, pong
[22:12] <mterry> stgraber, hm, I'll ask robert about what derivitives are supposed to do
[22:12] <seb128> lol
[22:13] <desrt> mterry: just wondering if you know something about setting per-user lightdm background images
[22:13] <seb128> mterry, I can reply for him if you want
[22:13] <mterry> desrt, maybe
[22:13] <seb128> mterry, he will tell you "if you figure anything that works please just do it"
[22:13] <seb128> mterry, didrocks asked him during the rally ;-)
[22:13] <mterry> seb128, heh  :)
[22:14] <seb128> mterry, seems robert_ancell has no particular interest in packaging alternatives or conffile handling and tried a few things that didn't work well and decide to just let whoever has a clue deal with it
[22:15] <mterry> I'm pretty sure gsettings is easy, since unity-greeter can rely on it (though doesn't help with lightdm).  stgraber, you confirm that would be easy for you right?
[22:15] <seb128> mterry, btw who between you two should I nudge until the keyboard stuff get fixed? ;-)
[22:16] <mterry> seb128, I think that's more in lightdm's court right now?
[22:16] <mterry> unless there's a bug in how unity-greeter handles layout support from liblightdm-gobject, which is certainly possible
[22:17] <seb128> mterry, dunno, I've not tried to debug it, I'm just trying to bootstrap the debugging ;-)
[22:17] <mterry> desrt, specific question?
[22:17] <seb128> mterry, if you give me debugging hint I can try to have a look tomorrow, I've no clue how the indicator handle layouts right now
[22:17] <seb128> mterry, like does it try to get the info from lightdm? stored config?
[22:18] <mterry> seb128, IIRC unity-greeter asks lightdm for the current layout and sets it
[22:19] <desrt> mterry: "do you know how to do it?  how?"
[22:21] <mterry> desrt, it's stored in accountsservices (an ubuntu-specific patch, though there's a bug filed upstream asking how they want it done For Realz).  g-s-d syncs the user's gsettings value to accountsservice when it sees it change
[22:21] <desrt> interesting
[22:21] <stgraber> mterry: yeah, gsettings would be easy, we can just ship and override file and be done with it
[22:21] <desrt> i wonder if it fails to work because my homedir is readable only by me
[22:22] <mterry> desrt, it also doesn't currently have 'upgrade' support in the sense that you have to change the gsettings key for it to kick in right now
[22:22] <seb128> desrt, did you change your background with the control center?
[22:22] <desrt> yes
[22:23] <mterry> desrt, oh, yeah, if your image is not readable by 3rd parties, it won't show the image
[22:23] <mterry> desrt, did you pick a system image or one in your read-only homedir?
[22:23] <desrt> one in my homedir :)
[22:24] <seb128> mterry, ok, I will to debug it tomorrow
[22:24] <seb128> mterry, I dropped an email to robert_ancell about it as well
[22:25] <mterry> seb128, I can help too, don't mean to be uncurious.  Just been busy most of today with patch piloting
[22:25] <robert_ancell> seb128, greeter keyboard issues?
[22:25] <seb128> mterry, yeah no worry, I'm just trying to make sure it's not one of those bugs sitting there for months ;-)
[22:26] <mterry> robert_ancell, hi Robert!
[22:26] <seb128> robert_ancell, hey
[22:26] <seb128> robert_ancell, "en" being default in the unity-greeter
[22:26] <seb128> robert_ancell, it leads user who don't look at screen details to just type their password as usual and report that lightdm is broken since login fails
[22:26] <seb128> tjaalton did that today ;-)
[22:26] <robert_ancell> hah!
[22:27] <robert_ancell> I guess there's no text entry anywhere to indicate that
[22:27] <robert_ancell> (it is wrong)
[22:27] <seb128> robert_ancell, there is the indicator
[22:27] <robert_ancell> was that showing en ?
[22:27] <seb128> yes
[22:27] <seb128> the bug I showed you during the rally
[22:27] <robert_ancell> oh, yeah
[22:27] <seb128> the greeter doesn't respect the system default or user setting
[22:27] <seb128> it just go "en"
[22:27] <robert_ancell> well, what other layout would you need?
[22:27] <robert_ancell> ;)
[22:28]  * seb128 slaps robert_ancell
[22:28] <seb128> (hate webkit, my box is slow, building it for over 3 hours and is running out of disk space)
[22:29] <seb128> if it fails because of disk space I'm going to be unhappy ... making space
[22:29] <robert_ancell> yeah, i've run out of memory compiling it before.  not fun
[22:29] <mterry> robert_ancell, I think unity-greeter is just using what lightdm is giving it in this case
[22:30]  * mterry pushes problem over to robert_ancell
[22:30] <robert_ancell> mterry, I'll set up a regression test for it, and check it gives good values
[22:30] <mterry> probably a good idea anyway
[22:30] <mterry> if it looks like unity-greeter after all, I'll fix it tomorrow
[22:31] <seb128> robert_ancell, mterry: what is weird is that it's neither using the user keymap nor the system default one
[22:31] <seb128> so seems a double bug, if it fails getting an user config it should default to the system default
[22:33] <seb128> or it's simply mterry who behaved as an american an hardcoded "en_US" in the source :p
[22:33] <mterry> seb128, don't think I wouldn't
[22:33] <seb128> ;-)
[22:34] <mterry> "Here's your new keyboard indicator with *SO* many choices.  Pick any one, as long as it's US English!"
[22:35] <seb128> I knew it!
[22:35] <seb128> Grrrr
[22:36] <seb128> ld failed in webkit without error
[22:39] <seb128> desrt, http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=27fa171efe4179c0a42ec79e0dc501077f042a08 another reason why we will not update g-c-c
[22:40] <seb128> oh btw there you, hard depends on systemd without public discussion at the GNOME level...
[22:40] <desrt> fascinating
[22:40] <seb128> indeed
[22:42] <seb128> desrt, I guess I can drop gnome-shell support now since Ubuntu is now officially unsupported by GNOME ;-)
[22:43] <chrisccoulson_> seb128, seems like you need a beefier machine for building webkit ;)
[22:44] <seb128> chrisccoulson_, yeah, I closed firefox and tb and it's ok now
[22:44] <chrisccoulson_> lol
[22:44] <seb128> ls is take 2.9g
[22:44] <seb128> doh
[22:44] <seb128> ld is taking 2.9g
[22:44] <chrisccoulson> that's a crazy amount
[22:44] <seb128> yeah
[22:45] <TheMuso> Ouch that is a lot.
[22:45] <seb128> it's cpp for you
[22:45] <chrisccoulson> it's more than firefox, and that is cpp ;)
[22:45] <seb128> the source is take 8mb compressed, the build dir is over 3g now
[22:45] <seb128> well it's dual building it
[22:46] <seb128> but still
[22:46] <seb128> ln: failed to create symbolic link `libwebkitgtk-3.0.so.0': No space left on device
[22:46] <seb128> Grrrrr
[22:46] <chrisccoulson> ouch
[22:46] <seb128> hate hate hate
[22:46] <chrisccoulson> i'm glad i'm not maintaining that!
[22:49] <desrt> seb128: okay.  now i do your trolling for you.
[22:50] <desrt> https://mail.gnome.org/archives/desktop-devel-list/2012-January/msg00015.html
[22:50] <chrisccoulson> i wish the day-to-day work would just stop for a few days :/
[22:51] <chrisccoulson> desrt, shouldn't "cannot" be "will not"?
[22:51] <chrisccoulson> i can do my own trolling too ;)
[22:51] <desrt> chrisccoulson: i didn't want to troll too hard to start
[22:51] <chrisccoulson> lol
[22:51] <desrt> chrisccoulson: you're welcome to pile on :)
[22:51] <seb128> desrt, thanks ;-)
[22:51] <chrisccoulson> i think i'll give that a miss ;)
[22:52] <desrt> seb128: fwiw, i honestly hope this conversation ends up with systemd as a hard dependency of gnome
[22:52] <desrt> seb128: but this should happen on the lists, properly
[22:53] <desrt> not just because someone goes ahead and does it
[22:53] <seb128> desrt, fine with me
[22:53] <seb128> desrt, I just don't like that previous discussion stopped without consensus and that somebody goes and decide to just do it
[22:53] <desrt> seb128: same feeling
[22:53] <seb128> desrt, that just reflects bad on GNOME
[22:53] <desrt> no kidding
[22:54] <seb128> it's like "let's avoid behing honest because honesty leads to discussion"
[22:55] <desrt> well
[22:55] <desrt> foundation-list is already warmed up for this year
[22:55] <desrt> time to give d-d-l a go :)
[22:56] <chrisccoulson> cyphermox, dang, i forgot to fix the eds dependency with the thunderbird upload
[22:56]  * chrisccoulson commits that to the nightly branch so i remember for the next release
[22:59] <seb128> waouh
[22:59] <seb128> webkit built!
[22:59] <seb128> $ du -ksh webkit-1.7.4
[22:59] <seb128> 8,4G	webkit-1.7.4
[22:59] <desrt> i love webkit
[23:01] <chrisccoulson> chr1s@farnsworth:~/src/firefox$ du -ksh mozilla-central/
[23:01] <chrisccoulson> 4.4G    mozilla-central/
[23:01] <chrisccoulson> ;)
[23:02] <TheMuso> /c/c


[07:16] <dholbach> good morning
[09:13] <dholbach> nhaines, jose: are you contacting possible judges already?


[02:23] <wgrant> StevenK: Hmm
[02:23] <wgrant> StevenK: That's not really sufficient
[02:23] <wgrant> I don't think
[02:23] <StevenK> Why not?
[02:23] <StevenK> The access checks will check only branch rows
[02:23] <wgrant> Doesn't the existing preload thing handle stacking etc.?
[02:24] <StevenK> It does do stacking as well, yes
[02:25] <StevenK> But almost all of preloadDataForBMPs isn't needed
[02:26] <wgrant> You probably need prereqs as well
[03:19] <StevenK> wgrant: Okay, I agree in terms of stacking, since that will impact the access checks.
[03:19] <StevenK> wgrant: Why prereqs?
[03:20] <StevenK> Those will already been pulled in via target_branch == self?
[03:33] <wgrant> StevenK: Howso?
[03:33] <wgrant> StevenK: prereq != target
[03:34] <StevenK> Oh, it may be checked for access
[03:34] <StevenK> Right
[03:34] <wgrant> you need access to all three branches, and their stacked-on branches
[04:46] <wgrant> StevenK: https://code.launchpad.net/~wgrant/launchpad/ppa-pub-skip/+merge/150264
[05:25] <StevenK> wgrant: r=me, with one niggle.
[05:46] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/preload-landing_candidates/+merge/150255 again?
[05:47] <StevenK> wgrant: And we'll have to go through and delete all of the empty dirs when that fix is deployed?
[05:48] <wgrant> StevenK: Yes
[05:49] <StevenK> It would have create pool and dists and everything?
[05:49] <StevenK> I'm just wondering how much of the tree it did create off the bat
[05:49] <wgrant> Yes, it created pool/ and dists/
[05:49] <wgrant> Anyway
[05:49] <wgrant> You've checked that this change actually works?
[05:49] <wgrant> accessing source_branchID doesn't call into the security proxy?
[05:50] <StevenK> It does not seem to
[05:51] <wgrant> Great.
[05:51] <wgrant> Oh
[05:51] <wgrant> Because you added them to zope.Public?
[05:51] <wgrant> Yes
[05:52] <wgrant> That's one bad bad security declaration
[05:52] <StevenK> source_branch and prerequisite_branch were already there
[05:52] <StevenK> But yes, IBranchMergeProposal needs fixing
[05:52] <wgrant> Yes
[05:52] <wgrant> Your changes aren't worse
[05:52] <wgrant> BUt what's there today is awful.
[05:53] <wgrant> r=me, then
[05:53] <StevenK> Shall I rip that crap out now in a seperate branch?
[05:53] <wgrant> Fixing it may be challenging, but is necessary
[05:53] <wgrant> So yeah, a followup would be good
[05:53] <StevenK> IBranchMergeProposalPublic etc etc
[05:53] <StevenK> Like the fun I had for IBug
[05:54] <wgrant> Not necessarily
[05:54] <wgrant> But you can if you want
[05:54] <wgrant> The problem is not that the attributes are listed in the ZCML
[05:54] <wgrant> The problem is that they are all public.
[05:56] <StevenK> Oh, no permission means zope.Public, not launchpad.View?
 means zope.Public
[07:32] <StevenK> wgrant: You lose at buildbot bingo
[07:34] <wgrant> Yeah, landing now
[07:37] <StevenK> I do like one line testfixes
[08:27] <adeuring> good morning
[11:25] <czajkowski> jml: you about ?
[17:39] <cjwatson> wgrant: Any thoughts on my last set of fixes for https://code.launchpad.net/~cjwatson/launchpad/bpph-phase/+merge/144154 ?
[23:01] <StevenK> wgrant: My QA looks good -- aside from the extra 50 odd queries by something failing to preload people
[23:02] <wgrant> StevenK: I assume that's the subscriber list
[23:02] <wgrant> So should be trivial to fix
[23:02] <wgrant> Care to look into it? :)
[23:03] <StevenK> I'm reading the traceback from one of the queries
[23:03] <StevenK> Which looks to hit TAL, then view and then TAL again
[23:06] <StevenK> Some indication what line is implicated in the template would be awesome
[23:53] <wgrant> StevenK: Any luck on Branch:+index?


[12:22] <ubotu> New bug: #122209 in xserver-xorg-driver-vesa "Cycling through display modes fails with vesa driver and NVIDIA 8400M GS." [High,New]  https://launchpad.net/bugs/122209
[04:30] <ubotu> New bug: #126074 in xserver-xorg-video-unichrome (universe) "xserver-xorg-video-unichrome" [Undecided,New]  https://launchpad.net/bugs/126074
[08:36] <ubotu> New bug: #74012 in compiz "Compiz crashes with two X-screens" [Unknown,Confirmed]  https://launchpad.net/bugs/74012