=== Sarvatt is now known as Sarvatt_ === thumper is now known as thumper-afk [04:20] Good morning [04:51] pitti: Hey, I'm testing colord 1.0.1. Does adt [04:51] pitti: Hey, I'm testing colord 1.0.1. Does adt-run-test support Restrictions: build-needed? Because it seems to not be doing that. [04:54] hey RAOF [04:55] RAOF: it does, but ATM it does it wrongly, see debian bug 711209 [04:55] Debian bug 711209 in autopkgtest "autopkgtest: build-needed restriction doesn't actually run tests in built tree" [Normal,Open] http://bugs.debian.org/711209 [04:55] RAOF: that bites me in umockdev as well, so today I'll look for a workaround [04:55] RAOF: or rather, fix that in adt-run [05:07] pitti: So, with that caveat, you may enjoy the debian/1.0.1-1 tag in colord's collab-maint git repository. [05:07] RAOF: yay [05:08] * pitti checks whether the keyring update in Debian has happened by now [05:08] RAOF: ah, seems it didn't yet, so I can't upload yet [05:09] Heh. Fair 'nuff. [07:04] good morning [07:09] salut jibel, ça va? [07:12] salut didrocks , bien et toi? [07:14] bonjour didrocks [07:15] bonjour pitti, ça va? [07:15] jibel: ça va, semaine qui démarrre en fanfarre, mais bon :) [07:15] didrocks: ça va très bien ! j'ai eu un bon week-end [07:15] pitti: tu as fait quoi? [07:16] didrocks: I'm going to blog/G+ about it RSN, watch out :) [07:18] pitti: heh, will do! :) [07:34] good morning desktopers [07:35] salut seb128! [07:36] lut didrocks! [07:36] Morning! [07:36] didrocks: hi! How was your long weekend? :) [07:37] hey sil2100 [07:37] sil2100: hey, was hot in Lyon! :) Got to the spa on Friday morning [07:37] was good, not too many people [07:37] Excellent [07:37] then, a lot of cycling (~30 kms) within the city [07:38] how was yours? [07:38] Ahh, I miss my bike, would love to ride a bit now that the weather is so nice [07:39] didrocks: done :) [07:39] bonjour seb128 [07:39] pitti: looking :) [07:39] didrocks: not bad, only had one day for resting theoretically, but I bummed around as much as I could ;) [07:39] pitti, salut, ça va bien ? [07:39] didrocks: btw. I see that the queue still has dbus-cpp and location-service waiting as (sync) [07:39] sil2100: yeah, I waited to ask you for it [07:40] it's from yesterday's right? [07:40] seb128: en effet, je vais très bien ! mon weekend était mervellieux [07:40] didrocks: it was from Friday [07:40] sil2100: oh, is seb128 to blame? :p [07:40] pitti, super, tu as fait quoi ? [07:40] seb128: hi! Was there some issue with NEWing those two? ^ [07:40] seb128: https://plus.google.com/107564545827215425270/posts/VtrGcA74wP9 [07:40] sil2100: I can NEW them, I reviewed them, apart if seb128 has some remarks on them [07:40] sil2100, no, they were just not in the queue at 7pm friday when I called it a week [07:41] seb128: tsss, 7pm on Friday and you call it a week? How dare you! :p [07:41] seb128: ok! didrocks: could you NEW ;) ? [07:41] sure [07:41] haha [07:41] Thanks, I'll check the stacks now [07:41] sil2100: ok, so on the stacks they both are, maybe you should rebuild those components [07:41] sil2100: once the merge back to trunk is done [07:41] I think we missed some new packages, but since there were some issues with tests and releasing, we only got that many new ones out [07:41] (for dbus-cpp and location-service) [07:41] sil2100: otherwise, the changelog will be screwed [07:42] didrocks, I was not sure they would land there since we had issue earlier in the day due to the lillypilly checklist (I think) [07:42] seb128: yeah, I saw a reject [07:42] didrocks, the copy there was not uptodate and not listing some of the components [07:42] telepathy-ofono [07:42] right? [07:42] and apparently trying to republish the same version doesn't work [07:42] yes [07:42] Yes [07:42] seb128: you have to cheat, it's possible to republish [07:43] seb128: sil2100: so that you know how it works [07:43] we tweaked the changelog [07:43] to bump the version [07:43] remember those .project files? [07:43] this is what are used to track what we didn't publish yet and need to monitor [07:43] didrocks: hm, so what should I do now with dbus-cpp and location-service? Should I rebuild those stacks and republish? Or merge something to their trunks? [07:43] didrocks: remember those, yes [07:43] as you can rebuild one part of the stack, we remove those .project file and recreate them [07:43] but you can as well publish them multiple times [07:43] (without rebuilding the whole stack) [07:44] so they are renamed .project_ [07:44] ok [07:44] if you need to republish the same version again, you need to mv package.project_ package.project [07:44] then launching the publication [07:44] Awesome to know [07:44] \o/ [07:44] Cheating is awesome [07:44] heh [07:45] well, it's not that easy, but in practice, this is "only" for new components [07:45] pitti, that sounds like a fun sunday ;-) [07:45] sil2100: so, yeah, once the changelog is merged back to dbus-cpp and location-service, please rebuild those [07:45] (just those components) [07:45] so get a real changelog :p [07:46] pitti: waow, excellent! [07:46] But but dbus-cpp and location-service already have 0.0.1daily13.06.14.1-0ubuntu1 in them ;p [07:46] sil2100: oh oh, silly me :) [07:46] yeah, it was "just" in NEW [07:46] but the diff isn't correct [07:46] Since those got published and just got stuck in the queue [07:46] yep :) [07:47] the only thing not "right" is the diff [07:47] between distro and bzr [07:47] to know if anything new was generated [07:47] seb128: indeed it was, Lieutenant! [07:47] pitti, ;-) [07:47] sil2100: so, just wait them to be published in -proposed [07:47] sil2100: and then relaunch them, maybe (I guess even :p) nothing new will be to be published [07:48] \o/ [07:48] * didrocks loves http://piware.de/fotos/Filmwelt-Bakede-Jun2013/slide_09.html [07:48] with the red eyes, it seems to be on purpose [07:50] didrocks: je crois que Kirk n'ai pas des yeux rouges ? [07:50] * hyperair wonders if anyone here is having intermittent issues with gtalk authentication in empathy [07:50] pitti: non, en effet, juste que je trouve que ça va bien dans le contexte tout de même :) [07:50] hyperair: I actually used to have, but it seems to have stabilized in the recent weeks [07:50] didrocks: :) [07:51] pitti: in saucy? [07:51] pitti: hum, it seems that Unity 7 became jaleous of the Unity 9 interface and decided to freeze :p [07:51] hyperair: yes (is there any other release? :) ) [07:51] heh [07:51] that should mean there's an SRUable patch, shouldn't it? [07:52] hyperair: I had the impression it was due to changes on the google side [07:52] no, i'm not sure it is. [07:52] i just killed signonpluginprocess, and it worked again [07:52] hyperair: maybe you have something different [07:52] previously i'd been removing and re-adding the google account in signon-ui [07:59] didrocks, seb128: I'll jump out for a quick exercise now, since the weather is excellent [07:59] sil2100: enjoy :) [07:59] Be back in some moments! [07:59] have fun! [08:00] morning [08:01] weather eh.. it's hazy as hell over here in singapore. === thumper-afk is now known as thumper === 13WAAK4RM is now known as tvoss [08:35] Laney, oh, I didn't notice your "morning" earlier, good morning! ;-) [08:35] heh [08:35] hey seb128! [08:35] it does seem quiet ;-) [08:35] hey Laney, good morning [08:35] everybody doing monday email catchup etc I guess [08:36] hey Laney! [08:37] \o/ [08:44] morning [08:44] i mean [08:44] bonjour! [08:44] ça va mlankhorst ? [08:44] very good [08:44] I exhausted my french for this week :-) [08:46] but the weather was nice saturday http://imgur.com/uVxApz4 [08:47] bonjour mlankhorst :) [08:49] mlankhorst: wow, that's a funny bike that you have there! [08:51] aye, I haven't tried the max speed yet [08:52] bet it requires a lot more maintenance than a push bike :P [08:54] yeah but I don't have to do most of it myself :-) [09:02] * mlankhorst is still using a conventional bike to get to the stables [09:29] * didrocks tries some reboots, bbiab [09:31] sil2100: back from exercising? :) [09:47] Laney: hum, you do have some upstart-session knowledge, right? :) [09:47] a small amount [09:48] do you have time for a small experiment? I think I probably did something wrong and it will take more time for me to debug [09:48] if you apt-get source unity [09:48] if I can't help then there are others who know more though :P [09:48] and apply that patch: http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3364 [09:49] does it start the panel service on session startup for you? [09:49] (it doesn't for me) [09:49] I wonder if ted is relying on one of the new indicators to emit indicators-loaded [09:49] and we don't have that signal [09:49] (in a vanilla installation) [09:50] Looking at the file it could be that 'start on started' is too late [09:50] depending on what it needs [09:50] but let me try [09:50] $ grep indicators-loaded /usr/share/upstart/sessions/* [09:50] /usr/share/upstart/sessions/unity-panel-service.conf:emits indicators-loaded [09:50] and nothing else [09:50] Laney: yeah, keep me posted :) [09:50] thanks! [09:50] that means that it sends a signal for others to look at [09:51] yeah, I just realized I misread [09:51] shouldn't affect the emitting service being run [09:51] I'll blame the hot weather :p [09:51] Back ;) [09:51] oh but, the other patch is "if we are under gnome-session… don't use the unity upstart job" [09:52] the other? [09:52] Resuming loking at stacks this very instance! Had to freshen up, since it's a bit too sunny for exercising [09:52] Laney: no, ignore me, the script exit 0, I think the event is emmitted [09:52] (in unity.conf) [09:53] sil2100: do you have time for a quick hangout to catch up? [09:53] didrocks: does 'status unity-panel-service' show it running? [09:53] didrocks: how about in 7 minutes? [09:53] sil2100: sure [09:54] Laney: I ran it by hand, does it impacts it? I can try a guest session [09:54] $ status unity-panel-service [09:54] unity-panel-service stop/waiting [09:54] $ status unity [09:54] unity stop/waiting [09:54] I don't have a unity upstart job [09:55] Laney: weird, I didn't revert that one AFAIK [09:55] http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3361 [09:55] start on started gnome-settings-daemon and xsession SESSION=ubuntu [09:55] wait, I'm lying [09:55] ah :) [09:55] gnome-settings-daemon is started here [09:55] but it isn't running [09:55] unless I got it today [09:56] Laney: no, not from today [09:56] and not running here as well [09:56] so "and xsession SESSION=ubuntu" is faly? [09:56] falsy* [09:56] let me see [09:56] ah, there is a stop in the script [09:57] aha, yes, it's tripping that [09:57] see ~/.cache/upstart/unity.log* [09:57] so your indicator event won't happen [09:57] right [09:57] grrr ted :p [09:58] in fact the check should be in the exec part [09:58] that's the right way to do a conditional start [09:58] yeah, but we still want to see the "unity" event started [09:59] can this be expressed in some way? (I don't think we want a super long "exec" line) [09:59] kind of confused by this [09:59] when wouldn't gnome-session be used? [09:59] Laney: touch [10:00] (I know, no sense for unity7 without xmir for now) [10:00] but I think ted wanted to implement it for the future [10:00] (the day of releasing unity 7 of course, hence the revert I had to do :p) [10:00] didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/apps_extra_packages_for_gallery/+merge/169756 <- could you take a look? [10:01] I guess started unity is the wrong thing for us at this point [10:02] sil2100: ok, making sense, thanks! [10:02] * Laney fires up the vm [10:02] didrocks: this would unblock Apps, looking at Indicators but LP is taking its time today\ [10:03] didrocks: hanging out in a moment? [10:03] Laney: do you mind tracking that once ted is back? you clearly have more knowledge on how we should build the sessions upstart once moving away from gnome-session to upstart to handle it [10:03] sil2100: I'm ready right now, tell me when you are [10:03] (I'll just exercice after this hangout) [10:03] I can probably figure out something to fix this up [10:03] didrocks: I'll just finish indicators and ready [10:03] but I don't really have a handle on moving away from gnome-session completely [10:03] thanks Laney :) [10:04] np [10:04] sil2100: ok [10:05] didrocks: ok, it seems that jbicha broke indicator-session on Saturday [10:05] Will have to wait for him to pop up [10:05] "nice", ok :/ [10:07] didrocks: do you have a hangout link ready by any chance ;)? [10:08] sil2100: https://plus.google.com/hangouts/_/d9e1fb52de2cf1cc1d14d5aca163296f609ed875?hl=fr [10:24] sil2100, how did he break it? [10:36] didrocks: OK, got it [10:36] didrocks: try "start on started unity or desktop-start DESKTOP_SESSION=ubuntu" / "stop on desktop-end" [10:52] seb128: have you tried system-settings on the device? [10:52] Laney, no, I planned to do that today ... does it work? [10:52] it's a bit buggy [10:52] like I couldn't get back from the individual panels [10:52] it's a bit annoying that you can't just deploy from qtcreator as you do for pure qml programs [10:52] oh [10:53] I will have a look [10:53] it just flicked instead [10:54] do you think it's ok to merge the appearance stuff with the example content? [10:54] I don't think I can do much more without dconf or the content picker [11:02] Laney: sorry, was in this hangout :) [11:02] np [11:02] Laney: nice! [11:02] does it work? [11:02] let me try [11:03] you can't have 'stop on stopping unity' because that is triggered by the job aborting itself [11:03] that one confused me for a bit [11:03] started unity is true even if the job stopped I guess? [11:04] no [11:04] ah or [11:04] but stopping is [11:04] hum [11:04] pre-start -> stopping -> stopped I think [11:04] I think ted wanted to start only if unity startede [11:04] started* [11:04] that's what the desktop-start should do [11:04] it comes from gnome-session [11:04] so you have both [11:04] yeah, it's a bit "uncrystalclear" [11:05] but works in theory [11:05] let me see :) [11:05] can comment it [11:05] contrive* was the term I was looking for :) [11:05] it's new world and old world [11:05] heh, right [11:05] you're going to get stuff like this until we are ... converged ... [11:07] Laney: working fine :) [11:07] (tried multiple starts) [11:07] so yeah, please, add a comment and I'll approve it :) [11:07] I suppose you could simplify it further if you made the unity job emit that desktop-start signal [11:07] thanks! [11:08] yeah, not sure if we can emits since the pre-start script though [11:08] from* [11:08] you'd probably do it in post-start [11:08] see /usr/share/upstart/sessions/gnome-session.conf [11:09] ah, so you mean, removing the unity signal, but have "destkop-start & session==…" [11:09] edit debian/unity.conf to have the same post-start and pre-stop as gnome-session does [11:09] then have unity-panel-service just listen for desktop-start/desktop-end [11:10] not sure if it's semantically correct, it's like if we were telling the session is ready if unity is ready (and we don't care about the rest) [11:10] as you wish, the best in your opinion :) [11:11] if we tell "DESKTOP_SESSION" is used to detect we are using gnome-session, I'm fine with it [11:12] ok [11:12] where's the MP? [11:13] Laney: oh, there is none, it's part from a revert, so reintroduce the revert + your additional commit I would say [11:13] sure [11:13] (I had to revert it in a hurry the day we released unity 7 as having that + a segfault was enough :p) [11:14] * Laney meditates for a minute on what is better [11:14] * didrocks lights a candle for Laney [11:16] Laney, sorry, I was grabbing a bite ... merge the background panel makes sense yes [11:17] ok [11:17] I want to get a widget merged into the ui toolkit first, so will try that this afternoon === MacSlow is now known as MacSlow|lunch [11:18] cool [11:20] is there a trick to restart unity and keep the workspace where each window are? [11:20] like gnome-shell does when doing alt-f2 r [11:20] if I just do unity --replace then all my windows goes to first workspace [11:21] hum, they should not, seems like a bug === greyback is now known as greyback|lunch === MacSlow|lunch is now known as MacSlow [12:25] seb128: regarding the indicator-session, I just checked and my conclusions were too soon - jbicha did not break it, it broke itself probably due to changes in saucy [12:25] seb128: as it's the same issue as with some other packages - pthread errors [12:25] sil2100, what's the error it hits? [12:26] oh, yeah, new binutils being pickier about incorrect linkage [12:26] /usr/bin/ld: libgtest.a(gtest-all.o): undefined reference to symbol 'pthread_key_delete@@GLIBC_2.2.5' [12:26] Yes [12:30] grr, silent rules! === greyback|lunch is now known as greyback [13:12] Laney, how did you run the settings app on the device? [13:24] sil2100: needing any packaging ack? [13:33] didrocks: not yet, uno momentos [13:37] tedg: hey! FYI, after some tests, there was still an issue with your panel-service + upstart branch, after talking to Laney, there is a solution that is merging right now (https://code.launchpad.net/~laney/unity/user-session-jobs/+merge/169771) [13:38] tedg: basically, the issue was that unity event always stops when using gnome-session, so the event for starting unity-panel-service was never triggered [13:39] didrocks, Ah, cool! [13:39] didrocks, Great stuff! [13:40] thanks Laney for providing an elegant solution :) [13:40] It should make debugging the indicator issues there *much* easier. [13:40] and make it starting faster [13:40] I can feel the difference, even on my beefy machine :) [13:40] Heh, great! [13:40] stopping seems a little bit longer, but on startup, it feels like if unity was already started :) [13:42] didrocks, I think that's because not all of our stuff is responding to SIGTERM properly. [13:42] didrocks, So then upstart has to formally kill things after a 5 second timeout. [13:43] tedg: I agree with you, we seem to timeout systematically [13:43] didrocks, I think we should look at some of the offenders, we have a SIGTERM handler in HUD that just shutsdown the mainloop gracefully, and it works with usptart well. [13:43] didrocks, Probably need to add that code around. [13:44] didrocks: hmmm... still checking that, but the new package dependency of gir1.2-dbusmenu-glib-0.4 for raring is a bit fishy [13:44] tedg: do you know if upstart has a way to tell "this is what timed out" [13:44] at least to have a list [13:45] sil2100: hum, didn't we decide to look at saucy first, making all possible publication and move on the SRU then? [13:45] didrocks: since I checked all the obvious projects and the only place where the gir1.2-dbusmenu-glib-0.4 dependency was added was libdbusmenu, but for saucy [13:45] didrocks: doing that too, was waiting for Apps to finish, I also re-ran Unity, will check the publications too [13:46] ok :) [13:46] didrocks: I'm just afraid that there might have been a stack publishing missing somewhere ;/ [13:46] sil2100: so let's ignore it [13:46] FOr raring [13:46] didrocks, Hmm, not sure it has a way to see that. It can give a reason that it was stopped, but I think the only cases now are pass/fail. Perhaps we could add "timeout" [13:46] sil2100: I wonder if it's not part of the "this used to work" [13:46] (ignored by UTAH checks) [13:46] and now otto really checks it [13:47] tedg: yeah, that would be interesting for debugging [13:47] * didrocks proposes a shutchart :) [13:49] seb128: I installed and launched it from the terminal [13:49] don't know why it didn't appear in the app lens [13:49] Laney, do you know how to get an icon for it? [13:50] it has a desktop file [13:50] kenvandine, hey, do you know what would be needed for system settings to get an icon on ubuntu touch. [13:50] ? [13:51] didrocks: that was one of the issues ;-) The other one was that the condition for gnome-session was never fired so you never got it started on the desktop [13:52] indeed :) [13:53] ooh, britney/autopkgtest is coming [13:53] so everyone will really have to make sure tests work ;-) [13:54] * mlankhorst still can't push xorg-integration-tests :( [13:56] it won't compile until x1.14 lands [13:58] didrocks: maybe... are you ready for some ACK's for publishing? ;) [13:59] sil2100: I fully am! [13:59] just need to reference an icon that is installed [14:00] right now it is using one from a theme that isn't installed [14:00] seb128, ^^ [14:00] didrocks: platform: http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qtubuntu_0.51daily13.06.17-0ubuntu1.diff/*view*/ <- but here I see a small problem with the changelog [14:00] didrocks: as one entry is duplicated by Tim and Ken [14:00] sil2100: it's not an issue, it means that both contributed to the branch that was merged [14:00] (they did each one at least one commit) [14:01] Awesome, then it's all ok in my eyes [14:01] sil2100: fine for me as well, feel free to publish :) [14:01] kenvandine, ok, I will do a MR to fix that then ;-) [14:03] didrocks: published, now sdk: [14:03] http://10.97.0.1:8080/view/cu2d/view/Head/view/SDK/job/cu2d-sdk-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_dee-qt_3.0daily13.06.17-0ubuntu1.diff/*view*/ [14:03] (no deps, just packaging) [14:04] seb128, cool [14:04] sil2100: good good! :) [14:04] seb128: kenvandine: I thought there was a touch icon theme? [14:04] Some of the panels in there don't have icons either [14:05] Laney, ubuntu-mobile-icons [14:05] Laney, but it's not complete [14:05] so the ones we chose are just what it will be? [14:06] you mean? the icon names? no, I tried to pick available icons as place holders [14:06] we will need to update that once design provides the icons [14:06] sil2100: on the indicator with binutils being pickier, this is fixed/merging or do we need help? [14:07] didrocks: published, settings now: http://10.97.0.1:8080/view/cu2d/view/Head/view/Settings/job/cu2d-settings-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-system-settings_0.1daily13.06.17-0ubuntu1.diff/*view*/ [14:08] didrocks: I think it's not being worked on yet, but I guess I could quickly fix that [14:09] sil2100: +1 [14:09] (we can notice seb128 writing commit message of 3 kms long :)) [14:09] heh [14:10] * Laney approves of that! [14:10] I'm writing nice details for you to read ;-) [14:10] seb128: that's kind of you :p [14:10] seb128: "settings": is there anything else? it's the name of the panel? [14:10] the settings panel of system settings? [14:10] didrocks: cyphermox fixed the indicator-session thing, so it's getting merged now [14:10] \o/ [14:11] moo [14:11] thanks cyphermox :) [14:11] ;) [14:11] didrocks, no, it's the settings app itsel ... you can notice some are "about: ..." which is the about panel [14:11] didrocks: I was surprised Laney didn't beat me to it like for indicator-datetime :) [14:11] I got the wrong impression that those were all fixed [14:11] otherwise I would have ;P [14:12] Laney: ahah ;) [14:12]