[08:44] <abeato> ogra_, why do some scripts fail when executed from console-app in touch?
[08:44] <ogra_> you mean the terminal ?
[08:44] <abeato> ogra_, in my case : /bin/sh: bad interpreter: Permission denied
[08:45] <abeato> yep
[08:45] <ogra_> security blocks
[08:45] <abeato> how can I overcome that?
[08:45] <ogra_> i think mzanetti has a way
[08:45] <ogra_> through his openappstore
[08:45] <ogra_> (running the terminal unconfined)
[08:47] <abeato> ogra_, hmm, and what is the rule for preventing execution? what is not allowed?
[08:47] <ogra_> no idea
[08:48] <ogra_> you can enable ssh and do something like "ssh phablet@localhost", that gives you a full login session
[08:48] <mzanetti> ogra_, abeato: that shouldn't be the case. the terminal app is allowed to run arbitrary stuff
[08:48] <mzanetti> it will still be SIGSTOPed when unfocusing the terminal app, but above error is new to me
[08:48] <ogra_> (but note that gets backgrounded and suspended when you put the terminal out of focus, if you re-focus it yopu need to type "fg" to get it back)
[08:49] <ogra_> mzanetti, it isnt allowed to spawn subshells iirc
[08:49] <abeato> ogra_, sure I know, what I want to use the app in this case :)
[08:49] <mzanetti> I think it is... at least I haven't ran into any restrictions except the pausing in background
[08:50] <ogra_> i ran into the "bad interpreter" message quite often in the past
[08:50] <abeato> mzanetti, ogre, was trying to run http://people.canonical.com/~okubik/adb.sh
[08:50] <abeato> ogra_, :)
[08:50] <ogra_> thoug i never bothered to research it  more
[08:51] <ogra_> abeato, well, i guess thats the mount call
[08:51] <abeato> ogra_, no, it is when executing the script, it does not reach the wget
[08:51]  * mzanetti tries
[08:51] <abeato> it just does not like spawning a shell apparently
[08:51] <ogra_> yeah
[08:52] <ogra_> as i said, no subshells
[08:52] <ogra_> you shoudl eb able to run aech of the commands manually
[08:52] <abeato> correct, that works
[08:53] <mzanetti> abeato, is this to fix frieza's adb?
[08:54] <abeato> mzanetti, it is a just workaround to make things easier for people
[08:54] <abeato> mzanetti, the fix will arrive in ota 10
[08:55] <mzanetti> but we're talking about frieza's not working adb? or some other adb fixes that apply to all devices?
[08:58] <abeato> mzanetti, no, forget about adb, it is just an example of a script not being launched in terminal app (I have copied it to phablet home, it is not in the image)
[09:02] <[tj]> are headphone buttons supported?
[09:02] <[tj]> like the volumne up/down or the pause button on a mic?
[09:02] <[tj]> if not I will report a bug in podbird
[09:15] <[tj]> moin
[09:18] <popey> [tj]: no, but I don't think that's a podbird bug, but a platform one
[09:19] <[tj]> yeah, looks like a platform one
[09:19] <[tj]> popey: where should they be reported?
[09:19] <popey> https://launchpad.net/canonical-devices-system-image
[09:19] <[tj]> there is another with the 'headphones' volume slider
[09:19] <popey> i would be surprised if there's not already a bug for that
[09:20] <[tj]> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1538231
[09:22] <[tj]> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1309731
[09:22] <[tj]> https://bugs.launchpad.net/music-app/+bug/1231909
[09:22] <[tj]> third one is more general
[11:13] <pete-woods> jgdx: hey, I put a fix for the rapid property change bug in silo 75, too
[11:13] <pete-woods> hopefully it works for you, too :)
[11:58] <jgdx> pete-woods, woo
[12:02] <jgdx> pete-woods, the rapid fix is in 20160304 that was just uploaded?
[12:04] <pete-woods> jgdx: should be, yes
[12:05] <jgdx> okay, testing
[12:29] <jgdx> pete-woods, are you able to repro this [1]? Could be debilitating, but kinda edge.
[12:29] <jgdx> pete-woods, other than that, everything seems to work great.
[12:32] <pete-woods> jgdx: link missing?
[12:33] <jgdx> pete-woods, heh, bug 1551258
[12:33] <jgdx> APN? wut
[12:34] <pete-woods> jgdx: I haven't tried to reproduce it
[12:34] <pete-woods> but it sounds bad
[12:34] <pete-woods> I really didn't even have enough time to look at that other bug, though
[12:34] <pete-woods> had to do it before work this morning
[12:36] <jgdx> :s
[12:36]  * pete-woods is really behind on this snappy work
[12:36]  * pete-woods sucks at Go
[12:36] <jgdx> mpt, hey, what constitutes a valid certificate? The spec is rather vague https://wiki.ubuntu.com/Networking#VPNs
[12:37] <jgdx> pete-woods, just use channels for everything and you're good
[12:37] <pete-woods> well as far as the API is concerned, a valid certificate is just a path to a file that exists
[12:38] <pete-woods> it just gets punted as a cmd line parameter to the openvpn binary
[12:38] <pete-woods> afaict the openvpn plugin doesn't do anything to interpret the certificates itself
[12:39] <jgdx> pete-woods, yeah, i've implemented code to deal with that http://bazaar.launchpad.net/~jonas-drange/ubuntu-settings-components/vpn/view/head:/plugins/Ubuntu/Settings/Vpn/ubuntusettingsvpn.cpp
[12:40] <jgdx> just not sure that e.g. a self signed certificate is an invalid one
[12:40] <pete-woods> I don't think it is
[12:40] <pete-woods> you might be connecting to your home VPN
[12:40] <jgdx> … in our ui, not philosophically/practicly
[12:41] <pete-woods> well I use our UI to connect my phone to my home VPN
[12:41] <pete-woods> and that uses a self signed cert
[12:41] <pete-woods> so it seems a pretty legit use case
[12:41] <jgdx> but if someone handed you a self signed cert…
[12:42] <pete-woods> I would add it to my list of trusted certs without question
[12:42] <pete-woods> ;)
[12:43] <pete-woods> at any rate, we can change that behaviour if people (like me) complain about their self-signed certs
[12:44] <pete-woods> or maybe we add a "I know what I'm doing" checkbox
[12:44] <jgdx> pete-woods, right
[12:52] <peat-psuwit> mariogrip: devices.ubports.com seems to have trouble authenticating with Launchpad. It gives me 502 Bad gateway.
[13:04] <mpt> jgdx, I know that invalid certificates exist, but I don’t know what makes a certificate invalid, sorry
[13:04] <mpt> It’s hard to find technical details about the structure and validity of certificates
[13:05] <jgdx> mpt, okay, I can tell you what I interpreted it to be: blacklisted, expired, self-signed, empty
[13:06] <jgdx> mpt, I am not sure about the self-signed one
[13:07] <mpt> jgdx, hmm, that seems very similar to the types of invalidity for TLS certificate
[13:07] <jgdx> mpt, good
[13:44] <Mirv> oSoMoN: since you're probably fast to do it, could you please double check 5.5.1+dfsg-15ubuntu1 from silo 051 still has TLDs intact? I'm 99% sure but Debian eventually started just calling that one script with LC_ALL instead of running the packaging with it
[13:47] <oSoMoN> Mirv, sure, let me check
[13:50] <oSoMoN> Mirv, confirmed, it looks good
[13:50] <Mirv> oSoMoN: thanks!
[14:05] <oSoMoN> sil2100, I’d need a core-dev ack for the packaging changes at https://code.launchpad.net/~osomon/webbrowser-app/qml-module-naming/+merge/288080, do you think you could take a look one of these days (not super urgent)?
[14:10] <Mirv> oSoMoN: I've PPU for webbrowser-app nowadays so it sohuld be enough (http://people.canonical.com/~ubuntu-archive/packagesets/xenial/ubuntu-qt-packages)
[14:10] <Mirv> oSoMoN: but the silo will need binNEW review from archive admin due to "new" packages
[14:12] <Mirv> oSoMoN: but actually, I just spotted on another going through there's no correct Replaces for the -doc package...
[14:14] <Mirv> commented. all of these really should be read through three times since they've so many little details in there..
[14:15] <Mirv> of course, an upgrade test to the silo when available, with all packages installed already before upgrading, is also one very useful way to check
[14:57] <mariogrip> peat-psuwit: I did a restart, does it work now?
[14:57] <mariogrip> it seems to be working for me
[14:58] <oSoMoN> Mirv, ah, thanks for spotting that
[14:59] <peat-psuwit> mariogrip: No. It still does not work.
[15:06] <mariogrip> peat-psuwit: now?
[15:07] <peat-psuwit> mariogrip: Ok, it works now. What happened?
[15:08] <mariogrip> it failed to request the launchpad api, so I added a try/catch
[15:09] <peat-psuwit> mariogrip: Ok. Thank you.
[15:10] <peat-psuwit> mariogrip: BTW, is it possible to customize the install instruction? I need some special way to boot into fastboot.
[15:11] <mariogrip> peat-psuwit: I haven't added that, but I can add that in next release
[15:11] <peat-psuwit> mariogrip: Ok.
[15:35] <peat-psuwit> does image in devel-proposed channel boot now?
[15:37] <ogra_> peat-psuwit, probably in 6 months
[15:38] <peat-psuwit> ogra_: So it's broken now, right? What happens?
[15:38] <ogra_> nothing, its nothing anyone uses
[15:39] <ogra_> once the phonne switches to a 16.04 base people will start looking after it
[15:39] <ogra_> actual development doesnt happen there anyway .... its just the place where everything gets dumped atm
[15:39] <ogra_> development happens in rc-proposed
[15:40] <peat-psuwit> ogra_: Ok. Thank you.
[15:51] <homa> hi
[15:51] <homa> i want change android of fonepad7 fe375cg to ubuntu touch how can i do?
[15:51] <homa> are there every body here?
[15:51] <dobey> !devices | homa
[15:52] <k1l> look out if someone made a port already for that specific phone.
[15:52] <k1l> if not you would need to make a port yourself, which is not a beginners task
[17:05] <talmage_> Is there a repo that contains Ubuntu Touch as packages that I can install on x86 16.04?  I have a WeTab tablet that's running 16.04.
[17:06] <talmage_> I tried the img files for x86 but I couldn't figure out how to boot from them.  I expected them to be disk images.  My WeTab couldn't boot from them, alas.
[17:06] <kenvandine> dobey, how's the battery life on your nexus 5?
[17:08] <dobey> kenvandine: well, not great
[17:08] <kenvandine> dobey, is that because of ubuntu or because your battery is old?
[17:08] <dobey> kenvandine: and recently rc-proposed results in maliit-server and unity8-dash constantly restarting; so very short life there
[17:09] <kenvandine> dobey, and the only real issue is lack of bluetooth right?
[17:09] <dobey> kenvandine: pretty sure because of ubuntu
[17:09] <dobey> well, i can't use an image that has bluez5, because there's no EGL now :(
[17:09] <dobey> my pre3 is old. it still lasts almost 3 days
[17:10] <kenvandine> dobey, i have a friend thinking about a nexus 5, i guess i should steer him away from that :)
[17:10] <dobey> my nexus5 is nowhere near that good for battery (at least wiht ubuntu on it)
[17:10] <dobey> kenvandine: well, if i could figure out what broke and get things working, it could probably be good
[17:10] <dobey> but alas, i'm not a kernel/egl/whatever developer
[17:11] <dobey> talmage_: the debian packages which make up the ubuntu phone images are all available in the ubuntu archive already
[17:12] <dobey> talmage_: the x86 "generic" image isn't really generic. it's the image for the x86 emulator
[17:12] <dobey> and no, it's not disk images
[17:12] <dobey> kenvandine: any idea why EGL would fail to initialize after an update? :)
[17:13] <kenvandine> dobey, no clue...
[17:14] <ogra_> because something broken indeed
[17:14] <ogra_> *broke
[17:14] <dobey> thank you captain obvious
[17:14]  * ogra_ grins
[17:16] <dobey> well, the device tarball didn't change
[17:16] <dobey> so i wonder why this isn't an issue on more devices :-/
[17:17] <dobey> mariogrip, mhall119: i'm curious, what exactly was the "fix" for this similar issue on fairphone?
[17:18] <mariogrip> dobey: permission was the issue
[17:18] <dobey> mariogrip: what permission?
[17:18] <mariogrip> dobey: dev folder
[17:18] <mariogrip> http://people.ubuntu.com/~mariogrip/Ubuntu-touch/70-bacon.rules
[17:19] <popey> \o/ bacon
[17:20] <popey> http://drool.popey.com/
[17:20] <dobey> mariogrip: so all the devices had wrong permissions? or the folder itself?
[17:20] <mariogrip> popey: have you set your irc client to notify you on bacon?
[17:21] <mariogrip> dobey: in the fp2 it was because it was missing  the rule file
[17:21] <mariogrip> popey: :P
[17:22] <ogra_> dobey, the device tarbal for N5 or the device tarball for everything else ?
[17:22] <ogra_> (what didnt change)
[17:22] <dobey> ogra_: the one that's used for N5
[17:22] <ogra_> right
[17:22] <ogra_> so perhaps you are lagging
[17:22] <ogra_> i think there was a new device tarball recently on my MX4
[17:22] <popey> mariogrip: nope :)
[17:22] <dobey> ogra_: oh?
[17:23] <ogra_> and Mir went to 0.20.1
[17:23] <ogra_> around MWC
[17:23] <dobey> this has been broken before that, but i know about the mir release
[17:23] <ogra_> well, 0.20.0 around MWC actually
[17:24] <dobey> hmm, it changed on mako in jan
[17:24] <mariogrip> dobey: I also ordered a second hand  n5, so I can start developing on it
[17:25] <ogra_> yay
[17:26] <dobey> hmm, why has the device tarball for mako changed so much; and what changed exactly
[17:27] <ogra_> you have to ask one of the hardware guys
[17:49] <mhall119> morphis: is there anything I can add to my Nexus 4 other than silo0 to try and get wifi display working?
[17:49] <morphis> mhall119: you wont get it working nexus4 right now
[17:49] <mhall119> I'm on the latest rc-proposed/bq-aquaris.en channel with apt updates
[17:50] <morphis> the hardware encoding bits are Android 5.x only right now
[17:50] <mhall119> morphis: I was afraid of that answer, I keep trying it every update anywa :(
[17:50] <morphis> mhall119: I know, and I know a lot people are after that :-)
[17:50] <mhall119> time to finally upgrade the android bits on mako
[17:50] <morphis> mhall119: there will be a refactoring of how the encoder works soon to squeeze more performance out of it
[17:50] <morphis> mhall119: no, no need for that
[17:51] <morphis> that is a more risky game
[17:51] <mhall119> so will the android bits be backported for the N4?
[17:52] <morphis> mhall119: no
[17:53] <morphis> mhall119: basically there is a MediaCodec class in stagefright which is the base interface to interact with the OMX based codecs
[17:53] <morphis> right now we're using a class MediaCodecSource from 5.x which puts some wrapping around MediaCodec to use it in an easy write/read way
[17:54] <morphis> so what we will do anyway to have a better control how buffers are passed around is using MediaCodec directly from aethercast
[17:54] <morphis> and that then mostly works the same way on 4.x and 5.x
[17:55] <morphis> (with small differences)
[17:56] <morphis> mhall119: with that it should mostly work then the same way on all devices
[17:59] <mhall119> morphis: ah, cool, well I'll keep checking on the state of things so I can jump in and test it once that change happens
[18:00] <morphis> mhall119: I will ping you when it comes :-)
[18:00] <morphis> this thing needs a lot of testing anyway so all we can get is good
[18:02] <morphis> mhall119: however its still something we have to find how well miracast performs on the different devices we have
[18:02] <mhall119> morphis: anytime, just let me know. I have a spare N4 that I can break, and a miracast-capable TV
[18:03] <morphis> mhall119: from which vendor?
[18:03] <mhall119> two TVs, though one lists miracast as a "beta" feature that doesn't even indicate that a connection is attempted
[18:03] <mhall119> TCL is the beta-support TV, the other is a Samsung (not sure the model off the top of my head)
[18:03] <morphis> ok
[18:03] <mhall119> neither are fancy/expensive, but both are "smart"
[18:05] <mhall119> also, there's an appliance/electronics store near me with dozens of display units advertising miracast support :)
[18:05] <mhall119> I checked with aethercastctl last time I was in there
[18:19] <dobey> i wonder wtf broke on hammerhead :(
[19:12] <talmage_> dobey: I'm installing the ubuntu-touch package on my x86 WeTab.
[19:13] <talmage_> When it generated the initramfs, it said "E: no boot partition found !"
[19:14] <talmage_> It said "run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1"
[19:14] <talmage_> Is it safe to reboot the WeTab and try out Ubuntu Touch?
[19:14] <ogra_> because it isnt designed for that
[19:16] <dobey> huh?
[19:16] <dobey> ubuntu-touch is a metapackage
[19:17] <dobey> there are a couple packages it pulls in though, that might add some stuff that conflicts with normal Ubuntu things
[19:17] <talmage_> yes.  I did 'sudo apt-get install ubuntu-touch'
[19:17] <talmage_> There was a conflict with a language pack.
[19:17] <talmage_> I removed that.
[19:18] <talmage_> No other conflicts with installed packages.
[19:18] <dobey> you need ubuntu-touch-session i think
[19:18] <ogra_> dobey, initramfs-tools-ubuntu-touch is not used at all usually ... only on nexus4 for dev purposes
[19:18] <dobey> i don't mean packaging or file conflicts
[19:18] <ogra_> all proper devices use the binary initrd
[19:18] <dobey> i mean ideological conflicts in how things work
[19:18] <ogra_> but anyway, you cant just install it through debs
[19:18] <dobey> because a phone isn't a PC and a PC isn't a phone
[19:19] <ogra_> on an x86 install you can surely install the mir session though
[19:19] <ogra_> but i dont know how
[19:19] <ogra_> #ubuntu-mir would know
[19:19] <talmage_> dpkg tells me that I have ubuntu-touch-session installed.
[19:20] <talmage_> So I can probably reboot my tablet.
[19:20] <talmage_> How do I start the touch session?
[19:20] <ogra_> you cant
[19:20] <ogra_> it isnt designed that way
[19:21] <ogra_> you want a desktop install and additionally install the unity8-mir-session on that ... that is designed to be used on PCs
[19:21] <ogra_> everything else will just totally mess up
[19:21] <talmage_> So I have a tablet with 16.04 desktop installed.
[19:22] <talmage_> On top of that, I installed ubuntu-touch.
[19:22] <ogra_> right, you cant just install the phone SW on it
[19:22] <ogra_> that will probably even break booting
[19:22] <ogra_> ubuntu-touch isnt for "normal" use ... it can be used for image builds but you cant "just install" it ... the result will just be broken
[19:23] <talmage_> Oh.
[19:23] <ogra_> there is a way to get a unity8 desktop session (so you get the touch UI) ... but i dont know whats the package name for that
[19:23] <ogra_> ask in #ubuntu-desktop or in #ubuntu-mir
[19:24] <talmage_> That will give me the Ubuntu Tablet UI on my x86 tablet?
[19:27] <talmage_> ogra_: thanks.  I'll ask in #ubuntu-mir
[19:28] <talmage_> You were right that the result was broken.  I just rebooted the tablet.  initramfs failed.  Time to reinstall the desktop.
[19:30] <dobey> why not just fix it instead of reinstalling?
[19:30] <dobey> but anyway
[19:33] <talmage_> Yes, I suppose.  Not sure how to fix it.
[19:36] <dobey> boot the installer and "try out ubuntu", mount the root partition of the installed system to a directory, chroot into that directory, uninstall initramfs-tools-ubuntu-touch or whatever, rebuild the initramfs, and reboot
[19:37] <talmage_> I can try that.
[19:39] <ogra_> dobey, it will have pulled in upustart in parallel to systemd and a ton of other things ... a reinstall is really the easier way
[19:40] <ogra_> (and lxc-android-config ... adb ... etc etc )
[19:40] <talmage_> OK. Back to plan 1! :-)
[19:40] <dobey> whatever
[19:41] <talmage_> I noticed lxc-whatever being installed.  Wondered why it needed containers.
[19:41] <dobey> to contain things
[19:41] <ogra_> heh
[19:41] <ogra_> the android based devices all need to use the binary android drivers ... they run inside a container
[19:42] <ogra_> annd the ubuntu-touch stuff is all crafted around that
[19:42] <ogra_> which is why it breaks if you just try to install it on a normal desktop pc
[19:46] <talmage_> Good to know.  Thank you ogra_ and dobey.
[20:38] <ddd_> Think I've bricked my Nexus 4 - I got impatient - Has anyone had any success with fastboot flashing back to factory when it looks  like its bricked?
[20:40] <dobey> yes
[20:40] <dobey> or from recovery
[20:40] <dobey> what do you mean it is "bricked" ?
[20:46] <ddd_> IT's booting to a purple screen saying it needs a pc to recover
[20:47] <ddd_> I've managed to get it back to Cyanogen Mod to boot
[20:47] <ddd_> Will flash touch again and be more patient this time
[20:47] <najah> hello all, is Ubuntu supported by some devices like galaxy S3 / nexus or is it possible to flash galaxy A3 with ubuntu ?
[20:47] <ddd_> Thanks so much for responding though
[20:48] <ddd_> Not sure Sir - I think there is a list of supported devices
[20:48] <ddd_> Let me get the URL
[20:48] <najah> this one ? https://wiki.ubuntu.com/Touch/Devices
[20:48] <ddd_> https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[20:48] <ddd_> There is a section for supported devices in there
[20:49] <ddd_> Good luck
[20:51] <najah> thanks
[20:51] <najah> i'm very sad about ubuntu is unsupported for this device
[20:53] <ddd_> That's a shame
[20:53] <ddd_> Perhaps you can pick up a 2nd hand device?
[20:53] <dobey> do any of those devices have 4.4.2 available?
[20:54] <najah> yes, I'm going to sell it and buy a supported devices
[20:54] <dobey> galaxy nexus doesn't; might be why it was dropped
[20:56] <najah> thanks ddd_, have a good day
[20:56] <dobey> galaxy a3 could be ported
[20:56] <dobey> just needs someone to do the work
[20:56] <dobey> at least, assuming there's an aosp tree for it somewhere
[20:56] <ddd_> You too
[20:56] <dobey> but the hardware should be usable i guess
[20:56] <najah> what does 'do the work' means ? is it developing tasks ?
[20:57] <dobey> yes
[20:58] <najah> i'm a junior sysadmin with 0 developing skills so... I think I'll brick the device
[21:15] <adfad666> ubuntu touch got renamed?
[21:16] <dobey> eh?
[21:16] <dobey> there is no ubuntu touch. there is only ubuntu. :)
[21:42] <jdstrand> beuno, popey: fyi, I will handle the appear-in review
[22:33] <Android-mods> Hello all. I am an android developer that is missing ubuntu and starting to have flashbacks of sublime editor and eclipse. I recently heard of ubuntu touch, and suggestions/tips on getting it to work on the note 5? Sm-n920t skyhigh kernel tekxodus n5 hybrid ur 6.3
[22:43] <mariogrip> Android-mods: the porting guide is a good place to start :) https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/