[08:34] <vitimiti> Hi
[10:41] <jgdx> hello vitimiti
[10:41] <vitimiti> Hello, jgdx
[10:45] <Zoomy500> hello
[10:46] <Zoomy500> Is there a way to install a ppa on Ubuntu touch?
[10:52] <chrisc> Zoomy500: mount the root partition read/write and then do it the same as for any other machine?
[11:55] <jgdx> chrisc, if you have phablet tools installed, it's $ phablet-config writable-image
[12:10] <jgdx> kenvandine, hey, could you take a look at the cellular ui split[1] The tests are failing but the failures seems spurious. [1] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/cellular-split-radio-pref-and-data-fix-1378812/+merge/238304
[12:12] <chrisc> jgdx thanks, all my other computers are running debian so i simply su and then remount rw...
[12:22] <jgdx> chrisc, it might be easier for most just to manage it via the file in /userdata/
[12:22] <chrisc> ah, i don't know about that, where is it documented?
[12:24] <jgdx> chrisc, here[1] under the section "Enabling read-write mode" [1] http://developer.ubuntu.com/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[12:24] <chrisc> jgdx: thanks
[12:24] <jgdx> chrisc, a pleasure!
[12:25] <chrisc> jgdx: so simply touch /userdata/.writable_image and reboot?
[12:26] <jgdx> chrisc, yeah – that probably does exactly the same thing you do, mounting it rw. :)
[12:27] <jgdx> I'm not sure actually.
[12:27] <chrisc> I have this alias set for the phablem user:
[12:27] <chrisc> alias mnt-root-rw='sudo mount -o rw,remount /'
[12:28] <chrisc> so i simply do `mnt-root-rw`
[12:28] <chrisc> s/phablem/phablet/
[12:29] <chrisc> which saves rebooting...
[12:31] <jgdx> chrisc, oh right. Cool
[12:31] <jgdx> whenever I reboot I do $ adb reboot, and then I get 10-15 seconds of free time to think
[12:31] <jgdx> :p
[12:31] <jgdx> it's a small vacation I cherish
[12:32] <chrisc> i only reboot when the gui is so messed up that a /etc/init/d/lightdb restart doesn't sort it
[12:32] <chrisc> :-)
[12:33] <chrisc> my android phone need far more rebooth than my ubuntu phone
[12:33] <chrisc> reboots
[12:33] <jgdx> well that's good!
[12:33] <jgdx> chrisc, if you find the time though, you might want to do a $ ubuntu-bug # or similar when you're in the messed up state
[12:34] <jgdx> better to file too many bugs than too few
[12:34] <chrisc> ok, but i'm running devel and updating via apt...
[12:34] <chrisc> i have posted some bugs
[12:34] <jgdx> thanks!
[12:34] <chrisc> like no ability to use a socks proxy with the web browser, think that was the last...
[12:51] <dobey> Tassadar_: hey. it seems the hammerhead builds aren't happening for devel-proposed or rtm channels at the moment
[12:52] <Tassadar_> devel-proposed is 297 same as on s-i.u.com
[12:53] <Tassadar_> and rtmp-proposed is on 104, same as on s-i.u.com
[12:53] <Tassadar_> if there are no new builds, then ubuntu build server simply has no new builds
[12:54] <dobey> hmm
[12:54] <dobey> Tassadar_: my n5 isn't showing an update as available
[12:54] <Tassadar_> which version do you have?
[12:55] <dobey> 103 from 14.09-proposed
[12:55] <Tassadar_> try running system-image-cli -n -v via adb/ssh
[13:00] <Tassadar_> http://system-image.tasemnice.eu/ubuntu-touch/ubuntu-rtm/14.09-proposed/hammerhead/ 104 is definitelly there
[13:01] <dobey> [systemimage] Oct 23 08:57:34 2014 (19199) [0xb5fd7350] Running group download reactor
[13:01] <dobey> and it's hanged there
[13:05] <Tassadar_> dobey: weird, I assume you tried rebooting?
[13:06] <dobey> Tassadar_: not exactly, but i hadn't seen any updates for probably over a week on devel-proposed and flashed to rtm propsed last night; got 103
[13:07] <Mirv> tsdgeos: https://bugs.launchpad.net/ubuntu/+source/qttools-opensource-src/+bug/1135394
[13:07] <Tassadar_> you can try accessing system-image.tasemnice.eu via web browser on your phone, to see if you can even get on that server
[13:10] <dobey> hrmm, it's not resolving for some reason :-/
[13:12] <dobey> now it works; for some reason it dropped the network
[13:12] <baudbaud> Hey, I was in here a couple days ago asking about using non-Click applications on Unity 8.
[13:12] <baudbaud> I tried running the Unity Next daily iso on a new x86_64 tablet, but clicking on text areas didn't bring up the on-screen keyboard
[13:13] <baudbaud> The "try Ubuntu without installing" option didn't have a terminal app, which would have been immensely useful
[13:13] <dobey> Tassadar_: so i can wget that url, but seems the update isn't showing up
[13:13] <baudbaud> When I was last here, I was told that there currently isn't a good place to file bugs like these. Is that still the case?
[13:14] <Tassadar_> dobey: system-image-cli is still stuck?
[13:14] <dobey> Tassadar_: yes
[13:14] <Tassadar_> have you tried rebooting?
[13:14] <dobey> not yet
[13:17] <dobey> Tassadar_: still stuck at that point, and no updates in the updates list
[13:18] <Tassadar_> dunno what to tell you
[13:18] <Tassadar_> I'm gonna try it in the evening once I get home
[13:19] <dobey> ok
[13:19] <dobey> i'm trying to do this on cellular data
[13:20] <Tassadar_> maybe try wiping /cache
[13:20] <Tassadar_> or see if it is full
[13:20] <Tassadar_> *check if it is full
[13:21] <Tassadar_> well, my ntb's battery is almost dead, bye for now
[13:24] <dobey> don't see any full partitions really. /lib/modules is 99%, but not sure why that is
[14:45] <mterry_> pmcgowan, can you make bug 1382212 critical?
[14:45] <vitimiti> Hi
[14:47] <pmcgowan> mterry_,it doesnt need to be critical to land, just reviewed on the wishlist
[14:47] <mterry_> pmcgowan, ah...  OK.  well that then
[14:47] <pmcgowan> mterry_, so add to that spreadsheet
[14:47] <mterry_> oh..
[14:47]  * mterry_ has not read some emails about the process I guess
[14:48] <mterry_> found it
[14:58] <pmcgowan> mterry_, I added it
[15:11] <pitti> ogra_: yay! just upgraded to image 104 (mako), and dpkg -l *autopilot* is empty!
[15:12] <ogra_> pitti, yeah !
[15:12] <ogra_> pitti, 40MB shoved off the rootfs tarball
[15:12] <pitti> wow
[15:13] <ogra_> and no obvious issues in smoke testing
[15:13] <pitti> ogra_: I'm running a test with adt-run now, to make sure that we can cover the "missing" packages with the "unpack into /tmp" trick
[15:13] <ogra_> cool
[15:13] <ogra_> let me know how it goes
[15:13] <ogra_> plars, ^^^
[15:13] <pitti> ogra_: I'm quite sure I need to teach it some additional tricks (like the autopilot udev rule), but let's see :)
[15:13] <ogra_> yeah
[15:14] <plars> :)
[15:14] <pitti> ogra_: oh, and did you notice that rsalveti found/fixed the RTM emulator breakage?
[15:14] <pitti> c'est un bon jour
[15:14] <ogra_> yep, we are just discussion how to land it in #ubuntu-ci-eng
[15:15] <ogra_> it is !
[15:15] <ogra_> 10 years ... and unicorns everywhere !
[15:15] <pitti> ogra_: oh yeah, adt-run is now pulling in a gazillion packages
[15:15] <ogra_> and everything seems to work smoothly today
[15:15] <pitti> ogra_: *shhht*, don't say that in a public channel!
[15:15]  * pitti fends off Dr. Murphy
[15:15] <ogra_> haha
[15:16] <ogra_> we have unicorn protectioon today ... murphy is out til tomorrow
[15:16] <pitti> ogra_: so as far as CI and testing goes, it's likely that we can keep this?
[15:16] <pitti> ogra_: oh, right!
[15:16] <ogra_> yep
[15:17] <ogra_> pitti, i asked plars to keep an eye out on the tests (i cant imagine we do not actually have at least one or two small regressions) but it seems all good so far
[15:17] <pitti> ogra_: well, p-test-run just apt-get installs everything with r/w, so that shouldn't make a difference?
[15:18] <pitti> so adt-run doesn't work right now, I'll figure that out
[15:18] <ogra_> yeah, indeed
[15:18] <plars> ogra_: still running, though reminders seems stuck on the auth issues
[15:19] <plars> TypeError: Argument 1 does not allow None as a value
[15:19] <ogra_> buit thats old
[15:19] <plars> balloons: ? I thought that worked now, or at least would make progress past that point
[15:19] <plars> ogra_: indeed, but if there are other things that were slated to run after and it gets stuck it could block them
[15:19]  * balloons reads backlog
[15:21] <balloons> plars, mm indeed, reminders should not be getting stuck
[15:21] <balloons> link?
[15:22] <ogra_> plars, how did 123 finishe then ?
[15:22] <ogra_> *finish
[15:22] <ogra_> it seems to have run fine over night
[15:28] <mterry_> kenvandine_, btw attached bug to that location-three-options MP
[15:30] <pitti> ogra_: oh right, we also pulled autopilot-qt; so Qt doesn't see the ap-qt module in /tmp/.../
[15:30] <ogra_> ah
[15:30] <ogra_> yeah
[15:30] <pitti> but when I wrote the qtsensors tests I figured out how to load Qt modules from the build tree, the same trick should apply
[15:31] <pitti> some more of these, and we can install a full distro into /tmp without root or writable / :)
[15:34] <plars> ogra_: 123 finished a long time ago I think
[15:34] <ogra_> plars, right
[15:34] <maxvi> when ubuntu phones will be released ?
[15:34] <plars> ogra_: going to be in a session for quite a while, and probably can't talk much
[15:34] <ogra_> plars, well, 123 was the last image ... with the dropped AP
[15:35] <ogra_> and reminders finished fine
[15:35] <plars> right, this is on mako that I'm watching though - 104 I think
[15:35] <ogra_> oh, ok
[15:35] <ogra_> i wonder why that would be device specific
[15:36] <ogra_> sounds more like a racy thing
[15:36] <ogra_> maxvi, soon
[15:38] <plars> ogra_: on 123,camera had quite a few more failures - might be one to check
[15:38] <ogra_> yep
[15:56] <pitti> ogra_: do you have a package delta for the autopilot drop?
[16:01] <vitimiti> Bye
[16:05] <ogra_> pitti, indeed i do (sorry, was afk) http://people.canonical.com/~ogra/touch-image-stats/rtm/123.changes
[16:06] <pitti> ogra_: thanks; that's pretty much what I figured out now too
[16:06] <ogra_> heh
[16:12] <pitti> apparmor="DENIED" operation="open" profile="com.ubuntu.calculator_calculator_1.3.334" name="/tmp/adt-run.Rjh6Qi/deps/usr/lib/libqttestability.so.1.0.0" pid=19165 comm="qmlscene" requested_mask="r" denied_mask="r" fsuid=32011 ouid=0
[16:12] <pitti> ogra_: oh! that would explain it :)
[16:15] <ogra_> pitti, didnt you call "phablet-config autopilot --dbus-probe enable" ?
[16:15] <pitti> does anyone know where I can find that apparmor profile?
[16:15] <pitti> ogra_: yes I did, but that only allows dbus, not file access
[16:15] <jdstrand> pitti: /var/lib/apparmor/profiles
[16:15] <ogra_> oh
[16:15] <ogra_> ok
[16:16] <pitti> jdstrand: cheers; that's built dynamically?
[16:17] <pitti> jdstrand: so as we don't install the autopilot qt modules any more, we need to put them into /tmp (or another writable path); I figure I need to dynamically adjust the rules to also allow reading from /tmp/<unpack dir>
[16:18] <jdstrand> pitti: when a click is installed, the click-apparmor system hook is run. that calls aa-clickhook which takes the security manifest in /var/lib/apparmor/clicks and generates the profile in /va/rlib/apparmor/profiles
[16:18] <jdstrand> pitti: yes, it sounds like you need to do the same thing that autopilot does
[16:18] <pitti> jdstrand: right, ap dynamically adds the dbus rule
[16:18] <jdstrand> pitti: right
[16:19] <pitti> jdstrand: I don't install a click, I test the installed ones, but should be the same principle indeed
[16:19] <pitti> jdstrand: sudo vi /var/lib/apparmor/profiles/click_com.ubuntu.calculator_calculator_1.3.334 won't work, I need to reload apparmor, right?
[16:19] <pitti> (for a first test)
[16:19] <jdstrand> pitti: so you have whatever rules you need in a profile, then run 'aa-clickhook -f --include=yourfile
[16:19] <jdstrand> '
[16:19] <pitti> ah
[16:19] <jdstrand> pitti: well, hold on
[16:20] <jdstrand> pitti: that aa-clickhook --include is your long term solution
[16:20] <jdstrand> pitti: for just testing your rules, modify the profile in /var/lib/apparmor/profiles, then do 'sudo apparmor_parser -r /var/lib/apparmor/profiles/...'
[16:20] <jdstrand> '-r' is for reload
[16:21] <pitti> ah, that's what I was looking for, cheers
[16:21] <pitti> blimey, it works!
[16:21] <pitti> so, initctl set-env QT_PLUGIN_PATH, adjust apparmor, and there we go \o/
[16:22] <jdstrand> nice! :)
[16:23] <pitti> jdstrand: so obviously directly finding and modifying /var/lib/apparmor/profiles/click_com.ubuntu.calculator_calculator_1.3.334 isn't right; what would you recommend how to do that for all click apps?
[16:24] <pitti> jdstrand: does does it actually have to happen per-click? (then I can re-use the same logic as AP)
[16:25] <jdstrand> pitti: for all click apps, that is what 'aa-clickhook -f --include=<your_rules_file>' is for
[16:26] <jdstrand> pitti: that will add whatever is in <your_rules_file> to all the policy in /var/lib/apparmor/profiles
[16:26] <pitti> jdstrand: ah, easy!
[16:28] <jdstrand> pitti: if you are running autopilot tests, you'll want to add those rules too. I just checked and aa-clickhook does not allow specifying --include multiple times, so I'll file a bug. however, to work around it you can just cat /usr/share/autopilot-touch/apparmor/click.rules to the end of your rules file
[16:29] <jdstrand> (perhaps as part of your script, so you don't have to maintain your autopilot rules)
[16:29] <Chipaca> larsu: bug 1384811
[16:30] <larsu> Chipaca: lp:~larsu/indicator-messages/allow-numbers-in-object-paths
[16:31] <larsu> tedg: can you have a look at this please? https://code.launchpad.net/~larsu/indicator-messages/allow-numbers-in-object-paths/+merge/239410
[16:33] <jdstrand> pitti: fyi, bug #1384812
[17:37] <pitti> sergiusens: btw, do you know why ubuntu-emulator snapshot --revert-pristine doesn't really revert?
[17:37] <pitti> sergiusens: the qemu images do seem to have snapshots, but after that I get a configured phone with my files instead of a first-time wizard with a pristine fs
[17:38] <sergiusens> pitti: I'd have to look into that as I just "imported" the same logic that was already there
[17:38] <pitti> sergiusens: my current workaround is to cp -r the entire instance dir, but that's a bit unwieldy
[17:38] <tsdgeos> renatu: font?
[17:38] <sergiusens> pitti: it is
[17:38] <pitti> sergiusens: ah ok; not that important, I just wanted to know whether "revert" was actually supposed to do that, as opposed to just wiping /userdata or so
[17:39] <pitti> sergiusens: (i. e. I want to clean up after apt-getting stuff)
[17:39] <larsu> tedg: thanks for the quick review ;)
[17:42] <renatu> tsdgeos, https://github.com/mozilla-b2g/moztt/commit/2372e891b10ff9a7382bbb4fbcd439a75cebd206
[17:43] <renatu> tsdgeos, this is the discussing bug https://bugs.launchpad.net/ubuntu-font-family/+bug/1137630
[17:46] <tsdgeos> renatu: kfontview doesn't like that font either
[17:46] <tsdgeos> but i can show other emojis fine
[17:46] <tsdgeos> i.e do you see 😉 ?
[17:48] <tsdgeos> renatu: also that Noto font is weird fontforge doesn't like it either
[17:48] <renatu> tsdgeos, yes but they are not colored :D
[17:49] <tsdgeos> correct
[17:50] <tsdgeos> i get a few
[17:50] <tsdgeos> http://paste.ubuntu.com/8643462/
[17:50] <tsdgeos> no clue how that important is
[17:50] <tsdgeos> can't help more
[17:50] <tsdgeos> sorries
[17:56] <pitti> jdstrand: oh, you are saying that I can't run aa-clickhook twice with a different file each time? i. e. would the second run undo the first one?
[17:56] <jdstrand> pitti: that is correct, but I gave a workaround in the bug
[17:58] <pitti> jdstrand: ack, thanks
[17:58] <pitti> jdstrand: it's not actually a big deal for me
[17:58] <jdstrand> ok. I'll fix it the next time I have a click-apparmor upload then
[18:10]  * vitimiti is back
[18:36] <afm> anyone working on porting that can offer some guidence?
[18:43] <pitti> jdstrand: hmm, what am I doing wrong here? http://paste.ubuntu.com/8643956/
[18:43] <pitti> jdstrand: NB I'm testing an already installed click
[18:44] <jdstrand> pitti: you also need '-f' to aa-clickhook
[18:44] <pitti> jdstrand: oh - that's the really expensive one, right?
[18:44] <jdstrand> yes
[18:45] <jdstrand> that changes all of the profiles to have the new rules, the compiles them, then loads them into the kernel
[18:45] <pitti> jdstrand: I know the click's name, so perhaps instead of -f I could just regenerate the profile for that click?
[18:45] <jdstrand> aa-clickhook without -f only updates files where the profile is missing
[18:46] <pitti> jdstrand: ah, that was the touch -h /var/lib/apparmor/clicks/${name}_*_${version}.json
[18:46] <jdstrand> pitti: you could rm -f /var/lib/apparmor/profiles/<profile> ; aa-clickhook --include=...
[18:46] <jdstrand> right, or touch the manifest
[18:46] <jdstrand> either will work
[18:46] <pitti> \o/
[18:46] <pitti> jdstrand: it works with -f
[18:46] <pitti> jdstrand: thanks muchly for your help
[18:47] <pitti> jdstrand: I already use that other workaround for a locally installed click package, so I'll see to factorizing this
[18:47] <pitti> but, AP tests now working with uninstalled autopilot and r/o image
[18:49] <veebers> pitti: nice
[19:00] <dobey> jhodapp: what project/package should i file a bug against for the AudioEngine api?
[19:01] <Tassadar_> dobey: I installed 103 from 14.09-proposed and it downloaded 104 just fine
[19:01] <jhodapp> dobey, what's the issue?
[19:01] <dobey> Tassadar_: thanks
[19:01] <Tassadar_> does it still not work for you?
[19:01] <dobey> jhodapp: it appears to read wav data over a named pipe, but doesn't actually play it through the speakers
[19:02] <dobey> Tassadar_: it doesn't.
[19:02] <Tassadar_> maybe strace system-image-cli to see what is it hanging on
[19:02] <Tassadar_> or just ctrl+c, it is python, it will show backtrace
[19:02] <jhodapp> dobey, file it against qtubuntu-media
[19:02] <jgdx> Why are we using ListItem.Standard as header in USS?
[19:03] <dobey> Tassadar: yeah but ^C just shows KeyboardInterrupt
[19:04] <Tassadar> maybe it is turned off?
[19:04] <dobey> Tassadar: what is turned off?
[19:04] <Tassadar> printing the whole backtrace
[19:04] <Tassadar> also, check if you have enough space in /cache
[19:05] <Tassadar> or what is in cache, might be something is blocking it for some reason
[19:05] <dobey> let me check. df -h didn't show it as full
[19:16] <dobey> jhodapp: https://bugs.launchpad.net/ubuntu/+source/qtubuntu-media/+bug/1384876
[19:17] <dobey> Tassadar: /cache/recover/ only has 400K in it, so I doubt that's the problem :-/
[19:17] <jhodapp> dobey, thanks
[19:17] <Tassadar> you can try deleting it, just to be sure
[19:17] <Tassadar> anyway, you have tried reboot already, right?
[19:17] <dobey> Tassadar: yes
[19:17] <Tassadar> dunno what to tell you, it works for me and the images are there
[19:18] <Tassadar> maybe bug barry, he works on system-image-cli (and isn't here right now)
[19:19] <dobey> yeah
[19:30] <dobey> Tassadar: ok, i let it sit there for a while and it seems to have thrown a TimeoutError now
[19:30] <dobey> ah well
[19:31] <Tassadar> the internet tubes might be clogged up with cats or something
[19:55] <jgdx> seb128, $ bzr ci -m "sweet header items" && bzr push
[19:55] <jgdx> let me know how it goes!
[19:55] <kenvandine> haha
[19:55] <kenvandine> seb128, i let the secret out about your header fix :)
[19:55] <kenvandine> seb128, now jgdx is drooling for it
[19:55] <jgdx> I've been dreaming about it for months
[19:57] <charles> nik90, it looks like we may also need to ping (zsombi? renatu?)  to bring them in on bug #1362341
[19:57] <charles> nik90, I have indicator-datetime marking the one-time alarms as disabled, as we agreed on, in my megabranch
[19:58] <charles> nik90, ie, tasks.ics gets updated s.t. the categories reads:
[19:58] <charles> CATEGORIES:x-canonical-alarm,x-canonical-disabled
[19:58] <charles> nik90, but clock-app doesn't update itself when that happens
[19:58] <nik90> charles: oh
[19:58] <charles> nik90, I don't know if that's a clock-app issue or a lower level one
[19:59] <charles> nik90, if you've got clock-app listening for that kind of change already, I can look at the lower levels and see if I can find the problem
[19:59] <nik90> charles: I think its a lower level issue
[19:59] <charles> nik90, ack. I'll investigate
[19:59] <nik90> since the Alarms SDK should technically listen for those changes
[19:59] <nik90> charles: when I mean lower level, I mean the Alarms SDK API
[19:59] <nik90> I think zsombi can provide a more educated answer to this
[20:02] <mterry> boiko, heyo!  You actually online?
[20:02] <boiko> mterry: yep
[20:03] <mterry> boiko, so in terms of listening for when to stop a ringtone, you should be able to just listen to Powerd signals (i.e. I don't think unity8 needs to be involved yet)
[20:03] <boiko> mterry: that's nice, I remember someone mentioning unity8 was eating those events and that's why we thought we would need it to forward them
[20:04] <mterry> boiko, we listen for those same events on DBus
[20:05] <boiko> mterry: nice! would you mind to point me to this code?
[20:05] <mardy> ricmm: hi! I have a problem with the network on one device (QNetworkManager is taking 10 seconds to initialize), do you know who could help me debug the issue?
[20:05] <mterry> boiko, you can see an example in unity8/plugins/Powerd/
[20:06] <mterry> boiko, ah, the signal is from unity-system-compositor, not actually powerd
[20:06] <mterry> boiko, but same difference
[20:06] <boiko> mterry: nice! thanks!
[20:06] <mterry> boiko, you want to look at the code that listens to DisplayPowerStateChange
[20:06] <mterry> boiko, (eventually you want to actually just pay attention to actual power button presses, not screen off events -- but that requires some re-architecting that isn't happening in short term)
[20:08] <ogra_> pitti, bug 1384841
[20:25] <one> hello everyone
[20:29] <one> hey i had to come and ask if anyones been porting the ubuntu phone os for any mtk chipset ?
[20:38] <Guest47970> hi
[20:38] <pitti> ogra_: I'm always fine to upload stuff directly -- I'm a core-dev :-)
[20:39] <pitti> ogra_: and FTR, big +1 on syncing
[20:39] <meko> yo
[20:39] <ogra_> pitti, well, better hope that olli didnt see that sentence :P
[20:39] <meko> how do get ubunto on sony
[20:41] <pitti> ogra_: *shrug* :)
[20:41] <ogra_> haha
[21:02] <mardy> cyphermox: hi! Do you have a few minutes to talk about bug 1380683?
[21:02] <cyphermox> err, sure, but I'm not sure just yet how I'll be able to help
[21:03] <mardy> cyphermox: eh, let's see :-) which room are you in?
[21:03] <cyphermox> I'm in the phonedations room
[21:03] <mardy> cyphermox: ok, coming
[21:12] <mardy> lpotter: hi! cyphermox told me that you are working on QNAM
[21:12] <lpotter> indeed
[21:13] <mardy> lpotter: can you please have a look at bug 1380683?
[21:13] <lpotter> the QtBearer backend was/is in need of much love
[21:13] <mardy> lpotter: in some cases, the device (N4) gets into a state where instantiating a QNAM takes 10 seconds
[21:14] <lpotter> off the top of my head, I blame synchronous dbus calls... which _should_ be resolved upstream soon
[21:15] <mardy> lpotter: it always takes about 10 seconds, so it really looks like a timeout
[21:15] <lpotter> upstream being 5.4, since 5.3 is rather closed
[21:15] <mardy> lpotter: I wonder what's the timeout on the dbus system bus...
[21:15] <lpotter> ahh. ok
[21:16] <lpotter> less than 20 seconds by default.
[21:16] <lpotter> err 10 even
[21:25] <sergiusens> mvo_: hey, can you tell me what I'm doing wrong here? http://pastebin.ubuntu.com/8645830/
[21:35] <charles> mihir, ping
[21:36] <mihir> charles: pong
[21:36] <charles> mihir, how does calendar-app read/save its events to EDS?
[21:38] <mihir> charles: we use QtOrganizer 5.0
[21:38] <mihir> charles: so we create/modify an object of Event.
[21:38] <charles> mihir, it looks like it's going straight to qtorganizer5-eds inside of EventListModel
[21:39] <mihir> charles: nope if you see save Function it does save to model.
[21:40] <mihir> model.saveItem(event);
[21:40] <mihir>             pageStack.pop();
[21:41] <charles> mihir, I should have phrased that better, it looks like it's using eds as the backend (ie, qtorganizer5-eds) and is instantiating the model in EventListModel
[21:42] <charles> and in the NewEvent, it calls model.saveItem() with the model it got from root.model.getCollections(), which is implemented in EventListModel
[21:42] <charles> mihir, I haven't done a huge amount of QML and am just making sure that I'm understanding the flow right :)
[21:43] <mihir> charles: yes we are using EDS as backend which is communicating to evolution calendar.
[21:43] <mihir> charles: does that make sense
[21:43] <charles> mihir, ya.
[21:44] <charles> I was just trying to understand where the QtOrganizer came from and how NewEvent was using it
[21:44] <charles> I'm trying to figure out where the timezone bug is, datetime, calendar-app, or qt5organizer-eds
[21:44] <charles> renatu: ^ :-)
[21:45] <charles> mihir, thanks
[21:45] <mihir> charles: np
[21:46] <charles> mihir, one last question, that model is a QOrganizerManager, right?
[21:47] <renatu> charles, we just merged this: http://bazaar.launchpad.net/~phablet-team/qtorganizer5-eds/trunk/revision/66
[21:47] <renatu> charles, maybe it fixes the bug
[21:48] <charles> renatu, is it in the images yet?
[21:48] <renatu> I do not know
[21:48] <charles> renatu, ok. I'll take a look. thanks for the link :)
[21:49] <renatu> mihir, could you test this branch: https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-atthendee-list/+merge/239460
[21:49] <renatu> mihir, check if you still having problems with all day events
[21:49] <renatu> charles, do you have the last image?
[21:50] <charles> renatu, I'm seeing the calendar-app issue in rtm r102
[21:50] <renatu> charles, check if the qtorganizer5-eds version is  0.1.1+14.10.20141010-0ubuntu1
[21:51] <renatu> charles, do you have the link to the bug?
[21:51] <charles> phablet@ubuntu-phablet:~$ dpkg -s qtorganizer5-eds | grep Version
[21:51] <charles> Version: 0.1.1+14.10.20141001.4-0ubuntu1
[21:51] <charles> nine days older
[21:51] <charles> renatu, do you have an armhf handy? :-)
[21:51] <charles> renatu, sure, one moment
[21:51] <charles> renatu, https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1372254
[21:52] <charles> renatu, ics porn in comment #7
[21:52] <renatu> charles, try that: https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-1311165/+merge/237142
[21:52] <charles> this sounds a lot like your fix
[21:52] <charles> renatu, ok
[21:53] <charles> renatu, was that really only two weeks ago? that review feels like... ~6 weeks ago :P
[21:54] <renatu> charles, it got stuck due the SDK release
[21:55] <charles> renatu, mihir, installing the armhf deb and re-testing
[21:55] <charles> I bet this is the fix
[21:56] <mihir> renatu: sure i'll do that and let you know tomorrow. my calendar doesn't work on device
[21:57] <charles> mihir, iirc there's also an autopilot test bug reported on calendar-app that's also related to timezones... might see if renatu's patch fixes that as well
[21:57] <mihir> charles: yup may be it should.
[21:57] <mihir> charles: i can double check this.
[21:58]  * charles curses at ubuntu-ui-toolkit for not supporting 12h in the time picker
[22:00] <charles> mihir, renatu: whoo https://www.dropbox.com/s/i371p98wzrdyrgy/2014-10-23%2017.59.19.jpg?dl=0
[22:00] <mihir> charles: Woohhh :D finally
[22:01] <mihir> charles: i am curious to know what it Event name and clock icon ?
[22:02] <charles> mihir, it's because I typed "Event name" for the event name, and because RTM still has the icon bug
[22:03] <renatu> charles, great
[22:03] <charles> mihir, I've got it now using the "calendar" and "calendar-today" icons
[22:03] <mihir> charles: great :)
[22:04] <mihir> charles: I am happy as it is not misguide  now to users
[22:05] <charles> :)
[22:07] <charles> hmmmm
[22:09] <charles> mihir, let's say you create a 9:00 event for a week from now, and sometime over the next week you go to a different timezone
[22:09] <charles> mihir, should the event be triggered at 9:00 of the timezone you're in next week?
[22:09] <charles> if so, this calendar.ics is still wrong :(
[22:09] <mihir> charles: good question.
[22:09] <mihir> charles: but again it should be depend on your phone timezone right?
[22:10] <charles> after renatu's patch, the timestamp's being converted to utc and then saved in utc
[22:11] <charles> which is an improvement, since they're both the same now :)
[22:11] <charles> but let's say you leave VA this weekend... how can EDS know what offset to apply to reverse that UTC-ification?
[22:12] <charles> mihir, does that make sense? We're in UTC-4, so when saved to calendar.ics the DTSTART gets 4 hours added to it
[22:13] <charles> but there's no way to know "four hours" is the magic number when we're in a different timezone
[22:13] <charles> probably better to save these as floating times and leave UTC out of it entirely
[22:15] <mvo_> sergiusens: hi, sorry, only just now saw it, can we debug tomorrow?
[22:16] <mihir> charles: hmmm
[22:16] <mihir> charles: may be we can do that.
[22:16] <mihir> charles: but still i am not sure.
[22:27] <renatu> charles, mihir , yes if you want the event to be in a fixed time even if you change the device timezone you need to save it as floating time, like the alarm does
[22:27] <renatu> charles, mihir, but this is not common on calendar events since they are events and events are based on timezones
[22:28] <renatu> charles, mihir, but both case are supported by qtorganizer-eds
[22:39] <mihir> renatu: charles we need to discuss and come out for the conclusion how should we store this.
[22:39] <mihir> but yes as of now charles let's keep it fix in UTC
[22:43] <mardy> lpotter: hi! still there?
[22:44] <mardy> lpotter: I was just looking at the proposed changes to qnam, and I think I saw some problems in https://codereview.qt-project.org/#/c/97542/
[22:44] <mardy> lpotter: I'll comment there
[22:45] <lpotter> ok