**** BEGIN LOGGING AT Mon Mar 07 02:59:58 2016
Mar 07 05:56:22 <Herrie> elvispre/Tofe: The not booting can be due to mismatch of libhybris and qt5-qpa-hwcomposer-plugin
Mar 07 05:56:42 <Herrie> Libhybris was bumped already, Tofe still wanted to test the qt5-qpa-hwcomposer-plugin first
Mar 07 05:59:14 <Herrie> morphis: morning
Mar 07 05:59:23 <morphis> Herrie: morning!
Mar 07 06:01:03 <Herrie> morphis: Got the modules loaded now for pulseaudio, but now we cannot seem to connect to the headsets :P
Mar 07 06:02:24 <Herrie> I see this in the logs when trying to connect from Settings app, which worked OK without the PA modules: https://bpaste.net/show/85d3b59fbaef
Mar 07 06:03:12 <morphis> Herrie: sure, as now bluez is talking with pulse to setup A2DP :-)
Mar 07 06:03:16 <morphis> so it must fail
Mar 07 06:03:27 <morphis> when the necessary configuration files are not in place
Mar 07 06:03:32 <morphis> this is now a dbus policy thing
Mar 07 06:03:50 <Herrie> morphis: Ah, so we need to give some more access somewhere/
Mar 07 06:03:51 <Herrie> ?
Mar 07 06:03:57 <morphis> yes
Mar 07 06:04:09 <Herrie> Also we have 4 module files on device now, but the list only shows 3
Mar 07 06:04:13 <morphis> Herrie: basiacally a Connect() call to bluez will try to connect all available profiles
Mar 07 06:04:27 <morphis> if one of those fail to connect the whole call fails
Mar 07 06:04:35 <morphis> and you know have additional support for A2DP
Mar 07 06:04:48 <morphis> Herrie: which list?
Mar 07 06:05:01 <Herrie> morphis the pa list modules one
Mar 07 06:05:18 <morphis> which ones are listed?
Mar 07 06:06:27 <Herrie> We added module-bluetooth-device, module-bluetooth-discover, module-bluez4-device and module-bluez4-discover. I read in PA 5.0 release notes that the first 2 can work with either bluez4 or bluez5 modules. module-bluez4-device is missing currently from the list of loaded modules
Mar 07 06:07:11 <Herrie> This is what we have now: https://bpaste.net/show/abde9d3803b6
Mar 07 06:11:49 <Herrie> morphis: We need this? https://wiki.archlinux.org/index.php/Bluetooth_headset#.2Fetc.2Fdbus-1.2Fsystem.d.2Fbluetooth.conf
Mar 07 06:12:17 <morphis> Herrie: the list is fine
Mar 07 06:12:28 <morphis> you only get the -device one loaded when you have a BT device connected
Mar 07 06:12:37 <morphis> means its loaded on demand, that is what the discover module does
Mar 07 06:13:00 <morphis> Herrie: looks good
Mar 07 06:13:08 <Herrie> morphis: Already figured it might be something like that
Mar 07 06:13:56 <morphis> good :-)
Mar 07 06:16:04 <Herrie> So we need those additional lines in bluetooth.conf? We currently have a very small one: https://bpaste.net/show/1f49d63394a1
Mar 07 06:36:10 <morphis> Herrie: yeah, try with an extended one
Mar 07 06:36:36 <Herrie> morphis: SAme problem
Mar 07 06:36:44 <morphis> Herrie: did you reboot?
Mar 07 06:36:46 <Herrie> Could that be due to the root user problem they mention?
Mar 07 06:36:48 <Herrie> morphis: Yeah
Mar 07 06:36:56 <Herrie> Since their example is for desktop
Mar 07 06:37:01 <morphis> Herrie: we're running both bluez and pulse as root afaik
Mar 07 06:37:04 <Herrie> Might be different with our setup?
Mar 07 06:41:59 <Herrie> Trying something else as per https://community.freescale.com/docs/DOC-103385 see if that works
Mar 07 06:42:27 <Herrie> We also get warnings that PA is running in system mode. Is that desired? From what I've read we have to right?
Mar 07 06:49:05 <morphis> Herrie: yes, we have to
Mar 07 06:49:13 <morphis> we don't have a session based system
Mar 07 06:49:18 <morphis> nor webOS never had
Mar 07 06:51:43 <Herrie> morphis: OK that's what I understood as well by reading the documents.
Mar 07 06:51:56 <Herrie> Still the same error though :S
Mar 07 06:52:51 <morphis> Herrie: http://paste.ubuntu.com/15319502/ is what we have on Ubuntu
Mar 07 06:54:11 <Herrie> Let me just try that
Mar 07 06:55:44 <Herrie> Don't we need to modify the pulseaudio-system.conf too?
Mar 07 06:55:56 <Herrie> I see that being done elsewhere
Mar 07 07:31:44 <elvispre3> Tofe,Herrie: For the record, my overnight clean build booted fine.
Mar 07 08:04:11 <Tofe> Morning!
Mar 07 08:05:25 <Tofe> Herrie: ah yes, I forgot: the qpa PR is fine :)
Mar 07 08:05:39 <ka6sox> morning Tofe
Mar 07 08:06:14 <Tofe> morning ka6sox !
Mar 07 08:06:57 <ka6sox> things are looking nice...i'm retiring my N4 from daily driver and going to start playing/testing latest LuneOS :)
Mar 07 08:09:03 <Tofe> :) yes, it feels like things are nicely working together at last
Mar 07 08:09:36 <Tofe> still a lot to do, as ever, but nevertheless :)
Mar 07 08:09:55 <ka6sox> it looks very nice on my TP
Mar 07 08:10:10 <ka6sox> I'm still looking forward to using it as a phone :)
Mar 07 08:11:17 <Tofe> We've done big improvements in that area lately, I'm nearly at the step where I will use LuneOS to order pizzas :p
Mar 07 08:12:30 <Tofe> But I don't think it's reliable enough yet, we didn't test it much outside of some local tests
Mar 07 08:13:40 <ka6sox> w00h00
Mar 07 08:23:31 <Herrie|Veer> ka6sox: We're currently working on getting bluetooth working and we'll need some work on the audio service, then it will be pretty OK to make calls :P
Mar 07 08:23:41 <Herrie|Veer> SMS also works pretty well :)
Mar 07 08:23:50 <Herrie|Veer> Just need polishing here and there.
Mar 07 08:24:46 <ka6sox> seems like nice progress all around.
Mar 07 08:26:18 <Herrie|Veer> ka6sox: Yeah :) We just have the device locking up after a while which is most likely due to Qt's DBUS implementation. This has been completely reworked in Qt 5.6 so we hope that will disappear once we upgrade :)
Mar 07 08:30:47 <ka6sox> Herrie|Veer, this is N4?
Mar 07 08:31:11 <Herrie|Veer> ka6sox: Yeah
Mar 07 08:31:18 <Herrie|Veer> Well all targets in general.
Mar 07 08:31:35 <ka6sox> I htnk I am running 1 rev back currently on TP
Mar 07 08:31:37 <Herrie|Veer> Tofe debugged a bit and came to the same errors as Qt guys reported.
Mar 07 08:31:49 <Herrie|Veer> ka6sox: It's been around for a while.
Mar 07 08:31:51 <ka6sox> whoops..well at least known
Mar 07 08:31:57 <ka6sox> okay
Mar 07 08:34:37 <Herrie|Veer> Probably since QT 5.2 or so... Tofe's been looking into upgrading to 5.6 but there are still some issues.
Mar 07 09:03:29 <Tofe> Well, mainly only one issue, but as it makes luna-next crash, it's a bit of a blocking point
Mar 07 09:42:46 <Tofe> JaMa: is jethro going to have Qt 5.6 for sure?
Mar 07 09:43:42 <JaMa> for sure not
Mar 07 09:43:52 <JaMa> meta-qt5/jethro will stay on 5.5*
Mar 07 09:44:28 <Tofe> ok; so the two migrations will be uncoupled
Mar 07 09:47:06 <JaMa> ?
Mar 07 09:48:00 <JaMa> ah I think I understand nwo
Mar 07 09:48:10 <JaMa> yes, first upgrade everything to jethro branches
Mar 07 09:48:20 <JaMa> then add meta-qt5/master to jethro based builds
Mar 07 09:48:28 <JaMa> to introduce Qt 5.6
Mar 07 09:58:37 <Tofe> yep
Mar 07 10:17:44 <Herrie|Veer> JaMa: meta-qt5/master should be equal more or less to a Jethro successor which we don't seem to have yet, right?
Mar 07 10:18:27 <Herrie|Veer> And which would then have 5.6 as well?
Mar 07 10:40:02 <JaMa> yes master will be eventually branched for Yocto 2.1
Mar 07 10:47:16 <Herrie|Veer> JaMa: You saw the errors in unstable? For the qtscenegraph you might need Tofe's fix
Mar 07 10:48:07 <JaMa> yes, I'm fixing other issues in initramfs image and pulseaudio
Mar 07 10:49:19 <Herrie|Veer> OK :)
Mar 07 10:49:38 <Tofe> Herrie|Veer, JaMa: the fix could also very well be added to testing, as it is also compatible with Qt < 5.6
Mar 07 10:51:17 <JaMa> ok, I've added it only to master branch for now
Mar 07 10:51:25 <JaMa> please add it to fido when you see fit
Mar 07 16:05:20 <JaMa> Herrie: http://build.webos-ports.org/luneos-unstable/images/mako/ latest image is built with Yocto 2.1
Mar 07 16:16:30 <Herrie|Veer> JaMa: Will give that a go tonight. Yocto 2.1 doesn't have a codename yet?
Mar 07 16:21:39 <Herrie|Veer> JaMa: You expect any improvement or just lucky shot?
Mar 07 16:26:40 <JaMa> doesn't have codename yet and only lucky shot
Mar 07 16:27:13 <Herrie|Veer> OK :) I don't expect my N4 to go up in smoke, so it's worth a try :)
Mar 07 17:51:14 <Herrie> JaMa: Flashing unstable
Mar 07 18:07:54 <Herrie> JaMa: Same result. I'll try to see if I can debug somehow
Mar 07 18:08:13 <JaMa> ok, thanks for test
Mar 07 18:08:36 <Herrie> What you think causes it? New compiler version?
Mar 07 18:08:45 <JaMa> possibly
Mar 07 18:08:59 <Herrie> GCC we're using right?
Mar 07 18:09:06 <JaMa> each MACHINE has different kernel
Mar 07 18:09:17 <JaMa> and each kernel needed 3-5 fixes to even build with gcc 5
Mar 07 18:09:20 <Herrie> JaMa: Yeah I know. For Fido we use GCC 4.8 right?
Mar 07 18:09:35 <JaMa> 4.8 or 4.9 I don't remember
Mar 07 18:09:52 <JaMa> Jethro has 5.2, master has 5.3
Mar 07 18:10:04 <Herrie> OK
Mar 07 18:24:30 <Herrie> JaMa: Seems Google itself is still using 4.6 on it's site :S
Mar 07 20:38:50 <Andolamin> Herrie: ping
Mar 07 20:52:33 <Herrie|2> Andolamin: pong
Mar 07 20:53:07 <Andolamin> Herrie|2: Mako, maguro, grouper, tenderloin, qemu - Builds are all working and running, right?
Mar 07 20:53:25 <Andolamin> testing branch
Mar 07 20:53:30 <Herrie|2> Andolamin: yup
Mar 07 20:53:48 <Herrie|2> Though I didn't test with latest few changes
Mar 07 20:53:57 <Herrie|2> Latest nightly is few days old
Mar 07 20:54:29 <Andolamin> OK - merged my layer updates into master. Tested and Pi 2 build works great. Will build for all the above mentioned devices, but can't test grouper myself as I don't have a device. Can you help with that?
Mar 07 20:55:12 <Herrie|2> I also don't have grouper
Mar 07 20:55:21 <Herrie|2> Nobody here has it seems :-P
Mar 07 20:56:04 <Andolamin> Oh - well, I'll just ignore it then.
Mar 07 20:56:18 <Andolamin> Will save quite a bit of time if I skip that build
Mar 07 20:58:53 <Andolamin> Also, http://webos-ports.org/wiki/Template:Device_RaspberryPi2 and http://webos-ports.org/wiki/Template:Device_RaspberryPi3, seems I don't have permission to create those pages.
Mar 07 20:59:46 <Herrie|2> Andolamin: Let me sort your access
Mar 07 21:06:15 <Herrie> What's your wiki username?
Mar 07 21:06:26 <Andolamin> Andolamin
Mar 07 21:06:31 <Andolamin> http://webos-ports.org/wiki/User:Andolamin
Mar 07 21:07:22 <Herrie> Can you try again?
Mar 07 21:10:01 <Andolamin> Access looks good now
Mar 07 21:10:03 <Andolamin> Thanks!
Mar 07 21:10:25 <Herrie> :)
**** ENDING LOGGING AT Tue Mar 08 02:59:59 2016