[08:14] <anand> hello
[08:15] <anand> any one is there
[08:16] <anand> can i install ubuntu in my samsung galaxy s3 neo model phone
[08:18] <anand> hhh
[08:36] <Davidrnd> Hello, is gtk+ supported on the ubuntu touch ? If yes, is there any specials to start an gtk+ app ?
[08:39] <anand> yes
[09:29] <Davidrnd> Ok, i've compiled a gtk+ example app, but i can't start it via the .desktop file.
[09:30] <Davidrnd> The screen goes black and the app terminates. Is there a exapmle how to use gtk+ apps in UbuntuTouch ?
[09:34] <Davidrnd> It was a gtk+ 3 app
[09:44] <Davidrnd> This is just an gtk3 example that i've compiled. But the app did not start. Is there any special entries ( like X-Ubuntu-XMir-Enable=true for gtk2 apps ) that i have to edit in the .desktop file ?
[09:44] <Davidrnd> http://snarvaez.com.ar/notes/gtk3_001.html#sec-3
[10:10] <Davidrnd> Did i have to set the "X-Ubuntu-XMir-Enable=true" and " X-Ubuntu-Touch=true" even for GTK3 apps ? I thought that gtk3 natively supports the mir display server.
[12:30] <Davidrnd>  Hello, As far as i know a GTK3 app should natively run on the ubuntu touch OS. I've compiled this sample app ( http://snarvaez.com.ar/notes/gtk3_001.html#sec-3 ) but the app don't start. Did i have to modify the .desktop file ? ( "X-Ubuntu-XMir-Enable=true" and " X-Ubuntu-Touch=true" like gtk2 apps ? )
[12:33] <mcphail> Davidrnd: whilst gtk3 should be able to use Mir as a abackend, I don't _think_ it is shipped on the device. So you're going to have to ship a mir-compatible gtk3 (and all dependecies) in your snap and do lots of debugging for any hard-coded gtk paths
[12:35] <mcphail> Davidrnd: certainly, that's what we had to do for SDL2 apps
[12:52] <Davidrnd> mcphail: Thanks for the quick answer. So if I can compile th gtk3 app on the ubuntu phone, define the .desktop - file without ( "X-Ubuntu-XMir-Enable=true" "X-Ubuntu-Touch=true" ) it should run correct ?
[12:58] <Davidrnd> BTW is there any documentation about the X-Ubuntu-WHATEVER sections inside of the .desktop file ?
[12:59] <mcphail> Davidrnd: if you chase down all the dependencies and fix any errors coming through in the logs for missing paths etc, it should work. Someone on here mentioned that gtk3 has a lot of hard coded paths. You may need to hack those, as your gtk3 will be bundled in you click's directory
[13:00] <mcphail> Davidrnd: I'm not aware of anyone releasing a mir-native gtk3 app on the phoe, but if you can find one you could pinch their directory structure
[13:06] <Davidrnd> Thanks ..
[13:10] <Davidrnd> So if i use the libgkt-3-dev package on the phone for building an gtk3 app, it should work ? :-)
[13:12] <mcphail> the -dev package is just the headers for building. You'd have to bundle to libe and all the lib's dependencies in the click. You might have to hack and recompile any libs which have hardcoded paths which don't match the click confinement/directory structure. It might all work easily, or it might all be a nightmare. SDL2 was fairly straightforward, but I suspect gtk3 will be trickier
[13:22] <mcphail> One of the joys of porting to Ubuntu Touch is being a pioneer ;)
[13:53] <Davidrnd> mcphail: :-) .. Thanks
[14:01] <dobey> matv2: well, some parts are going to be "hard" no matter what, but one won't need to provide their own system-image server to be able to flash with standard tools or provide OTA updates. the snaps with the kernel and android bits (not sure if those will be one snap or two) can just be published in the store, and then the default install config for standard ubuntu image can be tweaked to pull in those device-specific snaps to f
[14:23] <matv2> dobey hi and thanks. Although you were probably hit by max strnglngth of irc messages, i get the drif I think
[14:24] <dobey> matv2: what was the last word you saw?
[14:24] <matv2> snap to f
[14:24] <matv2> sorry snaps to f
[14:25] <dobey> snaps to  flash; after the initial flash, all updates are done via snapd
[14:27] <matv2> dobey right thanks again
[14:27] <dobey> matv2: i think the main parts there of "easier" are that stuff will be snaps in the store, and one ideally shouldn't have to fuss about building android system.img stuff
[14:28] <matv2> dobey keyword being ideally :)
[14:29] <dobey> matv2: right; but that's basically why i expect stuff to get a bit easier
[14:29] <dobey> hopefully whoever ends up building those bits will think similarly :)
[14:31] <matv2> dobey haha I will be watching to see whose lap that lands in then
[14:33] <matv2> thing is, regarding that whole so-called discussion on the deadness level of ubuntu phone, looking back I found that hw/device enablement has overall taken much longer then i guess you all expected it to take.
[14:35] <matv2> which i assume can be followed back to the area of hybris/libhybris and the way the higher levels deal with those
[14:35] <matv2> and the difficulty in that isnt going to change much right
[14:37] <dobey> matv2: generally i think hybris is only really a problem when trying to support newer versions of the android base system; since those bits shouldn't "break" from device to device really, on the same version of android.
[14:39] <jgdx> is it possible to flash m10 with > 102 now?
[14:39] <dobey> matv2: for retail devices, there were also different partitioning schemes between android and ubuntu; but mako and other community supported devices don't change partitioning, so a lot of times kernel size issues get hit when porting
[14:56] <matv2> dobey right. going to digest all this again. cheers. And as one famous austrian said: I'll be back
[14:56] <matv2> probably
[15:18] <Davidrnd> btw, i've heard about the "new" UbuntuPhone Meizu MX6. Is there anything news ? ( http://www.omgubuntu.co.uk/2016/07/meizu-mx6-official-announcement-specs )
[15:39] <Davidrnd> Is there a possibility to use the ubuntu sdk just as a cross-compiling suite ? Just like buildroot to create a build enviroment for the ubuntu touch os ?
[15:46] <dobey> sure
[15:49] <matv2> Davidrnd That MX6 is not going to happen. That much is sure. Apparently the Canonicals CEO did shed some light on why that was in a Q&A after her keynote at the recent Ubucon Europe in Germany. I didnt attend that day so not sure. but overall the point is moot. Official communication is that there are not going to be new devices until we have a fully Snapped version of Ubuntu.
[15:49] <Davidrnd> Is there an example / howto ? ( I want to use Codelite as primary IDE ) :-).
[15:49] <Davidrnd> matv2: Thanks for the info :-(
[15:51] <dobey> i don't know anything about codelite
[15:53] <Davidrnd> Codelite uses gcc .. i just don't want to use QTCreator :-)
[15:54] <dobey> then don't :)
[15:54]  * dobey uses emacs
[15:58] <Davidrnd> :-) nice. OK I will take another look at the SDK. btw: is there any manual/howto how to create/use the cross compile enviroment ?
[16:20] <dobey> Davidrnd: not sure. also, app devel questions might be bettere asked in #ubuntu-app-devel :)
[18:26] <mcphail> Davidrnd: https://developer.ubuntu.com/en/blog/2015/04/13/inner-workings-sdk/ is a very useful blog post if you want to set up cross-compilation outside the SDK
[23:01] <Robert_Zenz> Can I rollback the latest system update? Or downgrade to a specific OTA version?