[02:15] <jbicha> pitti: I think bug 1202054 is invalid but do you want to handle it?
[02:15] <ubot2`> Launchpad bug 1202054 in accountsservice (Ubuntu) "PostgreSQL Being Listed on Login Screen" [Undecided,New] https://launchpad.net/bugs/1202054
[03:30] <pitti> Good morning
[03:30] <pitti> jbicha: looking
[03:32] <pitti> jbicha: indeed, closed with a comment
[06:58] <didrocks> salut jibel!
[06:59] <jibel> Salut didrocks
[07:32] <seb128> good morning desktopers!
[07:35] <didrocks> hey seb128!
[07:35] <seb128> didrocks, hey ;-)
[07:35] <didrocks> seb128: I guess we have good reasons to not have gnome-terminal 3.8? :)
[07:36] <seb128> didrocks, try asking Laney or jbicha, the new version migrates to gsettings and had some issues IIRC but I didn't look at it, they did
[07:36] <didrocks> seb128: mind if I backport the fix for https://bugzilla.gnome.org/show_bug.cgi?id=685507?
[07:36] <ubot2`> Gnome bug 685507 in general "Tabbed windows resize themselves when unfocused" [Normal,Resolved: fixed]
[07:36] <didrocks> seb128: this is really getting on my nerves everyday :p
[07:37] <seb128> didrocks, you are welcome to fix desktop bugs ;-)
[07:37] <didrocks> \o/
[07:37] <didrocks> seb128: you never use tabs in gnome-terminal, I assume?
[07:38] <seb128> I do, but I use the default geometry (if that makes a difference)
[07:38] <didrocks> hum, vcs is at 3.8.4 :/
[07:38] <didrocks> ah, you don't resize it
[07:38] <seb128> somebody started the update but probably didn't end uploading for a reason
[07:38] <seb128> no I don't
[07:38] <seb128> the default size is good enough for
[07:38] <didrocks> ok, that's why you don't see that :p
[07:39] <seb128> what I'm doing
[07:39] <seb128> ;-)
[07:39] <didrocks> I think I'll just apt-get source && upload
[07:39] <seb128> that's the way to go when the vcs has ongoing work
[07:39] <seb128> we should stage those in a update vcs rather than in trunk
[07:40] <seb128> but most of the time when we start an update we just do it so we got used to abuse trunk...
[07:40] <didrocks> right, and only merge once ready to be uploaded
[08:03] <Laney> hey
[08:03] <seb128> Laney, good morning!
[08:03] <Laney> how are we all?
[08:03] <seb128> quite good! you?
[08:03] <Laney> gnome-terminal was just waiting for a resolution on the vte.sh issue from my side
[08:03] <Laney> yeah, good!
[08:05] <Laney> ooh, something weird is happening on my desktop
[08:05] <seb128> weird like?
[08:05] <Laney> I have the default background at the unity greeter
[08:06] <Laney> then log in, corruption under the launcher when it hides
[08:06] <Laney> then the session crashes and I get kicked back to lightdm
[08:06] <seb128> urg
[08:06] <seb128> we didn't changed a lot recently on the desktop that I can remember
[08:07] <Laney> I could have broken stuff when I was playing with gnome-session yesterday for that bug
[08:07] <seb128> yea, that would make sense
[08:07] <seb128> don't blame the archive when you can blame the user ;-)
[08:07]  * Laney tinkers
[08:10] <Laney> had a load of unconfigured packages
[08:11] <seb128> that's usually not a good thing as well
[08:12] <Laney> wee, much better
[08:12] <seb128> what is the inconsistent state of the packaging system then?
[08:12] <Laney> systemd wasn't configured
[08:12] <seb128> what happened to your update?
[08:13] <Laney> not sure
[08:13] <sil2100> didrocks: I'm slowly unblocking stacks, but this will take a while since I need to get some branches landed ;)
[08:13] <Laney> oh, wait, I remember
[08:13] <Laney> yesterday hud-tools and something else had a file conflict
[08:13] <Laney> I bet that broke it
[08:13] <sil2100> Laney: yes, hud-tools and phablet-tools
[08:13] <Laney> sil2100: did it get fixed?
[08:13] <sil2100> I remember Trevinho poking around for that, not sure if in the end he resolved that conflict ;/
[08:14] <Laney> I pinged sergiusns (however do you spell that?) but he didn't say anything in response
[08:14] <sil2100> Trevinho: would know more
[08:14] <sil2100> Although not sure why he was the one working on that :D
[08:15] <didrocks> sil2100: no worry
[08:15] <didrocks> sil2100: don't touch the platform stack
[08:16] <didrocks> sil2100: it's a bug in dailies to list powerpc, I've just reproduce it locally
[08:16] <didrocks> need to understand and fix that
[08:16] <didrocks> sil2100: please do sdk and media stack in priority
[08:16] <didrocks> to get this fix landed
[08:17] <sil2100> Aye
[08:17] <Laney> sil2100: looks like it was indeed fixed https://code.launchpad.net/~mathieu-tl/phablet-tools/exclude-tests/+merge/175328
[08:17] <Laney> cyphermox_: YOU HERO
[08:18] <sil2100> didrocks: btw. indicator stack has a failure treshold of 1? Or not?
[08:18] <Laney> also if you want to fix the same thing in hud tools? :-)
[08:18] <sil2100> Laney: yay \o/
[08:19] <didrocks> sil2100: I think it's 2, with 1 regression, you don't remember where to look at?
[08:19] <sil2100> Laney: those tests that are installed... those are unit tests, right?
[08:19] <sil2100> didrocks: don't remember... since 2 test failures caused it to fail, but I have been wondering if 1 failure is ok
[08:19] <didrocks> sil2100: oh, the treshold is 4 with 2% of regressions
[08:20] <didrocks> sil2100: /var/lib/jenkins/cu2d/history/head/indicators.autopilotrc
[08:20] <didrocks> on mangers
[08:20] <didrocks> magners*
[08:20] <Laney> sil2100: yeah, think so
[08:20] <didrocks> sil2100: see ratio | ptotal: +0.000 | pskip: +0.000 | pfailures: +0.048 | regressions: +0.048
[08:21] <Laney> I think it was just an accident to have them installed
[08:21] <didrocks> I know jibel is cryptic sometimes :p
[08:21] <didrocks> sil2100: 4.8% of regressions
[08:24] <sil2100> ;)
[08:24] <sil2100> didrocks: thanks for reminding!
[08:26] <sil2100> Laney: I'll try fixing that for hud-tools in a moment
[08:27] <Laney> cool beans
[08:28] <Laney> mlankhorst: http://www.guardian.co.uk/environment/bike-blog/video/2013/jul/17/man-v-bike-video
[08:29] <Laney> (no, no image build failures today :P)
[08:31] <tvoss_> pitti, ping
[08:32] <pitti> tvoss_: hello
[08:33] <didrocks> sil2100: ok, it was again a .copy() missing, pushing the fix and relaunching platform stack :)
[08:33] <sil2100> \o/ :)
[08:35] <didrocks> sil2100: it seems that sdk stack failed
[08:35] <sil2100> didrocks: yes, because of the gallery-app problem
[08:35] <sil2100> didrocks: wait for the fix to land
[08:35] <didrocks> sil2100: ah, the fix is in gallery-app as well?
[08:35] <sil2100> didrocks: I have it under control ;)
[08:36] <didrocks> ok, I'll let you then :p
[08:36] <sil2100> didrocks: it's only in gallery-app, siiiince - it's not a BUG, it's a change in the toolkit ;p
[08:36] <didrocks> hum, ok… ;-)
[08:36] <didrocks> sil2100: I'm leaving you all the stacks now, just ping me if you need me
[08:42] <sil2100> didrocks: are we still having so few powerpc builders ;/ ?
[08:43] <didrocks> sil2100: yeah, apparently the 3rd one will be racked today in London
[08:43] <didrocks> but yeah, this is delaying to get the fix into distro
[08:43] <didrocks> sil2100: if it's only blocking us, feel free to skip them
[08:43] <didrocks> sil2100: then, for proposed -> released, we can ask cjwatson to free the constraint
[08:46] <Laney> bah
[08:47] <Laney> I wonder if indicator-datetime could set XDG_CURRENT_DESKTOP=Unity itself for launching the g-c-c panel
[08:47] <Laney> since that has OnlyShowIn=Unity that kind of makes sense
[08:47] <Laney> larsu: ^?
[08:48] <seb128> Laney, what about fixing that race instead?
[08:48] <Laney> it's not just about the race
[08:48] <Laney> although it would stop that being a problem too
[08:48] <seb128> we are going to have the same issue with other indicators
[08:49] <seb128> I had a gnome-shell locking gnome-screensaver lock screen this week
[08:49] <Laney> you also get this if you use -applet for example
[08:49] <seb128> I guess that's because indicator-session spawned it with the wrong env
[08:49] <larsu> Laney: that sounds ... ugly
[08:50] <larsu> what's the race?
[08:50] <Laney> upstart user sessions starting u-p-s too early
[08:50] <larsu> too early for what?
[08:50] <Laney> for the env var to be set
[08:50] <Laney> but anyway, fixing that would still leave it borked in non-unity sessions
[08:51] <larsu> wait, shouldn't upstart set the right environment when spawning stuff?
[08:53] <Laney> gnome-session sets it iirc
[08:54] <larsu> right, I thought upstart user session was supposed to replace large parts of gnome-session (but then I haven't really looked into this whole püroblem much)
[08:55] <Laney> Hmm, don't know how much of it people want to replace
[08:57] <Laney> I suppose it'd be better to launch the upstream datetime panel in non-unity situations wouldn't it?
[08:57] <Laney> (woo, my fan just got delivered)
[08:59] <larsu> yeah, and I think that's what we already do
[09:00] <Laney> not quite
[09:01] <Laney> it's protected by #ifdef HAVE_CCPANEL
[09:01] <Laney> otherwise unconditional
[09:27] <Laney> larsu: Also, relatedly - https://wiki.ubuntu.com/TimeAndDate#Phone - we were wondering if that reuses the menumodel from the indicator?
[09:28] <larsu> Laney: it doesn't right now, but it could if that makes things easier
[09:28] <larsu> not sure what charles' plan is there
[09:28] <Laney> larsu: No, not really - I was just going to look at implementing that one
[09:29] <Laney> the spreadsheet says timedated for that information - is that true?
[09:30] <larsu> Laney: yes. But please talk to charles before starting on it
[09:30] <Laney> sure
[09:31] <czajkowski> random question I know, but does anyone use dropbox and running saucy ?  I do use U1 before people ask but work need dropbox account. however under saucy every time you click the folder dropbox to open it crashes and closes.
[09:33] <czajkowski> hmm in order for apport to send it I need to upgrade
[09:33] <czajkowski> gir1.2-glib-2.0, libgirepository-1.0-1
[09:38] <sil2100> Laney: maybe you have a moment for https://code.launchpad.net/~sil2100/hud/hud-tools_fix_tests/+merge/175475 ? ;)
[09:39] <seb128> czajkowski, I saw a launchpad bug which seems like a nautilus/dropbox segfault yes
[09:39] <seb128> czajkowski, not sure we can debug it though, dropbox is closed source
[09:40] <czajkowski> feck :/
[09:40] <czajkowski> queue more whinging about me not using a mac on my tea
[09:40] <czajkowski> *team
[09:40] <czajkowski> shall just use the web
[09:40] <czajkowski> thanks seb128
[09:41] <seb128> czajkowski, it's rather you not using u1 :p
[09:41] <czajkowski> no I do use U1, but all the team shares stuff via dropbox :( I've already sent them invites to U1 :)
[09:42] <czajkowski> web works :)
[09:43] <seb128> ;-)
[09:43] <seb128> ideally we would fix that dropbox/nautilus bug
[09:43] <seb128> not sure if that's the new glib it doesn't like
[09:43] <seb128> or if that's a bug in dropbox
[09:45] <seb128> the bug is https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1193522
[09:45] <ubot2`> Ubuntu bug 1193522 in nautilus (Ubuntu) "nautilus crashed with SIGSEGV in gtk_action_get_name()" [Medium,Confirmed]
[09:45] <Laney> sil2100: yep, looks good but I can't approve such things
[09:46] <seb128> ok, need to run for a bit
[09:46] <seb128> bbl
[09:47] <darkxst> seb128, czajkowski, dropbox plugin needs to be rebuilt against new gtk to fix that crash
[09:47] <Laney> ?!
[09:52] <czajkowski> Laney: you ok?
[10:02] <darkxst> In some ways it would be nice to have the dropbox plugins in the archives, similar issues seem to happen every time gtk is updated!
[10:03] <sil2100> Nooo, LP is dooown
[10:03] <sil2100> Oh, ok, up
[10:07] <sil2100> didrocks: since you enabled unity-action-api for daily-release, do you know what's the status with unity-action-api-nohud? Is it supposed to be daily-released?
[10:07] <didrocks> sil2100: I think it's just a different branch, maybe just check with wellark?
[10:08] <sil2100> Will do, so I'll leave it as it is for now
[10:08] <sil2100> larsu: hi! Maybe you have a moment to review and approve a hud-related merge? https://code.launchpad.net/~sil2100/hud/hud-tools_fix_tests/+merge/175475
[10:13] <tkamppeter> mlankhorst, hi
[10:23] <Laney> ctrl r -> power completed to "sudo poweroff" instead of "system-settings power"
[10:23] <Laney> DOH
[10:26] <sil2100> didrocks: I have been also thinking about daily-releasing webaccounts-browser-extension - it's lacking any integration tests right now, but there are unit tests
[10:26] <sil2100> didrocks: it's already in distro, and I don't know if there are any plans for integration testing
[10:26] <didrocks> sil2100: maybe check with ken about that one?
[10:26] <sil2100> didrocks: should I wait for upstream ?
[10:26] <didrocks> he should know more :)
[10:38] <didrocks> sil2100: for dailies, everything's under control? the media fix is released?
[10:40] <didrocks> sil2100: not with us? it seems the media stack is ready for 1h+ and it's our first priority so that they can respin the iso :/
[10:40] <didrocks> sil2100: it's in manual publishing because of sdk in particular
[10:41] <larsu> sil2100: approved :)
[10:42]  * didrocks reruns sdk stack with latest gallery_app
[10:48] <sil2100> didrocks: huuush!
[10:48] <sil2100> didrocks: we've been blocked by check jobs ;/
[10:48] <sil2100> didrocks: since unity was hogging autopilot
[10:48] <sil2100> But now it got unblocked
[10:49] <didrocks> sil2100: did that block platform and media publishing?
[10:49] <didrocks> (they finished 2h and 6h30 ago)
[10:49] <sil2100> didrocks: yes, since media check job was waiting for a run ;/
[10:49] <sil2100> didrocks: I couldn't publish without AP results, right?
[10:49] <didrocks> hum, jenkins is showing wrong dates then?
[10:50] <didrocks> 6 h 48 mn last success
[10:50] <didrocks> maybe it's showing "starting date"
[10:50]  * didrocks looks at the publish job
[10:50] <sil2100> hm
[10:50] <didrocks> ok, finished 40 minutes ago
[10:50] <sil2100> Anyway, I do all the stacks now that it's all moving
[10:51] <didrocks> sil2100: great! keep me posted
[10:51] <didrocks> sil2100: well, apart from mir*, as you can see, I'm still testing…
[10:52] <sil2100> didrocks: you re-ran SDK with check-whole-ppa? Did you make sure that the new gallery-app was built already? :)
[10:53] <didrocks> sil2100: just a little bit too early, it seems it was built but wasn't published (despite what launchpad told), I rerun it :p
[10:53] <sil2100> didrocks: since Apps was blocked on Friends, and Friends was blocked on unity autopilot ;p
[10:53] <sil2100> ACK :)
[10:54] <sil2100> didrocks: you free for some packaging ACKs?
[10:54] <didrocks> sil2100: sure, I'm waiting for u-s-c to be published
[10:56] <sil2100> didrocks: platform stack: http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_powerd_0.13+13.10.20130718-0ubuntu1.diff and http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qtubuntu_0.52+13.10.20130718-0ubuntu1.diff
[10:56] <sil2100> didrocks: besides stylistic issues, it's ok to me
[10:57] <didrocks> sil2100: +1 for me as well
[10:57] <didrocks> sil2100: ok, mirslaves don't seem to run fine, I wonder if the machines are not dead with the previous unity run
[10:57] <didrocks> sil2100: hum, same on ati
[10:57] <didrocks> I think it's not that, something doesn't start then…
[10:58] <sil2100> hmm, I think jibel needs to help out here ;/
[10:58] <didrocks> sil2100: let me kill those
[10:58] <didrocks> sil2100: otto support killing :)
[10:58] <sil2100> didrocks: in the meantime, http://10.97.0.1:8080/view/cu2d/view/Head/view/Friends/job/cu2d-friends-head-3.0publish/99/artifact/packaging_changes_friends_0.2.0+13.10.20130718-0ubuntu1.diff <- friends!
[10:58] <didrocks> sil2100: just want to unblock for sdk/apps running
[10:59] <didrocks> sil2100: ack for friends :)
[11:00] <didrocks> sil2100: for indicators, maybe bump the regression triggers?
[11:00] <didrocks> sil2100: seeing how the stack is dealing anyway…
[11:00] <sil2100> hmm ;/ I think that might be a good idea, since the second run has even more failures
[11:00] <sil2100> didrocks: maybe I could publish  the stack anyway?
[11:00] <didrocks> sil2100: that as well
[11:01] <sil2100> Those clearly seem to be AP issues, not regressions
[11:01] <sil2100> Then I bump the thresholds a bit
[11:01] <didrocks> sil2100: yeah, for mislaves, it seems to be the stack having issues (maybe the lightdm version?), the other tests are running
[11:01] <didrocks> sil2100: great, thanks!
[11:03] <sil2100> didrocks: in the meantime, I'll fix phone config, as it's missing packages it seems ;/
[11:04] <didrocks> sil2100: ah ok, and media is ok?
[11:04] <sil2100> didrocks: yes, published - it was waiting on manual publications of other stacks
[11:04] <sil2100> No packaging issues
[11:04] <didrocks> great :)
[11:09] <sil2100> didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/fix_extra_pkgs_phone/+merge/175534 <- I'll redeploy ;)
[11:10] <didrocks> sil2100: approved
[11:13] <sil2100> didrocks: hmmm, I got this error when trying to run publish for indicators (without force):
[11:13] <sil2100> http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/117/console
[11:13] <didrocks> sil2100: maybe they change something in the bzr config? try to redeploy the stack without -S, it should reset the destination as the right one
[11:14] <didrocks> sil2100: what you need I guess is             cmd = ["bzr", "config", "-d", "lp:{}".format(current_branch.unique_name), "public_branch={}".format(lpb)]
[11:14] <sil2100> didrocks: you mean, I should redeploy or republish the stack again?
[11:15] <didrocks> sil2100: well, redeploying is setting the right bzr config
[11:15] <didrocks> sil2100: I bet upstream changed their bzr config without fixing that
[11:15] <sil2100> Ok
[11:17] <sil2100> SDK yay \o/
[11:17] <didrocks> yep :)
[11:17] <didrocks> I think apps is almost there
[11:17] <sil2100> didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/SDK/job/cu2d-sdk-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-ui-toolkit_0.1.46+13.10.20130718-0ubuntu1.diff <- looks ok to meh!
[11:18] <didrocks> sil2100: yeah, it's in the distro, in universe and delivered by the same stack, fine as well! :)
[11:20] <sil2100> didrocks: btw. is the archive ready for ubuntu-geoip? ;)
[11:22] <didrocks> sil2100: it's already in main apparently, maybe it needs to check the packaging diff :)
[11:22] <didrocks> sil2100: or we can add to one stack and wait to be in manual publication, as you wish
[11:22] <didrocks> sil2100: run check-mir on it
[11:22] <didrocks> sil2100: as it's in main, all build-deps should be in main
[11:24] <didrocks> sil2100: apps passed!
[11:24] <didrocks> sil2100: is publishing indicators better now?
[11:24] <sil2100> \o/
[11:24] <didrocks> sil2100: ah, phone seems to have failed because the machine was rebooting
[11:25] <didrocks> sil2100: maybe after the reboot request, we should add a sleep 60 in the otto job
[11:25] <didrocks> jibel: ^
[11:25] <sil2100> didrocks: checking apps!
[11:26]  * didrocks cancels ati as we'll need to reload for intel anyway
[11:26] <sil2100> didrocks: eh, I blew it and re-ran the indicators stack instead of just the publish job ;p No problem though!
[11:26] <sil2100> didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_share-app_0.12~+13.10.20130718-0ubuntu1.diff <- ACK?
[11:26] <sil2100> Looks like a valid fix for autopilot package
[11:26] <didrocks> sil2100: did you stop the indicators check?
[11:26] <didrocks> sil2100: maybe no need to rerun once again autopilot, or as you wish :)
[11:26] <didrocks> sil2100: yeap, for binNMUing
[11:26] <sil2100> didrocks: I cancelled it ;p
[11:27] <didrocks> oh, it's my fix
[11:27] <didrocks> even more valid then :p
[11:27] <didrocks> sil2100: you didn't cancel the autopilot-saucy-daily-release though
[11:27] <didrocks> and it started :p
[11:27] <sil2100> didrocks: right, will do that now - btw. is it safe?
[11:27] <sil2100> To cancel the autopilot job?
[11:27] <didrocks> sil2100: should be yeah, jibel worked on that
[11:28] <jibel> didrocks, which job, there is already a 30s wait before rebooting
[11:29] <didrocks> jibel: let me get it, once sec
[11:29] <sil2100> didrocks: indicators published! \o/
[11:29] <didrocks> sil2100: great, was that config issue then :)
[11:29] <didrocks> jibel: that one: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/496/label=autopilot-intel/console
[11:30] <sil2100> didrocks: the webapps stack still has some problems though, will have to look into what's up
[11:30] <sil2100> robru probably knows more about that
[11:31] <sil2100> didrocks: but I guess the most important stacks are handled now
[11:32] <didrocks> sil2100: I'm rerunning phone right now
[11:33] <sil2100> didrocks: wait!
[11:33] <sil2100> Why?
[11:33] <sil2100> It passed!
[11:33] <didrocks> sil2100: it *just* passed :p
[11:33] <sil2100> Ah
[11:33] <sil2100> ;)
[11:34] <didrocks> 18s ago
[11:34] <didrocks> 19
[11:34] <didrocks> 20
[11:34] <didrocks>  :)
[11:34] <didrocks> sil2100: sounds like you can manually publish it :)
[11:34] <sil2100> It said 2 min here ;p Or something!
[11:34] <didrocks> not for publish
[11:34] <sil2100> Puuublissheeed
[11:34] <didrocks> sil2100: basically, we need to look at the jobs timestamp
[11:34] <didrocks> (and the one which failed/starts)
[11:34] <didrocks> the time is the time the job was started
[11:34] <didrocks> so head was started 3 minutes ago now
[11:35] <didrocks> and we went to publish 1 min ago
[11:35] <didrocks> (and right, it's confusing :p)
[11:36] <didrocks> sil2100: I'll continue to fight on the mir side while you finish the cleanups and so on :)
[11:36] <didrocks> sil2100: I hope xnox can help you with the header thing as he promised :)
[11:36] <sil2100> didrocks: right! Ok :) Good luck!
[11:36] <didrocks> thanks!
[11:36] <sil2100> I'll be going to lunch soon though, but good to have the good stacks all ok
[11:36] <didrocks> sil2100: yeah ;)
[11:46] <jibel> sil2100, FTR http://10.97.0.1:8080/job/autopilot-saucy-daily_release/496/label=autopilot-intel/console is bad luck, jenkins successfully scheduled a job, during the few seconds available before the machine reboots after its daily upgrade.
[11:46] <jibel> sil2100, I'll add a quiet period to guard against that
[12:08] <seb128> Laney, do you work on the phone settings? (just reading appdevel backlog)
[12:08] <Laney> yeah
[12:08] <seb128> ok
[12:08] <Laney> Tried to ping you but you were offline
[12:08] <Laney> :-)
[12:08] <seb128> Laney, please update the blueprint ;-)
[12:08] <Laney> Next question will be where to get the dial pad / contact chooser from
[12:08] <seb128> Laney, and thanks for working on it!
[12:08] <Laney> sure
[12:08] <seb128> hehe
[12:08] <seb128> I was just about to ask about that
[12:09] <seb128> did you try talking to whoever is doing lp:phone-app about that?
[12:09] <Laney> not yet
[12:09] <seb128> is the dialpad the same there?
[12:09] <seb128> we need at least one in system-settings to share between bluetooth and phone (and maybe others)
[12:10] <Laney> it's not the same as the design
[12:10] <Laney> but in principle, if you can replace the dial button with set and cancel, would probably be alright
[12:11] <Laney> depends how reusable it is of course
[12:12] <Laney> bp-ed
[12:12]  * Laney lunches
[12:20] <seb128> Laney, enjoy
[12:21] <seb128> Laney, btw do you plan to work on backends or just UI for those? we should perhaps put a warning in the UI for things that don't actually work
[12:22] <seb128> Laney, some people on #ubuntu-touch got confused by the carrier name being wrong yesterday, which made me think that we don't want to mislead users thinking they deactivated e.g 3g when they didn't
[13:32] <Laney> seb128: well, where we have backends to use...
[13:32] <seb128> Laney, I think you might be able to get the carrier through qtsystems...
[13:33] <Laney> I don't know how I'm supposed to check it works
[13:33] <seb128> but I don't have a phone with active sim to try
[13:33] <seb128> we need kenvandine to help there ;-)
[13:34] <kenvandine> sure :)
[13:34] <kenvandine> Laney, got any code for me to test?
[13:34] <seb128> NetworkInfo->networkName seems it might do what we want
[13:34] <seb128> kenvandine, wait, I will try to cook a small example
[13:34] <kenvandine> awesome
[13:35] <kenvandine> Qt or QML?
[13:35] <seb128> qml
[13:36] <Laney> do you have a qtsystems api reference?
[13:45] <seb128> Laney, no, I'm trying to guess from the source/.h :/
[13:45] <seb128> kenvandine, Laney: http://paste.ubuntu.com/5887585/
[13:45] <seb128> but no clue what I'm doing :p
[13:45] <Laney> sad
[13:45] <seb128> 0 is the device number
[13:45] <Laney> there doesn't even appear to be an api reference online anywhere
[13:46]  * kenvandine tries
[13:47] <kenvandine> woorks
[13:47] <kenvandine> works
[13:47] <seb128> carrier name included? ;-)
[13:47] <kenvandine> tech: 3
[13:47] <kenvandine> gsm on: 6
[13:47] <kenvandine> name T-Mobile
[13:47] <kenvandine> yes
[13:47] <seb128> \o/
[13:47] <Laney> nice
[13:47]  * seb128 files mp for carrier name
[13:47] <seb128> Laney, if that's ok with you?
[13:47] <Laney> what are those numbers?
[13:47] <Laney> sure
[13:48] <kenvandine> is there an enum or something that explains those numbers?
[13:49] <Laney> I think it's probably sensible for certain things to be left to those who have appropriate devices
[13:49] <kenvandine> annoying... qtcreator doesn't have any completion for the system info api
[13:49] <Laney> in terms of getting things done efficiently
[13:49] <kenvandine> indeed
[13:50] <Laney> hmm, there's a doc/ in qtsystems orig tarball
[13:50] <seb128> not sure, I'm looking at src/systeminfo/linux/qnetworkinfo_linux.cpp
[13:51] <seb128> .h as well
[13:51] <Laney> such weird source package names
[13:52] <kenvandine> http://harmattan-dev.nokia.com/docs/library/html/qtmobility/qml-networkinfo.html
[13:52] <kenvandine> looks like 6 is "Home Network"
[13:52] <kenvandine> those aren't current docs
[13:52] <kenvandine> but probably similar
[13:53] <seb128> yeah
[13:54] <kenvandine> http://qt.developpez.com/doc/5.0-snapshot/qml-qtsysteminfo1-networkinfo/
[13:55] <kenvandine> 5.0 docs
[13:55] <Laney> nice
[13:55] <seb128> great
[13:56] <seb128> kenvandine, Laney: I'm going to send the mp after the meeting that start in 4 minutes
[13:56] <seb128> I hope the hangout is not going to break my laptop again :p
[13:56] <kenvandine> hehe
[13:57] <Laney> use your phone
[13:57] <Laney> they're totally the best hangout clients
[13:57] <kenvandine> anything else device specific that i should work on?
[13:57] <seb128> Dell sent a tech today to change some parts in the laptop
[13:57] <seb128> I sort of want to test if that did it
[13:58] <seb128> kenvandine, the panel is https://wiki.ubuntu.com/Networking?action=AttachFile&do=get&target=phone-settings-cellular.png
[13:58] <Laney> "all of that stuff"
[13:58] <seb128> I will just send the carrier stuff since I've it done
[13:58] <seb128> if you want to pick on the other ones feel free
[13:59] <kenvandine> seb128, do you have a branch already that has the UI?
[13:59] <kenvandine> or starting from scratch?
[13:59] <Laney> trunk!
[13:59] <seb128> kenvandine, trunk
[13:59] <seb128> ;-)
[13:59] <kenvandine> cool!
[14:00] <seb128> even the daily
[14:00] <Laney> doesn't look like qtsystems lets us do everything though
[14:01] <Laney> I guess it's read only
[14:01] <kenvandine> the switches won't use this API
[14:01] <kenvandine> those should use the network indicator stuff
[14:01] <kenvandine> right?
[14:02] <Laney> yeah, I guess that'll provide that
[14:02] <Laney> don't know how to do the "Manually" bit
[14:02] <kenvandine> true
[14:02] <kenvandine> i guess that will be a cyphermox_ thing :)
[14:02] <kenvandine> cyphermox_, i assume the carrier choice stuff will use network manager?
[14:02] <seb128> ok, meeting tim
[14:02] <seb128> e
[14:02]  * seb128 starts hangout
[14:03] <seb128> let's see if Laney has sound this week
[14:05] <seb128> cyphermox_, want to join the settings call?
[14:11] <seb128> larsu, we just lost you
[14:11] <seb128> when you froze
[14:32] <seb128> yeah, laptop handled then hangout fine this week!
[14:32] <Laney> woot
[14:33] <Laney> firefox?
[14:33] <Laney> phwoar, my phone is hot not
[14:33] <Laney> now
[14:34] <tkamppeter> mlankhorst, I have tested the new Saucy X from x-staging PPA.
[14:35] <seb128> Laney, no, chromium, I didn't dare trying firefox
[14:35] <seb128> that was having issues on its own without the laptop ones
[14:35] <Laney> heh
[14:36] <Laney> huge MP is huge
[14:37] <seb128> which one?
[14:37]  * seb128 has a stack of small mp coming
[14:37] <Laney> language UI
[14:37] <seb128> oh
[14:37] <seb128> reminds me that I should have another look to ev's one
[14:37] <seb128> or if somebody wants to ack it feel free
[14:40] <Laney> "using GSettings to store the settings that we're setting"
[14:40]  * Laney rewords that sentence
[14:52] <sil2100> kenvandine: ping!
[14:52] <sil2100> kenvandine: are you around?
[14:52] <sil2100> kenvandine: would you mind if I enable webaccounts-browser-extension for daily release? It has no integration tests, but mardy said it would be hard to create such
[14:54] <kenvandine> syre
[14:54] <kenvandine> sure
[14:54] <sil2100> \o/
[14:55] <Laney> seb128: did you mean to advise Ev to keep a plugins/diagnostics/ directory?
[14:56] <seb128> Laney, no, I didn't think about the directory structure when I reviewed, just about the icons
[14:56] <seb128> Laney, ideally it should move under plugins/privacy ... as a subdir there might make sense
[14:56] <Laney> yes
[14:57] <Laney> I'll review the content and fix that if it's ok otherwise
[14:58] <seb128> Laney, thanks
[14:59] <seb128> Laney, so did you say that you were emailing -phone about the settings stuff or should I?
[14:59]  * seb128 got confused
[14:59] <Laney> I emailed /you/ with a draft!
[14:59] <seb128> ah
[14:59]  * seb128 checks email
[15:00] <seb128> Laney, looks good to me, not sure if we want to mention ringtone ... but I can reply with that
[15:00] <seb128> stuff like flight mode or rotation lock don't seem to have a "natural owner"
[15:00] <Laney> yep
[15:00] <seb128> where ringtone can be seen as a phone-app setting
[15:04] <Laney> sent
[15:05] <seb128> great
[15:27] <sil2100> didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/daily_release_stuff/+merge/175603 <- ;)
[15:27] <sil2100> didrocks: with this there will be only one daily_release: False that's not documentated
[15:27] <sil2100> didrocks: since Wellark seems AFK
[15:29] <didrocks> sil2100: everything is already in distro?
[15:29] <didrocks> no need for prenewing?
[15:29] <sil2100> didrocks: ah, indicator-location needs preNEWing (almost forgot!), but  webaccounts-browser-extension packages are in distro already
[15:30] <sil2100> didrocks: I discussed with Ted and kenvandine and we decided to release it as it is - it doesn't have sufficient integration tests, but it's not used anywhere yet and still waiting for its 'prime time'
[15:30] <sil2100> didrocks: so it's safe as it is now
[15:31] <didrocks> sil2100: ok, need to preNEWing, don't have the time right now TBH ;)
[15:31] <didrocks> sil2100: start on unity-mir meanwhile maybe?
[15:31] <sil2100> didrocks: no problem, the branch can wait ;)
[15:32] <sil2100> didrocks: what branches are those for unity-mir ;p?
[15:33] <didrocks> sil2100: racarr is upstream
[15:33] <sil2100> unity-system-compositor?
[15:41] <didrocks> sil2100: no no, unity-mir
[15:42] <sil2100> Ok, I'll poke Robert about it then ;)
[15:42] <sil2100> (I don't want to disturb)
[15:58] <mhr3> seb128, found a screen recorder that works in s?
[15:59] <seb128> mhr3, I didn't try again is grecordmydesktop still broken?
[16:00] <ricotz> mhr3, kazam ;)
[16:00] <mhr3> seb128, ricotz, neither works for me
[16:01] <ricotz> mhr3, then maybe plain avconv
[16:29] <seb128> Laney, you said you were reviewing ev's work and the language panel right?
[16:29] <Laney> yes / no :P
[16:29] <seb128> Laney, let me know if you want me to have a look
[16:30] <seb128> ok, I'm going to review the language one then
[16:30] <Laney> sure
[16:31] <Laney> don't hesistate to get a second review if you want one
[16:33] <seb128> let's see
[16:33] <seb128> my guess is that I'm going to find at least nitpicks so we can get another reviewer for the second iteration ;-)
[16:33] <seb128> (same as with ev's one)
[16:37] <seb128> time for some exercice, bbl
[17:11] <Laney> ok, I'm off
[17:12] <Laney> Tomorrow I'll poke about there being a dialer widget and look at starting a gsettings-touch-schemas package or so, then make some settings persist
[17:12] <Laney> \o
[17:18] <sil2100> o/
[17:35] <mterry> desrt, heyo!  I remember some talk about an accountsservice patch to allow arbitrary key/value settings.  Did that ever progress?
[17:36] <sil2100> didrocks: hm, quick question!
[17:36] <sil2100> didrocks: when and how are the *.ignore files cleaned up?
[17:36] <sil2100> didrocks: those that get created by cu2d-skip
[17:37] <didrocks> sil2100: everyday or everytime you rebuild a full stack
[17:37] <didrocks> (without specifying packages)
[17:37] <desrt> mterry: ya.  it's landed upstream and in the distro already
[17:38] <didrocks> sil2100: it's mv <dir> <dir>.bak
[17:39] <desrt> mterry: see the 'org.mydm.*' files in http://cgit.freedesktop.org/accountsservice/tree/doc for an example of how to use it
[17:39] <sil2100> didrocks: ah, ok, so the whole stack directories are moved, yes?
[17:39] <mterry> desrt, oh swell.  changelog didn't call it out, and I didn't look deeper
[17:39] <mterry> desrt, thanks!
[17:40] <desrt> mterry: what are you adding?
[17:41] <mterry> desrt, nothing yet.  I *might* add a key related to the demo of edge hints on first-boot
[17:41] <mterry> (for the phone)
[17:42] <desrt> mterry: it's our intention that our current patches for various things like wallpaper, message-count, etc. be migrated over to this interface eventually
[17:42] <desrt> if you're mucking around in that area, .... ;)
[17:42] <mterry> desrt, true
[17:42] <desrt> would be nice to nuke some accountservice patches
[17:42] <mterry> desrt, though the beauty of this is that my new keys don't need to bother the accountsservice package  :)
[17:43] <desrt> precisely
[17:43] <desrt> but we still have some old patches there for things before we had this interface
[17:43] <mterry> Yeah I know
[17:43] <desrt> would be nice to lose those
[17:43] <mterry> If I'm feeling fancy, I'll look at 'em
[17:43] <desrt> thanks
[17:44] <desrt> (you're always feeling fancy, so this is a high chance)
[17:49] <mpt> larsu, hey, remember when Super+M used to open the messaging menu? If that code still exists, then bug 558581 is related to bug 1201679.
[17:49] <ubot2`> Launchpad bug 558581 in indicator-applet (Ubuntu) "Indicator-applet forcibly overrides Super+m key combo" [Low,Triaged] https://launchpad.net/bugs/558581
[17:49] <ubot2`> Launchpad bug 1201679 in unity (Ubuntu) "ibus' Super+Space shortcut (usually) doesn't work" [Undecided,New] https://launchpad.net/bugs/1201679
[17:51] <larsu> mpt: super+m opens the dash for me...
[17:51] <larsu> oh, music lens I guess
[17:51] <larsu> I'm not aware that super+m ever openend the messaging menu
[17:51] <mpt> larsu, exactly. The Dash is trumping the messaging menu in the same way as it's trumping IBus.
[17:52] <mpt> But maybe we should just drop Super+M for the messaging menu.
[17:53] <larsu> mpt: right now the messaging menu doesn't listen to that combo, so I guess it's already dropped :)
[17:54] <larsu> maybe _because_ people wanted it for the dash?
[18:10]  * didrocks waves good evening
[18:17] <seb128> chrisccoulson, Laney: wth with your country: http://static.pcinpact.com/images/bd/news/136132.png
[18:17] <seb128> safari > i.e > chrome > firefox
[18:18] <chrisccoulson> what can i say, we've got more money than sense here in the UK ;)
[18:18] <seb128> (that's from http://www.atinternet.fr/en/documents/google-chrome-on-the-verge-of-becoming-leader-in-europe/)
[19:01] <davmor2> seb128: you got to understand the ignorance of the masses in the UK,  if it's shiny it good, the shiniest products are always the best, and the best shinies are mad be apple, and why install a browser when there is one right there ;)
[19:37] <attente> mlankhorst, hey
[19:44] <larsu> hm, why do we have gnutls at 3.0.11+really2.12.23-1ubuntu2 ?
[19:44]  * larsu can't compile gnome-settings-daemon master
[19:44] <larsu> (which needs >= 3.0)
[19:47] <mdeslaur> larsu: because of licensing issues. gnutls 3.x is in the "gnutls28" package
[19:47] <larsu> mdeslaur: in saucy? I don't seem to have it.
[19:48] <mdeslaur> larsu: https://launchpad.net/ubuntu/+source/gnutls28
[19:48] <mdeslaur> larsu: problem is, gnome-settings-daemon is in main, and gnutls28 is in universe
[19:52] <larsu> mdeslaur: hm. Can I just force-install the deb?
[19:53] <mdeslaur> larsu: it can be installed in parallel I believe. now you've got me curious, what uses gnutls in gnome-settings-daemon?
[19:53] <seb128> larsu, sudo apt-get install libgnutls28-dev?
[19:53] <larsu> mdeslaur: I have no idea, configure fails :)
[19:54] <larsu> seb128: ah, of course!
[19:55] <mdeslaur> perhaps I'm blind...I don't see anything in there related to gnutls...
[19:55]  * mdeslaur looks some more
[19:56] <larsu> mdeslaur: oops, it was glib-networing, my bad (me is jhbuilding too much tonight)
[19:56] <larsu> seb128, mdeslaur: works now, thanks for your help!
[19:56] <seb128> yw!
[19:56] <seb128> larsu, interesting info though, it means we are going to hit issues with the next update
[19:57] <larsu> :)
[20:02] <mdeslaur> they can't even legally link glib-networking, which is GPL 2 to gnutls 3.x which is LGPL3
[20:03] <mdeslaur> oh, maybe it's gpl2+
[20:03] <mdeslaur> anyway
[20:03]  * mdeslaur goes away
[21:19] <jbicha> larsu: I filed https://bugzilla.gnome.org/show_bug.cgi?id=704503 for you :)
[21:19] <ubot2`> Gnome bug 704503 in network "Reconsider glib-networking dependency on gnutls 3.0" [Critical,Unconfirmed]