[07:16] <jibel> pitti, bonjour
[07:17] <jibel> pitti, vicamo is porting touch on xenial from upstart to systemd
[07:17] <vicamo> pitti: hi
[07:17] <jibel> pitti, there is a special version of systemd for vivid.
[07:17] <jibel> pitti, would you know what are the differences and if it should be applied to xenial
[07:18] <jibel> pitti, or if we should go with the version of systemd in the archive for xenial?
[07:21] <NotKit> what is the status of Ubuntu Touch on xenial?
[07:21] <NotKit> is it reasonable to try porting on aarch64 device?
[07:22] <NotKit> (mixed architecture won't work due to broken 32-bit hwcomposer lib)
[07:23] <jibel> NotKit, the bq m10 works fine, there are still some issues here and there but overall it's okay.
[07:23] <pitti> bonjour jibel, ça va ?
[07:23] <jibel> NotKit, it's in this channel ubuntu-touch/staging/ubuntu/frieza_arm64/
[07:24] <jibel> pitti, ça va et toi?
[07:24] <pitti> jibel: ça va bien aussi, merci ! je peux voir le soleil à nouveau après cinq jours :)
[07:24] <pitti> jibel: WDYM with "special version" of systemd?
[07:24] <jibel> pitti, heh, welcome to Normandy ;)
[07:24] <pitti> jibel: xenial proper's version should work fine
[07:25] <vicamo> pitti: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/
[07:25] <jibel> vicamo, ^ what is 'special' in vivid?
[07:25] <vicamo> pitti: we got systemd_219-7ubuntu6vividtouch1_armhf.deb, so I'm wondering what's the difference between the one we have in normal vivid ports
[07:25] <pitti> vicamo, jibel: https://launchpadlibrarian.net/210619060/systemd_219-7ubuntu3_219-7ubuntu6vividtouch1.diff.gz
[07:25] <NotKit> jibel, is it ok to use rootfs from http://cdimage.ubuntu.com/ubuntu-touch/xenial/daily-preinstalled/current/?
[07:25] <pitti> seems fine
[07:26] <pitti> vicamo, jibel: it's just an upstream fix backport, so xenial should just work
[07:26] <pitti> vicamo: back around the vivid timeframe, I fixed enough units on touch to get the most important bits (unity8, wifi, 3G, browser, phone calls, SMS, etc.) working in the emulator and on the Nexus 4
[07:26] <sil2100> NotKit: hey! Work is ongoing, but well... it's still in development, so hard to say - depends on what level of stability you need
[07:27] <NotKit> at least for it to launch :)
[07:27] <pitti> vicamo: not sure about current devices, I suppose they got more/different custom upstart jobs
[07:27] <pitti> vicamo: I suggest to give it a first try by booting with init=/bin/systemd and checking how far you got
[07:27] <vicamo> pitti: yes, it seems so, and the lxc container doesn't start up, either.
[07:28] <pitti> vicamo: hmm, I fixed that in vivid, so something broke the unit again
[07:28] <vicamo> pitti: I've booted into systemd and has adb shell available
[07:28] <jibel> NotKit, this rootfs should be okay
[07:28] <pitti> vicamo: ah, good
[07:28] <NotKit> thank you
[07:28] <pitti> vicamo: http://pad.ubuntu.com/systemd-porting-sprint has my notes from the initial conversion back then
[07:28] <pitti> vicamo: but that mostly applied to even getting to that point
[07:29] <pitti> vicamo: tvoss asked me about this yesterday, did you take this over from him now?
[07:29] <vicamo> pitti: not yet
[07:29] <pitti> vicamo: updating the container start unit to the changes in the upstart job shuold be trivial, so I suggest starting with that
[07:30] <pitti> vicamo: most of the remaining conversion should be fairly straightforward, except for the android <-> upstart property bridge -- there is no equivalent on the systemd side for that yet
[07:31] <pitti> vicamo: xnox started working on that ages ago, but he got interrupted, so this is the main thing that needs to be discussed/designed
[07:31] <vicamo> pitti: the lxc-android-config.service is already available as it is, so the conversion should no longer be a problem
[07:32] <vicamo> pitti: I bumpped into https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625447
[07:32] <ubot5`> Ubuntu bug 1625447 in Canonical System Image "lxc-start failed to open /dev/null" [Undecided,New]
[07:32] <pitti> vicamo: right, I added that around the vivid timeframe; I suppose it just got out of sync with changes to the upstart job?
[07:33] <vicamo> pitti: hmmmm ... then I'd better check it again
[07:35] <vicamo> pitti: oops, lxc-start argument -d/-F differs
[07:37] <pitti> vicamo: nice and simple then? :-)
[07:38] <pitti> vicamo: although that might actually have been on purpose
[07:38] <pitti> in general it's nicer to let processes run in the foreground and *not* fork with systemd (and also with upstart actually)
[07:38] <pitti> much more useful logging that way
[07:40] <vicamo> not so lucky ...
[07:47] <iAmVille[m]> ;0;
[08:36] <autra> Hi! When trying to build ubuntu-touch for mako, i have this error "arm-linux-androideabi-gcc: error: unrecognized command line option '-fno-canonical-system-headers'" at the very beginning of the build. I'm on ubuntu 16.04.
[08:37] <autra> the build continues after that, but later I have this error:
[08:37] <autra> system/core/include/cutils/jstring.h:32:35: error: unknown type name ‘char16_t’
[08:37] <autra>  extern char * strndup16to8 (const char16_t* s, size_t n);
[08:38] <autra> so 1/ could it be related? 2/ if not, do I care about the first error?
[08:38] <autra> and of course, how can I solve this?
[08:39] <autra> I'm a bit confused about the second error, because char16_t seems to be defined in this file...
[08:45] <autra> I feel like something is wrong with my toolchain...
[09:09] <autra> anyone?
[09:18] <autra> ok I got the first error resolved: I had the package arm-linux-androideabi-gcc installed, and it was taking precedence over the one in the prebuilts toolchain of my tree. What's funny is that the reported versions were the same (4.8)
[09:19] <autra> but still it complains about unknown type name 'char16_t'
[09:19]  * autra tries cleaning everything
[10:22] <saavento> hi
[10:27] <sil2100> popey: hey! Could you op me for a moment? :)
[10:47] <sil2100> popey: thanks!
[10:47] <mcphail> sil2100: nice! Thanks all
[10:47] <brunch875> bah, rc-proposed removes the excitement of otas :P
[10:48] <sil2100> ;)
[10:48] <sil2100> Yeah, removes the excitement of OTAs but adds the excitement of breakage-risk, e.g. you never know when your phone stops booting ;p
[10:48] <sil2100> Didn't happen for a while though
[10:49] <mcphail> bfiller: have all of your own/nextcloud caldav improvements made it into OTA13? Can we access shared calendars on the shipped version?
[10:50] <popey> mcphail: that's what the changelog says! :D
[10:51] <mcphail> Ooh - where's the changelog?
[10:52] <popey> i think it was in a previous update which said it wouldn't start working until ota-13, wasn't it?
[10:53] <popey> "- Register app as "owncloud-caldav" online account application (ota13 required)" in 0.5.865
[10:53] <mcphail> There's been a 2stage fix. One allows multimple next/owncloud calendars (yay!) and a further on allows access to own/nextcloud calendars which have been shared with you
[10:54]  * mcphail needs to know where his wife expects him to be ;)
[10:54] <popey> oh, i see
[10:55] <mcphail> I might just flash it and try
[11:14] <iAmVille> iAmVille[m]: test
[11:15] <iAmVille> @iAmVille[m] test
[11:15] <iAmVille> Sorry, could've used another channel
[11:25] <robinhero> Is the image server under a high load? Because the System Updater doesn't find anything for me? The loading wheel is just spinning
[13:01] <robinhero> hey guys, what does this mean in the OTA-13 changelog? "Initial implementation of storage framework"
[13:12] <dobey> robinhero: i'm not sure if that's actually in the image yet
[14:00] <jgdx> mardy, hey, could you take another look at [1]? I've addressed your comments that you made on [2]. [1] https://code.launchpad.net/~phablet-team/ubuntu-system-settings/path-fixes/+merge/306115 [2] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/snapd-paths2/+merge/305751
[14:01] <jgdx> moved to team due to the lengthy life of this branch
[14:04] <mardy> jgdx: hi! Yes, I saw it, but you didn't address a couple of important ones: the one about QQmlEngine, and the other about relative urls, which should be treated as relative to the plugin's manifest file location
[14:04] <mardy> jgdx: both re in src/plugin-manager.cpp
[14:04] <mardy> *are
[14:05] <lotuspsychje> when is ota13 date release?
[14:07] <jgdx> mardy, hm, missed those comments
[14:07] <jgdx> lotuspsychje, today!!1
[14:08] <lotuspsychje> jgdx: yes!
[14:08] <lotuspsychje> tnx :p
[14:12] <aquiles> Facebook messenger and whatsapp ??
[14:13] <faenil> ?
[14:13] <dobey> ask facebook for them?
[14:13] <aquiles> When we will have whatsapp and facebook for ubuntu touch?
[14:13] <popey> aquiles: ask the developer of those apps
[14:14] <aquiles> *facebook messenger
[14:14] <jgdx> developers
[14:15] <aquiles> I'm using Ubuntu phone a half a year and I cant use facebook messenger and whatsapp
[14:15] <lotuspsychje> aquiles: more secure you dont :p
[14:15] <faenil> aquiles: unfortunately the way those platforms work like is: Facebook/WhatsApp gives you permission to access their unlimited APIs and develop and app. That has a cost for them as well, as they'll have to provide support for the users having problems with those apps, and their image will be affected by any problem the apps have. For that reason, they're very selective, and they won't consider any plat
[14:16] <faenil> form that is not a definite business gain for them
[14:17] <faenil> the alternative is to have some kind of Android compatibility layer that lets you run Android apps on UbuntuTouch. That way you'd be able to use the WhatsApp and Facebook Android apps
[14:18] <aquiles> Yes, compatibility layer
[14:19] <faenil> aquiles: you might want to file a bug about that (or subscribe to any existing one) and push to make that happen
[14:19] <aquiles> Any ideas if canonical already began built a compatible layer to use android apps?
[14:22] <aquiles> Because android is linux and ubuntu is ubuntu
[14:23] <aquiles> I fill a bug latter
[14:23] <aquiles> Ubuntu*linux
[14:23] <dobey> no, a compatibility layer is not really feasible
[14:24] <aquiles> Why not ?
[14:24] <dobey> the security models are incompatible
[14:25] <aquiles> And porting android apps in a easy way?
[14:25] <aquiles> React native...
[14:27] <jgdx> mardy, right, good point re: plugin.cpp asking for some engine's rootContext. Not sure that ever made sense
[14:28] <aquiles> I'm beginning to think to use android again, I don't have a reliable phone os
[14:30] <brunch875> I'd rather see XMPP and improvements to notifications / app lifecycle before an android compatibility layer, really
[14:31] <faenil> dobey: I wouldn't jump to conclusions like that :)
[14:32] <dobey> faenil: i'm not "jumping" to any conclusions
[14:34] <jgdx> dobey, turing would turn in his grave if he saw you make such conclusions
[14:35] <dobey> ...
[14:50] <DaDaCinnamon> Saw this & thought of you: http://www.breakingnews.ie/tech/new-google-phones-will-be-revealed-october-4th-755564.html
[14:57] <HoloIRCUser6> Anybody here?
[14:57] <dobey> !ask | QT
[14:57] <ubot5`> QT: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience
[15:43] <faenil> brunch875: what kind of improvements to notifications in particular?
[15:44] <brunch875> tightly related to application lifecycle: like a message received on dekko
[15:45] <faenil> brunch875: ah ok, did you the polld plugins news? (that apps can plugin to polld iirc)
[15:46] <faenil> did you see*
[15:46] <brunch875> no, care to link me? ☺
[15:46] <faenil> https://lists.launchpad.net/ubuntu-phone/msg21839.html
[15:46] <brunch875> nice!!
[15:47] <faenil> mardy can give an update on the status of that I guess :)
[15:47] <faenil> maybe to the ML? :)
[15:52] <sebsebseb> hi
[15:54] <faenil> sebsebseb: hi!
[15:55] <sebsebseb> faenil: hi
[16:54] <flohack> Hi there, again Im going to nag you with my apport log :)
[16:54] <flohack> http://pastebin.com/XZ2y8JQA
[16:54] <flohack> Can anyone imagine why the SessionManager is not running and/or what kind of dbus problem Im facing?
[17:16] <mterry> popey: re bug 1625074, we keep a list of teams we watch for to make sure we have maintainer coverage: http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/package-subscribers#L107  -- maybe ~system-apps-team would be a good fit?
[17:16] <ubot5`> bug 1625074 in Ubuntu Terminal App "[MIR] ubuntu-terminal-app" [High,In progress] https://launchpad.net/bugs/1625074
[17:16] <flohack> Plus, do I need to somehow enable developer mode on my port image manually because at the moment I cant access it via GUI of course
[17:47] <popey> mterry: agreed :)
[18:08] <Michalp> hello every body, I need your help, I have MX4 with custom bootloader and when I want install ota 13, restart go to custom bootloader so how install??
[18:11] <sebsebseb> Michalp: custom boot loader hmm?
[18:19] <Michalp> TWRP
[18:21] <powerless> hey folks...has anyone installed ubuntu touch on galaxy s6 edge?
[18:21] <dobey> Michalp: that is recovery, not bootloader
[18:22] <dobey> !devices | powerless
[18:22] <ubot5`> powerless: You can find the full list of devices, official images, community images, and works in progress at https://wiki.ubuntu.com/Touch/Devices
[18:22] <dobey> Michalp: why do you have TWRP? ubuntu needs the ubuntu recovery
[18:23] <powerless> ubot5`: yaah..theres no s6 there. i thought it wasnt complete cause find it hard to believe that no one had ever tried..its not a bad phone :P
[18:23] <ubot5`> powerless: I am only a bot, please don't think I'm intelligent :)
[18:24] <powerless> clever
[18:24] <Michalp> If you have android version of mx4, it is easy way how to flash ubuntu touch to mx4, finally it was only one way how to flash
[18:25] <Michalp> I tried find different way but not find.
[18:26] <Michalp> So any idea?
[18:27] <dobey> Michalp: how exactly did you flash ubuntu onto the device?
[18:27] <dobey> Michalp: you should boot to recovery with adb enabled, and then use ubuntu-device-flash from an ubuntu machine to flash it
[18:28] <dobey> once ubuntu is on the device, OTA updates are installed via system settings; you don't need to manually flash each OTA
[18:29] <Michalp> But when I click to install, then system reboot and go to custom bootloader
[18:30] <NotKit> Michalp, if you used 4PDA way to install it on Android device, you can't update it regular way
[18:31] <NotKit> image needs to be rebuilt
[18:32] <dobey> Michalp: why do you have TWRP (again, it is recovery, not bootloader)
[18:33] <Michalp> Sorry for exchange recovery by boootloader, any way you know how to get ubuntu touch to android version?
[18:33] <NotKit> I think because his device is Android edition, not Ubuntu one
[18:33] <NotKit> https://yadi.sk/d/Xuvo0JXImWnQN check dualboot_make_system_img.sh
[18:33] <Michalp> yes, I have android version
[18:34] <mrclp> It is difficult to port to zenfone 2 laser ze550kl? Have someone tried?
[18:35] <Michalp> this one I flash
[18:36] <Michalp> but first time you need use twrp
[18:38] <Michalp> the script can not function if you have android, it works after detect ubuntu
[18:40] <dobey> oh it's not because it was originally an android device
[18:40] <dobey> it's because you're trying to dual boot?
[18:41] <Michalp> I no need dual boot, it was bcs is only one way how to flash, nobody give me other way
[18:41] <Michalp> how to flash android lock version to ubuntu touch
[18:41] <Michalp> bcs you must unlock than flash
[18:42] <dobey> can you adb to the phone over usb while at twrp?
[18:42] <Michalp> I don't know, I can try
[18:49] <Michalp> No it doesn't find device
[18:50] <dobey> hmm ok
[18:55] <Michalp> If ota need update where reboot?
[18:57] <Michalp> Or I need wit to new image OTA13  from https://yadi.sk/d/Xuvo0JXImWnQN and then flash? :(
[18:58] <dobey> no you should not download anything from an unofffical site
[18:58] <dobey> you need to reflash your phone properly. can you flash a different recovery image to the device?
[18:59] <Michalp> I just want ota 13 to my deveice, how I don't care
[18:59] <Michalp> If  exit way how to flash then I will flash
[18:59] <dobey> well i'm sure you'd care if you downloaded a hacked image and it was sending your personal info somewhere unsavory
[19:03] <Michalp> I have not choice, original ubuntu touch mx4 can not get, I am working on UT more then one year with nexus 4 there all work official way, but with mx4 is different, there I have not choice how to flash UT by official way
[19:04] <dobey> you need the correct recovery image
[19:06] <Michalp> I am not sure if you are right, bcs I try flash original recovery of UT for MX4, but then I can not flash ubuntu by adb
[19:06] <Michalp> this one I tried before
[19:06] <Michalp> it wrote me no space to install
[19:07] <dobey> you need to repartition the phone
[19:08] <Michalp> If you know how to do, please let me know. Bcs I spend more then 3 days to find way how to install UT to MX4 and I got only one way (flash it by twrp)
[19:10] <Michalp> Anyway, reparptition phone looks very hard, isn't it?
[19:10] <dobey> you need a special tool for it. i'm trying to find better info to help you
[19:12] <dobey> Michalp: http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039 perhaps
[19:14] <Michalp> this link I tried firstly, but no function
[19:15] <Michalp> So this way I can not accept
[19:16] <Michalp> I try it with support from here, and no find function way. Tool don't find my device, I tried it in win and in ubuntu
[19:17] <Michalp> that is why I find only flash dual boor image
[19:17] <Michalp> by twrp
[19:25] <Michalp> So looks no any new idea, right?
[19:28] <dobey> i don't know
[19:28] <dobey> the old dual boot script stuff is old and not really supported
[19:29] <dobey> and running ubuntu properly on the device really requires repartitioning
[19:29] <NotKit> dobey, I think, he doesn't use dual boot script, but actually boots it the same way as on ported device
[19:30] <NotKit> is repartitioning possible on MX4?
[19:30] <dobey> NotKit: well it's clearly not the same way, because it doesn't work :)
[19:30] <NotKit> it does work
[19:30] <dobey> NotKit: yes, at least on some of them
[19:30] <NotKit> for OTA 12
[19:30] <dobey> well it "works"
[19:30] <NotKit> he can't update to OTA 13 since there are not system.img built for it
[19:30] <NotKit> *no
[19:30] <dobey> the partitions are still wrong, and OTAs won't work
[19:31] <NotKit> that's true
[19:31] <NotKit> it should be possible to use that script though to rebuild system.img and replace it manually or through recovery
[19:37] <Michalp> So you mean, I can try this script in my case?
[19:39] <NotKit> that script should build system.img with latest OTA
[19:40] <Michalp> And script connect to net, where download latest image?
[19:40] <NotKit> yes
[19:41] <Michalp> I see, I will try
[19:44] <Michalp> NotKit: will you here tomorrow? I must go out today, but tomorrow I will continue
[19:44] <NotKit> yes
[19:46] <Michalp> Great, many thanks.  See you tomorrow. once again thanks
[20:20] <JanC> is it intentional that OTA-13 now shows a "no SIM" icon (for the second SIM slot?) in the network indicator?
[20:20] <JanC> it's rather pointless (and looks ugly)
[20:23] <JanC> (this is on the bq E4.5, if that matters)
[20:26] <mcphail> JanC: my e4.5 on rc-proposed does that, so I suspect it is normal. I agree it is ugly
[21:43] <krowv> Does OTA13 update via System-Settings->Updates?
[21:43] <matv1> krowv yes
[21:44] <krowv> matv1: ok.  this is my first OTA update.  must not have fully rolled out yet.  My phone doesn’t seem to see it.
[21:44] <matv1> I heard  it could be wednesday before everyone has it
[21:45] <matv1> but you will get a notification of it when it is available to your device
[21:45] <krowv> Cool.  My trusty Nexus 4 will be waiting.  :)
[21:46] <matv1> awsum :)