[00:15] <OrokuSaki> So if my device is running a CAF kernel.. is this a no go?
[00:19] <OrokuSaki> YAY!
[00:19] <OrokuSaki> I have a KERNEL_OBJ directory in my out now
[00:19] <OrokuSaki> That should *help*
[00:19] <OrokuSaki> for like 10 minutes.. lol
[05:25] <lotuspsychje> gallery app and camera crashing on me
[05:25] <lotuspsychje> nexus7 ubuntu-touch devel
[05:25] <lotuspsychje> can you guys fix it?
[05:49] <michiel81> Is this channel purely for android devices/related problems?
[05:54] <RAOF> michiel81: All Ubuntu Touch development; that's the phone, tablet, and converged desktop thingies.
[05:59] <michiel81> So purely Ubuntu Touch? not 14.04?
[06:05] <RAOF> Well, IIUC we're backporting Unity8 to 14.04 as a development preview tester thingy.
[06:32] <michiel81> I'm not that familiar with what's going on.
[06:52] <OrokuSaki> I don't think this is as bad as I thought it would be
[06:52] <OrokuSaki> I guess with CM11 requiring CAF, this is why?
[07:07] <dholbach> good morning
[08:16] <JamesTait> Good morning all; happy Meteor Watch Day! :-D
[08:25] <CRPL> Hello. I have a problem with my Nexus4 - it does not correctly route the audio output to my earpice.
[08:26] <CRPL> In calls, if I push the speaker button I can hear that person on the loudspeaker, but not on the earpice.
[08:27] <CRPL> Any hopes on fixing this ?
[08:27] <JamesTait> That sounds familiar.
[08:27] <CRPL> Yes, I have the same problem on Android, but I use SoundAbout to re-route my audio.
[08:28] <JamesTait> In fact, described like that, it sounds like a possible explanation for what happened to me yesterday - I didn't think to try loudspeaker, though.
[08:28] <CRPL> What component of the Ubuntu Phone does the routing of the audio ?
[08:30] <JamesTait> I'm not sure, tbh, I don't know much about the workings at that level.  I think pulseaudio is involved somewhere in the pipeline.
[08:31] <JamesTait> But that sounds like the problem my wife has with her Nexus 4 - she also has to use SoundAbout to get audio routed correctly, we think because the headset detection switch is faulty.
[08:31] <CRPL> I really want to try to get used to Ubuntu Phone, but without the ... phone function, is not a good choice >D
[08:32] <CRPL> I'm not really sure if it is hardware issue or software issue
[08:32] <CRPL> But it will be nice to override it
[08:33] <JamesTait> Indeed. :)
[08:34] <CRPL> So, nobody here knows where to debug this ? :(
[08:37] <JamesTait> CRPL, this also reminds me of a bug on the phone a while back, which got fixed.
[08:38] <JamesTait> Let me see if I can find that, it might give some pointers.
[08:38] <CRPL> Thank you.
[08:45] <pitti> hello everyone
[08:45] <pitti> is there a programmatic way to unlock the screen on the phone? I'd like to do that in the "setup" script for running click tests, so that one can actually see what's going on
[08:46] <pitti> I didn't see anything in https://wiki.ubuntu.com/Touch/Testing except for "do it manually", but I figure in CI we automatically unlock
[08:48] <pitti> ogra, vila: ^ perhaps you know?
[08:48] <JamesTait> CRPL, I'm almost totally failing, so far.  The only piece of information I've found that *might* be useful as a starting point is this mailing list post describing the 13.10 audio stack: https://lists.launchpad.net/ubuntu-phone/msg03881.html
[08:48] <JamesTait> CRPL, it might be outdated by now, though.  If ogra_ is around, he'll probably have a better idea.
[08:48] <CRPL> For detecting whether a headphone/headset is plugged in or not, PulseAudio now has code for reading that from the Android kernel, through the "switch" interface [1].
[08:49] <CRPL> So I'll have to wait a little.
[08:49] <CRPL> On the other hand, where do I adjust the volume of the ringtone ?
[08:50] <vila> pitti: best best is to try again in #ubuntu-ci-eng when US comes online. There has been *several* attempts to get this right and I've lost track of where it ended up. It's still not at the test level though but part of the device setup prior to the test run.
[08:51] <JamesTait> CRPL, I think just by using the volume buttons from the home screen.
[08:51] <pitti> vila: right, I'm fine wiht it being on the device setup
[08:51]  * vila nods
[08:51] <pitti> vila: I figured out a way to run powerd-cli in the background (surprisingly complicated), now looking into screen unlocking, and then seeing whether aa-clickhook needs to be run
[08:51] <CRPL> JamesTait: nothing happends when I push volume buttons :D
[08:52] <pitti> vila: btw, https://plus.google.com/u/0/107564545827215425270/posts/h3K79htx1i3 :)
[08:52] <vila> pitti: s\o/
[08:52] <pitti> vila: looking into some remaining bits of the ssh runner and a manpage for it, then moving to the nova script (that's just reviewing and integrating, jibel already wrote it)
[08:52] <vila> ack
[08:54] <JamesTait> CRPL, what about the sound indicator?
[08:56] <CRPL> JamesTait: My bad. Was working but I was used to visible pop-ups
[08:57] <JamesTait> CRPL, I thought we had one at one stage, seems to have disappeared again.
[09:01] <pitti> vila: there's no magic command in the CI airline for that then? I went through phablet-config again, and there's nothing
[09:01] <mpt> Where should I report bugs about the startup screen? I don’t see a relevant component listed at <https://wiki.ubuntu.com/Avengers>.
[09:02] <vila> pitti: I don't think there is *a* magical command, rather, I think it's part of ... phablet-test-run (can't remember the exact name), I've not even sure there is an explicit option for it
[09:02] <popey> mpt: ubuntu-system-settings-wizard
[09:03] <popey> mpt: feel free to add it to the page ☻
[09:03] <mpt> popey, the one with the spinning logo and the progress bar?
[09:03] <mpt> I thought that had only just landed, whereas this screen has been around for weeks
[09:03] <popey> oh, i thought you meant the first run wizard
[09:03] <pitti> vila: I don't see it there either
[09:03] <popey> mpt: i dont know, ricmm will know
[09:04] <vila> pitti: :-/
[09:04] <pitti> vila: unless we run the tests with -n to completely disable the shell (unity8)
[09:04] <pitti> vila: I suppose stopping unity8 would stop the lock screen, but running app tests without unity8 seems a bit unrealistic to me
[09:05] <CRPL> JamesTait: How can I edit a .conf file in the FileManager ?
[09:05] <CRPL> or open a file with text editor
[09:06] <vila> pitti: yeah, seems a bit extreme ;)
[09:06] <JamesTait> CRPL, I don't know if you can via the GUI, currently.  I've always just used the terminal.
[09:07] <CRPL> Is there a shortcut to ~tab~ for long filenames ?
[09:08] <mpt> popey, actually that screen appears only after a system image update … It should appear, but doesn’t, on every startup. So maybe it’s part of system-image and shouldn’t be
[09:08] <popey> CRPL: in terminal, yes, tap the screen
[09:08] <CRPL> Thank you.
[09:12] <vila> pitti: from psivaa : http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh holds the info
 unity8-autopilot has that util
[09:12] <CRPL> seems like I can't edit directly the /usr/share/alsa/ucm/apq8064-tabla-snd-card/VoiceCall file
[09:13] <pitti> vila: ah, /usr/share/unity8/unlock-device -- thanks for pointing out!
[09:16] <CRPL> JamesTait: is there any way this could be my bug : https://bugs.launchpad.net/ubuntu/+source/android/+bug/1276901
[09:16] <CRPL> I don't understand the term ~hammerhead ootb~
[09:18] <CRPL> I don't think so; that bug affected all the sound
[09:18] <CRPL> So, how can I edit /usr/share/alsa/ucm/apq8064-tabla-snd-card/VoiceCall ?
[09:19] <Tassadar> CRPL: hammerhead is boardname of Nexus 5
[09:19] <JamesTait> CRPL, hammerhead is Nexus 5.  OOTB is Out Of The Box, i.e. unmodified, stock hardware/software.
[09:19] <CRPL> Oh, that makes sense :D
[09:19] <vila> pitti: routing thanks to psivaa ;)
[09:19] <pitti> psivaa: cheers!
[09:21] <JamesTait> CRPL, I don't think you'll be able to edit that file under normal circumstances - I think it resides in the read-only part of the system image.
[09:22] <CRPL> Yes, that's the error (read only fs). That file contains the conflict between Earpiece / Speaker / Headset
[09:25] <psivaa> pitti: vila: np :)
[09:28] <JamesTait> CRPL, what version are you running?  I just verified with my Nexus4 running devel r87 that I do get in-call audio through both earpiece and loudspeaker (so it must have beenmy wife's phone having problems yesterday).
[09:30] <CRPL> One hell of a buggy one :)) ... I installed it today
[09:30] <CRPL> so I think is the .... last version
[09:32] <CRPL> The stable version has all the features available ? (especially 3g)
[09:33] <JamesTait> CRPL, if you open up system settings, at the bottom of the first pane it says "About this phone" - click that, andabout 2/3 of the way down it'll say "OS: Ubuntu XX.YY (rZZ)"
[09:34] <CRPL> Wait a second to .... debug / restart ... it was frozen
[09:34] <JamesTait> Meanwhile, I need tea. :)
[09:35] <CRPL> Ubuntu 14.10
[09:36] <popey> CRPL: i think he means the rZZ bit
[09:38] <CRPL> r87
[09:40] <mpt> Is it just me, or does Ubuntu Touch have no startup screen, except on the first boot when it’s updated?
[09:41] <CRPL> mpt: I didn't see that either ... I forced-shutdown my phone several times because I thought it was off
[09:42] <popey> mpt: whats your definition of startup screen?
[09:43] <mpt> popey, the screen appears between the time that the phone is completely off, and the time that the welcome screen appears.
[09:43] <popey> mpt: just rebooted my phone and got.. rumble, google logo, slowly rotating ubuntu logo, h
[09:44] <popey> s/h/welcome screen/
[09:44] <mpt> I got the Google logo, but not the rotating Ubuntu logo
[09:44] <mpt> odd
[09:44] <popey> what version you running?
[09:44] <popey> r104 here
[09:46] <mpt> popey, r87 … Nothing more recent show up in updates
[09:46] <CRPL> mpt: I have r87 and no startup screen either
[09:46] <mpt> (that! shows! I can’t type this morning)
[09:49] <popey> mpt: ok, cool, wait for the next promoted image then
[09:50] <mpt> ok
[09:51] <sergiusens> pitti: hmmm, wrt to disabling shell; I got a general request from elopio to look into that for running app tests; you guys might want to sync up
[09:52] <pitti> sergiusens: why do we want to disable the shell for running app tests? don't some things even interact with it and check notifications and the like?
[09:52] <sergiusens> pitti: for unlocking; there's a python script and some unity8 autopilot 'emulators' that do the unlocking after you enable introspection on it
[09:53] <pitti> sergiusens: FWIW, it seems we don't run with -n (disable shell) in production, but something calls /usr/share/unity8/unlock-device instead
[09:53] <sergiusens> pitti: I am not claiming I want it done; just saying elopio was considering it as an option :-)
[09:53] <pitti> sergiusens: right, psivaa/vila pointed that out now
[09:53] <pitti> sergiusens: ah, good to know, thanks
[09:54] <popey> mpt: also, the colour of the new startup rotating logo differs from the colour of the logo you just filed a bug about#
[09:54] <mpt> Looks like I picked the wrong day to report bugs
[09:55] <popey> mpt: might be my eyes.. http://imgur.com/HRbQEcm  <- thats the slow spinning boot up animation
[09:57] <mpt> Aw, I was hoping it would be chartreuse
[09:58]  * popey googles chartreuse
[09:58] <CRPL> also in this build, you cannot set 2 alarms
[09:59] <CRPL> at least on my phone
[09:59] <CRPL> popey: the stable version offers full functionality ?
[10:00] <popey> i cant answer that question.
[10:00] <popey> stable is old, devel is recent, proposed is bleeding edge
[10:00] <popey> you are on devel
[10:01] <popey> proposed fixes (and breaks) things in devel & stable
[10:01] <popey> but only if we know about them, can you reproduce the alarm bug?
[10:01] <CRPL> Yes. I setup an alarm for 6:45 am, and I wanted to setup another to test it
[10:02] <CRPL> And the second one dosen't get pinned
[10:02] <pitti> mvo: when I run "apt-get update" on a freshly installed phone, I get messages like
[10:02] <pitti> W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/utopic/main/source/Sources  404  Not Found [IP: 91.189.88.140 80]
[10:02] <CRPL> or applyed
[10:02] <pitti> mvo: indeed these don't exist, only *.bz or *.bz2; but I don't see anything obviously wrong in  /etc/apt/sources.list
[10:02] <pitti> mvo: is that just an artifact of a read-only file system, or some weird bug?
[10:03] <mvo> pitti: give me a sec to look into this
[10:03] <CRPL> popey: were you able to replicate that ?
[10:04] <pitti> mvo: not urgent, I just asked in case you know
[10:04] <mvo> pitti: it could be that apt does not find a decompressor binary and therefore wants to download the uncompressed version, but that seems dubious
[10:05] <popey> CRPL: trying
[10:05] <popey> CRPL: is it a repeating alarm? can you be more specific about what you did?
[10:05] <CRPL> popey: first one is repeating
[10:05] <CRPL> second one ... any alarm
[10:06] <CRPL> popey: it worked now
[10:07] <popey> works here
[10:08] <CRPL> but I noticed that when I touched the + sign, my screen goes blank for a fraction of a second, and nothing happends .. and only after touching + sign again it opened the alarm add function
[10:08] <CRPL> and "please select alarm time in the future" also appeared ..
[10:09] <CRPL> What if I want to add an alarm for next monday at 1:00 pm
[10:09] <popey> known issue
[10:10] <CRPL> And ... how do I delete the alarm I set 2 minutes ago ? >D
[10:10] <CRPL> oh
[10:10] <CRPL> swipe it
[10:11] <CRPL> And it will be also good to disable auto-capitalisation on first letter with some apps like terminal
[10:16] <CRPL> Does Ubuntu Phone have email (gmail) integration ? (notifications on new mail arrival)
[10:23] <JamesTait> CRPL, not to my knowledge atm.
[10:23] <popey> CRPL: terminal bug is also known
[10:24] <CRPL> At least I have the earpiece - original bug, not duplicated :))
[10:25] <JamesTait> CRPL, on the face of it, your sound issue sounds like a hardware one to me - r87 is working ootb for most [citation needed] people.
[10:25] <JamesTait> CRPL, can you share the bug number?
[10:26] <CRPL> I didn't report it officialy yet ... waiting to confirm it
[10:26] <CRPL> Is a known bug in Android OEM
[10:26] <JamesTait> Aha!
[10:31] <CRPL> JamesTait: how can I temporary restore my backup.ab ?
[10:32] <CRPL> adb restore backup.ab
[10:32] <CRPL> ?
[10:34] <CRPL> Now unlock your device and confirm the restore operation.
[10:34] <JamesTait> CRPL, blimey, now you're testing me. :)  I think that's right, yes, but I haven't done it for so long I can't be sure.
[10:34] <CRPL> Now unlock your device and confirm the restore operation. - but nothing on the phone
[10:34] <JamesTait> That sounds right.
[10:35] <CRPL> no prompt on phone
[10:35] <JamesTait> Except, I'm not sure how you confirm the operation if you're running Ubuntu - exactly.
[10:35] <CRPL> google is my friend ... :D
[10:36] <JamesTait> Maybe the phone needs to be in recovery mode?
[10:37] <CRPL> no adb in recovery mode
[10:37] <CRPL> i think
[10:38] <CRPL> I think that I need to flash stock and then adb restore
[12:08] <njin> hi fellows, I can't understand why at fast oem unlock phone instead to display request  to acceptance of terms get locked with =>FASTBOOT mode... written, is it normal ?
[12:11] <njin> also terminal still without in working mode (blinking cursor
[12:19] <mandel> Elleo, do you want to take lp:~mandel/ubuntu-download-manager/expose-logger for a spin and let me know if it makes any sense?
[12:20] <mandel> Elleo, you have a Logger object with an init method that allows you to set the log level to be used by the client lib of the download manager and pass also the file where the logs will be written
[12:20] <mandel> Elleo, thread safe ofcourse
[12:22] <Elleo> mandel: okay, will give it a look as soon as I've finished with another issue
[12:22] <mandel> Elleo, great, ideally this will give you a hand for debugging purposes with the downloads
[12:22] <Elleo> mandel: yeah, thanks
[12:34] <njin> retried, at 'adb reboot bootloader, phone still with the '=>FASTBOOT mode..' written in the lower corner instead to show the green Android robot, any hint ?
[12:35] <davmor2> njin: what are you trying to do?
[12:36] <njin> davmor2 thanks, i am following the guide to install utouch
[12:37] <njin> unlocking android device step
[12:37] <davmor2> njin: do adb reboot bootloader then do sudo fastboot oem unlock
[12:37] <davmor2> njin: you need the sudo bit in there for fastboot
[12:38] <njin> how can i set up the sudo bit ?
[12:38] <davmor2> njin: you just type sudo fastboot oem unlock in the terminal
[12:39] <davmor2> njin: are you trying to do this from an Ubuntu machine?
[12:40] <njin> yup, I have already done it but all still locked, terminal with blinking cursor and phone with that written, yup from utopic
[12:40] <njin> I arrived to a time of 939 seconds
[12:41] <njin> then decided to hard reboot
[12:41] <njin> phone is a clone of xperia
[12:41] <njin> davmor2:^^
[12:42] <davmor2> njin: I don't know if Ubuntu touch is available for it.  However the oem unlock should work the same way across the board.
[12:43] <njin> all the steps of the guide are good till this one..
[12:45] <njin> davmor2: no buttons working, only power off, anyway thaks for the help
[12:48] <njin> at fastboot devices it reply: mt6572v1_phone	fastboot
[12:52] <davmor2> njin: so fastboot is working. So now if you Type sudo fastboot oem unlock what happens now?
[12:55] <njin> davmor2: nothing, cursor still blinking and phone stay as the same with that written in the corner,
[12:56] <njin> davmor2: previous attempt ( I hard reboot the phone after many time) was ... [sudo] password for njin:
[12:56] <njin> ...
[12:56] <njin> FAILED (status read failed (No such device))
[12:56] <njin> finished. total time: 962.568s
[12:58] <davmor2> njin: Are you sure the device is actually locked?
[12:58] <njin> nope..., it is a new cheap phone
[12:59] <njin> can be it is already unlocked ?
[12:59] <davmor2> njin: when you boot into android is there an unlocked padlock on the screen at all?
[13:01] <njin> davemor2: nope, when I boot android it appear the usual locked padlock
[13:04] <ogra_> then it is not unlocked
[13:05] <davmor2> njin: it might be that you have to go into a special mode to unlock it.  Have a look online and see if there is any different ways to unlock it
[13:06] <njin> davmor2, thnaks, i will search then.
[13:06] <njin> Thanks for the support
[13:06] <ogra_> which nexus device is that ?
[13:06] <njin> it is a cubot9+ (chinese clone of experia...)
[13:06] <njin> c9+
[13:07] <ogra_> well, then the instructions will not work at all for yu
[13:07] <njin> agra_ ok, I will google, any hint from you '
[13:07] <njin> ?
[13:07] <ogra_> "fastboot oem unlock" is a google invented command that only works on nexus devices
[13:08] <njin> ogra_: thanks
[13:08] <ogra_> well, "unlock cubot9+ bootloader"
[13:08] <ogra_> or "rooting cubot9+ phone" or some such
[13:09] <ogra_> (but even if you unlock, are you sure there is even an ubuntu touch image for that device that works ?)
[13:09] <njin> ogra_: it is not the best but i can unlock it with root genius 8win tool)
[13:09] <njin> ogra_: If it go bad no matter...
[13:11] <davmor2> njin: You don't understand if you won't be able to install the default image using our tools as you phone is not compatible you would need to follow the porting guide to get it installed
[13:11] <njin> agra_, davmor2. i go to unlock it on win and come back...thanks to both
[13:13] <njin> davmor2, thanks i will ensure before...
[13:42] <mhall119> popey: is there a known problem with the gallery in devel images?
[13:42] <popey> mhall119: can you be more specific?
[13:44] <mhall119> it won't load
[13:44] <mhall119> crashes on startup
[13:45] <popey> i dont have a device running devel right now, asking around
[13:46] <mhall119> popey: hmm, logs say something about not being able to read image file formats
[13:47] <ogra_> mhall119, works fine on #87 for me
[13:48] <ogra_> (which is the latest devel image)
[13:48] <sil2100> davmor2: ^
[13:48] <mhall119> also some actionmanager errors, shm errors, and binding loop errors
[13:49] <ogra_> oh
[13:49] <ogra_> wait, i run the originally shipped gallery app here
[13:49] <davmor2> sil2100: I'm on proposed works fine here
[13:49]  * ogra_ updates ... lets see if it still works then
[13:51] <ogra_> mhall119, confirmed ... the update breaks it
[13:51] <ogra_> popey, sil2100 ^^
[13:53] <davmor2> ogra_, mhall119, sil2100: D'oh it's because it had specific fixes for Qt5.3 I bet they are not compatible with Qt5.2.1
[13:54] <ogra_> davmor2, yes
[13:54] <popey> #87 is still 5.2.1!?
[13:54] <ogra_> it should have bumped the framework version
[13:54] <popey> we haven't promoted a 5.3 image yet?
[13:54] <mhall119> I think so
[13:54] <davmor2> popey: nope because we had the fall out
[13:55] <popey> unfortunate
[13:55] <popey> camera app got a framework bump, gallery didn't
[13:55] <ogra_> the last promoted image doesnt have -dev2 ....
[13:55] <mhall119> how did this pass testing?
[13:55] <popey> mhall119: it wasn't tested on a devel phone
[13:55] <ogra_> mhall119, by testing against -proposed
[13:55] <ogra_> we need to include that in the future ...
[13:55] <mhall119> Yeah
[13:57] <mhall119> ogra_: can I revert to the image's preinstalled version?
[13:57] <sil2100> popey: no 5.3 image yet ;/ That's why I said on Friday that the no-promotion state stresses me out
[13:57] <popey> mhall119: yes...
[13:57] <sil2100> I hope we'll have a promotion today I guess
[13:57] <mhall119> How?
[13:57] <popey> mhall119: one mo
[13:57] <mhall119> Thanks
[13:58] <popey> mhall119: http://popey.mooo.com/mirror/clicks/2014-06-23-100001/com.ubuntu.gallery_2.9.1.1001_armhf.click
[13:58] <popey> mhall119: http://popey.mooo.com/mirror/clicks/2014-06-12-100002/com.ubuntu.gallery_2.9.1.996_armhf.click
[13:58] <popey> grab either of those older ones
[13:59] <mhall119> popey: ok, I'll need to get my laptop out for this...
[13:59] <popey> you can wget in terminal
[14:00] <popey> http://bit.ly/1rPAcTK
[14:00] <popey> thats a nice short url for it
[14:00] <mhall119> I'm on the phone terminal atm
[14:00] <popey> yes
[14:00] <popey> thats what mean ☻
[14:00] <popey> wget http://bit.ly/1rPAcTK
[14:00] <popey> pkcon install-local com.ubuntu.gallery_2.9.1.996_armhf.click
[14:01] <popey> 996 is the one that shipped in the image you have
[14:01] <mhall119> i am ssh'd to my home server for irssi
[14:02] <ogra_> file a whishlist bug for tab support !
[14:02] <popey> get a pen, write down the url, disconnect from irc... etc
[14:03] <mhall119> what's a "pen"?
[14:03] <popey> legacy laptop
[14:12] <mhall119> popey: got it fixed, didn't even need to download anything
[14:12] <mhall119> just click register the old version
[14:13] <popey> ahh of course
[14:13] <popey> neato
[14:14] <mhall119> what's this PayUI in the store?
[14:16] <cwayne> mterry: heya, for the life of me i can't get lightdm to pull a conf from /custom, it should be as easy as having a system upstart job that sets XDG_DATA_DIRS, right?
[14:16] <mterry> cwayne, yeah...  should be.  Let me see your system job
[14:18] <cwayne> mterry: http://paste.ubuntu.com/7726655/
[14:20] <mterry> cwayne, OK, so one problem is that you are using export instead of initctl set-env --global
[14:21] <cwayne> mterry: i tried that as well, and i got an error
[14:21] <cwayne> let me find it
[14:21] <cwayne> mterry: initctl: Not permissible to modify PID 1 job environment
[14:21] <mterry> cwayne, for testing, you might want to edit /etc/init/lightdm.conf and add an echo for XDG_DATA_DIRS
[14:21] <mterry> cwayne, oh interesting, is that only allowed in user sessions?  huh
[14:22] <mterry> yup, it is
[14:22] <ogra_> yeah
[14:24] <mterry> cwayne, so two options: either the lightdm job needs to set XDG_DATA_DIRS for itself, or you need to change the environment of init in the first place
[14:25] <mhall119> mandel: how are we coming on the u-d-m docs?
[14:26] <mandel> mhall119, we have 4 branches for review for them, once they are landed you get a doc package :)
[14:26] <ogra_> mterry, cant lightdm (or a wrapper) just call "initctl start custom-env" ?
[14:26] <ogra_> iirc you are running a special cased user session for it, no ?
[14:26] <ogra_> oh, wait, that was split greeter ... ignore me
[14:26] <asac> how are scopes started nowadays?
[14:27] <asac> is that unity starting those processes?
[14:27] <asac> thostr_: Saviq: ^
[14:27] <Saviq> asac, the scope registry is spawning them
[14:27] <asac> interesting name for something that spawns something :
[14:27] <asac> )
[14:27] <Saviq> asac, so make sure to have smart-scopes-proxy and scope-registry started, if you're missing scopes
[14:28] <asac> Saviq: i am not missing scopes .. i am missing a way to install a scope that i have in a click and start that to try it
[14:28] <Saviq> asac, it's not just spawning them
[14:28] <asac> and stop it
[14:28] <Saviq> asac, there's ways to do that
[14:28] <Saviq> mhr3, can you guide asac ↑?
[14:28] <ogra_> just like any other click, no ?
[14:29] <asac> Saviq: i dont need the details right now. just on high level
[14:29] <asac> 1. install click with scope
[14:29] <mterry> ogra_, but that wouldn't affect the env of lightdm if the lightdm job started custom-env, eh?
[14:29] <asac> 2. run XXXX with arguments YYYY
[14:29] <Saviq> asac, 2. you should be done
[14:29] <asac> 3. see scope
[14:29]  * cwayne can verify that click-installed scopes work
[14:29] <asac> 4. kill or restart scope
[14:29] <Saviq> asac, is that on your desktop or phone?
[14:29] <asac> Saviq: phone
[14:29] <zbenjamin> Saviq: you can tell the scope registry to start and bring a scope to the front?
[14:29] <ogra_> mterry, well, it wouldnt be able to start it anyway ... that was a thinko ... custom-env is a user session job
[14:29] <Saviq> zbenjamin, you can go to the scopes scope and look for it
[14:30] <cwayne> mterry: so could i just do a upstart override, or should I just do an MP to lightdm to set that?
[14:30] <mterry> ogra_, well we wanted to create a system version of it, yeah.  Because we'd like lightdm to see the custom XDG_DATA_DIRS
[14:30] <Saviq> asac, what doesn't happen now afaict is that scope-registry does not pick up the newly installed scope unless it's restarted
[14:30] <Saviq> zbenjamin, ↑
[14:30] <zbenjamin> Saviq: yeah thats the last state i knew about too, but we actually need a way to tell the registry to bring the scope to the front when i press the "Run" button in the IDE
[14:30] <mterry> cwayne, I dunno.  How "official" is /custom?
[14:30] <Saviq> zbenjamin, then not the registry but the shell
[14:30] <zbenjamin> Saviq: ok that would be required too ;)
[14:31] <cwayne> mterry: it's our officially supported method of customization
[14:31] <cwayne> so, very?
[14:31] <Saviq> zbenjamin, I think the right way there would be for the shell to handle scope:/// urls, which we use internally anyway
[14:31] <Saviq> zbenjamin, and then you'd open that URL via url dispatcher
[14:31] <asac> Saviq: so right now one needs to restart the shelll after installing the click?
[14:31] <ogra_> asac, you shouldnt need to
[14:31] <Saviq> asac, not the shell but scope-registry
[14:31] <asac> Saviq: how do i do that?
[14:31]  * ogra_ installed the soundcloud scope yesterday 
[14:32] <ogra_> didnt have to restart
[14:32] <asac> really?
[14:32] <mterry> cwayne, (for touch yeah, but what about Desktop / other flavors which all share lightdm?)  regardless, it still feels "hacky" to have one-off each system job we want to see it.  it sounds like this is the first time this has come up though, so maybe we don't have to do it very often
[14:32] <asac> ogra_: it just showed up?
[14:32] <asac> maybe unity crashed for you?
[14:32] <asac> :)
[14:32] <mhr3> asac, you don't need to restart anything, installing a scope from the apps store is all that's needed
[14:32] <ogra_> you have to search for it
[14:32] <mhr3> asac, it will then show up in the scopes scope
[14:32] <asac> mhr3: how aobut installing it from the click cli
[14:32] <asac> does that work too without restart?
[14:32] <ogra_> asac, thats what i did
[14:32] <mhr3> asac, same
[14:32] <mhr3> asac, yes
[14:32] <mterry> cwayne, I'm leaning toward an override for now, and we can see if that's sufficient or if we'll eventually need to set it in a more general way
[14:33] <asac> zbenjamin: and we need something else?
[14:33] <ogra_> search for "soundcloud" in the store ... install it ... search for it on the scopes scope
[14:33] <asac> zbenjamin: forcing it to be the one shown at front?
[14:33] <asac> mhr3: so someone is listing for changes to files somewhere and if there is a change restarts the regsitry?
[14:33] <zbenjamin> asac: yes,  as a developer i want to see my app/scope when i press run
[14:33] <asac> mhr3: same for removing and updating a scope click?
[14:34] <mhr3> asac, the registry is watching itself
[14:34] <asac> zbenjamin: ack, thats the equiv of "to-front" i guess
[14:34] <asac> mhr3: nice
[14:34] <zbenjamin> asac: yes
[14:34] <asac> mhr3: any trick scope X to the front through a cli?
[14:34] <cwayne> mterry: well we could have it check for the existence of /custom first before it's set.. but most everything else is take care of with the session job that does that
[14:35] <mhr3> asac, ehm?
[14:35] <asac> mhr3: i have installed scope X
[14:35] <asac> mhr3: now i want to see it on my screen without having to touch the screen
[14:35] <asac> mhr3: so basically unity-cli --show-scope X
[14:35] <asac> :)
[14:35] <mhr3> asac, nope, you do have to touch it
[14:36] <asac> mhr3: who would have to implement such a feature if we wanted that?
[14:36] <mhr3> asac, just simulate the touches?
[14:36] <asac> or maybe after installing/updating a scope we want to always go to that scope?
[14:36] <asac> mhr3: nah. please not. that doesnt sound right :)
[14:37] <mhr3> neither does implementing test-only features :P
[14:37] <asac> any other ideas?
[14:37] <asac> its not test only
[14:37] <asac> well
[14:37] <mhr3> it is
[14:37] <asac> yes, but its an essential feature
[14:37] <mhr3> you wouldn't want to open that up to confined apps
[14:37] <asac> for a large user group we are targetting
[14:38] <asac> make dveloping scopes and running them easy and convenient
[14:38] <asac> yes, you only want to allow that to happen from adb
[14:38] <mhr3> that's what the sdk integration with unity-scope-tool is for
[14:38] <asac> through adb
[14:38] <asac> mhr3: thats a tool on the host or on the target?
[14:38] <mhr3> host
[14:42] <asac> mhr3: that thing seems to be something different
[14:42] <asac> mhr3: like a complete test environment running on your host
[14:43] <mhr3> yes, that's how you develop a scope
[14:43] <asac> mhr3: is the idea we ship that as well on the phone so you can get a test environment to iterate on your scopes?
[14:43] <mhr3> no
[14:44] <asac> so whats our story to iterate and test your scope on the phone? is that a non-story?
[14:44] <asac> meaning: explicitely decided that devs only iterate on desktop?
[14:44] <mhr3> pretty much, you click deploy and that installs the scope on the phone, then it's up to you
[14:45] <asac> mhr3: who owns the story how we develop scopes?
[14:45] <asac> from high level i mean
[14:45] <asac> thostr? bzoltan?
[14:45] <mhr3> thostr_
[14:46] <asac> ok thanks
[14:47] <thostr_> asac: I only own parts of the story
[14:47] <asac> zbenjamin: do we have other SDK main user stories that have no device/emulator story similar to scope?
[14:47] <thostr_> asac: we already had a longer discussion with Pat about hte dev story, VP is following that up
[14:47] <asac> thostr_: fwiw, i sensed that
[14:48] <zbenjamin> asac: the helpers
[14:48] <asac> helpers?
[14:48] <asac> zbenjamin: whats helpers?
[14:48] <zbenjamin> asac: they are small helper applications that give the app a way to have background tasks, like push helper for example
[14:48] <asac> thostr_: yeah, me being here is kid of part of that thread
[14:48] <asac> kind
[14:48] <zbenjamin> asac: thats pretty much all i know, other than that they are almost not debuggable/startable because they are triggered by the system
[14:49] <asac> thostr_: lets move that discussion for later/elsewhere
[14:49] <thostr_> asac: yes
[14:49] <asac> zbenjamin: ok, but i doubt we have no real "integarted dev story for those at tall?
[14:49] <zbenjamin> asac: no we are still ironing out how we want to integrate them into the process
[14:49] <zbenjamin> asac: means there is zero support yet
[15:09] <michiel81> Anyone here familiar with installing touch controllers in 14.04 LTS?
[15:13] <bregma> michiel81, what sort of touch controllers?
[15:13] <michiel81> USB - resistive
[15:13] <michiel81> Hid/vid 1bfd:3050
[15:14] <michiel81> lsusb shows 'touchpack'
[15:14] <bregma> michiel81, is this a new device (as in, may not have in-kernel device drivers)?
[15:14] <michiel81> but it seems to be recognised as a 'tablet input' so i tried adding it to hidusb
[15:15] <michiel81> well i got it to 'register input' but i can't get it to calibrate
[15:15] <bregma> are you talking to it directly or through X11?
[15:15] <michiel81> yeah
[15:15] <michiel81> added the calibration coords to 10-evdev.conf but it doesn't do anything
[15:16] <michiel81> Installed xinput calibrator
[15:16] <michiel81> used modprobe -r hidusb and added 'quirks' manually
[15:17] <michiel81> and when i was able to display the contents/settings from /dev/input/event2 and event3 (forgot the command something with dmesg?)
[15:18] <michiel81> it showed 'tablet input' which it is not
[15:18] <bregma> what does xinput show the device as?
[15:19] <michiel81> HID TOUCH HID Touch Panel
[15:19] <michiel81> It started showing that twice after the modprobe
[15:19] <michiel81> id 13/14
[15:20]  * ogra_ thinks this conversation rather belongs to #ubuntu-x ... not really phone related
[15:20] <michiel81> i disabled id13 using xinput disable id=13
[15:20] <bregma> ogra_, this channel used to be the Ubuntu touch input support channel, there's lots of docs out there that still convey that
[15:20] <michiel81> Ogra, i asked everywhere else and they all pointed me here :P
[15:21] <ogra_> bregma, right, we usually redirect people to ubuntu-x though ... since it isnt the touchscreen for X11 channel anymore
[15:21] <michiel81> i'm just happy to get a reply :)
[15:21] <michiel81> oh ok
[15:21] <michiel81> I can also try there, i'm open to suggestions
[15:22] <michiel81> it seems to be a hard problem to solve.
[15:22] <michiel81> Btw when i use xinput test 14 it does show input and 'button release 1' messages
[15:22] <bregma> well, I'll just suggest setting up a matching rule in /usr/share/X11/xorg.conf.d for MatchUSBID "1bfd:3050" and trick x.org into recognizing it as an evdev device, and see what happens
[15:23] <michiel81> And how do i do that exactly?
[15:23] <bregma> then, I guess, take the conversation over to #ubuntu-x
[15:24] <bregma> take a look at /usr/share/X11/xorg.conf.d/10-evdev.conf -- add another stanza
[15:25] <michiel81> rebooting now let's see what happens :)
[15:26] <michiel81> i'll check in ubuntu-x see if they have an idea. Thank you.
[15:27] <bregma> elopio, was it you I was talking to in Malta about integrating some Unity 7 and Unity 8 desktop tests?
[15:34] <elopio> bregma: yes. Hi.
[15:36] <bregma> elopio, cool, I'm just trying to get plans sorted
[15:42] <michiel81> Well i did add the MatchUSBID to the 10-evdev.conf but didn't do much
[15:46] <mhall119> yay image promotion!
[15:46] <mhall119> r105, here I come
[15:46] <ogra_> yep
[15:46] <ogra_> :)
[15:46]  * ogra_ is upgrading too 
[15:46] <ogra_> getting us the gallery-app back
[15:47] <elopio> bregma: I'm the QA guy assigned to unity. So please let me know how can I help with the testing plan and implementation.
[15:47] <ogra_> (i'm so curious about the rotation sensor fixes ... battery life should be lots and lots better with it )
[15:48]  * mhall119 is downloading the upgrade from a Microsoft store's wifi :)
[15:48] <ogra_> lol
[15:48] <mhall119> we have image signing, right?
[15:48] <ogra_> show them how it is done right :)
[15:48] <ogra_> yes
[15:49] <mhall119> they're doing a free code camp with their Kodu environment, my son's taking it
[15:49] <mhall119> I'm sitting in the back working :)
[15:49] <ogra_> "working"
[15:49] <ogra_> :)
[15:50] <mhall119> yup, on IRC and social media all day, that's me working :)
[15:50] <ogra_> haha
[15:51] <mhall119> ironically, I'm also working on our own programmer training material
[15:51] <ogra_> heh
[15:54] <dpm> hi robru, what are the next steps in getting the qtdeclarative packages from silo 3 uploaded?
[15:55] <robru> dpm, once they have passed the acceptance criteria, somebody needs to mark 'testing: done' in the spreadsheet
[15:55] <robru> dpm, and then I upload them
[15:55] <dpm> robru, ah, thanks. What's the acceptance criteria?
[15:56] <robru> dpm, I dunno, but presumably you have to confirm that this bug is really fixed: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1303746 ;-)
[15:56] <mhall119> the new user setup screens are nice :)
[15:56] <dpm> robru, and who does the testing? I've tested the packages from the silo and I can confirm they fix the bug, but I'm not too familiar with the process or what else needs to be tested
[15:58] <robru> dpm, so typically you coordinate this with whoever is listed as the lander for this landing. in this case that's pmcgowan, mzanetti, and rsalveti. I'm not sure why I put my own name on that one
[15:58] <rsalveti> dpm: if you tested, move it to tested and ask someone to land
[15:59] <dpm> robru, rsalveti, thanks, I can do that. I did test it and it fixed the bug, I just wasn't sure what else would need to be tested
[16:00] <dpm> let me test again with image 105
[16:00] <robru> dpm, yeah theoretically there should be some kind of document that explains what manual and automatic tests can be run to ensure that the new version does not introduce any new regressions, but I don't know where that document is or if it even exists for this particular package.
[16:02] <mzanetti> dpm: right.. what was the outcome of the app install problem?
[16:02] <dpm> mzanetti, let me update to image 105 and try again
[16:02] <mzanetti> dpm: I didn't set it to "testing done" because of that
[16:03] <dpm> ok
[16:11] <taiebot> I am testing r105 and i found a bug the keyboard does not come up in the search bar in the dash
[16:11] <bballguy44> Hi. Is it possible to apply real time patches to ubuntu 14.04 without rebuilding the kernel?
[16:14] <ogra_> taiebot, did you get the new welcome wizard  ?
[16:15] <taiebot> Yes but it hangs when it set the two wifi and did not see the last two messages as i was pressing skip few times. it just jumped to reboot.
[16:16] <taiebot> I am not able to raise the keyboard in any app. :-(
[16:17] <ogra_> it should come up after ~45seconds (there is a bug with the welcome screen, davmor2 can point you to it)
[16:20] <taiebot> ogra: after reboot its ok.
[16:20] <ogra_> right, most likely the same bug
[16:30] <ogra_> taiebot, bug 1335917 FYI
[16:31] <taiebot> Am i the only one seeing Mundefined in the photo of some of my contacts in the messaging app?
[16:38] <cwayne> mterry: this what you had in mind? https://code.launchpad.net/~cwayne18/ubuntu-touch-session/custom-xdg-data/+merge/225051
[16:39] <mterry> cwayne, sure, could work
[16:39] <mterry> a little hard coded...  but since it's a touch-specific ting, that's fine
[16:39] <mterry> cwayne, it works for you this way?
[16:40] <cwayne> mterry: yerp
[16:42] <robru> dpm, so what's the scoop? is silo 3 good to go?
[16:43] <cwayne> ogra_: got a sec for a quick MP? https://code.launchpad.net/~cwayne18/ubuntu-touch-session/custom-xdg-data/+merge/225051
[16:43] <ogra_> cwayne, approved
[16:44] <dpm> robru, it seems so, I asked popey if he could test it for me, and it works for him. My device seems to have unrelated troubles upgrading to image 105 (I'm using dualboot), but I tested the fix last week. I had another issue with downloading apps from the store, but popey could not reproduce it
[16:44] <dpm> robru, I'd add what I've just said as a comment, but I cannot edit the spreadsheet
[16:45] <taiebot> Anyone seeing this with messaging app ? http://uppix.com/f-bug53b1940e0016e3d6.png
[16:45] <taiebot> I am talking about the Mundefined on the picture.
[16:46] <ogra_> taiebot, nope ... i only get the initials there
[16:47] <cwayne> ogra_: thanks :)
[16:47] <ogra_> taiebot, file a bug ... might be translation related
[16:47] <ogra_> (the "M" is correct ... "undefined" isnt
[16:47] <ogra_> )
[16:47] <taiebot> Weird because the contact app is ok
[16:53] <taiebot> https://bugs.launchpad.net/messaging-app/+bug/1335927
[17:03] <robru> dpm, oh ok thanks, I'll add you on the spreadsheet and do the release then, thanks
[17:11] <popey> davmor2: if you have 5 mins can you help me review https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0ArLs7UPtu-hJdDZDNWliMmV1YUJ3Zk1pQlpDdGp4VFE#gid=0
[17:11] <popey> (nexus status link above)
[17:12] <popey> i reviewed it last week and i think it's already pretty up to date
[17:12] <davmor2> popey: I'll give it go after tea
[18:09] <dobey> so, has anyone ported synergy to mir yet? so i can run a synergy client on my phone
[18:32] <taiebot> Will oxide get adblock support ? webbrowser experience on UT is great but it is so different than my pc. I am always suprised (annoyed) to see so many ads on websites.
[19:38] <cwayne> cgoldberg: hey, i released my aros app to the store if you wanna try it out.. it's still got issues obviously, but it at least works for the simple stuff
[19:41] <cgoldberg> cwayne, sweet.. i'll install tonight :)
[20:50] <mterry> tedg, I'm seeing problems with dbus-test-runner and fakeroot.  That sounds like an issue that has been run into in the past?
[20:57] <thomi> tedg: Do you know who's working on reducing app startup times?
[20:59] <AskUbuntu_> What happened to the Ubutu Touch Browser address box? | http://askubuntu.com/q/490126
[22:03] <knott_rays> can you put ubuntu touch into geeksphone revolution?
[22:05] <Beldar> knott_rays, THe channel header has links to phones and tablets known to work.
[22:13] <knott_rays> there is no information about it
[22:42] <knott_rays> what is the cheapest ubuntu touch phone?
[22:45] <sarnold> if you can find a used nexus 4 it ought not be too expensive..
[22:46] <dobey> knott_rays: i don't think the prices have been announced for the meizu and bq phones yet. if you want a phone now, which you can run ubuntu touch on, the google nexus 4 is the only officially supported phone
[22:47] <knott_rays> okay
[22:47] <knott_rays> i think that if it would work with geeksphone revolution, i'd go with that one instead..
[22:57] <dobey> knott_rays: feel free to port it then
[22:59] <knott_rays> uff..
[22:59] <knott_rays> never ported anything, but i'll try..
[22:59] <knott_rays> ..if i even get the phone
[23:01] <knott_rays> it has an intel atom processor in it..
[23:21] <knott_rays> what might be the average battery life..?