[01:14] <Rjones> hello
[01:15] <Rjones> hi there!
[01:15] <learnbsd> Rjones: hi
[02:09] <bregma> muka, if an X11 app running in libertine was designed to zoom in/out, then you can zoom in/out with it
[02:09] <bregma> but there is nothing in the Unity 8 shell at the moment that will allow you to zoom in/out on arbitrary windows
[02:22] <duflu> bregma: Super+wheel/two-fingers in mir_proving_server. I still think that feature should be moved into common Mir and USC... just as soon as the required cursor support is done for Unity8
[02:26] <bregma> there's still plenty of a11y functionality on the list of things to be added to Unity 8, they're pedalling as fast as they can
[06:41] <MrChrisDruif> Hey guys, can someone tell me if the GPS is indeed broken on the OnePlus One built of Ubuntu Touch as mentioned in this link? https://devices.ubports.com/#/bacon
[06:42] <MrChrisDruif> #AintNobodyGotTimeToFlashAndTestThemselves
[07:19] <mardy> t1mp: hi! Unless you think you'll be able to fix bug 1617745 by OTA-13, you might want to send a message to the ML to warn developers to check their apps
[08:15] <t1mp> kalikiana: ^ do you want to comment on that bug? I see you change a debug() call to a warn().
[08:16] <kalikiana> Not sure how debug/warn is related, but taking a look
[08:21] <kalikiana> mardy: Can you be more specific what "doesn't work"?
[08:22] <mardy> kalikiana: it's not about the warning, but about the fact that the attached test case doesn't work anymore
[08:23] <kalikiana> mardy: There is no attached test case :-)
[08:23] <mardy> kalikiana: oops, lemme check
[08:25] <mardy> kalikiana: you are right, let me quickly write one...
[09:09] <mardy> kalikiana: added a test case to bug 1617745
[09:26] <rvr> dpm: ping
[09:38] <dpm> hi rvr
[09:38] <kalikiana> mardy: Did you always use a Window as a root item? I'm not sure that worked before
[09:39] <mardy> kalikiana: mmm, let me check, when I introduced it...
[09:39] <kalikiana> So I'm still investigating why this breaks it, but it's not a regression from my pov
[09:41] <rvr> dpm: Hi
[09:41] <rvr> dpm: So I think that sil2100 needs at least indicator-keyboard in the ubuntu-15.04/rtm series
[09:42] <mardy> kalikiana: you might be right, I don't think that the released version of my app is using Window
[09:43] <mardy> kalikiana: and indeed, then it wouldn't be a regression
[09:44] <dpm> rvr, ok, let me have a look at LP and see if the template needs approving, give me a few minutes
[09:45] <rvr> dpm: Ack
[09:45] <sil2100> dpm, rvr: thanks! I don't know enough of the LP-side-of-things internals, but I'd need indicator-keyboard visible in the ubuntu-rtm/15.04 exports
[09:49] <gb_mks> hi! I found a bug related in the package "click-review" related with Ubuntu-Trisquel. Can anyone help me to solve it? https://bugs.launchpad.net/click-reviewers-tools/+bug/1617288
[09:56] <dpm> rvr, sil2100, the template is there, but unfortunately I can't approve it as LP gives me a timeout error every time I try it :/ https://translations.launchpad.net/ubuntu-rtm/15.04/+source/indicator-keyboard/+imports?field.filter_status=all&field.filter_extension=pot
[09:56] <rvr> dpm: :(
[09:56] <dpm> rvr, ah, managed to get it approved after a few tries
[09:56] <rvr> Wee!
[10:01] <dpm> rvr, sil2100, https://translations.launchpad.net/ubuntu-rtm/15.04/+source/indicator-keyboard. The translations should be included in the next LP export and then added to the language packs if all goes well
[10:01] <rvr> dpm: Great, thanks you!
[10:01] <dpm> np
[10:03] <sil2100> \o/
[10:03] <sil2100> dpm: excellent, thank you!
[10:15] <matv1> during the weekend I installed rc-proposed in my Frieza. loving lots except that Libertine apps would cause a graphics freeze everytime i tried them. Didnt matter which.
[10:15] <matv1> Usualy it would take anything between a few minutes and a max of 10 minutes.
[10:16] <matv1> just having them open would be enough
[10:16] <matv1> as I said a graphics freeze so I assume a MIR thing?
[10:18] <matv1> is anyone able to confirm this is the case?
[10:19] <matv1> Also I discovered that the particular rc-prop image i went with wasnt as up to date as i expected.
[10:19] <matv1> its rc-proposed/ubuntu-pd
[10:20] <matv1> So it might be that this is already known and fixed.
[10:20] <matv1> Can anyone shed light?
[10:21] <gb_mks> hi, I´m trying to "build and validate" an app but I´m having issues with the bug #1617288.
[10:21] <gb_mks> I wrote one of the developers of the package https://launchpad.net/click-reviewers-tools
[10:21] <gb_mks> Is this a good practice?
[10:24] <Soelen> hello everyone, can anyone help me out? I am trying to flash a bq aquaris e5 device with the latest ubuntu phone os
[10:24] <Soelen> https://github.com/bq/aquaris-E5/tree/aquaris-E5-ubuntu-master
[10:25] <Soelen> unfortunatly when I do fastboot boot boot.img the < waiting for device > message seems never to go away
[10:25] <Soelen> when I do adb devices I dont see my devices listed there
[10:26] <Soelen> when I do dmesg | grep -i usb I can see that the devices has been connected successfully, I guess "[68930.280122] usb 2-3: New USB device found, idVendor=2a47, idProduct=2008"
[10:27] <Soelen> last but not least when I do lsusb -v | grep ID I see the devices being there but I think with no vendor attached to it? "Bus 002 Device 006: ID 2a47:2008"
[11:07] <MrChrisDruif> Soelen: is your device in fastboot mode?
[11:11] <Soelen> MrChrisDruif: how do I check that?
[11:11] <MrChrisDruif> If you can use your device normally it isn't in fastboot mode
[11:12] <Soelen> what do you mean with use your device normally?
[11:13] <mcphail> Soelen: I don't know what way you are flashing your device, but it doesn't sound like the "correct" way. Do you currently have Ubuntu or Android on the phone?
[11:13] <MrChrisDruif> On Android devices you have to hold the power and volume up button simultaneously during boot to go into fastboot mode
[11:14] <Soelen> mcphail: it has android on it
[11:14] <Soelen> MrChrisDruif: gotcha, I will try that!
[11:14] <mcphail> Soelen: then you'll probably need to bq tool to reflash it
[11:19] <mcphail> http://www.mibqyyo.com/en-articles/2015/09/16/ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5
[11:21] <Soelen> ah thank you
[11:22] <Soelen> haha
[11:23] <Soelen> my spanish isnt really fluent but I think I found the link
[11:23] <mcphail> You'll need the flash tool and the OTA12 image
[11:24] <mcphail> IIRC, when you extract the flash tool archive, you need to move it into a directory without spaces in the path, or the script breaks
[11:25] <Soelen> mcphail: ok, but
[11:25] <Soelen> I only see windows executables in this zip file
[11:27] <mcphail> Soelen: nope. script is there. Follow the instructions on that page _exactly_ or you may end up with a brick
[11:27] <ogra_> you need to do this only once though, to get the correct partitioning ...
[11:28] <ogra_> if you re-flash ubuntu on a properly partitioned phone you can just user ubuntu-device-flash then
[11:28] <ogra_> *use
[11:28] <mcphail> ogra_: Unless he is fickle like me, and flip-flops between Ubuntu and Android ;)
[11:28] <Soelen> heh
[11:28] <ogra_> yeah, then the MTK tool is your best friend (or you just buy a nexus4 )
[11:29] <Soelen> https://storage.googleapis.com/otas/Tools%26Drivers/Drivers_Tools.rar
[11:29] <Soelen> so I am downloading this rar file, and the flash_tool doesnt seem to be in there
[11:30] <mcphail> https://storage.googleapis.com/otas/2015/Tablets/Freezer%20FHD/Ubuntu/SP_Flash_Tool_exe_Linux_v5.1612.00.100.zip
[11:30] <mcphail> That's the link I get
[11:39] <Soelen> BROM ERROR : S_DA_SDMMC_CONFIG_FAILED (3152)
[11:40] <Soelen> that is what I get when I do step 5
[11:44] <Soelen> BROM Exception! ( BROM ERROR : S_TIMEOUT (1042)
[11:45] <ogra_> mvo, btw, not sure you have seen https://github.com/snapcore/classic-snap/pull/4
[11:54] <ogra_> bah
[11:54] <ogra_> echan
[12:04] <Soelen> so it started the booting process, how long does this take normally?
[12:06] <matv1> still no one on that Frieza image of mine? ^^
[12:14] <Soelen> it is still booting, is that normal
[12:33] <Soelen> I think the boot process is stuck
[12:33] <Soelen> still booting it
[12:35] <Soelen> it would help if somebody could tell me how long this fastboot process takes its time normally
[12:39] <mcphail> Soelen: it usually takes about 5--15 minutes, in my experience
[12:41] <Soelen> mcphail: thank you, I guess I can assume something went wrong since it is booting this phone for around 35 minutes : /
[12:41] <mcphail> Soelen: yep - that would seem abnormal
[12:42] <mcphail> Soelen: I'd repeat the process, making sure you follow every step carefully. Don't know what those error messages were about, but don't sound healthy
[12:45] <Soelen> mcphail: I disconnected it and it turned out the screen on the smartphoen froze, I guess I will charge it fully before I try this again
[12:45] <Soelen> charge the battery*
[12:45] <Soelen> also I was sitll able to boot up android so I guess it didnt flashed anything
[12:46] <mcphail> Soelen: sounds like it
[12:46] <Soelen> also also, I used a boot.img which I compiled it, sources from there: https://github.com/bq/aquaris-E5/tree/aquaris-E5-ubuntu-master
[12:46]  * mcphail see bq have released Android 6 for the e4.5, and might be running the flash tool again to experiment
[12:48]  * mcphail sees it is actually for M4.5 and contains his excitement
[13:34] <dobey> pitti: hey. can you look at https://requests.ci-train.ubuntu.com/static/britney/last-run.txt and search for "landing-019" in it. seems there's something wrong with the result.tar for the apparmor-easyprof-ubuntu tests
[13:35] <pitti> dobey: robru pointed that out last Friday; apparently apt has slightly changed the format of the Package-List: field, I adjusted autopkgtest this morning
[13:36] <pitti> dobey: i. e. a retry should work
[13:37] <dobey> hmm ok
[14:36] <Soelen> so I tried to install ubuntu touch with sudo ubuntu-device-flash touch --channel ubuntu-touch/stable/bq-aquaris.en --bootstrap --recovery-image recovery.img
[14:37] <Soelen> and it tells me this: Device 1 not found on server https://system-image.ubuntu.com channel ubuntu-touch/stable/bq-aquaris.en
[14:37] <Soelen> so I guess
[14:37] <Soelen> https://www.amazon.de/gp/product/B00KLZB53A
[14:37] <Soelen> this product is not compactible with ubuntu touch?
[14:37] <dobey> !devices Soelen
[14:38] <dobey> it sounds like it has the wrong device identifier
[14:38] <dobey> to use ubuntu-device-flash the device must also be repartitioned
[14:39] <Soelen> how do I do that?
[14:41] <Soelen> dobey:
[14:42] <Soelen> also when you wrote !devices Soelen nothing appeared
[14:42] <dobey> yeah, should have been...
[14:42] <dobey> !devices | Soelen
[14:45] <Soelen> ubot5: so 2 of them are tables, 2 of them are emulators, 2 of them are sold out and 2 of them are linked wrong
[14:45] <Soelen> oh.
[14:45] <Soelen> who would have thought to get an ubuntu phone would be so hard
[14:45] <dobey> the E5 is "vegetahd" for device name
[14:46] <dobey> from scrollback it looks like you managed to mess things up with some other tools
[14:46] <Soelen> I guess so, so what do I do now?
[14:48] <dobey> it sounds like the tool needs to be used to restore the device; given that device appears to be "1" you probably broke the IMEI data too. i don't know exactly what you need to do, though. perhaps bq support can help you?
[18:03] <linmob> I guess the fact that the "Software Updater" app gives wrong timestamps for older updates (it pretends that the updates were done at the same time as the latest update) is a known one? (Nexus 4, rc.proposed 517)
[18:08] <pmcgowan> yes, bug fix in QA
[18:40] <linmob> pmcgowan: Great. Thanks!
[18:50] <barryt> Hello.
[18:53] <linmob> Hello!
[18:54] <barryt> I need a little advice about reporting a bug.
[18:55] <dobey> !ask | barry
[18:55] <dobey> :)
[18:55] <barryt> This is my first time on IRC so please be kind!
[18:56] <barryt> I installed UT on a Nexus 4 16Gb but had trouble connecting to my home wifi. What package should I report this under?
[18:58] <dobey> trouble in what sense exactly? wifi itself just wasn't working right, or you had trouble typing the password, or with the UI?
[19:00] <barryt> My SSID was shown on the list of available networks but it would not connect when I typed in my password. However if I typed the SSID using the 'hidden network' option then it would accept my password and connected succesfully.
[19:01] <dobey> i think i've seen someone else describe that problem recently. or was that you at a different time? (hard to remember everyone :)
[19:01] <barryt> Not me: this is my first time on here.
[19:02] <dobey> ah ok
[19:02] <barryt> Do you know if a bug was filed?
[19:02] <dobey> i'm not certain, would have to look and see
[19:03] <barryt> I could not find anything but I may not have used the correct search criteria.
[19:03] <JanC> barry: does your SSID have special characters in it?
[19:04] <JanC> barryt: I mean
[19:04] <pmcgowan> barryt, are you on the stable channel? A bug with wifi connect timeout was just recently fixed
[19:04] <barryt> No, just letters - all lower case - and numbers.
[19:05] <barryt> Yes, it was the stable channel.
[19:05] <pmcgowan> could be this bug https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126
[19:06] <pmcgowan> sounds like you found a better workaround
[19:06] <barryt> I found that one, but my password is shorter than his limit.
[19:08] <pmcgowan> I think the key in finishing in 25 secs, if you did that could be something else
[19:11] <barryt> It could be the time limit as I have to jump back and forward between text and numbers on the on-screen keyboard which slows me down.
[19:12] <dobey> barryt: do you have an otg cable and a spare keyboard (or a bt keyboard) to test if that's it?
[19:13] <barryt> No I don't.
[19:16] <pmcgowan> barryt, could try copy and paste from another place, but pretty sure thats the issue
[19:17] <barryt> You said earlier that this has been fixed on an upstream channel. Should I just let it go and wait for the OTA update?
[19:19] <pmcgowan> barryt, the fix will go to stable within a couple weeks or you could run rc-proposed
[19:19] <pmcgowan> barryt, but seems you found a good workaround
[19:20] <barryt> I have a work around so I will wait. I shall also try and borrow an otg cable from a friend to see if it is the time out issue.
[19:21] <barryt> Thank you for your help. Bye.
[19:21] <dobey> you're welcome
[19:37] <matv1> i am finding that launching x-apps in desktop mode causes my graphics to freeze up all the time
[19:37] <matv1> is this a known issue?
[19:38] <matv1> in rc proposed
[19:40] <dobey> bregma, ChrisTownsend: ^^
[19:42] <ChrisTownsend> matv1: What device?
[19:43] <matv1> Frieza
[19:43] <ChrisTownsend> matv1: You say desktop mode, do you have it connected to an external monitor?
[19:44] <ChrisTownsend> matv1: I will say, no known issues of X apps freezing up the machine.
[19:44] <matv1> no. I thought this at first. But its just desktop mode that does it. No external screen is needed for this to be triggered
[19:45] <ChrisTownsend> matv1: Hmm, my frieza is on rc-proposed and fully up to date and X apps launch fine in desktop mode, ie, with BT keyboard and mouse.
[19:46] <ChrisTownsend> matv1: Is this all X apps?  And do you have your own custom Libertine container or is it the Desktop Applications container?
[19:46] <matv1> Ah well maybe we are using different images. yesterday I flashed my Frieza to rc-proposed/ubuntu-pd
[19:47] <matv1> but have since found out that this image may be a little beind other rc-prop images
[19:47] <ChrisTownsend> matv1: Ah, no, that won't work and is deprecated.
[19:48] <matv1> ahah but which one should I be running. I was led to believe that bq-aquaris-pd currently has an empty libertine scope is that right?
[19:49] <dobey> err?
[19:50] <matv1> dobey did I misunderstand?
[19:50] <dobey> yes. i said i think it has the empty _puritine_ click (because real one is like 650 MB)
[19:51] <dobey> but either way, unless you didn't have the full one installed already, and didn't --wipe, that's not especially important
[19:52] <matv1> dobey ok so all that means that I wont be able to create new x-apps for myself on the system, correct?
[19:52] <matv1> the ones that are installed with the system are just there and working?
[19:53] <dobey> no. you can still create your own container instead of using the default one
[19:53] <ChrisTownsend> matv1: Yes, there is currently a problem wit hte Libertine Scope in rc-proposed that I'm currently working on.
[19:53] <matv1> ChrisTownsend So how exactly will that limit me?
[19:54] <ChrisTownsend> matv1: The problem being that the Libertine Scope installed on devices and from the Store is built against libubuntu-app-launch2, but that has been removed from the image, so the Libertine Scope fails.
[19:54] <ChrisTownsend> matv1: You can't launch X apps.
[19:54] <dobey> oh that's a click
[19:54] <dobey> fun
[19:54] <ChrisTownsend> dobey: Yes:(
[19:55] <matv1> ok and what if I go back a few revisions on that same channel?
[19:55] <ChrisTownsend> matv1: I'm not sure of the exact revision this showed up, but yes, that is possible.
[19:55] <dobey> matv1: well, depends on what your goal with using that channel is
[19:56] <ChrisTownsend> matv1: You could also run stable and it will work.
[19:56] <dobey> matv1: if it's to get/test something which landed after that point, going back won't really help you much :)
[19:56] <matv1> my aim was to be as current as I can on rc-proposed. on the on the one hand for some goodies that i want to look at coming up in ota 13 . like owncloud plugin
[19:57] <matv1> on the other hand I also definetly want the libertine purtine stuff to work
[19:58] <matv1> but I dont need it to be bleeding edge
[19:58] <ChrisTownsend> I can't publish a new version of the Libertine Scope in the Store yet because if I do, it will break everyone on stable when they update the Libertine Scope package:(
[19:59] <matv1> ChrisTownsend Stable be damned. There is work to be done!
[19:59] <ChrisTownsend> matv1: lol, I wish:)
[19:59] <matv1> just joking. I understand
[19:59] <dobey> ChrisTownsend: you can fix it to resolve that library at runtime, and then work with either one. ;)
[20:00] <dobey> you know you always wanted to write a plug-in system just for loading system libraries
[20:00] <ChrisTownsend> dobey: It's probably possible, but who has time for dat?
[20:02] <matv1> ChrisTownsend dobey so my best would be to try going back a few revisions on bq-aquaris-pd and see if it hold together
[20:04] <matv1> my short experience with libertine apps on stable is that they dont crash but are slower than on rc-proposed (before they crash on me)
[20:04] <ChrisTownsend> matv1: If you feel particularly brave, you can put your device in r/w mode and install libubuntu-app-launch2...but I'm sure others would highly discourage that.
[20:04] <ChrisTownsend> matv1: Also, I think r175 will work.
[20:05] <ChrisTownsend> matv1: r176 and later has this issue I believe.
[20:05] <dobey> i think the problem with that is that the version from the overlay is no longer available
[20:06] <dobey> so if you were able to install libubuntu-app-launch2 it would be ~18 months old
[20:06] <ChrisTownsend> dobey: Oh, rvr stated in the bug that he installed it on his device and it fixed it, so I'm just taking that with a grain of salt.
[20:06] <matv1> ChrisTownsend dobey I am still not that brave :)
[20:07] <ChrisTownsend> matv1: lol, ok, it's not for the faint of heart.
[20:08] <dobey> meh
[20:08] <dobey> it's easier than getting stuff mounted in lxc
[20:08] <matv1> faintness of heart is not my problem. I am trying to put together a short demo for my it department on the system. I want to be as up to date as possible without having the risk of crashing be too big
[20:09] <matv1> but thanks very much both. i will try for rev 175
[20:09] <matv1> have a good evening!
[20:09] <ChrisTownsend> matv1: Ok, you're welcome and good luck!
[20:36] <kaisoz> hi!
[20:54] <learnbsd> kaisoz: hi
[20:55] <MrChrisDruif> Hi