[00:09] <Smaug> hey all, I just installed ubuntu 12.04 on a computer.   When I turn it on, the log in page comes up.  When I log in, it seems to hang.  It shows the background and my mouse and nothing else.  The desktop never comes up.  Thoughts?
[00:10] <jbicha> !support
[00:10] <ubot2> The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org and http://askubuntu.com
[00:12] <Smaug> ty
[05:29] <pitti> Good morning
[06:11] <didrocks> hey pitti, how are you?
[06:11] <didrocks> (didn't look at IRC, lost in emails until now)
[06:11] <pitti> hey didrocks
[06:11] <pitti> didrocks: quite fine, thanks! how about yourself?
[06:11] <didrocks> pitti: I'm good, thanks!
[06:12] <pitti> yay for another huge Mir thread
[06:13] <didrocks> yeah, not a really productive one…
[06:28] <duflu> didrocks: Sorry, was that my fault? Should I avoid the list in future?
[06:32] <didrocks> duflu: we are not talking about the same thread I guess :) (the one on ubuntu-devel)
[06:33] <didrocks> duflu: you didn't talk on that one?
[06:33] <duflu> didrocks: Good, no, different. Good morning then :)
[06:33] <didrocks> (or maybe you did but your message is still moderated)
[06:33] <didrocks> hey duflu! how are you?
[06:33] <duflu> didrocks: Good. You?
[06:33] <didrocks> I'm good, thanks!
[06:58]  * didrocks soon to be renamed professional packages reviewer
[07:04] <mlankhorst> bonjour
[07:05] <pitti> bonjour Monsieur mlankhorst, comment vas-tu ?
[07:05] <mlankhorst> and the equivalent in english: sup?
[07:06] <pitti> let's say, the equivalent in the US Midwest :)
[07:06] <didrocks> mlankhorst: hey! how are you?
[07:09] <mlankhorst> es geht gut
[07:14] <jibel> good morning
[07:15] <didrocks> salut jibel, ça va?
[07:16] <jibel> salut didrocks , bien et toi?
[07:16] <didrocks> ça va
[07:33] <seb128> good morning desktopers
[07:35] <pitti> bonjour seb128
[07:35] <seb128> pitti, salut, ça va ?
[07:35] <pitti> seb128: il fait très chaud; je vais bien, mais je dois manger beaucoup de glace :)
[07:36] <pitti> seb128: et toi ?
[07:36] <seb128> ici aussi il fait (trop) chaud
[07:36] <seb128> glace \o/
[07:38]  * pitti -> out for a bit
[07:38] <seb128> pitti, bonne glace !
[07:38] <pitti> not for glace, some errands :)
[07:39] <seb128> hehe
[07:39] <didrocks> salut seb128
[07:39] <seb128> didrocks, salut ! en forme ? pas trop chaud ?
[07:40] <didrocks> seb128: si, chaud, enfin là, ça va encore mais d'ici 2/3 heures, ça va être la fournaise :)
[07:40] <didrocks> et toi?
[07:40] <seb128> ça va, je profite de la fraicheur matinale ;-)
[07:40]  * seb128 wants temperate weather
[07:40] <seb128> not 16°C, not 35°C, just good old 25°C
[07:41] <didrocks> heh
[07:53] <didrocks> sil2100: no more "bootstrap" case now, you can add whatever you need after "automatic revision from…" apart from something containing: "(ppa:.*)"
[07:53] <didrocks> which is only used for feature branches
[07:57] <sil2100> \o/
[07:57] <sil2100> /o/
[07:57] <sil2100> \o\
[08:02] <Laney> morn'
[08:02] <seb128> Laney, good morning
[08:02] <didrocks> hey Laney
[08:02] <Laney> hey
[08:02] <Laney> how's it going?
[08:02] <didrocks> I'm fine, thanks! yourself?
[08:02] <seb128> good! you?
[08:03] <Laney> had to get up at dawn to scare off some fighting birds :P
[08:03] <Laney> but otherwise good
[08:10] <seb128> lol, be nice to the birds!
[08:12] <mlankhorst> heheehhehe
[08:17] <asac> anybody else gets "self-signed certificate" warnings when using google online accounts?
[08:17] <asac> maybe talk.google.com is an abandoned host?
[08:21] <seb128> asac, I get those as well yes
[08:23] <mlankhorst> or MITM :p
[08:23] <mlankhorst> https://talk.google.com didn't give me a warning, fwiw..
[08:24] <asac> maybe you checked "Remember this choice for future connections" at some point
[08:25] <asac> ah i see what you mean
[08:26] <jpds> mlankhorst: Well, that's HTTPS, not XMPP.
[08:26] <asac> maybe this is a jabber connection?
[08:26] <asac> :)
[08:26] <asac> yeah
[08:26] <jpds> Considering they've
[08:26] <jpds> ...abandoned that for hangouts.
[08:26] <asac> i presume that gtalk just ships this as a whitelist in their app
[08:26] <asac> or something
[08:26] <jpds> asac: No, it is no more.
[08:26] <asac> something else? not xmpp?
[08:26] <jpds> https://en.wikipedia.org/wiki/Hangouts
[08:27] <asac> hmm.
[08:27] <asac> so then its probably because we use a legacy service :)
[08:28] <asac> hmm. no official api?
[08:28] <asac> not even a subset for just chat?
[08:28] <asac> that sucks :)
[08:28] <asac> i hope i am not getting this right
[08:30] <asac> https://developers.google.com/+/hangouts/
[08:30] <asac> ok thats in-hangout api
[08:30] <jpds> asac: No, it's completely closed service.
[08:31] <asac> guess they dont like us leaeching their services :)
[08:33] <asac> http://tech.slashdot.org/story/13/05/20/2315216/google-drops-xmpp-support
[08:33] <asac> so actually pretty recently
[08:34] <jpds> Quite.
[08:44] <asac> jpds: so seems they continue to support xmpp on client, just not federation after all http://arstechnica.com/information-technology/2013/05/hands-on-with-hangouts-googles-new-text-and-video-chat-architecture/
[08:44] <asac> i believe we should hardcode the cert as "known to be good" and not annoy the user :)
[08:44] <asac> seb128: ?
[08:45] <jpds> asac: Haven't you used Hangouts before?
[08:45] <asac> jpds: i know hangouts
[08:45] <asac> probaly have been 1k hours on them already :)
[08:45] <asac> counting
[08:46] <seb128> asac, I'm not sure I've a grasp on the issue ... are they discontinuing the service (in this case we should stop using it at all) or do they keep running in (in which case why is the certificate buggy)?
[08:46] <asac> seb128: they will continue to support xmpp for clients
[08:47] <asac> but not jabber federation
[08:47] <asac> (to lock out MS and FB to leech on them)
[08:47] <asac> so that seems to be OK
[08:47] <asac> now the real issue is that there are warnings about self-certs ... those we can fix by whitelisting this known good cert maybe?
[08:48] <seb128> asac, that makes sense
[08:48] <seb128> not sure if that error comes from empathy or uoa
[08:48] <seb128> xclaesse, ^ do you know?
[08:48] <asac> not sure how to really know though that its a good server that we currently talk to :)
[08:48] <Laney> I'm getting that warning about chat.facebook.com FYI
[08:48] <asac> hmm
[08:48] <asac> maybe its a bug on how we do ssl?
[08:49] <asac> or maybe they really dont bother and just whitelist their own certs in their apps
[08:49] <Laney> it worked before
[08:49] <Laney> so something has changed
[08:50] <xclaesse> seb128, what's the problem ?
[08:50] <xclaesse> facebook & gtalk connects fine here
[08:52] <Laney> infact it's MSN and GTalk too :-)
[08:52] <xclaesse> MSN connects fine via xmpp here too :)
[08:52] <xclaesse> did not see any cert issue
[08:53] <xclaesse> if the cert cannot be validated, empathy will ask the user to accept it or not
[08:53] <Laney> yeah
[08:59] <seb128> xclaesse, it seems everyone on saucy see certificat confirmation dialog, do you know what could be going on there?
[08:59] <xclaesse> seb128, smcv on #telepathy is our cert expert ;-)
[08:59] <xclaesse> seb128, afaik we are using GIO something to validate certs
[09:00] <seb128> bah, nautilus keeps segfaulting when I open it here
[09:00] <seb128> xclaesse, http://ubuntuone.com/2uxNfUpH4SLqTOzoY05D3p
[09:00] <seb128> is what I see
[09:01] <seb128> xclaesse, let's move to #telepathy
[09:01] <xclaesse> seb128, maybe saucy's CA doesn't work well
[09:08] <seb128> xclaesse, I've no clue about CA, let's see if/when Simon replies
[09:09] <xclaesse> seb128, it works fine on raring, so something changed in saucy
[09:10] <xclaesse> does it have different version of gabble?
[09:10] <seb128> https://launchpad.net/distros/ubuntu/+source/telepathy-gabble
[09:10] <xclaesse> gnutls maybe
[09:10] <seb128> 0.16.5 -> 0.16.6
[09:10] <seb128> we updated glib-(networking) to 2.37
[09:10] <seb128> you said that's used for cert verification
[09:11] <seb128> https://launchpad.net/ubuntu/+source/gnutls26
[09:11] <seb128> that didn't change
[09:12] <xclaesse> hm, release notes of gabble .6 have lots of stuff about tls actually
[09:12] <xclaesse> seb128, could you try with gabble .5 on saucy ?
[09:13] <xclaesse> quickly checking gabble code, it is gnutls doing the checks, no gio. But I'm not really familiar with that code
[09:15] <seb128> xclaesse, downgrading gabble doesn't change anything
[09:16] <xclaesse> wocky does not seems to be using GTlsConnection yet, so I don't think it is using GIO' stuff
[09:16] <Laney> gcr?
[09:16] <xclaesse> yep could be gcr issue
[09:17] <xclaesse> seb128, btw I think you guys should push gabble .6 to raring
[09:17] <xclaesse> seb128, release notes says "This release fixes a man-in-the-middle attack. You should upgrade."
[09:17] <seb128> xclaesse, security team backported that fix it seems: https://launchpad.net/ubuntu/+source/telepathy-gabble/0.16.5-0ubuntu1.1
[09:18] <xclaesse> ah ok, good :)
[09:22] <seb128> Laney, xclaesse: not easy to downgrade gcr without empathy :/
[09:22] <Laney> even with rebuilding?
[09:22] <seb128> I didn't try that
[09:22] <seb128> empathy: error while loading shared libraries: libgcr-ui-3.so.1: cannot open shared object file: No such file or directory
[09:23] <seb128> when just trying to downgrade gcr
[09:24] <seb128> not sure I care enough atm to spend more time on that though
[09:24] <seb128> Laney, if you want to give that a try please do
[09:25] <seb128> but I'm not sure how useful that is, even if we determine it's the gcr update, we will still need to fix the bug in the new version
[09:25] <xclaesse> those things have always been fragile :(
[09:30] <seb128> ok, I'm out for some exercice before it gets too hot for that
[09:32] <czajkowski> aloha
[09:42] <Laney> well I tried building empathy against gcr 3.6 and it doesn't fix it
[09:52] <mlankhorst> seb128: can you approve https://blueprints.launchpad.net/ubuntu/+spec/client-s-xorg-general
[09:55] <didrocks> hey czajkowski-from-the-other-side-of-the-world :)
[09:56] <czajkowski> at least here I have sunshine!
[09:57] <Laney> also jet lag :P
[09:57] <czajkowski> 3am yesterday 4am today :/
[09:58]  * ogra_ hands czajkowski a handfull of melatonin for tomorrow night .... helps a lot with that
[09:59] <Laney> seb128: xclaesse: Downgrading gnome-keyring to 3.6.3 fixes it here
[09:59] <Laney> (just that)
[10:00] <czajkowski> whoo new laptop X1 carbon to play with when I come back to UK
[10:01] <czajkowski> wiping and installing Ubuntu on it, handed back the air I was given, got some odd looks for that
[10:04] <davmor2> czajkowski: you can install ubuntu on a mac air you know :)
[10:05] <hyperair> i hear it's a pain though
[10:06] <Laney> works fine enough
[10:06] <hyperair> how's it stability wise?
[10:06] <Laney> had to install some daemon to control the fans
[10:06] <Laney> but good
[10:06] <czajkowski> davmor2: I'd never hear the end of it from the other half :)
[10:06] <hyperair> cool
[10:07] <hyperair> are the installation steps suitable for mere mortals, or do you need to be halfway godlike to do so?
[10:07] <Laney> pretty standard
[10:08] <hyperair> hmm cool
[10:08] <Laney> that's not to say that i wouldn't choose a thinkpad given the free choice
[10:09] <hyperair> heh
[10:09] <hyperair> how are the newer thinkpads with hardware support?
[10:09] <hyperair> my thinkpad e220s is crap
[10:10] <hyperair> trackpoint doesn't work properly with suspend/resume, gets detected as ps/2 generic mouse..
[10:10] <hyperair> and snb-i915 gpu hangs every few hours
[10:45] <czajkowski> having not used empathy before is there a way to stop the notifications displaying ?
[10:52] <seb128> mlankhorst, done
[10:52] <seb128> Laney, ok, it might be worth opening a gnome-keyring upstream bug about it, do you want to do it or should I?
[10:53] <Laney> I am trying to boot GNOME OS to verify it but I can't get it to work :P
[10:53] <Laney> if you could that would be good
[10:53] <seb128> sure, shower first though
[11:18] <xclaesse> Laney, seb128: which version of gnome-keyring?
[11:18] <xclaesse> with the gnome3 ppa on raring it works
[11:18] <xclaesse> 3.8.2-0ubuntu1~raring1
[11:19] <xclaesse> that should be what saucy has, no?
[11:19] <Laney> 3.8.2 bad 3.6.3 good
[11:19] <Laney> just replacing that one package in saucy
[11:19] <xclaesse> Laney, 3.8.2 works here on raring + gnome3 ppa
[11:25] <Laney> also works for me in a fedora vm
[11:28] <Laney> maybe it's something to do with UOA
[11:29] <xclaesse> I doubt that
[11:29] <sil2100> didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/missing_libical/+merge/170040
[11:30] <xclaesse> Laney, check debug msg of empathy-auth-client
[11:30] <didrocks> sil2100: ? libical isn't in the stack we are interested in
[11:30] <didrocks> sil2100: it makes no sense to add it
[11:30] <didrocks> we don't want to add every dep on our stacks :)
[11:30] <xclaesse> G_MESSAGES_DEBUG=all EMPATHY_DEBUG=all /usr/lib/empathy/empathy-auth-client
[11:30] <xclaesse> then connect your account
[11:30] <sil2100> didrocks: but it's failing to do the check job now
[11:31] <sil2100> didrocks: how can we make it pass then?
[11:31] <sil2100> SInce it's failing because of extra installed packages
[11:31] <didrocks> sil2100: check with whole ppa? to disable the check?
[11:31] <sil2100> didrocks: and will that work from that time onwards?
[11:31] <didrocks> sil2100: just for that run
[11:32] <didrocks> ah
[11:32] <sil2100> didrocks: so next time indicators will fail then
[11:32] <sil2100> ?
[11:32] <didrocks> sil2100: hum no
[11:32] <didrocks> sil2100: because it will move to the release pocket
[11:32] <Laney> xclaesse: abort_verification: Verification error 6, aborting...
[11:32] <didrocks> sil2100: and will be installed by default as the transition will end
[11:32] <didrocks> right?
[11:32] <Laney> xclaesse: repros for me in a VM too so if you can set one of those up you should be able to get it
[11:33] <sil2100> didrocks: hm, right!
[11:33] <didrocks> sil2100: maybe we'll need to redo the container tomorrow morning if it didn't pick the right iso yet, but then, we should be fine
[11:35] <didrocks> sil2100: I pasted the discussion on the MP for reference :)
[11:36] <sil2100> didrocks: good! Sometimes I need to remember that it's all 'transition' right now, noting that!
[11:36] <didrocks> sil2100: no worry, I prefer you ask than doing without this :)
[11:37] <didrocks> sil2100: even for me, sometimes the big puzzle is quite hard :p
[11:37] <sil2100> didrocks: is a simple revert like this fine? https://code.launchpad.net/~sil2100/libappindicator/revert_debian_rules ;)
[11:37] <didrocks> sil2100: perfect, #nochangelog wasn't really needed as you touched debian/changelog, but fine with it as well :)
[11:38] <seb128> Laney, xclaesse: p11-kit changed in saucy as well and changed the location of the key files, not sure if some files is still at the old location or something
[11:45] <sil2100> didrocks:  https://code.launchpad.net/~sil2100/libappindicator/revert_debian_rules/+merge/170050 then ;) I know I could have pushed directly, buuut I noticed that Mathieu did the commit through a MR, so I would feel silly to push directly without a request
[11:46] <xclaesse> seb128, could be that, indeed
[12:04] <Laney> ah
[12:04] <Laney> seb128: try installing p11-kit
[12:05] <seb128> Laney, that fixes it?
[12:05] <Laney> I think so, but I've been monkeying with versions so ...
[12:06] <Laney> that's where the new trust module thingy is
[12:06] <Laney> which was removed from g-k in 3.8
[12:07] <xclaesse> p11-kit is not installed here
[12:07] <seb128> Laney, yeah, that fixes it!
[12:07] <Laney> cool
[12:08] <Laney> should we have g-k depend on that?
[12:08] <pitti> (FTR, needs MIR)
[12:09] <Laney> yeah ...
[12:09] <Laney> should be eligible though
[12:10] <Laney> oh no wait, the source is already in main
[12:11] <seb128> pitti, it's only a binary of a source already in main?
[12:11] <Laney> it is
[12:11] <seb128> Laney, not sure, is g-k using it or empathy?
[12:11] <pitti> oh, indeed
[12:11] <seb128> having g-k depends on it works for me
[12:12] <Laney> well I see this in NEWS:  * Remove the roots-store module replaced by p11-kit 0.16+ trust module
[12:12] <Laney> but tbh I don't know how it all fits together
[12:13] <Laney> yeah they added it in Debian
[12:13] <Laney> I'll do that now then
[12:15] <seb128> Laney, thanks
[12:19] <seb128> asac, ^ btw
[12:20] <seb128> asac, install "p11-kit", should fix the certificate issue
[12:20] <Laney> grr
[12:20]  * Laney brings the VCS up to date
[12:21] <pitti> Laney: oh, speaking of VCS
[12:21]  * Laney runs
[12:21] <pitti> Laney: I recently updated the sessioninstaller bzr
[12:21] <pitti> Laney: no worries :)
[12:22] <pitti> Laney: and I noticed that you applied some debian/patches/ bits with changes from upstream
[12:22] <pitti> Laney: this is much easier with bzr bd
[12:22] <asac> seb128: will that come through ubuntu-desktop now?
[12:22] <pitti> Laney: next time, just bump the bzr revno in the  0.1.2+bzr1234 version number
[12:22] <asac> if so i will wait for that :)
[12:22] <seb128> asac, yes
[12:22] <asac> (i have since set this warning to ignore, so i might not see it
[12:22] <asac> )
[12:22] <Laney> pitti: hm, never done anything like that
[12:22] <pitti> Laney: bzr bd is clever enough to see this, check out upstream at that rev, build an orig for that, and build a package
[12:23] <Laney> interesting
[12:23] <pitti> Laney: like in https://launchpad.net/ubuntu/+source/sessioninstaller/0.20+bzr134-0ubuntu4
[12:23] <pitti> mterry did a few of those as well
[12:23] <Laney> I mean the magic orig stuff
[12:23] <seb128> oh, come on nautilus, wth, every day it segfaults the first time I click on it
[12:24] <Laney> sounds cool!
[12:24] <pitti> Laney: anyway, it's effing awesome magic, and much easier than quilting around :)
[12:24] <pitti> Laney: just FYI
[12:24] <Laney> thanks for the tip
[12:24] <pitti> seb128: oh, je ne suis pas seul !
[12:25] <seb128> pitti, non, moi aussi ... j'ai gagné le droit de le débugger ?
[12:26] <pitti> seb128: non, mais j'ai le mis sur Launchpad
[12:27] <Laney> 3.8 time ;-)
[12:27]  * pitti looks at today's /var/crash/_usr_bin_nautilus.1000.crash
[12:30] <pitti> seb128: seems I got the one in gtk_icon_info_get_attach_points(), you as well?
[12:30] <seb128> pitti, yes
[12:30] <seb128> I wonder if those are after upgrades when the icon cache is refreshed or something
[12:31] <seb128> Laney, speaking of 3.8 I should build/install it, it's almost ready in the gnome3 vcs
[12:32] <pitti> peut-être, il souvent bloque dans les matins
[12:32] <pitti> oh, 3.8 for nautilus or for everything/
[12:32] <pitti> ?
[12:32] <pitti> I'm just about to start backporting the g-s-d power 3.8 bits to 3.6 (for bug 1180513)
[12:32] <ubot2> Launchpad bug 1180513 in gnome-settings-daemon (Ubuntu) "lid close actions are ignored laptop always suspends" [High,Triaged] https://launchpad.net/bugs/1180513
[12:33] <seb128> pitti, nautilus, g-s-d/g-c-c are the only one missing 3.8 atm I think
[12:33] <seb128> pitti, so we sort have the set already
[12:33] <seb128> g-s-d/g-c-c being trickier because of the number of changes they did and our number of patches
[12:33] <seb128> the fact that they made harder to have external panels (that we need)
[12:33] <seb128> the depends on the new ibus as well (which is quite broken out of GNOME)
[12:36] <seb128> pitti, my gut feeling is that it's going us to take at while before having g-s-d/g-c-c ready for the archive, especially that our focus is mobile this cycle ... I wouldn't count on 3.8 to be in saucy
[12:37] <pitti> ack
[12:37] <pitti> btw, bug 1187709
[12:37] <ubot2> Launchpad bug 1187709 in nautilus (Ubuntu) "nautilus crashed with SIGSEGV in gtk_icon_info_get_attach_points()" [Medium,Confirmed] https://launchpad.net/bugs/1187709
[12:37] <seb128> thanks, I will check upstream/valgrind it
[13:28] <sil2100> seb128: ping :)
[13:28] <seb128> sil2100, hey
[13:29] <sil2100> seb128: I'm looking at lp:gnome-control-center-unity/raring right now and the latest commit looks like a fix, but no bug has been attached to it
[13:31] <sil2100> seb128: would it be much bother to open up a bug for that? Since I guess this way we'll have all the fixes in an SRU documented by bugs that the SRU team could assert
[13:31] <sil2100> seb128: I would modify the changelog then
[13:31] <seb128> sil2100, indeed, I wonder why it has no bug info
[13:31] <seb128> sil2100, https://launchpad.net/ubuntu/+source/gnome-control-center-unity/1.3daily13.06.13-0ubuntu1
[13:32] <seb128> sil2100, that saucy upload had one ... I guess I forgot the --fixes lp: when doing the backport
[13:32] <seb128> sil2100, #1173818 is the bug to use
[13:32] <seb128> sil2100,  let me update the bug to be SRU compliant
[13:33] <sil2100> seb128: thanks! Great, I'll modify the changelog then
[13:35] <seb128> sil2100, bug updated
[13:51] <czajkowski> Laney: any idea what would cause a geoip crash on raring ?
[13:51] <czajkowski> keep getting them today
[14:15] <Laney> czajkowski: 'fraid not
[14:15] <Laney> do you have any more details?
[14:15] <Laney> like the program or package that is crashing?
[14:15] <Laney> https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1157232 is quite a high one on errors
[14:15] <ubot2> Ubuntu bug 1157232 in ubuntu-geoip (Ubuntu) "ubuntu-geoip-provider crashed with SIGSEGV in _dbus_header_get_byte_order()" [High,Confirmed]
[14:20] <czajkowski> Laney: it says it'll send a report but no bug opens
[14:21] <Laney> it'll be reporting to errors
[14:21] <seb128> it probably reports the issue to errors.ubuntu.com
[14:21] <czajkowski> al I know is I'm having to reboot the machine every 20 mins
[14:21] <czajkowski> :/
[14:21] <Laney> a geoip crash is making you reboot?
[14:21] <czajkowski> Laney: everything dies
[14:21] <czajkowski> wifi goes
[14:24] <seb128> seems like a kernel issue or something
[14:25] <Laney> czajkowski: look for a file with the right-ish timestamp in /var/crash (ls -l /var/crash) and then apport-bug /that/file
[14:25] <czajkowski> seb128: yeah but geoip is the only thing coming up
[14:26] <czajkowski> Laney: ahhh http://pastebin.ubuntu.com/
[14:28] <Laney> don't think you meant that :P
[14:28] <czajkowski> nothing to see here
[14:28] <czajkowski> move along :)
[14:29] <czajkowski> Laney: http://pastebin.ubuntu.com/5777262/
[14:30] <Laney> apport-bug /var/crash/_usr_lib_ubuntu-geoip_ubuntu-geoip-provider.1000.crash
[14:31] <seb128> czajkowski, firefox 'http://errors.ubuntu.com/user/'$(printf $(sudo cat /sys/class/dmi/id/product_uuid) | sha512sum)
[14:31] <seb128> czajkowski, that should show you the issues you reported to e.u.c
[14:32] <czajkowski> ah
[14:33] <Laney> mine is some huge list of uuids
[14:34] <Laney> would hate to have to find a single crash in that
[14:34] <seb128> Laney, talk to ev ... ;-)
[14:34] <Laney> might as well file a bug :P
[14:35] <czajkowski> wow
[14:35] <czajkowski> I've a whole lot of data there
[14:35] <czajkowski> thanks seb128
[14:35] <seb128> yw
[14:37] <pitti>   * Start gsd via user session if starting 'unity' too. This is in preparation
[14:37] <pitti>     for starting unity directly.
[14:37] <pitti> Laney: ^ is that ok to upload?
[14:38] <pitti> Laney: I'm about to do a g-s-d upload to make seb128 happy again
[14:38] <Laney> pitti: yes, should be a noop currently
[14:38] <Laney> that unity job doesn't get used
[14:38] <Laney> but if you want to test it I won't complain ;)
[14:50] <jbicha> hi, is someone planning to finish the indicator-datetime upload? :)
[14:51] <pitti> seb128: there, g-s-d uploaded for respecting lid handling action config again
[14:53] <seb128> pitti, \o/
[14:53] <seb128> jbicha, sil2100 is working on it
[14:56]  * pitti goes to update gvfs to 1.17.2
[14:57] <Laney> ah, back in the land of gnome updates?
[14:57] <pitti> Laney: it's too hot to do anything which requires serious thought..
[14:57] <pitti> (after fiddling with g-s-d for two hours ..)
[14:58] <Laney> :-)
[14:58] <Laney> you can come troll the desktop team meeting in a minute then :P
[14:58] <Laney> well, 30 minutes
[14:59] <seb128> rather yes ;-)
[15:17] <jbicha> seb128: hey what do you think about me uploading gnome-session 3.8 once ical is done? it's been in the desktop ppa for a week
[15:17] <seb128> urg
[15:17] <seb128> jbicha, stop pushing so much crack in the archive ;-)
[15:17] <jbicha> or we could talk about it first :)
[15:18] <seb128> jbicha, sorry I forgot to test it, I will mention it during the meeting and install it now
[15:18] <pitti> are there intrusive changes in -session?
[15:18] <seb128> and test tomorrow
[15:18] <jbicha> there's not much crack left :)
[15:18] <seb128> pitti, some yes
[15:18] <pitti> je peux faire ça aussi, si tu veux
[15:18] <seb128> pitti, ça serait utile, merci
[15:22] <seb128> jbicha, pitti: hum, I don't like that much
[15:22] <seb128> The following NEW packages will be installed:
[15:22] <seb128>   libsystemd-journal0
[15:22] <pitti> oh? not here
[15:22] <pitti> oh, already had it, nevermind
[15:22] <seb128> pitti, you probably had it
[15:22] <pitti> Size: 55804
[15:22] <seb128> do we know how the lib behave if journald is not there?
[15:23] <seb128> will it spawn an extra service?
[15:23] <jbicha> I thought pitti said that library was ok but I think it's fairly simple to patch it out if we definitely don't want it
[15:25] <pitti> it at least survived a reboot, and unity session start
[15:25] <pitti> guest session is broken in lightdm, but that was the case before already
[15:27] <seb128> guest session worked here
[15:27] <seb128> that's all I tried so far, I don't want to restart my user session
[15:27] <pitti> user switching works as well
[15:27] <pitti> _sbin_init.1001.crash
[15:27] <pitti> *cough*
[15:28] <seb128> urg
[15:28] <pitti> must have been on logout, I didn't notice anything wrong, except a small delay
[15:28] <pitti> which reminds me..
[15:29] <seb128> yeah, I keep hitting segfaults on logout, it's annoying since apport blocks the process and logout takes 10 seconds
[15:30] <pitti> FTR, that crash is bug 1190526, already reported by Laney
[15:30] <ubot2> Launchpad bug 1190526 in upstart (Ubuntu) "init crashed with SIGABRT in nih_discard()" [Medium,Confirmed] https://launchpad.net/bugs/1190526
[15:30] <Laney> muhahaha
[15:30] <seb128> ok
[15:30] <seb128> it's meeting time
[15:30] <seb128> qengho, Laney, mlankhorst, tkamppeter, attente, desrt, larsu, Sweetshark: hey
[15:31] <mlankhorst> g'day mate
[15:32] <seb128> let's get started
[15:32] <seb128> qengho, hey
[15:33] <seb128> ok, no qengho
[15:33] <seb128> Laney, hey
[15:33] <Laney> hey
[15:33] <Laney> More work on appearance panel - currently working on a CrossFadeImage comoponent to push to the UI toolkit which it will use. Once this is landed the panel (demoware, with example content) can be merged with system-settings. Turns out the content picker is being worked on by other teams so this, combined with the lack of dconf bindings, means that not much can be done ATM.
[15:33] <Laney> • Upstream patch to EDS to add a desktop file so it appears in UOA.
[15:33] <Laney> • Many FTBFS fixes from the rebuild test. Still lots left!
[15:33] <Laney> • Discuss a bit about language-selector/fontconfig. Gunnar is taking on most of the maintenance here which is great.
[15:33] <Laney> • Rework unity/unity-panel-service's upstart user session jobs to be more logical, and work ;-).
[15:34] <Laney> • Debug empathy failing SSL cert verification which turned out to be missing p11-kit.
[15:34] <Laney> (Discover the nautilus trash crash isn't actually fixed)
[15:34] <Laney> eof
[15:35] <seb128> Laney, thanks
[15:35] <seb128> busy week ;-)
[15:35] <seb128> Laney, merging demoware system settings code is ok, most of it is UI only atm
[15:35] <seb128> but you need to start somewhere
[15:35] <Laney> yeah
[15:35] <seb128> mlankhorst, hey
[15:35] <mlankhorst> porting bcmwl to 3.10, got ack from peterz about the wound/wait kernel locking, going to be upstream soon, fixing nvidia regression with hybrid graphics, final pieces of raring stack landed, fixing up the lts status report scripts, investigating the pieces required to add support for https://www.opengl.org/registry/specs/EXT/glx_swap_control_tear.txt , melting from heat, and forgetting other stuff I've worked on
[15:36] <seb128> mlankhorst, thanks
[15:36] <seb128> tkamppeter, hey
[15:38] <qengho> seb128: I'm here!
[15:38] <seb128> qengho, great, your turn if you are ready then ;-)
[15:38] <qengho> - Was debugging ARM crash, still. Now trying yesterday's release, v28.
[15:38] <qengho> - Amazon extension feedback. Looking for more unpleasant tricks in their code.
[15:38] <qengho> The ARM crash was so ugly, I hope it's gone with this version.
[15:38] <qengho> EOF
[15:39] <seb128> qengho, thanks
[15:39] <qengho> (ARM crash in gdb, fwiw:   http://pastebin.ubuntu.com/5775201/ )
[15:39] <seb128> Sweetshark, since you are back as well, ready?
[15:41] <seb128> not it seems...
[15:41] <seb128> attente, hey
[15:41] <attente> seb128, hi
[15:41] <attente> got IBus working with g-s-d 3.6 and gnome-desktop 3.8
[15:41] <attente> debugged u-g-m autopilot tests
[15:41] <attente> u-g-m icon support
[15:41] <attente> worked a bit on the language and text settings panel ui
[15:41] <attente> eof
[15:42] <seb128> shrug, I really need to test your indicator!
[15:42] <seb128> is it in a working state atm? do you have a ppa with it? (does it require fixes to other sources?=
[15:42] <attente> seb128, it's in a working state, but a few of the packages in the ppa were superceded
[15:43] <attente> i can re-upload them and let you know when they're all updated
[15:43] <seb128> which ones do you need?
[15:43] <seb128> we got the gdk/gtk patches in the distro
[15:43] <seb128> with the new glib in saucy
[15:43] <seb128> what else?
[15:43] <Laney> speaking of menus, they're weird in virt-manager
[15:43] <attente> there's g-c-c, g-s-d, vala, g-o-i
[15:43] <attente> there's ubuntu-themes
[15:43] <Laney> is that ugm related? :-)
[15:43] <attente> virt-manager? hope not :)
[15:44] <seb128> attente, do you need all those for the indicator?
[15:44] <Sweetshark> seb128: back for good
[15:44] <Sweetshark> seb128: shall I shoot my blurb?
[15:44] <seb128> attente, in any case please submit merge request with your changes, even if we don't ack them yet it will help to start reviews, etc
[15:45] <seb128> Sweetshark, one sec, once attente is done
[15:45] <attente> seb128, you can probably get away without vala and g-o-i since those are build-depends
[15:45] <attente> there's also ibus 1.5 in the ppa
[15:45] <Laney> http://people.canonical.com/~laney/weird.png
[15:46] <seb128> ibus , going to be a fun discussion
[15:46] <attente> seb128, it seems to be working just fine on my system, but what issues were you running into?
[15:47] <seb128> attente, I'm not using ibus, so none personally ... but there was quite some pushback from other distros on it because it breaks features out of GNOME
[15:48] <seb128> like "by window layout"
[15:48] <seb128> there was some setting migration issues as well
[15:48] <seb128> but that's not a topic for this meeting, we lack people knowing/using ibus in the team and it's going to be a more than 10min discussion
[15:49] <seb128> attente, thanks
[15:49] <seb128> Sweetshark, you can go
[15:49] <Sweetshark> - build some prerelease of LibreOffice 4.1.0 beta2
[15:49] <Sweetshark> -- massive problems with space on ppa buildds
[15:49] <Sweetshark> -- most arch-indep dependencies (aka java)
[15:49] <Sweetshark> -- builders do not fail, they just hang with no-space-left-on-device (DDOS?!)
[15:49] <Sweetshark> -- got a _very_ beta version in anyway, without java: https://launchpad.net/~libreoffice/+archive/libreoffice-prereleases/+sourcepub/3310247/+listing-archive-extra
[15:49] <Sweetshark> - released LibreOffice 4.0.4~rc2 into ppa
[15:49] <Sweetshark> -- this expected to be 4.0.4 final
[15:49] <Sweetshark> -- we should SRU it after some incubation in the ppa
[15:49] <Sweetshark> - LibreOffice Hackfest Hamburg 2013 was awesome
[15:49] <Sweetshark> -- https://wiki.documentfoundation.org/Hackfest/Hamburg2013
[15:49] <Sweetshark> -- reduced dev build time by ~10% on all platforms with one commit: http://cgit.freedesktop.org/libreoffice/core/commit/?id=66a0713dc9c676182fcd7aa1e21f8dc25c05be5e
[15:49] <Sweetshark> -- essential group photo: https://plus.google.com/101094190333184858950/posts
[15:49] <Sweetshark> -- disabled internal unity stuff on backports, this needs raring or later
[15:49] <Sweetshark> - upcoming plans for next week:
[15:49] <Sweetshark> -- the evil one: on ppa buildds delete all object files in install-common and friends, before actually installing into ./debian to get back some space (evil hack from hell)
[15:49] <Sweetshark> -- get liborcus 0.5.1 into saucy
[15:49] <Sweetshark> EOF
[15:50] <seb128> Sweetshark, thanks, good luck with the hack
[15:50] <seb128> desrt, hey, there (or busy at the hackfest)?
[15:51] <didrocks> RuntimeError: the sip module implements API v10.0 but the PyQt4.QtGui module requires API 9.2, does it ring a bell to anyone?
[15:51] <didrocks> (sorry, meeting)
[15:51] <seb128> no desrt
[15:52] <seb128> larsu, hey
[15:52] <larsu> seb128: sound!
[15:52] <larsu> widgets for ido are finally done (MR today). Took a bit longer than expected because they were very intermingled with dbusmenu code
[15:52] <larsu> did some small fixes on the sound indicator service, most importantly it didn't procide a way to set microphone volume yet. Doing that right now, after that it should be ready for review as well
[15:52] <larsu> started reviewing the other indicators that are landing this week

[15:53] <seb128> yeah for indicators landing!
[15:53] <larsu> we're getting there :)
[15:53] <seb128> larsu, do you know what's the status of gsettings-qml on qt5?
[15:53]  * kenvandine hopes for a positive answer...
[15:53] <seb128> as Laney mentioned, we could sort of use access to gsettings keys for system settings :p
[15:54] <larsu> seb128: oh right - the qt bug that blocked me is fixed and in a ppa
[15:54] <kenvandine> WOOT
[15:54] <larsu> I'll update dconf-qt for qt5 this week
[15:54] <larsu> it's the next thing on my list after getting the sound MRs out
[15:55] <seb128> great
[15:55] <seb128> larsu, thanks
[15:55] <seb128> my turn
[15:55] <Laney> sweet
[15:56] <seb128> - lot of system settings hacking, got the about panel UI mostly done and following the design
[15:56] <seb128> - some bug fixing there and there
[15:56] <seb128> - looked at some of the ftbfses from doko's rebuild
[15:56] <seb128> - some desktop updates
[15:56] <seb128> but it was mostly system settings this week
[15:57] <seb128> starting look at doing "backend work", but yeah, no easy access to gsettings values or dbus methods from qml sucks

[15:57] <seb128> I'm going to try to have a look at nautilus 3.8 for next week (and indicator-keyboard)
[15:58] <seb128> ok, 3 minutes before didrocks' takes the channel
[15:58] <seb128> comments/question/...?
[15:59] <seb128> larsu, I guess you know what's the status on gmenumodel based indicators ... is that going to start landing soon? is unity7 compatible with those?
[15:59] <seb128> (sort of overlapping topic so I'm asking there)
[15:59] <seb128> larsu, we could also use those backend and qmenumodel for system settings... ;-)
[15:59] <larsu> seb128: yes, after dconf
[16:00] <larsu> seb128: I have a branch almost ready
[16:00] <larsu> just some minor things and cleanup, and a review
[16:00] <seb128> we need to clone larsu :p
[16:00] <larsu> seb128: https://code.launchpad.net/~larsu/qmenumodel/add-unitymenumodel
[16:00] <larsu> haha
[16:01] <didrocks> cyphermox: kenvandine: sil2100: robru: hey, meeting time!
[16:01] <didrocks> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=0
[16:01] <didrocks> how are you guys?
[16:01] <seb128> larsu, thanks
[16:01] <kenvandine> yo
[16:01] <seb128> didrocks, enjoy ;-)
[16:01] <didrocks> thanks seb128 :)
[16:01] <sil2100> Hello!
[16:03] <didrocks> I'll take silence from robru and cyphermox as a yes :)
[16:03] <kenvandine> hehe
[16:03] <cyphermox> yeah
[16:03]  * kenvandine was doing well until trying to build signon-ui for powerpc :/
[16:03] <didrocks> ok, let's make a quick round up!
[16:04] <didrocks> Finding the root cause of the Unity autopilot problems, with the DBus hang-ups: not a priority for now, but mhr3 is looking at it
[16:04]  * sil2100 pokes robotfuel 
[16:04] <sil2100> uuuh, robotfuel sorry
[16:04]  * sil2100 pokes robru 
[16:04] <didrocks> WebCred: Fix autopilot tests keyring issue. kenvandine, I think you are working on getting the stack on shapes first?
[16:05] <kenvandine> the autopilot was blocked on me getting otto, is that ready for me to use?
[16:05] <kenvandine> that and i've been working on other things :)
[16:05] <kenvandine> didrocks, can you get me some simple docs on setting up otto?
[16:05] <didrocks> kenvandine: should be, but not docs, as no time yet :p
[16:05] <sil2100> Yay for otto \o/
[16:06] <didrocks> kenvandine: let's see a little bit later, I don't think it's a priority for now, right?
[16:06] <kenvandine> my top priority right now is getting signon-ui for powerpc
[16:06] <kenvandine> so we can get it out of -proposed
[16:06] <didrocks> yeah, good luck! ;)
[16:06] <didrocks> seems fun :p
[16:06] <kenvandine> not really :)
[16:06]  * didrocks hands off his card of powerpc lover to kenvandine
[16:06] <kenvandine> and lots of settings work coming in
[16:07] <kenvandine> i did successfully add a facebook account on the nexus 4 with system-settings :)
[16:07] <didrocks> sweet :)
[16:07] <didrocks> ok, next topic: raring SRU
[16:08] <didrocks> I think sil2100 won that one from Mirv :)
[16:08] <sil2100> Yes! Changelogs fixed, merges for adding bug numbers are done
[16:08] <didrocks> I did some changes to the daily release so that we can use another ppa for staging SRUs
[16:08] <didrocks> and not having launchpad removed
[16:08] <didrocks> sil2100: ok, so all should be good tomorrow?
[16:08] <sil2100> Awesome
[16:08] <didrocks> so that we can publish to this staging ppa and ask the sync to UNAPPROVED?
[16:08] <sil2100> didrocks: yes, I'll just double-check the bugs if they're SRU-compatible
[16:09] <didrocks> sil2100: thanks! so this one should be fixed by tomorrow :)
[16:09] <didrocks> next one
[16:09] <didrocks> daily release of libpam-freerdp
[16:09] <didrocks> this is for a ken :p
[16:10] <didrocks> kenvandine: ^
[16:10] <kenvandine> yeah... still on my list
[16:11] <didrocks> ok
[16:11] <didrocks> then, there was a new component list
[16:11] <didrocks> I think this is all excellently handled, right sil2100 ?
[16:12] <sil2100> Yes, well, not excellently, but we managed ;p
[16:12] <didrocks> ahah
[16:12] <sil2100> So all the listed components are NEWed now
[16:12] <didrocks> \o/
[16:12]  * didrocks looks at https://launchpad.net/ubuntu/saucy/+queue
[16:12] <didrocks> nothing from us, few!
[16:13] <didrocks> nice work!
[16:13] <didrocks> ok, the 2 next are for cyphermox
[16:13] <didrocks> first one is the indicators-client to readd
[16:13] <cyphermox> aye.
[16:13] <cyphermox> indicators-client readd in in progress
[16:13] <didrocks> as we discussed, we'll do that just after indicators finally publishes :)
[16:13] <cyphermox> yup
[16:13] <didrocks> thanks cyphermox! do we have integration tests?
[16:13] <cyphermox> we do, there's a chewie_client autopilot suite of tests
[16:14]  * didrocks removes the line "/me looks at tedg with brown eyes"
[16:14] <didrocks> \o/
[16:14] <didrocks> so we are going to enable those as well?
[16:14] <cyphermox> it's in the merge proposal
[16:15] <didrocks> sweet
[16:15] <didrocks> sil2100: do you mind approving + deploying it once you published the indicator stack?
[16:17] <didrocks> cyphermox: meanwhile: "Fix indicator-network and re-enable it for the indicator stack tests", any news?
[16:17] <sil2100> cyphermox: where's the merge proposal for that?
[16:17] <cyphermox> didrocks: I re-asked ted this morning, it's depending on some libindicator changes, but will get done soon. for now we can just leave it out
[16:17] <sil2100> cyphermox: I'll bookmark it
[16:18] <didrocks> cyphermox: let's wait for ted then, thanks! mind updating the spreadsheet with this info? :)
[16:18] <cyphermox> yup
[16:18] <didrocks> ok, then, for the next one, we need robru
[16:18] <didrocks> we saw some progress AFAIK on the daily_release: False package
[16:19] <didrocks> but it's still in progress
[16:19] <didrocks> next one is for me, cleaning all packages, same progress, but need some double checking
[16:19] <didrocks> cyphermox: kenvandine: sil2100: any issues on  your package list from that list? http://paste.ubuntu.com/5741741/
[16:19] <sil2100> didrocks: re-checking
[16:22] <sil2100> didrocks: do you have anything particular in mind?
[16:22] <didrocks> sil2100: not that I know, I'm not sure if there were blockers for anyone on the list
[16:23] <kenvandine> i think i proposed branches for all the packages in my stacks
[16:23] <didrocks> but I'll check individually I guess :)
[16:23] <didrocks> kenvandine: needing reviews?
[16:23] <didrocks> kenvandine: or let upstream doing them?
[16:23] <didrocks> (I'm fine with both)
[16:24] <kenvandine> upstream
[16:25] <didrocks> good :)
[16:25] <kenvandine> i think they might have all been reviewed
[16:25] <didrocks> (less work \o/)
[16:25] <kenvandine> i'll double check
[16:25] <didrocks> thanks :)
[16:25] <didrocks> ok, then we listed some daily release enhancements + tracking the unity upstart revert which is now fixed thanks to Laney's help!
[16:25] <didrocks> last item
[16:25] <didrocks> I think mlankhorst is really eager to migrate to the new Xorg
[16:25] <didrocks> (1.14?)
[16:25] <mlankhorst> yes
[16:25] <didrocks> it needs an unity patch, mlankhorst who worked on this unity side already?
[16:25] <didrocks> was it Trevinho?
[16:26] <mlankhorst> the patch is in the x-staging ppa, Sarvatt might know
[16:26] <sil2100> We'll release the old unity soon I guess, indicators I'd like to unblock before that, so we're waiting on the python-qt patch
[16:26] <didrocks> ok, sil2100, once this one is done, do you want to take that transition in charge? ^
[16:27] <didrocks> coordinate with mlankhorst and Sarvatt on it
[16:27] <sil2100> ACK! Hope I won't screw up ;)
[16:27] <didrocks> (we'll probably use -proposed as for libical)
[16:27] <didrocks> sil2100: ask if anything
[16:27] <sil2100> You can assign that to me
[16:27] <didrocks> sil2100: thanks man! :)
[16:27] <didrocks> I think xorg should breaks: current_unity
[16:27] <Trevinho> didrocks: no bschaefer did that
[16:27] <didrocks> then, we try to release unity with the new patch using proposed
[16:27] <didrocks> Trevinho: thanks for the pointer :)
[16:27]  * didrocks marks the names in the spreadsheet
[16:27] <didrocks> any questions meanwhile?
[16:27]  * bschaefer wonders what i've done
[16:28] <bschaefer> Trevinho, what did I do?
[16:28] <didrocks> bschaefer: bad things! like an unity patch for new xorg :p
[16:28] <mlankhorst> didrocks: it's not as much that it breaks Xorg, it's the depends on libxi/xfixes
[16:28] <bschaefer> didrocks, well...yeah :) that should be a good thing!
[16:28] <didrocks> mlankhorst: ok, you will deal the xorg side so that it can be transitionned without the new unity?
[16:28] <didrocks> bschaefer: do you have a branch to point us at?
[16:28] <bschaefer> didrocks, yes, let me get a link
[16:29] <mlankhorst> will it be for today? it's EOD for me and I'm leaving shortly
[16:29] <bschaefer> didrocks, https://code.launchpad.net/~brandontschaefer/unity/move-pointer-barrier-to-xi-1.6.99.1
[16:29] <didrocks> mlankhorst: ah no, it's for this week :)
[16:29] <mlankhorst> ah good
[16:29] <mlankhorst> bbl!
[16:29] <didrocks> mlankhorst: we hope to be able to release unity+indicators this week
[16:29] <didrocks> mlankhorst: let's do that as the next step :)
[16:29] <didrocks> (this week/today)
[16:29] <didrocks> mlankhorst: enjoy!
[16:29] <didrocks> thanks bschaefer
[16:30] <bschaefer> didrocks, np! have fun getting that all set up :)
[16:30] <sil2100> didrocks: btw. you think I could run the unity tests with "whole PPA" to force it to use the new hud, bamf and indicators ;)?
[16:30] <didrocks> sil2100: I'm adding myself as a backup :)
[16:30] <didrocks> sil2100: let's discuss that now if the meeting is over for the others?
[16:30] <didrocks> thanks eveyrone
[16:30] <sil2100> didrocks: since I guess many failures might be fixed by those
[16:30] <sil2100> Ok
[16:30] <didrocks> everyone*
[16:31] <didrocks> sil2100: so, let's try to unblock indicators for now
[16:31] <didrocks> sil2100: I think we can workaround the problem
[16:32] <Laney> btw I checked on libical and it seems to me that indicator-datetime is the only thing left holding that transition
[16:32] <didrocks> Laney: yeah, but sip has a broken transition and that's breaking all the tests running
[16:32] <sil2100> Laney: ok, thanks, we enabled -proposed and rebuilt it, but have some problems related to some things happening in -proposed
[16:32] <didrocks> sil2100: it's worse, it's in the release pocket as well
[16:33] <didrocks> (the sip issue)
[16:33] <Laney> the tests for datetime itself or something else?
[16:33] <didrocks> Laney: all the autopilot tests
[16:33] <didrocks> pyqt4 is bailing out
[16:33] <sil2100> uuu
[16:33] <Laney> I'm secretly suggesting that you (or I) can upload just datetime and it will make that transition finish
[16:34] <Laney> it's only the build fix since distro
[16:35] <seb128> Laney, I tried suggested that this morning as well :p
[16:35] <didrocks> Laney: seb128: we have quite some changes in the indicator stacks
[16:35] <didrocks> we could force a publication as well
[16:35] <didrocks> workarounding and not testing with new libical doesn't sound good to me :)
[16:36] <didrocks> I have a solution, let us try
[16:36] <seb128> k
[16:36] <didrocks> it's juts a pity that some stack can be broken for days and that sip was uploaded breaking even more…
[16:36] <didrocks> (it's this kind of direct uploads which is the cause of the pain :p)
[16:40] <sil2100> didrocks: how do you want to workaround this?
[16:40] <didrocks> sil2100: see my pings :)
[16:41] <didrocks> no need to fill the channel with uninteresting details…
[16:47] <rickspencer3> seb128, my new computer ... Wireless works fine here, but refuses go connect with a certain WEP access point
[16:47] <rickspencer3> seb128, do you think this is a driver issue? if so, is there still Jockey built in to help me out with this?
[16:48] <seb128> cyphermox, ^ help ;-)
[16:50] <cyphermox> rickspencer3: yes, likely a driver issue
[16:50] <czajkowski> cyphermox: ping, am having a lot of connection issues today on raring, never had them before, others in the office are fine. wondering was there any udpates done today?
[16:50] <cyphermox> what driver is this?
[16:50] <cyphermox> czajkowski: no
[16:50] <cyphermox> czajkowski: kernel update perhaps?
[16:53] <cyphermox> rickspencer3: can you tell me what "grep wlan.*driver /var/log/syslog" reports?
[16:53]  * kenvandine stabs ppc, but it lives on!
[16:53] <rickspencer3> cyphermox,
[16:53] <rickspencer3> Jun 18 09:41:29 rick-Lenovo-IdeaPad-U310-Touch NetworkManager[908]: <info> (wlan0): driver supports Access Point (AP) mode
[16:53] <rickspencer3> Jun 18 09:41:29 rick-Lenovo-IdeaPad-U310-Touch NetworkManager[908]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
[16:54] <cyphermox> huh, that one should work great for WEP too
[16:54] <rickspencer3> cyphermox, well, I'm on WEP here
[16:54] <cyphermox> does the AP have special caracters in the name?
[16:54] <rickspencer3> it was just one certain access point
[16:54] <rickspencer3> cyphermox, yes, there is an apostrophe
[16:54] <rickspencer3> NM works
[16:55] <rickspencer3> it asks me for the password
[16:55] <rickspencer3> but then it fails to connect
[16:55] <cyphermox> I don't think an apostrophe would block connecting to WEP though
[16:55] <cyphermox> ok
[16:55] <cyphermox> rickspencer3: could you send me a copy of syslog? I'll take a look at all the errors NM throws, if any
[16:55] <rickspencer3> cyphermox, sure
[16:56] <cyphermox> rickspencer3: btw, for battery use, I was able to reproduce it here on saucy
[16:56] <rickspencer3> cyphermox, you mean on the phone?
[16:56] <rickspencer3> that's great news!
[16:57] <cyphermox> yeah, so it's a first step to actually fixing the issue
[16:57] <czajkowski> cyphermox: sent to pm
[16:57] <cyphermox> czajkowski: ack
[17:04] <cyphermox> I'm going to go grab some food; I'm starving
[17:06] <rickspencer3> cyphermox, I send the syslog to your email
[17:06] <cyphermox> rickspencer3: ok, I'll have another thing for you to check
[17:06] <rickspencer3> cyphermox, ok
[17:06] <cyphermox> or actually, I'll just look in syslog
[17:07] <cyphermox> rickspencer3: saucy or raring?
[17:07] <rickspencer3> it's annoying that I won't be back at that access point until tonight :/
[17:07] <rickspencer3> cyphermox, saucy
[17:07] <rickspencer3> fresh install
[17:07] <cyphermox> doh
[17:07] <rickspencer3> d'oh ?
[17:07] <rickspencer3> saucy ftw
[17:12] <cyphermox> rickspencer3: I was kind of hoping it was an issue like czajkowski ;)
[17:12] <cyphermox> which seems to be a kernel regression, tbh
[17:12] <rickspencer3> oh well
[17:12] <cyphermox> rickspencer3: Jun 18 08:29:40 rick-Lenovo-IdeaPad-U310-Touch kernel: [ 6598.038710] wlan0: AP 00:24:b2:db:d7:30 changed bandwidth in a way we can't support - disconnect
[17:12] <cyphermox> ^ this is my guess at the problem
[17:12] <cyphermox> it's the first time I see this
[17:13] <cyphermox> I'll need to look it up to see what triggers it
[17:13] <rickspencer3> cyphermox, well, there was one access point that I could connect to, but it would disconnect occasionally
[17:13] <rickspencer3> that message could be from that access point
[17:13] <cyphermox> rickspencer3: it's from the AP that has an apostrophe
[17:13] <rickspencer3> cyphermox, ok, that's the busted one :/
[17:13] <rickspencer3> cyphermox, here's the thing ...
[17:14] <rickspencer3> my phone works fine with that access point
[17:14] <cyphermox> yeah
[17:14] <cyphermox> I'm not surprised
[17:14] <cyphermox> it seems like you're getting inconsistent informations from the AP about the frequency to use
[17:14] <cyphermox> well, the bandwidth to be precise
[17:15] <cyphermox> but it's likely the kernel not understanding it
[17:15] <cyphermox> rickspencer3: could you file a bug against 'linux' for that?
[17:15] <rickspencer3> cyphermox, sure
[17:16] <cyphermox> rickspencer3: you should add the make and model of the router maybe too, if it's available
[17:16] <rickspencer3> cyphermox, it's not available to me
[17:16] <cyphermox> just in case it's broken router firmware, that the phone is able to workaround
[17:16] <cyphermox> oh
[17:16] <cyphermox> when you said phone, you obviously meant touch, right?
[17:16] <rickspencer3> cyphermox, why would the phone work around it and not my laptop?
[17:16] <rickspencer3> cyphermox, yes
[17:17] <rickspencer3> I meant yesterday's Nexus 4 image
[17:17] <cyphermox> so it would be a new kernel thing in saucy probably
[17:18] <rickspencer3> hmmm
[17:18] <rickspencer3> cyphermox, can you put what you know in bug #1192259 ?
[17:18] <ubot2> Launchpad bug 1192259 in linux (Ubuntu) "wireless access point won't connect- changed bandwidth in a way we can't support - disconnect" [Undecided,New] https://launchpad.net/bugs/1192259
[17:19] <cyphermox> yup
[17:21] <cyphermox> now I'm really going to go get food before it's too late
[17:21] <cyphermox> brb
[17:30] <Sweetshark> ahhh, great. I just realized that libreoffice 4.0.2 fails to rebuild on armhf ...
[17:30] <robru> cyphermox, kenvandine sil2100 : sorrry! forgot about the meeting :-(
[17:30] <attente> seb128, i'm not able to MP on lp:ubuntu/vala-0.20. the only way i can push the branch is if i target vala, but if it targets vala, it says it's unmergeable :(
[17:31] <Sweetshark> ... to make it more fun its actually gcc-4.8 being either too stupid or too clever for itself, as that are both of the way it can end in an 'internal error'
[17:31] <Sweetshark> ... well, there is a third possibility: hardware fluke or cosmic rays ...
[17:32] <seb128> attente, oh, just open a bug with the patch then
[17:35] <sil2100> robru: ah HA!
[17:35]  * sil2100 slaps robru around a bit with a large trout
[17:35] <sil2100> UNFORGIVABUBURU
[17:35] <robru> sil2100, eww, slimy
[17:36]  * sil2100 is a bit too tired so he's spouting nonsense
[17:51] <rickspencer3> til that you can DOUBLE click on an app in the dash to just launch it
[17:51] <rickspencer3> I assumed it was a bug that it kept going to the preview
[17:55] <robru> rickspencer3, same here. I think it's dumb though... single click should launch, right click should open more info. that would be consistent with every other UI ever
[17:56] <rickspencer3> robru, tbh, I think it's fine
[17:56] <jbicha> rickspencer3: it is a bug though ;) bug 1189088
[17:56] <ubot2> Launchpad bug 1189088 in Ubuntu Manual Tests "Unity Dash, left mouse button starts preview instead of directly the application" [High,Confirmed] https://launchpad.net/bugs/1189088
[17:56] <rickspencer3> robru, well, phones and tablets don't have right click
[17:56] <rickspencer3> I think making it work the same across my devices is sweet
[17:56] <jbicha> newer GNOME stuff uses long click (or right-click) to pull up additional options, I'm expecting that Nautilus will do that eventually
[17:56] <rickspencer3> not to get dragged into a design flamewar ;)
[17:57] <robru> jbicha, I agree actually, long click / right click for more options/context, single click to just launch.
[17:58] <jbicha> hmm, maybe it's not long-click yet; there's a dedicated ✓ button though
[19:16] <robru> sil2100, still around?
[19:42] <desrt> oh no.  i missed the meeting :(
[19:45] <kenvandine> desrt, you missed it hours ago :)
[19:46] <sil2100> robru: yes, now I am
[19:47] <robru> sil2100, oh hey, I'm just stepping out for lunch. was wondering if you could redeploy cu2d-config for me. I landed all those changes for daily releasing webapps
[19:49] <sil2100> robru: ok, redeployment of webapps stack, yes?
[19:49] <sil2100> robru: did you add any new packages?
[19:49] <robru> sil2100, well, no hurry, you can wait for jenkins to do the release. I just want you to copy the -config branch to the jenkins server
[19:49] <robru> sil2100, yeah, there's a bunch of new ones
[19:50] <robru> sil2100, https://code.launchpad.net/~robru/cupstream2distro-config/enable-many-webapps/+merge/169570 here is the list of apps that have been enabled for daily_release
[19:50] <sil2100> robru: ok, so tomorrow we'll have to poke didier regarding the new ones, I'll note that down for the morning
[19:50] <robru> sil2100, yeah, didier said he'd handle it
[19:50] <sil2100> robru: since he needs to modify the filtering :)
[19:51] <robru> sil2100, alright, thanks!
[19:51]  * robru heads for lunch
[19:52] <sil2100> robru: thanks for handling that!
[21:02] <sil2100> robru: redeployed if anything!
[21:03] <robru> sil2100, great, thanks a bunch. we'll leave the rest for didrocks tomorrow ;-)
[22:32] <TheMuso> grrr I am getting regular compiz crashes  here...