[00:00] <rsalveti> ondra: awesome, please release that soon
[00:00] <rsalveti> :-)
[00:00] <ondra> rsalveti: actually just working on dualboot now, adding ubuntu and android update support
[00:01] <rsalveti> awesome
[00:01] <ondra> rsalveti: did you ask to use own ubuntu build with dualboot, or to have recovery functional unless you reboot to Ubuntu from the app?
[00:03] <ondra> rsalveti: BTW do we still need SWAP with 4.4.2 ports?
[00:03] <rsalveti> ondra: I was just wondering if there was any other way to update the image without downloading it from the app
[00:03] <rsalveti> as that's really really slow
[00:04] <rsalveti> ondra: we don't, will ping ogra_ tomorrow to get that disabled after our next promoted image
[00:06] <ondra> rsalveti: so I can share with you app we used at mwc, that has this feature already enabled
[00:07] <ondra> rsalveti: I did some extra tweaking and scripting, so that you can use already if you want
[00:07] <ondra> rsalveti: OK so I can drop swap from dualboot as well then
[00:08] <rsalveti> ondra: that would be nice, I believe Saviq might want that as well
[00:08] <ondra> rsalveti: I will drop this to my chinstrap then
[00:09]  * Saviq wants
[00:11] <ondra> rsalveti: okubik/public_html/humpolec/mwc
[00:12] <ondra> rsalveti: use script dualboot-one-device.sh
[00:14] <ondra> rsalveti: use param  'PUSH_CUSTOM' followed by list of the tar.xz you want to push to the phone
[00:15] <ondra> rsalveti: just remember to update app with one included there, at least once
[00:18] <rsalveti> ondra: that's great, will give it a try
[00:18] <ondra> rsalveti: let me know if it works, still a bit work in progress
[00:19] <rsalveti> sure
[00:19] <ondra> rsalveti: close app and let it work, it will open app and button should be at state "resume", it will resume with your own files
[00:21] <rsalveti> ondra: hm, got app not installed after trying to install the apk
[00:21] <rsalveti> ondra: do I need to remove it first?
[00:22] <rsalveti> hm, it's a built-in app
[00:22] <ondra> rsalveti: probably not signed properly
[00:22] <rsalveti> can't even remove it
[00:23] <rsalveti> ondra: should I use UPDATE-UbuntuInstaller.zip?
[00:23] <ondra> rsalveti: adb reboot bootloader && fastboot boot recovery <CWM> && adb mount /system && adb push <UbuntuInstaller.apk> /system/app
[00:24] <rsalveti> alright
[00:24] <ondra> rsalveti: this will replace system app with one with our own key
[00:24] <rsalveti> ondra: PUSH_CUSTOM is not available in https://chinstrap.canonical.com/~okubik/humpolec/dualboot-one-device.sh
[00:24] <ondra> rsalveti: or you can remove it from system, and then you can update with adb install
[00:24] <ondra> rsalveti: humpolec/mwc/
[00:24] <Saviq> wonder how that'll work for me with adb going crazy :|
[00:25] <rsalveti> ondra: oh, sorry
[00:25] <ondra> rsalveti: sorry all the files are in mwc folder
[00:29] <rsalveti> ondra: then what should I give as arguments? device.tar.xz and ubunut.tar.xz?
[00:31] <ondra> rsalveti: yes
[00:31] <ondra> rsalveti: but ubuntu always as first!
[00:31] <ondra> rsalveti: since our brilliant overlaying, you need to have rootfs as first
[00:31] <rsalveti> ondra: oh, ok
[00:31] <Saviq> damn, that's not gonna work, wth is happening ;|
[00:32] <ondra> rsalveti: it will take any number of packages
[00:33] <ondra> rsalveti: I put there also scripts which will convert you tar.gz preinstalled into system-image package which you need for dualbootr
[00:33] <rsalveti> cool, but I'll try with the official image first, let's see
[00:33] <ondra> rsalveti: same is there for converting device image, just point that script to your out/target/product/mako
[00:33] <rsalveti> ./dualboot-one-device.sh PUSH_CUSTOM ubuntu-c6b7105334c67a0c762f84904a3dc4e7818b7e7a1a95eef6f82c149ff0bc6f44.tar.xz device-456bc5a53bcbb0481be13acacc4de673433c4ea0255ffabe0cbc35925481715d.tar.xz
[00:33] <ondra> Saviq: what are you mumbling? :)
[00:34] <ondra> rsalveti: correct
[00:34] <Saviq> ondra, my mako USB reconnects every 5s
[00:34] <ondra> rsalveti: then you are doomed, it needs almost minute to push all the files to the phone
[00:34] <rsalveti> Saviq: what do you get in your host syslog?
[00:35] <Saviq> rsalveti, usb disconnect/connect, nothing more interesting
[00:35] <ondra> rsalveti: you can also passed to it device id as first param if you have more devices, as Saviq once requested :P
[00:35] <Saviq> ;D
[00:35] <Saviq> rsalveti, http://pastebin.ubuntu.com/7122863/
[00:35] <rsalveti> ok, app was opened automatically
[00:36] <Saviq> rinse&repeate
[00:36] <Saviq> -e
[00:36] <ondra> rsalveti, Saviq if things go well, I will be able to use Ubuntu upgrader to update installed Ubuntu with deltas :)
[00:36] <Saviq> ondra, /me awaits
[00:37] <rsalveti> ondra: hm, can't see any resume in here
[00:37] <rsalveti> rm: cannot remove ‘update_command’: No such file or directory
[00:37] <Saviq> ondra, so basically instead of recovery doing that work, the app in android will?
[00:38]  * Saviq starts from scratch
[00:38] <rsalveti> Saviq: yeah
[00:38] <ondra> rsalveti: yeah, app will do it
[00:39] <rsalveti> ondra: pushed the app to /system/app, as you said
[00:39] <ondra> rsalveti: magic is to convince android not to delete downloaded update before anything happens
[00:39] <Saviq> ondra, mhm
[00:39] <rsalveti> but still can't see any resume option
[00:39] <ondra> rsalveti: hmm, and app was not running and script started the app?
[00:39] <rsalveti> ondra: yeah
[00:40] <rsalveti> running it again with the app opened
[00:40] <ondra> rsalveti: OK I wonder if version of the app is wrong
[00:40] <rsalveti> says 0.3 here
[00:40] <ondra> rsalveti: no app needs to be closed
[00:40] <rsalveti> no, still nothing
[00:40] <ondra> rsalveti: so version should be right
[00:41] <rsalveti> let me reboot and try again
[00:44] <rsalveti> no resume :-(
[00:44] <rsalveti> ondra: http://paste.ubuntu.com/7122890/
[00:44] <Saviq> we need to allow logging the phone in via QR code
[00:44] <Saviq> typing a strong password through is crazies
[00:45] <rsalveti> hahah, yeah
[00:45] <Saviq> every freakin' time
[00:45] <ondra> rsalveti: looks all good
[00:45] <ondra> rsalveti: OK uninstall the app
[00:46] <rsalveti> ondra: just remove it?
[00:46] <rsalveti> from recovery
[00:46] <ondra> rsalveti: no you can just uninstall it, we will install one from zip file
[00:47] <ondra> rsalveti: actually this could be the problem
[00:47] <ondra> rsalveti: you might still have old app
[00:47] <ondra> rsalveti: sometimes android is really stubborn to remove old app
[00:47] <ondra> rsalveti: so from recovery just delete /system/app/UbuntuInstaller.apk
[00:48] <rsalveti> right
[00:49] <rsalveti> removing, rebooting
[00:49] <Saviq> ;( reflashing phone didn't help
[00:49] <Saviq> reboot, biab
[00:50] <rsalveti> ondra: then use the zip in recovery?
[00:50] <ondra> rsalveti: no just pick app from that zip file
[00:50] <ondra> rsalveti: and install it with adb install
[00:50] <rsalveti> ondra: sorry, which zip?
[00:51] <rsalveti> https://chinstrap.canonical.com/~okubik/humpolec/mwc/recoveries/UPDATE-UbuntuInstaller-v0.3.zip ?
[00:51] <ondra> rsalveti: boot normally now and make sure app is gone
[00:51] <ondra> rsalveti: yeah that is the one
[00:51] <rsalveti> file 'UPDATE-UbuntuInstaller-v0.3.zip' does not contain AndroidManifest.xml
[00:53] <ondra> rsalveti: but you don't need that
[00:53] <ondra> rsalveti: hold a sec, i will get you the app
[00:53] <rsalveti> ondra: just grab the apk from that zip?
[00:53] <ondra> rsalveti: yeah
[00:54] <rsalveti> installed
[00:54] <ondra> rsalveti: I just replaced one in chinstrap with one from zip
[00:54] <ondra> rsalveti: with adb install?
[00:54] <ondra> rsalveti: and when you booted there wasn't dualboot app?
[00:54] <ondra> rsalveti: so now rerun script, fingers crossed
[00:55] <rsalveti> ondra: it wasn't there, so I guess it removed successfully
[00:57] <ondra> rsalveti: OK
[00:58] <rsalveti> ondra: ok, resume is available now \o/
[00:58] <Saviq> ondra, bootstrap possible with that new option, or do I need to bootstrap once before I can go with "resume install"?
[01:01] <ondra> rsalveti: sweet :)
[01:01] <ondra> Saviq: what do you mean by bootstrap now/
[01:01] <ondra> ?
[01:02] <Saviq> ondra, I freshly flashed my mako with android
[01:02] <ondra> Saviq: that's perfect
[01:02] <ondra> Saviq: app will backup your stock recovery
[01:02] <Saviq> ondra, and installed the app through recovery
[01:02] <ondra> Saviq: and once you uninstall ubuntu it will restore it
[01:02] <ondra> Saviq: no need
[01:03] <ondra> Saviq: but you will need to install SU through recovery
[01:03] <Saviq> right, SU, /me does
[01:04] <ondra> Saviq: if you don't mind app in the system partition, you can run FULL command, it will install some old Ubuntu though
[01:04] <rsalveti> ondra: we might just need to improve it to accept a build number
[01:05] <rsalveti> root@ubuntu-phablet:/# system-image-cli -i
[01:05] <rsalveti> current build number: 0
[01:05] <rsalveti> other than that, working fine
[01:05] <ondra> Saviq: find function "complete_ubuntu_instalation()"
[01:05] <ondra> rsalveti: I'm working on it now
[01:05] <ondra> rsalveti: it will be getting build number from installed ubuntu
[01:06] <rsalveti> ondra: awesome, thanks so much, you can't image how easier my life will be now hahah
[01:06] <ondra> rsalveti: so if you pass to it "version.tar.xz" it will pick correct version
[01:06] <rsalveti> tired of waiting almost one hour to get this device flashed
[01:06] <ondra> rsalveti: welcome :)
[01:06] <rsalveti> ondra: great
[01:06] <Saviq> ondra, SuperSU installed, can I just go and PUSH_CUSTOM now?
[01:06] <rsalveti> ondra: let me know when you get that working
[01:07] <ondra> rsalveti: hope soon, I will need some beta testers so I will ping you
[01:07] <ondra> Saviq: adb install UbuntuInstaller.apk?
[01:07] <rsalveti> thanks
[01:07] <Saviq> ondra, it's already installed
[01:07] <ondra> Saviq: then you can just PUSH_CUSTOM
[01:07] <Saviq> ondra, cool, let's see
[01:09] <Saviq> ondra, hmm no "resume install", only lets me choose the channel
[01:10]  * Saviq might not be using the right app
[01:12] <ondra> Saviq: you need to close the app, run the script, once that is done, script with start app with extras in the intent pointing to sideloaded packages
[01:13] <Saviq> ondra, yeah, I think I might not have installed the correct version of the app
[01:13] <ondra> Saviq: use one from the zip file, older but will work
[01:13] <Saviq> used the UPDATE v0.3
[01:13] <Saviq> now
[01:14] <Saviq> \o/
[01:15] <Saviq> ondra, it's alive! ;)
[01:16] <ondra> Saviq: nice :)
[01:16] <ondra> OK I'm off to get some sleep now
[01:17] <ondra> tomorrow guys
[01:17] <rsalveti> cya
[01:27] <Saviq> rsalveti, does the app lie about the installed ubuntu version for you as well? says image 200 from channel trusty for me, but it should be 247 (and also system-image has no idea about the number, that's what you said above?)
[01:33] <rsalveti> Saviq: yeah
[03:49] <Guest4571> i have been trying to port ubuntu touch on i9082 for past several hours.. stuck on device boot
[03:49] <Guest4571> need suggestions
[04:33] <jonahbron_> Hello, I'm working on adding a MenuBar to my QML app.  When I add it, the menu doesn't appear.  Any idea why?
[05:21] <cgfree> hi all
[05:22] <cgfree> is it going to be possible to get ubuntu touch experimentally on my samsung galaxy tab 3 smt210?
[05:23] <Nullrez> everything is possible
[05:24] <cgfree> where can I find the img?
[05:25] <Nullrez> might have to port on your own
[05:25] <cgfree> hmm sounds tricky
[07:41] <dholbach> good morning
[08:12] <Mirv> tsdgeos: I wonder if you could take a look at the calendar-app crasher bug #1294995 - trunk having it is a blocker for the actual calendar-app blocker, which is the last one preventing promoting Qt 5.2 based image
[08:13] <Mirv> it seems the trunk could see a revert that "fixes" the issue, but a crash would be good to be looked at anyway
[08:25] <tsdgeos> Mirv: let me have a quick look
[08:25] <Mirv> it's quite easy to trigger from trunk
[08:25] <tsdgeos> Mirv: desktop also?
[08:28] <tsdgeos> "Running the app on the desktop via qmlscene segfaults when manually selecting dayview as well." sayss the bug
[08:28] <Mirv> tsdgeos: yes, especially desktop since I don't know yet if people are getting that on device and I fail to remember how to upgrade trunk for click packages on device
[08:28] <tsdgeos> works for me
[08:29] <Mirv> tsdgeos: bzr branch lp:ubuntu-calendar-app, cd u*, bzr bd, dpkg -i, /usr/bin/calendar-app?
[08:30] <tsdgeos> no, not that
[08:30] <tsdgeos> let me try
[08:30] <Mirv> for me it crashes every time I click first "Week", then click "Week" again to reveal the lables again, then click Day
[08:30] <tsdgeos> i'm just doing qmlscene calendar.qml
[08:30] <tsdgeos> and that works
[08:30] <Mirv> so they managed to trigger that bug in the latest commit which now then prevents landing fixes for the AP tests
[08:30] <tsdgeos> let me see if doing what you say makes any difference
[08:30] <Mirv> the /usr/bin doesn't do anything else either
[08:33] <Mirv> also happens with LANG=C qmlscene /usr/share/calendar-app/calendar.qml
[08:34] <tsdgeos> let's see if that helps me
[08:34] <tsdgeos> maybe it just likes catalan
[08:34] <jose> hey didrocks! mind a quick PM?
[08:34] <didrocks> jose: sure
[08:36] <Mirv> tsdgeos: there's CoreDump and friends in the bug too, though, if it helps
[08:37] <tsdgeos> Mirv: i see that i did not have qtorganizer5-eds installed that seems to be needed
[08:37] <tsdgeos> let me see if that does anything
[08:37] <tsdgeos> may be the fact also that i have no appointments at all
[08:37] <tsdgeos> Mirv: do you?
[08:37] <Mirv> tsdgeos: yes to both
[08:38] <Mirv> I've appointments via evolution, and qtorganizer5-eds installed
[08:38] <tsdgeos> that may make it do more stuff than my empty thing
[08:40] <popey> Mirv: i marked bug 1294671 as a dupe of your bug 1294995 - dunno if it has more tracing, but has core dump
[08:41] <Mirv> popey: thanks. the 995 has the best trace via lp:daisy usage
[08:41] <popey> k
[08:51] <janimo`> ogra_, would it be possible to start adbd if the container fails to start as well?
[08:52] <janimo`> it helps debug while porting
[08:59] <ogra_> janimo`, i'll try to come up with something
[08:59] <ogra_> janimo`, until then just change the upstart job back to what it was i guess
[09:00] <janimo`> ogra_, I did that, sure, just thought it would be good fixed properly :)
[09:01] <ogra_> cwayne added a function to rootstock that can replace single files inside a build btw (for example the adbd job ;) )
[09:01] <janimo`> ogra_, maybe the container emit some error signal and have that too trigger adbd
[09:01] <ogra_> yeah
[09:01]  * janimo` knows too little about upstart to suggest anything else
[09:01] <ogra_> i need to find if thats possible
[09:01] <ogra_> its not so much upstart but rather lxc
[09:01] <janimo`> ogra_, for the phone I am working on I also have an overlay thingy copied over at buildd time so no biggie
[09:01] <ogra_> ah, cool
[09:02] <janimo`> ogra_, also changes can - as I learned yesterday - be added using the regular system-image deploymnt mechanism
[09:02] <janimo`> very convenient
[09:02] <ogra_> right
[09:02] <ogra_> (rootstock install just copies that script :) )
[09:03] <janimo`> I no longer know where rootstock fits in now with so many scripts and different ways of flashing a device
[09:04] <janimo`> I am glad we can finally make this port work with system-image
[09:04] <janimo`> and not the legacy layout
[09:04] <ogra_> well rootsotck is a tool for porters that dont want to bother with creating system images
[09:05] <tsdgeos> Mirv: should adding meetings from the calendar-app work?
[09:05] <popey> yes
[09:05] <tsdgeos> doesn't work here
[09:05] <popey> known bug editing them though
[09:05] <tsdgeos> maybe something is missing a dependency to evolution-data-server ?
[09:05]  * tsdgeos tries installing that
[09:06] <Mirv> it seems Olivier now provided a better backtrace with QV4_FORCE_INTERPRETER=1
[09:06] <janimo`> ogra_, right now I reuse pristine Ubuntu images and add an overlay at build time. I think this is simplest
[09:06] <ogra_> janimo`, the installer is identical to the system-image script inside the recovery but you can hand over the android system.img of your build directly (and a rootfs traball frokm cdimage) the result is identic to a s-i install
[09:06] <tsdgeos> that's better
[09:07] <tsdgeos> and now i get it to crash
[09:07] <tsdgeos> so yes it only crashes if you have data in your calendar
[09:07] <tsdgeos> and you need eds to be installed
[09:07] <tsdgeos> to be able to add data
[09:13] <mihir> my mouse pointer  flickers with dual monitors (2 LED & 1 Built-in Display) , any easy fix ??
[09:13] <mihir> ubuntu 13.10
[09:23] <Mirv> do you understand if https://code.launchpad.net/~timo-jyrinki/ubuntu-calendar-app/bug_1293489_mega-merge/+merge/211887 makes sense or not? ETOOMANYBRANCHES
[09:35] <JamesTait> Good morning all; happy World Storytelling Day! :-D
[09:37] <tsdgeos> Mirv: so found http://pastebin.com/7kVvV6kr that seems to help, but i still need a testcase for Qt
[09:46] <Mirv> tsdgeos: \o/
[09:46] <Mirv> good to have something, as one never knows when that crasher appears somewhere we can't workaround
[09:53] <timppa> Has someone tried putting a full length movie to Touch? I just copied one x264 trailer and it works, but a full length movie in same format does not show up at all
[09:55] <Mirv> timppa: sounds like worth filing a bug against https://bugs.launchpad.net/mediascanner2 or something.. I think it's possible no-one has tested a full length movie
[09:57] <timppa> Mirv: is Video lens correct "term" for it?
[09:58] <timppa> Mirv: and where can I find logs for the mediascanner?
[10:03] <Mirv> timppa: yes, video lens. my knowledge on the media side is not too deep, but it seems there are log files under .cache/upstart/mediascanner.log
[10:03] <timppa> Mirv: I'll have a look on those also
[10:03] <timppa> Mirv: thanks
[10:03] <Mirv> np
[10:04] <Mirv> yes, I can see stuff happening when I do tail -f mediascanner.log and then copy videos in
[10:07] <timppa> Mirv: I see error: Unable to discover /home/phablet/Videos/filename.mp4, error code: 5
[10:08] <Mirv> timppa: oh, note also mediascanner-2.0.log
[10:08] <timppa> yes, that gives a different error
[10:08] <Mirv> that seems quite clean, it gives an error for one of my media files and then "Added video" for others
[10:08] <sergiusens> Mirv, hmmm, jim has watched full movies with the media player
[10:09] <sergiusens> not sure he was monitoring the scanner
[10:10] <Mirv> ok then, maybe it's related to the more limited scope of support then. like is h264 AVC high profile supported, or only mainline/base profiles?
[10:15] <timppa> Mirv: https://bugs.launchpad.net/mediascanner2/+bug/1295062
[10:16] <popey> probably wants a distro task for that?
[10:20] <popey> timppa: mediascanner-service[2001]: ERROR error/fs-walker: Content discovery failed for "/home/phablet/Videos/Cosmos.A.Space.Time.Odyssey.S01E01.720p.HDTV.X264-DIMENSION.mkv": gst-core-error-quark(12): Your GStreamer installation is missing a plug-in.
[10:20] <popey> related?
[10:20] <ogra_> popey, shouldnt be if a trailer of the same format works
[10:21] <ogra_> (if it really *is* the same indeed)
[10:29] <timppa> ogra_: I look codec info with vlc, it *looks* the same :)
[10:29] <timppa> popey: I did not have that kind of error messages
[10:30] <popey> ok
[10:50] <asac> ChickenCutlass: https://bugs.launchpad.net/music-app/+bug/1292306
[10:50] <asac> ChickenCutlass: there is a test attached, but doubt this will really cause the issue in automation beause adb etc.
[10:50] <asac> will keep our device awake
[10:50] <asac> so guess we would need a mechanism to put phone into deep sleep for N seconds
[10:50] <asac> and have it auto wake up
[10:50] <asac> can we do that?
[11:11] <ogra_> asac, hard to tell, we would need to disable adb automatically for a certain time or so ...
[11:16] <asac> ogra_: from host side?
[11:16] <ogra_> no
[11:16] <ogra_> on the device
[11:16] <davmor2> Morning all
[11:17] <ogra_> asac, a nohup script that calls: setprop persist.sys.usb.config mtp, sleeps a while and then adds adb back to the property might work
[11:17] <asac> ChickenCutlass: do you know if the emulator has similar properties wrt to powermanagmenet as our devices? e.g. sleeping if no wake locks
[11:18] <ogra_> not sure if nohup actually works since the shell will be completely dead when adbd is off
[11:18] <ogra_> i'll do some testing later today
[11:21] <ogra_> bah, sigh
[11:21] <ogra_> http://people.canonical.com/~ogra/touch-bootcharts/ubuntu-phablet-trusty-246.png vs http://people.canonical.com/~ogra/touch-bootcharts/ubuntu-phablet-trusty-248.png ... the container starts 2sec later with 248
[11:21]  * ogra_ wonders why
[11:23] <ChickenCutlass> asac: I know we needed to turn off powerd in the emulator. it does not behave the same as the device
[11:54] <jhodapp> timppa, full length movies work just fine, it has more to do with supported codecs and profiles
[11:54] <jhodapp> timppa, I test playback with many different lengths of video files
[12:07] <mardy> dobey: hi! About your question on enabling account plugins only on desktop/touch, please file a bug
[12:07] <awafaa> erm, is there no email client just the gmail one? also is there a way to access caldav/carddav/webdav resources?
[12:07] <mardy> dobey: I'm afraid that this will require a FFe, and in that case if you took care of the bug his would save me quite some time :-)
[12:08] <mardy> awafaa: an email client is in development
[12:08] <awafaa> mardy: ah, thanks
[12:44] <asac> zsombi: any idea why this wasn't merged/landed yet? is it not ready or something? https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/statesaver-discard-shutdown/+merge/205042
[12:45] <zsombi> asac: it was blocked because of Qt5.2 landing, so we have to redo the tests now with 5.2. once those are done, we can land it
[12:48] <asac> zsombi: ok please check with didrocks. thought it was one of the thigns pat scheduled for landing asap after qt5.2
[12:48] <asac> e.g. critical issues before promotion
[12:48] <asac> so please follow through i would assume
[12:48] <didrocks> zsombi: there is an issue with alarm sound not working
[12:49] <didrocks> that popey and davmor2 discovered
[12:49] <didrocks> is that supposed to fix it?
[12:49] <zsombi> didrocks: that's not muy business :) charles may know more about that
[12:49] <didrocks> zsombi: hum, so you just checked that there is no more denials?
[12:49] <didrocks> in syslog
[12:49] <zsombi> didrocks: I don't think so, that MR only fixes the statesaver state file
[12:50] <zsombi> didrocks: Alarms API uses QOrganizer, and has nothing to do with setting sounds or not. Not even with playing.
[12:50] <didrocks> zsombi: so, you think the denials are not due to a missing profile file and then is denied to play sound?
[12:51] <didrocks> this wasn't what the denials were about?
[12:52] <zsombi> didrocks: my comments were for 14:48 <didrocks> zsombi: there is an issue with alarm sound not working
[12:53] <didrocks> zsombi: yeah, can you explain with dumb words what's the impact of the bug exactly, and what it fixes?
[12:53] <didrocks> like "can't set an alarm clock"
[12:53] <didrocks> or anything else?
[12:56] <zsombi> didrocks: from teh comments in the bug it seemed that StateSaver is the guilty as the config path seemed to be related to that feature. the MR I proposed was about to solve the placement of the State database from ~!/.config to /tmp. That's what the bug sais. Nothing about the ability to get alarm sounds or not.
[12:57] <zsombi> ~/config is the proper path
[12:57] <didrocks> zsombi: right, and this sate file is used to set an alarm, right?
[12:57] <zsombi> didrocks: nope
[12:58] <zsombi> didrocks: the StateSave is not doing anythiong for the alarms, unless the app uses it for that. But if it does, then it does wrong. StateSaver is to save th eapp state in case it is closed by the app lifecycle manager
[12:59] <didrocks> zsombi: ah, ok, making sense and so, not that critical for now
[12:59] <didrocks> thanks
[12:59] <zsombi> didrocks: welcome :)
[13:02] <asac> zsombi: can you check out this alarm bug? seems its a qt 5.2 regression and one of two things blocking promotion
[13:02] <asac> zsombi: or find sonmeone in sdk team who can see? i think the alarm clock didnt change, so something else must have landed that broke it
[13:03] <asac> didrocks: sergiusens: can you confirm that alarm app didnt land recently?
[13:03] <zsombi> asac which bug?
[13:03] <asac> zsombi: the bug you talked with didrocks about
[13:03] <asac> alarm broken since qt5.2 landing
[13:03]  * asac wonders why that wasn't fixed. thought we had that solved - shrug
[13:03] <sergiusens> asac, I can't confirm; balloons has been doing most of the uploads of late in coordination with didrocks
[13:03] <asac> or guess we didnt try the app
[13:04] <asac> just the APs
[13:04] <didrocks> asac: it didn't land
[13:04] <sergiusens> asac, by alarms you mean calendar?
[13:04] <sergiusens> clock
[13:04] <didrocks> last version was before 5.2 landing
[13:04] <didrocks> sergiusens: clock yep
[13:04] <asac> sergiusens: didrocks has the details
[13:04] <asac> not sure what the bugid is
[13:04] <sergiusens> I can check on the webstore
[13:04] <didrocks> I just got the info it started to break with the 5.2 landing image
[13:04] <didrocks> http://people.canonical.com/~ogra/touch-image-stats/20140314.1.changes
[13:05] <didrocks> sergiusens: if you can double check, I quickly went to all diff from last image to that one ^
[13:05] <sergiusens> New version: 1.0.373 on 2014-03-10 22:25 - 1 week, 2 days ago
[13:05] <didrocks> popey: davmor2: do you have a bug for it?
[13:05] <sergiusens> Ran 20 tests in 545.735s
[13:05] <sergiusens> OK
[13:05] <didrocks> sergiusens: yeah, so before 5.2
[13:05] <zsombi> asac: didrocks: so it ends up that the bug is on the critical path then?
[13:05] <popey> didrocks: for which?
[13:05] <didrocks> sergiusens: there is no test for alarm
[13:05] <asac> zsombi: alarms broken, yes
[13:05] <didrocks> zsombi: just before the promotion, yeah :/
[13:05] <didrocks> popey: the alarm regression
[13:05] <asac> zsombi: it was even critical before qt5.2
[13:05] <popey> not yet
[13:06] <asac> zsombi: not sure why its still not working. thought we fixed that. guess something fell somewhere through the crack.
[13:06] <sergiusens> didrocks, one thing that needs to be tested as well is upgrade from trusty --wipe to trusty-proposed; some apps don't seem to handle the transition
[13:06] <sergiusens> at least for me
[13:06] <zsombi> asac: didrocks: are we talking about this bug #1288742?
[13:07] <didrocks> zsombi: it was raised as a possible cause for the bug by the security team, but seems it's not as per our discussion
[13:07] <t1mp> is there a bug report then for the bug that is being discussed now?
[13:08] <didrocks> sergiusens: you lost data? I guess we'll have only time from stable to stable
[13:08] <zsombi> didrocks: ok, I got confused again... :)
[13:08] <didrocks> 14:05:18       didrocks | popey: davmor2: do you have a bug for it?
[13:08] <didrocks> 14:05:30          popey | didrocks: for which?
[13:08] <didrocks> 14:05:54          popey | not yet
[13:08] <didrocks> t1mp: ^
[13:09] <t1mp> ok, thanks
[13:09] <davmor2> popey: are you midst filing one if not I can
[13:09] <popey> go for it
[13:11] <sergiusens> didrocks, no, music app doesn't launch
[13:12] <ogra_> sergiusens, rsalveti [   13.755104] init: cannot find '/system/bin/ubuntuappmanager.disabled', disabling 'ubuntuappmanager'
[13:12] <didrocks> sergiusens: "nice" :/
[13:12] <ogra_> how about we finally rip that stuff out
[13:12] <didrocks> sergiusens: do you have a bug report/reproducer for that?
[13:12] <didrocks> sergiusens: while we are on the list of criticals
[13:12] <davmor2> popey: on it
[13:14] <timppa> jhodapp: which codecs are supported?
[13:14] <sergiusens> didrocks, ogra_ that's been like that since we switched to mir...
[13:14] <ogra_> ?
[13:15] <jhodapp> timppa, depends on your hardware
[13:15] <didrocks> sergiusens: ah, so it's more a stable to stable…
[13:15] <didrocks> test
[13:15] <didrocks> then
[13:15] <ogra_> (sorry my comment was unrelated to the other conversation)
[13:15] <didrocks> not for next image
[13:15] <sergiusens> ogra_, that is only used for surfaceflinger
[13:15] <timppa> jhodapp: Nexus4 and Nexus7 (2013)
[13:15] <jhodapp> timppa, check out /etc/media_codecs.xml
[13:16] <ogra_> sergiusens, well, didnt we want to drop support for it once screenshooting works on Mir ?
[13:16] <timppa> jhodapp: ok
[13:16] <sergiusens> didrocks, yeah, my test is from trusty to trusty proposed assuming the next trusty proposed is going to be the next stable
[13:16] <didrocks> sergiusens: so it's not there since Mir is in
[13:16] <sergiusens> ogra_, that's a tough question; I would of dropped it ages ago
[13:16] <sergiusens> ogra_, that things was supposed to last a week
[13:16] <sergiusens> thing*
[13:16] <ogra_> heh
[13:17]  * didrocks is confused
[13:17] <ogra_> lets talk about it in the standup
[13:17] <timppa> jhodapp: no such file!?
[13:17] <jhodapp> timppa, do a find for it, must have been moved
[13:17] <didrocks> davmor2: any bug that we can give to zsombi and t1mp?
[13:17] <didrocks> sergiusens: tell me once you get a bug for it, seems it needs to be on the blocker list
[13:18] <davmor2> t1mp, popey, didrocks, zsombi: bug #1295122
[13:18] <timppa> jhodapp: /android/system/etc/media_codecs.xml
[13:18] <jhodapp> timppa, yeah that's it
[13:19] <sergiusens> didrocks, yeah, I'll need to reproduce cleanly which means wiping MY phone ;)
[13:19] <zsombi> didrocks: ok, this is something charles can do
[13:19] <timppa> jhodapp: basically if the file works on android it should work with ubuntu?
[13:19] <didrocks> davmor2: hum, why indicator-datetime?
[13:19] <asac> zsombi: is charles avaialble?
[13:19] <popey> didrocks: what else would it be?
[13:19] <davmor2> didrocks: popey said that it was the indicator that triggered the alarm
[13:20] <jhodapp> timppa, for the most part, but the most tested codec pair is h.264 and aac
[13:20] <didrocks> sergiusens: doing that now? I think it's not something that we should wait for having another firedrill at the last minute
[13:20] <zsombi> asac he should be available later yes
[13:20] <davmor2> didrocks: setting the alarm is working so the clock app is doing it's bit
[13:20] <asac> zsombi: how long?
[13:20] <didrocks> popey: davmor2: I don't think the service is datetime
[13:20] <asac> charles: wake up :)
[13:20] <sergiusens> didrocks, well I'm dealing with the music app now
[13:20] <asac> charles: important mission for you
[13:20] <sergiusens> didrocks, I can't parallelize this
[13:21] <didrocks> sergiusens: I thought the music app issue wasn't critical where you change seems to be?
[13:21] <davmor2> didrocks: feel free to change it
[13:21] <sergiusens> popey, davmor2 do you have devices to test this?
[13:21] <popey> sergiusens: "this"?
[13:21] <ogra_> no, that
[13:21] <didrocks> s/change/bug/
[13:21] <sergiusens> popey, davmor2 -> ubuntu-device-flash --wipe --channel devel ; ubuntu-device-flash --channel devel-proposed (a simulated upgrade path)
[13:21] <timppa> jhodapp: ok, thanks! I'll try to see if the file is indeed in incorrect format
[13:21] <jhodapp> ok
[13:22] <popey> sergiusens: what is that to achieve?
[13:22] <crawler2014> hi folks :)
[13:23] <zsombi> thostr_: when charles will be available?
[13:23] <sergiusens> popey, keep launching the music app :-)
[13:23] <thostr_> zsombi: in about an hour or 1.5 usually
[13:23] <asac> cjwatson: seems we have an issue that makes music-app not start when you upgrade a device from current promoted to current dev image
[13:23] <zsombi> asac: ^
[13:23] <asac> cjwatson: but that doesnt happen if you do a fresh install. think this could be us?
[13:23] <asac> or rather sdk?
[13:24] <popey> sergiusens: ok
[13:24] <crawler2014> I was wondering whether I could contribute some things to get ubuntu / ubuntu touch working on RK3188-based tablets like the Vido N90 I have
[13:24] <asac> cjwatson: see with sergiusens, didrocks and friends for details ... think they filed a bug alread
[13:24] <asac> tedg: ^^ see the two lines for colin above
[13:24] <asac> guess you might also know
[13:24] <didrocks> asac: I'm waiting for sergiusens to file one :) but seems popey will reproduce first
[13:25] <crawler2014> I could provide the partition scheme and boot options, firmware files if needed :)
[13:25] <popey> sergiusens: flashing 237 on flo
[13:26] <tedg> asac, Do we know what error it's giving?
[13:27] <cjwatson> asac: do we have logs or anything?
[13:27] <cjwatson> snap
[13:27] <tedg> :-)
[13:27] <crawler2014> could anybody give me some advice ?
[13:28] <asac> sergiusens: didrocks: have to run to lunch, can you give tedg and cjwatson info about the startup issue?
[13:28] <didrocks> dholbach: maybe you would know (porting guide? ^)
[13:28] <asac> thanks
[13:28] <asac> will be back in 20 i hope
[13:28] <a_muva_>  I think I found a bug. My current build number is 237, but if I want to upgrade, the system is upgrading to 237. phone is nexus 4.
[13:28] <didrocks> asac: sergiusens has the info, I don't…
[13:28] <tedg> We need a way to convince apport to file bugs on click packages.
[13:28] <tedg> We've got an "app failed" upstart job, we could just upload automatically.
[13:29] <cjwatson> errors would be better for that
[13:29] <sergiusens> tedg, what I see with upstart-app-launch and my instance of music is that it doesn't error but I don't get music to start up in any way
[13:29] <didrocks> asac: lunch? lucky you :p
[13:29] <sergiusens> afaik ev has that in his agenda
[13:29] <tedg> Certainly, but isn't apport effectively the frontend for errors?
[13:29] <cjwatson> sure, you just specifically said "bugs" that's all
[13:30] <tedg> sergiusens, Anything in the log file in ~/.cache/upstart/application*music*.log
[13:30] <tedg> cjwatson, Heh, we need a name for errors DB entries. pre-bugs? ;-)
[13:30] <sergiusens> tedg, there is no log file created
[13:31] <popey> sergiusens: want me to put music on this and play with the app between flashes?
[13:31] <tedg> No log file...
[13:31] <tedg> sergiusens, Do you have a device doing this right now?
[13:31] <cjwatson> sergiusens: can you check whether the music entry in ~/.local/share/applications/ exists and whether the various paths in it all point to sane places?
[13:32] <sergiusens> cjwatson, sure one sec
[13:32] <tedg> sergiusens, If so, can you run this and see if a log file gets created on next run?  initctl set-env --global G_MESSAGES_DEBUG=all
[13:32] <sergiusens> tedg, yes
[13:39] <sergiusens> tedg, cjwatson paths seem to be correct http://paste.ubuntu.com/7125271/ ; thanks for the set-env thing
[13:39] <sergiusens> I do notice there's still a -I in there; not sure if added back or never removed as it's using the import path upstart-app-launch sets now
[13:40] <sergiusens> the error would be different as well
[13:40] <cjwatson> sergiusens: paths> agreed.  doesn't look like a click problem
[13:41] <crawler2014> well...that's sad...I'd love to participate, but if noone cares...
[13:42] <ogra_> crawler2014, see the porting doc from the channel topic
[13:42] <tedg> sergiusens, Yeah, I don't see anything odd in that log other than the icon seems to be in the root instead of in "images"
[13:42] <tedg> Clearly shouldn't break starting up though.
[13:43] <ogra_> crawler2014, we officially only suppport a few nexus devices, other doing ports is up to the community
[13:45] <tedg> sergiusens, I'm a little concerned that you're not getting lttng errors.
[13:46] <tedg> I hadn't figured out how to suppress those yet.
[13:46] <sergiusens> tedg, music is unconfined
[13:47] <tedg> sergiusens, Ah, okay.
[13:48] <sergiusens> tedg, wait; am I supposed to see the qt import dir setup when launching with debug?
[13:48] <sergiusens> or is that not printed/logged?
[13:48] <tedg> sergiusens, Let me check
[13:49] <tedg> sergiusens, No, not printed.
[13:50] <tedg> sergiusens, Where is the vala comment comming from?
[13:54] <sergiusens> tedg, let me launch again and see if I can get the process
[13:54] <tedg> Ah, got it, that's the zg posting
[13:54] <mterry> fginther, so autopilot-testrunner-touch-saucy involves unlocking the screen
[13:54] <mterry> fginther, and I'm trying to land a branch that separates the greeter
[13:55] <mterry> fginther, what's the best way to land a branch against autopilot-testrunner-touch-saucy in sync with a code change like that?  Can it be part of the same silo?
[13:55] <sergiusens> tedg, hmm, is it ok for upstart-app-launch to return 255?
[13:56] <sergiusens> guess not
[13:57] <cjwatson> sergiusens: that kind of sounds like an exec failure ...
[13:58] <cjwatson> sergiusens: does that aa-exec-click command from the .desktop file work if you run it with the current directory set to the value of Path?
[13:58] <cjwatson> er and I suppose you have to substitute %f too
[13:59] <cjwatson> I think it expands to empty?
[14:00] <popey> sergiusens: flashed latest unpromoted on flo.. unity is in a restart loop ☹
[14:00] <ogra_> popey, not here with OTA
[14:00] <sergiusens> cjwatson, no worries; not the first time I launch with that; but I would need to set the import paths manually (which u-a-l does for me)
[14:00] <popey> ogra_: i clean flashed promoted image with --wipe, put some music on it, then flashed latest unpromoted
[14:00] <popey> sergiusens: ^^
[14:01] <sergiusens> popey, that's worse than my issues
[14:01] <ogra_> popey, right, i just did an OTA upgrade here, no issues with that (though i dont have any music on it)
[14:01] <sergiusens> ogra_, well you've been getting gradual improvements; this simulates ota from trusty current to trusty next
[14:02] <sergiusens> which has a bundle of changes
[14:03] <popey> yeah, rebooted device and now it's just not starting unity without dying
[14:04] <tedg> sergiusens, Sorry, got pulled into a HO.
[14:05] <tedg> sergiusens, Yes, I'd agree with cjwatson that it's probably an exec failure.
[14:05] <davmor2> sergiusens: on my flo the music app opened
[14:05] <sergiusens> davmor2, with simulated upgrade or a fresh flash
[14:05]  * sergiusens knows that it works fresh
[14:06] <davmor2> sergiusens: with the command you gave me
[14:06] <sergiusens> hmm
[14:06] <sergiusens> davmor2, ok; then I'll drop this one for now
[14:06] <davmor2> sergiusens: meh hang on
[14:07] <sergiusens> uh oh
[14:07] <davmor2> sergiusens: it looks like it only ran the first flash and not the second I'm on 237
[14:08] <davmor2> sergiusens: reflashing the second part
[14:08] <tedg> sergiusens, I guess the next thing I'd do is see if the apparmor profile is correct.
[14:08] <tedg> sergiusens, Is there a deny in the system logs?
[14:09] <sergiusens> tedg, nope; it's unconfined :-)
[14:09] <tedg> sergiusens, It can't be unconfined and be a click, it has to a null confinement.
[14:10] <davmor2> sergiusens: D'oh that's why.  The second flash tried to run as soon as the first exited but it was still rebooting the device at the time
[14:10] <tedg> sergiusens, sudo aa-status | grep music
[14:11] <jdstrand> well, I don't know what 'null confinement' means
[14:11] <jdstrand> I like to use the term 'effectively unconfined profile'
[14:11] <tedg> Heh
[14:12] <jdstrand> or 'it uses the unconfined template'
[14:12] <popey> phablet@ubuntu-phablet:~$ sudo aa-status | grep music com.ubuntu.music_music_1.3.385
[14:12] <sergiusens> tedg, it uses the unconfined template as jdstrand mentions
[14:13] <tedg> popey, Are you implying you don't have an apparmor profile for it?
[14:13] <jdstrand> popey: curious-- does 'apparmor_parser -p /var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.385 || echo fail' say fail?
[14:13] <popey> i am not implying anything
[14:13] <popey> i pasted what you typed ☻
[14:13] <tedg> popey, Was there output?
[14:13] <jdstrand> tedg: his paste shows it has a profile
[14:13] <popey> i get stuff
[14:13] <popey> com.ubuntu.music_music_1.3.385 was the output tedg
[14:13] <tedg> Oh, I didn't get the return.
[14:13] <popey> sorry
[14:14] <popey> #blameadb
[14:14] <davmor2> sergiusens: music app still opened it just took it's time
[14:14] <popey> jdstrand: no, it doesn't say fail
[14:14] <jdstrand> ok, good
[14:15] <sergiusens> tedg, http://paste.ubuntu.com/7125434/
[14:15] <popey> more worrying to me is that unity flat out wont start
[14:15] <didrocks> popey: so, you have the "after upgrade" issue?
[14:15] <sergiusens> didrocks, he has a different issue though
[14:15] <popey> didrocks: I have _an_ issue, dunno if it's one others have seen
[14:15] <didrocks> hum
[14:15] <popey> unity keeps respawning
[14:16] <didrocks> nice
[14:16] <sergiusens> didrocks, the music stopping problem isn't music app; seems platform
[14:16] <sergiusens> all signals are blocked on suspend
[14:16] <popey> blimey, finally stopped respawning, no idea why.
[14:17] <didrocks> sergiusens: yeah, discussing that with ogra_
[14:17] <didrocks> sergiusens: so alarm can be the same…
[14:17] <ogra_> yeah
[14:17] <sergiusens> yup
[14:17] <ogra_> i would say thats very likely
[14:18]  * ogra_ pets if you set an alarm that goes off when suspended you will hear the alarm as soon as you wake up the device
[14:19] <davmor2> ogra_: no you see the notification but not the alarm
[14:19] <ogra_> ah
[14:19] <davmor2> ogra_: if you wake it just before it is meant to go off it works
[14:19] <ogra_> right
[14:20] <tedg> sergiusens, Hmm, this is weird. Can you copy the /usr/share/upstart/sessions/application-click.conf to ~/.config/upstart/ and then change the "exec" to a script dumping the environment? That'd tell us if it's getting to exec-line-exec at least.
[14:21] <davmor2> ogra_: but you know my cure all for getting things fixed is I blame popey (tm) he blames this ogra_ dude and magically it works in the next image  ;)
[14:23] <sergiusens> tedg, sure; give me a sec on that though
[14:24] <tedg> sergiusens, Thanks!
[14:24] <charles> asac, zsombi, thostr_: looking at the ticket now
[14:24] <asac> thanks
[14:24] <asac> very urgent :P
[14:25] <ogra_> davmor2, heh
[14:25] <charles> asac, so there are at least three things going on in this ticket
[14:25] <popey> didrocks: gonna try and reproduce. I suspect it may be because I had a /userdata/.writable_image hanging around. trying to prove/disprove that.
[14:26] <thostr_> charles: fyi: (03:15:10 PM) ogra_: asac, thostr_, so we nailed the issue down to "*all* events get queued when suspended" volume changed as well as playing the next song from the playlist (and i suspect also alarms) get queued up as long as the screen is off ... and get applied immediately when we wake up the device
[14:26] <asac> cool
[14:26] <asac> hope thats it
[14:26] <ogra_> the issue spreads across too many channels :P
[14:26] <didrocks> popey: and, let's hope so
[14:26] <davmor2> popey: there is a bug for that, that I think didrocks assigned himself to that the .writable_image isn't being removed by ubuntu-device-flash
[14:26] <ogra_> (3 at least)
[14:27] <popey> thats a separate issue, but yes, i am aware of it davmor2 thanks ㋛
[14:27] <sergiusens> davmor2, didrocks right, and I don't intend to fix that; should work just like the on image upgrader but with full images
[14:33] <asac> TOPIC: qt events not getting processed when screen off - PoC: Saviq and kgunn :)
[14:33] <ogra_> :)
[14:33] <sil2100> ;)
[14:34] <charles> thostr_, popey, asac, zsombi, ogra_: it's already a known issue that the alarms don't work correctly on suspend, we need the hardware alarm API to land in platform-api before that can be resolved
[14:34] <charles> from popey's video it looks like it's working when not suspended
[14:35] <asac> charles: what introduced this bug?
[14:35] <sergiusens> but wrt to music; it was working before qt 5.2
[14:35] <ogra_> charles, ok, so it is not related to the swallowing of events with all other Qt apps then
[14:35] <asac> charles: i was told alarms were fixed even before we landed qt5.2 :)
[14:35] <ogra_> they used to work, yeah
[14:35] <Saviq> sergiusens, exactly, I suspect that's what can be causing it - Qt might have decided that "since I'm not rendering, I can't do anything, so why would I deliver any events"
[14:35] <charles> asac, nothing's introduced this bug; it's always been there. The plan all along has been for tvoss to add hardware alarm support to platform-api s.t. indicator-datetime can wake up the phone to make snap decisions
[14:35] <asac> the cases that didnt work are ok to continue not working
[14:35] <ogra_> (as long as you were on UTC)
[14:36] <asac> charles: right, but we see a new bug
[14:36] <asac> afaik
[14:36] <Saviq> sergiusens, which kind of makes sense for a UI app
[14:36] <asac> that one is to be investigated
[14:36] <asac> the old one we dont care for today
[14:36] <tvoss> ogra_, they never worked, n4 just didn't go to deep sleep
[14:36]  * ogra_ knows that davmor2 and popey have been testing alarms before
[14:36] <charles> asac, walk me through what you're seeing that's different here?
[14:37] <popey> so this is not "alarms dont work when they used to" but "suspend now works where it never used to"?
[14:37] <ogra_> charles, we see an issue where all events (vol up/down, music playback) get queued when the device is suspended and get applied as soon as you wake it up
[14:37] <charles> popey: I believe that's correct, yes
[14:37] <popey> ok.
[14:37] <ogra_> charles, there was suspicion that alarms are affected by the same issue
[14:38] <tvoss> popey, right, deep sleep was broken on the n4
[14:38] <tvoss> ChickenCutlass, ^ correct?
[14:38] <ogra_> tvoss, still is afaik
[14:38] <davmor2> ogra_: I've only tested it on active systems as I was informed that the alarms didn't activate the phone if it was in sleep, popey it seems went the extra step
[14:38] <ogra_> tvoss, it wasnt fixed yet
[14:38] <ogra_> unless rsalveti did a secret upload with a fix :P
[14:38] <ChickenCutlass> tvoss, yes, deep sleep is currently not correct on the n4
[14:38] <Saviq> ogra_, charles, tvoss, I don't think the "all events are queued" is related to deep sleep, it probably can't go into deep sleep within the 5s that the issue still shows if you suspend after having moved to the end of a song
[14:38] <popey> Indeed, on #237 (pre-5.2, stable image) I can set an alarm, and turn off the sceen. The alarm *does* sound.
[14:38] <ogra_> ChickenCutlass, but that didnt change
[14:38] <ChickenCutlass> right
[14:39] <ChickenCutlass> did not change
[14:39] <ogra_> Saviq, right, no changes wrt deep sleep
[14:39] <Saviq> or vol up/down straight after turning the display off
[14:39] <ogra_> it was and still is broken
[14:39] <Saviq> so what I *think* is happening is Qt internally queues all events when it can't render, only thing that makes sense
[14:39] <ogra_> Saviq, yeah
[14:39] <tvoss> Saviq, yup, that makes sense
[14:39] <sergiusens> Saviq, your comment makes sense
[14:39] <ogra_> i'm with you on this one
[14:40] <rsalveti> tvoss: ogra_: deep sleep is broken by default :-)
[14:40] <rsalveti> and won't be fixed
[14:40] <popey> Saviq: yes, now you mention it I have seen the clock on the welcome screen do a "fast forward" from 12:18 to 12:40 and all minutes in between when i woke my phone earlier
[14:40] <rsalveti> this is an issue with the original kernel and image
[14:40] <ogra_> rsalveti, thats mean !
[14:40] <rsalveti> modem issue
[14:40] <ogra_> yeah
[14:40] <popey> just reproduced it again
[14:41] <Saviq> popey, oh yeah, that always happens
[14:41] <ogra_> yep
[14:41] <rsalveti> ogra_: bug 1267570
[14:41] <popey> i have only ever seen it jump
[14:41] <popey> not seen it actually display every minute inbetween. hey ho
[14:41] <Saviq> popey, you don't pay attention
[14:41] <popey> hah
[14:41] <popey> true
[14:41] <popey> ooh, shiny
[14:41] <Saviq> popey, it's worse now with deep sleep
[14:41] <ogra_> no deep sleep
[14:41] <ogra_> see the bug above
[14:41] <Saviq> or whatever
[14:42] <Saviq> popey, 'cause it would take 5s to update after a night on the nightstand
[14:42] <Saviq> for me
[14:42] <charles> hm, one thing here is that indicator-datetime isn't (yet) using the Qt stack to play sounds
[14:42] <ogra_> Saviq, might be the nightstand
[14:42] <ogra_> :P
[14:42] <sergiusens> Saviq, fwiw; the music problem and the EOS signal happens with the cable plugged in
[14:42] <ogra_> same for vol up/dn
[14:42] <sergiusens> when I turn the screen on, it gets the EOS signal and goes to the next track
[14:43] <charles> (see https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1283065 -- it's currently going directly to PA)
[14:43] <ChickenCutlass> sergiusens, not for me
[14:43] <charles> so that might explain why popey is hearing the alarm go off even when the screen is darkened...
[14:43] <ChickenCutlass> sergiusens, If I have USB connected -- I still do not get events
[14:43] <ogra_> ChickenCutlass, i think thats what he said
[14:43] <sergiusens> ChickenCutlass, yeah, that's what I said; but constrained it to EOS
[14:43] <ChickenCutlass> ogra_, sergiusens lol right
[14:43] <ChickenCutlass> sorry
[14:44] <davmor2> sergiusens, Saviq: confirmed I have the lead in my flo and the end of the track playing has just happened and it has stopped playing
[14:44] <sergiusens> ChickenCutlass, just trying to say I had an adb shell tail -f running
[14:44] <ChickenCutlass> right
[14:44] <sergiusens> so deep sleep seems rather impossible
[14:44] <ChickenCutlass> it is not a deep sleep issue
[14:45] <sergiusens> exactly
[14:45]  * sergiusens tries to clarify and rule out, seems to confuse
[14:45] <sergiusens> :)
[14:45] <Saviq> sergiusens, AFAICT unrelated to any cables :)
[14:46] <rsalveti> ogra_: we can only remove 'ubuntuappmanager' once we officially drop support for SF
[14:46] <ogra_> rsalveti, today ?
[14:46] <ogra_> :P
[14:46] <ogra_> i think the only bit that held us back was the missing screenshot capability ... which now works
[14:47] <ogra_> oh
[14:47] <ogra_> and Kaleo :P
[14:47] <ogra_> rsalveti, ignore me, i totally forgot he wants to do performance tests
[14:47] <kgunn> hehe
[14:48] <Saviq> ok, so... /me grabs a patch from Daniel that disables the "stop rendering" in mir
[14:48] <ogra_> oh ! we have such a thing ?
[14:48] <ogra_> awesome
[14:51] <rsalveti> sergiusens: didn't Saviq just reproduce the issue when forcing the screen to be on with powerd?
[14:52] <Saviq> rsalveti, no
[14:52] <Saviq> rsalveti, active != display on
[14:52]  * Saviq tries again
[14:52] <rsalveti> Saviq: so if you force the screen to be on, or disable powerd, it works?
[14:52] <rsalveti> just want to make sure it's really related with screen being off
[14:52] <Saviq> rsalveti, verifying again, but last I tried, yes - even if greeter is on screen
[14:53] <ChickenCutlass> rsalveti, yes only when screen is off
[14:53] <asac> charles: alarm was reported to work with screen off before, now its broken
[14:53] <asac> i cant walk you though. i am just here to facilityate and connect people
[14:53] <popey> bug 1295170 ☹
[14:53] <rsalveti> asac: it might be related with a suspended device
[14:53] <asac> charles: just look around whoelse is active here and engage. we all here work on the promotion issues
[14:53] <asac> which might all be related
[14:54] <rsalveti> I mean, there is a wakelock that is used by the modem, that keeps the device not suspending from time to time
[14:54] <Saviq> rsalveti, so yeah, as long as you keep the screen on (even on greeter)
[14:54] <Saviq> rsalveti, it works fine
[14:54] <ogra_> right, screen on processes all events ... screen off queues them
[14:54] <sergiusens> rsalveti, there's a wakelock requested over dbus for music that is never released as well
[14:54] <ogra_> screen on again processes the queue
[14:54] <rsalveti> awesome, so it's indeed screen related
[14:55] <rsalveti> not suspend and such
[14:55] <Saviq> nope
[14:55] <ogra_> nope
[14:55] <ChickenCutlass> rsalveti, right
[14:55] <rsalveti> sergiusens: right, that could help as well
[14:55] <sergiusens> half of the work is done now that we convinced rsalveti :-)
[14:55] <Saviq> ok, so dandrader's code won't help, he just didn't SIGSTOP the apps
[14:55] <Saviq> \o/
[14:55] <ChickenCutlass> lol
[14:55] <ogra_> heh
[14:55]  * ogra_ makes some meeting coffee
[14:57] <rsalveti> sergiusens: just making sure because people were running like crazy spending time on this as well
[14:57] <Saviq> kgunn, ok, can we get a mir patch that would allow apps to render even though screen is off?
[14:57] <ChickenCutlass> sergiusens, I think rsalveti just does not beleive us
[14:57] <ChickenCutlass> lol
[14:57] <kgunn> Saviq: maybe...
[14:57] <sergiusens> true
[14:58] <Saviq> kgunn, would help greatly with testing the theory
[14:58] <ogra_> ChickenCutlass, pfft ... the beachboy ...
[14:58] <kgunn> Saviq: because if the hw doesn't flip then we'd queue the buffers and be stuck...
[14:58] <kgunn> depends a little on the hw ability to consume
[14:58] <Saviq> kgunn, or discard them?
[14:58] <kgunn> yeah...we can hack it somehow
[14:58] <Saviq> kgunn, the usual frame drops?
[14:58] <kgunn> you don't care about artefacts right ?
[14:58] <Saviq> kgunn, nah
[14:59] <rsalveti> wonder when this started to happen
[14:59] <kgunn> AlbertA: ^ could we just ignore screen state ?
[14:59] <Saviq> kgunn, I just want to test the theory that indeed stopping the rendering messes with the Qt event system
[14:59] <kgunn> hack for testing
[14:59] <rsalveti> probably part of mir that landed right before qt
[14:59] <ogra_> rsalveti, 5,2
[14:59] <ogra_> well, around that time at least
[14:59] <Saviq> rsalveti, yeah, another thing that makes me think it's Qt → this must've happened with Qt 5.2
[14:59] <rsalveti> ogra_: not sure if only qt related, could be qt + mir or just mir
[15:00] <ogra_> rsalveti, right, we landed to much around the same time (again)
[15:00] <Saviq> which one's the first Qt 5.2 image again?
[15:00] <rsalveti> but we got an image before doing the qt switch
[15:00] <kgunn> Saviq:  so do you actually want 2 test patches ??....e.g. one that allows renders while screen off...and then a toggle to "stop rendering" in mir/block basically while screen is on ?
[15:00] <kgunn> AlbertA: ^
[15:00] <Saviq> kgunn, that could work, too
[15:01] <ogra_> Saviq, http://people.canonical.com/~ogra/touch-image-stats/238.changes
[15:01] <Saviq> kgunn, as long as I can make mir block the rendering without SIGSTOPing the app
[15:01] <Saviq> ogra_, !
[15:01] <Saviq> ok so no mir upgrade there
[15:01] <ogra_> Saviq, so 237 was the last non 5.2 one
[15:01]  * Saviq flashes238
[15:01] <kgunn> AlbertA: i was about to say as quick and dirty as you like...but not with SIGSTOP on apps :)
[15:01] <kgunn> he already had that patch :)
[15:01] <rsalveti> yeah
[15:01] <rsalveti> let me flash 237
[15:02] <ogra_> 243 had a Mir update then
[15:02] <jibel> Saviq, I confirm that 238 is the image where bug 1292306 appeared, worked fine on 237
[15:02] <Saviq> jibel, right, so Qt
[15:03] <ogra_> and 246 had another Mir update
[15:04]  * Saviq uses ondra's WiP way to flash dual-boot without downloading on the device :>
[15:04] <mterry> elopio, maybe you can help me with a testing problem with my split greeter branches...  How would I propose a branch to autopilot-testrunner-touch-saucy that would land in conjunction with a code change?  Can I just add it to the silo?
[15:05] <mpt> awe, sorry I had to leave early, I had another call. One more question: Is it ever the case that when you use the same APN for Internet and for MMS, you use different user name and/or password for Internet and for MMS?
[15:05] <elopio> mterry: I have never touched autopilot-testrunner-touch-saucy. But I have seen people adding to the silos all the changes that need to be landed at the same time, even if they are from different projects.
[15:06] <elopio> mterry: the ci vanguard should help you with that.
[15:06] <Saviq> mterry, there's no way to do that atm :|
[15:06] <mterry> elopio, good point
[15:06] <mterry> Saviq, bummer  :(
[15:07] <mterry> Saviq, ah...  but I bet I can make my change work with pre and post split code....
[15:07] <Saviq> mterry, only way is to actually flash a device and run the tests that you wanted to run after dist-upgrading from a silo
[15:07] <elopio> Saviq: because is on autopilot-testrunner-touch-saucy, or because we can't land two projects in conjunction?
[15:07] <Saviq> elopio, because the job doesn't know how to use PPAs
[15:07] <didrocks> popey: sergiusens: on the upgrade issue, do we do one or two bugs?
[15:08] <elopio> Saviq: ah, but the autopilot guys added a script to the jenkins job that added the ppa and did the dist-upgrade
[15:08] <popey> didrocks: i have one.
[15:08] <elopio> I'm not sure if that's doable for all the jobs.
[15:08] <didrocks> popey: please send my way
[15:08] <Saviq> elopio, I'm not saying it's difficult, I'm just saying it's not there tet
[15:08] <Saviq> yet
[15:08] <Saviq> mterry, btw, whenever you're ready for a silo, let me know
[15:08] <popey> didrocks: bug 1295170
[15:08] <davmor2> popey: you have that on flo right?
[15:08] <popey> yes
[15:09] <elopio> I understand
[15:09] <davmor2> popey: so why didn't I
[15:09] <popey> only triggers once you enable wifi (I suspect it's the service going off to get media for all the music)
[15:09] <popey> look at the very explicit instructions
[15:09] <Saviq> mterry, we can now have multiple silos for a single project, only we need to make sure that we reconcile after one of them lands
[15:09] <popey> about connecting to wifi and music
[15:09] <davmor2> ah I enabled wifi in the second flash not the first let me try that again
[15:09] <didrocks> sergiusens: do you have a bug for your issue maybe?
[15:09] <didrocks> sergiusens: upgrade one
[15:09] <didrocks> as it seems quite separate
[15:09] <mterry> Saviq, I suppose I'm ready for a silo
[15:10] <mterry> Saviq, all the branches are listed in https://code.launchpad.net/~mterry/unity8/split/+merge/210664
[15:10] <mterry> Saviq, though...
[15:10] <Saviq> popey, please unity8.log to bug #1295170
[15:10] <mterry> Saviq, did I hear something about how a branch can't be in two silos?
[15:10] <popey> Saviq: k
[15:10] <Saviq> mterry, it can
[15:10] <Saviq> mterry, only when it lands in one
[15:10] <mterry> Saviq, ok, great
[15:10] <mterry> Saviq, I expect some of these branches I need will land separately
[15:11] <Saviq> mterry, sure, that's fine
[15:11] <Saviq> mterry, we'll remove them from the silo then
[15:11] <Saviq> mterry, and resync stuff with trunks
[15:11] <mterry> Saviq, so all the branches listed in that merge, plus the merge itself is needed (lp:~mterry/unity8/split)
[15:11] <Saviq> mterry, ok, will let you know
[15:12] <Saviq> popey, and there's no unity8 .crash is there?
[15:12] <mterry> Saviq, for lightdm 1.9.13, I guess just do lp:lightdm
[15:12] <popey> Saviq: no
[15:12] <Saviq> mterry, does it need a rebuild?
[15:12] <popey> Saviq: uploaded unity8.log
[15:12] <Saviq> popey, thanks!
[15:12] <mterry> Saviq, does what?
[15:13] <Saviq> mterry, does lightdm need a rebuild? or is it just not yet released?
[15:13] <mterry> Saviq, just not yet released
[15:13] <mterry> Saviq, branch got merged to trunk, but not in trusty
[15:13] <Saviq> mterry, please do a temporary no-change MP
[15:13] <mterry> Saviq, for silo purposes?
[15:13] <Saviq> mterry, yeah, they can only deal with MP
[15:13] <mterry> ok
[15:14] <Saviq> mterry, or well, we could dput, but same difference
[15:14] <Saviq> mterry, can be set to WiP straight away or something
[15:14] <Saviq> mterry, silos don't care
[15:14] <dholbach> didrocks, sorry - I was not around... what about the porting guide?
[15:15] <Saviq> :'( ondra's way doesn't boot
[15:15] <didrocks> dholbach: I don't have the trace and can't find it easily, when I poke you, someone wanted to have porting info
[15:16] <mterry> Saviq, https://code.launchpad.net/~mterry/lightdm/fake-no-change-mp/+merge/211969
[15:16] <dholbach> didrocks, yeah, I'm not an expert - I never ported anything myself - I just helped put the docs up and advertise them
[15:16] <didrocks> yeah, not sure if the doc is up to date though
[15:17] <dholbach> didrocks, we always said "yeah, we need to rework some bits again", but probably never got around (if the comment was about some information missing?)
[15:17] <didrocks> ok
[15:17] <Saviq> mterry, thanks
[15:18] <Saviq> mterry, that not released yet either https://code.launchpad.net/~robertcarr/mir/remove-ensure-display-powered/+merge/209734 ?
[15:18] <mterry> Saviq, right
[15:18]  * Saviq wonders how silos will deal with that
[15:19] <Saviq> didrocks, I wanted to prepare a silo with ↑ for testing the split greeter, but that branch is against lp:mir/devel, will silos cope with that?
[15:20] <mterry> Saviq, you can just do mir/devel then
[15:20] <mterry> Saviq, oh but that's not an MP
[15:20] <Saviq> mterry, yeah, that MP will be fine I think
[15:20] <Saviq> mterry, or well, we might need another no-change against devel
[15:20] <mterry> boiko, what's the plan for a release of telephony-service with those AccountsService changes?
[15:21] <mterry> Saviq, you don't think silos like merged branches?
[15:21] <Saviq> mterry, not sure, we'll find out soon enough :)
[15:22] <mterry> tedg, I assume you saw the comments in your indicator-sound FFe?
[15:24] <didrocks> Saviq: the branch should be against trunk? I don't think we want to ship devel?
[15:24] <Saviq> didrocks, it will get into trunk on its own
[15:24] <Saviq> didrocks, we'll strip that silo a lot before landing
[15:24] <Saviq> didrocks, we just wanted to prepare for it
[15:25] <Saviq> didrocks, but yeah, I'm asking because it's against devel, we don't plan on landing it
[15:25] <didrocks> Saviq: not sure you'll want a silo then
[15:25] <ogra_> didrocks, dholbach, the porting guide is really behind ... but luckily we have some poeple doing ports and reporting to the ML, once these ports are successfull we should go over the thread and update the wiki accordingly
[15:25] <Saviq> didrocks, but silos are so nice!
[15:25] <didrocks> Saviq: yeah, but it's not the airline :)
[15:25] <davmor2> popey: I can't replicate your issue and I followed the steps in the bug and everything :D
[15:25] <Saviq> didrocks, what would be the issue?
[15:26] <Saviq> there's probably one interesting question... ABI breakage in mir devel
[15:26] <tedg> mterry, Yeah, working on it.
[15:26] <dholbach> ogra_, yeah, that'd be great - or the folks who get good advice can go and update the guide?
[15:26] <didrocks> Saviq: blocking, need everyone to set "force" on that components and you will stuck a silo where we are already low on resources
[15:26] <Saviq> we'd probably need to rebuild qtubuntu, platform-api and unity-mir at least
[15:26] <davmor2> didrocks: I can't replicate what popey is seeing at all
[15:26] <didrocks> davmor2: music app is starting?
[15:26] <didrocks> as well?
[15:26]  * mterry hugs tedg
[15:26] <Saviq> didrocks, :|
[15:26] <popey> davmor2: i did it twice ☻
[15:26] <Saviq> didrocks, yeah I get what you mean
[15:27] <ogra_> dholbach, yeah, prob is that porting isnt usually done in one shot so telling the good from the bad advise is needed
[15:27] <Saviq> mterry, it might be too early for a silo then
[15:27] <didrocks> Saviq: you really want the airline which is to address that :)
[15:27] <Saviq> didrocks, of course I do
[15:27] <davmor2> didrocks: music starts which is sergiusens issue blown out the water
[15:27] <ogra_> if they just dump in everything the guide will be mess again
[15:27] <Saviq> didrocks, thought locking is off, though... I could have two unity8 silos with nothing special?
[15:27] <didrocks> davmor2: I just reflashed #137
[15:27] <didrocks> davmor2: let me upgrade
[15:27] <davmor2> didrocks: and popey 's restarting loop of unity8 I can't reproduce
[15:27] <sergiusens> tedg, seems my changes aren't taking effect; even tried replacing the original conf
[15:28] <didrocks> Saviq: it's an exceptional case as told
[15:28] <Saviq> didrocks, ok
[15:28] <didrocks> Saviq: and the consequence is that we are low on silos now :p
[15:28]  * mterry reads back
[15:28] <sergiusens> tedg, init-checkconfig says conf is ok and I did reload the configurarion
[15:28] <dholbach> ogra_, right
[15:28] <tedg> sergiusens, Try putting something in the pre-start? Perhaps that is failing?
[15:28] <Saviq> didrocks, it's all juju-ified, isn't it? just crank the dial up! ;D
[15:28] <didrocks> Saviq: ahah, not the LP-side though :p
[15:29] <Saviq> mterry, so yeah, a little bit early for a silo
[15:29] <didrocks> Saviq: you are building the Mir thingy to hope it will help the music one?
[15:29] <Saviq> didrocks, although I'd say the split greeter would be a big transition enough to warrant the exception
[15:29] <mterry> Saviq, because of the Mir issue?   I'll have to keep poking kgunn then  :)
[15:29] <davmor2> sergiusens: of course we are all fools for following your advice for the upgrade simulation  ubuntu-device-flash --channel=devel-proposed --revision=237 --wipe would be the way to do it then you can actually upgrade :)
[15:29] <didrocks> Saviq: yeah, but clearly not until we can promote an image and get to a normal silo level
[15:30] <Saviq> mterry, not only that
[15:30] <sergiusens> tedg, was pre start
[15:30] <Saviq> didrocks, yes, understand
[15:30] <tedg> sergiusens, Did you try the aa-exec-click -p thing? I'm curious if the apparmor profile is failing to load? (that happens between pre-start and and the job itself)
[15:30] <didrocks> Saviq: but agreed then
[15:30] <Saviq> didrocks, waiting for a patch from AlbertA, what Daniel had was only dealing with SIGSTOP/SIGCONT
[15:30] <didrocks> Saviq: ok, but we all agree that the alarm one is different?
[15:30] <sergiusens> tedg, not yet; happens next
[15:30] <didrocks> and it's on thostr_'s team
[15:30] <Saviq> didrocks, ENOCOMMENT, dunno the alarm one
[15:31] <Saviq> didrocks, but people said so
[15:31] <didrocks> Saviq: lucky you :p
[15:31] <sergiusens> tedg, http://paste.ubuntu.com/7125780/ that's with env from pre start
[15:31] <didrocks> Saviq: kgunn is off today?
[15:31] <ogra_> he was around
[15:31] <didrocks> ok
[15:31]  * didrocks invites him to the meeting
[15:32] <davmor2> didrocks: which one in particular
[15:32] <didrocks> davmor2: I'm upgrading to latest proposed image as we speak
[15:32] <didrocks> from latest promoted
[15:32] <tedg> sergiusens, Can you throw an "echo foo" after the click-exec just to make sure it happens?
[15:32] <tsdgeos> Mirv: you can add the patch to our Qt, i have a patch+test for upstream (that is slighlity different since they are only accepting 5.3 now) https://codereview.qt-project.org/#change,81454
[15:33] <didrocks> and see if I can reproduce popey's/sergiusens issues
[15:33] <Saviq> didrocks, he lost connection like a quarter ago or something
[15:33] <didrocks> Saviq: ok :)
[15:33] <tedg> sergiusens, Just trying to clear up possibilities.
[15:33] <didrocks> thanks
[15:33] <garvit> hello i am new to development world and i would like to port ubuntu touch on my SONY XPERIA P can someone guide me.
[15:34] <sergiusens> tedg, wrapped in prefoo and postfoo http://paste.ubuntu.com/7125796/
[15:35] <tedg> sergiusens, So, no postfoo?
[15:35] <sergiusens> nope
[15:36] <tedg> Hmm, there's no error handling between that last print out and the "return 0"
[15:36] <tedg> sergiusens, No crash file for UAL, right?
[15:37] <sergiusens> nope
[15:37] <tedg> sergiusens, Did you make it so it wasn't "exec click-exec" just a call?
[15:38] <sergiusens> tedg, the pre-start script has exec originally
[15:39] <tedg> sergiusens, Yes, just checking that you removed it. Because the exec there would make postfoo not print.
[15:39] <charles> didrocks, so are you experiencing the alarm bug that's being discussed this morning?
[15:39] <sergiusens> right
[15:39] <didrocks> charles: popey and davmor2 are, right
[15:41] <sergiusens> tedg http://paste.ubuntu.com/7125821/ ...
[15:41]  * sergiusens goes back to the upstart handbook
[15:41] <sergiusens> davmor2, didn't make sense of what you just said
[15:42] <tedg> sergiusens, Heh. And did you put a prebar and postbar around exec-line-exec?
[15:42] <didrocks> charles: you can't reproduce?
[15:43] <didrocks> sergiusens: I can start music app
[15:43] <seb128> charles, didrocks: I didn't follow up, too much IRC channels and a meeting, but didn't Saviq said that the issue for alarm/music was down to Mir/events being queued/blocked?
[15:43] <didrocks> quite slow to start
[15:43] <davmor2> sergiusens: so if we reflash with --revision=237 (last promoted) we can do a real upgrade to 248 without having to reflash
[15:43] <didrocks> seb128: issue for music yeah
[15:43] <sergiusens> davmor2, oh, well devel-proposed only keeps the last 10 images; my comment was a generic one; you are just lucky it was rolled out
[15:43] <charles> didrocks, tbh I'm still not sure what the new issue is, the bug reported is about indicator-datetime not showing snap decisions while the screen is off
[15:43] <didrocks> seb128: alarm doesn't use Qt
[15:43] <didrocks> charles: what is playing the alarm music, do you know?
[15:43] <seb128> didrocks, ^ that's qt :p
[15:43] <didrocks> seb128: charles told the indicator isn't using Qt
[15:44] <charles> didrocks, right now it's pulseaudio
[15:44] <didrocks> charles: what is asking pulseaudio to play a music?
[15:44] <seb128> didrocks, (I was talking about notification, not the sound)
[15:45] <charles> (didrocks, seb128, there's a bug ticket to switch from PA to use ricmm's upcoming media API for that, bug #1283065)
[15:45] <sergiusens> tedg, I have another env there so it should of reprinted
[15:45] <didrocks> charles: sure, but we are talking about the present :)
[15:45] <charles> :)
[15:45] <rsalveti> charles: well, the existing audio stack is PA
[15:45] <didrocks> so, indicator-datetime is triggering the alarm sound?
[15:45] <charles> didrocks, indicator-datetime is what tells PA to play the alarm and show the snap
[15:45] <rsalveti> didrocks: what is the issue? (alarm)
[15:45] <rsalveti> if do we have a bug?
[15:45] <charles> rsalveti, that's what we're trying to figure out
[15:46] <didrocks> rsalveti: sure  https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122
[15:46] <tedg> sergiusens, Can you pastebin the job, I'm getting myself confused :-)
[15:46] <didrocks> charles: the bug was pointed to you by thostr_ an hour ago IIRC :)
[15:46] <charles> didrocks, yes I know. We discussed it then but the discussion petered out and I had a pair of hangouts
[15:47] <charles> so I'm back and continuing the conversation, trying to figure out what actually is new in 1295122, if anything at all :-)
[15:47] <didrocks> wonder why image # were not set though
[15:47] <charles> so there's an existing known issue about not working when the phone is suspended, we need for hardware alarms to land in platform-api before indicator-datetime can wake the phone up to show snap decisions then
[15:47] <charles> previously it seemed to work because the phone wasn't actually suspending...
[15:47] <sergiusens> tedg, here, let's make it atomic: http://paste.ubuntu.com/7125841/ and http://paste.ubuntu.com/7125847/
[15:47] <didrocks> charles: how come was it working pre-Qt 5.2 then?
[15:48] <didrocks> charles: on #237?
[15:48] <charles> didrocks: previously it seemed to work because the phone wasn't actually suspending...
[15:48] <didrocks> rsalveti: but it seems you punned that one off, right? ^
[15:48] <Saviq> mterry, we're getting a silo after all ;D
[15:48]  * didrocks seems to be back one hour earlier
[15:48] <charles> :)
[15:49] <Saviq> mterry, only we need not to complain if they flush us out of it when needed
[15:49] <rsalveti> didrocks: no, it just suspends correctly sometimes :-)
[15:49] <didrocks> rsalveti: hum, but what changed? seems to be reliably working on #237
[15:49] <didrocks> and not on #238
[15:49] <rsalveti> davmor2: popey: can you guys try to reproduce bug 1231455 after running 'powerd-cli active' on another terminal?
[15:50] <didrocks> jibel: davmor2: popey: right? ^
[15:50] <tedg> sergiusens, Cool, great idea! That clears things up. So it seems to not be getting to the exec section of the job.
[15:50] <rsalveti> didrocks: nothing changed, but the wakelock is usually not around when the antenna signal is strong enough for the modem to be quiet
[15:51] <popey> rsalveti: you sure about that bug number?
[15:51] <rsalveti> Popey: See's the alarm notification but not hears no sound.
[15:51] <rsalveti> this is a different issue
[15:51] <rsalveti> popey: no, that's wrong
[15:51] <rsalveti> lol
[15:51] <rsalveti> popey: davmor2: but 1295122
[15:51] <rsalveti> bug 1295122
[15:52]  * rsalveti needs coffee
[15:52] <davmor2> I was beginning to wonder then popey beat me to the ask
[15:52] <rsalveti> being able to see the alarm and not hearing is an interesting issue
[15:53] <tedg> sergiusens, Can you dump the output of this while starting the app please? dbus-monitor --session interface=com.ubuntu.Upstart0_6.Job
[15:53] <mterry> Saviq, OK  :)
[15:53] <davmor2> rsalveti: am I running that as root via adb or via sudo -u phablet -i in adb?
[15:53] <kgunn> mterry: saw you talkin' bout silo in scrollback...
[15:53] <didrocks> sergiusens: assigning you with popey for the upgrade issue to get more investigation, neither davmor2 or I can reproduce it
[15:54] <kgunn> you need any help ? (leave Saviq free for real work :)
[15:54] <rsalveti> davmor2: as root
[15:54] <popey> rsalveti: does that stop it blank?
[15:54] <mterry> kgunn, sure you could help set it up instead of Saviq
[15:54] <davmor2> rsalveti: roger wilko
[15:54] <Saviq> kgunn, it's there in row 42
[15:54] <rsalveti> popey: no, just stop suspending
[15:54] <popey> k
[15:54] <kgunn> Saviq: mterry....glad i could help ;D
[15:54] <Saviq> kgunn, sil2100 and didrocks decided to give us the silo with the caveat that we might lose it if it gets tight
[15:56] <Saviq> kgunn, so the row is good, only potential issue is if mir broke ABI between trunk and devel (or that the branch does), in which case we'll need to rebuild papi, qtubuntu and unity-mir
[15:56] <Saviq> and whatever else you rebuild on Mir ABI break, but that you'll know better
[15:56] <popey> rsalveti: it's the same, i mean, with the screen blanked (I tapped power) I see nothing until I wake the screen
[15:56] <didrocks> popey: davmor2: rsalveti: screen blanked works here
[15:56] <sil2100> Saviq: is that landing row good MR-wise?
[15:56] <didrocks> rsalveti: anyway to force the suspend?
[15:56] <Saviq> sil2100, yes
[15:57] <rsalveti> didrocks: nops
[15:57] <didrocks> anyway to turn off the alarm as well?
[15:57] <davmor2> rsalveti: and it rings
[15:57] <jonahbron> Anyone know the status of the QtQuick.Controls.MenuBar widget?  It's not working for me.
[15:58] <rsalveti> hm, confused haha
[15:58] <tedg> sergiusens, Actually this might be more informative: dbus-monitor --session interface=com.ubuntu.Upstart0_6,member=EventEmitted,arg0=stopped
[15:58] <didrocks> rsalveti: so, to have is suspended for sure, need to unplug the cable and wait for x minutes ?
[15:58] <rsalveti> popey: so broken the same way for you
[15:58] <rsalveti> and working fine for didrocks and davmor2
[15:58] <popey> left comment on bug
[15:58] <rsalveti> didrocks: in theory yes, but with mako that is not always true as the modem might be holding a wake_lock
[15:58] <rsalveti> didrocks: testing with flo is better in this case
[15:58] <didrocks> rsalveti: I only have mako
[15:59] <popey> i have flo
[15:59] <kgunn> mterry: Saviq...yeah, that ought to be ok...that mp doesn't break abi & will use trusty branch as base
[15:59] <davmor2> rsalveti: I have mako/flo/manta
[15:59] <kgunn> should be fine
[15:59] <Saviq> kgunn, will not
[15:59] <popey> now, if only unity didnt die on me on flo
[15:59] <Saviq> kgunn, it's gonna use devel as base
[15:59] <rsalveti> davmor2: but you said it worked for you on mako, right?
[15:59] <mterry> kgunn, that branch actually does delete a public method
[15:59] <rsalveti> not sure why it would fail for popey
[15:59] <rsalveti> are you guys using the same image?
[15:59] <kgunn> Saviq: oh my bad...
[15:59] <Saviq> kgunn, since it's directed to devel, it will build devel
[16:00] <popey> -rw-rw-rw-  1 root   root            0 Mar 20 12:45 .writable_image
[16:00] <popey> ffs
[16:00]  * popey reflashes his device clean
[16:00] <rsalveti> didrocks: but we know it'll be broken if the device is properly suspended
[16:00] <mterry> kgunn, when is 0.1.18 planned?
[16:00] <fps> what's the preferred way to reboot the device with ubuntu touch?
[16:01] <rsalveti> that is a known issue and not a regression
[16:01] <fps> s/the/a/
[16:01] <davmor2> rsalveti: ah hang on retried and now it seems to of trigger I hit dismiss and it's carried on
[16:01] <fps> just hold the power buttong?
[16:01] <fps> feels a bit rough ;D
[16:01] <rsalveti> didrocks: the possible regressing is alarm not working when the device is not suspended
[16:01] <kgunn> mterry: let me add 2 mp's
[16:01] <didrocks> rsalveti: well, it's an user regression (from his point of view)
[16:01] <didrocks> rsalveti: and seeing how hard the line management is taking, I think they are going to block any new promotion
[16:01]  * davmor2 throws the phone out of the window to stop it ringing
[16:02] <rsalveti> didrocks: right, but nothing can be done to get that fixed, only when we land hw alarms
[16:02] <rsalveti> didrocks: it's not a regression
[16:02] <charles> davmor2, popey, https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/comments/6
[16:02] <rsalveti> didrocks: all you need to do is get low signal so the modem can take a wakelock
[16:02] <charles> + rsalveti, didrocks, ^
[16:02] <davmor2> rsalveti: the second test should of gone off at 16:00:00 it went off at 16:00:32 and then refused to stop ringing
[16:02] <didrocks> rsalveti: well, it's a "4.4 regression" actually as the device sleep is fixed
[16:03] <didrocks> rsalveti: just talking about user's view
[16:03] <rsalveti> it's not :-)
[16:03] <rsalveti> it was always broken
[16:03] <rsalveti> it works sometimes
[16:03] <didrocks> ah, so deep sleep isn't something fixed in 4.4
[16:03] <didrocks> ok
[16:03] <rsalveti> no, broken the same way
[16:03] <didrocks> not sure why it was so reliably working/not working for popey and davmor2
[16:03] <sergiusens> tedg, http://paste.ubuntu.com/7125933/
[16:03] <rsalveti> maybe with usb cable connected
[16:03] <rsalveti> charging
[16:03] <charles> that's plausible
[16:04] <rsalveti> caused by the music-app bug (not removing the suspend blocker)
[16:04] <didrocks> ok
[16:04] <didrocks> popey: davmor2: tell us about the second test, otherwise, happy to remove it from the list
[16:04] <rsalveti> but if the alarm is broken when the device is not suspended, then we have a bug
[16:04] <didrocks> based on what rsalveti told
[16:04] <didrocks> rsalveti: tried 3 times already
[16:04] <didrocks> here
[16:05] <didrocks> and all ok
[16:05] <charles> is that the second test in popey's video?
[16:05] <popey> i am re-flashing my device cleanly now
[16:05] <popey> its possible there was crap on it, I don't know.
[16:05] <rsalveti> davmor2: going off before the desired time is a bug for sure
[16:05] <rsalveti> yeah, trying reproducing after a clean flash and clean boot
[16:06] <charles> reflashing here
[16:06] <charles> (...we really need a nicer alarm tone :)
[16:06] <didrocks> it's all clean here (well, after an upgrade from a clean last promoted image)
[16:06] <sergiusens> rsalveti, fwiw the suspend blocker is a powerd bug ;-)
[16:06] <rsalveti> sergiusens: right :-)
[16:06] <davmor2> rsalveti: that is after the desired time by 32 seconds. but the issues is the fact that I hit dismiss which stopped it the first time and didn't the second I had to power down the device to make it stop ringing
[16:06] <tedg> jdstrand, Is there a way that we could load the music app profile to see if it's failing somehow?
[16:07] <tedg> jdstrand, If I just called "aa-click-exec -p music ls" would that work?
[16:07] <rsalveti> davmor2: yeah, that might even be a different bug
[16:07] <rsalveti> let's see if charles is able to reproduce that
[16:08] <tedg> jdstrand, We seem to be getting out of pre-start but not into the main job, and the only thing I can think of that happens there is switching to the apparmor profile.
[16:08] <rsalveti> always keep 'powerd-cli active' running when testing the alarms
[16:08] <rsalveti> so we know it's not suspend related
[16:08] <rsalveti> also flashing latest
[16:08] <charles> rsalveti: I'm just now starting the flash, so this may take a bit ;)
[16:09] <tedg> jdstrand, So looking for an independent way that I can ask sergiusens to verify that the apparmor part isn't failing.
[16:09] <davmor2> rsalveti, didrocks: right I'm going to start an album playing let the device sleep with the  powerd-cli active on and see if we get to track 2
[16:09] <charles> davmor2, could you walk me through the steps to try & reproduce the wont-stop-ringing issue you saw
[16:09]  * sergiusens checks /var/lib/apparmor
[16:09] <rsalveti> davmor2: Saviq tried that already, and failed the same way
[16:09] <rsalveti> davmor2: the music-app issue happens when the screen is off, not necessarily suspended
[16:10] <davmor2> rsalveti: :(
[16:10] <sergiusens> tedg, jdstrand think I found the issue :-/
[16:10] <sergiusens> tedg, phablet@ubuntu-phablet:/var/lib/apparmor$ ls clicks/|grep music
[16:10] <sergiusens> com.ubuntu.music_music_1.1.359.json
[16:10] <sergiusens> wrong version
[16:11] <tedg> Oh, heh. Computers are such sticklers about numbers.
[16:12] <boiko> mterry: unfortunately landings are blocked until an image is promoted
[16:12] <davmor2> charles: the time was 15:55 so I set the first alarm for 15:57 and hit the power button to stop the screen, alarm went off fine and I was able to wake the phone and hit dismiss and it did, I then tried again for 16:00 this time the alarm went off 32 seconds late and wouldn't stop ringing
[16:12] <Saviq> davmor2, the alarm does wake the device up, though, right?
[16:12] <didrocks> rsalveti: did miss one with mako this time, so yeah, probably suspended
[16:13] <mterry> boiko, makes sense
[16:13] <rsalveti> didrocks: right
[16:13] <Saviq> davmor2, so it will light up the screen, so the "screen off" issue shouldn't matter
[16:13] <rsalveti> hopefully we'll be able to land hw alarms next week anyway
[16:13] <davmor2> Saviq: this was with powerd-cli active in place the alarm went off both times correctly just wouldn't stop ringing
[16:13] <tedg> sergiusens, So I'm gonna assume I'm out of this one now then. I think it's cjwatson vs. jdstrand for this bug now :-)
[16:13] <Saviq> davmor2, ah ok, so different
[16:14] <davmor2> Saviq: alarm didn't wake the screen I had to
[16:14] <sergiusens> tedg, would be hard to now has this happened or why it hasn't regenerated (relinked)
[16:14] <Saviq> davmor2, hmm not sure what the UX design is, but I imagine it should
[16:14] <sergiusens> tedg, thanks
[16:14] <rsalveti> I don't think we have anyone waking up the screen reliably though
[16:14] <davmor2> Saviq: but that is a known bug
[16:14] <sergiusens> hard to know*
[16:14] <davmor2> Saviq: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/comments/6
[16:15] <tedg> sergiusens, Yeah, I'm guessing it's either a click hook didn't run or when it ran it didn't generate it correctly.
[16:15] <tedg> sergiusens, I guess if there's no symlink, it's probably a click thing.
[16:15] <Saviq> davmor2, oh ok
[16:15] <sergiusens> tedg, there is a symlink, with an incorrect version :-P
[16:16] <mpt> awe, another question: About how long does it take for ofono to tell whether manually entered APN settings work? One second? Five? Ten?
[16:16] <rsalveti> right, so nobody should be waking up the screen atm
[16:16] <rsalveti> and that is expected
[16:16] <charles> davmor2, right, the screen will wake up but powerd hasn't done that yet because iiuc it's waiting on hw alarms in platform-api
[16:16] <rsalveti> but the sound should still play
[16:16] <rsalveti> charles: sound not playing when device is not suspended is a bug
[16:17] <charles> rsalveti, agreed. I'm trying to reproduce that
[16:17] <rsalveti> and not being able to stop it is another bug
[16:17] <sergiusens> tedg, seems it happens since I installed a click for that package that doesn't belong to the normal in image clicks (as an update or out of band install); seems similar to what kenvandine saw yesterday
[16:17] <ogra_> who wants to stop alarms anyway :P
[16:17] <didrocks> rsalveti: davmor2: powerd-cli active
[16:18] <rsalveti> davmor2: do you get the 'unable to stop the alarm sound' issue when forcing 'powerd-cli display on bright'?
[16:18] <didrocks> rsalveti: davmor2: no ringing here :/
[16:18] <ogra_> (we could just call it a feature ... it reminds the whole day you that you didnt forget to set the alarm)
[16:18] <kenvandine> sergiusens, i rebuilt my click and it worked
[16:18] <rsalveti> didrocks: right, that's a bug
[16:18] <kenvandine> no changes
[16:18] <kenvandine> not sure what was up with that
[16:18] <didrocks> charles: ^
[16:18] <didrocks> charles: so no deep sleep
[16:18] <didrocks> and no alarm either
[16:19] <rsalveti> wonder if pulse is smart enough to not play when the screen is off?
[16:19]  * ogra_ thought it was clearified 2h ago by rsalveti that we have no deep sleep on mako
[16:19] <didrocks> rsalveti: worked once though
[16:19] <rsalveti> right
[16:19] <didrocks> with screen off
[16:19] <ogra_> (why is this still discussed, we need to improve our communication seriously
[16:19] <ogra_> )
[16:19] <tedg> ogra_, It's because everyone was in a deep sleep and didn't get the message.
[16:20] <rsalveti> ogra_: we have, that's the issue, but not always (deep sleep on mako)
[16:20] <didrocks> ogra_: well, rsalveti told the contrary here (I thought we had no deep sleep, but seems we can have it)
[16:20] <didrocks> ogra_: you need to backlog even more! :)
[16:20] <ogra_> ah, k
[16:20] <ogra_> seems ted is right then ...
[16:20] <ogra_> (wrt /me)
[16:21] <charles> davmor2, with the second alarm that went off 32 second late -- did you get a snap decision when it went off?
[16:21] <qengho> ara: Hi hi. I'm working on chromium-browser touch support. You mentioned that you have a touch-pad and you tried two-finger pinch, and it didn't do what you expect.  Does *any* app you try understand two-finger pinch?
[16:21] <didrocks> charles: see https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/comments/7
[16:21] <davmor2> charles: Yes I hit dismiss it just didn't
[16:22] <ara> qengho: hello, I would need to try, do you have any recommendation of an app that should understand 2-finger pinch?
[16:23] <popey> ara: web browser
[16:23] <popey> ara: the OSM (webapp) understands 2 finger pinch
[16:24] <ara> popey: is it available for the desktop?
[16:24] <popey> ara: ya, apt-get install webbrowser-app
[16:25] <qengho> popey: Thanks! When you say it should, have you tried it on something not a touch-screen, like a touch-pad?
[16:25] <popey> nope
[16:26] <popey> i switch touch-pads off on my laptops ☻
[16:26] <rsalveti> hm, can't get alarm to work
[16:26] <rsalveti> interesting that in the upcoming indicator the alarm is set with UTC
[16:26] <davmor2> charles, rsalveti: so with powerd-cli display on bright it is popping up the alarm snap decision and dismissing correctly each time it has worked 3 times now
[16:26] <popey> davmor2: how are you doing that?
[16:27] <didrocks> rsalveti: hum
[16:27] <ara> qengho: I need to reboot, will get back to you in a second
[16:27] <didrocks> rsalveti: It didn't ring even screen on
[16:27] <didrocks> rsalveti: I wonder if the issue isn't rather "first alarm(s?) work"
[16:27] <didrocks> then none
[16:27] <davmor2> popey: adb shell and then type in powerd-cli display on bright the nset the alarm etc
[16:28] <rsalveti> argh, why I can't get alarm to work
[16:28] <popey> ok
[16:28] <charles> following didrocks' suggestion of adb shell + powerd-cli active + manually turning off the screen, I get a ringtone at the right time, and then when I turn on the screen I see the snap decision & am able to stop the ring by dismissing the snap
[16:28] <davmor2> rsalveti: that powerd-cli command though is opening directly to the clock-app/apps scope bypassing the welcome screen is that what is meant to happen
[16:28] <didrocks> charles: did you try to setup another alarm then?
[16:28] <charles> having trouble editing alarms in the clock app, but that's a different issue...
[16:28] <didrocks> charles: even screen on now I don't get any new alarm
[16:28] <charles> didrocks: each time I've done it, it's been creating a new alarm from scratch
[16:28] <rsalveti> how can I remove an alarm?
[16:29] <didrocks> charles: do you delete old alarms?
[16:29] <charles> didrocks: if the recipe involves editing an existing alarm, I'm not able to edi tthem
[16:29] <didrocks> rsalveti: I tried rebooting just in case
[16:29] <didrocks> then, I'll go on removing alarms
[16:29] <didrocks> if I can :)
[16:29] <charles> rsalveti: in the clock app, slide them to the side and you'll get a trashcan button
[16:29] <didrocks> charles: no, I keep appending
[16:29] <rsalveti> oh, awesome
[16:29] <davmor2> charles: yeah you just have to delete the old alarm
[16:29] <charles> didrocks: I deleted and repeated. I'll try appending instead
[16:29] <didrocks> I wonder if it can be a ETOOMANYALARMS
[16:29] <didrocks> then
[16:29] <rsalveti> lol, app is frozen now after removing second alarm
[16:30] <rsalveti> apport is on fire
[16:30] <popey> gah!
[16:30] <charles> lol
[16:30] <rsalveti> _usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash
[16:30] <rsalveti> yay
[16:30]  * charles blames it all on ubuntu-clock-app, then runs away
[16:30] <popey> freshly flashed my device with 248. keeping display on i can see the popup but hear no sound.
[16:31] <didrocks> ok, it's ringing
[16:31] <mhall119> bzoltan: is it possible to tell qtc to look in a subdirectory of a project for the click and apparmor manifest files?
[16:31] <didrocks> after a reboot
[16:31] <mhall119> instead of hte project rot
[16:31] <davmor2> rsalveti: <kings of leon style> My apport is on fire </kings of leon style>
[16:31]  * popey reboots
[16:31] <didrocks> let me try again to add more
[16:31] <rsalveti> lol
[16:31] <charles> it's like blind men feeling the elephant
[16:32] <ara_> qengho: confirmed that 2-finger pinch does not work either in webbrowser-app
[16:32] <didrocks> so it's not the number of alarms
[16:32] <qengho> ara, All, I'm glad I'm in this channel, so people can tell me I'm full of nonsense. I don't think any touch-pads will support two-finger pinch in ubuntu. The underlying layers take two-finger gestures and make them into motion or scroll events, not touch events. It's an ancient hack to support apps that didn't understand 2-finger scrolls in early 2000s. So, terminal gets a PageUp/Down.  At three fingers, it flips to interpretation to touch events.
[16:32] <didrocks> ok, 2nd alarm since reboot rings as well
[16:32] <qengho> I have played with it, and I'm no expert, but I don't see a way to get pinch info from a touchpad.
[16:33] <didrocks> 3rd works…
[16:33] <qengho> Not until xinput2 get rewritten.
[16:33] <didrocks> if the 4th works, I have no idea…
[16:33] <charles> so, appending a new alarm (instead of deleting the old one) seems to not affect anything, getting the same behavior with "powerd-cli active" + screen off that I saw before
[16:33] <qengho> ara_: touch*screens* should work. They don't have the historical baggage.
[16:34] <didrocks> charles: even screen on, I had nothing after a while
[16:34] <popey> after reboot alarm works.
[16:34] <didrocks> 4th worked :(
[16:34] <didrocks> I don't know…
[16:34] <didrocks> I tried dismiss/ok as well
[16:34] <ara_> qengho: do you happen to have a bug  around we can reference?
[16:35] <didrocks> ok, trying to get a low power now
[16:35] <didrocks> and let's see if it breaks alarm forever
[16:35] <didrocks> (until you reboot)
[16:35] <qengho> ara_: Not yet.  I'm just discovering it.  I'm hoping to be told I'm wrong.
[16:35] <charles> popey, you're able to reproduce the no-sound issue?
[16:35] <charles> oh, not after reboot. damn :/
[16:36] <popey> charles: on first boot, yes
[16:36] <popey> after reboot, sound works
[16:36] <davmor2> charles: I'm at the continued ringing after hitting dismiss on powerd-cli active what info is useful?
[16:37] <ogra_> qengho, phones with touch pads ?
[16:37] <rsalveti> brb, need to grab some food
[16:37] <qengho> ogra_: I'm not here to talk about phones uniquely.
[16:37] <ogra_> qengho, well, but this is the channel for them :)
[16:37] <qengho> Sorry.
[16:37] <ara_> qengho: maybe we should ask in #ubuntu-x
[16:38] <ogra_> (teh channel name is misguiding)
[16:38] <qengho> Good idea.
[16:38] <ogra_> yeah
[16:38]  * ogra_ was about to suggest that
[16:38]  * qengho leaves.
[16:38] <davmor2> charles: it went off at 16:35:26 rather than 16:35:00
[16:38] <ogra_> stay :)
[16:38] <ogra_> we like you around
[16:38]  * qengho hugs ogra_.
[16:38]  * ogra_ hugs qengho
[16:38] <davmor2> charles: only seems to keep ringing if it is late
[16:38] <ogra_> (and ara_ )
[16:39] <charles> davmor2, and you're getting the snap decision late too?
[16:39] <charles> ie, the popup shows up at 16:35:26 rather than 16:35:00, just as the ring does?
[16:39] <davmor2> charles: pass I don't unblank the screen till the alarm sound
[16:41] <didrocks> charles: rsalveti bah, passing everytime on that one…
[16:42] <didrocks> charles: I do confirm though that waiting for too long doesn't enable us to dismiss the ringing
[16:42] <didrocks> davmor2: opening a bug on that?
[16:42] <davmor2> didrocks: will do
[16:43] <didrocks> davmor2: before the meeting please :)
[16:43] <davmor2> charles: can I shutdown the phone the ringing is driving me crazy now if there are no logs you need
[16:43] <charles> davmor2, try this for me please
[16:44] <charles> ssh in as phablet
[16:44] <charles> $ stop indicator-datetime
[16:44] <charles> $ G_MESSAGES_DEBUG=all /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
[16:44] <AlbertA> Saviq: sorry I had to go deal with my kid
[16:44] <charles> davmor2: ^ this will start dumping debug messages to the terminal
[16:45] <Saviq> AlbertA, nw, plenty of things to do :)
[16:45] <davmor2> charles: It stopped ringing
[16:45] <AlbertA> Saviq: here's a branch that should do what you want
[16:45] <Saviq> AlbertA, did you survive? (or did he/she?)
[16:45] <charles> davmor2: this may help us to see why it's running late sometimes
[16:45] <AlbertA> Saviq: lp:~albaguirre/mir/test-hack-consume-buffers-display-off
[16:45] <charles> davmor2: then, while the debug messages are dumping to the terminal, try to make the alarm trigger late again
[16:46] <davmor2> charles: right yeap so I have the stuff dumping in the cli now and then trigger the alarms again right?
[16:46] <AlbertA> Saviq: yeah we survived :)
[16:46] <charles> davmor2: hm, it would be nicer if these messages had timestamps. oh well
[16:46] <mterry> MacSlow, poke
[16:46] <charles> davmor2: yes specifically a late alarm
[16:46] <MacSlow> mterry, what's up?
[16:46] <mterry> MacSlow, got some feedback about spinner, but not final design note
[16:46] <davmor2> charles: okay
[16:46] <charles> davmor2: since there's no timestamps on here, a little more info on what I'm looking for:
[16:46] <mterry> MacSlow, dropping text, likely use ubuntu logo instead of spinner, and likely back background.  Will know more tomorrow
[16:47] <charles> davmor2: I'm wanting to know which (if any) messages show up at the correct time, and which show up only when the alarm goes off late
[16:47] <davmor2> charles: right okay
[16:48] <MacSlow> mterry, that sound like easy changes... which I could do on the side... once final... still very busy with the "avoid fullscreen notifications messing up visual queue"-issue.
[16:48] <mterry> MacSlow, cool
[16:48] <Saviq> AlbertA, thanks
[16:49] <davmor2> charles: http://paste.ubuntu.com/7126132/ no alarm at all
[16:49] <davmor2> and now I have (process:6560): Indicator-Datetime-WARNING **: Unable to show snap decision for 'Alarm': Timeout was reached
[16:49] <charles> oho!
[16:50] <charles> interesting.
[16:50] <charles> (process:6560): libnotify-WARNING **: Failed to connect to proxy
[16:51] <jonahbron> Does anyone know why the QtQuick.Controls.MenuBar isn't working on Trusty?
[16:51] <charles> davmor2: that unblocks me on the never-stops-ringing question anyway
[16:52] <charles> davmor2: so you got no snap decision popup, is that right?
[16:52] <didrocks> charles: I got one when it didn't stop ringing
[16:53] <davmor2> charles: with that one I got no alarm so I didn't hit the power button so saw no snap decision either
[16:53] <didrocks> davmor2: meeting approaching, got a bug for me?
[16:53] <didrocks> davmor2: easier to setup for the meeting with the list :)
[16:53] <davmor2> didrocks: writing it now
[16:54] <charles> didrocks: one issue, indicator-datetime will keep playing the sound until the user dismisses the snap decision. Dismissing the snap decision is impossible if libnotify can't be reached. In that case, the sound plays forever. :/
[16:55] <charles> didrocks: (process:6560): libnotify-WARNING **: Failed to connect to proxy
[16:55] <didrocks> charles: yeah, in the case I had, I saw the snap decision, clicked dismissed, but no effect
[16:55] <didrocks> (in the 2 cases)
[16:55] <didrocks> so probably multiple sources
[16:56] <charles> ya, agreed
[16:58] <cyphermox> charles: isn't indicator-datetime just notifying for minute change only when about to sleep?
[16:58] <cyphermox> so the alarm will either pop up before, or after sleep, and never inbetween sleep cycles?
[16:58] <cyphermox> brb
[16:59] <davmor2> didrocks: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295237
[16:59] <charles> cyphermox, no that's not correct. minute_change gets fired whenever the clock notices that the time has changed. This can happen through sleep/wakeup, or through normal time passing
[17:00] <charles> davmor2: could you please paste into that ticket a log of the debug messages that get logged during one of those late-by-XX-seconds runs?
[17:00] <charles> davmor2: is http://paste.ubuntu.com/7126132/ an example of that?
[17:02] <cyphermox> charles: where is the code that does that? I see LiveClock has a timer, but it's not used in Clock or ClockWatcher. Am I looking at the right place?
[17:02] <charles> cyphermox: inbetween sleep cycles, it's tested this way: http://bazaar.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.14.04/view/head:/src/clock-live.cpp#L105
[17:03] <charles>  cyphermox, in that file, line 112 is the event that fires out to listeners
[17:03] <charles> cyphermox, and clockwatcher registers for it http://bazaar.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.14.04/view/head:/src/clock-watcher.cpp#L41
[17:23] <asac> Saviq: news?
[17:23] <asac> kgunn: ?
[17:23] <asac> did we find out whats the probl with those messages?
[17:23] <Saviq> asac, building mir
[17:23] <Saviq> asac, "those messages"?
[17:23] <asac> Saviq: err. events not getting dispatched
[17:23] <Saviq> asac, I did confirm it's Qt 5.2 - i.e. between images 237 and 238
[17:24] <asac> Saviq: cool. and building mir is part of finding out more?
[17:24] <AlbertA> Saviq: just noticed that there would be race in the branch I sent you, I updated it and adding some logs
[17:24] <asac> Saviq: do you need more help? anyone i could activitate?
[17:25] <Saviq> asac, yes, confirming that it's indeed the stopped rendering that breaks the events
[17:25] <Saviq> or not
[17:25] <Saviq> AlbertA, ok
[17:25] <AlbertA> Saviq: you should see it compositing but not posting after screen off with adb shell tail -f /var/log/lightdm/unity-system-compositor.log
[17:26] <Saviq> AlbertA, atm I got http://pastebin.ubuntu.com/7126300/
[17:27] <Saviq> AlbertA, although I did merge your branch into trunk, if that makes any difference
[17:29] <AlbertA> Saviq: I based it off trunk
[17:29] <Saviq> AlbertA, right, yeah, the diff was minimal
[17:29] <tedg> popey, davmor2, hey guys, chatting with charles about the alarms bug. Have either of you attempted to get a bustle/dbus-monitor log of the failure?
[17:30] <AlbertA> Saviq: I can send you the two binary libraries if you want
[17:30] <Saviq> AlbertA, armhf/
[17:30] <Saviq> ?
[17:31] <AlbertA> Saviq: yeah well libmirserver.so.17 and libmirplatformgraphics.so specifically
[17:31] <Saviq> AlbertA, sure, that would work
[17:32] <davmor2> tedg: no idea what or where I'm trying to get the alarm to not stop to get feedback from the terminal nothing else using G_MESSAGES_DEBUG=all /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
[17:36] <tedg> davmor2, Ah, good, that'll be helpful as well.
[17:36] <rsalveti> didrocks: davmor2: when setting up an alarm, can you see it in the right timezone when checking it in the upcoming indicator?
[17:36] <rsalveti> in the indicator mine is always in UTC
[17:36] <rsalveti> and can't get the alarm to be triggered here
[17:36] <didrocks> rsalveti: I always uses it on UTC for that test
[17:37] <rsalveti> right :-)
[17:37] <davmor2> rsalveti: have you set the time zone in settings?
[17:37] <rsalveti> that is probably why
[17:37] <rsalveti> davmor2: yes
[17:37] <davmor2> rsalveti: hmm might be an issue with either eds or clock app then maybe
[17:37] <charles> popey, https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295271
[17:38] <popey> charles: wow, what a lovely bug-bot you are ☻
[17:38] <charles> popey: I like the bugs that are easy to trace :-)
[17:39] <tedg> Hah, so it seems that notifications is broken in general.
[17:39] <charles> tedg, maybe
[17:39] <tedg> Trying to tab complete gdbus on org.freedesktop.Notifications I get "Timeout"
[17:39] <rsalveti> didrocks: davmor2: yeah, alarm only works when you set it with UTC
[17:39] <charles> all we know for sure is that we can't connect to it
[17:39] <rsalveti> add an alarm for 3 hours ago, and worked fine this time
[17:39]  * rsalveti opening another bug
[17:40] <didrocks> rsalveti: bugfest ;)
[17:40] <davmor2> rsalveti: you're meant to be fixing them not creating more ;)
[17:41] <Saviq> AlbertA, a script? you're making me obsolete! :D
[17:41] <davmor2> popey: what was the link to that screenshot again please
[17:41] <charles> the timezone issue sounds a little like https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1283236, which says it's In Progress
[17:41] <AlbertA> Saviq: :)
[17:41] <popey> davmor2: see the bug above
[17:41] <popey> from charles
[17:41] <charles> davmor2: it's in https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1283236
[17:41] <davmor2> popey: I want to add it to a bug as I've seen it to now :)
[17:42] <popey> davmor2: or fish it out of this lot http://popey.com/~alan/phablet/gallery.php
[17:42] <charles> no, wrong pahttps://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295271
[17:42] <tedg> d-feet the same.
[17:42] <tedg> I'm totally willing to blame Unity8 now.
[17:42] <tedg> :-)
[17:42] <charles> this also explains why no sound
[17:42] <charles> this also explains why popey had those test runs with no sound, I think
[17:43] <charles> indicator-datetime doesn't play a sound if there's no way to dismiss the popup
[17:43] <charles> and if there are not buttons, there's no way to dismiss
[17:45] <cjwatson> sergiusens,tedg: so, sorry, I had a couple of meetings
[17:45] <rsalveti> davmor2: didrocks: the timezone issue is already opened: bug 1283236
[17:45] <cjwatson> sergiusens: could you please pastebin "find /usr/share/click/preinstalled /opt/click.ubuntu.com /var/cache/apparmor /var/lib/apparmor -ls" for me?
[17:46] <didrocks> rsalveti: ok, so nothing really "new" (not that a good news, but not a bad either)
[17:46] <davmor2> rsalveti: \o/
[17:46] <rsalveti> yeah
[17:46] <rsalveti> charles: sorry, so what do you think is currently causing these alarm issues?
[17:47] <rsalveti> (no sound, no way to dismiss, etc)
[17:49] <rsalveti> it seems to be bug 1295237
[17:49] <charles> rsalveti: I am tempted to close the first ticket as being too vague. https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295271 and https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295237 are more useful
[17:49] <rsalveti> so it might be the same issue
[17:49] <charles> rsalveti: I've done writeups in both of those two tickets about what I think the cause is
[17:49] <rsalveti> charles: right, mark one as duplicate of the other
[17:50] <charles> rsalveti: but the tl;dr seems to be (1) unity-notifications is not responding (so there may be a bug on their end?) and (2) indicator-datetime needs to fail more gracefully when it can't reach the libnotify server (which is a bug on my end :)
[17:51] <hedz09> ogra_: , I have u-boot able load the ramdisk and find the init within it, but I'm getting the message that: "initrd: couldn't find data partition"
[17:51] <ogra_> hedz09, so try adding datapart= to your kernel cdmline
[17:51] <sergiusens> cjwatson, sure; one sec
[17:51] <ogra_> hedz09, (with the device that holds your rootfs)
[17:52] <charles> rsalveti: no, 1295271 and 1295237 are slightly different from each other. But I'd be ok with closing bug #1295122 in favor of those two more descriptive ones
[17:52] <sergiusens> cjwatson, and no worries; just affecting me
[17:53] <rsalveti> charles: yeah, sounds good
[17:53] <charles> davmor2, since you reported 1295122 -- does ^ that sound right to you?
[17:54] <sergiusens> cjwatson, http://paste.ubuntu.com/7126410/
[17:58] <Saviq> asac, rsalveti, ogra_, davmor2, sergiusens, charles, @all: https://bugs.launchpad.net/music-app/+bug/1292306/comments/8
[17:59] <davmor2> charles: so I think they are slightly different but related.  I'd be happy for you to merge some together or mark both as fixed once there is a fix in place
[17:59] <Saviq> confirmed, Qt 5.2 queues events when it can't render
[17:59] <sergiusens> Saviq, nice
[17:59] <rsalveti> Saviq: awesome
[17:59] <davmor2> Saviq: I'll have a look in a bit teatime has been called
[18:00] <tedg> Ah guessing that's the same thing.
[18:00] <charles> Saviq, fun
[18:00] <sergiusens> Saviq, the find, not the situation it put us in :-)
[18:00] <hedz09> ogra_: initrd: That seems to be doing something, but it fails again: "mounting mmcblk0p3", "btrfs: open mmcblk0p3 failed", "initrd: couldn't find a system partition"
[18:00] <tedg> It's kinda fun with notify-send, you can get it to pause right until you hit the screen on function.
[18:00] <ogra_> hedz09, do you have the ubuntu system.img in  /userdata/system.img on that partition ?
[18:01] <ogra_> (note that you first need to assemble that system.img like rootstock-touch-install does)
[18:01] <Saviq> sergiusens, indeed
[18:02] <tedg> Saviq, Do you have a bug tracking that we should make the others dup to?
[18:02] <Saviq> tedg, "the others"?
[18:02] <Saviq> tedg, that above was the master bug
[18:03] <ogra_> we have other bugs for that ?
[18:03] <tedg> Saviq, I'm pretty sure bug 1295237 is the same, if the screen is off the dbus messages don't get processed.
[18:03] <hedz09> ogra_: I don't. That partition has system.img at its root abd doesn't reside in a /userdata/ folder within it.
[18:04] <hedz09> ogra_: I have assembled the system.img and am trying to test that I put it together correctly.
[18:04] <tedg> Saviq, I can literally turn off processing them or not by hitting the lock button.
[18:04] <ogra_> hedz09, wipe the partition, look at the rootstock-touch-install script and try to do the same by hand that it does and it should just boot
[18:04] <Saviq> tedg, possible
[18:04] <Saviq> tedg, try the binaries from there
[18:05] <Saviq> from my comment, that is
[18:05] <ogra_> hedz09, the  "initrd: couldn't find a system partition" is only printed if the initrd could not find a system.img in the right place
[18:05] <tedg> k
[18:05]  * Saviq called it 18hrs ago! WIN
[18:06] <asac> charles: tedg: thostr_: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295237
[18:06] <asac> who is the ultimate owner?
[18:06] <Saviq> asac, read up
[18:06] <asac> ah
[18:06] <asac> does that answer my question :)?
[18:06] <Saviq> asac, it's most probably the same Qt 5.2 events issue
[18:06] <asac> right
[18:06] <thostr_> asac: we're on it
[18:06] <asac> still we should keep folks confirming etc.
[18:07] <asac> and not rest because it might be this :)
[18:07] <Saviq> asac, tedg is confirming with the binaries from there
[18:07] <asac> yeah thanks
[18:07] <asac> kk
[18:07] <ogra_> Saviq, cant be ... everyone denied that when i said 4h ago that the event processing affects alarms :P
[18:07] <asac> tedg: its on you! :_
[18:07] <Saviq> ogra_, you weren't pushing enough ;)
[18:07] <ogra_> Saviq, lol
[18:07] <tedg> Heh
[18:07] <Saviq> ogra_, so alarms are processed fine
[18:08] <Saviq> ogra_, but when the notification is sent
[18:08] <Saviq> ogra_, it reaches unity8, which can't render
[18:08] <ogra_> yeah,  thats what i said before :)
[18:08] <Saviq> ogra_, and Qt doesn't deliver it up until later
[18:08] <Saviq> and everything goes apeshit
[18:08] <ogra_> poo
[18:09] <hedz09> ogra_: ok. Would btrfs: open mmcblk0p3 failed have anything to do with it?
[18:09] <ogra_> hedz09, why do you even have btrfs in your kernel ?
[18:10] <ogra_> (it doesnt really do well on MMC/SD)
[18:10] <hedz09> ogra_: to be honest I don't even know what it is
[18:10] <ogra_> its a filesystem
[18:11] <ogra_> but you should use ext4 on SD cards anyway, so you dont need it
[18:11] <cjwatson> sergiusens: is there anything in /var/log/upstart/click-system-hooks.log?
[18:12] <tedg> Saviq, Works for the notify-send case, checking with an alarm.
[18:12] <Saviq> asac, your ANN to ubuntu-devel got bitch-slapped into Junk by my dspam ;P
[18:12] <mterry> fginther, you around to help me practice running mediumtests?
[18:13] <Saviq> consider yourself ignored ;)
[18:13] <sergiusens> cjwatson, not there, I do see it in the apparmor one http://paste.ubuntu.com/7126501/
[18:13] <asac> Saviq: haha. well, i needed to setup special rules for mark, rick etc. to avoid that
[18:13] <asac> so its on you :)
[18:13] <asac> Saviq: its just telling you what will happen :)
[18:13] <asac> if you ignore it will still happen
[18:13] <asac> but i know you are joking
[18:13] <ogra_> just stop using all caps subjects in mails ;)
[18:13] <Saviq> :D
[18:14] <asac> its good that it even came through
[18:14] <Saviq> mterry, can I help? you mean mediumtests as in the jenkins jobs directly? or locally?
[18:14] <mterry> Saviq, locally on my phone
[18:14] <asac> thought i wouldn't go to list since i was kicked out of the core-dev and ubuntu member club a while back
[18:14] <Saviq> mterry, what project in particular?
[18:14] <mterry> Saviq, is there a wiki page for that?
[18:14] <asac> because of my laziness :)
[18:14] <cjwatson> sergiusens: mm, that's different, that's processing the symlinks that are in place.  I'm trying to work out how the symlinks got there
[18:14] <Saviq> mterry, if unity8, `phablet-test-run -p unity8-autopilot -n unity8`
[18:14] <mterry> Saviq, unity8 with my split stuff -- I wanted to test my proposed fixes for the mediumtests scripts to work in that scenario
[18:15] <seb128> asac, how is that lock playing out with the desktop LTS for shared component where we need fixes?
[18:15] <Saviq> mterry, then just ./run_on_device
[18:15] <mterry> Saviq, how do I point it at my branch of the mediumtests scripts?
[18:15] <sergiusens> cjwatson, I dont have a click-system-hooks log though
[18:15] <Saviq> mterry, and then PYTHONPATH=~/shell/tests/autopilot autopilot run unity8
[18:15] <asac> seb128: everything that goes on touch image is part of this
[18:15] <asac> special exceptions can be discussed with me or rickspencer3 as pointed out in mail
[18:16] <cjwatson> sergiusens: so you said this is basically just you at the moment?  (and I agree, it doesn't seem like a regression, more a corner case we hadn't previously found)  if so I can look at it tomorrow, as I need to leave pretty soon
[18:16] <seb128> asac, what happen to the desktop LTS if the touch image doesn't recover before the release?
[18:16] <asac> seb128: but we won't really make exceptions from what i understood
[18:16] <Saviq> mterry, you need to make install (or ninja, depending on whether you got it on the phone)
[18:16] <seb128> rickspencer3, ^
[18:16] <sergiusens> cjwatson, yeah, don't worry about it
[18:16] <asac> seb128: if that happens we are all fired :)
[18:16] <mterry> Saviq, that's all basic running unity8 tests on phone stuff
[18:16] <cjwatson> sergiusens: not that I expect I could land a fix for it at the moment anyway :P
[18:16] <asac> seb128: we have a veery strong team, with smart people. they are actively working on this as priority
[18:16] <Saviq> mterry, and the only other point is you need to `stop unity8` before (it will tell you) and keep the screen on
[18:16] <sergiusens> cjwatson, I don't use this phone for click testing that much (as I use it daily) just flashed to devel-proposed this week
[18:16] <mterry> Saviq, but I'm specifically talking about using the same scripts that jenkins does, but custom versions
[18:17] <asac> seb128: this is a matter of hours and at most days to sort out
[18:17] <sergiusens> :-)
[18:17] <cjwatson> sergiusens: yeah, it has an excitingly baroque set of packages installed apparently
[18:17] <cjwatson> might have some work to do on garbage collection :)
[18:17] <mterry> Saviq, hrm.  They seem very particular to QA.  Like connecting to 'ubuntu-qa-g-wpa-d' wifi
[18:17] <seb128> asac, let's see, last time it took you guys a week to unfreeze things when that happened
[18:17] <Saviq> mterry, those scripts don't do anything other than setting the device up (or should not)
[18:17] <mterry> Saviq, yeah but notably, they also unlock the screen
[18:17] <asac> seb128: right. hope we are getting better. also we just have those 3 bugs
[18:17] <Saviq> mterry, not for unity8 tests
[18:17] <mterry> Saviq, which is going to change with split
[18:17] <seb128> asac, I'm not sure why your smart people need a freeze also to fix the bugs
[18:18] <Saviq> mterry, where it's the test itself that will do it
[18:18] <asac> seb128: otherwise new bugs will come along
[18:18] <Saviq> mterry, unity8 tests are excepted from unlockign
[18:18] <seb128> asac, well, as long as they are not regressions or blockers
[18:18] <Saviq> mterry, and even for other tests, they use (or should use, in the case of smoke testing) the process_helpers from unity8
[18:18] <mterry> Saviq, well.  they actually do unlock screen there, but then also stop unity8
[18:18] <Saviq> mterry, so all in all
[18:18] <asac> seb128: every regression is a blocker
[18:18] <Saviq> mterry, just test locally, everything should be the same
[18:18] <asac> seb128: thats the current standing rule
[18:18] <seb128> asac, what about changes on shared component that don't affect the touch runtime paths?
[18:19] <asac> seb128: we discuss that, so might change, but for now we continue to stay strong
[18:19] <mterry> Saviq, yeah, but process_helpers.unlock_unity in unity8 will hopefully go away with split (unity8 doesn't need it)
[18:19] <Saviq> mterry, if it's not, we generally need to fix the scripts, not the tests
[18:19] <janimo`> stgraber, barry are there any plans to enable 3rd party gpg keys for system-image updates? From what I see the option for porter devices is disabling signature verification in recovery, or flash a fake archive-master key
[18:19] <rickspencer3> hi seb128
[18:19] <seb128> asac, screwing us on the desktop/LTS on the way...
[18:19] <asac> seb128: if there is any likelyhood that this affects runtime behaviour its covered
[18:19] <seb128> rickspencer3, hey
[18:19] <asac> seb128: otherwise you can move on
[18:19] <mterry> Saviq, and mediumtests I was planning to fix to modify lightdm config and swipe greeter itself
[18:19] <Saviq> mterry, sure, there should be a unity-greeter.process_helpers then
[18:19] <rickspencer3> seb128, you guys have important fixes that you are blocked on getting into the archive for desktop LTS now?
[18:19] <Saviq> mterry, or an equivalent
[18:19] <rickspencer3> or, are you just worried that that will happen?
[18:19] <seb128> rickspencer3, not now, but starting tomorrow it seems, from asac's email
[18:20] <seb128> rickspencer3, the later one
[18:20] <barry> janimo`: not on the official s-i.u.c site afaik.  but you can run your own site with your own keys, as some folks are already doing
[18:20] <rickspencer3> seb128, right
[18:20] <hedz09> ogra_: ahh, yeah the mmcblk0p3 partition is ext4. And I am not having any luck finding out where it's looking for system.img. It seems like /data/system.img but it isn't finding it there.
[18:20] <seb128> rickspencer3, I've fixes on indicators waiting for review that we were planning to land tomorrow
[18:20] <Saviq> mterry, so yeah, if you're after fixing the scripts, you'll need fginther/vanguard for mediumtests and doanac/plars for smoketesting
[18:20] <mterry> Saviq, yeah but it's tricky.  We need to modify lightdm config to run greeter with testability.  I could leave the unlock_unity method in unity8 source if we wanted, but unity8 wouldn't use it itself.  Made sense to move it into mediumtests
[18:20] <rickspencer3> so, I read this:
[18:20] <rickspencer3> We also kindly ask our core-devs with direct upload power for their
[18:20] <rickspencer3> support. Please wait with your uploads that affect touch until we have
[18:20] <rickspencer3> fully recovered.
[18:20] <seb128> rickspencer3, so it's not an hypothetic situation
[18:20] <barry> janimo`: we have okay support for that now (not perfect, but we'll be improving that after 14.04 i suspect)
[18:20] <seb128> rickspencer3, right, that could be after the LTS release for what we know :p
[18:20] <janimo`> barry, right, and if using new keys the recovery image needs to have another archive-master right?
[18:21] <Saviq> mterry, it needs to be in some source
[18:21] <asac> rickspencer3: i think his indicators go through CI TRain. if its desktop only they can float of course, but seems there are shared components in his landing
[18:21] <Saviq> mterry, to verify it works
[18:21] <rickspencer3> seb128, well, I think, let's fix the last issues right away
[18:21] <rickspencer3> right, I get it
[18:21] <Saviq> mterry, whether it's lightdm, unity-greeter or unity8, you decide
[18:21] <asac> kk
[18:21] <janimo`> barry, yes it is ok support indeed ( I use that now) but was wondering if there are other plans. I udnerstand it is risky to have other keys signed by the official Ubuntu ones
[18:21] <stgraber> janimo`: did you read https://www.stgraber.org/2014/02/11/your-own-ubuntu-touch-image-server/ ?
[18:21] <rickspencer3> I think that it's not an issue today
[18:21] <ogra_> hedz09, right, it needs to be in /data/system.img on that partition
[18:21] <seb128> rickspencer3, I don't get why we need a lockdown to fix bugs, but let's see
[18:21] <rickspencer3> and tomorrow will be a pain, but not an issue
[18:21] <mterry> Saviq, ?
[18:21] <Saviq> mterry, but it does need to be *tested* with every -ci job
[18:21] <Tassadar> janimo`: I'm using my own gpg keys in my system-image server
[18:21] <Saviq> mterry, it can't live with the mediumtest runners etc.
[18:22] <janimo`> stgraber, yes, and I have set up a local server (more or less). I think there's a typo there, it needs newgrp instead of newgroups
[18:22] <stgraber> janimo`: we can also build a trust chain from the main system-image server using the device keyring, but we haven't done so at this point because we didn't have any reason to
[18:22] <seb128> rickspencer3, well every day we delay desktop landing is less days to verify the fixes that should land in the LTS, I'm not sure we are doing the right tradeoff there
[18:22] <Tassadar> janimo`: I mean, the ones generated by generate-keys, so I suppose those are testing only (but the signature gets verified in recovery)
[18:22] <seb128> rickspencer3, I get that touch is important, but the desktop LTS is as well
[18:22] <Saviq> mterry, we (lightdm, unity8 devs) need to be responsible for keeping those helpers working
[18:22] <rickspencer3> seb128, well, like I say, let's just get this fixed and promoted so it doesn't become an issue
[18:22] <janimo`> Tassadar, so you did not need to change archive-master then, ok. I need to see why I had verification failed there
[18:23] <seb128> rickspencer3, agreed, and we could do that with a lockdown of the uploads...
[18:23] <Tassadar> you have to put your archive-master into the recovery image
[18:23] <seb128> lockdown doesn't resolve any byg
[18:23] <seb128> bug
[18:23] <cjwatson> most people aren't qualified to help of course
[18:23] <hedz09> ogra_: Okay, it's there but it just isn't find it. System.img is supposed to be ext2, right? Couldit be a permission issue on the folder? I can't imagine...
[18:23] <Saviq> mterry, so they need to be with our code, not with mediumtest scripts (which should do as little as possible so that we can reproduce the same env locally)
[18:23] <janimo`> Tassadar, indeed, what I figured
[18:23] <seb128> rickspencer3, sorry, *without*
[18:23] <rickspencer3> seb128, I understood
[18:23] <cjwatson> so they just have to stop landing, it's not like our developers are interchangeable
[18:23] <ogra_> hedz09, you need to create it the same way that the prepare_ubuntu_system() function from rootstock-touch-install uses, then unpack the tarball into it and copy the converted android system.img into var/lib/lxc/android/ in there
[18:23] <rickspencer3> cjwatson, right, I get it
[18:23] <Saviq> mterry, bug #1262879, too
[18:24] <janimo`> stgraber, right, the trust chain plans is what I was wondering about
[18:24] <mterry> Saviq, fine.  That tiny bit of python code can continue to live in unity8 code, even though unity8 tests don't need it.  But that doesn't change the fact that mediumtests need changing for split mode, to run greeter with testabiliity
[18:24] <ogra_> hedz09, and it is system.img, not System.img (no capital S)
[18:24] <barry> Tassadar, janimo` if you find things missing from the client, please do file wishlist bugs.  for the sake of stability i don't want to do much more with s-i in 14.04 except fix critical bugs, but i'm interested in doing more feature work after trusty is released
[18:24] <Saviq> mterry, they need changing to use whatever helper you provide to run greeter with testability
[18:25] <Saviq> mterry, the mediumtests scripts can't know what happens
[18:25] <janimo`> barry, I will if I find any bug :)
[18:25] <mterry> Saviq, it's not that simple, due to the way lightdm works
[18:25] <Saviq> mterry, I understand
[18:25] <Tassadar> barry: except for the duplicate keyring files bug it's fine
[18:25] <barry> Tassadar: yep
[18:25] <Saviq> mterry, but we still need to build as little knowledge as possible into mediumtests, and as much as possible into the components that the knowledge is of
[18:25] <barry> janimo`: cool
[18:26] <Saviq> mterry, or they will get stale,
[18:26] <Saviq> mterry, things will fail here, but not there
[18:26] <Saviq> mterry, we won't be able to reproduce locally
[18:26] <mterry> Saviq, but this isn't component knowledge, it's system knowledge
[18:26] <Tassadar> janimo`: oh, yeah, look at http://bazaar.launchpad.net/~vbocek/+junk/system-image-server-tasemnice/revision/221 and the bug linked in the commit message
[18:26] <janimo`> stgraber, any plans to package the server?
[18:26] <Saviq> mterry, good, then we need system helpers
[18:26] <mterry> Saviq, this particular instance of "run greeter with testability"
[18:26] <Saviq> mterry, maybe they need to live with the integration tests project that elopio is starting to build
[18:27] <janimo`> Tassadar, thanks I had just figured this out and used a full image to flash the phone. I had not done anything with deltas or actual upgrades
[18:27] <Saviq> mterry, with as much as possible abstracted closer to the affected services (and tested there)
[18:27] <stgraber> janimo`: I don't have any such plan personally, ubuntu-cdimage isn't package so I don't see a good reason to package ubuntu-system-image besides the server on which this actually runs is on precise and we don't have package installation rights, so having it packaged would just make things harder for me
[18:27] <Tassadar> janimo`: it'd bite you later and you'd have to edit the index.json files by hand
[18:27] <Saviq> mterry, I just want to save us the pain of having to run around after all the scripts that somewhere somewhen implemented a workaround
[18:28] <Saviq> mterry, we just need to say: to unlock the device, call foo.foo_unlock
[18:28] <Saviq> mterry, and that foo.foo_unlock needs to live somewhere outside of mediumtests
[18:28] <tedg> Saviq, I'm not able to revive the screen with this mir binaries. Either by locking with the button or timeout.
[18:28] <tedg> Saviq, Is that expected?
[18:28] <mterry> Saviq, I get the vision.  It's just that some calls have side effects.  Like in this case, probably a reboot and a system config change that will later need to be undone
[18:28] <Saviq> tedg, hmm just noticed
[18:29] <Saviq> tedg, actually no, works here
[18:29] <Saviq> tedg, try touching the screen
[18:29] <Saviq> tedg, maybe the compositor needs to catch up
[18:29] <Saviq> mterry, I understand
[18:29] <tedg> Saviq, Yeah, I think you have to generate an event.
[18:29] <Saviq> tedg, that can be expected, yeah
[18:30] <Saviq> mterry, but that "change, reboot, clean" logic might still be outside of mediumtests, and that's completely fine
[18:30] <Saviq> mterry, as long as that's the only documented and supported way of doing that
[18:31] <mterry> Saviq, sure.  I just think it makes it unsuitable for unity8 source.  But I can toss it in some elopio repository
[18:31] <Saviq> mterry, of course, that's why I said lightdm / unity8 / unity-greeter, but maybe even something global
[18:32] <Saviq> mterry, truth be told, there's probably only a few autopilot tests in unity8 that should remain there
[18:32] <mterry> Saviq, sure.  I thought mediumtests was a reasonable global place to put it (it has the rest of the kitchen sink in there).  But since we are apparently trying to get away from that, I'm happy to talk to elopio
[18:32] <Saviq> mterry, after all, they are integration tests, and how can you integrate just one project?
[18:32]  * Saviq AFK
[18:34] <tedg> Saviq, asac, confirmed to be the same bug, Saviq's binaries make it so alarms show.
[18:34] <tedg> (and make noise)
[18:34] <ogra_> finally
[18:34] <asac> tedg: cool
[18:34] <ogra_> :P
[18:35] <asac> now Saviq needs to RTK :)
[18:35] <asac> hehe
[18:35] <ogra_> (if people would just have listened to me 4.5h ago we would have had far less noise :P )
[18:36] <rickspencer3> ogra_, I'm strongly resisting the urge of suggesting that perhaps messaging is causing problems in the alarms, but I guess that would be more noise?
[18:36]  * rickspencer3 ducks
[18:36] <ogra_> lol
[18:36]  * rickspencer3 notes to listen to ogra early and often
[18:37]  * ogra_ hugs rickspencer3
[18:37]  * rickspencer3 hugs ogra_ :)
[18:37] <rickspencer3> we're getting there
[18:37] <rickspencer3> so close to promoting with Qt 5.2 !!!
[18:38] <seb128> ogra_, can you tell rickspencer3 to not lockdown the archive tomorrow? ;-)
[18:38] <ogra_> hahahaha