=== _salem is now known as salem_ === salem_ is now known as _salem === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [04:02] howdy everyone === _salem is now known as salem_ [04:48] Well I was trying to get Ubuntu Touch to recognize my files from Android using mount —-bind but all that was doing was getting it to show up in Full Mode/Terminal but not in the Music app. [04:48] So at this point, I suspect a permissions issue but I took ownership of the files. [04:48] hi mate [04:48] Ah well. [04:48] wich device your on? [04:49] howdy [04:49] hammerhead/Nexus 5 [04:49] cool [04:49] nexus7 here [04:49] I’m not overly worried about that, in all honesty I’m more concerned with my lack of SMS xD [04:49] does it run well on n5? [04:49] test message buggy for you? === salem_ is now known as _salem [05:08] yeah it runs fine. [05:08] In fact if SMS worked I’d use it all the time, just use it instead. [05:09] i also have a few bugs on nexus7 [05:09] like brightness control resets every boot [05:10] you also have this on n5? [05:10] Yeah well it’s the price we pay for using Beta software [05:10] Yep. I turned on Auto Brightness [05:10] that helps it [05:11] what happens on auto brightness? [05:11] It is initially reset but it then takes over properly and just adjusts it. [05:11] ill try it later on [05:11] i need 100% all the time :p [05:12] well, at least we have a secure Os on tablet/phone :p [05:12] Well the auto brightness does a good job. [05:12] nothing like android nightmare [05:12] tnx for the tip, ill try it [05:12] Well Android could be much much worse. [05:12] howso? [05:12] But yeah I prefer having a true Linux base to work with. [05:13] Well they could easily just install whatever they wanted and by they I mean bad people. [05:13] so much malicious on android [05:13] At least there are barriers if you use it properly. [05:13] but i have to admit android still runs smoother for now [05:13] i hope the RTM touch gets real stable [05:14] hackersarchangel: you think release of Bq and meizu will influence ubuntu touch? [05:14] Yep. [05:14] i also think :p [05:14] I think it will at least do something to shake people up, and it will probably help it get a better reputation if nothing else. [05:15] true [05:15] i miss my terminal apps so badly [05:15] i wanna get them on touch [05:15] but cant because dir lock [05:16] hackersarchangel: do you also run the devel version on your n5? === chihchun_afk is now known as chihchun [06:01] mvo_: Please sync this MR with the branch, it seems to conflict after your last MR, what finally landed https://code.launchpad.net/~mvo/qtcreator-plugin-ubuntu/lp1366786-click-deploy [06:01] hi bzoltan, let me have a look [06:02] mvo_: Thank you :) [06:04] bzoltan: np, I updated the branch and fixed the conflicts [06:04] mvo_: Great. I will include that to the actual landing (silo3) and ping you when it is ready for review. [06:32] good morning === chriadam is now known as chriadam|away [06:51] Hello everyone. I was using ubuntu touch (devel, 203r @ lg nexus 4) for a few days and noticed some problems with a clock. When I'm not using a smartfone for some time time freezes. I.e. lockscreen shows 10:30 PM, but a real time is 10:45 PM. Same story with system tray (or how it's called here?) [06:52] I believe for the same reason alarm never works :( [06:53] Is there any known workaround for this issue? === kickinz1|afk is now known as kickinz1 === kickinz1 is now known as kickinz1|afk === kickinz1|afk is now known as kickinz1 [08:19] Good morning all; happy Swap Ideas Day! :-D [08:41] popey : we have 4 diferent section in UT.. scope, apps, music and videos... so there will be any option in future to change them, like adding new one or removing any one [08:41] mailyaseen: yes, you can change them [08:41] popey: how can i change them? [08:42] swipe up from the bottom in the dash === kickinz1 is now known as kickinz1|afk === kickinz1|afk is now known as kickinz1 [09:10] popey : but i cant delete any existing section, or cant add any new section there.... [09:11] mailyaseen: yeah, you use the star icon in the top right to favorite them [09:11] maybe you're on an older image than me ☻ [09:11] popry : i am on r203... [09:12] I'm on 235 here [09:13] popey : then i will wait for stable release... and will make use of that, to remove or add section [09:13] popey: thank you === kickinz1 is now known as kickinz1|afk [09:25] mailyaseen: no problem! [09:43] Um, hi. [09:43] I want to ask some questions. [09:43] What's the safest way to repair my grub? === kickinz1|afk is now known as kickinz1 [09:49] D [10:05] morning all [10:09] Akiva-Thinkpad: morning [10:09] hey davmor2 [10:10] what you working on today? [10:10] Akiva-Thinkpad: same as always new an interesting ways of destroying Ubuntu [10:11] davmor2, oh? Do tell :P [10:15] Akiva-Thinkpad: I'm QA it's what I do :) [10:16] davmor2 any idea when the phone's gonna come out? [10:17] Akiva-Thinkpad: No [10:17] davmor2, Shucks [10:23] Akiva-Thinkpad: The Meizu MX4 is scheduled for september 20, but I don't know if it will come with Ubuntu from the start. === kickinz1 is now known as kickinz1|afk [10:35] sturmflut-work, yah i heard about that. Ive never used a large phone like that before [10:35] have you? [10:44] o/ [10:45] hi all, yesterday i asked a question and got now answert. i am new to irc and hope it was not because i oversteped some rules. i post it again in the hope somebody would answer it. thx in advance [10:45] Hi everyone! A question: it seems it has been a bit silent around the feature that you can use a full desktop version of ubuntu with a dockingstation. is this a soon to come reality or was that just a plan? [10:48] E524, to dock an ubuntu phone that then turns into a desktop, you actually first need an ubuntu phone ;) [10:49] hehe, yes, but it's soon comming and i am saving money for it. if that docking fuction is also comming, i suppose there will be dockinstations too [10:50] so was that a yes? [10:52] E524: We need the ubuntu desktop to be on unity8 too so it most likely won't be on this phone, but will be in the future, as I understand it. [10:53] E524, well, the first iteration will just be a phone ... once thats out the team will have time to work on integrating a dektop/dock mode [10:53] Akiva-Thinkpad: I used a Nexus 5, the MX4 is only slightly larger. It is quite nice to have such a large display. [10:53] and what davmor2 said too ... [10:54] it will only work if both UIs use the same code [10:54] ah ok thanks for the answers! so i will go with the bq model first i guess and have then still something to be looking for :) still great news! [10:54] sturmflut-work, interesting... [10:54] sturmflut-work, I'm afraid the larger it is, the less durable it is [10:54] I'd hate to have a screen cracked. [10:55] Akiva-Thinkpad: That largely depends on the type of glass. I have never cracked any of my devices. [10:56] does it fit well in a pocket? [10:58] Akiva-Thinkpad: The Nexus 5 did. The additional diagonal inch does not automatically translate into a much bulkier device. Which phone are you used to? The Nexus 4 for example has a 4.7 inch screen and some additional space around the screen, at the end it is nearly exactly as large as the Nexus 5. [10:59] Screen size alone doesn't mean much, you have to look at the actual size of the device. [10:59] sturmflut-work, the last phone I had was the htc dream [11:00] sturmflut-work, sort of ironic considering that I am developing phone apps. I am really looking forward to the touch. [11:01] The HTC Dream is 117.7 x 55.7 x 17.1 mm in size. The MX4 is rumored to be 144 x 75.2 x 8.9 mm. I think the reduction in thickness alone makes the MX4 less bulky than the HTC Dream. You might miss the physical keyboard though. [11:03] Akiva-Thinkpad: [11:04] sturmflut-work, well its the ubuntu touch; don't think I'll miss it much [11:05] i was so non-impressed with android, didn't feel like touching it again. === MacSlow is now known as MacSlow|lunch [11:32] sergiusens, hmm, do we store persistent properties anywhere in the emulator ? [11:34] ogra_: afaik all props are set throuh the init script [11:34] aha [11:34] that might be the adbd issue then [11:35] god ... thats time consuming [11:36] * ogra_ guesses his next laptop will have a touchscreen just for the emulator :P [11:38] i have a phone with physical keyboard (xperia pro) and really hope there will be one with ubuntu in the future. working with ssh is so much more conveniet! [11:38] ogra_: skip the emulator, run it native then! [11:39] haha [11:39] tbr, i need to fix a bug that only shows in emulator :P [11:39] excuses, excuses ;) [11:51] hmpf, so stuffing the property in build.prop doesnt help :/ === chihchun is now known as chihchun_afk [11:59] dobey: so, I've analysed bug 1342858 some more, and I think I have most of a fix for it, but it doesn't cover the situation that you raised in a comment there after all. Sorry for the inadvertent misdirection. Would you mind filing a fresh bug? [11:59] bug 1342858 in click (Ubuntu) "old click packages are not always cleaned out" [High,In progress] https://launchpad.net/bugs/1342858 === MacSlow|lunch is now known as MacSlow [12:15] sergiusens, i'm lost, where do i find that init script [12:16] (and why cant i mount the image files ... i thought they are plain qemu qcow images) [12:17] ogra_: need to create with --use-raw-disk [12:17] gah [12:18] ok [12:18] ogra_: the scripts are under devices/generic [12:18] cool, thanks === kickinz1|afk is now known as kickinz1 [12:20] Saviq: do we have a unity8 bug for being unable to launch apps after they're updated? [12:21] would anyone mind if I upload a new ubuntu-touch metapackage with updated deps for the ubuntu-sdk-libs-dev ? [12:21] popey, right, I was meaning to look for one / file one [12:21] popey, it's actually not a u8 bug but a unity-scope-click one [12:21] popey, please file with them [12:21] k [12:28] grmblfjx [12:28] now system-settings doesnt start :( [12:30] sergiusens, do you have any clue waht /system/bin/qemud is ? it seems that replaces adbd (or at least manages it) in the emulator [12:30] ogra_: it's the bridge to your host [12:31] ah [12:31] ogra_: such as the egl bridge [12:31] so the equivalent to the kernel gadget [12:31] man this is awful [12:32] ogra_: https://code-review.phablet.ubuntu.com/gitweb?p=aosp/platform/external/qemu.git;a=blob;f=android/adb-qemud.c;h=9d82251cd18fabfafc22177df06b5ac7dc6e10e4;hb=refs/heads/phablet-4.4.2_r1 [12:33] ogra_: all emulator things are complicated; took me a lot to get the sdcard stuff working [12:33] screen not turning off during call - - which package controls that ? [12:39] ha ! [12:39] now that was to easy [12:39] !changelog [12:39] changelogs for Ubuntu packages can be found on http://changelogs.ubuntu.com [13:00] Hi anyone. Can someone help me with a NFS issue ( Ubuntu 14.04.1 LTS) ? [13:02] ,usrquota, is not understood by mount ( mount.nfs: an incorrect mount option was specified error ) [13:08] cjwatson: sure [13:08] thc2cat: you probably want to /join #ubuntu which is the support channel [13:09] if I want to back up my Ubuntu phone - which parts should I adb pull over? /home/phablet and /var/lib - anything else? === chihchun_afk is now known as chihchun [13:10] dholbach: what you expecting to be in /var/lib? [13:10] popey, I think I remember sergiusens mentioning it the last time I asked :-) [13:10] maybe stuff like previously used networks? [13:11] I was sort of hoping somebody would say "oh, we have ubuntu-device-backup for that now" :-P [13:11] dholbach: popey you want to tar preserve perms /userdata/[user-data|system-data] [13:12] dholbach: "oh, we have ubuntu-device-backup for that now" [13:12] <3 [13:13] thanks sergiusens [13:24] are we there yet? Ubuntu phone release date anyone? [13:29] derek-g: some time in the next billion minutes [13:30] davmor2, that's about 1,901 years [13:30] He's right! [13:31] popey: you say that like you are surprised I'm right ;) [13:32] I meant derek-g was right, I'd never say you were. [13:32] popey: phew [13:32] Launch date is still this year - right? RIGHT? [13:33] popey: I was also right it will be released with in that time though :P [13:36] I just hope I can get it by christmas time. [13:45] bfiller: regarding bug https://bugs.launchpad.net/gallery-app/+bug/1366820, the share does not work because it has never been implemented for selections. i started implementing it, but right now it occurred to me that maybe it would be better to just remove the share option when a selection is available [13:45] Ubuntu bug 1366820 in gallery-app "sharing broken from Photos tab" [High,In progress] [13:45] bfiller: btw it's also broken from events tab [13:46] nerochiaro: we should try to support that [13:47] nerochiaro: seeing we can share a single photo doesn't seem like it should be too hard to support single or multiple from the selection view [13:47] bfiller: ok, i'll keep working on it then. it's not hard, except for the fact that the hub doesn't support mixed type shares, so when videos and photos are in the same selection we need to disable the option [13:48] nerochiaro: yup ok [13:50] bfiller: do you know who's responsible for qtubuntu camera backend ? i ended up using Florian's suggestion in the end (I'll explain why on the standup) to fix bug https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1234130 but I'll need someone to review it [13:50] Ubuntu bug 1234130 in gallery-app (Ubuntu) "Gallery app does not refresh thumbnails correctly" [High,In progress] [13:50] nerochiaro: jhodapp can help review it [13:51] nerochiaro, yes, I can review it for you...just assign me to any MR [13:51] jhodapp: done [13:51] thanks [13:52] nerochiaro, cool...I'll get to it a bit later today if you're not in a huge hurry...I have some other MRs to look at first [13:52] jhodapp: no rush at all [13:52] nerochiaro, cool thanks [14:03] sergiusens, hmm, u-d-f doesnt halt anymore if i'm not in the bootloader with --bootstrap ... it downloads and then hangs silently until i reboot into bootloader ... no message [14:04] hmm [14:04] s/doesnt halt/doesnt notify [14:04] ogra_: ah, if you pass --device it doesn't halt [14:05] sergiusens, oh, i didnt know that [14:05] * ogra_ only ever passed device in recovery before :) [14:06] (whithout --bootstrap) [14:06] slangasek, FYI i got around using pam_exec (or any other pam hook) [14:09] nik90: hey [14:10] zyga: hey [14:10] nik90: how's your plainbox stuff going on [14:11] zyga: I created my demo example provider and then started reading through the demo example to see how I can split up my jobs and whitelist [14:12] zyga: I should be able to push it to a branch in a few hours [14:13] zyga: when do you EOD? I can try to have something to show you by that time [14:15] nik90: late, I'm working on cool features [14:15] nik90: ping me any itme [14:15] time [14:15] cool, will do [14:18] ogra_, what channel would you suggest for my Nexus 7? [14:19] rsalveti: hey, I talked to the designer yesterday and they strongly feel that calls, alarms must always (also) be played in the speaker phone regardless of whether a headphone is connected to the phone. [14:19] rickspencer3, well, we check flo on neither channel ... the test results for rtm look not worse than mako http://ci.ubuntu.com/smokeng/utopic/touch_stable/ ... so probably that one [14:20] http://ci.ubuntu.com/smokeng/utopic/touch/ doesnt really have enough info with failing devices etc [14:20] thanks ogra [14:20] (the latter is devel-proposed) [14:20] yeah, I figured [14:20] rsalveti: we are tracking that request at bug 1364647 [14:20] bug 1364647 in Ubuntu Clock App "Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used" [High,Confirmed] https://launchpad.net/bugs/1364647 [14:24] barry, when you ran QtCreator, could you not cancel out of the wizard? [14:26] rickspencer3: didn't see a cancel button [14:28] rickspencer3, I just for the same [14:28] I cancel, it warns me I'll die if I do [14:28] I accept [14:28] nada. [14:28] *I just had the same [14:29] awesome [14:29] barry, are you coming tonight? [14:30] rickspencer3: yep, planning to! [14:30] cool! [14:31] rickspencer3: i might bring my son, if he's homework clear and doesn't mind being bored by a bunch of geek talk ;) [14:33] hehe === dandrader is now known as dandrader|afk [15:04] * cjwatson wonders why the dual-boot app on android isn't seeing any ubuntu-touch/devel-proposed updates beyond 226 [15:06] ogra_: ah? How did you get around pam? [15:08] slangasek, adb is poretty tricky since it has two disconnect parts ... (gadget driver and adbd) and the world ends if they go out of sync ... so i have an upstart job that watches the gadget property anyway, this also already checks the PW lenght on boot ... i just had to add a simple upstart-file watch for the shadow file ... works awesome :) [15:08] *pretty tricky [15:08] niemeyer: ok, cool, will take a look at that later this week then [15:08] niemeyer: sorry [15:09] nik90: ^ [15:09] slangasek, i'll outline all that (and why i did it like that) in the document ... [15:09] rsalveti: cool [15:12] ogra_: ok [15:13] it is effectively the same ... just without involving pam === dandrader|afk is now known as dandrader [15:26] seb128, hey, I'm looking at bug 1364366 – it strikes me as odd. Everything is in order, but the icons aren't showing. In fact, without changing any code except using "fallbackIconName" instead of "iconName" shows the icons. [15:26] bug 1364366 in ubuntu-system-settings (Ubuntu) "Wi-Fi networks in System Settings lack strength or authentication icons" [High,Confirmed] https://launchpad.net/bugs/1364366 [15:26] seb128, any idea? [15:29] Does anybody know what the plans for ARM64/ARMv8 support are? 64 bit CPUs will become mainstream shortly, will there just be a new type of kit in Qt Creator (e.g. "UbuntuSDK_for_arm64_GCC_ubuntu_sdk_14_10_utopic") and everything is fine? [15:29] sturmflut-work, ubuntu has an arm64 distro since about a year [15:30] but i doubt anyone will target arm64 in the SDK before we even have any devices running ubuntu touch on an arm64 [15:31] ogra_: also, all the packages in the ubuntu-touch images aren't necessarily built on arm64 yet. lots of things aren't yet, unfortunately [15:32] ogra_: I know. My question is if the SDK has to be changed in a major way to support ARM64, or if it is flexible enough already. [15:32] dobey, yeah, who cares :) [15:32] sturmflut-work, the SDK is just a UI for various tools ... i think all the tools it uses should already be able to do arm64 [15:33] so its most likely some config adjustments you will need to do once that becomes an issue [15:34] seb128, figured it out. [15:35] We looked into ARM64 server hardware a short time ago. Sadly it is still too expensive, otherwise I could have tested Ubuntu ARM64 on a real machine instead of just inside the emulator. [15:36] * ogra_ doesnt expect any ubuntu touch arm64 devices within the next year at least [15:36] so nothing i would bother with just yet [15:38] barry, does this make sense to you ? [15:38] http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/view/head:/plugins/system-update/system_update.cpp#L209 [15:38] ogra_: you're not porting to the iPhone 6? :P [15:39] dobey, send me one [15:39] barry, you can see that is what we do on UpdateAvailableStatus from s-i-d [15:39] barry, it's calling downloadUpdate if the state is downloading [15:40] barry, i suspect that's what's triggering the multiple downloads [15:40] barry, but... i'm also not sure if we want the inverse of that [15:40] if s-i-d doesn't show it as downloading, we don't want to just tell it to start downloading [15:41] barry, we'd want to check the setting right? or does s-i-d do that for us? [15:41] barry: ping [15:41] Chipaca: hey, can you hold on for a sec? ;) [15:41] uh oh... barry is getting flooded :) [15:41] hah, DOSing barry [15:41] Chipaca, we can fight for him :) [15:41] ENOEGO [15:42] kenvandine: no fair! I'm tired out after hauling two 9yo kids back from school [15:42] :-p [15:42] Chipaca, on your back? or in the back seat? [15:42] if the later, i'd say you're out of shape :) [15:42] kenvandine: one on my back, both of them on the bus [15:42] anyway. in answer to barry's first, serious question: sure, i can wait [15:43] i'll go make myself more tea and grab some ginger biscuits [15:43] mmm [15:43] * Chipaca goes [15:43] kenvandine: yeah, you don't want to be calling DownloadUpdate if it's already downloading. [15:43] barry, so i think we could either just drop that or we need to do a check for the setting and then call downloadUpdate === rickspencer3_ is now known as rickspencer3__ === rickspencer3__ is now known as rickspencer3 [15:44] kenvandine: if you see the downloading flag is true, then that means it will automatically download and you don't need to do so explicitly. if downloading is false, you need to explicitly initiate the download [15:44] barry, but we should check the autodownload setting right? [15:44] dobey: There also already is at least one 64 bit Android phone in the market, the HTC Desire 510. Amusingly it does come with a 32 Bit version of Android. Android will not have 64 bit support until Android L is released. [15:44] barry: question while you're there, if it's on 3g but set to auto-download on wifi, will downloading be true? [15:45] * barry still thiking about kenvandine's q [15:45] * Chipaca really goes for tea [15:45] Chipaca: if we're wifi-only, we pass that flag straight to ubuntu-download-manager and expect it to dtrt [15:45] if (!downloading && (m_downloadMode == 0)) [15:46] e.g. udm.allowGSMDownload(allow_gsm) [15:47] kenvandine: i think the idea was that if auto-downloads are *not* enabled, it would only download on explicit action by the user [15:48] barry, right, so i need to check that before i call downloadUpdate [15:48] except where they click the button [15:48] which is handled elsewhere [15:49] kenvandine: i don't totally understand this code though. [15:49] barry, but also, would isAvailable mean it has already been downloaded? [15:50] kenvandine: not necessarily. it just means the device is behind revs on the server [15:50] ondra: I can't figure out why humpolec isn't showing me versions of ubuntu-touch/devel-proposed newer than 226. The last useful thing in "adb logcat" output is "D/UbuntuInstallService( 5144): onHandleIntent>>: CHECK_IF_UPDATE_AVAILABLE". How do I go about tracking this down further? [15:50] * Chipaca dunks his ginger biscuits in the tea and reads the backlog [15:50] barry, ok, so when i get UpdateAvailableStatus, there is no way to know if it is already downloaded? [15:51] mpt, hey, you have to remember to re-assign that background bug you stole from me :p [15:51] (when you're done) [15:51] jgdx, I haven’t forgotten, it’s Critical [15:51] kenvandine: correct. you need to watch for the UpdateDownloaded signal, which always tells you the download is done (or UpdateFailed for error cases) [15:51] jgdx: mpt: now now, no squabbling over the bugs, i'm sure there are enough for both of you [15:52] cjwatson that is known, it's because there is no delta from from version you are on ( at least I saw this in other channel) [15:52] jdstrand, hi there... was wondering about click-reviewers-tools and the way it triggers checks for manual review [15:52] barry, ok, so when i have this signal i just need to call downloadUpdate if it isn't currently downloading and assume s-i-d will not crash :) [15:52] ondra: Ah, do I have to just uninstall and reinstall then? [15:52] jdstrand, so far I was hooking on (MANUAL_REVIEW) being part of the check text [15:52] pindonga: in the sdk? [15:52] jdstrand, are there more hooks like this? or a better way to track checks requiring manual review? maybe we can expand the return json [15:52] cjwatson so dualboot won't see new verson, but reboot to Ubuntu and run updater there [15:52] to avoid depending on a string? [15:53] ondra: Oh, does that work now? [15:53] barry, i'd expect if i call downloadUpdate on a download that has already downloaded, s-i-d would just emit the updateDownloaded signal right? [15:53] jdstrand, this is for the checks run in the store [15:53] cjwatson you can download update with Ubuntu upgrader then reboot to Android and dualboot will pick that downloaded update [15:53] kenvandine: correct. :) but i'm having a difficult time reproducing this bug locally because 1) the crash happens *after* the UpdateDownloaded signal is sent so there's no change in client behavior; 2) in my test suite the si-dbus process does not seem to exit, even though logging proves that the lock release fails. so i'm not sure how the crash reporter is registering the crash and traceback! [15:53] ondra: ah, brilliant, thanks [15:53] Chipaca, I've got bugs in my room/ears/pocket/shoes. Do I kill them? Become their friend? [15:53] cjwatson that was wortking since last release in june or when I did it [15:53] jdstrand, we run the click-reviewers-tools checks on uploaded pkgs, and need a way to mark pkgs that need manual review [15:54] kenvandine: correct, and it does! it's just that on the device it also crashes after the signal is sent ;) [15:54] pindonga: so, there are three types of output-- error, warn and info. manual review happens in error, but there are other errors in there [15:54] right [15:54] barry, so the crash happens if the download is already in /android/cache/recovery [15:54] i can reproduce that reliably [15:54] pindonga: so, you want to somehow display something different if there is only manual reviews and if there are errors? [15:54] jdstrand, so, my understanding was that erros requiring manual review were marked as (MANUAL_REVIEW) [15:55] jdstrand, however I now see there is another case (EMAIL NEEDS HUMAN REVIEW) [15:55] and it happens before i get the updateDownloaded signal [15:55] was wondering if there is a list of such tags [15:55] barry, it crashes very quickly... [15:55] kenvandine: the crash happens if a DownloadUpdate is called without a matching CheckForUpdate. i can reproduce reliably on my device too, i just can't see the process exit for some reason [15:55] or if we can maybe expand the error structure to include a 'manual_review': True in the json [15:55] instead of relying on these tags [15:55] barry, ok [15:55] I think that makes sense === kickinz1 is now known as kickinz1|afk [15:55] kenvandine: that makes sense. the validity check for the already downloaded files should be quick-ish. just checks some gpg sigs. if all that looks okay, it should send the UD signal rather quickly [15:55] the manual review tag [15:56] yeah, but i never get the signal [15:56] jdstrand, will work on an mp for that then [15:56] it just crashes while i wait for it [15:56] jgdx: I can't comment on what you choose to do in the privacy of your home [15:56] pindonga: cool, thanks! [15:57] kenvandine: okay, that part doesn't make sense ;) unless something about the device environment would cause the process to crash before dbus has a chance to put the signal on the wire. and that environment is different than the test suite [15:57] barry, ok, it'll take some time to get a build of this to test on the device, but this should fix some nasty conditions caused by system-settings at least [15:57] Chipaca, lol.. your comment reminded me of Pearl Jam – Bugs. A fitting song in these bug squashing days. [15:58] kenvandine: cool. i'm going to keep thinking about this. i think i need to know more about how the crash reporter is hooked into all this [15:58] Chipaca: so what's up? [15:59] barry: hiya. the other day a mock/testing system image service was mentioned, something about --testing=potato. There's an in-passing reference on https://wiki.ubuntu.com/ImageBasedUpgrades/Client but .. dunno more [16:00] jgdx: heh, i hadn't heard this. Nice. [16:00] barry: like, what is --testing an option of? [16:01] Chipaca: it's an option of /usr/bin/system-image-dbus but only if the system-image-dev package is installed, which it generally isn't on devices [16:01] barry: but it needs running as root? [16:02] later all [16:02] Chipaca: not necessarily. e.g. the s-i test suite runs all this stuff on private system buses [16:02] as $USER [16:02] barry: i need to run this stuff for testing the settings push helper [16:02] Chipaca: it's possible, but not currently *easy* to do the same outside the s-i test suite [16:02] augh [16:03] Chipaca: you might want to talk to kenvandine or other system-settings folks, because i'm pretty sure they run it with --testing in their test suites (at least, that's why i added it :) [16:03] so i might be better off mocking the bits i want to use myself [16:03] ah [16:03] kenvandine: well hello there :D [16:03] Chipaca: the trick is to start a private system bus via dbus-launch and then connect to that [16:04] Chipaca, off hand, i have no clue how we test that :) [16:04] i just recently looked at the update code for the first time [16:04] Chipaca: all the si test suite horribleness is here: http://bazaar.launchpad.net/~ubuntu-system-image/ubuntu-system-image/client/view/head:/systemimage/testing/controller.py [16:05] * barry thinks you don't actually need an ubuntu-download-manager process for --testing [16:05] yowza [16:05] Chipaca: welcome to the beauty that is dbus :) [16:06] and i'm sure it will all be easier when systemd subsumes dbus [16:06] [16:06] Chipaca: the real goodness is here: http://bazaar.launchpad.net/~ubuntu-system-image/ubuntu-system-image/client/view/head:/systemimage/testing/controller.py#L197 [16:07] that's what fires up dbus-daemon and sets the envar for the private system bus [16:07] Chipaca: but be aware, once you set $DBUS_SYSTEM_BUS_ADDRESS and initialize libdbus, you cannot change that value in process, which is why the si test suite goes to great lengths to only terminate the child processes, never dbus-daemon itself [16:08] Chipaca: because if dbus-daemon exited, the foreground test process could never reset the private system bus address and it would be beyond its event horizon ;) [16:08] * barry is getting an idea for a pycon 2015 talk ;) [16:09] barry: out of academic curiosity, is reload (imp.reload) smart enough to make that work again? [16:10] Chipaca: no because it's a libdbus problem, nothing to do with python, so i think once libdbus is dynamically loaded, it gets initialized once and for all in the process's address space. i don't *think* reload() will cause libdbus shlib to reinitialize, though i'm not certain about that [16:11] it would be a fun experiment === chihchun is now known as chihchun_afk [16:14] kenvandine, Chipaca i'm getting some lunch. bbs === chihchun_afk is now known as chihchun [16:22] seb128, can you do review? renatu has a packaging change that will add a NEW binary [16:22] https://code.launchpad.net/~renatofilho/ubuntu/utopic/ttf-ancient-fonts/fix-1269017/+merge/234013 [16:22] seb128, i looked it over and made some fixes already, which he merged [16:38] Does anybody know if 802.1x (WPA2 Enterprise) wifi authentication will be supported at launch date? [16:40] ogra_, you mentioned some bug with adb and having to change udev permission order -- what's the bug # for that? [16:41] mterry, that got immediately fixed i dont have a bug for it [16:42] ogra_, oh hrm. I'm having troubles adb'ing into a nexus 10 that appears to have developer mode enabled [16:42] ogra_, any other reports of tha? [16:42] *that [16:44] mterry, i was just looking into that and see it without even having the developer mode stuff installed ... in fact i dont even see anything in dmesg from USB on my PC after the device is running [16:45] i think this is not dev mode related [16:45] ogra_, oh so nexus 10 just isn't accessible for other peeps too? seems bad :-/ [16:45] we had to make some adjustments in the upstart job for supporting krillin ... i assime it is related to that [16:45] mterry, it is a bug ... and i will fix it [16:46] ogra_, ah but I can ssh in... [16:46] (its just not as high on my prio list as krillin or mako are thogh) [16:46] mterry, yes, if your key is on the device :) [16:46] people that did a fresh flash are a bit screwed [16:48] if you ssh in, you will see that adbd is running fine and that it is also properly set in the android properties ... [16:48] there is something low level broken [16:49] ogra_, haha! I'm in [16:50] :) [16:57]