[07:50] <didrocks> hey mmrazik
[07:50] <didrocks> what was the bzr misconfiguration you are talking about?
[07:52] <didrocks> thanks for the report btw :)
[09:20] <didrocks> larsu: on this not so sunny Friday, do you want some really free karma? https://code.launchpad.net/~didrocks/indicator-power/bootstrap/+merge/134623
[09:28] <larsu> didrocks, sure! done ;)
[09:28]  * larsu love lp karma
[09:29] <didrocks> larsu: thanks! I knew you live for karma!
[10:04]  * apw has recently updated on Quantal and the messaging indicator is gone, i assume this is not expected
[10:06] <larsu> apw, yes it is: the messaging menu is only shown when you have applications that integrate with it. And you need to start them manually once
[10:08] <apw> larsu, oh, hmmm, is that new behaviour or am i just unobservant
[10:09] <apw> larsu, i thought i used to start the applications from that menu ...
[10:09] <ppisati> i've same problem as apw
[10:09] <ppisati> and i always had the envelope icon
[10:09] <larsu> apw, you'll be able to, you just need to start them once and they'll show up again
[10:09] <ppisati> first thing i did in the morning was to start irc, msn, skype, ectec
[10:10] <larsu> beware: not all applications have been ported to the new API yet
[10:10] <ppisati> and i did it going to the messaging menu, and mrking myself as avilable there
[10:10] <apw> larsu, indeed starting gwibber did make the menu appear
[10:11] <ppisati> now, how am i supposed to login in msn if all the dialogues went through it? (and the icon/menu is not there anymore)
[10:11] <larsu> apw, and it will stay there now :) (until you uninstall gwibber or disable messaging menu integration in its preferences)
[10:12] <apw> larsu, so did that happen when i updated P->Q and i just didn't notice?
[10:12] <larsu> apw, yep
[10:13] <apw> an pidgin which i use most isn't apparently connected to it hense its not appeared again before
[10:13] <larsu> apw, yeah pidgin is one of the apps that aren't ported yet. But there's already a patch attached to https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1040259
[10:16] <larsu> apw, fyi: http://design.canonical.com/2012/04/status-menus/
[10:16] <apw> larsu, thanks for the explanations; i am not sure the user supprise this clearly engenders was the best user experience possible, not that any of that is your fault
[10:17] <ppisati> larsu: so, if i start an application that uses that menu, it appears, right?
[10:17] <ppisati> larsu: but wasn't empathy supposed to start automatically at boot?
[10:18] <larsu> ppisati, no, empathy doesn't start automatically afaik
[10:18] <ppisati> larsu: well, then it did when you select "available" in the envelope men
[10:18] <ppisati> u
[10:22] <larsu> ppisati, you only have to start the application once to make it appear in the menu forever from that point on (even after you close the app or reboot)
[10:22] <ppisati> larsu: ack, done
[10:22] <ppisati> larsu: thanks
[10:23] <apw> larsu, is there a way to get rid of things you never use from it which you used in the past and no longer do ?
[10:23] <ppisati> larsu: but i don't get why it shouldn't be there after a P->Q transition
[10:23] <larsu> ppisati, apw, I agree it's not a perfect experience for users upgrading from P -> Q, but due to the new API it was practically impossible to write migrations
[10:23] <larsu> it was a tradeoff, we chose the minor annoyance of starting the app once
[10:23] <ppisati> larsu: ok
[10:24] <larsu> apw, a well-behaved application will offer a preference. Otherwise you can remove it from dconf-editor (com.canonical.indicator.messages.applications)
[10:24] <larsu> of course, uninstalling an application will also remove it
[10:26] <ppisati> larsu: another question, i was used to have the skype icon show up in the iconbar
[10:26] <ppisati> larsu: but is not there anymore, you know why?
[10:26] <ppisati> of course, skype is running now
[10:26] <larsu> ppisati, it shows up for me, right next to the messaging menu
[10:26] <ppisati> :(
[10:26] <ppisati> nt for me...
[10:26] <ppisati> i've it in the unity bar
[10:26] <ppisati> but not up there
[10:28] <larsu> ppisati, no idea, sorry. There doesn't seem to be a preference, either
[10:31] <ppisati> larsu: do you know if there's a place (directory, gconf entry, etcetc) where all the icons that show up in the bar are listed?
[10:31] <larsu> no, there isn't
[10:49] <mhr3> ppisati, try adding "skype" to com.canonical.unity.panel.systray-whitelist
[10:49] <mhr3> (in dconf)
[10:53] <ppisati> mhr3: so we still need to whitelist it, ok
[10:54] <ppisati> mhr3: question: since it's such a common app (and it's integrated with the messaging menu), why don't we whitelist by default?
[10:54] <mhr3> it's weird, i remember it using indicator previously, now it isn't :/
[10:54] <mhr3> larsu, i guess because of the api changes?
[10:55] <ppisati> s/it's integrated/it's not integrated/
[10:56] <larsu> mhr3, yep, but somebody seems to be working on it: https://bugs.launchpad.net/skype-wrapper/+bug/1040259
[10:58] <larsu> mhr3, I don't have skype on the whitelist. I think its an appindicator already
[10:58] <mhr3> larsu, that's what i said, but it disappeared for me after moving to 12.10
[10:59] <larsu> mhr3, oh, you mean skype in the messaging menu or skype on the panel?
[11:03] <mhr3> larsu, panel
[11:04] <mhr3> or maybe it's just a qt lib that's no longer installed with skype
[11:05] <larsu> mhr3, might be. Does the sykpe binary export the /org/kde/statusnotifieritem objects for you?
[11:05] <larsu> and do you have indicator-application installed
[11:06] <mhr3> larsu, it doesn't export that
[11:06] <larsu> that's the problem, then :)
[11:06] <larsu> which skype version are you running?
[11:06] <mhr3> the question is why :)
[11:06] <mhr3> 4.0.0.8
[11:06] <larsu> okay, same for me
[11:12] <larsu> mhr3, do you have sni-qt installed?
[11:13]  * larsu found agateaus blog post about it: http://agateau.com/2011/07/19/statusnotifieritem-for-qt-applications/
[11:13] <larsu> skype seems to use QSystemTrayIcon still, and sni-qt is a plugin that turns systray icons into app indicators
[11:13] <mhr3> larsu, i do :/
[11:13] <larsu> :(
[11:14] <mhr3> and that's what happens when aurelien leaves
[12:08] <conscioususer> larsu: do you know where I can find some UOA docs for third party app devs? just reading the api is being insufficient for me
[12:10] <conscioususer> mhr3: I heard some people solved this issue by installing the correct arch of sni-qt
[12:12] <mhr3> conscioususer, bingo, installing the i386 variant fixed it
[12:13] <mhr3> larsu, ^^
[12:13] <conscioususer> :)
[12:15] <mhr3> now if only the skype menu didn't flicker everytime i click on it
[12:16] <larsu> conscioususer, awesome, thanks!
[12:17] <larsu> conscioususer, I'm not sure about docs for uoa, let me find out
[12:18] <conscioususer> larsu: thanks :)
[12:23] <didrocks> larsu: hey, I have an other simple and dummy merge for your karma :) https://code.launchpad.net/~didrocks/indicator-power/changes_from_trunk.12.10/+merge/134643
[12:24] <larsu> didrocks, sure - but I'll wait to see the diff. Not that I don't trust you.......
[12:24] <didrocks> larsu: sure sure :)
[12:25] <larsu> conscioususer, meet amigadave :)
[12:25] <amigadave> conscioususer: hi!
[12:25] <amigadave> conscioususer: mardy wrote https://docs.google.com/a/canonical.com/document/d/1MVsDdwzff6LqQ6i3z-cSgg8dHjb5DaHMXFeWtIa6Cvo/edit which is some general developer documentation for UOA
[12:25] <amigadave> conscioususer: is that more what you were looking for?
[12:27] <conscioususer> amigadave: probably, as I'm specifically looking for info for 3rd party clients
[12:27] <conscioususer> amigadev: at a first glance this seems enough, thanks :)
[12:27] <amigadave> conscioususer: we are working to get all of that documentation into the API references too
[12:28] <amigadave> let us know if you have any feedback :)
[12:29] <conscioususer> amigadave: will do, thanks :)
[12:31] <larsu> didrocks, approved
[12:32] <larsu> didrocks, I'm really looking forward to seeing how daily landing will turn out in practice
[12:33] <didrocks> larsu: same here, we are >< <- that close
[12:33] <larsu> \o/
[12:33] <didrocks> larsu: just need a commit after the bootstrapping so that it can detect there are some changes
[12:33] <didrocks> larsu: let's find something useful for each project :)
[12:35] <larsu> didrocks, yep :)  btw, did you decide on a rule on when to mark bugs as "fix released"?
[12:36] <didrocks> larsu: right now, I only open the downstream bug and it will be marked as fix released, I don't touch the upstream one until you decide to do your own release
[12:36] <didrocks> larsu: it's really as you prefer, if you think it should close it, we can discuss it :)
[12:37]  * larsu is unsure
[12:37] <larsu> still :)
[12:41] <didrocks> let's see how it goes that way :)
[13:50] <conscioususer> amigadave: er, why does uoa store user passwords for oauth-based accounts?
[13:55] <amigadave> conscioususer: so that it can reauthenticate without the user having to enter the credentials again
[13:55] <conscioususer> amigadave: isn't this what the access token is for?
[13:56] <amigadave> conscioususer: if the token expires, then the user would otherwise have to re-enter the username and password
[13:57] <amigadave> i think that refresh tokens were tried (with Google, specifically) but they did not work reliably
[13:57] <amigadave> and Google has very short token validity :/
[13:57] <conscioususer> amigadave: but what about oauth1.0 services like twitter?
[13:58] <conscioususer> amigadave: btw, what do you mean by "not work reliably"? I'm curious on that one because I use google refresh tokens on an app of mine
[13:59] <amigadave> conscioususer: mardy knows the full details
[13:59] <amigadave> conscioususer: and #accounts-sso might be a better place for these questions :)
[13:59] <conscioususer> oh, of course
[13:59] <conscioususer> sorry, will move there :)
[14:53] <davidcalle> mhr3, does this kind of bug fall under your new jurisdicition? (frequency of recommendations and sources calls to *search.ubuntu.com) https://bugs.launchpad.net/ubuntu/+source/unity-lens-video/+bug/1079699
[14:53] <mhr3> pawel is looking at it
[14:54] <mhr3> i mean, pstolowski
[14:54] <davidcalle> Ok
[14:56] <pstolowski> davidcalle, mhr3: hey, yep. it's basically "by design", I'll check with server side guys if we can query it less often for recommendations.
[14:57] <mhr3> pstolowski, are the sources checked that way too?
[14:58] <pstolowski> mhr3: yes, same interval
[14:58] <pstolowski> mhr3: this is definately too often for sources
[14:58] <mhr3> i can imagine that sources should be checked just once
[14:58] <mhr3> + on location change
[14:58] <mhr3> which i'm not sure can be detected easily
[14:59] <davidcalle> mhr3, I think that tedg has made some work on Ubuntu geoclue last cycle, maybe he could give a hint?
[15:00] <mhr3> yea, i'm pretty sure the time indicator or whatever behind it knows, just don't think it exposes changes to location as some signal
[15:01] <tedg> mhr3, We poll occasionally, it's GeoIP though so it really only changes on reboot.  But it's all just GeoClue.
[15:01] <tedg> mhr3, So if you cache an address then you can get the new one.
[15:02] <tedg> mhr3, If you grab indicator-location you can see what you've got easily.  Also, some simple sample code.
[15:02] <pstolowski> mhr3, davidcalle: we could consider location for R, but for P or Q we should only fix the frequency
[15:03] <mhr3> tedg, i'm not a fan of polling, i want to be notified :)
[15:03] <mhr3> pstolowski, sure
[15:03] <davidcalle> pstolowski, +1
[15:04] <tedg> mhr3, Well, you'll be notified on changes.  For GeoIP we can't get notified.
[15:30] <Squarism> java is the most popular programming language, intellij is the most popular IDE... tons of hotkeys in intellij conflict with Unity. Please solve this to make ubuntu alot more user friendly for a big number of programmers
[15:31] <larsu> [citation needed]
[15:34] <bregma> Squarism, is there a bug in Launchpad you can reference?
[16:55] <MCR1> smspillaz: Hi :) Thanx 4 the ultra-fast approval...
[17:44] <mterry> didrocks, what does the jenkins error in https://code.launchpad.net/~mterry/unity-scope-gdrive/rename/+merge/134567 mean?
[17:45] <didrocks> mterry: I don't really know, it seems something similar to my check I did with tarmac, like "check that the approved rev id is the latest rev on the branch"
[17:45] <didrocks> I think they do the same on jenkins
[17:45] <didrocks> mmrazik? ^
[17:45] <didrocks> hum, not here…
[17:46] <didrocks> mterry: so, I approved agian
[17:46] <didrocks> now see:
[17:46] <didrocks> Approved revision: 30
[17:46] <didrocks> sometimes, it can be "unknown"
[17:46] <didrocks> due to launchpad timeout I guess
[17:46] <didrocks> maybe that was the case
[17:46] <didrocks> let's bet on this
[17:47] <MCR1> didrocks: Hi :) Could we change the way expo is patched for Ubuntu ? It seems to create quite some problems...
[17:47] <didrocks> (it seems they have the same check, see "Unapproved changes made after approval.")
[17:47] <didrocks> MCR1: how do you want to change it?
[17:47] <MCR1> Hmm, maybe with some ifdefs or so...
[17:48] <MCR1> COMPILE_FOR_UBUNTU_UNITY or something like that
[17:48] <MCR1> the problem is that for example this patch fails all the time: https://code.launchpad.net/~mc-return/compiz/compiz.merge-fix1009592-and-1074487-expo-xml-tooltip-fixes/+merge/132754
[17:48] <didrocks> MCR1: what do you mean? it's still a patch applied
[17:49] <didrocks> MCR1: with inline packaging, you can now try and apply it yourself :)
[17:49] <didrocks> and fix it
[17:49] <didrocks> or convince upstream who did the patch to take it by default
[17:49] <MCR1> yeah, that is what I mean
[17:49] <didrocks> I would love that it's upstream
[17:49] <MCR1> it should be in upstream, otherwise things are really hard to fix
[17:50] <didrocks> if you can push for that, please try :)
[17:50] <didrocks> (I already tried)
[17:50] <didrocks> having patches to maitain is a burden
[17:50] <MCR1> and expo is currently very broken in various ways (the ubuntu patch is breaking it...)
[17:50] <didrocks> well, the ubuntu patch was done by upstream, you know ;)
[17:50] <MCR1> for example brightness and saturation settings are ignored...
[17:51] <MCR1> *of inactive viewports
[17:51] <MCR1> and other issues
[17:51] <didrocks> if you feel fixing them, that would be awesome!
[17:51] <MCR1> so I got to convince smspillaz and duflu ?
[17:51] <didrocks> exactly!
[17:51] <MCR1> ok
[17:51] <MCR1> thx
[17:51] <MCR1> 4 the info
[17:52] <didrocks> yw
[20:33] <Munchor> Hello guys
[20:33] <Munchor> When an appindicator does not remove itself properly, what is actually done