[00:39] <UbuntuUser> Hi, I was wondering. I installed ubuntu touch on my Nexus 7 (2013) and now my computer when the tablet is in bootloader mode won't detect it. I wanted to possibly reinstall and see if some of the buggy features are fixed.
[00:39] <UbuntuUser> Are there any solutions that can help an ubuntu desktop or any other distro detect it in adb?
[01:02] <dobey> UbuntuUser: when in bootloader adb is not used. you need to boot into recovery or live system with dev mode enabled, instead, to get adb
[01:03] <UbuntuUser> I tried developer mode but, nothing is detected
[01:04] <UbuntuUser> can you reflash android from recovery mode?
[01:07] <UbuntuUser> like the Music app crashes constantly, theres no volume control in the ubuntu touch. I'd kinda like to either reflash ubuntu or android and try a different version.
[01:11] <dobey> yes
[01:11] <dobey> you can reflash in bootloater too, but doing so will erase all user data on the device (if you're ok with that)
[01:11] <dobey> which i guess you are if android is an option there
[01:12] <dobey> well you have to flash android from the bootloader (at least, the stock android image)
[01:12] <dobey> but --bootstrap option will flash while in bootloader, and erase all user data too
[01:12] <dobey> (for ubuntu-device-flash)
[01:13] <dobey> there could also be an issue with the usb cable or the port it's connected to (or the port on the device itself), as well, if it doesn't even show up in dmesg output for example
[01:20] <UbuntuUser> why does it show up with lsusb and fastboot then?
[01:22] <UbuntuUser> it does show up in dmesg too
[01:22] <UbuntuUser> but, when I use adb in dev mode or bootloader mode. I get nothing.
[01:23] <UbuntuUser> [ 1148.427550] usb 1-1: Manufacturer: Google [ 1148.427553] usb 1-1: SerialNumber: 05b28bde [ 1519.014705] wlp2s0: AP ac:22:0b:7c:6f:c8 changed bandwidth, new config is 2422 MHz, width 1 (2422/0 MHz)
[01:23] <UbuntuUser> Hmm /Desktop# adb devices List of devices attached
[01:49] <dobey> there is no adb in bootloader
[01:49] <dobey> if you're in bootloader try "fastboot devices" to see it
[01:50] <dobey> in dev mode, it has to be enabled and the screen unlocked. if it doesn't show up then, maybe a bug, or maybe some other problem
[02:57] <UbuntuUser> welp dobey
[02:57] <UbuntuUser> I reflashed it and I got back my volume control
[02:57] <UbuntuUser> thank you very much
[02:58] <UbuntuUser> (:
[02:58] <UbuntuUser> I also learned that you could flash from recovery
[02:59] <UbuntuUser> Was sweating bullets there for a minute or two (not going to lie, I've never done this before). I thought it was going to brick.
[03:02] <dobey> :)
=== JoseeAntonioR is now known as jose
=== durksauce_ is now known as durksauce
=== KCinJP_ is now known as KCinJP
=== petevg_ is now known as petevg
=== Namidairo_ is now known as Namidairo
=== ulkesh_ is now known as ulkesh
=== chihchun_afk is now known as chihchun
=== saidinesh is now known as saidinesh5
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== ecloud is now known as ecloud_wfh
=== enthusi_ is now known as enthusi
[08:57] <mardy> morphis: hi! Any news about bug 1658617?
[08:57] <ubot5> bug 1658617 in Ubuntu App Platform "webapps crashing - oxide being compiled with wrong libs?" [Undecided,New] https://launchpad.net/bugs/1658617
[09:03] <morphis> mardy: hey!
[09:03] <morphis> mardy: not really, but there is a quick workaround you can try without us changing libhybris
[09:03] <mardy> morphis: oh! I'm all ears :-)
[09:04] <morphis> auto ptr = android_dlopen("libcamera_compat_layer.so", RTLD_LAZY);
[09:04] <morphis> that should return nullptr when the library isn't available
[09:05] <mardy> morphis: mmm... now it's a matter of deciding whether it's easier to rebuild oxide, or wait for libhybris :-)
[09:05] <morphis> hah :-)
[09:05] <morphis> is that such a big issue?
[09:05] <mardy> morphis: do you have an approximate ETA?
[09:05] <morphis> not really
[09:06] <mardy> morphis: well, many webapps are not working, and some important ones, such as gmail and google+
[09:06] <morphis> I am full with a lot of other work items but what is this blocking?
[09:06] <mardy> morphis: liuxg has also written another one for an important chinese website
[09:06] <morphis> the bug doesn't give much information nor does it link to any milestone
[09:07] <mardy> morphis: it's hard for me to tell how urgent this is, I guess that at the moment no one is using these webapps, but...
[09:08] <morphis> is this just for the snap variant?
[09:08] <morphis> or does this happen on desktop in general?
[09:08] <mardy> morphis: I'll ping you back in a while, when dbarth get online; he will tell
[09:08] <morphis> mardy: "I should point out, this runtime check does work fine on a standard desktop install."
[09:08] <mardy> morphis: I have been seeing it only on the snaps, but it's also because it'e the only way I've been using oxide on the desktop, so that doesn't tell much
[09:09] <Guest0815> hello
[09:09] <davmor2> Guest0815: hello
[09:10] <morphis> mardy: "the check on whether to use libhybris is done at run-time" -> can you point me to the relevant code part in oxide for this?
[09:10] <Guest0815> sorry, i have to leave due to real world
[09:13] <mardy> morphis: I just tried webbrowser app (as a deb) on xenial, and it doesn't crash -- but it's using an older version of oxide, so maybe things are different there
[10:23] <mardy> dbarth: hi! We were wondering with morphis how urgent bug 1658617 is
[10:23] <ubot5> bug 1658617 in Ubuntu App Platform "webapps crashing - oxide being compiled with wrong libs?" [Undecided,New] https://launchpad.net/bugs/1658617
[10:23] <mardy> dbarth: it affects gmail, google+ and a webapp by liuxg (taobao)
=== marcusto_ is now known as marcustomlinson
=== chihchun is now known as chihchun_afk
=== sergiusens_ is now known as sergiusens
=== _salem is now known as salem_
[12:20] <jim__> Hi,I have experienced the broken wifi problem with Ubuntu 16.04. Was working for past 6 Months prior to yesterday, is there a fix yet?
[12:23] <brunch875_> jim__, are you talking about ubuntu-touch? I thought we were still on vivid
[12:24] <jim__> No , maybe I am on wrong forum. Just standard 16.04 Laptop
[12:24] <ogra_> jim__, try #ubuntu then
[12:25] <jim__> ok thank you..
=== chihchun_afk is now known as chihchun
=== alan_g is now known as alan_g|lunch
=== Ubport-user|4108 is now known as biraj
=== alan_g|lunch is now known as alan_g
[14:16] <ayib29> indonesia version
=== JanC_ is now known as JanC
=== chihchun is now known as chihchun_afk
=== jdstrand_ is now known as jdstrand
[18:52] <mterry> tedg_: are UAL tests passing in trunk for you?
[19:12] <dobey> mterry: libertine ones were failing until ken's silo lands, i think
[19:12] <dobey> a libertine landing caused that to break
[19:14] <mterry> ah yes lp:~ted/ubuntu-app-launch/libertine-service seems to be that branch
[19:14]  * mterry tries
[19:25] <mterry> Hmm, that looks like it fixes some...   /me deep dives into other branches
[19:26] <dobey> mterry: what others are failing?
[19:26] <dobey> i guess some might still be flaky otherwise, but should in general be passing
[19:26] <mterry> Well the toplevel notice is
[19:26] <mterry> 	 14 - libual-cpp-test (Failed)
[19:26] <mterry> 	 18 - list-apps (Failed)
[19:26] <mterry> 	 24 - exec-util-test (Failed)
[19:26] <mterry> I don't have a full list of internal ones that fail
[19:27]  * mterry retries, sees what goes away
[19:27] <dobey> hmm
[19:30] <mterry> I'm building on xenial+overlay, maybe that affects it
[19:30] <tedg_> mterry: I can build that branch on x+o and the tests pass
[19:30] <tedg_> mterry: You'll need libertine >= 1.6
[19:31] <dobey> mterry: nah. the tests have to pass in launchpad builders to land in the overlay and on zesty, so they at least passed at that point
[19:31] <mterry> tedg_: I have libertine 1.6 from the overlay
[19:31] <dobey> mterry: are you just doing "make test" there?
[19:32] <mterry> tedg_: the CI for your branch didn't pass
[19:32] <mterry> dobey: debuild
[19:34] <dobey> mterry: ah. it should print out the errors for the failed tests then, above that listing you pasted. could be a LOT of debug info printed too though
[19:34] <mterry> Oh there is
[19:34] <mterry> Seems to be libertine errors...
[19:34] <tedg_> mterry: Are you doing it in an sbuild?
[19:34] <mterry> no
[19:34] <tedg_> mterry: If so you'll need kenvandine libertine fixes
[19:35] <tedg_> mterry: Oh, you'll need the liblibertine patch no matter what.
[19:35] <dobey> ?
[19:35] <tedg_> mterry: https://bileto.ubuntu.com/#/ticket/2405
[19:35] <tedg_> mterry: liblibertine uses QtDBus as per the docs, which is broken. So we had to fix it.
[19:36] <mterry> tedg_: ah ok will try with that silo, thanks
[19:36] <dobey> tedg_: oh is that why the tests hanged?
[19:36] <dobey> 17:42:45 E: Build killed with signal TERM after 150 minutes of inactivity
[19:36] <kenvandine> dobey, that was actually a missing depends in libertine
[19:37] <tedg_> dobey: Yup, dbus connection singletons
[19:37] <kenvandine> partially
[19:37] <tedg_> kenvandine: Different hang :-)
[19:37] <kenvandine> once ted fixed the dbus issue it uncovered the depends that caused the hang
[19:37] <kenvandine> it was like peeling an onion :)
[19:37] <kenvandine> i'm still not sure why the missing depends caused a hang... it should have just blown up
[19:37] <tedg_> But we fried that onion and made onion rings!
[19:38] <kenvandine> yum
[19:38] <dobey> what was the missing depends?
[19:39] <tedg_> kenvandine: The test is waiting for the service to start, but also ignoring it for determining if it fails or not (we don't care about the return of libertine service). So that creates a situation where we'll wait forever. Need to fix that, but not a priority for getting this out.
[19:39] <kenvandine> so ted's fault :)
[19:39] <dobey> usually is :)
[19:39] <kenvandine> dobey, some python depends that didn't get moved from libertine-tools to python3-libertine like they should have
[19:40] <dobey> ah
[19:40] <kenvandine> dobey, it's been fun :)
=== salem_ is now known as _salem