[00:39] <mfisch> When doing merges of desktop packages via UDD do you guys typically set distoseries to UNRELEASED for the MP?
[00:42] <RAOF> mfisch: If it's intended to land as-is, I'd set distroseries to saucy.
[00:42] <mfisch> RAOF: okay. my team uses UNRELEASED to prevent dputting from non-trunk, so I was curious. Thanks
[00:46] <RAOF> I use UNRELEASED for everything but the final dput, but when you're proposing a merge like that my view would be that you're doing a dput-by-proxy ☺
[02:49] <mterry> desrt, regarding your deja-dup hook script, no.
[02:56] <desrt> mterry: i found an awesome way to compact git repos
[02:58] <mterry> desrt, do tell
[02:58] <mterry> desrt, ah, and you want that before backup
[02:58] <desrt> mterry: yes.  precisely.
[02:59] <desrt> shrank my ~6GB of ~/code/ into ~15M
[02:59] <mterry> oh nice
[02:59] <desrt> and being as ~/code/ is the largest thing i have outside of ~/.cache/ this has a rather substantial impact on running time for dejadup
[02:59] <mterry> desrt, you could add a wrapper deja-dup script in ~/bin or something
[02:59] <mterry> desrt, but no official support.  There is a feature request bug I think
[03:00] <desrt> ya... i want something a bit nicer than that, i think
[03:00] <desrt> i also don't exactly just want a hook
[03:01] <desrt> i rather want a way to say "ya... this directory, let me give you some files to backup instead of what you find on the disk"
[03:01] <mterry> desrt, eh.  You could point deja-dup at ~/SmallCode instead of ~/Code and use a hook to sync the two right before backup
[03:01] <desrt> ya.  this is exactly what i was pondering
[03:01] <desrt> then put ~/code/ on the ignore list...
[03:02] <desrt> trouble is that not all stuff in ~/code/ is tuckable
[03:02] <desrt> (i call this new thing 'git tuck')
[03:02] <mterry> :)
[03:03] <mterry> alright, got to go to bed
[03:03] <desrt> ciao.
[03:39] <pitti> Good morning
[04:08] <Mirv> cyphermox: regarding the precise SRU patch piloting, I believe didrocks will want to do that as we have a history of doing that and he has the test document already
[07:11] <sil2100> Morning!
[07:12] <sil2100> Mirv: Im currently walking around the city looking for a place with free wifi
[07:13] <sil2100> Since it seems this city doesnt like free wifi, and mc donnalds filters out everything non-http
[07:13] <sil2100> But I see some hotspots I can try hacking into
[07:13] <sil2100> I mean, connecting into
[07:24] <Mirv> sil2100: :)
[07:24] <Mirv> and morning
[07:25] <Mirv> http should be enough for everybody (tm)
[07:25] <Mirv> actually, using corkscrew and friends even just http + forced proxy is usually enough for everything I do
[07:29] <sil2100> I would like to use irc normally, and while I use it locally, I would kike to have access to all the neat ports
[07:31] <sil2100> I need a proxy, *sighs*
[07:35] <lifeless> I need a hero?
[08:07] <Laney> ahoy
[08:59] <sil2100> Already have a question to didrocks, it's harder for me without him it seems ;)
[09:13] <sil2100> Mirv: do you know by any chance if all of our build-next projects are using autopilot 1.3 already?
[09:14] <sil2100> Mirv: since I noticed unity from the unity stack in Head was still using autopilot 1.2 strangely, even though our PPA already offers 1.3
[09:15] <sil2100> (but it was fetching it from the archives instead)
[09:37] <Mirv> (sil2100 gone, but merges still pending)
[10:07] <pitti> Laney: ah, thanks for http://people.canonical.com/~laney/upower-dbus-usage
[10:07] <Laney> np - it's a very dumb grep ATM though
[10:07] <pitti> Laney: for "to build list of packages using UPower for suspend/hibernate", are you going to use a pad again? (or the same pad)
[10:08] <Laney> I'll spend some time triaging it soon
[10:08] <Laney> yeah, probably a pad to avoid BP mail spam
[10:08] <pitti> i. e. http://pad.ubuntu.com/saucy-logind-transition
[10:08] <Laney> no opinion on the URL yet :-)
[10:08] <Laney> whoever does the work first can choose
[10:11] <pitti> Laney: I'm a bit confused -- so https://code.launchpad.net/~laney/indicator-datetime/use-upower/+merge/153809 was merged on 2013-05-03 with said commit message
[10:11] <pitti> https://launchpad.net/ubuntu/+source/indicator-datetime/+changelog has autolandings from 13.05.06
[10:11] <pitti> is that subsumed under "* Stop using ConsoleKit (LP: #1156613)"?
[10:11] <ubot2`> Launchpad bug 1156613 in indicator-datetime (Ubuntu) "Stop using ConsoleKit" [High,Fix released] https://launchpad.net/bugs/1156613
[10:11] <Laney> I think that some manual mangling of the changelog happened
[10:11] <pitti> oh, apparently yes
[10:12] <pitti> the changelog is the bug title, not the merge commit message
[10:12] <Laney> right, those don't get used
[10:12] <Laney> for d/changelog anyway
[10:12] <pitti> apt-get source shows that this is in, so this is done
[10:12] <Laney> I lost track a bit about what happened to those around release time
[10:12]  * pitti moves
[10:13] <pitti> thanks
[10:13] <Laney> there were split raring and trunk branches which had to be merged, and blah blah
[10:13] <Laney> cyphermox_ sorted it out anyway
[10:13]  * Laney puts the Queen's speech on
[10:13] <Laney> http://www.bbc.co.uk/news/uk-politics-22441280 you know you want to watch too
[10:27] <mlankhorst> they're red
[10:36] <mlankhorst> Laney: why do I cringe every time I hear more mucking with intellectual property
[10:36] <Laney> because you have no faith in politicians
[10:37] <mlankhorst> am I wrong? :p
[10:37] <Laney> dunno what these plans are
[10:38] <mlankhorst> making it easier for companies to lift copyrighted 'orphan works'
[10:39] <Laney> the eu is doing stuff on that too
[10:40] <mlankhorst> http://www.theregister.co.uk/2013/04/29/err_act_landgrab/
[10:40] <Laney> yeah i wouldn't trust that site's journalism
[11:48] <cyphermox_> Laney, mlankhorst: if you look at anything on thereg; look at the BOFH pages :)
[11:49] <Laney> heh, yeah, those are alright
[11:49] <Laney> they have some curious hatred of wikipedia
[11:50] <mlankhorst> who maintains the unity packages in ubuntu?
[11:50] <cyphermox_> Laney: http://xkcd.com/978/
[11:50] <cyphermox_> mlankhorst: various people, what do you need?
[11:51] <mlankhorst> cyphermox_: well i fixed up x 1.14 now, and made a xorg-server-omap-revert package to keep the pandaboard running. some coordination for uploading the pointer barrier fixes at the same time as xserver
[11:53] <sil2100> cyphermox_: morning!
[11:54] <cyphermox_> sil2100: hey
[11:55] <sil2100> cyphermox_: I was looking at the states of the stacks and wanted to check if autopilot 1.3 is already used for the projects, but I noticed for instance that unity from the unity stack Head still uses autopilot 1.2 even though 1.3 is in our PPA already
[11:55] <sil2100> cyphermox_: do you know why it's still only using 1.2 from the archives and not 1.3 from our PPA?
[11:56] <cyphermox_> sil2100: without checking, no
[11:56] <Laney> sil2100: which PPA?
[11:57] <cyphermox_> Laney: indeed, that's probably the best question to figure this out
[11:58] <sil2100> Laney: daily-build-next
[11:58] <Laney> link?
[11:58] <sil2100> https://launchpad.net/~ubuntu-unity/+archive/daily-build-next
[11:59] <Laney> sil2100: what's an example of a bad build in that PPA?
[11:59] <sil2100> Laney: what do you mean by 'bad build'
[11:59] <Laney> one which got the wrong autopilot
[12:00] <cyphermox_> Laney: it doesn't translate into a failed build
[12:00] <cyphermox_> it's a failed test though
[12:00] <Laney> I didn't say failed
[12:00] <sil2100> cyphermox_: hmm, not really
[12:00] <Laney> how can you see that it didn't do what you wanted?
[12:00] <sil2100> cyphermox_: since the thing is:
[12:00] <sil2100> Wait a moment guys
[12:00] <cyphermox_> sil2100: http://10.97.0.1:8080/job/ps-generic-autopilot-release-testing/283/label=autopilot-nvidia/console ?
[12:01]  * Laney stab vpn stab
[12:01] <cyphermox_> I hear you ;)
[12:01] <sil2100> http://10.97.0.1:8080/job/ps-generic-autopilot-release-testing/283/label=autopilot-ati/consoleFull
[12:01] <sil2100> Right
[12:01]  * sil2100 stabs himself
[12:01] <sil2100> But this one for isntance was ok, all ok
[12:01] <sil2100> And the thing is!
[12:01] <sil2100> It's not even using unity trunk here!
[12:02] <sil2100> It's using Unity from the raring archives :|
[12:02] <sil2100> Why is it using unity from the archives, since it was supposed to check the latest unity from the daily-build-next PPA instead
[12:02] <sil2100> As this is what the job is for
[12:02] <cyphermox_> sil2100: check configuration, make sure the package is listed in testpackages:
[12:03] <cyphermox_> Laney: https://jenkins.qa.ubuntu.com/job/ps-generic-autopilot-release-testing/283/
[12:03] <cyphermox_> this is the public copy of the same data ^
[12:03] <sil2100> cyphermox_: unity-autopilot is, and it's still installing it from raring it seems...
[12:03] <sil2100> cyphermox_: since installed_test_packages says:
[12:03] <sil2100> unity-autopilot is already the newest version.
[12:04] <sil2100> Which is not true, as the PPA should have a newer version
[12:05] <Laney> I don't see anything about the PPA in the apt-get update output
[12:05] <Laney> but we've gone into jenkins which means I have no clue what's going on so /me runs away screaming
[12:07] <cyphermox_> good move.
[12:08] <sil2100> I'll look into that in more detail then, thanks guys ;) Just wanted to know if there was something obvious going on
[12:08] <sil2100> But it seems nothing jenkins is obvious
[12:11] <cyphermox_> sil2100: there's not
[12:11] <cyphermox_> everything seems to me like it should have taken the new version, but it didn't
[12:12] <cyphermox_> evidently something is either wrong in the configuration, or in the code for the check jobs.
[12:19] <sil2100> Actually...
[12:19] <sil2100> cyphermox_: there's no unity in the daily-build-next PPA
[12:19] <sil2100> ?!
[12:19] <sil2100> Ok, there is
[12:19] <sil2100> cyphermox_: scratch that
[12:19] <cyphermox_> yeah, there are two :)
[12:20] <cyphermox_> one for raring and one for saucy. both build the unity-autopilot source package
[12:23] <sil2100> And for instance now the new test infrastructure would be useful, as we could simply fetch the test snapshot and check what exactly happened on the test system
[12:23] <cyphermox_> sil2100: mind if I let you hack at it for now, I'll tackle the other issues?
[12:23] <cyphermox_> hahah yeah :)
[12:23] <sil2100> cyphermox_: no problem, I'll poke you if I have some insider questions ;)
[12:24] <cyphermox_> autopilot-qt had an issue, and I reran head-phone just to check if we could convince that small one to go green
[12:24] <cyphermox_> sil2100: #ubuntu-unity; we can leave -desktop for the desktopy stuff.
[12:25] <cyphermox_> sil2100: heh, the phone stack tests will undoubtedly fail, utah is as wedged as ever.
[12:27]  * sil2100 sighs
[12:47] <mlankhorst> tkamppeter_: can you kill https://blueprints.launchpad.net/ubuntu/+spec/client-1305-convertibles-and-touch-desktop ? it's nothing more than a work item for the xorg session
[12:55] <cyphermox_> mlankhorst: about unity coordination stuff; wanna ping in #ubuntu-unity? you'll run a better chance of getting the right people.
[12:55] <cyphermox_> sil2100: this one is quite interesting: https://code.launchpad.net/~mathieu-tl/qml-friends/bootstrap-message/+merge/162971
[12:56] <cyphermox_> I'm not necessarily asking for a review from you, I think robru or ken should take a look, but I wrote the explanation for why the change is needed and there are links
[12:57] <mlankhorst> cyphermox_: well there's still a blocker for now, I guess when new nvidia-tegra lands I can get serious about moving x1.14 to saucy
[12:57] <cyphermox_> ok
[13:01] <sil2100> cyphermox: it seems a rather obvious fix, so I can review it and approve
[13:01] <sil2100> Good catch!
[13:02] <cyphermox> you're in super-friends?
[13:02] <cyphermox> how come I'm not in the cool kids group? :'(
[13:02]  * cyphermox cries
[13:02] <sil2100> It seems I am, since I can approve the merge it seems ;p But I don't know why!
[13:02] <sil2100> Since I never ever did anything super-friend'ly
[13:03] <cyphermox> right.
[13:16] <attente> sil2100, hi
[13:20] <sil2100> attente: hello!
[13:22] <attente> so i'm not really sure what else is needed to land unity-gtk-module
[13:22] <attente> i merged your ap-fixes branch, thanks for that
[13:23] <sil2100> attente: thanks for reviewing - do the tests as they look currently work OK on your system?
[13:24] <attente> yes, they do
[13:26] <attente> we still have a couple of gtk patches to remove it seems
[13:28] <sil2100> attente: ok, so let me check if it all works here as well
[13:29] <sil2100> attente: I also need to check what's the status with 13.04, but I need robru for that
[13:29] <sil2100> attente: since I have no clue what's happening with that - once I have a clear situation here, I'll do what needs to be done to re-enable it in daily build
[13:30] <sil2100> attente: s/13.04/autopilot 1.3
[13:30]  * sil2100 needs coffee
[13:31] <attente> heh, ok
[13:31] <attente> thanks
[13:39] <tkamppeter_> mlankhorst, hi
[13:43] <tkamppeter> mlankhorst, hi
[13:43] <mlankhorst> what i said above, there is no point in an entire session for a single bug, so please take it down :)
[13:44] <sil2100> robru: could you ping me when you're here?
[13:46] <tkamppeter> mlankhorst, it is not about this single bug. The bug is one work item. Other points are implementation of touch gestures (pinch to zoom, scroll by dragging, right click (long press? Ctrl+tap? ...), script triggered by flipping the screen of a convertible, how the convertible should behave in tablet mode, ...
[13:48] <mlankhorst> I honestly have no idea about that
[13:49] <tkamppeter> mlankhorst, I created this session to find the right people to take care of all these parts. Perhaps also the people who worked on the Nexus 7 can help here.
[17:02] <robru> cyphermox, sil2100 : hey, just woke up.
[17:05] <robru> cyphermox, ~super-friends contains ~canonical-product-strategy, are you not in that one?
[17:06] <cyphermox> I am not
[17:06] <robru> cyphermox, you should get in that one, it gives you near-godlike powers over launchpad ;-)
[17:06] <cyphermox> robru: sil2100: Mirv: figured out the issue with the API calls after all.
[17:07] <cyphermox> heh
[17:12] <cyphermox> I'm not sure I want that kind of responsibility ;)
[17:12]  * cyphermox -> lunch
[17:41] <larsu> desrt: do you know if we'll get the new gtk this cycle? Or will we stay on 3.8?
[17:41]  * larsu needs to update his custom menu item ipatch
[17:41] <desrt> i guess we'll get the new one...
[17:41] <desrt> no seb today?
[17:41] <larsu> I think it's a public holiday in France
[17:41] <desrt> btw: i landed the gtkmenutrackeritem patch
[17:41] <desrt> jasper is currently pouring over it
[17:41] <larsu> ah, nice!
[17:42] <desrt> i'd appreciate the same from you, since you will be the other consumer
[17:42] <larsu> let me guess, he hates the Gtk namespace?
[17:42] <desrt> ya.... he wants egg
[17:42] <desrt> we discussed it
[17:42] <desrt> not going to happen
[17:42] <larsu> ugh, that's equally stupid
[17:42] <larsu> have a bug #?
[17:43] <desrt> ya
[17:44] <desrt> https://bugzilla.gnome.org/show_bug.cgi?id=699934
[17:44] <ubot2`> Gnome bug 699934 in GtkApplication "add GtkMenuTrackerItem" [Normal,Unconfirmed]
[19:05] <sil2100> robru: hi!
[19:06] <sil2100> robru: so, what I wanted is - what's the state of the 1.3 autopilot transition?
[19:16] <sil2100> robru: ping
[19:17] <kenvandine> sil2100, i just found out why we are getting so many autopilot failures
[19:17] <kenvandine> the qa guys added some debugging for us
[19:18] <kenvandine> we have autopilot-phablet in testpackages
[19:18] <kenvandine> and that isn't installable
[19:18] <kenvandine> we need autopilot-touch
[19:18] <sil2100> kenvandine: oh
[19:18] <sil2100> autopilot-touch? What's that?
[19:18] <kenvandine> but that also isn't going to be installable... because it depends on python-ubuntu-platform-api
[19:18] <kenvandine> the new autopilot-phablet :)
[19:18] <sil2100> kenvandine: I thought that autopilot-phablet was the touch-based autopilot
[19:18] <kenvandine> they renamed it for 1.3
[19:18] <sil2100> Ah, ok, for 1.3
[19:19] <sil2100> fginther: ping
[19:19] <kenvandine> it's in the ppa
[19:19] <kenvandine> but...
[19:19] <sil2100> fginther: did you quick-fix the generic jobs?
[19:19] <kenvandine> it depends on a missing package
[19:19] <sil2100> kenvandine: that can only be used on devices?
[19:19] <fginther> sil2100, yes, I believe it is working now
[19:19] <kenvandine> not sure
[19:20] <sil2100> kenvandine: I think we'll have to poke thomi about this ultimately, since my understanding was that autopilot 1.3 will be able to 'emulate' touch input even on a desktop device
[19:20] <sil2100> fginther: excellent! Big thanks
[19:20] <fginther> sil2100, np
[19:20] <kenvandine> sil2100, maybe we should change it to autopilot-desktop and see if that works?
[19:21] <kenvandine> sil2100, i have a branch changing it in cups2d
[19:21] <kenvandine> if you can give me a quick approval i'll rerun a job
[19:21] <kenvandine> i can try changing it to autopilot-desktop
[19:21] <kenvandine> oh... i think we can just remove it
[19:22] <sil2100> kenvandine: no problem, send the link ;)
[19:22] <sil2100> kenvandine: I think indeed maybe let's try using the desktop autopilot
[19:22] <sil2100> Maybe it would have bindings for touch for the desktop
[19:23] <fginther> sil2100, kenvandine, for what it's worth. autopilot-desktop is the expected package to use on a desktop install
[19:25] <kenvandine> sil2100, https://code.launchpad.net/~ken-vandine/cupstream2distro-config/autopilot-touch/+merge/163037
[19:25] <kenvandine> fginther, sil2100: yeah, we had added autopilot-phablet to testpackages as a hack to work around it not getting installed before
[19:26] <kenvandine> we don't need it at all now, there are depends that bring in python-autopilot
[19:26] <kenvandine> which depends on autopilot-touch || autopilot-desktop
[19:30] <fginther> sil2100, there may be autopilot 1.3 issues related to ps-generic-autopilot. It was working with the older 1.2 version where there was no autopilot-touch || autopilot-desktop
[19:34] <fginther> sil2100, I did a local test, looks like it should work
[19:38] <sil2100> \o/
[19:38] <sil2100> kenvandine: approved
[19:40] <kenvandine> sil2100, thanks
[19:40] <kenvandine> i'll redeploy
[19:46] <robru> sil2100, sorry, was on lunch. as far as my end goes, I still haven't made any progress in getting autopilot enabled for webapps. I gotta work with vrruiz on that, it seems stale & incomplete to me
[19:51] <sil2100> robru: hm, ok, so we still need to get that sorted out
[19:55] <kenvandine> fginther, the guy from #qa that helped debug the autopilot/utah issues pointed out a couple other things that should be fixed
[19:56] <kenvandine> are you the right person to fix the utah script?
[19:56] <fginther> kenvandine, yes
[20:20] <robru> ok, I am going to upgrade to suacy... wish me luck!
[20:47] <robru> success!
[20:48] <desrt> robru: boring.
[20:49] <desrt> if you want fun, try an f19 upgrade
[20:50] <robru> haha
[20:50] <desrt> good for that oldschool "i need to debug my bootloader" linux feel
[20:50] <robru> hey desrt, you'd probalby know this: how can I tell what app created a certain window? I have a mysterious window on my desktop and I'm not sure where it's coming from
[20:51] <desrt> xprop will tell you
[20:51] <desrt> xprop | grep PID
[20:51] <desrt> then click
[20:52] <robru> desrt, great. so what the hell is gcr-prompter? ;-)
[20:52] <desrt> something about the keyring i guess
[20:53] <desrt> the thing that asks you "do you wnat to allow access?" maybe?
[20:53] <robru> desrt, well, it's asking me for a password, but I'm not sure for what. It says "for account rbpark@gmail.com", which I assume is my google account, so I enter my google account password, but it tells me that it's incorrect. except I just logged into google 2 seconds ago, so I'm quite confident that I know what my password is. so clearly this is asking for soemthing else, and I'm not sur ewhat
[20:54] <robru> so this keeps popping up randomly, and i keep cancelling out of it, and I haven't noticed any features being broken by the inability to login to this thing
[20:54] <desrt> maybe something to do with online accounts?
[20:54] <robru> kenvandine, ^^
[20:54] <robru> ;-)
[20:54] <desrt> maybe use 'ps f' to find out what spawned gcr-prompter?
[20:56] <desrt> well, 'ps xf' you would need
[20:56] <robru> there we go ;-)
[20:57] <desrt> any smoking gun there?
[20:57] <robru> desrt, yep, 'init --user'
[20:57] <robru> ;-)
[20:57] <desrt> that's probably not a smoking gun...
[20:57] <robru> I know
[20:58] <robru> was being sarcastic
[20:58] <desrt> i'm guessing upstart does the prctl() thing to get to be the new grandparent process for everything in the session
[20:58] <desrt> so everything that gets orphaned get picked up by it
[20:58] <robru> desrt, i guess. still not sure what password it wants me to put in there though
[20:59] <robru> or what it's even for
[20:59] <desrt> VIRUS
[20:59] <robru> the online accounts pane in system settings doesn't report any failures
[20:59] <desrt> check seahorse maybe?
[20:59] <desrt> something obvious may turn up in there
[21:01] <robru> desrt, dunno, seahorse opened fine, none of the entries there reference rbpark@gmail.com
[21:01] <desrt> i'd continue on the previous course of blaming ken, then :)
[21:02] <robru> it looks like https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549
[21:02] <ubot2`> Launchpad bug 1044549 in gcr (Ubuntu) "The "Access Prompt" randomly pop up!" [High,Triaged]
[21:03] <robru> oh, workaround in comment #14
[21:03] <robru> yay
[21:04] <desrt> blame rishi, then :)
[21:04]  * desrt wonders why goa is even on ubuntu?
[21:04] <robru> for the gnome remix
[21:04] <robru> I guess
[21:05] <desrt> ah.  you have it installed?
[21:05]  * kenvandine reads back
[21:05] <robru> well, I was using Gnome-Shell through the Quantal cycle, and only switched to Unity at some point early in the raring cycle. so yeah, I had all the gnome stuff installed.
[21:06] <desrt> makes some sense, then
[21:07] <kenvandine> robru, oh... so you figured it out?
[21:07] <robru> kenvandine, I guess so. it remains to be seen if the workaround from that bug actually fixes it or not though
[21:07] <kenvandine> i doubt that is triggered by UOA
[21:08] <robru> yeah, seems a GOA thing that's attacking me from beyond the grave...
[21:09] <robru> https://launchpad.net/gcr also, it seems pitti is to blame ;-)
[21:15] <robru> brb, gotta run to the store
[21:55] <dupondje> Yeey, Empathy is totally broken :(
[21:57] <dupondje> https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1175582 https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1177833 https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1176757 https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1174208 https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1173472 https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1163961
[21:57] <ubot2`> Launchpad bug 1175582 in empathy (Ubuntu) "Empathy not displaying any online contacts" [Undecided,New]
[21:57] <ubot2`> Launchpad bug 1177833 in empathy (Ubuntu) "empaty does not connect to any account. and it does not show the yahoo contacts avatar." [Undecided,New]
[21:57] <ubot2`> Launchpad bug 1176757 in empathy (Ubuntu) "doesn't connecting to any account except facebook" [Undecided,New]
[21:57] <ubot2`> Launchpad bug 1174208 in empathy (Ubuntu) "Empathy shows no contacts in Ubuntu 13.04" [Undecided,Confirmed]
[21:57] <ubot2`> Launchpad bug 1173472 in empathy (Ubuntu) "the facebook accounts in empathy shown disconnected" [Undecided,Confirmed]
[21:58] <dupondje> seems buggy no ? :)