[00:02] robru: Confirmed, simply rebooting didn't help, but silo 15 fixed the thumbnail issue. (libthumbnailer0_1.0+14.04.20140319-0ubuntu1_armhf.deb) [00:02] ToyKeeper, oh excellent [00:02] ToyKeeper, can you dogfood a little bit more with silo 15 to make sure it doesn't break anything? [00:02] i'm testing a different silo right now [00:02] Yes, but it probably won't be until a bit later. [00:02] oh ok [00:14] Hmm, my time zone bug seems to be back. [00:16] (basically, Denver is not UTC+1: http://toykeeper.net/tmp/phablet-tz-denver-wrong.png ) [00:16] ... will continue when I get back later, though. [00:41] alright, I'm heading out for dinner, will check in after a few hours [03:04] === trainguard: IMAGE 248 building (started: 20140320-03:05) === [04:14] === trainguard: IMAGE 248 DONE (finished: 20140320-04:15) === [04:14] === changelog: http://people.canonical.com/~ogra/touch-image-stats/248.changes === [04:38] Laney: thank you for publishing qtbase, you were the lander after all. I have a note of proposing that to upstream. [04:38] I mean, Debian [06:44] Mirv: hey! are you looking at the calendar-app thread on the phone ML? Seems as it's Qt related, you would be the best to understand it [06:48] didrocks: yes I've been looking. maybe sdk team can also help. [06:49] Mirv: that would be sweet! [07:52] can I get a silo for line 64 [07:56] thostr_: sure, just a minute [07:56] thostr_: actually not, it's already on line 15 [07:57] the question is whether to release it since it claims to be tested, or how risky it is now that we're almost having a promoted image [07:58] Indeed [07:58] and did the build actually include the exif branch, hmm [07:59] yes, yes it did [07:59] so, what about then adding the fix to line 15 [07:59] and rebuilding it [07:59] then we can still decided whether to land or not [07:59] thostr_: it is already there, I just checked that it was included during the build: http://162.213.34.102/job/landing-015-1-build/20/consoleFull [07:59] the same branch [08:00] Mirv: ah, ok. then we're good for now [08:01] sil2100: would you have time to double test gallery-app? I'm trying to debug the calendar app problems at the moment on my device. [08:01] thostr_, Mirv: the changes look pretty safe, but I would only land it if someone from our team could double-test it [08:01] Mirv: sure [08:01] Mirv: you're reading my mind! [08:02] thanks :) [08:02] Let me just re-flash [08:02] a crasher fix is a crasher fix after all (thumbnailer) [08:09] thostr_: can you cleanup the req you have from line 6 to line 10? seems some can be removed [08:10] thostr_: hmmm, regarding landing 10... [08:10] didrocks: still applicable... some where blocked or waiting on other fixes [08:10] thostr_: landing line 10 I mean [08:11] didrocks: i have been the bottle neck as well... [08:11] thostr_: most of them are ready: no though? [08:11] thostr_: see the comment on line 9 as well [08:11] it's already merged? [08:11] thostr_: the FFe bug you mentioned is not the curent one - that one is from 13.10 [08:12] thostr_: url-dispatcher is not in the FFe list from https://bugs.launchpad.net/ubuntu/+bug/1282590 [08:12] Ubuntu bug 1282590 in Ubuntu "[FFe] standing freeze exception in trusty for Ubuntu Touch-specific packages" [Undecided,Confirmed] [08:12] didrocks: ^ is the old FFe still valid? The one from last cycle that Steve filled in? [08:12] didrocks: or should we only look at the trusty one now? [08:14] didrocks: sil2100: I'll recheck all my landing requests today... need to wait for some for ted/charles though [08:15] thostr_: ok, please do :) [08:15] sil2100: no, its not [08:15] sil2100: so yeah, we need a new one for trusty [08:20] thostr_: ok :) [08:23] the calendar-app issue looks complex. I can confirm reverting the last commit fixes the crasher on x86, which was mentioned to be blocking a fix for the autopilot test. I pinged tsd_geos so that he could look at my local backtrace bug #1294995 [08:23] bug 1294995 in qtdeclarative-opensource-src (Ubuntu) "qmlscene crashed with SIGSEGV in value() when running calendar-app" [Undecided,New] https://launchpad.net/bugs/1294995 [08:23] then regarding the flaky test, it hasn't flaked during the last five images at all it seems [08:24] and I remember I didn't get the failure on my tests either [08:34] Mirv: I think we may want to follow reverting both? [08:35] Mirv: regarding that landing 15 - I'm starting to test it right now, but I see some of the MRs there are not approved or reviewed even [08:35] I would say we wait for Bill to appear with landing this one [08:35] didrocks: which both? so https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/revert-212/+merge/211813 seems to fix the x86 crasher balloons mentions to be a blocker for landing fixes for the AP problems in bug #1293489 [08:35] bug 1293489 in Ubuntu Calendar App "Multiple test failures since move to Qt5.2 #238 on Mako" [Undecided,New] https://launchpad.net/bugs/1293489 [08:36] I'm not confident in releasing something from merges that don't have a visible review on them, it's state is a bit 'unknown' right now [08:37] sil2100: yeah, even though it's mentioned to be tested the branches should be top-approved [08:38] Mirv: there is as well that one: https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/standalone-ap-for-1293489/+merge/211854 [08:38] to fix the real AP test issue [08:39] didrocks: oh, ok, you just said "reverting both" but that other one is refactoring [08:40] but yes, approving both of them. I should test the autopilot on desktop more with/without branches. [08:40] Mirv: ah sorry, yeah, needing both branches :) [08:59] didrocks: so, the flaky messaging-app test fix that boiko did - there is a landing for that but I cannot assign a silo for it as messaging-app is already part of landing-009, which is 'Testing pass' but seems a little bit risky for me [08:59] sil2100: please override, add a commit to the other one with the rationale and set testing to no === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: none [08:59] didrocks: ACK [09:05] sil2100, http://irclogs.ubuntu.com/2014/03/19/%23ubuntu-release.html#t20:41 [09:06] sil2100, that's where the url-dispatcher ffe got discussed (you are being overzealous on that one it seems ;-) [09:07] * didrocks prefers overzealous than having something to be reproached for :) [09:07] I can see that [09:07] seb128: well, I just checked the FFe bug back then and didn't see it ;) Just doing my duties! [09:08] sil2100, I had the link to the bug in the comment, it just happens that they are 2 bugs for touch ffe now? [09:08] if that one is invalid/from last cycle we should maybe fix released it? [09:08] seb128: yes, one is for last cycle, one is for this cycle [09:08] we should close the old one then [09:08] seb128: probably, I already once made the mistake on looking at the wrong one... [09:08] to avoid those confusions [09:09] seb128: I'm unsure from the discussion it came to a resolution though [09:09] (seeing your IRC link) [09:09] and yeah, they are not leftover, they were in last cycle one because those weren't in the desktop seed, and they are now [09:10] didrocks, I'm based on "slangasek so if we're sure that lib isn't used except on touch, then yeah, that all sounds reasonable" [09:10] we don't use url-dispatcher in the indicator to run stuff on desktop [09:10] so I think virtually that's not being used [09:10] seb128: I'm just looking at what's pulling it in, one sec [09:11] but if you guys want a formal confirmation we need to go back to slangasek [09:11] so, the indicators [09:11] didrocks, indicators to call settings mostly I think [09:11] pulling liburl-dispatcher1 [09:11] ok [09:11] right [09:11] I think if there is no ABI breakage and based to yesterday discussion, that we can +1 [09:11] sil2100: wdyt? [09:11] didrocks: correction. the revert-212 branch includes the other branch, the other branch alone just isn't enough [09:11] on* [09:12] Mirv: ok, it's a prereq? [09:12] didrocks: sounds good to me I guess [09:15] didrocks: no, it's included, the other one is just the "other fixes" but not the revert which is needed to fix the crash [09:15] then, to fix the actual AP bug two more branches from bug #1293489 are needed [09:15] bug 1293489 in Ubuntu Calendar App "Multiple test failures since move to Qt5.2 #238 on Mako" [Undecided,New] https://launchpad.net/bugs/1293489 [09:15] didrocks, do you have a " free silo" counter somewhere? looks like it would be useful ;-) [09:16] seb128: for people with the right commit access level, it's possible, but yeah, can do that [09:17] seb128: I'm working on making reconfigure/assignement easier first [09:17] Mirv: ok, seems we need to test this whole bundle [09:18] didrocks, ok, that would be nice (I keep wondering if stuff are waiting because there are no silo left :p) [09:19] seb128: I'll be assigning silos in a moment ;) [09:19] Was busy testing [09:19] sil2100, no hurry, it's just that the topic came back a few days this week [09:20] seb128: well, in overall we're a bit 'stuffed' with things which we either don't want to land before promoting an image or need to test manually and/or need comment from the authors [09:21] So things tend to stretch a bit longer, I hope we'll get a promotable image soon... [09:21] sil2100, well, Mirv assigned me silos for my desktop specific entries so I'm happy enough [09:21] it feels like l32&33 should be fine as well [09:21] one touch the wizard in settings, which is not used [09:21] the other one is in a test tool [09:22] All seem safe [09:22] seb128: G1 [09:23] didrocks, thanks! [09:23] yw :) [09:23] so we are on top of the normal assignment atm [09:24] seb128: ok, one more silo assigned - but the rest needs to stay free for emergency needs ;) [09:24] yep [09:24] sil2100, right, thanks [09:24] I'll test some ready safe-landings in the meantime [09:24] yw [09:28] sil2100, publish 28 pls? [09:30] mhr3: one moment, resolving that one, some doubts [09:30] (and meeting) [09:31] Mirv: coming? [09:34] I needed to juggle between laptops a bit [09:43] psivaa, doanac seems to only have the phonesim install/remove code to the dialer-app test, but not to the messaging-app one, could we get it there too ? (messaging-app fails with "no phonesim found" on both tablets ... it works on N4 because there is a physical SIM apparently) [09:43] *have added [09:44] (that will get us 16 failures less per tablet :) ) [09:47] ogra_: 'messaging-app-autopilot' does not look to have it as a dep.. but i'll take a look at this deeper. thanks for looking at it [09:47] psivaa, no, thanks to you :) [09:49] mhr3: testing the landing and publishing - just tell me sincerely: how 'risky' you thing those changes are? ;) [09:49] *think [09:50] sil2100, very low, plus no effect without new-scopes [09:50] mhr3: I love landings like that, thank you for that! [09:51] mhr3: anyway, expect it being published in the nearest minutes, just want to run unity8 tests till the end as a quick double-check [09:51] it really can't affect that, it's all new-scopes only [09:59] hmm, phone is plugged into usb, does that prevent deep sleep? [10:00] ogra_: ^ [10:00] * popey starts the song again [10:00] getting sick of this song now ㋛ [10:00] i think adbd keeps a wakelog in the kernel [10:00] ok [10:00] * popey unplugs [10:01] ogra_: wakelock, you meant? (you keep sayig wakelog, so maybe I missed something? :p) [10:01] saying* [10:01] err, not really awake locked here :P [10:01] (indeed i meant wakelock ;) ) [10:05] didrocks, hey, fyi; last night it seems cjwatson gave me the hint that components landing only for ubuntu touch are covered by the spirit of the original bug/FFe ... the only thing I forgot to ask yesterday was if we should add a comment or edit the description of such bug [10:06] sergiusens: hum, I think the description was clear it was about that, (and that's why there is the exact list). It's telling: [10:07] I would like to request a blanket FFe wrt Ubuntu Touch, for those packages that are part of Ubuntu Touch but not part of Ubuntu Desktop [10:07] didrocks, oh, I'm not talking about the current list; but about additions to that list [10:08] sergiusens: ah, it needs to be acked first, so I guess on comment [10:08] sergiusens: and then, we add it to the description === vrruiz_ is now known as rvr [10:09] sergiusens: maybe in a subsection, mentioning that they are in other seeds, but won't have any backward incompatible breakage/not used really on the desktop [10:09] to make the separation clear [10:10] didrocks, yeah, my case is for totally new components like media-hub and push-notifications [10:11] sergiusens: oh sure, I guess once it's recorded in the comment that the RT +1 on it, feel free to append at the bottom of the description [10:11] ok, good that we have a process; fwiw media-hub was separately logged and approved already :-P [10:12] sergiusens: ah great, so if you want to add to the list, please do (and reference the other bug in a comment) [10:15] didrocks: packaging ACK: http://162.213.34.102/job/landing-005-2-publish/46/artifact/packaging_changes_unity-scopes-shell_0.4.0+14.04.20140320-0ubuntu1.diff <- looks sane [10:16] sil2100: +1 [10:24] sergiusens: I think it's appropriate to ask, just saying that from the point of view of the release team it probably means we normally don't need to think *too* hard [10:28] sounds good, thanks [10:44] dbarth_: hi, wanted to ask some questions regarding landing line 12 [10:56] sil2100, ok, I freed some silos, you are back to 4 ;-) [10:57] sil2100: go ahead [10:58] sil2100: it's good to go; i was just checking and sounds like robru didn't land it [10:59] sil2100: tests pass, we verified that with alex_abreu yesterday; can you press publish? [10:59] sil2100: then i can merge and clean that silo [10:59] Mirv, can you look at silo 1? it should be low risk fwiw; but land after promoting if you want [11:05] dbarth_: I just wanted to double check if all is ok from the phone side, but it seems ok [11:05] dbarth_: how would you assess the risk factor of this landing? [11:07] seb128: thanks! I noticed already earlier, that's why I assigned an additional silo for you ;) [11:07] sil2100, thanks ;-) [11:12] sil2100: limited, it changes JS code used by the html5 stack; only html5 app developers would be affected if there is a regression we haven't seen [11:12] popey: didrocks: Stairway to heaven 8:02 played from start to finish no issues [11:12] davmor2: while plugged in or not? [11:13] popey: not I was downstairs [11:13] hm, okay [11:13] how odd [11:13] dbarth_: publishing! [11:13] didrocks: also I've replied to the phone list [11:14] sil2100: ok [11:16] morning all [11:16] sergiusens: you're correct that it looks safe since it only adds a plugin not touching other things. that said, it wouldn't hurt to have the promotion happening either [11:16] sergiusens: the docs branch is not top-approved [11:21] Mirv, right; the top approving is really necessary these days? [11:21] sil2100: ^ [11:21] sergiusens: I don't know, asking from the more experienced train mover :) [11:22] popey: just played it again to prove it wasn't a fluke still not plugged in [11:22] sergiusens, Mirv: it's nice to have, but it's not necessary - as long as we see there is someone from upstream doing any approval for the newest and latest of the commit [11:22] *commits [11:22] sil2100: yeah, so some approval is enough. ok. [11:23] sil2100: would you mind looking too if https://code.launchpad.net/~diegosarmentero/ubuntu-download-manager/udm-qml-plugin/+merge/209573 seems safe to you? it only adds stuff so that's why it'd seem to me it's safe to publish. [11:23] Mirv: u-d-m! Oh noes! Let me check [11:23] sil2100: yeah, I've some memories of u-d-m breaking earlier, that's why it feels like it's useful to be extra sure :) [11:25] Mirv: I think you're right - it seems really nice and safe, only adding the plugin - is it tested in a silo already? :) [11:25] Mirv, fwiw; we landed u-d-m 2 times this week already [11:26] sil2100: yes, it's tested. there's another MP that claims to be docs only but I see slight weird differences there otherwise too: https://code.launchpad.net/~mandel/ubuntu-download-manager/documentation/+merge/209664 [11:26] sergiusens: why there's a registerMetaType() function removed in the docs commit? [11:26] Mirv, let me double check, but it is mainly docs and I did the test plans for udm, click scope and system image updates [11:26] and there are consts added, and &:s moved around [11:27] mandel: ok, just pointing out since it claims to be about documentation but has some other slight changes [11:27] Mirv, the function call was removed because it was never used and makes no sense [11:27] Mirv, const were added but are just for internal objects in the priv lib [11:28] Mirv, I can link bugs about that to document it, no problem [11:28] mandel: it'd be enough if the MP commit / description would state that some function and some constructors were removed and consts:s added, in addition to docs changes [11:29] well and of course if there are already bugs open, those are welcome too to be linked [11:29] Mirv, there are no bugs added, no, but I'll update the commit msg, does that sound good? [11:29] s/constructors/destructors/ [11:29] mandel: sounds good [11:30] other than the group_download_struct.cpp changes it's quite clear [11:30] davmor2: bug 1295086 if you can reproduce pls.. [11:30] bug 1295086 in mtp (Ubuntu) "Content doesn't refresh when viewed in desktop file manager" [Undecided,New] https://launchpad.net/bugs/1295086 [11:30] seen it for ages, only just got round to filing it [11:31] Mirv, MR updated [11:31] mandel: thanks [11:32] Mirv, no proble, sorry for that I did it without thinking it was very important :-/ [11:33] didrocks: I'd need packaging ack for http://162.213.34.102/job/landing-001-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.3+14.04.20140319.1-0ubuntu1.diff - seems good, unless all plugins are wanted to be forced to be of the form qtdeclarative5-[packagename][version]. I'd allow that, but I'm not sure how strict our policy is. that current version sounds better than qtdeclarative5-ubuntu-download-manager0.1 [11:34] Mirv, we can ping gatox about that [11:34] mandel: you just did :) [11:35] Mirv, I think is better to follow the norm if possible [11:35] Mirv, awesome, then I'll let you guys decided about qml, is out of my area :) [11:35] mandel, if it's about naming, i think it shold follow the convention [11:35] mandel: gatox: yeah, I don't see too many deviations from that norm, so possibly qtdeclarative5-ubuntu-download-manager0.1 should be used [11:35] ok, commenting on the MR then [11:35] didrocks: unping [11:36] gatox, please, can you update that? I think with that change we can land the qml so that the browsers guys can start looking into it [11:36] ;) [11:38] commented, also mentioning the version-specific install directory which we are implementing quite poorly in general but that was the proposed policy and makes sense [11:38] working unping would actually be useful [11:39] mandel, updated [11:39] Mirv, didrocks ^^ [11:39] gatox, sweet, thx [11:39] mandel: gatox: then the version specific install directory too, please [11:40] so eg. UbuntuDownloadManager.0.1, so that when you'll have 0.2 the new package can be co-installed [11:41] mandel, Mirv version added to the install folder [11:41] it might need a bit more tweaking in the .pro files [11:42] Mirv, how's that? [11:42] gatox: the make install obviously needs to install to that directory too [11:42] it could be tricked with packaging maybe too, though, but that'd need creating directory manually and moving files or such [11:43] friends has something like http://bazaar.launchpad.net/~super-friends/qml-friends/trunk/view/head:/modules/Friends/Friends.pro [11:43] so modifying installPath [11:45] popey: I get the same even if I hit reload I think it is an issue in mtp infrastructure and instantly blame ogra_ ;) can you see if the same thing happens on your iphone? [11:45] popey: ie if it is mtp at fault or just our implementation of it [11:46] popey: oh by the way were you able to replicate the issue I found with contacts/dialer app? [11:48] Mirv, mandel .pro updated [11:51] mandel: ok, kick a rebuild? [11:51] didrocks, just thought of a relatively simple thing that could be helpful if possible - updating the PPA description with some data like the description of the landing, list of included MPs and such [11:51] Mirv, sure [11:52] popey: confirmed and commented [11:59] davmor2: thanks, also.. can you test alarms? They're not going off for me [11:59] popey: and confirmed it works correctly on android so it is just our implementation of mtp [11:59] popey: in which case I definitely blame ogra_ :D [12:01] popey: alarm set for 5 minutes past [12:02] popey: should they go off with the phone screen blank? [12:02] popey: or is that still not implemented yet? === cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cjohnston | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - [12:03] davmor2: even with the screen on [12:04] it should ring. [12:05] popey: okay, did you look at this in the end https://bugs.launchpad.net/bugs/1294710 [12:05] Ubuntu bug 1294710 in dialer-app (Ubuntu) "Call log view contact flashes the contact details then goes to the normal list" [Undecided,New] [12:05] popey: ringing with screen on and the clock app closed [12:05] davmor2: no, i have no contacts on my phone [12:06] popey: right trying again now with the screen off [12:08] popey: do you have like a 150 number to check your balance that is free to call? [12:09] i have lots of numbers i can call for free, I just have no contacts on my device so will need to set them up to try it, not got round to it thats all [12:10] popey: ah okay cool :) [12:10] popey: Huston I think we have a problem [12:10] Saviq: that's a good idea. I have other things I want to do first, but if you open a bug, I'll do that after the bot :p [12:11] didrocks, ;D [12:11] popey: with the screen on I got an alarm, with the screen off I don't and looking at the device it seem that the clock got stopped when the alarm should of gone off [12:11] davmor2: tried your bug, can't reproduce, contact appears [12:12] davmor2: clock doesn't trigger alarms, indicator-datetime does [12:12] popey: yeah the time in the indicator is stuck when the alarm should of gone off [12:13] didrocks, bug #1295096 [12:13] bug 1295096 in Canonical Upstream To Distro "Description of silo PPAs should be updated with some relevant info" [Wishlist,New] https://launchpad.net/bugs/1295096 [12:14] popey: can you edit an alarm twice and have it update correctly? [12:15] * popey tries [12:15] davmor2: when i try to edit an alarm I get this... http://popey.com/~alan/phablet/device-2014-03-20-121531.png [12:16] boiko: hello! Your messaging-app is in silo 014 [12:16] right so I've set an alarm now for 18 minutes past I'll let the phone sleep and I'm betting at 19 minutes past the clock will still say it is 18 minutes past [12:16] Saviq: thanks :) [12:17] davmor2: also, clock crashes when you delete an alarm [12:17] [Thu Mar 20 12:07:55 2014] type=1400 audit(1395317761.205:493): apparmor="DENIED" operation="mknod" parent=1928 profile="com.ubuntu.clock_clock_1.0.373" name="/home/phablet/.config/com.ubuntu.clock_clock_1.0.373.conf.L21550" pid=21550 comm="qmlscene" requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011 [12:17] popey: oh I don't get that what happened for me is the last alarm was at 12:08 I changed it to 12:15 hit save and it still showed 12:08 [12:17] sil2100: thanks, let me build that [12:17] davmor2: popey: IIRC, alarms were not triggered already in previous promoted image, right? [12:17] popey: it just deletes them here [12:18] didrocks: lemme try [12:18] sil2100: oh, they are already built, nice [12:18] boiko: I already pressed build to speed things up if anything ;) [12:18] * didrocks has never seen that working [12:18] sil2100: nice! thanks [12:18] didrocks: having two phones means i find it hard to remember what works where ☻ [12:18] * sil2100 wants this fix badly ;) [12:18] didrocks: iirc it did if the phone was awake but not when it was asleep [12:18] popey: ETOOMANYPHONES! [12:18] davmor2: hum [12:18] you're right [12:19] didrocks: which is what I am seeing now [12:19] on arlams or on the too many phones? :p [12:20] didrocks: bad news! [12:20] popey: it looks like the alarm just went off and now won't stop so 2 minutes late and the clock says 12:18 [12:20] alarm just went off on my stable phone! [12:21] didrocks: ^ [12:21] hum [12:21] grrr, ok :( [12:21] not sure what our tests, there are alarms tests [12:21] just had to reboot the phone to stop the alarm [12:21] popey: davmor2: so I guess it's alarm testing time… [12:22] didrocks: now I know it works I will I wasn't adding it till it did though there was no point :) [12:23] so, the question is… is it a blocker in your opinon? [12:24] popey: Column AD does the description make sense? [12:25] davmor2: popey: so on latest promoted image, it was only working if the screen wasn't blank? [12:26] wait 2 mins for my alarm [12:26] popey: ^ does it work with the screen blank as well as active? [12:26] * popey taps power button [12:26] * popey waits [12:26] davmor2: IMHO, if didn't work with a blank screen ~= non functional for me [12:27] alarm rings when screen is blank [12:28] ok, and so, not on latest image, right? [12:28] on current build number: 237 [12:28] aah [12:28] but? [12:28] you didn't say the contrary [12:28] * didrocks is lost [12:28] so, in summary:- [12:28] ah, #237, so latest promoted [12:28] You asserted that the alarms never worked on a promoted image. I'm saying they did. When blanked. [12:28] ok [12:29] dpm just heard it via a hangout :D [12:29] so, we need to bisect [12:29] hahaha [12:29] let me test again on latest image [12:29] yep [12:29] note though that I see a lot of this... [12:29] [Thu Mar 20 12:07:56 2014] type=1400 audit(1395317761.205:493): apparmor="DENIED" operation="mknod" parent=1928 profile="com.ubuntu.clock_clock_1.0.373" name="/home/phablet/.config/com.ubuntu.clock_clock_1.0.373.conf.L21550" pid=21550 comm="qmlscene" requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011 [12:29] on the latest promoted image [12:29] jdstrand: ^ [12:30] gnnnn [12:30] popey, make sure alarms work on flo which doesn't have the wakeloc problem [12:30] latest non-promoted image [12:30] ffs [12:30] ;/ [12:30] sil2100: so, continue to not publish anything risky :p [12:31] bah. clock crashes on alarm save [12:31] I hate news like this! I want to publish everything as it goes already ;p ! [12:31] sil2100: well, even once we promote, we need to ramp up publication [12:31] sil2100: and cut images regularly [12:31] popey: on current when the alarm goes off does it wake the screen in the same way a call would? [12:31] no [12:31] just rings [12:32] right, cleared out all alarms and created a new one [12:32] no errors in dmesg, no crash [12:32] didrocks: indeed [12:32] * popey hits power and waits 2 mins [12:33] popey: okay that's odd are you leaving the clock app open? [12:34] didrocks, popey: that is bug #1288742 [12:34] bug 1288742 in ubuntu-ui-toolkit (Ubuntu) "clock app using incorrect path for config file" [High,In progress] https://launchpad.net/bugs/1288742 [12:35] thanks jdstrand [12:35] np [12:35] popey: last alarm didn't go off but the clock app was open, trying again now with the clock app closed [12:35] didrocks: alarm didnt ring on latest unpromoted [12:36] aha! [12:36] it displays but doesn't ring! [12:36] but if the display is off, obviously you can't see it [12:36] jdstrand: argh, so it was known? [12:36] yes, I filed it weeks ago [12:36] jdstrand: but I guess you didn't know it was preventing the alarm going off [12:37] sil2100: Mirv: can we try to land that with bzoltan's help? [12:37] and reported it on the list when I examined new denials [12:37] didrocks: actually, I think I said as much-- ie, that the app wouldn't work right. I told Pat about it. looking at the bug there is an MP [12:38] didrocks: davmor2 http://popey.com/~alan/phablet/device-2014-03-20-123802.png [12:38] thats latest unpromoted, the alarm _does_ trigger, but no ring [12:38] (ie, I told Pat, Pat escalated it, there is an MP) [12:38] jdstrand: ok :( sad that Pat didn't report the info [12:38] well, I did [12:39] * jdstrand finds the thread [12:39] didrocks: sil2100: with bzoltan's help, yes [12:39] bzoltan: can you check https://bugs.launchpad.net/ubuntu-clock-app/+bug/1288742 and add a line for that MP only? [12:39] Ubuntu bug 1288742 in ubuntu-ui-toolkit (Ubuntu) "clock app using incorrect path for config file" [High,In progress] [12:40] Mirv: I guess if bzoltan isn't aroud, we have to land and test ourself ASAP [12:40] didrocks, jdstrand: so till this is fixed are we saying that alarms should be flakey then? [12:40] jdstrand: on the ML == on the Qt 5.2 discussion? it wasn't raised as a blocker (not meaning by you, but when I asked for remaining bugs) [12:40] actually, I didn't mention that bug in the thread I was thinking of, cause I had already reported it and it was escalated [12:40] didrocks: ok, adding line [12:40] Mirv: ok [12:40] didrocks: davmor2 i believe the issue jdstrand is talking about is separate from the alarm sounding. [12:41] Mirv: and build and so on :) [12:41] Mirv: need some help with testing? [12:41] sil2100: can you help on the testing ^ [12:41] * jdstrand doesn't actually know the impact of the bug [12:41] the alarm saves, and we get the DENial, but when the alarm time comes, it _does_ trigger, just makes no noise. [12:41] jdstrand: do you think it can impact the current bug we are talking about? [12:41] I just assume that things won't work right cause it can't write out its .conf file [12:41] didrocks, Mirv: just in case poke me once the packages are built and I'll perform the testing as well [12:41] I have no idea. All I reported is what I saw in the log [12:41] didrocks: whowever owns this MP should have pusehd for landing it [12:41] didrocks: who owns the MP? [12:42]