[15:21] <balloons> flocculant, wxl, you may notice I'm adding you to a few tasks in GCI
[15:26] <flocculant> balloons: mmm - looking at one now - how is one of these students supposed to work out that to run tests for a flavour - the download link you gave is no good?
[15:27] <flocculant> example - how can I test mousepad on an ubuntu install ;)
[15:28] <balloons> flocculant ?
[15:28] <balloons> I don't doubt there may be an issue. can you edit it and fix the description?
[15:28] <flocculant> well
[15:29] <flocculant> what *I* was going to do was point at xubuntu daily current - then point at xubuntu package tests
[15:29] <flocculant> I'd assume wxl would do the same
[15:29] <flocculant> well - almost - Lubuntu instead :p
[15:32] <flocculant> balloons: any documentation about instance count and time to complete - or is it as easy as we want this done 50 times and you get 3 days to do your one?
[15:32] <flocculant> https://codein.withgoogle.com/dashboard/tasks/6233079207165952/
[15:33] <balloons> flocculant, yep that's correct
[15:33] <flocculant> check that now - Ubuntu specific
[15:33] <flocculant> impossible to make them generic I Think
[15:33] <balloons> ok. So shall we just add ones for xubuntu and lubuntu as well then?
[15:33] <flocculant> I was going to
[15:34] <balloons> great, thanks
[15:34] <flocculant> wasn't doing anything today - not working tomorro
[15:34] <flocculant> w
[15:34] <balloons> well then.. :-) You can join me in writing tasks if you wish
[15:34] <flocculant> so was going to bung a bunch of X specific things
[15:34] <balloons> yes, specific is good. You are right
[15:34] <balloons> better to be specific
[15:34] <flocculant> well - tomorrow I will - today I'm doing r/l things ;)
[15:35]  * balloons laughs when flocculant tags balloons as mentor for all of them
[15:35] <flocculant> ha ha ha
[15:35] <flocculant> I assume that the mentee's mail mentors?
[15:35] <balloons> well, the key to the mentor bit is you agree to review the work at the very least
[15:36] <flocculant> ofc
[15:36] <flocculant> so ...
[15:36] <balloons> and yes, in general, you will provide help if needed
[15:36] <flocculant> what we need to do is set anything using the tracker to a date AFTER someone fixes the tracker filtering \o/
[15:38] <flocculant> balloons: as long as you don't add me to something I'm just going to say 'What?' to I'm fine
[15:48] <balloons> flocculant, I like that idea! We need to get those tracker issues added
[15:48] <balloons> it's on the list, but I can only braindump and type so fast
[15:48] <flocculant> yea ofc
[15:49] <flocculant> balloons: why don't you concentrate on those - I'll fill QA qa tracker things up fast enough when I get going tomorrow
[15:49] <balloons> thank you flocculant, I appreciate it. I am indeed saving QA stuff for last, as I'm trying to brainstorm and get the tasks already pending in other areas in
[15:50] <flocculant> I won't do tracker code tasks - not a clue :p
[15:50] <flocculant> other than I know what I would like to *see* :)
[15:52] <flocculant> balloons: quick question - on the iso test task - you gave it 3 days? reason for that? I'd be suprised it took longer than an hour ...
[15:52] <flocculant> or is that time between someone saying I'll do that and finishing?
[15:53] <balloons> flocculant, the idea is after 3 days if the person who said 'i want to do this' hasn't completed it, the task resets
[15:54] <balloons> since we have a high instance count, this actually doesn't matter too much in this case
[15:54] <flocculant> ok - thanks
[15:54] <balloons> but it's intended I believe to prevent people from blocking all the tasks
[15:54] <balloons> and never finishing :-)
[15:54] <flocculant> right
[15:54] <flocculant> yea - that makes sense
[15:56] <flocculant> I'll have done a bunch by the time you get around to waking up tomorrow
[16:21] <balloons> Heh. Magic while i sleep. Tis nice


[04:06] <larsu> good morning :)
[04:49] <pitti> Bonjour tout le monde
[04:55] <larsu> bonjour pitti
[04:57] <pitti> larsu: wow, you are early :)
[04:57] <pitti> larsu: in my defense, I was in the garden, collecting snails
[04:58] <larsu> pitti: haha, breakfast?
[04:58] <pitti> larsu: je n'est suis pas français !
[04:59] <larsu> pitti: I figured now that you can speak french, ...
[06:28] <darkxst> pitti, hey!
[06:35] <RAOF> Grr. Why does logind conflate VTs and local sessions?
[06:35] <pitti> hey darkxst, hello RAOF
[06:35] <RAOF> pitti: Good morning!
[06:40] <darkxst> pitti, any chance you could look at the retracer sometime soon?
[06:45] <RAOF> pitti: Do you know any way of interrogating logind's internal state to see which session it considers active?
[06:46] <RAOF> Particularly, I want to know why my one and only session isn't considered active.
[06:48] <pitti> RAOF: "loginctl show-session c2" (or any session identifier from "loginctl") shows the details
[06:50] <pitti> darkxst: ah, sore spot..
[06:51] <sil2100> Morning!
[06:55] <darkxst> pitti, we still get way more data from raring+ppa than saucy, but its all mostly useless!
[06:57] <RAOF> pitti: Yeah, but that doesn't show which session logind thinks *is* active. There's only one session listed, and it's not active
[07:02] <sil2100> Mirv: hello!
[07:03] <pitti> RAOF: "loginctl" shows all sessions, so if none is active then there just isn't a registered PAM session for that VT
[07:03] <RAOF> pitti: Correct! My session isn't associated with a VT!
[07:03] <pitti> RAOF: sorry, I mean not a foreground one, which is the current VT
[07:03] <pitti> RAOF: ah right, that's like ssh then
[07:04] <sil2100> Mirv: do you have a moment for some stacks reviews?
[07:04] <sil2100> Mirv: https://code.launchpad.net/~sil2100/cupstream2distro-config/fix_extra_pkgs_next/+merge/177512
[07:05] <sil2100> Mirv: the QA stack is missing ibus, but I guess I'll have to discuss this with seb, as the 'extra package' won't be needed once the new ibus goes out of -proposed
[07:05] <sil2100> Mirv: so for now all the other stacks
[07:05] <pitti> RAOF: although, that apparently is also active; ssh is just "remote"; so, no immediate idea then
[07:05] <sil2100> Mirv: would be grateful for a quick review and approval since I want to move the stacks ;)
[07:08] <RAOF> Why does logind even have the ability to activate a session?
[07:08] <pitti> RAOF: that's what logind managers have used for years (well, it's ConsoleKit equivalent back then) to switch between multiple sessions
[07:08] <pitti> login managers or things like indicator-session
[07:09] <Mirv> sil2100: hi!
[07:09] <Mirv> sil2100: I had https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/add_libubuntu-application-api1_to_platform/+merge/177509 already waiting for you :)
[07:09] <Mirv> to fix my stack
[07:09] <RAOF> Yeah, but you can't switch to an arbitrary logind session.
[07:10] <RAOF> This is particularly annoying because logind is going to be *unable* to switch between our sessions.
[07:10] <RAOF> Beacuse a switchable-session-is-a-VT, and all our sessions are going to be on a single VT.
[07:10] <sil2100> Mirv: ok, hm, so maybe we can approve your branch and then mine
[07:11] <sil2100> Mirv: since my branch has the same change, it shouldn't conflict ;)
[07:11] <Mirv> sil2100: right, that should work I think
[07:11] <darkxst> pitti, or perhaps I could just get the scripts you use for the retracer?
[07:11] <sil2100> Mirv: approved yours ;)
[07:11] <pitti> darkxst: sure, there's nothign particularly magic about them
[07:12] <sil2100> Mirv: once it gets in, approve mine if +1
[07:12] <pitti> darkxst: this is basically a checkout of lp:apport, plus a checkout of https://code.launchpad.net/~ubuntu-archive/apport/lp-retracer-config/ for the per-ubuntu-release config
[07:12] <pitti> darkxst: this branch also has the crontab which I'm using in the data center
[07:14] <Mirv> sil2100: yeah, will check and +1
[07:15] <Mirv> sil2100: thanks :)
[07:16] <pitti> RAOF: right, so we either need to disable user switching from the session indicator, or teach logind about Mir's idea of VT multiplexing; then it needs an alternate way of getting notified about what the current session is and how to enumerate them (i. e. Mir sending out some signals)
[07:17] <RAOF> I feel it might be simpler to just incorporate that functionality into lightdm
[07:17] <RAOF> But for now I need to help prepare Zoë for dinner.
[07:17] <pitti> or that
[07:17] <pitti> that would also avoid heavy patches against logind, and keep the Ubuntu specific bits together
[07:18] <pitti> RAOF: logind still needs to know about that though, to be able to assign correct device ACLs
[07:18] <asac> pitti: checking
[07:18] <asac> pitti: ctrl+alt+f1 goes to console as expected (no suspend)
[07:19] <pitti> asac: yes, I mean if you close the lid on VT1, does it suspend?
[07:20] <asac> pitti: ok will try in a bit
[07:20] <pitti> asac: so you can reproduce suspend errors in X?
[07:21] <asac> pitti: last two days whenever i closed the lid it never suspended
[07:21] <asac> always have to remember to push the menu
[07:22] <asac> ok trying console and lid
[07:22] <asac> pitti: yeah. on console it works
[07:22] <asac> on x it just turns off the screen
[07:22] <pitti> asac: just to cover all bases, what do these show?
[07:22] <pitti> gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action
[07:22] <pitti> gsettings get org.gnome.settings-daemon.plugins.power lid-close-battery-action
[07:23] <RAOF> pitti: Unless lightdm applies the ACLs :)
[07:23] <asac> asac@thinki:~$ gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action
[07:23] <asac> 'suspend'
[07:23] <asac> asac@thinki:~$ gsettings get org.gnome.settings-daemon.plugins.power lid-close-battery-action
[07:23] <asac> 'suspend'
[07:23] <pitti> RAOF: sure :)
[07:23] <asac> pitti: ^^
[07:23] <pitti> asac: -> /msg
[07:24] <chrisccoulson> good morning everyone
[07:28] <sil2100> Morning!
[07:28] <sil2100> Mirv: it's in, can you approve my branch?
[07:28] <slomo> Laney: are you planning to go with gstreamer 1.2 for this release? planned release date is somewhere in september just in time for gnome 3.10
[07:30] <RAOF> pitti: Seriously, though, if (in the magical future) lightdm is already handling session tracking and switching it doesn't seem as though there's any reason to keep logind around.
[07:30] <Mirv> sil2100: yep, redeployed platform and approved your commit for the two others which you can then redeploy
[07:30] <sil2100> \o/
[07:30] <sil2100> Thanks
[07:30] <pitti> RAOF: quite a lot of upstream software depends on it, though; so maybe not in a default ubuntu installation, but as dependencies
[07:31] <RAOF> pitti: libsystemd-login is just a dbus wrapper around logind, right?
[07:31] <sil2100> Mirv: so I'm leaving platform up to you and dealing with all the other stacks
[07:32] <pitti> RAOF: yes
[07:32] <RAOF> So all we'd need to do is expose a compatible dbus interface?
[07:33] <jibel> good morning
[07:33] <RAOF> "all"
[07:33] <pitti> RAOF: in principle, yes
[07:33] <pitti> if lightdm emulates that in terms of Mir sessions, that'd be fine
[07:33] <pitti> that's going to be no small task, though (all the cgroup handling, etc.)
[07:34] <Mirv> sil2100: right, ok
[07:34] <RAOF> logind exposes all that cgroup handling?
[07:34] <pitti> RAOF: i. e. it's d-bus plus a compatible cgroup handling
[07:34] <RAOF> I thought that was basically an implementation detail?
[07:34] <RAOF> Ah.
[07:35] <pitti> well, it is, but (1) we still want that, and (2) quite a lot of software checks for /run/systemd/seats (or similar)
[07:35] <pitti> RAOF: mostly JavaScript/Python/etc. stuff which doesn't want to or can't link to the lib
[07:35] <RAOF> Yay.
[07:35] <pitti> but reproducing the /run state files is rather simple
[07:36] <pitti> RAOF: we actually switched away most upstream software from checking the cgroups, to checking the /run files
[07:38] <RAOF> Ah, well. There's still the transitional case we need to care about, with both VTs and Mir sessions.
[07:38] <RAOF> That makes patching logind more palatable.
[07:39] <pitti> RAOF: would gnome not get a similar problem when switching to wayland?
[07:39] <pitti> RAOF: or does that use different VTs somehow?
[07:39] <RAOF> pitti: GNOME is not planning to use a system compositor; they'll run a Wayland compositor on each VT.
[07:40] <pitti> ah
[07:40] <pitti> so they wouldn't have that problem
[07:40] <seb128> good morning desktopers
[07:41] <RAOF> Right.
[07:41] <RAOF> They also don't get the benefits ☺
[07:42] <RAOF> They might eventually decide that they want them, and then they will indeed hit exactly this problem.
[07:42] <Mirv> sil2100: I wonder why platform still compiles about the package.. bzr pull:d the -config, redeployed, reran with foo
[07:42] <slomo> seb128: (already asked Laney before but maybe you know too?) are you planning to go with gstreamer 1.2 for this release? planned release date is somewhere in september just in time for gnome 3.10
[07:43] <seb128> slomo, hey, we were discussing it recently with kenvandine (he said the new version would be nice/useful for some of the stuff on the touch image)
[07:43] <seb128> slomo, I'm not sure though, I've little confidence on the gstreamer release schedule ... wasn't 1.2 initially scheduled for around GNOME 3.8?
[07:44] <slomo> seb128: well, for the ubuntu touch work that jhodapp is doing you'll need it anyway ;) but that's independent i guess?
[07:45] <slomo> seb128: but yes, our release schedule is not very reliable unfortunately :) however we're almost there now finally, what is missing right now is just some more testing and then it can get the 1.2.0 label
[07:47] <seb128> slomo, right, that's what Ken said, jhodapp's work need it, we could do with a ppa though
[07:48] <RAOF> pitti: In less frustrating news, feel like sponsoring colord 1.0.2-1? :)
[07:48] <pitti> RAOF: sure! still no DM?
[07:49] <RAOF> I'll get around to sending that email sometime :)
[07:49] <didrocks> seb128: hey! how are you?
[07:50] <slomo> seb128: ok, so what information do you need to decide? i think it would make sense to either switch now or after the next ubuntu release to give it enough testing for ubuntu
[07:51] <pitti> RAOF: expected?
[07:51] <pitti> dpkg-source: info: local changes have been recorded in a new patch: colord-1.0.2/debian/patches/debian-changes
[07:52] <pitti> RAOF: i. e. it generates a debian/patches/debian-changes
[07:52] <RAOF> pitti: Yup. You should find that debian-changes contains your glib deprecation fixes.
[07:52] <seb128> didrocks, hey, good, you, having fun at the sprint with everyone? not too much beer drinking? ;-)
[07:52] <pitti> RAOF: ah, not using real patches for that?
[07:53] <didrocks> seb128: not too much beer, lot of discussions, we'll see :)
[07:53] <RAOF> pitti: For things which are upstream I cherry pick.
[07:53] <didrocks> seb128: btw, I honored the promise to work on ubuntu-system-settings during the flight
[07:53] <pitti> RAOF: ah, upstream pulls
[07:53] <didrocks> seb128: small ui changes: https://code.launchpad.net/~didrocks/ubuntu-system-settings/system-update-improvment/+merge/177371
[07:53] <didrocks> do you mind giving a look?
[07:53] <RAOF> pitti: That way I don't have to notice when we pass a revision which contains them :)
[07:53] <didrocks> sil2100: once/if merged, do you mind kicking the stack again with this? ^
[07:53] <pitti> RAOF: ack, sbuilding now; I just wanted to confirm, as they sometimes slip in accidentally
[07:53] <didrocks> small UI changes to have a better demo :)
[07:54] <didrocks> seb128: ah, FYI, I'll be on a meeting during the team meeting, I asked sil2100 to lead it :)
[07:54] <sil2100> \o/
[07:54] <sil2100> didrocks: ok!
[07:54] <didrocks> thanks sil2100 ;)
[07:55] <seb128> didrocks, will review, thanks ;-)
[07:55] <seb128> didrocks, ok
[07:56] <didrocks> seb128: thanks to you ;)
[07:56] <didrocks> seems it's fresh in France as here
[07:57] <seb128> 19°C this morning
[07:57] <seb128> going to get warmer again tomorrow though
[07:58] <pitti> RAOF: uploaded; NB that we are past DIF, so you'll need to sync manually if you want this in saucy
[07:58] <RAOF> pitti: There's no particular reason not to have it; I'll sync away!
[07:59] <slomo> seb128: ok, anyway, let me know if you need any more information or have decided something :)
[08:00] <seb128> slomo, sorry, IRC is a bit busy...
[08:00] <seb128> slomo, when do you plan to land the new one is unstable?
[08:01] <seb128> slomo, also ... is there any known problem with the current 1.1/things to worry about?
[08:02] <Laney> morning
[08:02] <Laney> slomo: I was a bit put off by the advice against adopting it in your announcement the other day :-)
[08:03] <slomo> seb128: unstable once the API is stable, i can't guarantee yet that there will be no changes in anything newly added... but it's unlikely. otherwise, i'm not aware of any regressions that are left, the last one was fixed right before 1.1.3 :)
[08:03] <slomo> seb128: and in general it's all in bugfix and cleanup mode now, no bigger new features are going to happen before 1.2
[08:03] <Laney> I think we'll probably start out with a PPA
[08:04] <Laney> the packaging should be easier anyhow since some of the plugin moves get to be undone
[08:04] <slomo> Laney: well, you ship glib 2.37 too, right? the warning in my announcement mail goes along the same line ;)
[08:04] <sil2100> ugh
[08:04] <Laney> heh
[08:04] <sil2100> didrocks: the apps stack has some problems, so I will probably have to fill in a bug and get it fixed before it can get released today ;/
[08:05] <Laney> slomo: Also I don't really know about it but it'd make me happy if jhodapp's stuff could have some upstream review before we include it ;-)
[08:06] <seb128> slomo, ok, I think it's reasonable for us to consider it once it's unstable
[08:06] <Laney> not sure if he's submitted it yet or is close to
[08:06] <Laney> I'll start work on PPAing it anyway quite soon
[08:06] <Laney> (upstream, not seen his stuff yet)
[08:07] <seb128> Laney, thanks
[08:07] <seb128> Laney, good morning btw ;-)
[08:07] <Laney> hallo!
[08:07] <slomo> Laney: agreed, i think it's still full of bees :) i didn't look at it closer yet
[08:09] <slomo> seb128: ok, what's exactly the reason for depending on it being in unstable? my reason for not putting it there is basically the same as for glib 2.37, if it wasn't for the possible small API changes i would just put it there ;)
[08:10] <didrocks> slomo: ok, please keep bfiller aware
[08:10] <Laney> It's being conservative
[08:10] <didrocks> slomo: sorry, I mean sil2100 ^
[08:10] <seb128> slomo, it has a cost to follow unstable series, we do it for glib because we use some of the new features and we have desrt on board who can help with the issue
[08:10] <seb128> issues
[08:10] <Laney> we have experience with unstable glibs, and also can abuse ryan for fixes if necessary
[08:10] <seb128> slomo, we have less expertise on gstreamer
[08:11] <Laney> so one path with that is ppa, people self select for testing, if no major problems then distro
[08:11] <Laney> helps insulate us a bit
[08:12] <slomo> seb128: ah, makes sense :) thanks for explaining
[08:13] <seb128> slomo, yw
[08:16] <darkxst> pitti, how do the need-retrace tags get set?
[08:19] <pitti> darkxst: through the blob uploaded to Launchpad, in apport/crashdb_impl/launchpad.py _generate_upload_blob()
[08:19] <pitti> darkxst: i. e. they are there when creating the bug
[08:21] <darkxst> pitti, ah right, our bugs are already tagged ;)
[08:21] <pitti> darkxst: yes, you mostly need to create a config file for your project instead of the distro (add a stanza to the config file in lp-retracer-config)
[08:22] <pitti> darkxst: and use 'project': 'ubuntu-gnome', insteaed of 'distro': 'ubuntu' (see /usr/share/doc/apport/crashdb-conf.txt.gz)
[08:23] <pitti> darkxst: crash-digger has a --crash-db option where you supply the new db you are adding (instead of using the "default" one in crashdb.cnof)
[08:24] <darkxst> pitti, thanks, I think i got it now
[08:29] <sil2100> Mirv: are you on the platform stack failure?
[08:30] <rickspencer3> seb128, is there a list of setting backend for Ubuntu Touch that we need for 13.10?
[08:30] <sil2100> Mirv: since I don't want to release the related stacks before knowing if all is ok
[08:31] <sil2100> seb128: hello!
[08:31] <seb128> sil2100, hey
[08:31] <seb128> rickspencer3, define "setting backend"?
[08:31] <sil2100> seb128: how's the ibus release from -proposed going?
[08:31] <seb128> sil2100, it's in saucy proper since yesterday
[08:31] <rickspencer3> seb128, I dunno, like things that need to have settings for them
[08:31] <sil2100> \o/
[08:32] <sil2100> seb128: awesome then! So it seems out otto images are still outdated
[08:32] <sil2100> But good, it means tomorrow all will be ok already
[08:32] <seb128> rickspencer3, the prd has the list, it's basically the ones listed on the "phone" column of https://wiki.ubuntu.com/SystemSettings
[08:32] <rickspencer3> thanks seb128
[08:33] <seb128> rickspencer3, yw
[08:37] <Laney> seb128: have you started doing the suggesting I made to about-connect-check-for-update?
[08:37] <Laney> suggestion
[08:38] <seb128> Laney, I did it yesterday, but not the shared js way, just trying the getByName
[08:38] <Laney> ok, would have done it myself otherwise
[08:38] <seb128> Laney, but it's 1 extra object and 10 lines of code, I'm not convinced of the value of the change...
[08:39] <sil2100> Mirv: ok, redeploying the stack ;/
[08:39] <seb128> Laney, I don't expect us to rename pages
[08:39] <seb128> Laney, I think I'm going to end up doing the shared js stuff to avoid the extra churn in the plugin itself ;-)
[08:40] <Laney> :-)
[08:40] <sil2100> Mirv: re-running the platform stack after redeployment now
[08:41] <Mirv> sil2100: ok, I think should be good now
[08:41] <Mirv> sil2100: I just forgot the -U
[08:42] <Mirv> rusty from vacation still :)
[08:42] <sil2100> ;)
[09:06] <Mirv> seb128: can you check/approve the package rename packaging change of http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_platform-api_0.18.3+13.10.20130730-0ubuntu1.diff ? libplatform-hardware-api1-hybris became libubuntu-platform-hardware-api1, and libplatform-api1-hybris -> libubuntu-application-api1
[09:10] <Sweetshark> seb128: soo, bug 1204449 is blocking on bug 1196263 and I agree with upstream that the reporter is likely seeing ghosts there. Is there any way to go ahead with this SRU (which is fixing critical bugs) despite these vague and nonreproducable claims?
[09:10] <ubot2`> Launchpad bug 1204449 in libreoffice (Ubuntu) "[SRU] LibreOffice 4.0.4 for Ubuntu 13.04 (raring)" [Undecided,Confirmed] https://launchpad.net/bugs/1204449
[09:10] <ubot2`> Launchpad bug 1196263 in libreoffice (Ubuntu) "Libre Office 4.0 Paper Tray" [Undecided,Incomplete] https://launchpad.net/bugs/1196263
[09:12] <seb128> Sweetshark, can somebody test the scenario he describes and confirm if it works/doesn't work for them?
[09:15] <Sweetshark> seb128: If someone has a printer with multiple trays it might give hints. tkamppeter maybe?
[09:15] <seb128> Sweetshark, yes, try asking tkamppeter or maybe in the London office?
[09:16] <Sweetshark> seb128: note though that you cant proof the absence of errors. He might still claim it does not work with _his_ printer.
[09:17] <Sweetshark> seb128: also he hasnt even confirmed that it wasnt a problem in 4.0.2 as released with raring.
[09:17] <sil2100> seb128: are you ready for some quick packaging ACKs? ;)
[09:17] <seb128> Sweetshark, well, I wouldn't block the SRU on it, but it would still be good to check if the problem he points is not an obvious breakage
[09:18] <seb128> sil2100, sure, trying to review Mirv's one but I don't understand all the renames there
[09:18] <seb128> Mirv, it would help to have changes help a bit more than "to match debian guidelines"
[09:18] <xnox> seb128: larsu: http://ubuntuone.com/0u8ueGOxYL3eRu4Gti9PHo =) i'll see if I can find where ubiquity's theming is going absurd =)
[09:18] <sil2100> seb128: ok, in the meantime I'll prepare the rest and send you the links
[09:18] <seb128> Mirv, why are the replaces/breaks versionned rather than just forcing to uninstall the old names?
[09:19] <seb128> xnox, hehe
[09:19] <seb128> sil2100, thanks
[09:19] <larsu> xnox: first absurdity is that it loads the theme in every draw() event...
[09:20] <larsu> xnox: s/theme/background pixmap/
[09:20] <Mirv> seb128: more information at https://code.launchpad.net/~ricmm/platform-api/package-match-sonames/+merge/175181
[09:20] <seb128> Mirv, thanks
[09:21] <seb128> Mirv, looks fine to me, +1
[09:22] <Mirv> seb128: ok, thanks
[09:23] <Sweetshark> seb128: All he claims is "it used to work with the 4.0 ppa on 12.04 at some point". So it could be a/ it doesnt work on 12.04 but works on 13.04 b/ he had some other ppa breaking his stuff c/ it was never working on LibreOffice 4.0.2, but only on e.g. 4.0.0 (which is not what we released with raring) ....
[09:24] <sil2100> seb128: in the meantime! http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/WebApps/job/cu2d-webapp-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-webapps-qml_0.1+13.10.20130730-0ubuntu1.diff
[09:24] <sil2100> seb128: this will be a buuusy week for you... ;)
[09:24] <seb128> Sweetshark, well, as said don't block on that, but if it's easy to check if what he describe is a bug or not you might want tkamppeter/somebody at the office to give it a try and confirm it's a bug (even if it's not a regression it might still be a valid bug)
[09:25] <seb128> sil2100, yeah, thanks didrocks for letting me with some extra pings :p
[09:25] <seb128> sil2100, what's the rational for the arch any -> hardcoded list change there? I though we didn't want to list archs manually anymore?
[09:26] <didrocks> seb128: \o/
[09:27] <didrocks> all worked like according to the plan :)
[09:27] <seb128> :-)
[09:27] <didrocks> just want to show to rickspencer3 I'm not slacking off :p
[09:27] <sil2100> Mirv: tell me once platform and sdk are published
[09:27] <sil2100> seb128: I think there's no real rationale besides making sure that powerpc is not supported ;)
[09:28] <rickspencer3> o/didrocks
[09:28] <rickspencer3> will you be joining us in the spa?
[09:28] <Laney> O_O
[09:28] <seb128> didrocks, do you know if there is a reason we should still use hardcoded arch lists (I think you said Ken has to roll back on not listing ppc because colin was having issues)?
[09:30] <didrocks> rickspencer3: taking my towel :)
[09:30] <seb128> tssss
[09:30] <didrocks> seb128: some packages needed for colin to be able to unblock for webcreds (accounts-settings AFAIK)
[09:30] <didrocks> seb128: but that should be temporary and not needed anymore AFAIK
[09:31] <seb128> didrocks, so http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/WebApps/job/cu2d-webapp-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-webapps-qml_0.1+13.10.20130730-0ubuntu1.diff feels wrong
[09:31] <didrocks> arch: any is better so that the day we start having armel64…
[09:31] <seb128> sil2100, -1 from me, please change back to arch: any or give the rational in the changelog
[09:31] <sil2100> Mirv: since platform got published, could you publish SDK?
[09:31] <sil2100> seb128: ACK
[09:31] <didrocks> seb128: I don't see anything justifying it for me
[09:31] <didrocks> so -1 as well
[09:31] <mlankhorst> rickspencer3: oh btw did you get the memo about touch fixes?
[09:31] <rickspencer3> mlankhorst, no
[09:32] <rickspencer3> mlankhorst, yes!
[09:32] <rickspencer3> I saw that you had an xorg for me to try and stuff
[09:32] <mlankhorst> yeah
[09:32] <rickspencer3> but I hadn't had a chance yet
[09:32] <rickspencer3> mlankhorst, are you still waiting for me?
[09:32] <mlankhorst> rickspencer3: no, but if you want working touch at least it's possible, but hard to get back in raring because it probably requires a newer version of onboard
[09:32] <sil2100> Mirv: I already published all the standard stacks
[09:32] <rickspencer3> mlankhorst, raring is dead
[09:32] <rickspencer3> ;)
[09:33] <rickspencer3> we are on saucy
[09:33] <rickspencer3> put raring out of your mind
[09:33] <mlankhorst> saucy could work, I'm waiting for the backport to 1.14
[09:33] <mlankhorst> rickspencer3: hah, when I still have to land it in the LTS? :P
[09:33] <rickspencer3> mlankhorst, yes
[09:33] <rickspencer3> but for now, our focus still needs to be on Ubuntu Touch for 13.10 to the maximum extent possible
[09:33] <mlankhorst> yeah
[09:34] <sil2100> Mirv: I jump out to the store - please publish SDK in the meantime!
[09:34] <rickspencer3> mlankhorst, so, I worked around this bug by not using the touchscreen with Chromium ;)
[09:35] <mlankhorst> yeah the fixes will be in saucy, was just hoping upstream would merge it to 1.14 so I didn't have to do it manually, it's quite a big patch series..
[09:39] <Sweetshark> seb128: oh, there sure might be valid bug -- otherwise I would not have upstreamed that one. Note though upstream currently has 131 unresolved bugs related to printing (of 251 with resolved bugs). Also note that there are at least two related bugs: One is a (fixed) 3.3->3.4 regression, the other one is reported against 3.6 and was fixed for 4.1: https://bugs.freedesktop.org/show_bug.cgi?id=61186 ...
[09:39] <ubot2`> Freedesktop bug 61186 in Printing and PDF export "Print dialog ignores saved settings from Printer Settings + more" [Normal,Verified: fixed]
[09:40] <seb128> Sweetshark, right, as said, don't block the SRU on it in any case
[09:40] <Sweetshark> ... so without the reporter confirming it still doesnt work in 4.1.0 its actually likely a dupe of fdo#61186 ..
[09:40] <Mirv> sil2100: yeah, on my list
[09:40] <Sweetshark> seb128: yep ;)
[10:18] <mlankhorst> hm looks like upstream has some more fixes that might help without having to update unboard..
[10:24] <seb128> Laney, thanks for approving the dash privacy setting mp ... days/months, I've no idea when design is going to iterate on that, seems safer to just stick with that meanwhile ;-)
[10:25] <Laney> sure
[10:25] <seb128> Laney, oh, new glib out btw, in case you feel like you need a break from system settings at some point ;-)
[10:25] <Laney> I do feel like that :P
[10:25] <seb128> ;-)
[10:25] <Laney> I'm just making datetime use NM for status for now and then I'll do that or gst for a bit
[10:26] <mlankhorst> lucky you, I was looking at fixing xinput :P
[10:27] <Laney> shortly I have to go to the police station and give a statement about my Crime Of The Century :-)
[10:29] <mlankhorst> hah
[10:29] <mlankhorst> did you steal your own bike?
[10:30] <Laney> no comment
[10:30] <Laney> srsly though I told them I thought it wasn't worth anybody's time to do that for the theft of one skewer but they insisted
[10:32] <mlankhorst> oh that
[10:33] <mlankhorst> well it's probably for insurance and/or their own numbers
[10:33] <Laney> that's why I reported it
[10:33] <Laney> didn't expect to have to do anything other than phone up
[10:33] <Laney> maybe there will be an armed response
[10:36] <sil2100> seb128: ah, here's the arch revert for webapps: https://code.launchpad.net/~sil2100/unity-webapps-qml/arch_any/+merge/177559 (if you have a moment)
[10:37] <seb128> sil2100, approved by comment, you need to change the MR status though, I'm not in the right team to do it
[10:37] <sil2100> seb128: thanks!
[10:41] <didrocks> sil2100: hum
[10:41] <didrocks> did you relaunch system-settings?
[10:42] <seb128> didrocks, I did, why?
[10:42] <seb128> didrocks, slangasek wanted a landing
[10:42] <sil2100> didrocks: the merge wasn't merged in back when I checked, so no
[10:42] <didrocks> seb128: did you check it wasn't already launched?
[10:43] <seb128> didrocks, no, nobody else than me is usually dealing with settings stuff
[10:43] <didrocks> seb128: not sure what will happen, I think I stopped the prepare job before it was uploaded in the ppa
[10:43] <seb128> didrocks, aren't you supposed to be busy in IoM? ;-)
[10:43] <didrocks> we'll know in 2 minutes
[10:44] <seb128> didrocks, jenkins flagged a changelog merge back as approved
[10:45] <didrocks> seb128: yeah, I think even if you rebuild, it would have been blocked in the publisher step
[10:45] <seb128> didrocks, I would appreciate if you let me know next time you republish settings
[10:45] <didrocks> seb128: I asked sil2100 first to look at that, so you did relaunch without warning him as well :)
[10:45] <didrocks> (but I admit I didn't tell him before relaunching it)
[10:47] <seb128> didrocks, well, we already had a landing today, I didn't see you ping sil2100 about redoing one ... anyway no problem, I will check next time, I was just 100% nobody else would touch because until now nobody ever did look at settings (out of normal published when the stack is un manual publishing)
[10:47] <seb128> didrocks, sorry for the conflict
[10:47] <didrocks> seb128: no worry at all, we're both guilty :)
[10:47] <didrocks> seb128: TBH, the system would have handled it
[10:48] <didrocks> I'm just unsure about launchpad enabling binary copy of a superseeded package
[10:48] <seb128> cool
[10:48] <didrocks> then, the second publish would have failed
[10:48] <didrocks> (as the version in distro would have been != from the version when prepare run)
[10:48] <didrocks> it would just have been an useless build in the ppa
[10:49] <didrocks> but TBH, I won't challenge that today and test in production :p
[11:54] <sil2100> jibel: hi! Just reminding, https://code.launchpad.net/~sil2100/otto/fix_1203809/+merge/176692 <- the fix has been made as you recommended it ;) So I guess it would be a quick review now!
[11:59] <xnox> seb128: larsu: the menuitem gets the same height as the submenu, thus the menubar ends up having the height of the tallest submenu =( i'm not sure why the menuitem gets such large height. Maybe it's horizontal/vertical error? and/or homogenous somewhere? well I didn't manage to shrink it, with request_size.
[12:00] <larsu> xnox: this is unrelated to my fix, it looks the same to me without
[12:00] <larsu> xnox: I'll have a look later today
[12:01] <xnox> larsu: well, I uploaded your fixes to at least get back the indicators. so it will be on tomorrow's daily cd, to test live / easier.
[12:01] <xnox> larsu: thanks a lot for your branch =)))) !!!!
[12:02] <larsu> xnox: cool, thanks for the quick upload
[13:02] <qengho> chrisccoulson: I can help with Firefox.
[13:03] <seb128> qengho, hey, how is the chromium build on saucy going?
[13:03] <qengho> chrisccoulson: I don't think I'm immersed in its culture enough to adopt, but I want to learn it some.
[13:04] <qengho> seb128: Er, linker bug avoided, I think. Only time will tell.
[13:04] <qengho> seb128: turnaround time is far too long.
[13:04] <seb128> qengho, when do we get an upload? ;-)
[13:05] <qengho> seb128: saucy-proposed should be halfway through building.
[13:05] <seb128> qengho, hum, there was no chromium-browser upload since the 24 ... or you mean you are ppa testing it before archive upload?
[13:07] <qengho> seb128: Hrm, I meant actual distro.  Let me look around.
[13:07] <seb128> qengho, https://launchpad.net/distros/ubuntu/+source/chromium-browser
[13:08] <seb128> https://launchpad.net/ubuntu/+source/chromium-browser/28.0.1500.71-0ubuntu<IP_ADDRESS> is the most recent upload and it failed armhf and i386
[13:09] <kenvandine> mpt, working on the SIM Services page, what should we display if there is no SIM card?
[13:10] <kenvandine> i assume disable the listitem
[13:10] <kenvandine> but should we display something like SIM Services (No SIM found) ?
[13:17] <mlankhorst> sigh, found out that in xserver.git most recent commit broke the test, then found out both the test and the commit were broken :/
[13:23] <mpt> kenvandine, yes, insensitive. https://wiki.ubuntu.com/PhoneApp?action=diff&rev2=5&rev1=4
[13:23] <qengho> seb128: Okay, well, I thought I had it sponsored and uploaded a day ago. I guess I was wrong.  When you said to chrisccoulson that you saw him uploading chromium, I thought that was him uploading  chromium-browser_28.0.1500.71-0ubuntu3 .
[13:24] <seb128> qengho, oh no, that was the previous uploads a week ago, sorry for the confusion
[13:24] <kenvandine> mpt, thx
[13:25] <seb128> chrisccoulson, ^ can you sponsor it?
[13:25] <qengho> seb128: Where do you see the feed? Do you sip from the firehose saucy-proposed mailing list?
[13:25] <seb128> qengho, yep, saucy-proposed ... I just glance over the title in the morning and a few time a day, it's a bit of traffic but just reading the package names in the subject list is taking like a minute
[13:55] <Laney> another u-s-s snapshot?
[13:59] <seb128> Laney, I ran a rebuild, not noticing that didrocks did one, but that was before lunch and didrocks was supposed to have killed it
[13:59] <chrisccoulson> qengho, thanks for the offer :)
[13:59] <Laney> oh and it just took that long to grind through
[13:59] <seb128> didrocks, ^ did you trigger a new one?
[14:00] <seb128> Laney, that's my guess, but it's just guessing...
[14:00] <chrisccoulson> qengho, one thing i need to try and figure out is why the tests don't run in saucy: https://jenkins.qa.ubuntu.com/job/saucy-adt-firefox/
[14:00] <chrisccoulson> they do run ok in raring: https://jenkins.qa.ubuntu.com/job/raring-ppa-adt-mozillateam_firefox_next-firefox/ (same package)
[14:01] <seb128> Laney, ok, that might make you happy, uploaded the new poppler ... that's giving plenty of opportunity to change our mind, by doing rebuild/build fixes, after looking at qt for too many hours
[14:01] <Laney> hehe
[14:01] <Laney> I just started looking at glib
[14:02]  * Laney types d p u t  f t p - m a s t e r really slowly
[14:10] <qengho> chrisccoulson: I'm new to autopkgtest, but I'll poke at it.
[14:10] <chrisccoulson> qengho, thanks. don't worry about it too much if you have other stuff to do though :)
[14:11] <seb128> chrisccoulson, hey, how are you?
[14:11] <didrocks> seb128: yeah, I didn't see anything merged and I wanted to have the stack green
[14:11] <didrocks> seb128: but obviously, I was wrong :p
[14:11] <chrisccoulson> seb128, yeah, not too bad thanks. how are you?
[14:11] <seb128> didrocks, I'm good thanks
[14:12] <didrocks> seb128: sorry ;)
[14:12] <seb128> didrocks, haha, ok
[14:12] <seb128> didrocks, no problem ;-)
[14:28] <sil2100> didrocks: any ETA for all the mir bits from platform-api and qtubuntu to land? Asking in relation to the pending unity-mir daily-releasing/autolanding ;)
[14:30] <didrocks> sil2100: there is no platform-api/qtubuntu changes I'm aware of TBH, do you see that some patches are needed for unity-mir?
[14:30] <didrocks> sil2100: we'll get:
[14:30] <didrocks> 1. have Mir in main
[14:30] <didrocks> (in progress)
[14:30] <didrocks> 2. xmir (xorg + patches) built against Mir
[14:31] <didrocks>    get mesa and driver patches in
[14:31] <didrocks> 3. get u-s-c fixing its test failing and go into distro
[14:31] <didrocks> I think as soon as 1 and 2, we'll be able to proceed in unity-mir
[14:31] <didrocks> does it make sense?
[14:32] <didrocks> seb128: in fact, for ubuntu-system-settings, I thought I pushed the "stop" buttons in jenkins (3 times actually)
[14:32] <didrocks> seb128: maybe I didn't push hard enough
[14:40] <sil2100> didrocks: makes sense! I just remember greyback mentioning that he needs some specific plaftorm-api and qtubuntu branches for it to build, or something
[14:41] <didrocks> sil2100: interesting, do you mind digging a little bit and writing that down?
[14:41] <sil2100> didrocks: so just give me a green light to proceed with unity-mir - the packaging is reviewed already and lintian clean
[14:41] <didrocks> great! ;)
[14:41] <didrocks> thanks sil2100
[14:42] <sil2100> didrocks: will do, I poked ricmm about that last week, but he also didn't know much about those, just that we're waiting for mir to get released - and Gerry wasn't around (like now!)
[14:42] <sil2100> But once he pops up again, I'll poke him what he meant with that
[15:15] <Laney> desrt: your new dbus-appinfo test hangs for me without an x server
[15:15] <desrt> i've heard rumours about this
[15:15] <desrt>  not sure what the issue is though... we're using dbus-testrunner, right?
[15:15] <Laney> p.s. hello!
[15:16] <desrt> hi :)
[15:17] <Laney> plain ol' make check
[15:18] <desrt> Laney: i can reproduce.  nice.
[15:18] <desrt> i wonder what's going on there
[15:18] <desrt> i bet it's some dbus-launch stupidity, like usual
[15:19] <desrt> [pid 29126] write(2, "Autolaunch error: X11 initialization failed.\n", 45) = 45
[15:19] <desrt> yup.
[15:19]  * desrt wonders why
[15:19] <Laney> yeah that's what tipped me off about the missing X
[15:21] <desrt> something very very stupid is happening here
[15:22] <desrt> i'll take a look while i'm on the plane :)
[15:23] <seb128> desrt, hey, when do you fly?
[15:23] <desrt> in ~6 hours
[15:23] <desrt> i should start packing :)
[15:26] <seb128> larsu, kenvandine, Laney: https://code.launchpad.net/~seb128/gsettings-qt/build-qmltypes-description/+merge/177626 ... warning, I don't really know what I'm doing, but it seems to work
[15:27] <larsu> what's a qmltypes?
[15:27] <Laney> I suggest you ask someone on the SDK team :P
[15:27] <kenvandine> :-p
[15:27]  * Laney knows nothing of this
[15:27] <Laney> crap
[15:27]  * Laney writes a status update
[15:28] <seb128> larsu, something qmlplugindump generates that describes your object apparently, seems needed for qtcreator to have a list of the properties/types/...
[15:28] <kenvandine> i can review that
[15:28] <seb128> larsu, that's needed for cpp plugins apparently
[15:28] <kenvandine> done those before :)
[15:28] <seb128> kenvandine, great, see review comments on the mp page ;-)
[15:29] <seb128> I'm sure there is a better way than the ld hack for the lib, but I can't figure it out, and I spent enough time on that
[15:30] <kenvandine> oh... you're creating it at build time
[15:30] <Laney> what do other packages do?
[15:30] <seb128> qengho, mlankhorst, Sweetshark, Laney, tkamppeter, attente, desrt, larsu: hey, it's meeting time
[15:30] <kenvandine> i think most people do it manually... which never seemed like a good idea
[15:30] <seb128> Laney, some ship a pregenerated copy, some build it at build time
[15:30]  * qengho dances.
[15:30]  * Sweetshark steps to the right ...
[15:30] <mlankhorst> g'day mate
[15:30]  * Sweetshark steps to the left ...
[15:30] <kenvandine> seb128, what does ubuntu-ui-toolkit do?
[15:31]  * Sweetshark hops around.
[15:31] <Sweetshark> meeting time?
[15:31] <seb128> kenvandine, let's move to #ubuntu-touch
[15:31] <seb128> Sweetshark, yes
[15:31] <seb128> let's get started
[15:31] <kenvandine> Sweetshark, you're in a good mood :)
[15:31] <seb128> qengho, hey
[15:31] <qengho> Yo.
[15:31] <qengho> * chromium-browser 28.0.1500.71 landed for stable.
[15:31] <qengho> * ... Building again for saucy-proposed, after 1) working around linker bug and 2) being killed in build-time tests by zealous timeout watchdog.
[15:31] <qengho> * Adding more build-time tests.
[15:31] <qengho> * Continuing work on integrating LP translations into chromium-browser.
[15:31] <qengho> EOL
[15:31] <Sweetshark> kenvandine: survived a LO release.
[15:31] <kenvandine> hehe
[15:31] <kenvandine> :)
[15:33] <seb128> qengho, did you get chrisccoulson to sponsor it for you?
[15:33] <qengho> seb128: yes.
[15:33] <seb128> qengho, chrisccoulson: it's not showing up on https://launchpad.net/ubuntu/+source/chromium-browser
[15:33] <seb128> ?
[15:33] <chrisccoulson> seb128, yes, it's on my list :)
[15:33] <chrisccoulson> (i've not forgotten about it ;) )
[15:33] <seb128> chrisccoulson, ok, so not done yet... when do you think you will have time for it?
[15:34] <chrisccoulson> seb128, i can probably do it in a few minutes
[15:34] <seb128> chrisccoulson, qengho: thanks
[15:34] <seb128> Sweetshark, hey
[15:35] <Sweetshark> 4.0.4 for raring pending (bug 1204449) -- pending bug 1196263 -- prepared at https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-precisetest-20120327/+sourcepub/3371647/+listing-archive-extra
[15:35] <ubot2`> Launchpad bug 1204449 in libreoffice (Ubuntu) "[SRU] LibreOffice 4.0.4 for Ubuntu 13.04 (raring)" [Undecided,Confirmed] https://launchpad.net/bugs/1204449
[15:35] <ubot2`> Launchpad bug 1196263 in libreoffice (Ubuntu) "Libre Office 4.0 Paper Tray" [Undecided,Incomplete] https://launchpad.net/bugs/1196263
[15:35] <Sweetshark> 3.5.7 for precise -- pending feedback on bug 1176923 -- prepared at https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-oneirictest-20110718/+sourcepub/3384413/+listing-archive-extra
[15:35] <Sweetshark> 4.1.0 final released -- first time we have PPA builds ready at the upstream announcement for Ubuntu+1 (saucy), Ubuntu current (13.04) and Ubuntu LTS (12.04) -- thanks to ricotz for the coordination to get the last two there just in time -- so far: >~31000 ppa downloads alone (plus upstream downloads) -- some more fixes: lintian foo
[15:35] <Sweetshark>  -- some more fixe: build against system lp-solve and graphite (see alaso: bug 1206107) -- synced from debian: fix uno paths -- bugwrangling/triaging/syncing of initial bug report influx -- both upstream and on lp
[15:35] <ubot2`> Launchpad bug 1206107 in libreoffice (Ubuntu) "LibreOffice should build against system lpsolve" [High,Fix committed] https://launchpad.net/bugs/1206107
[15:35] <Sweetshark> other bits: -- hunting/observing ppa stats -- seemed to me some additional ~8000 downloads on precise got lost in the count on Thursday (I have a script running there nowto see if it happens again)
[15:35] <Sweetshark> EOF
[15:36] <Sweetshark> whops, the copypasta didnt bring along the formatting.
[15:36] <seb128> Sweetshark, is bdrung doing sponsoring for you for those?
[15:37] <Sweetshark> seb128: bdrung had some early feedback over lintian nagginess. I fixed some already, most are bogus anyway.
[15:37] <seb128> ok
[15:37] <seb128> let me know if you need me to sponsor some of those
[15:37] <Sweetshark> seb128: k, will do
[15:37] <seb128> we should also discuss again adding you to -desktop at some point
[15:38] <Sweetshark> seb128: right
[15:38] <seb128> since the dbm seems set on the mindset that we don't need a libreoffice maintainer for Ubuntu
[15:38] <seb128> Sweetshark, thanks
[15:38] <seb128> ok, larsu is next since he has to run out soon
[15:38] <seb128> larsu, hey
[15:38] <larsu> seb128: thanks :)
[15:38] <larsu> - worked with dednick on unitymenumodel (he found some issues while using it)
[15:38] <larsu> - added phone menu to indicator-sound
[15:38] <larsu> eof
[15:38] <larsu> - ported ubiquity to the new indicator stack
[15:39] <seb128> - fixed gsettings-qt properties not updating correctly
[15:39] <larsu> oh, and I had a big discussion on icons in unity8
[15:39] <larsu> I think it's going in a good direction now :)
[15:39] <seb128> thanks for that one, and for the ubiquity fixing
[15:39] <seb128> great!
[15:39] <larsu> :)
[15:40] <seb128> larsu, quick q., do you know the status of the custom widgets for the indicators?
[15:40] <seb128> aka, are we going to get real indicators on unity8 soon?
[15:40] <larsu> seb128: yes, that's what I'm working on with dednick
[15:40] <larsu> seb128: well, he's doing all the unity8 work
[15:41] <larsu> seb128: as for specific menu items, please ask him on the status
[15:41] <seb128> larsu: ok, thanks
[15:41] <larsu> I have to run, sorry. bbl
[15:41] <seb128> mlankhorst, hey
[15:42] <mlankhorst> Today I pushed a new xserver to x-staging for testing touch bug, took a bit longer a test failed during build, both the code and test were wrong! Touch bug testing, fixing radeon/nouveau/generic upstream kernel bugs, and helping out with mir bugs. Seems I broke kernel compiling with llvm, ah well! And limited sports this week, until my bike's front wheel is replaced. Got upload rights to xorg packageset for debian now! :D I will probably tak
[15:42] <mlankhorst> \0
[15:42] <seb128> larsu, that's fine, we were done, have fun!
[15:42] <mlankhorst> touch bug can be workarounded afaict now
[15:42] <Laney> "probably tak"
[15:42] <Laney> got cut off
[15:42] <seb128> what Laney said
[15:42] <mlankhorst> >> I will probably take thursday off again as a holiday.
[15:43] <seb128> ok
[15:43] <seb128> mlankhorst, thanks
[15:43] <seb128> Laney, hey
[15:43] <Laney> • Fix libtimezonemap's -dev package to be usable on its own
[15:43] <Laney> • Various system-settings MPs: handle DBus activation correctly, use the cities list from libtimezonemap, use a thread to make the UI more responsive when doing this (discovered a possible QSortFilterProxyModel bug which needs investigating/filing and sapped quite some time), get connectivity from NM but possibly should be QNetworkInfo?
[15:43] <Laney> • Reviews, arguments about command line argument parsing
[15:43] <Laney> • Ask some questions about which APIs are available to do stuff, with the aim of getting more settings working
[15:43] <Laney> • Discussions about GStreamer packaging / including some non-upstream plugins. Agreement on using a PPA for now until there has been some upstream feedback/iterations (will need to build for armhf for touch I guess)
[15:43] <Laney> • Start packaging new glib, find a hang in the testsuite(!)
[15:44] <Laney> • Restore some lost packaging improvements to maliit (most importantly running the testsuite)
[15:44] <Laney> • Holiday next week then Debconf the week after during which I don't know how much I'll be around.
[15:44] <seb128> oh, holidays/debconf
[15:44] <seb128> have fun with those ;-)
[15:45] <mlankhorst> oh and new item -> testing touch bug without workaround, apt-get upgrade finished :P
[15:45] <Laney> surely will
[15:45] <Laney> hopefully will get to meet up with didrocks in his city :P
[15:45] <seb128> Laney, right, I didn't approve your connectivy through n-m work yet because it feels like that's something qt should provide in qtnetwork or something
[15:45] <seb128> kenvandine, do you know if qt has an api to query network status?
[15:45] <Laney> I didn't know about it
[15:46] <Laney> http://qt.developpez.com/doc/5.0-snapshot/qnetworkinfo/
[15:46] <Laney> I don't see something there which says "we have internet connectivity" though
[15:46] <seb128> that's qtsystems
[15:46] <seb128> which is modem stuff
[15:46] <Laney> it's what someone linked on the ML
[15:46] <seb128> I would expect qt to have more "normal network" stuff
[15:47] <seb128> anyway, not really a meeting topic
[15:47] <mlankhorst> oops, onboard back to crashing normally :P
[15:47] <seb128> we can discuss it on #ubuntu-touch or after the meeting
[15:47] <seb128> Laney, thanks
[15:47] <Laney> k
[15:47] <seb128> tkamppeter, hey
[15:47] <tkamppeter>  - Move upstream home of gstoraster (and gstopxl) from ghostscript to cupsfilters
[15:47] <tkamppeter>  - Several tests for X bugs on Lenovo Thinkpad Twist
[15:47] <tkamppeter>  - cups-filters: gstoraster and pdftoraster are ready for PPD-less printing
[15:47] <tkamppeter>  - GSoC mentoring
[15:47] <tkamppeter>  - Bugs
[15:48] <kenvandine> seb128, i don't know
[15:48] <seb128> tkamppeter, thanks
[15:48] <seb128> attente, hey
[15:48] <attente> seb128, hi
[15:48] <attente> device language switching, waiting for polkit working on device
[15:48] <attente> accountsservice input source support proposed upstream, testing a patched gnome-settings-daemon locally for synching input sources
[15:48] <attente> eof
[15:48] <attente> refactoring some of indicator-keyboard for greeter work
[15:49]  * desrt thinks attente doesn't know what means 'eof' ;)
[15:49] <seb128> attente, on the good news, ibus 1.5 is in saucy and indicator-keyboard landed in NEW (I'm going to review it after the meeting)
[15:49] <attente> seb128, great, thanks!
[15:49] <seb128> attente, good work on getting the system settings panel in as well ;-)
[15:49] <attente> desrt, what do you mean?
[15:49] <jbicha> desrt: or larsu
[15:50] <seb128> attente, you wrote one line after eof I think
[15:50] <seb128> attente, re what desrt means ;-)
[15:50] <attente> sounds racy :P
[15:51] <seb128> attente, jbicha: I lost a bit track, but once indicator-keyboard is in/promoted we should be able to land g-s-d/g-c-c right?
[15:52] <jbicha> seb128: yes
[15:52] <seb128> great
[15:52] <seb128> attente, thanks
[15:52] <seb128> desrt, hey
[15:52] <desrt> seb128: hi!
[15:52] <desrt> got on a bit of a yakshave last week from the desktop file index stuff
[15:53] <desrt> ended up fixing a lot of things with the filemonitor implementation in GIO
[15:53] <jbicha> seb128: and Unity or something needs to depend on indicator-keyboard
[15:53] <desrt> added a new internal API so that we can actually use file monitors from inside of glib (without assuming a mainloop is running) which will allow us to have much better handling for stuff like /etc/mtab /etc/fstab /etc/localtime ~/.hidden files, as well as changes in desktop files (which was my real goal there)
[15:54] <desrt> because of this we can now keep track of what is in the desktop file dirs instead of rescanning it all of the time, which is a big performance gain for just about all desktop file operations
[15:55] <desrt> i started integrating the desktop file index stuff on top of that work, finding a few bugs in the process.... and now on a branch, we have an experimental g_desktop_app_info_search() API... and it's fast.... like 50µs per search kinda fast
[15:55] <desrt> i did a lot of small bugfixing and reviewing... including for larsu's multi-name-watching dbus patch (for mpris for the sound indicator)
[15:56] <desrt> got in a fight about how and if to store keyboard layouts in the accounts service ... hopefully we can push that in the right direction, since the GNOME approach now is just totally wrong (going to talk to rui about it at guadec)
[15:56] <desrt> tracked down some dconf writes happening at login upstream and talked to colin about the possibility of setting up an ostree smoketest for that
[15:56] <desrt> and also created an API for measuring the disk usage of a directory recursively (basically 'du' for GFile)
[15:57] <desrt> also (as a btw) that patch that tedg needed for the annotations made it into yesterday's glib release, so you need only to rebuild gobject-introspection and everything should be OK
[15:57] <seb128> great
[15:57] <desrt> eof
[15:57] <seb128> we backported the vapi fix meanwhile, so no hurry
[15:57] <tedg> I think that vala has to rerelease as well.
[15:57] <seb128> "backported"/"hacked"
[15:58] <desrt> ah.  it was vala?
[15:58] <tedg> I think they build the vapi files at release time.
[15:58] <desrt> ya... i guess vala will need to do a new release then :)
[15:58] <seb128> desrt, thanks for the "du" api, going to make my life easier ;-)
[15:58] <tedg> It's a long chain for one comment ;-)
[15:58] <Laney> more GLib in system-settings? :P
[15:58] <desrt> seb128: hope to get it reviewed at guadec by alex
[15:58] <seb128> desrt, the .desktop stuff is pretty cool as well!
[15:58] <desrt> actually, a lot of the stuff i'm doing needs alex to look at it and he's on vacation lately
[15:58] <desrt> but he'll be at guadec, so i'll try to catch him :)
[15:58] <seb128> desrt, have fun at GUADEC ;-)
[15:58] <seb128> desrt, thanks
[15:59] <desrt> i'm leaving today, btw... and will be on a plane in about 3 hours
[15:59] <desrt> (well... going to the airport in 3 anyway)
[15:59] <desrt> (eof)
[15:59] <seb128> have a safe trip!
[15:59] <seb128> ok, my turn
[16:00] <seb128> * ubuntu-system-settings work mostly again this week:
[16:00] <seb128> - storage: started using gsettings to store the sort order preference
[16:00] <seb128> - sound: updated to reflect design changes, started using gsettings for preferences
[16:00] <seb128> - phone: started on the phone preferences work
[16:00] <seb128> - about: sorted out how to get the current update date on the touch image,
[16:00] <seb128> updated the code to read the real timestamp and display it
[16:00] <seb128> - quite some reviews for others
[16:00] <seb128> - security-privacy: added the preference to disable online dash queries
[16:00] <seb128> - some other bug fixes and UI tweaks
[16:00] <seb128> * looked at the phone-app, submitted a merge request to read the ringtone sounds from gsettings
[16:00] <seb128> * worked a bit on teached GSettings to qtcreator, learn a bit about qmltypes on the way, submitted a merge proposal that seems to make the thing work
[16:00] <seb128> * uploaded the new poppler to saucy, started on the transition
[16:00] <seb128> * some packaging/NEW reviews and sponsoring

[16:01]  * sil2100 waits :)
[16:01] <seb128>
[16:01] <seb128> no didrocks, sil2100 is going to lead the second half of the meeting ... any question before we and him the channel?
[16:01] <Mirv> \o
[16:01] <seb128> sil2100, thanks for stepping up while didrocks is slacking in meetings ;-)
[16:01] <kenvandine> wb Mirv!
[16:01] <sil2100> ;) np!
[16:02] <sil2100> Mirv, kenvandine, cyphermox, robru, didrocks: hi guys! How are you?
[16:02] <didrocks> sil2100: sleeping even
[16:02] <didrocks> seb128: ^ :)
[16:02] <seb128> didrocks, ;-)
[16:02]  * didrocks goes back to the swimming pool
[16:02] <Mirv> hi all
[16:02] <seb128> tssss
[16:02] <sil2100> As mentioned by seb128, I have been asked to lead the meeting today
[16:02] <sil2100> I see robru is not around today, maybe he'll join later on
[16:02] <Mirv> and thanks kenvandine
[16:03] <sil2100> Everyone here? (not counting didrocks who just goes out to swim)
[16:03] <sil2100> I guess we'll have a 100% proper meeting next week, but let's maybe do at least a quick status update from everyone and browsing through the spreadsheet
[16:04] <sil2100> Remember to write down the current tasks you are working on there so we can keep track of what's going on!
[16:04] <sil2100> Mirv: how's the status with Qt5, 5.1 etc. after you got back?
[16:05] <sil2100> Mirv: could you start with the status update?
[16:05] <Mirv> sil2100: mostly fine, not much happened while I was away but ken updated Qt Creator. now there are new things queueing up like yet another qtpim update needed and qtconnectivity wanted for archives
[16:05] <Mirv> and I'm working on getting u1db-qt into archives right now
[16:05] <sil2100> Mirv: all written down in the spreadsheet and monitored? ;)
[16:06] <sil2100> Great, thanks!
[16:06] <Mirv> sil2100: not everything, there are so many little things I do anyhow
[16:06] <Mirv> but anything that I'm not doing right away or is bigger is there
[16:06] <sil2100> Mirv: I guess it doesn't make sense to write down those tiny tasks indeed, so good
[16:06] <Mirv> the tests running thing is not even assigned, I guess my name should be there
[16:07] <Mirv> sil2100: yeah I've my own todo list and also report to the SDK team, there are many lists around :)
[16:07] <sil2100> Done ;)
[16:07] <sil2100> Ok, cool
[16:07] <Mirv> I've just no idea initially how much work are those, but anyway since they're in main, tests should be run
[16:07] <Mirv> that's it for me, back from vacation most of all!
[16:07] <sil2100> \o/ Glad to have you back
[16:08] <sil2100> Now, following along... kenvandine!
[16:08] <sil2100> kenvandine: you and cyphermox are the two people I don't see much in the spreadsheet ;) What are you working on right now and how's it proceeding?
[16:08] <kenvandine> system-settings right now
[16:09] <kenvandine> and planning for share service, which apparently might be getting scheduled
[16:09] <kenvandine> and just daily keeping the stacks building :)
[16:09] <sil2100> Good ;) Last week I noticed gsettings-ubuntu-touch-schemas got preNEWed and released
[16:09] <kenvandine> that's it for me
[16:10] <sil2100> kenvandine: thanks! If you can, try writing down the bigger tasks that are under works in the spreadsheet, this way we know what's going on instantly as well
[16:10] <sil2100> cyphermox: hi! Are you around?
[16:11] <kenvandine> not currently working on anything specific to PS integration
[16:11] <sil2100> Ok
[16:11] <sil2100> I guess cyphermox is not around as well, we'll catch him next week about the status update then, along with robru
[16:12] <sil2100> So now for me
[16:13] <sil2100> For most of the time I'm working on keeping the stacks up and running, making sure that most of the things get released before noon
[16:14] <kenvandine> robru is on his way to guadec
[16:14] <sil2100> kenvandine: yes, Didier reminded me about that as well ;)
[16:14] <sil2100> Anyway, last week we finally essentially unblocked the unity stack, now it's daily releasing again properly
[16:15] <sil2100> There have been some problems with the test machines, but those got resolved one way or another
[16:15] <Mirv> sil2100: what was blocking it for so long btw?
[16:15] <sil2100> Mirv: many many things, I think we already had a chat about that during the last meeting during your holiday, but in short: outdated tests, dbus issues, recordmydesktop OOM problems
[16:16] <sil2100> ;)
[16:16] <Mirv> yes, during that :) ok, thanks, just interested
[16:16] <sil2100> We're daily releasing unity8 now as well
[16:16] <sil2100> Besides that, I'm helping out some of our projects to get into Ubuntu universe, like lucene++ and such
[16:17] <sil2100> Cleaning up packaging and between package building, working on the Qt5 proper QPA appmenu support, since it's finally time for that
[16:17] <Mirv> I noticed ont thing missing today when getting Qt 5.1 / Unity8 working on device - unity-api isn't in archives
[16:18] <sil2100> hm, right
[16:18] <Mirv> if it's not yet on our radar, it should be
[16:18] <sil2100> Mirv: the reason for that is that we're basically daily-releasing to a PPA right now
[16:19] <sil2100> Mirv: since we don't think it's 'there' yet
[16:19] <sil2100> Mirv: so right now it's anyway recommended just to use the ubuntu-unity/next PPA for those things
[16:19] <Mirv> ok, there could be a spreadsheet about those in radar but not yet packages
[16:20] <sil2100> Also, this week I'll be working with andyrock to get a newer compiz tested and into saucy
[16:20] <sil2100> Mirv: I guess that might make sense
[16:21] <sil2100> Ok, I think that's it for the status updates
[16:21] <sil2100> Mirv, kenvandine, cyphermox: let's take a look at the spreadsheet again and try to find some additional tasks that already got finished
[16:21] <sil2100> You guys see anything, or is it more or less up-to-date?
[16:22] <sil2100> Mirv: about the XIM support thing - we're still blocked on SRU team decision
[16:22] <sil2100> Mirv: they wanted the bug descriptions made with the rationale, I did that and informed them
[16:22] <kenvandine> not me
[16:22] <sil2100> So until we get any feedback, not sure if we should do anything else
[16:22] <Mirv> sil2100: yes, thanks for the e-mail CC:ing
[16:23] <sil2100> Ok then, archiving the tasks then!
[16:23] <Mirv> the sheet seems uptodate
[16:23] <sil2100> Pressing \o/
[16:23] <sil2100> Done
[16:23] <sil2100> Ok then, I think we can finish this pseudo-weekly-meeting
[16:24] <sil2100> cyphermox: would be nice if you could pop up on those
[16:24] <sil2100> Mirv, cyphermox, kenvandine, didrocks: thanks guys! See you later o/
[16:24] <Mirv> thanks, bye!
[16:24] <seb128> sil2100, thanks
[16:24] <Laney> he's on holiday
[16:24] <kenvandine> later!
[16:25] <sil2100> Oh, I wasn't aware of that
[16:25] <seb128> kenvandine, sil2100: do you know about indicators-client?
[16:25] <sil2100> seb128: what do you have in mind?
[16:25] <seb128> sil2100, the current version is stucked in saucy-proposed because the -examples binary depends on phone-app which is not in saucy
[16:26] <seb128> sil2100, I was wondering if there is any plan to fix that
[16:26] <seb128> e.g britney blocks it to enter the archive because of the broken depends
[16:26] <kenvandine> i don't know
[16:26] <seb128> maybe dropping the examples binary would make sense?
[16:26] <sil2100> Uh
[16:26] <sil2100> seb128: in this case, I guess that's the right thing to do - thanks for bringing that up
[16:26] <kenvandine> larsu might know
[16:27] <seb128> sil2100, yw
[16:42] <seb128> tkamppeter, could you have a look at making cups-filters build with the new poppler that is in saucy-proposed?
[16:45] <tkamppeter> seb128, OK, will do.
[16:45]  * Laney looks at a couple of poppler packages
[16:45] <Laney> pdf2djvu pdftoipe
[16:46] <seb128> tkamppeter, thanks
[16:46] <seb128> Laney, pdftoipe already uploaded
[16:46] <Laney> k
[16:46] <Laney> guessing it was no-change then :P
[16:46] <seb128> yeah
[16:46] <Laney> did you get all of those ones?
[16:47] <seb128> Laney, no, I just did gnome-commander and inkscape is building
[16:47] <Laney> k
[16:47] <Laney> building texlive-binaries
[16:47] <seb128> what wants to do libreoffice? :p
[16:48] <Laney> /part
[16:48] <seb128> ;-)
[17:04]  * seb128 grrrs at packages that need build-depends to be source built
[17:04] <Laney> -nc?
[17:05] <seb128> Laney, I had forgotten about that, didn't use it in ages ... thanks ;-)
[17:06] <Laney> good trick for these situations
[17:06] <seb128> it's a cdbs package which was complaining about /usr/share/cdbs/1/class/gnumakefile.mk missing
[17:06] <seb128> (popplerkit.framework)
[17:09] <seb128> Laney, ok, I uploaded gnome-commander and popplerkit.framework and I'm still building inkscape, and I'm done for a while, going to review indicator-keyboard and do some email catchup before dinner then
[17:09] <Laney> doing gambas3 calligra
[17:09] <seb128> Laney, so feel free to tackle anything else in the poppler rdepends
[17:09] <Laney> both pretty huge builds
[17:09] <seb128> great
[17:09] <Laney> otherwise not really here any more, so see you tomorrow ;-)
[17:09] <seb128> Laney, you are warming up before tackling libreoffice? ;-)
[17:09] <Laney> maybe Sweetshark can do a no-change rebuild of that overnight :P
[17:13] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/with_ofono_serviceNumbers/+merge/177652
[17:13] <kenvandine> seb128, ^^
[17:13] <seb128> kenvandine, nice, reviewing that in a bit (once I'm done with the NEW reviews I just started)
[17:14] <kenvandine> thanks
[17:14] <kenvandine> it almost all works on my device :)
[17:14] <kenvandine> the presenceChanged signal isn't emitted
[17:14] <kenvandine> but that is from ofono's side
[17:15] <kenvandine> i have to restart my phone to get it to detect the SIM
[17:25] <seb128> attente, still there?
[17:25] <seb128> attente, I'm looking at indicator-keyboard in NEW and I've some questions
[17:26] <seb128> attente, what's that deps directory with documentation/html files for e.g gnome-desktop ... is that to generate the vapis? can't we have those provided by the libs/vala instead?
[17:31]  * desrt attempts to recalibrate his brain to czech money
[17:31] <desrt> hm... has gone from 15:1 to more like 20:1
[17:32] <desrt> easier conversions!
[17:32] <attente> seb128, yeah, those are just to provide the vapi
[17:32] <attente> seb128, how did you want to provide them?
[17:33] <seb128> attente, I've no strong opinion, I'm fine with the current way ... I'm just asking to understand the situation
[17:34] <seb128> attente, do you know if there is any reason vala doesn't/couldn't ship the vapi for gnome-desktop?
[17:36] <seb128> desrt, attente: you guys seem to pong at the same time, are you hanging out at the airport? ;-)
[17:36] <seb128> attente, are you going to GUADEC btw?
[17:37] <desrt> seb128: nope.  still at home.
[17:37] <attente> seb128, i don't know why the vapi isn't included
[17:37] <attente> seb128, not going to GUADEC unfortunately...
[17:37] <seb128> attente, @vapi: ok, no worry
[17:38] <seb128> attente, @GUADEC: :-(
[17:38] <jbicha> seb128: it looks like gnome-desktop 2's vapi is included https://git.gnome.org/browse/vala/tree/vapi
[17:38] <seb128> jbicha, that's the old version?
[17:38]  * seb128 gets confused by the gnome-desktop versions
[17:39] <seb128> we are at 3 right?
[17:39] <jbicha> yes, it's gtk2 https://git.gnome.org/browse/vala/tree/vapi/gnome-desktop-2.0.deps
[17:39] <attente> yes, we're on gnome-desktop 3
[17:41] <seb128> attente, did you copy that deps/ directory from somewhere or just built it up to get the vapis you needed?
[17:42] <attente> i just built them
[17:43] <seb128> attente, ok, seems alright ... some days I wonder if by using vala we don't spent as much effort with those issues than you spare by using vala over C though ;-)
[17:44] <sarnold> replace vala by $language and I've thought that thought hundreds of times...
[17:44] <attente> seb128, i wonder that too sometimes, but i think we gained by using vala in this case
[17:45] <asac> seb128: everything is broken on desktop now :/ ... corruption, no suspend on lid, now bluetooth is not working anymore ... :(
[17:45] <seb128> sarnold, hey, how are you?
[17:45] <asac> can we revert everything? :)
[17:45] <asac> everything that was done in last week i guess
[17:45] <seb128> asac, desktop didn't change, blame the kernel team?
[17:46] <sarnold> seb128: pretty good, thanks, you? :)
[17:46] <seb128> asac, we are busy on touch settings, we barely do desktop work this cycle
[17:46] <asac> seb128: you didnt upload anything in last week?
[17:46] <seb128> sarnold, I'm good thanks
[17:46] <asac> seb128: ok so no new stuff from gnome at all?
[17:46] <asac> then i will search for others to blame :)
[17:46] <seb128> asac, not that I can think about no
[17:46] <asac> guess foundations and kernel
[17:46] <seb128> kernel would be my guess
[17:46] <seb128> they had a few breakages recently
[17:46]  * asac needs to make a phone call :/
[17:46] <asac> ok let me reboot with old kernel
[17:47] <asac> libusbx and stuff have killed the power/lid stuff afaik
[17:47] <asac> :)
[17:47] <seb128> sarnold, since you spoke here, I'm going to corner you  about https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1186553 ;-)
[17:47] <ubot2`> Ubuntu bug 1186553 in libwebp (Ubuntu) "[MIR] libwebp" [Undecided,New]
[17:47] <seb128> sarnold, do you have any ETA on the review?
[17:47] <sarnold> seb128: in progress now :)
[17:47] <asac> ok ttyt
[17:47] <seb128> asac, that's true about libusbx
[17:47] <stgraber> I've had to kill upower everytime I want to suspend as it seems stuck and that's preventing the suspend on closed lid here. Killing it and calling upower -d respawns it, then everything works.
[17:47] <seb128> asac, that's a direct sync from debian though
[17:47]  * stgraber blames pitti
[17:48] <seb128> stgraber, blame debian and aurel32
[17:48] <stgraber> seb128: TIL for upower is pitti
[17:49] <stgraber> (or my system is out of date, which is quite likely considering I'm on vacation in the middle of nowhere with a rather bumpy internet)
[17:49] <seb128> stgraber, that's likely the libusbx issue we just mentioned
[17:50] <stgraber> do I even want to know how libusb is related to suspend on closed lid? (and knowing I have no USB device connected on that system) ;)
[17:52] <jbicha> http://packages.qa.debian.org/libu/libusbx/news/20130730T171814Z.html
[17:53] <seb128> stgraber, upower uses libusbx which has a lock and block upowerd
[17:54] <seb128> jbicha, thanks, syncing that
[17:54] <seb128> it was just uploaded it seems
[17:54] <seb128> waiting for it to hit the mirror
[17:54] <seb128> stgraber, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717988
[17:54] <ubot2`> Debian bug 717988 in libusb-1.0-0 "libusb-1.0-0: upowerd deadlocks in libusb (maybe related to suspend/resume)" [Important,Fixed]
[17:57] <didrocks> seb128: do you have a minute for https://code.launchpad.net/~didrocks/ubuntu-system-settings/fix-typos/+merge/177660
[17:57] <didrocks> seb128: seems an easy one ;)
[17:58] <seb128> didrocks, not sure I want to make Steve and Loic happy :/
[17:59] <seb128> didrocks, ok, approved ;-)
[18:00] <didrocks> seb128: sorry, was disconnected
[18:01] <didrocks> seb128: thanks! it's a surprise for him ;)
[18:01] <didrocks> I hope in beers as well :)
[18:02] <seb128> ;-)
[18:03] <seb128> on that note diner time
[18:03] <seb128> didrocks, have a good evening if you are off by the time I'm back (I'm going to read scrollback before calling it a day, so if you need anything just ask there on in query)
[18:03] <seb128> bbl
[18:03] <didrocks> seb128: thanks! enjoy your dinner ;)
[18:04] <didrocks> seb128: FYI, I'll just relaunch a landing for u-s-s
[18:04] <didrocks> so that we are cleaned for tomorrow
[18:27] <bschaefer> seb128, ping
[18:36] <seb128> bschaefer, hey
[18:37] <bschaefer> seb128, hey! Soo I had a question about keyboard layouts and ibus 1.5 :)
[18:37] <bschaefer> seb128, as I just noticed, if you change the keyboard layout to say greek
[18:37] <seb128> bschaefer, I'm probably not the best one to ask but ask away, if I don't know I can redirect you to attente or jbicha who might know ;-)
[18:38] <bschaefer> ibus 1.5 wont update and is still in english, making keyboard layout kind of useless, as you need to change it in ibus 1.5 now
[18:38] <bschaefer> err in ibus-setup
[18:38] <bschaefer> seb128, well, hopefully they will see this
[18:39] <bschaefer> since ibus is always on
[18:39] <seb128> bschaefer, how do you change the layout?
[18:39] <bschaefer> seb128, non ibus way, System Settings -> Keyboard -> Keyboard layout
[18:39] <bschaefer> and add greek, and move it to the top of the list
[18:39] <seb128> bschaefer, in current saucy? or using the ubuntu-desktop ppa versions?
[18:40] <bschaefer> seb128, i just purged that ppa, and im using current saucy
[18:40] <bschaefer> cause ibus 1.5 made it in right?
[18:40] <seb128> yeah, g-s-d/g-c-c didn't land yet
[18:40] <bschaefer> seb128, ooo, i see, cause when I was using the ppa keyboard layout was crashing on me...
[18:40] <seb128> so the configuration ui/indicator might be buggy still
[18:40] <seb128> hum
[18:41] <seb128> that's worth a bug report, we should know about those before uploading
[18:41]  * bschaefer has to many ppas installed though
[18:41] <bschaefer> seb128, right...sorry!
[18:41] <seb128> no worry
[18:41]  * bschaefer installs ppa and files bug
[18:41] <attente> did you get a bt, bschaefer?
[18:41] <bschaefer> attente, not yet, im going after one now
[18:41] <seb128> but yeah, I can imagine things are not so coherent until the new configuration UI lands
[18:42] <seb128> since the gsettings keys used for config changed
[18:42] <bschaefer> right, and now ibus 1.5 uses gsettings, im just hoping that ibus is taking that into consideration
[18:42] <jbicha> yeah, ideally ibus 1.5 wouldn't have landed until indicator-keyboard did too
[18:42] <jbicha> hopefully it'll all get straightened out before the week is over though
[18:43] <bschaefer> cool, it seems hard to get everything to land at the right time :)
[18:51] <bschaefer> attente, would you happen to know how run keyboard layout through gdb?
[18:51] <bschaefer> as apport isn't picking it up...
[18:51] <seb128> attente, could you add standard license/copyright headers to indicator-keyboard and make the sources GPL3 in the header (standard Canonical licenses for indicators)?
[18:52] <attente> bschaefer, i'm not sure what that is, let me downgrade to check
[18:52] <bschaefer> attente, thanks, Ill look some more, but it doesn't seem to be a nicly name binary for me...
[18:52] <bschaefer> nicely*
[18:53] <seb128> didrocks, mterry: can you review https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1205995 when you have some spare cycles?
[18:53] <ubot2`> Ubuntu bug 1205995 in indicator-keyboard (Ubuntu) "[MIR] indicator-keyboard" [Undecided,New]
[18:53] <bschaefer> attente, is it: gkbd-keyboard-display?
[18:54] <seb128> bschaefer, that binary is a libgnomekbd one to display maps of the keyboard layout I think
[18:54] <bschaefer> seb128, cool thanks
[18:54] <seb128> bschaefer, what process is hiting the segfault?
[18:54] <bschaefer> seb128, well when I open up keyboard then click Keyboard Layout
[18:54] <bschaefer> and gkbd-keyboard-display is giving me an error on:
[18:54] <seb128> oh
[18:54] <attente> bschaefer, yeah, that's the one
[18:54] <bschaefer> (gkbd-keyboard-display:26864): GnomeKbdIndicator-CRITICAL **: Either layout or group have to be specified
[18:54] <mterry> seb128, yes, was going to wait til it hit the archive, as I saw test failures in pbuilder and wanted to see if it was just me
[18:54] <bschaefer> attente, no stack trace, just this error
[18:55] <seb128> mterry, it's in the queue, which means it went through daily build in ppa etc
[18:55] <seb128> mterry, if that's of any help for you
[18:55] <mterry> hm
[18:55] <bschaefer> attente, do you want me to file a bug?
[18:56] <attente> bschaefer, you can, but that panel should be gone when the new g-c-c lands
[18:56] <seb128> bschaefer, attente: that means "don't bother"
[18:56] <bschaefer> attente, well, I can wait a bit until the new g-c-c lands
[18:56] <bschaefer> :)
[18:56] <attente> lol
[18:56] <seb128> bschaefer, I would suggest you try to ubuntu-desktop ppa to get the full updates or wait a few days
[18:56] <seb128> intermediate state is not going to be worth spending efforts on
[18:56] <bschaefer> seb128, im back on the ubuntu-desktop ppa
[18:57] <seb128> the new g-c-c is in the ppa
[18:57] <bschaefer> seb128, attente well im getting this error in the new g-c-c ... unless its using the old one with new packages?
[18:57] <seb128> bschaefer, dpkg -l | grep gnome-control-center
[18:57] <bschaefer> ii  gnome-control-center                         1:3.6.3-0ubuntu31~ppa1                                 i386         utilities to configure the GNOME desktop
[18:58] <bschaefer> seb128, hmm strange when I start it from terminal keyboard layout works
[18:58] <seb128> yeah, that's the ppa version
[18:58] <seb128> hum
[18:58] <bschaefer> seb128, but when I go to system setting it fails
[18:58] <jbicha> bschaefer: I assume you manually installed indicator-keyboard?
[18:58] <seb128> bschaefer, talk to attente ;-)
[18:58] <bschaefer> jbicha, nope, just with the ppa, I also don't see a keyboard indicator
[18:59] <attente> bschaefer, we don't have a depends on indicator-keyboard yet
[18:59] <seb128> bschaefer, is indicator-keyboard installed?
[18:59]  * bschaefer checks
[18:59] <bschaefer> hmm no
[18:59] <seb128> attente, did you see my license comment earlier?
[18:59] <attente> seb128, yes, fixing
[19:00] <seb128> thanks
[19:00] <bschaefer> attente, but why would keyboard layout work when opening g-c-c through terminal and crash through system settings?
[19:00] <bschaefer> attente, well...installing that indicator fixed it?
[19:00] <bschaefer> attente, nevermind :)
[19:01] <attente> bschaefer, i don't think it's a gkbd-keyboard-display issue
[19:02] <attente> the bt shows a NULL widget size allocation
[19:02] <bschaefer> attente, yeah, its working now, so it must have been missing some info
[19:02] <attente> :S
[19:02] <bschaefer> :), thanks!
[19:03] <jbicha> bschaefer: there's some weird issue where XDG_CURRENT_DESKTOP isn't always set right in the terminal
[19:03]  * bschaefer doesn't have it set in his terminal
[19:03] <jbicha> I don't know if that's upstart or what that's responsible
[19:04] <Laney> yes there is/was a race there
[19:04] <bschaefer> o interesting!
[19:04] <Laney> i haven't seen it for a while though
[19:04] <jbicha> it's bad because there are quite a few patches that assume that XDG_CURRENT_DESKTOP is right and adjusts behavior for Unity because of it
[19:42] <seb128> chrisccoulson, thanks for sponsoring chromium-browser
[19:47] <mterry> seb128, jbicha: indicator-keyboard needs a bug sponsor
[19:47] <mterry> *subscriber
[19:47] <seb128> mterry, sponsor = subscriber?
[19:47] <mterry> seb128, yar, corrected myself above
[19:48] <seb128> mterry, sorry, I was typing slower than you :p
[19:48] <seb128> mterry, sure, I can do that once the package is in the archive
[19:48] <mterry> seb128, it has an archive page already, because it's in a PPA
[19:49] <seb128> mterry, oh, nice, let me subscribe the desktop bugs team to it
[19:49] <seb128> mterry, done
[19:49] <mterry> thanks!
[19:50] <mterry> seb128, oh, sorry.  A team subscriber preferably.
[19:50] <seb128> mterry, refresh, I got confused by the launchpad ui
[19:50] <mterry> seb128, new requirement for MIRs, since we have so many packages in main without teams looking after their bugs
[19:51] <mterry> seb128, yup, I see now.  Thanks  :)
[19:51] <seb128> mterry, yeah, I understand the requirement, it somewhat assume that teams keep up with/read their bugs emails, but that's not a discussion for today ;-)
[19:51] <mterry> seb128, one battle at a time
[19:51] <seb128> yeah
[19:52] <jbicha> maybe ~indicator-applet-developers should be subscribed too
[19:53] <seb128> mterry, I think the requirement is good in principle, even if teams don't keep up, that's holding some ground ... if we dropped on that requirement we would be arguing over the next one in the line soon
[19:54] <seb128> jbicha, good point
[19:54] <seb128> tedg, ^ can you subscribe the indicator dev team to https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+subscriptions ?
[19:55] <tedg> seb128, done
[19:55] <seb128> tedg, thanks
[20:20] <mterry> jbicha, seb128: LP isn't letting me leave a comment on the Ubuntu MIR for indicator-keyboard, because it's not in Ubuntu yet...  Anyway, here is one comment:   The deps/ directory worries me, from the perspective of having to keep them in sync with upstream changes.  There are several vapi files in deps/ that aren't used (libxklavier) and some that are already available on disk elsewhere (libbamf3).  Can that be cleaned up?  Do we need any of
[20:20] <mterry>  the vapi files in the deps folder?
[20:22] <seb128> mterry, weird for the comment
[20:22] <seb128> mterry, I'm a bit concerned about the vapi stuff, I asked attente about it earlier
[20:22] <seb128> we should probably clean that yeah
[20:22] <attente> mterry, we are using the libxklavier.vapi
[20:23] <seb128> attente, what are we using libxklavier/libgnomekbd for (I think GNOME deprecated those, what are they using instead)?
[20:24] <attente> just for stitching together the display name of the keyboard layout (language + country)
[20:26] <seb128> those libs are there and we can use them
[20:26] <seb128> but it might make sense to try to drop them at some point
[20:26] <seb128> otherwise we are going to end up maintaining them
[20:26] <attente> yeah, makes sense
[20:26] <seb128> they might be pretty stable/bug free, in which case it's ok
[20:27] <seb128> but still would be better to use maintained things
[20:27] <attente> there must be some alternative way to get those names
[20:27] <mterry> attente, I see libxklavier.pc being used, but not the vapi
[20:28] <attente> in lib/main.vala, anything referring to the Xkl namespace is using that vapi
[20:29] <mterry> attente, hmm...  how does it get pulled in?  I don't see any --pkg libxklavier or see it in any .deps files
[20:30] <mterry> The documentation in deps/ is also kind of odd
[20:30] <mterry> Not sure why that's in-tree
[20:31] <attente> hmm.. you might be right about that.. i only see --pkg Xkl-1.0
[20:32] <attente> i wonder if it's going straight for the gir for that
[20:32] <jbicha> attente: perhaps https://developer.gnome.org/gnome-desktop3/stable/gnome-desktop3-Language-Utilities.html
[20:33] <attente> mterry, sorry, you're right, it doesn't need that vapi at all
[20:34] <mterry> attente, there is an Xkl metadata file..  Does that work in concert with the gir?  I'm not used to metadata files
[20:36] <attente> yes, the metadata file is just there to tweak annotations in the gir when producing the vapi
[20:36] <attente> it seems like only the metadata file is necessary though
[20:37] <attente> and the system gir i guess
[20:37] <attente> i'll remove it
[20:53] <Laney> *another* u-s-s!
[20:55] <seb128> Laney, yeah, people in IoM want to get a demo, build from the archive, of system updates
[20:55] <seb128> blame slangasek!
[20:56] <Laney> this late and with only typo fixes? :P
[20:58] <seb128> Laney, it could be that didrocks was overzealous on the typo fix, though it was a 1 unit error, e.g Mb -> Gb
[20:58] <seb128> which makes a difference on your 3G data plan, if that's the deciding factor to click "download" :p
[21:28] <seb128> Laney, I wonder why poppler has that number of items listed on update_output.txt
[21:29] <seb128> like wth is cups listed
[21:30] <Laney> recursive rdeps i guess
[21:31] <seb128> through which one?
[21:31] <seb128> I though most were due to tex stuff
[21:31] <seb128> but you rebuilt that
[21:32] <Laney> Try apt-get install package libpoppler37- in a chroot with saucy-proposed
[21:32] <Laney>  cups : Depends: cups-filters (>= 1.0.24-3~) but it is not going to be installed
[21:32] <seb128> oh ok
[21:32] <seb128> damn, it's not my day for apt tricks
[21:32] <seb128> I tried -libpoppler37
[21:33] <seb128> not libpoppler37-
[21:33] <seb128> Laney, thanks ;-)
[21:33] <Laney> :P
[21:33] <Laney> and on that bit of wizardry, goodnight!
[21:33] <seb128> Laney, 'night!