[01:24] <guy> Just got Ubuntu Touch.
[02:05] <CyborgCygnus> So only just discovered the ubuntu tv section on the main website, forgive me if I'm annoying anyone but I seem to find it hard to find more thorough info on ubuntu os's for all devices. Ubuntu TV will that be installable on tv's like smart tv's?
[02:05] <CyborgCygnus> Ignore that^, wrong channel sorry.
[06:00] <lotuspsychje> ogra_: morning
[06:00] <lotuspsychje> did you see meizu ubuntu touch showed off in china?
[06:07] <dholbach> good morning
[07:40] <Kaleo> ogra_, popey, easy way to prevent the screen from locking on the phone?
[07:40] <Kaleo> +do you know an
[07:45] <didrocks> Kaleo: hey! it's quite late for you, isn't it?
[07:48] <Kaleo> didrocks, I'm in Paris until this weekend :)
[07:48] <didrocks> ah, I was afraid for unsane hours for you :)
[07:48] <Kaleo> didrocks, nah :) I gave up on that
[07:53] <pitti> hello all
[07:53] <pitti> I have a question about click apps with compiled code
[07:53] <pitti> e. g. ubuntu-filemanager-app has
[07:53] <pitti>     "architecture": "armhf",
[07:53] <pitti> in its manifest
[07:54] <pitti> that'll build com.ubuntu.filemanager_0.3.212_armhf.click on *any* platform, even if I build it on amd64
[07:54] <pitti> I can change that to ["armhf", "i386", "amd64"], and then it'll build com.ubuntu.filemanager_0.3.212_multi.click which I can install on x86 (tests run fine)
[07:55] <pitti> but that's still wrong, as in both cases the .click contains amd64 code (regardless of whether it's tagged _armhf or _multi)
[07:55] <pitti> but if I don't specify "architecture" at all, it just says _all.click, which is also wrong
[07:55] <pitti> is there an equivalent of "any" which will behave like dpkg, and add the arch you built it on?
[07:55] <pitti> cjwatson: ^
[07:55] <pitti> https://click.readthedocs.org/en/latest/file-format.html#control-area doesn't talk about the details of that
[07:56] <ogra_> Kaleo, unity8-autopilot ships a script ... /usr/share/unity8/unlock-device
[07:56] <Kaleo> ogra_, nice!
[07:56] <Kaleo> so hmm
[07:56] <ogra_> Kaleo, http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh
[07:56] <Kaleo> I can just call it before running autopilot
[07:56] <lotuspsychje> every boot my brightness resets on halfway again on nexus7, you guys got that issue on other devices aswell?
[07:57] <lotuspsychje> would be nice if it sticks 100% brightness
[08:01] <mandel> popey, monring! yes, but we have to land the cmake job that generates them
[08:01] <mandel> popey, Elleo_ created a branch, so it will be landing asap
[08:14] <lotuspsychje> nice fix on the 'save image' on webbrowser, ive been able to set matrix wallpaper on startscreen
[08:14] <lotuspsychje> just the main device background stays white default
[08:15] <lotuspsychje> i hope you guys get your hands on the meizu image soon  to check it out :p
[08:22] <pitti> didrocks, sil2100: I'm currently running the autopilot tests of various click apps with autopkgtest in a container
[08:22] <didrocks> pitti: oh waow, nice! :)
[08:22] <pitti> didrocks, sil2100: for the most part that works fine, but I stumbled over a failure in calendar-app, which fails with ImportError: No module named 'dateutil'
[08:22] <pitti> didrocks, sil2100: indeed python[3]-dateutil isn't installed on the phone (or my container)
[08:23] <pitti> didrocks, sil2100: so hence my question: when we run the autopilot tests, do we actually install the .click, or do we build a .deb and isntall that?
[08:23] <pitti> the calendar-app-autopilot package indeed does have the python-dateutil dep
[08:23] <pitti> (and not python3, argh!)
[08:23] <didrocks> pitti: we install the .click
[08:24] <pitti> didrocks: oh, but supposedly we also install the <app>-autopilot .deb?
[08:24] <didrocks> if it's a click apps installed on the phone, the whole debs world is ignored
[08:24] <didrocks> no
[08:24] <didrocks> sergio is using a script to branch latest trunk
[08:24] <didrocks> and take the autopilot from it
[08:24] <pitti> didrocks: then I don't understand how calendar-app's tests can succeed
[08:24] <didrocks> that sounds weird as well
[08:25] <didrocks> calendar-app is for sure a click app on a vanilla system ?
[08:25] <didrocks> ogra_: do you have your list handy? ^
[08:25] <didrocks> pitti: sometimes, we had click apps, but they were installed as debs on the image
[08:25] <didrocks> (during the transition, this was all puzzling)
[08:25] <pitti> didrocks: hm, not sure; I just picked some random things from https://launchpad.net/ubuntu-phone-coreapps and locally built .clicks from it
[08:25] <ogra_> http://people.canonical.com/~ubuntu-archive/click_packages/click_list
[08:25] <pitti> right, there's calendar
[08:25] <pitti> root@ubuntu-phablet:~# dpkg -l *calend*
[08:25] <pitti> dpkg-query: no packages found matching *calend*
[08:25] <popey> phablet-click-test-setup --click com.ubuntu.calendar
[08:26] <popey> ^^ thats what sets up autopilot
[08:26] <didrocks> pitti: the thing is that autopilot and other things are installed first
[08:26] <didrocks> so maybe something is pulling it in first ?
[08:26] <popey> not installed, copied to ~/home/phablet/autopilot
[08:26] <ogra_> https://wiki.ubuntu.com/Touch/Testing
[08:26] <pitti> right, autopkgtest is doing something similar now (if the filesystem is r/o, it installs the test depends into /tmp/... and sets all the $*PATH envs
[08:27] <popey> run that command and you'll see (for example) python_dateutil-2.0.egg-info in /home/phablet/autopilot/
[08:27] <popey> i.e. we don't use debs
[08:28] <pitti> python_packages = (
[08:28] <pitti>     'python-mock', 'python-dateutil', 'python3-dateutil'
[08:28] <pitti> )
[08:28] <pitti> ooh
[08:28] <pitti> yay hardcoding
[08:28] <pitti> so this should definitively become a test dependency in calendar-app's manifest then
[08:28] <pitti> but at least that explains how it can currently work in production :)
[08:28] <pitti> popey: thanks for pointing out
[08:28] <popey> np
[08:30] <didrocks> so, installed from pypi
[08:31] <pitti> didrocks: right, but the point is, it's currently an externally hardcoded test dependency; that's what I wanted to know
[08:31] <pitti> cf. balloons's u-phone@ discussion, we want to move these test depends into the click's manifest
[08:31] <pitti> similar to dep-8
[08:31] <didrocks> yeah, and so, it's duplicated between the .deb and the python_packages list
[08:32] <didrocks> yeah, one place to rule them all, or DRY ;)
[08:32] <pitti> didrocks: well, the -autopilot debs will go away (hopefully), right?
[08:32] <didrocks> not only the -autopilot, but the whole deb as well
[08:32] <didrocks> the day we can have .click built from source
[08:38] <pitti> didrocks: how do you mean? I currently build them directly from the lp checkout
[08:38] <pitti> ah well, build deps
[08:38] <pitti> they seem to be pretty much constant for arch:all clicks, but of course not for the compiled ones
[08:38] <didrocks> yeah
[08:38] <didrocks> I mean for compiled ones
[08:39] <pitti> click building indeed feels fairly incomplete still
[08:41] <pitti> RuntimeError: Application Launch Failed: Application crashed.
[08:41] <pitti> w00t
[08:41] <pitti> I'll leave that to running on an actual phone then :)
[08:42] <pitti> but 3/4 success is quite nice for running locally with a very fast turnaround
[09:16] <JamesTait> Good morning all; happy Chocolate Pudding Day! :-D
[09:20] <sveta> aha.
[09:58] <AskUbuntu> Ubuntu for Android on HP Slate 21? | http://askubuntu.com/q/488368
[10:05] <lotuspsychje> !devices | AskUbuntu
[10:14] <cjwatson> pitti: I suspect "click build" is deficient here and you just have to set the manifest right yourself.  bug would be welcome
[10:14] <pitti> cjwatson: sure, filing one
[10:14] <pitti> cjwatson: thanks; nice timing, was just about to re-ask on the ML :)
[10:23] <pitti> cjwatson: done, bug 1334597
[10:26] <cjwatson> ta
[11:19] <sil2100> oSoMoN: hello! We also noticed that in recent images the number of failing tests for webbrowser-app increased
[11:25] <Jazzcat14736251> Hi folks :)
[11:26] <Jazzcat14736251> I was wondering how best to find out information about getting ssh working (if this is possible)
[11:29] <Jazzcat14736251> I've copied my id_rsa.pub to /home/phablet/.ssh/authorized_keys and adb shell tells me ssh service is running
[11:30] <popey> Jazzcat14736251: does the right user own .ssh and authorized_keys, and have the right permissions?
[11:31] <Jazzcat14736251> I believe the permissions are correct, perhaps not the user
[11:32] <Jazzcat14736251> -rw-------  1 root    root     405 Jun 19 00:35 authorized_keys
[11:33] <popey> nope, thats nto right
[11:33] <popey> should be owned by the user, phablet
[11:33] <oSoMoN> sil2100, let me take a look
[11:33] <sil2100> oSoMoN: brendand tried looking into what's wrong but didn't see anything obvious
[11:33] <Jazzcat14736251> cheers, will fix.
[11:33] <sil2100> But we're having a lot of failures recently
[11:36] <oSoMoN> sil2100, looks like a mix a different types of failures, some of them due to the toolbar not being open correctly (using the UITK emulator), and others where the OSK doesn’t show up
[11:36] <oSoMoN> I don’t think any of those failures are actually on the browser side
[11:38] <Jazzcat14736251> popey, thanks again, I chowned the file and folder, now it is working ^_^
[11:38] <popey> sweet
[12:48] <jdstrand> does the weather app work for anyone else on latest promoted? seems to be broken for a while now
[12:49] <jdstrand> I start it and am told it couldn't load weather data. then, I can't do anything
[12:49] <jdstrand> bottom toolbar is empty, nothing to click, etc
[12:53] <pmcgowan> jdstrand, I have 81 and it works here, and there are no app updates pending
[12:53] <jdstrand> I think I'll delete the data dirs
[12:53] <jdstrand> pmcgowan: thanks
[12:58] <popey> jdstrand: works fine here.
[12:59] <jdstrand> I got it working
[12:59] <jdstrand> but I have a feeling I am going to have a problem again
[12:59] <jdstrand> in the distant past I would set it to a nearby city since the city I live in wasn't listed
[13:00] <jdstrand> more recently, the city I live in starting showing up
[13:00] <jdstrand> so I chose it
[13:00] <jdstrand> today when resetting it up, I looked for my city, but was told no data sources
[13:00] <jdstrand> so I used the nearby city
[13:00] <jdstrand> then for giggle I tried adding my city again
[13:00] <jdstrand> and it worked
[13:01] <jdstrand> my thinking is there may be an intermittent problem with my city
[13:13] <popey> jdstrand: move
[13:13] <popey> fix-committed
[13:13] <jdstrand> heh
[13:25] <cwayne> mardy: ping
[13:25] <mardy> cwayne: hi!
[13:26] <cwayne> mardy: hiya!  so I saw account plugin click hooks are in the image now?!
[13:26] <cwayne> but I also saw that my fitbit plugin is borked :( (even the deb-packaged one in universe)
[13:28] <mardy> cwayne: yes, click hooks are there, but the thing is not really ready yet
[13:28] <cwayne> mardy: so i changed log level to 2 in /etc/signond.conf, and I still can't quite see what's wrong
[13:28] <cwayne> ah
[13:28] <cwayne> well, I'll still need to solve my deb-packaged one being broken anyhow :)
[13:29] <mardy> cwayne: so, what's the symptom?
[13:29] <cwayne> mardy: so it launches the site to authenticate, and when you fill in your info then click accept, everything dies and the account isn't added
[13:30] <cwayne> i tried using a standard qml-plugin (like twitter's) instead of the one I made, but same issue
[13:31] <mardy> cwayne: the logs should help, I think
[13:36] <oSoMoN> didrocks, hey, I have a webbrowser-app MR with minor packaging changes, I’ll need a core-dev to ack them, would you mind doing that when you have a spare moment?
[13:36] <oSoMoN> the MR is: https://code.launchpad.net/~osomon/webbrowser-app/contextual-selection/+merge/223760
[13:36] <didrocks> oSoMoN: sure, looking
[13:38] <cwayne> mardy: let me get some logs, 1 sec
[13:41] <didrocks> oSoMoN: done
[13:41] <oSoMoN> didrocks, thanks! I’ll remove the Replaces stanza
[13:42] <didrocks> oSoMoN: perfect, consider the +1 then (but I can approve if you need that in your process :))
[13:42] <oSoMoN> didrocks, it’s probably better for the sake of the process, although I don’t think it’s mandatory
[13:43] <didrocks> oSoMoN: just tell me once pushed then :)
[13:43] <oSoMoN> didrocks, note that I used Replaces because the package installs the same files, but in a different location, but IIUC Replaces is only when there is a conflict in fully-qualified filenames, right?
[13:44] <cwayne> mardy: just syslog? or would anything else be useful?
[13:44] <didrocks> oSoMoN: yeah, it's only the full path that is taken into account
[13:44] <mardy> cwayne: online-accounts-ui logs might help
[13:44] <didrocks> there is no md5sum magic or whatever :)
[13:44] <oSoMoN> didrocks, pushed
[13:45] <didrocks> oSoMoN: approved
[13:45] <oSoMoN> thanks!
[13:46] <mardy> export OAU_LOGGING_LEVEL=2
[13:46] <mardy> export OAU_DAEMON_TIMEOUT=9000
[13:46] <mardy> online-accounts-ui
[13:46] <mardy> after killing any running instance
[13:46] <mardy> cwayne: ^
[13:48] <didrocks> yw ;)
[13:48] <cwayne> mardy: segfaulted,i tried ubuntu-app-launch online-accounts-ui and nothing showed up
[13:48] <cwayne> huh
[13:48] <cwayne> now it worked
[13:49] <mardy> cwayne: oops! invoke it as "online-accounts-ui --desktop_file_hint=/usr/share/applications/online-accounts-ui.desktop"
[13:50] <cwayne> mardy: hah, but now that i got all the logging stuff setup, adding an account works
[13:50] <mardy> cwayne: see? :-)
[13:50] <cwayne> lol
[13:50] <cwayne> seems weird
[13:50] <cwayne> must be an intermittent issue
[13:52] <cwayne> mardy: segfaults for me
[13:54] <tomheng> rootstock-touch-install run for a while, it report device not found, what that mean ?
[13:54] <cwayne> mardy: so i found that if i hit enter after putting in my password, it works. but if i press the button on the page, it crashes.
[13:55] <mardy> cwayne: you mean a button which is inside the webpage?
[13:57] <cwayne> mardy: yes
[13:57] <mardy> cwayne: might be an oxide bug, but it would be nice to have a stacktrace to confirm
[13:58] <cwayne> mardy: I can't seem to launch online-accounts-ui from cli without it segfaulting :/
[13:58] <mardy> cwayne: with the desktop_file_hint?
[13:58] <mardy> cwayne: and are you killing any previously running instance?
[13:58] <cwayne> yes and yes
[13:58] <cwayne> let me reboot
[14:02] <cwayne> mardy: still segfaults
[14:05] <mardy> cwayne: backtrace?
[14:06] <cwayne> mardy: none, just does this: http://paste.ubuntu.com/7706033/
[14:07] <mardy> cwayne: but does it starts if you launch it from the system settings UI?
[14:08] <cwayne> mardy: yep
[14:08] <mardy> cwayne: and what's the command line used in that case?
[14:08] <cwayne> no idea tbh
[14:08] <mardy> cwayne: maybe some environment variable is missing in the shell (though I wonder, because it's working here)
[14:08] <mardy> cwayne: ps -fe | grep online
[14:09] <cwayne> mardy: nothin, http://paste.ubuntu.com/7706049/
[14:11] <mardy> cwayne: that's just impossible, if online accounts is open there *must* be an online-accounts-ui process running
[14:11] <mardy> cwayne: ah, you are logged in as root!
[14:11] <mardy> (though you still should see the running processes...)
[14:12] <cwayne> mardy: just where I was doing the ps -fe
[14:12] <cwayne> i did a sudo -iu phablet in another shell and am now running /usr/bin/online-accounts-ui --desktop_file_hint=/usr/share/applications/online-accounts-ui.desktop
[14:12] <cwayne> and it's not showing up..
[14:13] <cwayne> mardy: hm, what about this: application-legacy-online-accounts-ui-1403791371914694.log:** (process:3741): WARNING **: Desktop file 'online-accounts-ui' is set to not display, not copying
[14:14] <mardy> cwayne: so, you need to run that, and then open online accounts from the ui; then, you'll start see messages in the console
[14:15] <cwayne> oh i didnt know i needed to do it from UI too
[14:16] <cwayne> mardy: there we go : http://paste.ubuntu.com/7706101/
[14:16] <cwayne> looks like it segfaults, gah
[14:18] <mardy> cwayne: can you please report a but and attach those logs?
[14:18] <mardy> cwayne: do you think you can run it under gdb?
[14:18] <cwayne> i can try
[14:18] <mardy> gdb /usr/bin/online-accounts-ui and then "run --desktop_file_hint=/usr/share/applications/online-accounts-ui.desktop"
[14:18] <cwayne> what do i log it against, u-s-s-o-a?
[14:18] <mardy> cwayne: yes
[14:19] <stgraber> ogra_, barry: heads up, I've updated image-signing.tar.xz on system-image just now, let me know if you see any problem happening as a result of that.
[14:19] <ogra_> stgraber, ok
[14:19] <barry> stgraber: ok
[14:19] <stgraber> we're not yet using the new signing key though, just shipping the new keyring as the old one would have expired on Saturday
[14:19] <barry> hopefully, all the key update logic is as well tested as i think it is ;)
[14:19] <stgraber> the old key expires in a year from now so I'll have time to do some more checks before I switch over to it
[14:20] <stgraber> barry: I sure hope so because we don't exactly have much breathing room if it doesn't ... :)
[14:20] <barry> stgraber: is there a way we can test this now?
[14:20] <stgraber> barry: I think my phone is at least one image behind, so I'm testing it now
[14:21] <barry> stgraber: cool.  i'll try to reflash my device with an older image and do an upgrade
[14:21] <stgraber> barry: so it only downloaded the blacklist, IIRC we're caching the tarballs unless they fail to validate right?
[14:22] <stgraber> barry: so I'd have to set my phone's clock to say a week from now and retry
[14:22] <barry> stgraber: correct
[14:22] <stgraber> Tue Aug 26 14:22:54 UTC 2014
[14:23] <stgraber> let's try that again now :)
[14:23] <cwayne> mardy: alright, so i got the crash after running from gdb, now what? paste the output?
[14:23] <stgraber> barry: we've got a problem...
[14:24] <stgraber> barry: http://paste.ubuntu.com/7706148/
[14:24] <stgraber> barry: a re-run appears to fix it though, so maybe not entirely dramatic
[14:25] <stgraber> barry: the second run, I get (as expected): http://paste.ubuntu.com/7706151/
[14:25] <mardy> cwayne: type "bt"
[14:26] <cwayne> mardy: http://paste.ubuntu.com/7706163/
[14:27] <barry> stgraber: interesting.  i'll have to do some debugging to understand what's going on
[14:28] <barry> stgraber: i think it shouldn't error out the first time
[14:28] <mardy> cwayne: not useful :-(
[14:28] <mardy> cwayne: but please report a bug anyway
[14:28] <barry> stgraber: the trick will be devising a test for this condition
[14:28] <stgraber> barry: well, it shouldn't error out ever, but yeah, I think it got confused because I did a first run with -n, then did the time change and then did it again
[14:28] <cwayne> mardy: done: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1334688
[14:29] <cwayne> im sad it's not a bug in my account-plugin, would probably have been easier to fix :(
[14:29] <barry> stgraber: could you file a bug please?  at least then we'll have a good record of what happened
[14:29] <stgraber> barry: sure
[14:57] <alf__> Elleo: Hi! Are the QML files that ubuntu keyboard uses embedded in the plugin .so file?
[15:00] <Elleo> alf__: no, the main files are installed to /usr/share/maliit/plugins/com/ubuntu/
[15:01] <alf__> Elleo: great, thanks
[15:01] <Elleo> no problem
[15:02] <Elleo> alf__: I don't know if the keyboard position mappings *should* have worked with Mir 0.2, since it also got resized to 1222 in image #88
[15:02] <Elleo> alf__: I mean it *did* work, but I don't know if that was actually depending on something wrong in Mir 0.2 which was fixed in 0.3 for example
[15:03] <alf__> Elleo: That's what I am trying to figure out :)
[15:03] <alf__> Elleo: Is the related calculating happening in Keyboard.qml reportKeyboardVisibleRect ?
[15:04] <alf__> s/calculating/calculation/
[15:04] <Elleo> alf__: yeah, it's basically assuming that it's being positioned on a fullscreen item so it can take its x/y values as being global screen cordinates
[15:05] <Elleo> alf__: which seems nasty, but as far as I could see QML doesn't provide any proper mechanism for translating between window cooridnates and screen coordinates
[15:05] <cwayne> Elleo: hey, any update on that pinyin bug?
[15:06] <Elleo> cwayne: not sure; we passed that along to the SDK team, will just find the bug report tracking it
[15:08] <Elleo> cwayne: https://bugs.launchpad.net/bugs/1324955 <-- looks like they're targetting it for june, so presumably it'll be looked at soon; might want to check with zsombi
[15:09] <cwayne> zsombi: ping, re ^
[15:09] <zsombi> cwayne: I'm affraid we cannot have that in June :( but on the next MS
[15:10] <zsombi> kalikiana: dude, could you actually take care of this bug? ^^
[15:12] <cwayne> zsombi: it's a pretty high priority, critical for chinese images
[15:12] <zsombi> cwayne: I understand that :)
[15:13] <zsombi> cwayne: well, actually you coudl also contribute a fix for the text inputs :)
[15:13] <cwayne> hah
[15:14] <cwayne> so basically http://patcheswelco.me/ ?
[15:14] <zsombi> cwayne: we discussed this with Elleo that the fix should be in teh text inputs (more precisely in InputHandler) and it seems to be a pretty small fix
[15:15] <cwayne> zsombi: so should the bug be also affecting network-manager then?
[15:15] <zsombi> cwayne: the problem is that I have ~3 MRs on teh text inputs pending, and I cannot take it anymore till eo June
[15:15] <cwayne> or whatever draws that snap decision
[15:15] <zsombi> cwayne: why would it?
[15:15] <cwayne> is that not where that text input is?
[15:15] <clevas> Should ubuntu work on a knock off tablet from china?
[15:15] <cwayne> er network-indicator sorry
[15:15] <zsombi> cwayne: this one you mean? https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1324955
[15:16] <cwayne> yeah
[15:16] <zsombi> cwayne: I don't see the connection between those...
[15:20] <cwayne> that was why the bug was logged in the first place. inputting a wifi password with pinyin doesn't work because it's not auto-committed
[15:20] <cwayne> and I thought you were saying it needed to be fixed where the text input is
[15:54] <kalikiana> zsombi: checking
[15:56] <zsombi> kalikiana: it's a pretty straight FW stuff, in InputHandler you need to call Qt.inputMethod's commit when teh text input looses focus
[15:59] <kalikiana> I could be wrong but didn't somebody propose a patch for that some time ago?
[15:59] <kalikiana> it feels familiar
[16:01] <kalikiana> hrm I don't see a branch like that so I guess not
[16:04] <alf__> Elleo: Does maliit_geometry.visibleRect need to be in screen coordinates?
[16:04] <alf__> Elleo: i.e, what code expects it to be in screen coordinates?
[16:09] <Elleo> alf__: I believe those values get reported to Mir; they're what defines the actual area of the screen that receives touch events for the keyboard
[16:10] <Elleo> they go through the UbuntuApplicationApiWrapper class which opens a socket somewhere and sends them off
[16:10] <Elleo> I'm not especially familiar with that code though, as until this bug showed up I hadn't had any reason to go near it before
[16:11] <alf__> Elleo: I see in InputMethod::onVisibleRectChanged() that we are passing the coordinates to the inputMethodHost() (I don't know what that is)
[16:13] <Elleo> that'll be the maliit framework iirc
[16:14] <Elleo> not sure what it needs them for, below that you'll also see they're being reported via the application wrapper though: d->applicationApiWrapper->reportOSKVisible
[16:14] <Elleo> which I believe is what actually sends it off to something responsible for shaping the input area (maliit-framework wouldn't do that)
[16:16] <Elleo> although it might actually
[16:16] <Elleo> yeah, I know nothing about this side of the keyboard really :P
[16:22] <Elleo> yeah, iirc the InputMethodHost ends up going to the maliit framework which then in turn interacts with the QInputContext, etc. it's taking the values so it can inform apps what areas to avoid displaying content in
[16:23] <Elleo> pretty sure its the transmission through applicationApiWrapper which tells Mir(/or something else?) what area to take touch input from
[16:24] <Elleo> but don't take my word as gospel on that, like I say this is a part of the Keyboard I've never had to do anything with before
[16:25] <alf__> Elleo: fair enough, who should I ask about this part of the code?
[16:26] <Elleo> alf__: I'm not sure; the keyboard was somewhat abandoned when I joined the company, I just sort of inherited it
[16:27] <Elleo> alf__: bfiller might have an idea if there's anyone still at Canonical who'd be more familiar with that stuff
[16:27] <Elleo> alf__: otherwise bzr blame can at least tell you who touched it last :/
[16:31] <Elleo> alf__: from the logs it looks like it was mostly Thomas Moenicke and Guenter Schwann who were involved in that stuff, but I don't think either are with us anymore?
[16:32] <Elleo> alf__: so for now I guess I'm your best bet :/
[16:53] <Elleo> alf__: fyi there is a branch going to land working around this in the keyboard (it just looks at the discrepancy between the real screen geometry and the item size), so we have something to unblock the issue for now; I'd guess the main thing to figure out is if it's indicative of something wrong in Mir or not
[16:53] <alf__> Elleo: so short story, the problem is that the "fullScreenItem" is not really fullscreen anymore. The keyboard rectangle it reports is relative to "fullScreenItem". That would be fine for Mir since it expects surface-relative coords for the input region. But somehow absolute coordinates reach mir and this messes up input handling (we ignore the area of 58 at the top of the OSK and therefore can't swipe)
[16:54] <alf__> Elleo: from what I have seen up to now, it doesn't seem to be a problem in Mir. But I will look a bit more tomorrow.
[16:55] <Elleo> alf__: is it possible that Mir 0.2 was expecting absolute coordinates?
[16:55]  * alf__ checks
[16:58] <alf__> Elleo: probably so
[16:58] <Elleo> alf__: I wonder what's translating between the relative coordinates in keyboard and the absolute coordinates then
[16:59] <Elleo> possibly something in the ui session stuff that UbuntuApplicationApiWrapper talks to?
[16:59] <alf__> Elleo: UbuntuApplicationApiWrapper is a bit mysterious... I only see a connection to which we sent data
[17:00] <Elleo> yeah, I have no idea what it's doing, just that it does something...
[17:01] <alf__> Elleo: anyway, I will investigate more tomorrow, thanks!
[17:02] <Elleo> alf__: okay, thanks for helping out with this :)
[18:54] <jgdx> does the background image change depending on the device rotation?
[19:02] <dobey> jgdx: doesn't change here
[19:02] <dobey> jgdx: but on my phone(s) uniy8 doesn't rotate anyway
[19:02] <dobey> or do new images do that now?
[19:02] <jgdx> dobey, which channel? Rotates on #89 here (mako)
[19:03] <dobey> my mako has a totally dead battery right now
[19:03] <dobey> on hammerhead i'm stuck on image $50 because regressions :(
[19:04] <dobey> dash isn't rotating on my mako on #91
[19:05] <jgdx> actually, uss will change the background if you rotate in-app. ha
[19:05] <jgdx> dobey, thanks, you led me to my answer
[19:05] <dobey> doesn't here :)
[19:06] <jgdx> only temporary
[19:06] <dobey> eh i'm flashing it to 99 now
[19:07] <dobey> Tassadar: hi! did you look into the screen blank issue on hammerhead any further? i haven't been able to, myself
[19:07] <Tassadar> I did, but I can't figure out how to fix it
[19:07] <Tassadar> the drivers are shit :P
[19:07] <Tassadar> :/
[19:07] <dobey> :-/
[19:08] <Tassadar> do you know when did it start?
[19:08] <dobey> around image #71
[19:08] <dobey> when the split greeter was added iirc, but i don't know if that's related
[19:08] <dobey> taking the split greeter back out obviously didn't fix it
[19:11] <Kohelet_> so I'm working on a port to xperia z ultra and while building I get
[19:11] <Kohelet_> make: *** No rule to make target `/home/kohelet/freshTogari/out/target/product/togari/obj/STATIC_LIBRARIES/libelf_intermediates/export_includes', needed by `/home/kohelet/freshTogari/out/target/product/togari/obj/RECOVERY_EXECUTABLES/extract_elf_ramdisk_intermediates/import_includes
[19:12] <Kohelet_> from what I understand this is because libelf isn't found, but libelf is on the system and I also have it in my manifest.xml
[19:15] <jgdx> is it possible to easily resize the window of an app in autopilot? I'm sure I've seen a example somwhere. /me investigates.
[19:27] <Kohelet> was able to figure it out...
[19:31] <dobey> Tassadar: any ideas how i can help figure it out?
[19:32] <Tassadar> if you can determine when it started, then we'll know which change broke it
[19:33] <Tassadar> but tasemnice probably already deleted builds around 71 :/
[19:39] <popey> Tassadar: the n5 builds or our builds?
[19:39] <Tassadar> n5
[19:40] <Tassadar> he can't test it with official builds)
[19:40] <popey> ah
[19:40] <popey> i keep an archive of our builds
[19:49] <dobey> Tassadar: it was around that time when it broke :-/
[20:01] <ahayzen> Saviq, ping
[20:09] <mhall119> alex_abreu: when I create a new webapp project, it doesn't actually create a QtCreator project file, just a .desktop and .json file
[20:09] <alex_abreu> mhall119, yes this is a bug, I have a branch that is almost done (but got postponed) that fixes this at the qtc level
[20:10] <alex_abreu> mhall119, I'll try to make it land soonish
[20:30] <Saviq> ahayzen, pong
[20:30] <ahayzen> Saviq, Are you the right person to ask about unity8 bugs?
[20:31] <Saviq> ahayzen, sure, just leave the questions around, I'll reply when around
[20:31] <ahayzen> Saviq, cool :) ... When I have an application open if I do a full swipe from left to right, sometimes, you only see the background behind and not the scope until the swipe is complete?
[20:32] <ahayzen> Saviq, is this a bug/design? if is a bug it is known or do i need to report it?
[20:32] <ahayzen> *it is a bug is it
[20:39] <Saviq> ahayzen, bug #1333261
[20:40] <ahayzen> Saviq, ah cool thanks you guys are already on it :)
[20:40] <Saviq> ahayzen, we probably won't spend time on it (it's caused by Qt 5.3), because we
[20:41] <Saviq> 'll be changing this whole transition
[20:41] <ahayzen> ah i see ... well i'll look forward to the new transition :)
[20:50] <mhall119> alex_abreu: my webapp isn't launching, won't even get to where it writes a log file in ~/.cache/upstart/
[20:50] <mhall119> https://code.launchpad.net/+branch/~mhall119/+junk/bbqpad-app is the code
[20:50] <mhall119> can you help me figure out what I'm doing wrong?
[20:51] <mhall119> I'm using the devel channel image
[20:51] <mhall119> r87
[20:52] <alex_abreu> mhall119, remove the "," at the end of http://bazaar.launchpad.net/~mhall119/+junk/bbqpad-app/view/head:/app.json#L8
[20:52] <alex_abreu> mhall119, add a "-" between session and cookies in http://bazaar.launchpad.net/~mhall119/+junk/bbqpad-app/view/head:/app.desktop#L5
[20:53] <alex_abreu> mhall119, those are know issues w/ fixes landing very soon
[20:56] <mhall119> alex_abreu: those did the trick, thanks!
[20:57] <alex_abreu> mhall119, np
[20:59] <AlbertA> ogra_: can  I get top approval on this one: https://code.launchpad.net/~albaguirre/ubuntu-touch-session/remove-power-off-delay-arg/+merge/224469
[21:48] <Wellark> Saviq: still around?
[21:49] <Wellark> is that suru theme going to land?
[21:49] <Wellark> I have a MP against system-settings I would love to get landed but I don't want to collide with the theme landing silo
[22:37] <compulsive> hi all
[22:41] <popey> hi
[22:41] <compulsive> how's it goin
[22:42] <popey> great
[22:42] <compulsive> cool
[22:43] <compulsive> is ubuntu touch even going to hppen
[22:43] <popey> Hell yeah!
[22:43] <compulsive> I hope
[22:44] <popey>  ☑ That was easy