=== chriadam|away is now known as chriadam === chihchun_afk is now known as chihchun === salem_ is now known as _salem [04:19] hi every one [04:19] who can help me? [04:19] i have device tree [04:19] but a cant know [04:19] what file take from android system [04:20] plzzzzzzzzzzzzzzz [04:22] alksfahsfgaqhe ogfhsoaihf efhoaeihf aefo e [04:22] hjc [04:22] k co ai tra loi het tren z tr [04:22] chan thiet chu [05:02] somebody free to answer me [05:13] hey is there a way to turn the touch on and off? [06:26] hi [06:27] well script freeze once that s accomplished [06:27] 292.85 MB / 292.85 MB [==================================] 100.00 % 742.13 KB/s [06:27] 2015/08/13 08:24:54 Start pushing /home/nocomp/.cache/ubuntuimages/pool/ubuntu-dcf6a5e745ce46aff22add18c8cd2f21b4811a62383f857c0f955a74d2ac866a.tar.xz to device === raj` is now known as raj === zyga-afk is now known as zyga [07:02] What's the component to log bugs against for the touch tutorial? (the thing after the setup wizard)? [07:03] Oh actually probably unity8 [07:21] good morning [07:25] bfiller, please finish off bug 1400675 [07:25] bug 1400675 in dialer-app (Ubuntu) "Dialer app has two unsynced bug lists" [Low,In progress] https://launchpad.net/bugs/1400675 [07:34] Hi, bq5 phone related question on ubuntu-touch is there a waz how can I one of the sim cards from operator? (e.g. not receiving calls / SMS and caller would receive NA message from operator) [07:35] and Q #2 can I setup sim card to not send the caller ID when calling / sendind SMS? [07:47] hi alltogether! The two latest devel-proposed versions (277 and 278) are both not booting on nexus 4. Is there any way to re-flash the old version without loosing data? [07:49] seb128, I followed up on bug 1483888 [07:49] bug 1483888 in dialer-app (Ubuntu) "Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones plugged" [Undecided,New] https://launchpad.net/bugs/1483888 [07:49] mpt, hey, thanks [07:50] mpt, it's not only the phone app, the bug also mention that alarms go through the headset, the user failed to be waken up in the morning because of that [07:51] mpt, so maybe affecting indicator-datetime as well (I think it's what handles those events) [07:51] seb128, so “buzzer” is a LOTE term for “alarm”? [07:51] Hmm, I guess so [07:51] Probably should be split into a separate bug report, though [07:53] seb128, aha! I knew I’d commented on something like this before. For alarms it’s bug 1364647. [07:53] bug 1364647 in Ubuntu UX "[System Settings] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used" [Medium,Triaged] https://launchpad.net/bugs/1364647 [07:53] mpt, thanks [08:01] * davidcalle was so happy to see a new devel-proposed image this morning. [08:01] * davidcalle reverts to the previous one [08:05] Hi all, I was trying to import my contacts on my phone via VCF file, but both files and dekko say that there is no application associated with that filetype... [08:05] Meizu MX4 with OTA5 here [08:13] @gvs77 you can use the following: syncevolution --import /path/to/file/allcontacts.vcf backend=evolution-contacts database=Personal [08:20] rsalveti: can you check the comment at https://codereview.qt-project.org/#/c/122936/ and push the same change to 5.5 instead? they'd apparently want it in stable series (from where they'll merge it to dev) [08:25] rsalveti, charles, hey, do you know what component is dealing with how specific sounds event are handled? like where bug #1364647 should be fixed? is that in the service playing the sound? or pulseaudio [08:25] bug 1364647 in pulseaudio (Ubuntu) "Can't hear clock alarm when headphones are plugged in but not in your ears" [High,Confirmed] https://launchpad.net/bugs/1364647 [08:32] Mirv: hi! +1 for silo 29 (also added a comment to the bug) [08:35] hehe: Thanks, that did it! [08:48] Is there any plans to build an android app compatibly layer like Jolla have for Ubuntu phone/touch? [08:49] I have a jolla phone today and the android app support works very well, but i would like to use ubuntu [08:56] Hey, I just figured out how to resize the phone's rootfs in a very evil way. Wondering if anyone has documented this yet (or has a better solution)? [08:56] mardy: thanks a lot! I ran AP:s througout the night, now I think I'll need to do manual testing trying to get listviews breaking + build the gles package, then it'd be ready for QA [08:58] MannerMan: AFAIK no, Ubuntu is more about getting better functioning native apps than offering a compatibility layer for poorly integrated external apps. that doesn't mean some day it wouldn't be possible, if there'll be a free software Android compatibility layer (some are trying this recently again from another angle...). Jolla's Android compatibility is proprietary so that won't happen. [08:59] ogra_: Hey, How dangerous using rc-proposed for daily use? It's not a problem If I can't use some features, can't open an app, and similar things, but I don't want to use it, If I can make a huge mobile invoice thanks to a bug in the rc-proposed channel :) [09:00] where did I see the latest Android effort again.. [09:02] duflu, you need to tell us your solution if you wanna know if people have 'better solutions' ide assume [09:03] i havent really looked at a way to increase its size, i havent looked myself [09:03] ProstheticS: I'd rather not reveal if there's a nice solution already published [09:03] Plus I'm still improving it [09:06] MannerMan: no plan to === chriadam is now known as chriadam|away [09:18] Mirv; popey; Aight, I understand. Too bad the Jolla compatibility aint opensource, it works really well. Perhaps I can manage by dualbooting android and Ubuntu. [09:22] MannerMan: yeah there's quite a lot of work to do for community to come up with Android compatibility layer, so I guess the best would be if Myriad (the vendor of the Jolla's Android compatibility) would decide there's no more business in that area and open source theirs ;) anyway, if Android retains the current market share and we don't get to post-app era, there'll be incentive for people to develop s [09:22] uch for the random airliner app etc [09:23] but for the community to do the development, I think it requires a certain mindshare of the hackers to stay using Jolla, Ubuntu, Tizen, FirefoxOS, whatever alternatives... hopefully that'll be like that [09:23] i doubt there is duflu(another solution) , been too busy messing with other gear since i got this, with what time ive had to put to messing wiht the thing [09:23] Mirv: pretty unlikely (open sourcing); did you notice shashlik though? [09:23] though i am interested in increasing its storage [09:23] * duflu is working on an official answer [09:23] Mirv: That would be so awesome, it they could create something together to benefit them all :) [09:23] Stskeeps: ah, that was it! thanks! very interesting. [09:30] ProstheticS: http://askubuntu.com/questions/514913/how-to-get-a-larger-root-partition-on-touch [10:10] shrug [10:10] dpm, did you change the ubuntu-system-settings translation setup to enable sharing with upstream again? [10:11] seb128, not that I know of [10:11] k [10:11] I think translators complained that the stats were pointing to the wrong project and you maybe did it in reaction [10:12] I wonder who did [10:12] I had disabled upstream translations [10:12] but they are back on and set as shared with ubuntu === marcusto_ is now known as marcustomlinson === howefield is now known as howefield_afk [11:37] Mirv: will do, thanks [11:40] seb128: I believe it's pulse, will take a look in a few [11:40] (in a sprint) [11:44] jdstrand, hello [11:44] rsalveti, thanks [11:57] I'd like to build a .click package from a WebApp. [11:59] How can I install the necessary minimum necessary requirements for building .click packages on my developer machine? Without having to install ubuntu-sdk. [11:59] I've tried to install click-dev, but I find no command to use (is it "click?") [12:00] alan@deep-thought:~⟫ dpkg -S `which click` [12:00] click: /usr/bin/click [12:00] ^ you want click not click-dev === _salem is now known as salem_ === alan_g is now known as alan_g|lunch [12:03] Okay, cheers, click did it. -- Then click-dev is for developing click itself? [12:06] peter-bittner: i guess :) thats our standard naming convention [12:07] is there currently a way to run wily image on phone? I'm just getting "This phone needs restoring from a PC or service center" after flashing latest devel-proposed :) [12:08] how nice of me to ask 1 day after GCC5 became the default in release pocket [12:12] Mirv: I couldn't get a wily image to boot last night [12:13] It just got stuck at the bq flash screen [12:26] wily is pretty broken right now [12:55] *** Skype for Web now available on Ubuntu Touch! http://community.skype.com/t5/Linux/Ubuntu-touch-port/m-p/4082105#M12567 *** [12:56] does it work? :) [12:56] Yes! :-) Enjoy! [12:56] * popey tests this [12:57] I had to struggle with the user agent override a bit. The documentation on developer.ubuntu.com is a bit misleading. [12:59] can you file a bug? (there's a link at the bottom of the pages) === alan_g|lunch is now known as alan_g [12:59] (to correct any issues you found) [13:00] Okay, I was about to write this to the mailing list. [13:04] * Mirv is bold and tries dist-upgrade from vivid to wily on phone - this is not going to end up well [13:06] jgdx, how's the hotspot redesign going? [13:07] kenvandine, going okay [13:07] had a json error in settings which took me way too long to figure out [13:07] le sigh [13:07] waiting for ci now [13:16] Mirv: it ended with / being full i guess? :) [13:19] dobey: not yet :) I've been here long enough to know to manually remove a couple of hundred megs from the / by removing "unneeded cruft" like Oxide, various language support, desktop libraries not needed etc [13:20] Mirv: it will definitely break anyway, as everything hasn't migrated from proposed yet [13:21] :'( copy/paste to webapps etc. perhaps coming in OTA-6? [13:22] dobey: I've naturally enabled wily-proposed too, to get even more excitement (plus 0.01% chance of it working) [13:22] peter-bittner: thanks, fixed the page with the issue. [13:25] janimo: hello :) [13:25] jdstrand, hi, sent you an email :) [13:25] ok, haven't gotten to the inbox yet, but will in a bit [13:32] mandel, ping [13:33] Done. The documentation is fixed now. [13:34] Thanks everyone here! And enjoy Skype on Ubuntu Touch! Download it today. [13:38] seb128, I think rsalveti is right wrt it being a pulse issue -- datetime's part is to tell pulse what role to use, either 'alarm' or 'alert'. Pulse's decides how the roles are handled [13:39] charles, ok, thanks [13:55] * Mirv reports phone as dead as could have been guessed after dist-upgrade from vivid to wily-proposed [13:57] lol [14:01] Mirv, told you willy is broken [14:07] guest42345: I had to try! [14:10] Mirv: well, there is a wily image you could have just installed probably more quickly [14:10] and it would have just as easily broken your phone :) [14:15] * ogra_ grins [14:16] I did that first, then wanted to break it the harder way :) [14:17] Mirv: that phone not dead, He's just sleeping, He's pining for the fjords, I didn't want to be a pet shop owner anyway, I wanted to be a Lumberjack! [14:18] s/pet/phone [14:19] davmor2: that phone is no more, it has ceased to be! [14:19] is your hovercraft full of eels by chance ? [14:27] oh, someone has had useful time http://www.omniglot.com/language/phrases/hovercraft.htm [14:27] the essential in any language [14:29] Mirv, beauty ! [14:29] * ogra_ bookmarks [14:30] guys.. why is python3 using 100% cpu on arale when running a simple qml test via sdk [14:39] greyback_, hey, any update on bug #1483840 ? [14:39] bug 1483840 in qtmir (Ubuntu) "webapp_container tests started failing reliably with rc-proposed image #92" [Critical,Confirmed] https://launchpad.net/bugs/1483840 [14:40] oSoMoN: am looking at it still. I suspect you're not using upstart to launch the webap container, which does expose this [14:40] let me check how the app is started [14:41] hi folks [14:41] has anybody ever experienced this issue with rc-proposed? [14:41] http://forum.xda-developers.com/ubuntu-touch/development/t-swithc-mx4-to-rc-proposed-t3177682/post62307487#post62307487 [14:42] i am loosing home [14:42] hope [14:43] greyback_, the autopilot tests use self.launch_test_application(…) to launch the app, not sure what it does under the covers [14:44] nocomp, you looked into the usb issue thing, right? [14:44] switched cable, picked the slowest usb port you've got, etc [14:44] what is this usb issue thing? [14:45] ah [14:45] yes [14:45] switch usb port [14:45] sitch cable [14:45] switch computer [14:45] nocomp, wipe cache again and flash with the open recovery in fastboot mode [14:45] i ve reset the phone [14:45] ubuntu-device-flash touch --channel ubuntu-touch/rc-proposed/meizu.en --recovery-image recovery.img ... [14:45] !recovery [14:45] You need to use the right recovery.img for your device when flashing with adb: see https://wiki.ubuntu.com/Touch/Devices#Working_with_ubuntu-device-flash [14:45] ok [14:45] download it from the link in the table [14:45] one sec [14:46] i restart the pc [14:46] drove me so mad i turned everything off [14:46] also how long did you wait, pushing the rootfs tarball can take 10-15min [14:46] yes but i ve let it overnite [14:47] 9hours [14:47] should of be enough [14:47] k [14:49] re [14:51] recovery downloaded [14:51] i retry [14:57] hmm [14:57] seems to be the same [14:57] what is weird === chihchun is now known as chihchun_afk [14:57] i can easely do an adb push [14:57] without any issues [14:59] adb push while in recovery ? [15:00] nop [15:00] i am not in recovery [15:01] do i have to do a fastboot oem unlock ? [15:01] no [15:01] your bootloader is already unloicked [15:01] ok [15:01] you need to be in fastboo mode and use the --recovery-image option for ubuntu-device-flash [15:01] ahhhhhhh [15:02] ok [15:02] i reboot in fastboot [15:02] clean the cache first [15:02] thx [15:03] ok i get it [15:03] i have no recovery installed [15:03] adb reboot fastboot puts me back in normal state [15:04] i think it is "adb reboot bootloader" [15:04] ok i try [15:05] damm mx4 freezed [15:07] ok [15:07] fastboot devices shows it [15:07] i retry the flash process [15:08] ubuntu-device-flash touch --channel ubuntu-touch/rc-proposed/meizu.en --recovery-image recovery.img [15:08] 2015/08/13 17:08:01 Expecting the device to expose an adb interface... [15:08] device cannot be detected over adb [15:08] nocomp@up-yours:~$ [15:09] wtf [15:09] i am in fastboot [15:09] i am in fastboot, [15:09] so adb won t work correct ? [15:10] right [15:10] so i should flash just the recovery? [15:10] and you have the right recovery.img (and the path to it is correct ?) [15:10] yes [15:11] nocomp@up-yours:~$ ls [15:11] Bureau examples.desktop Modèles Public Téléchargements [15:11] Documents Images Musique recovery.img Vidéos [15:11] nocomp@up-yours:~$ [15:11] no, you shouldnt need to flash anything ... u-d-f should just boot the recovery.img you provide [15:11] so what is not working? [15:11] and that recovery.img file is the MX4 image ? [15:11] nocomp@up-yours:~$ fastboot devices [15:11] 75HABLM3ARFY fastboot [15:11] nocomp@up-yours:~$ [15:11] yes [15:12] also do you have the right version of u-d-f ? [15:12] u d f = ? [15:12] ubuntu-device-flash [15:12] yes [15:12] installed phablet tools [15:12] * ogra_ blames sergiusens for picking an annoyingly long name [15:13] if adb is not working in gastboot [15:13] how can this flashing process work [15:13] i am missing something [15:13] it uses fastboot to boot the recovery img you provide [15:13] recovery img file is on my pc [15:13] oki [15:14] doest it has a verbose mode? [15:14] you can try to use fastboot manually to flash it: [15:14] sudo fastboot flash recovery recovery.img [15:14] ok [15:14] ten boot into this recovery [15:15] there you should have adb [15:15] and can use u-d-f to flash [15:15] nocomp@up-yours:~$ sudo fastboot flash recovery recovery.img [15:15] [sudo] password for nocomp: [15:15] sending 'recovery' (10672 KB)... [15:15] FAILED (data transfer failure (Value too large for defined data type)) [15:15] finished. total time: 0.034s [15:15] nocomp@up-yours:~$ [15:15] and you are 100% sure this is the right img ? [15:16] i show u the one i ve took [15:16] there is only one for mx4 [15:17] i redownload it [15:17] http://people.canonical.com/~alextu/tangxi/recovery/recovery.img [15:17] well, i hope alextu keeps that recent :) [15:18] so do i [15:19] but i'm honestly out of ideas [15:19] ocomp@up-yours:~$ sudo fastboot flash recovery recovery.img [15:19] takes quite some time [15:19] shouldnt [15:20] sending 'recovery' (10672 KB)... [15:20] FAILED (data transfer failure (Value too large for defined data type)) [15:20] finished. total time: 0.034s [15:20] nocomp@up-yours:~$ [15:20] gbreat [15:20] great [15:20] wtf [15:20] john-mcaleely, do you know if flashing recovery on arale should work ? [15:20] i hope it still boot [15:21] still boot [15:21] i retry [15:22] ogra_: it does [15:22] weird, why does it not work for nocomp_ then [15:23] nocomp@up-yours:~$ fastboot devices [15:23] 75HABLM3ARFY fastboot [15:23] nocomp@up-yours:~$ sudo fastboot flash recovery recovery.img [15:23] sending 'recovery' (10672 KB)... [15:23] FAILED (data transfer failure (Value too large for defined data type)) [15:23] finished. total time: 0.034s [15:23] nocomp@up-yours:~$ [15:23] nocomp_: has this always been an ubuntu device? [15:23] there is no value in trying it over and over [15:23] yes [15:23] meizu mx4 [15:23] yeah, that would have been my next question too === didrocks1 is now known as didrocks [15:23] ubuntu edition [15:23] if there was a factory ubuntu install on it [15:25] drives me mad [15:25] you are using a USB 2.0 port ? [15:25] and the original cable ? [15:26] no cable in the box [15:26] i use different usb [15:26] i retry with other one [15:27] if cable wasn t working [15:27] fastboot devices wouldnt show the device correct? [15:28] is there a way to do that from device? [15:28] i upload all file via pc [15:28] and then flash from device? [15:28] cables can be deceptive about whether they are "working" or not [15:29] ok [15:29] they work fine with all my android devices [15:29] so what other option do i have? [15:30] nocomp_: have you checked the md5sum of the image you are trying to flash at fastboot? [15:30] nop [15:31] https://wiki.ubuntu.com/Touch/Devices#Working_with_ubuntu-device-flash [15:31] took the one for mx4 [15:31] nocomp_: yes, but check it [15:31] there are no [15:31] nocomp_: check it anyway and feed the hash into google [15:32] how do i do that? [15:32] nocomp_: just run "md5sum whatever.img" and paste the long string of characters into google [15:32] ok [15:33] nocomp_: if the hash matches anything on google it is probably ok [15:33] or not ok [15:33] no result [15:33] dobey: but very likely to be ok [15:33] http://system-image.ubuntu.com/ubuntu-touch/rc-proposed/meizu.en/arale/ doesn't have md5sums [15:33] mcphail: not in this case i guess :) [15:33] dobey: no, but someone else may have posted them [15:34] dobey: ha! [15:34] and md5 is insecure anyway [15:34] so in fact i have an authentic ubuntu phone [15:34] but i can do less with it [15:34] than if i had a nexus [15:34] great [15:34] dobey: security is not the issue here [15:34] you're falsely assuming you wouldn't have the same problems with a nexus device [15:35] well i am just saying i can t do much with it at least less than ogra_ with his nexus [15:36] my nexus ? [15:36] well my nexus4 won't even boot at the moment. it just keeps rebooting from the google boot screen [15:36] lol [15:36] * ogra_ hasnt booted any nexus in over a year [15:36] ok [15:36] i thought u had a nexus [15:36] my mistake [15:36] no, i have a few bq 4.5 and one MX4 [15:36] oh mx4 ubuntu edition? [15:36] other than flashing your device, i also have no idea what yu're trying to accomplish exactly [15:36] mainly using the MX4 nowadays [15:37] i d like to switch to rc-proposed [15:37] http://forum.xda-developers.com/ubuntu-touch/development/t-swithc-mx4-to-rc-proposed-t3177682 [15:38] ogra_ can probably do a lot more than you can, with the phone, regardless of whether the flash works or not, simply because he has a greater knowledge and understanding of how it all works :) [15:38] uused the same recovery file as i do? [15:39] i don't know what recovery.img you are trying to use [15:39] there is only one in the link i gave you [15:39] nvm [15:39] i give up [15:39] 2 days on it [15:40] i hhope tthe next ota with hotspot option ll come soon [15:40] dobey, apparently the one from alextu thats linked on the Devices wikipage [15:40] sorry, despite popular belief, i am not omnitient/omnipotent/omnipresent [15:41] udf just ignores it when using the --recovery-image option .. and flashing it with fastboot seems to trigger a size error [15:41] dobey: I think they were saying you were _incontinent_ :) [15:42] mcphail, i think he still has a few years til diaper-again age [15:42] s/a few/a great many/ [15:43] nocomp_: out of interest, what was the md5 hash for the file you downloaded? [15:44] 60ae535e863d48bbc3b071938c12a188 [15:44] nocomp_: OK, same as me when I download it. At least we know it hasn't been corrupted on your disk. Doesn't mean to say it is a working image, though [15:44] ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/meizu.en --bootstrap --recovery-image=recovery-arale.img [15:44] that should work with the phone at the bootloader [15:46] --bootstrap will wipe the device though, so if you have any data on it you want to keep, you need to back it up [15:47] dobey: afaik from hacking my krillin last night, that only works from an adb-enabled recovery. (The krillin device, at least, calls "fastboot" the bootloader) [15:47] you have to use --bootstrap to flash from the bootloader, as it's a different interface than adb [15:47] mcphail: no, you can't use --bootstrap if in recovery or with system booted with developer mode [15:47] mcphail: --bootstrap is for fastboot (and it will wipe data) [15:48] if you're in recovery or booted system, you can't use --bootstrap [15:48] dobey: I had to use that command in recovery last night, and switch to fastboot after it started. Wouldn't run directly in fastboot mode [15:48] so either use --bootstrap and wipe the data, or boot to recovery or system and don't use --bootstrap [15:49] mcphail: not with --bootstrap [15:49] --bootstrap doesn't work in recovery because it uses fastboot [15:49] yep, with. I had to switch to fastboot [15:50] so what would you recommand? [15:50] to try [15:50] nocomp_: always try a new cable and different USB port before anything else [15:50] if you are in fastboot, then the command i pasted; assuming you don't care about your data [15:51] this one? [15:51] ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/meizu.en --bootstrap --recovery-image=recovery-arale.img [15:52] yes [15:53] ok thxx [15:53] it *will* destroy any data you have on the phone though [15:53] don t care [15:54] it s emptty [15:54] ok [15:54] just reset it [15:54] then run that with the phone in fastboot mode [15:54] i go get the device [15:57] dobey: so, for future reference, I _should_ be able to run that directly in fastboot mode on krillin as well? When I tried last night I was given "no adb" errors in fastboot mode, whether or not I was using --bootstrap but I may have made a typo somewhere else in the command [15:58] mcphail: yes. [15:58] dobey: ok, good to know [15:58] --bootstrap requires fastboot, and without --bootstrap you must have adb available [15:58] nocomp@up-yours:~$ ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/meizu.en --bootstrap --recovery-image=recovery.img [15:58] 2015/08/13 17:58:35 Expecting the device to be in the bootloader... waiting [15:58] 2015/08/13 17:58:35 Device is |arale| [15:58] 2015/08/13 17:58:39 Flashing version 87 from ubuntu-touch/rc-proposed/meizu.en channel and server https://system-image.ubuntu.com to device arale [15:59] lets see what happends [15:59] thxx dobey [15:59] sure [15:59] i go prepare dinner [15:59] i keep u poster [15:59] posted [16:00] dobey: so, the converse is I should also be able to flash from recovery without --bootstrap and without wiping everything on the device? When I tried that last night I was getting shell errors and had to resort to --bootstrap [16:01] 2015/08/13 18:00:48 Created ubuntu_command: /home/nocomp/.cache/ubuntuimages/ubuntu_commands030084128 [16:01] 2015/08/13 18:00:48 Rebooting into recovery to flash [16:01] nocomp@up-yours:~$ [16:02] mcphail: yes; i've done it numerous times, but i've not flashed a consumer krillin device ever, so there might be special needs there for recovery image or something [16:03] dobey: it may have been the case that the device was so messed up a complete flash was the only option [16:03] mcphail: also possible [16:03] nocomp_: so, it worked then? [16:03] seems to [16:03] geting meizu splash screen back on [16:04] ubuntu splash screen [16:04] u did it :) [16:04] thxxx [16:05] np [16:20] what;s wrong with telegram? this is from telegram's log [16:20] libust[21905/21925]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958) [16:20] libust[21905/21924]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) [16:20] there are 10000000000000000 lines like this [16:20] this is silly [16:22] guest42345: all the logs have those [16:22] :| [16:23] guest42345: they are a bit annoying [16:23] yeah :( [16:24] but harmless beyond that [16:24] * ogra_ blames ted [16:24] will snappy fix this? [16:24] * guest42345 or cure cancer? :P [16:24] snappy will fix everything you can imagine indeed ;) [16:24] yay! [16:25] ogra_, I think all mine are hidden now, I think those are in qtubuntu now. [16:25] ah [16:25] If nothing else, UAL has a bunch more of them :-) [16:25] * ogra_ wonders who owns qtubuntu nowadays [16:26] ted it's like billions of lines.. they are trashing the logs [16:26] and i find it hard to read the logs [16:27] cat /path/to/log | grep -v lttng|less [16:27] :)) NO [16:27] ;) [16:27] ogra_: I do [16:27] * mcphail stroles the spurious cat [16:27] *strokes [16:28] you could indeed let the cat out and use grep directly :) [16:28] :) [16:31] guest42345, I'm not saying it isn't a problem, I'm saying that in this case I don't think it's my fault :-) [16:37] ted, :P === alan_g is now known as alan_g|EOD === boiko_ is now known as boiko [18:00] ogra_: fix everything you say...... that you can imagine you say...... Where's my flying unicorn then hmm hmm hmm??? [18:02] you don't want much, not content with a unicorn, you want a flighted one. [18:02] davmor2, did you try snappy install my-flying-unicorn.snap yet ? [18:03] popey: it's easier to get around if you are not on the ground [18:03] fair [18:04] popey: plus international travel suddenly becomes free :) [18:04] popey: and why have just a flying horse when you can have a unicorn [18:05] ogra_: hahaha [18:06] popey: I'd of gone for nyan cat but that music [19:31] hello [19:32] I just tried to flash ubuntu-touch-devel-proposed/krillin.en and now my device gets stuck on the bq load screen.... [19:32] any ideas? I cannot even power it off [19:34] ahhh [19:34] t1mp: don't use devel-proposed [19:35] just after asking here I managed to get it in fastboot mode :) by holding the proper keys long enough [19:35] dobey: I wanted to try the latest UI toolkit which was released to the overlay ppa today [19:35] t1mp: you'll need to reflash to stable or rc-proposed [19:35] I can try the stable image and then install the ppa manually [19:35] dobey: ok, flashing rc-proposed now. [19:35] t1mp: devel-proposed is wily. rc-proposed is vivid+overlay [19:36] dobey: do you know if there is a delay between a package going in overlay and it ending up in an image? [19:36] t1mp: images are built daily for rc-proposed; but promotion to stable is usually once every 4-6 weeks or so i guess [19:38] hmm, after (supposedly) flashing it still gets stuck in the bq screen [19:39] how did you flash? [19:40] ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/bq-aquarius.en-proposed [19:41] with the phone in recovery? [19:41] krillin [19:43] yes. were you booted into fastboot, or recovery? [19:43] fastboot [19:44] ah, I also added --bootstrap [19:45] is it possible to get AGPS on mako? [19:52] t1mp: ok, well that flashed a whole new image, so first boot will take a bit longer than normal [19:56] dobey: hmm.. I get this: http://pastebin.ubuntu.com/12074006/ [19:57] dobey: and the device is stuck in the loading screen (with a large ubuntu logo) [19:57] should I just wait longer? [19:57] ah it rebooted now... back in the bq boot screen. [20:00] yeah if it doesnt' boot, you might need to pass --recovery-image to flash on the krillin; with the recovery.img from the wiki page [20:00] yes it is stuck in the boot screen again [20:02] dobey: do you have a link at hand? I don't see recovery.img on https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/ [20:02] ah, that's no wiki. But the wiki page links there [20:04] seems like I left by accident [20:04] https://wiki.ubuntu.com/Touch/Devices#Working_with_ubuntu-device-flash [20:04] you need the recovery-krillin.img most likely [20:06] dobey: thanks. I'm now trying ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/bq-aquaris.en-proposed --bootstrap --recovery-image=Downloads/recovery-krillin.img [20:15] dobey: thanks! it works now! :) [20:16] great [20:19] Elleo, i had an autopilot test from settings type an extra "e" [20:19] from the logs: Could not connect: "Access point with SSID [eduroame] could not be found" [20:20] the test types "eduroam" for the ssid [20:20] but it got an extra "e" [20:25] let's just cave and rename the access point === salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem === zyga is now known as zyga-afk === _salem is now known as salem_ [22:43] where can i find defconfig for mako or hammerhead? === Guest41160 is now known as alin [23:37] do mako use devtmpfs?