=== LarrySteeze|Away is now known as LarrySteeze === h[a]kr is now known as hakr === alecjw_ is now known as alecjw === Namidairo`bnc is now known as Namidairo === ricardodrosales is now known as ricdros [01:20] hello everyone, i just wanted to check in to see how its going with Ubuntu-Touch for the 2013 Nexus 7 tablet model FLO running Android 4.4? [01:20] has anyone successfully ported it yet? [01:20] and has anyone here been able to install with multirom?... [01:22] afaik you can't dualboot android/ubuntu w/ multirom [01:23] because ubuntu-touch and android are still having problems communicating with eachother right? [01:23] the problem is on the ubuntu end from what i have read from XDA... [01:23] i want to take this time to thank the developers/contributors [01:24] we all owe you so much...please know your hard work is very much appreciated and you are what make the open source community linux/android community great [01:24] it has nothing to do with communication... they just can't live besides eachother :/ [01:24] i really hope that we get Ubuntu-Touch soon for N7 [01:25] oh ok i thought maybe it had to do with something like sharing a kernel or something along those lines... [01:25] yeah [01:25] sharing kernel is the problem iirc [01:26] actually, seems possible... [01:26] http://askubuntu.com/questions/261539/can-i-dual-boot-a-nexus-4-with-touch-preview === thomi_ is now known as thomi [01:48] ya i think ubuntu touch can be dualbooted with multirom on the Nexus 4 and Nexus 7 2012 but not the newer Nexus 7 device... [01:48] sorry for the late response [01:49] aah, makes sense [02:24] Can I lock orientation in Touch yet? I don't want any app at all to switch between landscape and portrait modes, regardless of how I hold the phone... === shuduo_afk is now known as shuduo === chriadam|away is now known as chriadam === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [03:28] Hey all, my ubuntu touch (mako) does not seem to have a wifi interface, anyone seen something like that before? === spence_ is now known as spence === shuduo is now known as shuduo_afk === LarrySteeze is now known as LarrySteeze|Away === Namidairo is now known as Namidairo`bnc === Namidairo`bnc is now known as Namidairo [04:55] Anyone have any ideas about a missing wcnss.mdt making wlan0 not exist on mako? === Namidairo is now known as Namidairo`bnc === Namidairo`bnc is now known as Namidairo === shuduo_afk is now known as shuduo === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === fisuk1 is now known as fisuk [06:36] is ubuntu touch compatible with note 2 [07:01] How can I download latest binary version for my Nexus? Are they available on launchapd? I don't want to compile it myself. Or how to easily compile only ofone. I'm searching for bugfix made only few days ago: 05 Dec [07:04] PoltoS: http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/ I believe. [07:15] PoltoS: phablet-flash will install the latest image for you; once you've got an image on your phone, the “Updates” section of System Settings will do OTA updates for you. [07:18] pitti, ping [07:18] RAOF, will it keep my data intact? I've contacts, images,... [07:19] PoltoS: Yes, data intact. [07:20] RAOF. Cool! thanks. [07:21] RAOF: is there a way to make FULL backup in case something goes wrong? Data + Image [07:21] phablet-flash might have something? [07:24] hey tvoss [08:17] hello everybody, I was curious to know if any more developments have been made for touch on the razr xt912 spyder. I contacted a developer on the provided page and he told me he had not heard from the software writer in over a year. The last update was in March so I was just curious as to whether anything has been updated for this device. === iahmad is now known as iahmad|afk === iahmad|afk is now known as iahmad === chriadam is now known as chriadam|away === Guest86827 is now known as JamesTait === JamesTait is now known as Guest44086 === Guest44086 is now known as JamesTait [09:35] om26er: need a bit of help with an AP problem when you have a minute [09:35] nerochiaro, sure, what is it? [09:36] om26er: i'm trying to write an AP test that access the Tabs object inside a MainView, and then tries to access the Tabs.selectedTab property. But even if the property is there, AP tells me it doesn't exist [09:37] nerochiaro, can you share the code where I can reproduce the problem [09:37] one minute [09:42] om26er: you can check lp:~amanzi-team/gallery-app/gallery-app-save-state and the file tests/autopilot/gallery_app/tests/test_picker_mode.py. There's a test test_save_picker_state which has a comment at the end where the problem happens [09:42] nerochiaro, ok [09:42] popey, ISTR from a recent screenshot you posted that you are, or were, running bitcoin-app on your nexus 4. Does it still work for you today? [09:43] JamesTait: there's two. one is a bitcoin wallet, one is a currency converter, which one? [09:43] The wallet. [09:43] JamesTait: and which image you running? [09:44] yes, works for me on #55 [09:44] trusty-proposed. r55 I think. [09:44] note there's a bug in #55 [09:44] bug 1259253 [09:44] bug 1259253 in click (Ubuntu) "UID changes for clickpkg user breaks app updates/installs" [High,Triaged] https://launchpad.net/bugs/1259253 [09:44] Click installation and upgrades? [09:44] you may need to chown your /opt/click.ubuntu.com yes [09:45] Yeah, I noticed it and was going to report it, but saw that someone *cough* had already done so. ;) [09:46] You're too efficient, Mr Pope. :-P [09:46] conveniently it was the first thing I happened to test [09:46] because someone added an app to the store that I wanted to test [09:46] can't even remember what it was now [09:51] Seems like I have other problems with my device anyway - bitcoin wallet just segfaults for me. :( [09:51] have you updated it? [09:51] he's fixed a bunch of bugs === rachelliu_ is now known as rachelliu [10:22] popey, I did update it. It was working fine before, but 0.3.2.1 isn't working for me currently. I built it from source on my laptop and it also fails there, but then I reverted the source to an earlier version that I'm pretty sure did work on the phone, and I got the same result, so I'm not convinced that what I'm doing is proving anything. :) [10:22] Except maybe that I'm rubbish at building this particular app. :-P [10:23] JamesTait: any logs in /home/phablet/.cache ? [10:27] popey, nothing in org.sambull.bitcoin-app; I'm not sure about upstart logs yet. :) [10:29] Ah, a JRE error in ~phablet/.local/cache/upstart/application-click-org.sambull.bitcoin-app_bitcoin-app_0.3.2.1.log [10:29] "Internal Error (is_linux_zero.cpp:285) ... fatal error: caught unhandled signal 11" [10:30] Sorry, that's "os_linux_zero.cpp". My typing is terrible today. === cjwatson_ is now known as cjwatson [10:35] zsombi: hi, quick question about StateSaver: it seems that it doesn't work if the app is sent a SIGINT or SIGTERM. I was talking yesterday with greyback to modify it so that it catches that signal and does the proper saving. I need because otherwise there's no way to run AP tests for StateSaver on desktop [10:36] nerochiaro: ok [10:38] nerochiaro: fiel a bug so we can follow it [10:38] file I mean [10:38] zsombi: ok, against ubuntu-ui-toolkit ? [10:38] nerochiaro: yep [10:38] nerochiaro: let's see whether we can catch that in the plugin... [10:39] zsombi: i don't see why not [10:50] Mirv, ping [10:58] greyback: you said yesterday that MIR on devices can send a signal to apps requesting them to terminate. is there a way to do that in an AP test using the unity8 Shell ? [10:59] Morning all [10:59] nerochiaro: when you switch away from an app, the app gets the "save your state" signal. So if you can have AP do that, it should work [11:00] greyback: but it's not what the test should test, i want to test on app termination [11:01] nerochiaro: that's not done by shell yet. AFAIK only the OOM killer is killing apps right now [11:01] greyback: eww, ok. how do i switch away from the current app using the shell, then ? [11:02] nerochiaro: same as you'd do yourself: left edge swipe, or show launcher and click Dash icon. === shuduo is now known as shuduo_afk [11:02] greyback: i mean, how do i do that from AP. does the shell provide emulators to do the edge swipes ? [11:04] nerochiaro: you'll need to dig into unity8's AP test suite to see how it's done. We have added methods to make it easier (i.e. things like self.main_window.get_greeter().swipe() to swipe away greeter) [11:04] greyback: ok, i'll have a look into that stuff then. thanks [11:05] nerochiaro: am I right that you want to test that your app is saving & restoring state? [11:05] greyback: correct. save state between application runs, however [11:05] greyback: or at least that was the requirement [11:06] greyback: i am ok as a workaround for now having a "unfocus app" before killing it and restarting it again [11:06] greyback: to ensure state is saved [11:06] nerochiaro: yep I see. That's something I expect most other apps will need to do. We need proper solution for this [11:07] nerochiaro: I think your SIGINT idea is best tbh [11:07] greyback: i filed a bug for that. zsombi is aware of it. not sure when it will be taken care of [11:07] nerochiaro: ok === rachelliu_ is now known as rachelliu === chihchun is now known as chihchun_afk [11:28] kalikiana_, tvoss: seems google test doesn't have qmake integration; would it be okay to write the qtubuntu-sensors integration tests (i. e. test QtSensors API against simulated sensors from platform-api) with QtTest? [11:28] as that seems to be Qt's standard test framework, and qtubuntu-sensors is all Qt/qmake [11:30] pitti, kalikiana_ I thought qtubuntu-sensors is cmake? [11:31] nope [11:31] * pitti does his first steps in qmake [11:31] pitti, I would rather prefer switching over to cmake then, especially with our cmake cross-building efforts [11:32] kalikiana_, who is taking care of qtubuntu-sensors nowadays? [11:32] ok; can this be done by someone who already knows cmake and qmake? [11:32] pitti, I would think so [11:33] ok, I'll just write some minimal qmake files for local experimentation, so that I can learn about the QtSensors API [11:33] moving example tests from QtTest to gtest shouldn't be a big deal [11:33] tvoss: if your measure is who touched the code last it might be me :-] I'm not sure there's an actual owner [11:34] pitti, ack, get started, I will get you a cmake setup [11:34] popey, fyi I removed the data dir for bitcoin-app and now it starts, so I guess there's a problem with my wallet. :( [11:47] kalikiana_: hm, qmake is *absurdly* easy :) [11:47] I must say, first impression is quite nice === _salem is now known as salem_ === chihchun_afk is now known as chihchun [11:57] I would phrase it this way, if you have basic needs it's easy, but it doesn't scale [12:00] kalikiana_: how can I tell the QtSensors API which backend to use, in particular the qtubuntu-sensors one? [12:04] pitti: I don't think you can from the API. It loads what it can [12:05] maybe for tests the lib path can be set to achieve that [12:05] kalikiana_: I was wondering because on my desktop I don't hav any particular backend installed, and instantiating a proxmity sensor succeeds [12:05] kalikiana_: right, I'll do that, but it should fail if I don't [12:06] I guess it falls back to some builtin dummy backend [12:06] kalikiana_: well, I'll play around a bit [12:06] well it can't fail by default because it's normal that you have no backends on the desktop :-D [12:06] it would be slightly unusable [12:07] I didn't yet find a "valid" property or something equivalent, which would tell me whether the thing I just instantiated actually makes sense [12:12] kalikiana_: ah, got it [12:12] QCOMPARE(sensor.isConnectedToBackend(), true); [12:12] that fails [12:12] (as I expect) [12:32] kalikiana_: did you ever try running the plugin from the source tree? [12:32] kalikiana_: I created a lib/sensors -> . symlink, and run with QT_DEBUG_PLUGINS=1 QT_PLUGIN_PATH=`pwd`/lib [12:32] but I get [12:32] "Plugin verification data mismatch in '/home/martin/ubuntu/qtubuntu-sensors/integration-tests/lib/libqtubuntu_sensors.so.1.0.0'" [12:33] does that ring a bell? [12:35] kalikiana_: oh wait, that's not actually the plugin, that's in plugins/, sorry [12:36] kalikiana_: OOI, what does that library do? I thought the official API was QtSensors only? [12:38] I've always used 'make install', no idea about that error I'm afraid [12:39] pitti: not sure I understand the question - what do you mean by "that library"? [12:39] kalikiana_: yes, QT_PLUGIN_PATH=`pwd`/plugin works fine [12:39] kalikiana_: what is lib/libqtubuntu_sensors.so.1.0.0 ? [12:39] kalikiana_: (it gets installed into /usr/lib as a public system library) [12:40] which smells fishy, given that this package says it's a Qt plugin, and isn't multi-arched, etc. [12:40] the plugin itself doesn't link to this [12:40] it contains the code used by the plugins [12:41] didrocks: so I've not seen anything really bad in 54 or 55 and 55 seems better on memory use too. I have about 76MG free running the same app as yesterday on 54 [12:41] maybe it "should" be installed elsewhere, not sure [12:41] didrocks: so there is only popey's issue [12:42] kalikiana_: I thought plugin/libqtubuntu_sensors_plugins.so woudl contain that code? (and it doesn't link to libqtubuntu_sensors.so) [12:42] kalikiana_: sorry for newbie questions, I'm still trying to understand the structur [12:42] e [12:42] davmor2: yesterday the phone was 100% now it's ~3% in less than 7hours because i left the system settings opened :( [12:43] davmor2: indeed, I think it's a good test case (installing a click app, ideally after upgrade :)) [12:44] didrocks: installing is working from what I can tell it was upgrading that wasn't right? but because monday is my fresh install day there were no updates for me :( [12:44] pitti: look at lib/lib.pro versus plugin/plugin.pro [12:44] popey: ^ [12:46] kalikiana_: is that lib used by the plugin, or by applications that want to use the ubuntu sensors, or something else? [12:46] didrocks: maybe I should create a test app that we can update at will, I'll look into that after lunch [12:47] davmor2: not really, if you look at the bug report, it's: [12:47] - installing an older image [12:47] (before the new click package, so like #32) [12:48] - upgrading to latest image and try to install/upgrade a click apps [12:48] davmor2: no, installing didnt work [12:48] pitti: by the plugin only afair. [12:52] popey, didrocks: right okay so the only issue there would be the time taken to install the one older version upgrading to the new to install one app. However it might be a justifiable case for doing an old stable install once a month and upgrading to the current and ensure everything works maybe? [12:52] kalikiana_: still weird, as the plugin doesn't link to it, and you can even drop the -lqtubuntu_sensors from plugin/plugin.pro .. [12:52] davmor2: I guess maybe before each promotion, installing latest promoted image and upgrading [12:52] indeed [12:53] but that would possibly find _this_ issue [12:53] but perhaps not others which would be uncovered by dogfooding them upgrading [12:53] e.g. where files in ~/ become fragged during the upgrade [12:54] popey: indeed but I am limited on the amount of time I can spend on this each day. [12:55] I wasn't necessarily saying you ☻ [12:55] popey: :) [12:57] didrocks, popey: so how about this. Install old promoted image. Install some apps and data (music/vidoes/app and run the apps) then upgrade to the current proposed promoted image and makes sure the data and the apps work and that the apps can be updated and new ones installed? [12:58] davmor2: yeah, do not forget you need to log in to ubuntu sso for that (which is a good one :)) [12:59] didrocks: yeah I do that on every fresh install to get my apps that I use daily back on anyway :) [12:59] great ;) === greyback is now known as greyback|lunch [13:07] xnox: Have you been able to get at system settings in the emulator? I just get a white screen [13:08] Or if anyone knows another way to log into Ubuntu One ... === bfiller is now known as bfiller_afk [13:09] ricmm: hi, Kaleo suggests that maybe you can tell me if there is already a clean way from an autopilot test to request an application to close === chihchun is now known as chihchun_afk [13:11] cjwatson: can you copy over ~/.config/libaccounts-glib from a working device? [13:12] popey: hmm, maybe [13:13] guess you also need ~/.config/signond ? [13:14] sil2100: tvoss: pulling the question over here see pitti in the backlog. seems related to "for qtubuntu sensors and the symbols file in there: Do you really want to version all those symbols or are you just interested in the exported symbols for loading the plugin" maybe it makes sense to see if the public lib is needed at all [13:15] from the .pro files I thought the plugin is using the lib, but it doesn't seem to link to it [13:15] kalikiana_, but: the plugin still needs the symbols from the lib [13:15] kalikiana_, as far as I understand it [13:16] tvoss: so I thought until pitti suggested it doesn't link to it - I'm wondering how that fits together [13:16] maybe it pulls its in statically in a way I don't see in the .pro file [13:21] kalikiana_, okay, do the feedback symbols go to sensors, too? [13:22] feedback is a separate .so [13:22] it has no normal lib [13:22] cjwatson: you can login into ubuntu one via command line. [13:23] cjwatson: i don't remember the interface but it should be the same as people used to setup online account for facebook & twitter [13:23] cjwatson: before we got online accounts pane in the settings. [13:23] cjwatson: not sure if 2fa will work, so do try to login with ubuntu sso which doesn't have 2fa enabled. [13:23] tvoss: I don't know why there's a public sensors lib to be honest. that's why I said maybe it should just be removed/ merged [13:24] I don't think it is needed [13:24] kalikiana_, okay, let me push my cmake setup [13:25] kalikiana_, pitti lp:~thomas-voss/qtubuntu-sensors/cmake [13:25] kalikiana_, pitti builds, but fails at package build time due to symbol issues [13:30] tvoss: so you indeed build just two libs [13:30] sensors/feedback [13:31] kalikiana_, yup, and those are installed to the respective plugin directories [13:33] I'm not quite sure on the symbols. it probably makes sense to include feedback, though we don't really want to expose api [13:34] should symbols be used to check the implemented interface? === Ursinha-afk is now known as Ursinha === Ursinha is now known as Guest48115 [13:47] re from lunch [13:47] kalikiana_, tvoss: .symbols files are only used for public libraries, i. e. which you install into /usr/lib/ and you have a -dev package with header files [13:47] this doesn't seem to be the case for this ominous libqtubuntu_sensors.so.1.0.0 [13:48] pitti, ack [13:48] and yes, statically linking that into the plugin would be clearer; I still don't know what it does (I'm not claiming it can be dropped, I'm not that far into understanding it yet) [13:48] pitti, the cmake setup I pushed does the static linking. As I understand it, we could safely drop the .symbols file from the packaging setup [13:50] om26er: does unity8.process_helpers.restart_unity_with_testability work for you ? it fails with this error for me on yesterday's image: http://pastebin.ubuntu.com/6551217/ [13:51] nerochiaro, is the screen turned on ? [13:52] nerochiaro, try to turn on the screen of the phone before restarting unity === Guest48115 is now known as Ursula [13:55] tvoss: cmake/EnableCoverageReport.cmake is a standard copy&paste file, I guess? [13:55] (and similarly the other cmake/ files) [13:55] yay for having to do so much code copies :/ [13:56] tvoss: nice! === Namidairo is now known as Namidairo`bnc [13:56] pitti, I have a branch factoring out all the common cmake functionality, still need to make it a proper project [14:00] om26er: yes it is on [14:00] nerochiaro, I am updating my phone, will test [14:01] tvoss: ah good, so that will become a cmake-building-blocks build dep in the future? [14:01] pitti, yup, that's the idea. If nothing comes in between, I should have a package by the end of the week, at least for reviewing purposes === jdstrand_ is now known as jdstrand [14:03] gah [14:03] I HATE GROUPER [14:03] popey: I'm sorry, my device is just not reliable enough right now for me to be able to test this in a useful way [14:03] so frustrating [14:03] bummer. [14:03] popey: do you have a device in a broken state right now? [14:04] yes [14:04] cjwatson: as popey is in a broken state, maybe just patching the file would work for him? [14:04] (popey is always broken :p) === Namidairo`bnc is now known as Namidairo [14:07] this is true [14:08] i need to go afk at :30 for ~2 hours - personal appointment. [14:08] popey: ok, could you first record "find /opt/click.ubuntu.com -ls" in a file, apply the output of "bzr diff -c317 --new lp:click click/database.py click/hooks.py" live (patch -d /usr/lib/python3/dist-packages/click -p1), reboot which should fix it, and then record the output of "find /opt/click.ubuntu.com -ls" in a different file and send me both those records? [14:08] ok [14:09] if I had either (a) a working physical device or (b) an emulator with a working U1 login, I could do this myself :-/ [14:10] no worries. === rachelliu_ is now known as rachelliu [14:11] om26er: after a reboot it worked, not sure why. sorry for the noise [14:11] cjwatson: alan@deep-thought:/tmp/cjw$ bzr diff -c317 --new lp:click click/database.py click/hooks.py [14:11] bzr: ERROR: Not a branch: "/tmp/cjw/click/database.py/". === dem0n is now known as Guest12176 [14:12] need to bzr branch lp:click first? [14:12] oh right sorry, tested in the wrong place [14:12] "bzr diff -c317 lp:click" and filter out debian/changelog then [14:13] k === dandrader is now known as dandrader|afk [14:15] kalikiana_: do you know/have a preferred way of manually testing qtubuntu-sensors? [14:15] (actually it looks like "bzr diff -c317 lp:click/click" works anywhere, even though that's rather confusing syntax) [14:16] kalikiana_: like some example programs which put values/changes to cout, or some app which uses the accelerator === bfiller_afk is now known as bfiller [14:16] kalikiana_: platform-api supports proximity, light, and acceleration, but AFAICS qtubuntu-sensors only implementes accell, right? [14:16] ok, rebooting after patching [14:16] (it patched database.py, hooks.py and tests/test_database.py fine) [14:19] cjwatson: http://popey.com/~alan/before.txt http://popey.com/~alan/after.txt [14:19] rsalveti: sergiusens: so i've looked at the android-emulator packages and all the dependencies generated are api/abi compatible all the way back to precise. Hence I simply copied the latest trusty binaries into a PPA from precise to saucy. [14:20] rsalveti: sergiusens: i will test them, but by the looks of things we don't even need to rebuild the emulator to provide it on stable releases. [14:20] xnox, sounds good; I was waiting on that to split it up a bit [14:20] xnox: iirc bzoltan was going to take care of that together with the sdk work [14:20] yeah, it should be fine [14:20] popey: ok, couple of minor wrongnesses there which I'll look into, but that should fix the bug? [14:20] rsalveti: sergiusens: at the moment it's pending publication in https://launchpad.net/~ubuntu-toolchain/+archive/android/+copy-packages [14:20] xnox, as I only want to have a runtime and just download and setup everything else from phablet tools (go get launchpad.net/phablet-tools/ubuntu-emulator) [14:20] rsalveti: sergiusens: my expectation is to simply seed "android-emulator" package to the ubuntu-sdk seed. [14:21] cjwatson: i'll try installing something new [14:21] xnox: right, but I'd wait a bit more as sergiusens is changing the package and renaming it as well [14:21] popey: could you manually chown /opt/click.ubuntu.com/.click/log first? [14:21] sergiusens: sure, we do want to split -bin & images, and only provide a small package with bin. [14:21] popey: I'll fix that in the code [14:21] besides cleaning up the build/run scripts [14:21] ok [14:21] xnox, I want to get rid of the 'android' name as well; it's basically a fork [14:21] ubuntu-emulator-runtime; ubuntu-emulator-data or something like that [14:22] rsalveti: sergiusens: i know this is not permament, but at least this enables to test pre-build emulator on previous releases, right now. [14:22] fine by me [14:22] without doing any additional work, which is well taking dev time away. [14:22] sergiusens: do you know when you'll have your changes ready for review? [14:22] cjwatson: yes, that appears to have fixed the bug. [14:22] xnox, yeah, but given the sdk is broken on precise, quantal and I think raring; I'm in no hurry [14:22] * xnox *giggle* [14:22] tested by installing a new app I've never installed. [14:22] rsalveti: xnox: That is correct... the sdk integration is on me [14:23] sergiusens: ok, so at least the emulator is not blocking anything at the moment. I'll test it stand-alone on precise-saucy, to make sure there are no surprises. [14:23] rsalveti, the packaging of android-emulator or the tools? [14:23] popey: great, thanks. I'll just work on clearing up these loose ends and then land [14:24] np, thanks for dealing with it quickly. [14:24] sergiusens: originally my plan to split was to package src tarball, e.g. android_*orig.tar.gz simply shipped as is in a binary package, and then various other packages can simply build-depend on it "to only get the sources" and then we can have src package per device and/or emulator. [14:24] sergiusens: both [14:24] rsalveti, ogra_, you guys should know :) mzanetti had his galaxy nexus vibrate on touch a few days ago - that something we've enabled or? [14:24] rsalveti, always so needy :-) [14:24] Saviq: not that we know :-) [14:25] mzanetti, Friday, you say [14:25] sergiusens: and well build mako/maguro/nexus/emulator all in parallel, just upload N amount of no-change source packages. which rebuild across multiple builders. Instead of spending 40m on a single builder. [14:25] mzanetti, you mean just after the Thursday Xmas party... [14:25] Saviq: :D [14:25] dude, that was just withdrawal [14:25] Saviq: I don't think I've been that drunk that it would relate [14:25] lol [14:25] sergiusens: rsalveti: is emulator running mir or is it using surface flinger? [14:25] xnox, mir [14:26] yup, mir [14:26] rsalveti, any idea if haptics is on anyone's plate? [14:27] Saviq: ChickenCutlass is developing that in go, and sergiusens is currently merging and getting that ready to be integrated [14:27] but we're still missing the platform-api part of it afaik [14:27] rsalveti: Saviq right. We need to extend it out to qml [14:27] rsalveti: Saviq going to have ricmm do that [14:27] via platform api [14:28] ChickenCutlass, rsalveti cool [14:28] Saviq: so you will have an api like On/Off/Pattern [14:28] ChickenCutlass, christina (design) is asking who can she talk to about them [14:28] (them == vibrations) [14:29] lol [14:29] sergiusens: rsalveti: ok thanks for update. I'll go back to improving cross-compilation then. === dandrader|afk is now known as dandrader [14:30] ChickenCutlass, shall I put you on the line, and you'll talk who to put there next? [14:31] sure === greyback|lunch is now known as greyback === tdaitx_ is now known as tdaitx [14:46] ricmm: ping [14:51] nerochiaro: otp [15:12] ricmm, what's the status of the libhybris fix? [15:14] rsalveti: ricmm: the dialer-app crash seems to be Mir related: https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-dialer-app-autopilot/52/artifact/clientlogs/application-legacy-dialer-app-.log/*view*/ [15:14] rsalveti: ricmm: or at least that's what the logs suggest [15:18] boiko: related to what? [15:18] kenvandine: did you see my friends-app branch? [15:21] mardy, not yet [15:21] i'll look for it [15:24] mardy, i see CI failures :) [15:24] haven't looked at the logs though [15:25] kenvandine: yep, because it depends on the app-access branch [15:25] ah [15:25] is that app-access branch ready to be merged? [15:26] i didn't approve it because i wasn't sure if you were ready === alan_g is now known as alan_g|tea === shuduo_afk is now known as shuduo [15:41] mardy: kenvandine: ^ if that app-access branch gets merged, any chance mine can sneak in too? :) [15:42] cwayne, maybe, up to mardy :) === alan_g|tea is now known as alan_g [15:43] didrocks: right I'm going to be looking at running my tests in a bit any preference on which image? === shuduo is now known as shuduo_afk [15:52] renato, i'm adding the type for contacts, but no associated store [15:52] renato, the hub will fallback to using CacheLocation [15:53] kenvandine, ok nice [15:53] since vcards shouldn't persist [15:53] and the hub cleans those up automatically [15:57] + [16:07] tvoss, kalikiana_: ok, have a first PoC test case running, it already found the first bug :) [16:08] pitti, \o/ [16:08] tvoss: before I spend much more time on it (as putting it all together is rather specific wrt. Qt vs. GTest), are you going to propose your cmake change? [16:08] or does this need some further discussion? [16:09] pitti, give me some time tomorrow with a fresh mind, need to test on the device, too [16:09] pitti, but I do not see anything blocking right now [16:09] kalikiana_, ^ thoughts? [16:09] tvoss: sure, no problem; I have tons of other stuff to work on in the meantime :) [16:10] pitti, cool :) === dandrader is now known as dandrader|lunch [16:18] kgunn: hello! Could I poke you about some unity8 and qtubuntu tasks needing attention? [16:18] sil2100: what's up ? [16:19] kgunn: so, since we still have some time before we actually get anything landed, didrocks asked me to poke you about one flaky AP test in unity8 we seem to be having [16:20] kgunn: http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/unity8-autopilot/558729/ <- it seems to be flaky on maguro, mako is fine [16:20] kgunn: we want to remove all the unreliable tests - either by fixing them to be non-flaky (;)) or removing them in overall [16:20] tvoss: pitti I'd say let's get the cmake stuff in first and start cleanly with the tests on top of that - there're no code changes so it's as cheap as verifying it installs in the right places, later it would become more involved [16:20] So that no re-runs are needed [16:21] bfiller: is somebody on your team working on an API to tell if a device has a keyboard and/or mouse? [16:21] kalikiana_, yup, agreed [16:21] sil2100: i would totally be for removing them on maguro...is that possible ? [16:21] alternately, MacSlow could take a look but it'd be low priority.... [16:22] mhall119: there is a work item on this blueprint assigned to Kaleo from sdk team: https://blueprints.launchpad.net/ubuntu/+spec/appdev-1311-apps-convergence [16:22] kgunn: just for maguro? Not sure if we allow for different test suites per-platform, this would have to be done AP-wise - or maybe removed in overall? [16:22] kgunn: (or just disabled for now maybe) [16:22] Like skipped or something [16:22] sil2100: to me the best thing would be remove for maguro...but keep on mako.... [16:22] surely we need this capability [16:22] ah, thanks bfiller [16:22] sil2100: eventually side stage will only be for manta.but not for mako ? [16:23] kgunn: I'll ask the guys if it's possible and feasible from the CI side [16:23] sil2100: thanks...it makes sense that's a nice config capability...and prevents throwing baby out with bathwater [16:23] Kaleo: we're going to need that keyboard/mouse detection for Unity 8's desktop convergence too, do we have a timeframe specified for it's implementation? [16:23] kalikiana_: agreed [16:23] kalikiana_: btw, whether or not I set LD_LIBRARY_PATH to lib/ makes no difference -- it works/doesn't work either way [16:24] kalikiana_: so it looks like the relevant parts are already linked into the plugin, and the lib itself can go away; I think that's what tvoss did, so the .deb might look different in comparison [16:24] kalikiana_: how do you usually manually test new versions? install it on the device and run something? [16:24] (what's that something) [16:25] kgunn: the other things I wanted to poke about are some release-critical bugs that need fixing/reviewing: [16:26] kgunn: bugs #1253810 and #1258655 - could you prioritize them in the meantime? We would be happy release-wise then ;) [16:26] bug 1258655 in Unity 8 "Abort when blanking/unblanking screen" [High,Triaged] https://launchpad.net/bugs/1258655 [16:26] bug 1253810 in unity8 (Ubuntu) "Messages in Incoming not always display the correct date and content" [High,In progress] https://launchpad.net/bugs/1253810 [16:27] kgunn: sorry for poking you about those, but we want to make sure we can release unity8 pretty soon! [16:27] mandel: ping. wondering if you have a few minutes to chat about udm [16:27] barry, I do just before EOD, lets do it! [16:27] barry, looks like system-image is still not landed on an image? [16:28] sil2100: we are landing something asap on 1253810 (the msg one) [16:29] dholbach: oh, trust me i know [16:29] pitti: I test-built the cmake branch and it dropped the .so for the lib so I think that's fine – I test by pressing buttons in the ui toolkit gallery, or any app really [16:29] all standard buttons use feedback out of the box [16:29] sil2100: and on the blanking one 1258655...i'm asking someone on mir team to look at today high priority...however i want to caution...it could end up leading [16:29] to some other component [16:30] possibly worst case....the android hwc is flaky [16:37] davmor2: was out for a run, image #57 please :) [16:37] didrocks: no worries [16:39] kgunn: ouch, ok - but good if you guys have it on your radars [16:41] sil2100: for sure [16:45] didrocks, has the new system updates 2.0 stuff landed yet? [16:45] assuming not [16:47] pmcgowan: I still see it in trusty-proposed, I guess barry knows the detail === jevon is now known as Guest62925 [16:49] oh, i know all about it. the dep 8 tests refuse to complete successfully, for unknown reasons. i.e. the *exactly same tests* succeed locally in-tree, and during package build time (otherwise it would ftbfs). it's just autopkgtests which fail. we're trying to figure it out now :( [16:50] thus the package builds but can't migrate from -proposed [16:51] I see [16:55] kenvandine, cwayne: no, it's not ready to be merged until bug 1245903 is fixed [16:55] bug 1245903 in apparmor-easyprof-ubuntu (Ubuntu) "Online Accounts applications need a couple of more D-Bus interfaces" [Undecided,In progress] https://launchpad.net/bugs/1245903 [16:57] jdstrand: any update on that? ^ [16:59] cwayne: yes, I am working on touch image tests now for apparmor-ubuntu-easyprof and once I have that I will upload the fix for that bug === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss|dinner [17:02] jdstrand: awesome, thanks! [17:03] cwayne, mardy: I worked on that a bit yesterday and it is my top priority atm. I'm sorry that I have been blocking you-- I knew you wanted the fix but I didn't know other stuff was blocked on it [17:03] (I apologized to mardy earlier, but I feel bad) [17:05]