=== Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === kgunn is now known as Guest14808 === jpyles is now known as jpy27 === _salem is now known as salem_ === Beldar is now known as Guest1917 === friendlyfascism is now known as Guest95256 === kgunn is now known as Guest35270 === salem_ is now known as _salem === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [06:47] morning dholbach ! [06:47] good morning [06:47] :D [06:50] hello popey === chihchun_afk is now known as chihchun === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [07:11] mzanetti: hey! you've submitted the upstream commit 'move loading of testability driver from QApplication to QGuiApplication'. now that our distro patch for tests enablement env var doesn't work anymore, could you potentially submit such a thing to the correct place? [07:11] mzanetti: it was originally at https://codereview.qt-project.org/#/c/63026/ - the last time I will submit a patch from someone else as mine, since it never really progressed :) [07:12] mzanetti: I guess for now, I can change the distro patch to add the same three lines in somewhere QGuiApplication instead [07:12] Mirv: wait [07:12] what do you want me to do? [07:13] mzanetti: if it's trivial for you, submit something similar to https://codereview.qt-project.org/#/c/63026/ but that applies to current dev [07:14] mzanetti: we have that as a distro patch (since that never went in), and I'm now trying to add the same environment variable support somehow to qguiapplication.cpp. but you would be better suited to answer any questions about the proposal. [07:15] hmm... am I? [07:15] :) [07:15] well, can try [07:15] mzanetti: considering you've touched the code in question, surely yes :) [07:15] Mirv: I never submitted this actually [07:16] I only added the -testability flag to QGuiApplication, as otherwise only QApplication loads it [07:16] but iirc I failed to get any reviewers for that too [07:18] mzanetti: moved, not added? https://codereview.qt-project.org/#/c/66513/ [07:19] so that got merged to 5.3.2, which is why the support for env var http://pastebin.ubuntu.com/8363327/ doesn't apply anymore [07:19] interesting [07:20] didn't know this got merged in the end [07:21] mzanetti: ah, I see, quite a gap in between proposal and merging :) so I was thinking about http://pastebin.ubuntu.com/8363333/ [07:22] yeah... I proposed this back I was in QA still [07:22] and I barely can remember it [07:22] ok. maybe I can just update my proposal (or, Thomi's, but he didn't want to submit to upstream) and see if it would progress this time. [07:22] Mirv: well... I guess I can try to... [07:22] mzanetti: you have much more credibility in there :) [07:22] hmmm? [07:23] I doubt that... but lets see [07:23] hi thomi :) [07:23] thomi: you remember https://codereview.qt-project.org/#/c/63026/ ? ;) [07:23] thomi: it's still a bit in progress! [07:23] thomi: so next time you get to submit patch yourself :) [07:23] I love fast, responsive upstreams! [07:25] mzanetti: actually, http://pastebin.ubuntu.com/8363356/ is more according to the comments received. the only problem was that there were two commenters and they had differing suggestions. [07:26] I'll leave it in your capable hands. [07:26] the other suggestion was to use qIsEnvironmentVariableSet("") instead [07:31] ok. I'll give it a try [07:32] thanks! [07:32] I can then eventually abandon my submittal === psivaa_ is now known as psivaa_-afk === VDVsx_ is now known as VDVsx === psivaa_-afk is now known as psivaa [08:35] right, loadTestability instead of load_testability, and I get a build even... [08:40] Good morning all; happy Country Music Day! :-D === vrruiz_ is now known as rvr [10:01] Hi all! I use adb push to copy translations (.mo files) to the device, but something changed and all I've got is an error messages: device offile [10:01] any idea? === chihchun is now known as chihchun_afk [10:06] romuill: adb is no longer available unless you set a PIN or passphrase and turn on developer mode (System Settings > About this phone > Developer Mode) [10:07] nhaines: I set a PIN code and activated Developer mode, but still got the error [10:12] tsdgeos: could you give unity8 some testing with https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-019 , or are you already running with the patch? [10:13] Mirv: i was already running with the patch [10:13] since yesterday [10:13] self compiled ftw [10:14] tsdgeos: ok, that should be then good enough for unity8. thanks. [10:16] Can somebody help me? I set PIN code and Developer Mode, restarted the device and I've got the same error: device offline. [10:41] I don't get which channel I need to provide to "ubuntu-device-flash" to get the rtm promoted image, any hint? :) === tvoss is now known as tvoss|lunch [10:56] ybon: ubuntu-touch/ubuntu-rtm/14.09 [10:56] ybon: try out ubuntu-device-flash --list-channels [10:56] it shows all available channels === MacSlow is now known as MacSlow|lunch [11:09] thanks nik90 :) [11:10] humm, Flashing version 1 from ubuntu-touch/ubuntu-rtm/14.09 [11:10] I thought it was #41 [11:10] hmm strange [11:20] ubuntu touch can i installing in any smart phone soon [11:22] yes for certain definitions of any === tvoss|lunch is now known as tvoss [11:25] help me can i root any smart phone on ubuntu [11:26] !devices | ahmed___ [11:26] ahmed___: You can find the full list of devices, official images, community images, and works in progress at https://wiki.ubuntu.com/Touch/Devices [11:26] that link tells you probably all you need to know [11:27] ubuntu supported tecno phone === gnu is now known as Guest13192 [11:48] nik90, around? [11:49] tvoss: hey, yeah [11:49] nik90, had a chance to test the silo? [11:49] tvoss: I wasn't able to install it :/ last nite...I am going to give it a shot again now [11:50] tvoss: strangely before the new adb stuff, I was testing silos perfectly fine [11:52] tvoss: I will report back with the testing results in about 15-20 mins..I just tried adding the ppa again and it seems to work with phablet-shell [11:55] nik90, ack === MacSlow|lunch is now known as MacSlow [12:11] nik90: you can manually add ppa's by adding the lines to /etc/apt/sources.list.d/foo.list if add-apt-repository is busted [12:11] popey: yes. I tried add-apt-repository again and it seemed to work with phablet-shell. [12:12] ok === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === kgunn is now known as Guest35530 === _salem is now known as salem_ [12:51] Anyone have a good way to layout to dialogs that become really long? [12:51] Dialogs does not seem to currently handle many stacked items at once. [13:01] tvoss: hey it doesn't seem to work [13:01] nik90, some more detail would be appreciated : [13:01] ) [13:01] tvoss: in the process of explaining :) [13:02] bfiller: hey! [13:02] tvoss: I clean wiped my phone and then installed a new clock package with some console debug statements. When I open the clock app, I got the location trust store prompt. I deliberately pressed Deny. However the source error output shows "No Error". [13:03] tvoss: I used the following code to print out the source error for different conditions http://paste.ubuntu.com/8364914/ [13:03] nik90, okay, let me see [13:03] Is there any reason why i should keep a bug reported against indicator-network via apport-cli private? (eg sensitive info in there?) or do all apport bugs go private first? [13:04] ahayzen: the latter; if you vet the stack trace or other info that it doesn't have sensitive, it's fine to make it public === Ursinha is now known as Ursinha-afk [13:04] tvoss: I have a test branch at lp:~nik90/ubuntu-clock-app/implement-location-finding [13:04] pitti, ok thanks :) [13:04] ahayzen: like your wifi passwords or so (unlikely for the indicator) [13:05] pitti, heh === Ursinha-afk is now known as Ursinha [13:10] nik90, ah, interesting [13:11] nik90, so, in the qtlocation source package: The error is initalized to NoError and not initialized with the error from the actual position source in qdeclarativepositionsource.cpp [13:11] nik90, I set the error at construction, at which time I cannot emit a signal [13:11] tvoss: oh [13:12] or better: I can emit a signal, but no one will be connected [13:12] kalikiana, could you help out in patching the src package? [13:15] kenvandine, hey, silo 1 from yesterday tested fine, btw. [13:18] kenvandine, hi [13:19] jgdx, thx! [13:19] hey gatox [13:19] gatox, can you review https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/update_mgr_singleton/+merge/234420 [13:20] kenvandine, hello... i was wondering if you could help me with something.... i have always have trouble trying to tests my system settings branches in the phone..... and i was wondering how are you doing it, to see if maybe you are doing something different..... because i waste a lot of time to try to get this to build and test it [13:20] jgdx, i decided to hold off on the api bump branch, until we're sure the testplan is accurate [13:20] kenvandine, sure [13:21] gatox, sure... "testing" you mean finding updates to test? [13:21] not building it for the phone... [13:21] i wait for CI to build for me... which sucks [13:21] but to get updates, i figured out a nice trick [13:21] kenvandine, nono..... that part i can do it..... i mean run my branch on the phone [13:21] i unregister the latest version of some clicks :) [13:21] ah... [13:21] kenvandine, so..... waiting for CI and then installing the deb? [13:21] that's hard.. [13:21] i wait for debs [13:21] yeah [13:22] i've spent so much time trying to get cross builds that work... and gave up [13:22] kenvandine, ack. Get a look at the wifi branch? I've identified some issues, but the main lines seems to work. [13:22] kenvandine, yes!! me too...... [13:22] gatox, kenvandine me too [13:22] jgdx, :( [13:23] there is something really wrong with that :S [13:23] I'll buy anyone who fixes that five beers [13:23] jgdx, the dialog branch right? [13:23] kenvandine, yesh [13:23] i didn't get to look at it yet.. sorry [13:23] i'll do that this morning [13:23] kenvandine, np. Thanks [13:23] gatox, so my branch fixes keeping the updates available count in sync with the updates page [13:24] it doesn't fix the issue with having it find updates after starting and changing visibility [13:24] i have a hack in there to use a timer, and do the checkForUpdates after 60s, but only if the model is empty [13:24] but i disabled it for now [13:24] kenvandine, i'll review it now [13:25] i figure with the timer, if you go into the updates page it'll populate the model and so we don't need to do it on start in the entry on the main view at all [13:25] and it'll show up if you initiate a check on the updates page or about page [13:26] but... for now i disabled the timer and have it check at start to match the current behavior === dandrader is now known as dandrader|afk [13:26] at least it fixes the count not matching the updates bug [13:26] gatox, do you think you could add some transition magic to the "Updates available?" As a heavy Ubuntu System Settings user, I often mispress due to it's sudden appearance. :P [13:26] s/it's/its [13:26] and i'll get some feedback from design on what to do at start [13:26] jgdx, we're going to resolve that :) [13:26] wee [13:26] that's what i was just talking about :) [13:27] i experimented with deferring the check so it doesn't show up quickly [13:27] the transition as well? nice [13:27] and chances are when you go into settings, you'll probably navigate into another page within 60s [13:27] welllll [13:27] so you won't even see it when it appears, but it'll be there when you come back [13:27] what if I see the badge and want to install the updates? [13:28] i know that's a hack too... but i figure it's better than what we have now [13:28] that takes you right to the updates page [13:28] actually... [13:28] the notification does [13:28] i don't know what happens from the launcher with the badge [13:28] you just launch uss [13:28] if you open it from the push notification it takes you right to updates [13:29] right, that's good [13:29] tvoss, nik90: so this is a qtlocation distro patch? [13:30] you want a s-i-dbus API which tells you if it already knows about an update without doing any remote operation [13:31] Laney, yeah, so right now we get an updateAvailableFound signal pretty quickly after doing the start [13:31] but not quick enough [13:32] yes, I think you want a method [13:32] a sync method? [13:32] I imagine you'd call it synchronously [13:32] but that method would need to happen outside of the plugin then [13:32] in whatever loads the entries [13:33] i think what we really need is to drop the entry complete and add a badge to the updates icon in the grid [13:33] why's that? [13:33] battery plugin does something like this [13:33] because of the dynamic visibility [13:34] the loader needs to determine visibility before it loads the plugin [13:34] or it'll load invisible until we toggle it [13:34] which is what happens now [13:34] it's done in the constructor which is blocking (AFAIK) [13:34] for battery [13:34] there's no jumping around there [13:35] i'll look at that [13:35] oh... i see [13:35] so in the constructor we call a sync method to set visibility [13:35] right [13:35] the behaviour you want is "do you already know about an update?" I think [13:36] not "go and find out if there is one" [13:43] kenvandine, +1 looks good [13:43] gatox, thx [13:44] kalikiana, it would be in the worst case, just looking through the other plugins in the source package [13:46] bfiller: so, we noticed that dialer-app is failing in ubuntu-rtm smoketesting for both mako and krillin [13:47] sil2100: ok we'll take a look [13:48] bfiller: thanks :) [13:48] sil2100: might be related to this regression with snap deciosins https://bugs.launchpad.net/ubuntu-ux/+bug/1368862 [13:48] Launchpad bug 1370240 in QtMir "duplicate for #1368862 Clicking a snap decision button makes the foreground application inactive" [Critical,New] === dandrader|afk is now known as dandrader [13:51] sil2100: can you point me at the failures? seeing a lot of failures on dashboard across the apps. want to make sure I'm looking at the right links [13:52] bfiller: sure, for instance here: http://ci.ubuntu.com/smokeng/utopic/touch_stable/mako/42:20140917:20140903.1/10510/dialer_app/ [13:55] sil2100: thanks [13:57] anyone know why i wouldn't be able to flash my nexus4? i keep getting errors about cache formatting or recovery image [13:57] like: 2014/09/17 09:48:56 Cache formatting was not successful, flashing may fail, check your partitions on device === Guest35530 is now known as kgunn [14:00] 2014/09/17 09:59:53 Cannot cleanup /cache/recovery/ to ensure clean deploymentexit status 255 [14:00] now that [14:00] i am lost :( [14:05] salem_, Hi! [14:05] salem_, did you look at bug 1370106 yesterday ? [14:05] bug 1370106 in telepathy-ofono (Ubuntu) "telepathy-ofono crashed with SIGSEGV in ~QString()" [High,New] https://launchpad.net/bugs/1370106 [14:06] om26er, sorry, I read the bug report but didn't have time to actually work on it. [14:07] salem_, can you look at that now, please. [14:12] 2014/09/17 10:12:05 Cannot push /home/dobey/.cache/ubuntuimages/pool/ubuntu-cbe7b905c3a6b174f5e650d248091dbb6d69a7ed68d2be650d4495f6cbaa1a4a.tar.xz.asc to device: free space on /cache/recovery is unknown [14:12] om26er, yes, just need to finish something else first. [14:12] what does that mean? [14:12] salem_, ok, btw I faced the crash again today :) [14:15] searching for the "free space on /cache/recovery" on ddg just gives me links to unanswered questions on askubuntu :( [14:18] wtf [14:25] if i try to adb push the ubuntu or device tar.xz, it just exits with no info at all. but the files aren't on the phone [14:30] so many new goodies in r243! [14:32] 2014/09/17 10:32:12 Cache formatting was not successful, flashing may fail, check your partitions on device [14:33] how the heck can i get ubuntu back on this mako? [14:34] E:Can't mount /cache/recovery/ubuntu_command [14:35] weird [14:35] why is it trying to mount logs and such [14:37] jdstrand, Hi! [14:40] jdstrand, can you please look at bug 1369512 ? [14:40] Error: Could not gather data from Launchpad for bug #1369512 (https://launchpad.net/bugs/1369512). The error has been logged [14:45] jgdx, the dialog sizing when the OSK shown is awkward [14:46] whee, and now it's stuck at the android bouncy balls boot screen [14:46] jgdx, but i'm not sure what we can do about that when using a dialog [14:46] kenvandine, yeah, it's really bad. [14:46] it is... [14:46] without the OSK it's nice :) [14:46] sigh... [14:47] we must have prior art for this [14:47] oh... look at the dialogs used in the various pin setting/changing pages [14:47] i think there is some hacks in there from mterry to adjust the size so they fit better [14:47] kenvandine, I did, but can't see an immediate solution. It's just too long. [14:48] i copied/pasted his hacks :) [14:48] :) [14:48] well if the dialog stays above the OSK, at least it can scroll [14:48] yeah I just shrunk the spacing :( [14:48] mterry, ok... so probably not enough for what we're doing [14:48] rsalveti, Hi! you work on powerd, right ? === nik90_ is now known as nik90 [14:48] jgdx, Wellark, abeato: I’m testing bug 1356239 and I notice that the IP address is in an editable text field. That isn’t right, it is? You can’t change your IP address just by editing a field [14:48] bug 1356239 in Ubuntu UX "Can't see device's IP address or MAC address" [High,Fix committed] https://launchpad.net/bugs/1356239 [14:49] om26er: I did a few patches, yes :-) [14:49] om26er: what's up? [14:49] kenvandine, how big is your dialog!? [14:49] rsalveti, sometimes auto-brightness stops working and when I dial a call the screen does not turn off when I bring it near my ear. [14:49] mpt, is it editable? Can you type in stuff? [14:49] that's on mako. [14:49] mpt, no, you can't change the ip. [14:49] mterry, it's for connecting to a hidden wifi AP [14:49] rsalveti, My device is currently in that state, but powerd seems to be running fine i.e. didn't crash. [14:49] so varies [14:50] jgdx, huh, my mistake, the cursor flashes but I don’t get a keyboard [14:50] I guess that’s a toolkit bug [14:50] om26er: hm, but probably in a broken state, as it's the one responsible for the proximity sensor [14:50] mpt, but right, that field isn't up to spec. [14:50] rsalveti, any logs that I could gather, right now ? [14:51] om26er: is it at least shutting off the screen after the call? (after the 60s timeout) [14:51] rsalveti, didn't try that but the screen does turn off on its on if I leave the device. [14:51] want me to test that ? [14:52] no, that means the basic things are working, can you start up another voicecall to see if proximity is still broken? [14:52] wonder if this was a side effect of another bug we had in mediahub [14:52] mpt, fyi I have a branch coming up fixing the broken "Disconnect" behaviour in that same page. [14:52] that was leaving a suspend blocker and the screen was always on after that [14:53] mpt, not sure if you filed a bug or not? /me looks [14:53] om26er: see if you can find a way to reproduce the issue, and please open a bug against powerd, adding your syslog and steps [14:53] om26er: and tag it to rtm14 [14:53] jgdx, this is the first time I’ve seen this screen, so no :-) [14:53] rsalveti, the proximity sensor is not working. [14:54] rsalveti, the problem is random though. saw that twice in a week. [14:54] mpt, ah [14:54] om26er: can you give me the output of 'powerd-cli list'? [14:54] yeah, it could be many things =\ [14:54] rsalveti, System State Requests: [14:54] None [14:55] the screen does turn on on incoming calls [14:55] right, then just the proximity that might be broken [14:55] maybe the sensor is not giving the right output, or a bug in powerd itself [14:55] jgdx, so I guess as long as bug 1286282 isn’t fixed, a read-only text field is the only way of making the value copyable? [14:56] bug 1286282 in ubuntu-system-settings (Ubuntu) "No way of copying system details from ListItem elements" [Wishlist,Triaged] https://launchpad.net/bugs/1286282 [14:56] om26er: done [14:58] mpt, I could not find other ways, no. It could/will be styled to look like a listitem value, though. [14:58] jdstrand, it started happening recently, was there any policy change ? [14:59] jdstrand, 3 apps are affected. [14:59] mpt, correction, will. [14:59] no policy change. perhaps an underlying change to mediahub [14:59] jdstrand, and the apps are trying to access the camera flashlight [15:00] om26er: that might be related. jhodapp, can you comment on that ^. torch apps wanting to use the camera flash light are requiring access to media-hub [15:01] jdstrand, that's weird...are they trying to play audio? [15:01] jdstrand, my guess is they have an Audio element in their QML [15:02] om26er: I will have an update to the camera policy group that allows access to the media-hub, but I'm surprised they need to talk to media-hub if they are only using the camera flash [15:02] om26er: can you respond to jhodapp? [15:03] jhodapp, jdstrand I don't think so. they are very simple apps, no sound [15:04] they'd have to, otherwise they shouldn't be getting media-hub [15:04] media-hub does nothing with the camera yet [15:04] I have one of those on the phone [15:04] let me look [15:05] om26er: is com.ubuntu.developer.majster-pl.utorch one? [15:05] jdstrand, the code for utorch is in lp:utorch if you want to inspect [15:05] jdstrand, yes === kgunn is now known as Guest81961 [15:07] jhodapp: grep -ri audio ./* shows nothing [15:07] nik90, mind updating [15:07] jhodapp: I'm guessing it is: [15:07] Camera { [15:07] id: camera [15:07] flash.mode: utorch_main.torchOn ? Camera.FlashVideoLight : Camera.FlashOff [15:07] } [15:07] tvoss: sure [15:08] jdstrand, oh I know why, because the click sound for camera is in qtubuntu-camera, which using the Camera object in QML would utilize [15:08] jdstrand, the real bug seems to be that we need to move the click sound out of qtubuntu-camera, and let each app play a click sound if they need it [15:09] yeah, that makes sense [15:09] tvoss, what do you think, this is a design/architecture decision ^ [15:09] tvoss, see my last comment about moving the click sound out of qtubuntu-camera [15:10] jhodapp, +1, if apps want, they can use QML's audio {} [15:10] this would also address the tagger and authenticator apps [15:10] indeed [15:10] jamesh__, Hi! [15:10] tvoss, ok thanks, I agree [15:10] which, I have not uploaded that policy yet [15:10] nik90, thank you [15:12] jhodapp: so, based on your previous comment that actual access to the camera will be handled via media-hub, seems I should still upload my policy change for camera [15:12] jdstrand, which change exactly? [15:12] jdstrand, will that fix the apps not starting issue ? [15:12] jhodapp: but, in the future when apps want the click sound, they'll need to add the audio policy group [15:12] jdstrand, agree with that [15:12] jamesh__, can you please look into bug 1369539 [15:12] bug 1369539 in mediascanner2 (Ubuntu) "mediascanner-service-2.0 crashed while creating thumbnails" [High,New] https://launchpad.net/bugs/1369539 [15:14] jhodapp: the change to camera policy group: [15:14] +dbus (receive, send) [15:14] + bus=session [15:14] + path=/core/ubuntu/media/Service{,/**}, [15:14] om26er: it should, yes [15:14] jdstrand, ah right, sounds good to me [15:15] jdstrand, should I move the bug to apparmor ? [15:18] nik90, any luck? [15:19] tvoss: I just ran apt-get update and then dist-upgrade. But I don't see any new qtlocation or platform-api packages. [15:19] tvoss: I see qtubuntu-sensors though [15:19] is that it? [15:19] rsalveti, Can you tell if bug 1370091 is pulseaudio ? [15:19] bug 1370091 in pulseaudio (Ubuntu) "With music playing, pressing the dialpad keys reduces the volume for an odd interval" [Undecided,New] https://launchpad.net/bugs/1370091 [15:19] hey just coming back from abroad and still facing this bug. https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1323837 . I would like to know if there was some little terminal hack which would let me enable my network from the phone. I am stuck with a useless phone every time i leave the UK and i have to ask my girlfriend for her phone to enable my simcard. [15:19] Launchpad bug 1323837 in unity8 (Ubuntu) "Sim toolkit is not available on UT" [Wishlist,Triaged] [15:21] om26er: it's not, but let me update the bug [15:21] nik90, our qtlocation plugin is part of qtubuntu-sensors [15:21] tvoss: ok..2 mins then :) [15:21] nik90, ack [15:22] om26er: can you better describe why do you think it's currently broken? [15:22] om26er: just updated the bug [15:24] om26er, jhodapp: I rearranged bug #1369512 a bit for this [15:24] bug 1369512 in apparmor-easyprof-ubuntu (Ubuntu) "please move click sound out of qtubuntu-camera" [Critical,In progress] https://launchpad.net/bugs/1369512 [15:24] jhodapp: I assigned you to the qtubuntu-camera task, but feel free to adjust [15:24] jdstrand, that's perfect...can you tag that for rtm14 and for the 25th milestone? [15:24] jhodapp: I did just now [15:25] rsalveti, I think I was expecting the audio to fade-out/fade-in instead of just reducing down and increasing at once. And then the time after which it is turn-up is a bit long that I would expect. [15:26] om26er: right, that's because it takes a while for the dtmf stream to go off [15:26] jhodapp: there is a media-hub project task. I am unable to remove it [15:26] om26er: that can probably be worked on [15:26] om26er: yeah, the fading is not yet supported, but I know it's indeed a bit annoying [15:27] rsalveti, when I reported I was in a silent room with music at full so it annoyed me when it turned down and then came back to loud noise. I agree fading will make it better. [15:30] tvoss: bah my dist-upgrade is installing all sorts of language packs and generating locales for every one of them which is taking time :P. .will ping when ready [15:32] dont use dist-upgrade on phones ! [15:32] om26er: thanks for the bug report, will try to take a look at that hopefully soon :-) [15:33] after the critical bugs are gone [15:33] ogra_: I had to after installing a silo to install packages from the PPA :) [15:33] rsalveti, thanks [15:33] ogra_: or did you mean I should use apt-get upgrade instead? [15:33] barry, how would you feel about adding a synchronous method to system-image-dbus that i can call to see if there is already a known update? [15:33] nik90, evem then, dont call dist-upgrade [15:34] nik90: just install the silo packages it it safer [15:34] nik90, no, upgrade only refreshes the package lists [15:34] barry, just returning a boolean and i can wait for UpdateAvailableStatus to get the details [15:34] nik90, what davmor2 said ... apt-get update and then apt-get install the silo packages individually [15:34] davmor2: yeah I realise that now after all these locale generations which it has been doing for the past 10 mins [15:34] kenvandine: you mean like Information()? `man system-image-dbus` :) [15:35] ogra_: ack. [15:35] if it would only locale generations :) [15:35] *only be [15:35] kenvandine: hmm, well, that doesn't give exactly whether there's a known update but it was added to provide a last check date [15:35] barry, that returns if there is a known update? [15:36] kenvandine: that isn't really possible because trying to figure out if there is an update available requires a check with the server, which can be slow, so must be async. [15:36] i need to determine if the updates-available entry needs to be visible or not when the main view loads [15:36] ogra_: :) [15:36] why? [15:36] barry, if we already have an emblem on the launcher, that there is an update available [15:36] s-i-d should know without doing a check right? [15:37] barry, right now in that scenario, we get the updateAvailableStatus signal quickly, which is good... but we can't block loading of the entry on that [15:37] kenvandine: no, i don't think so. it has to check with the server, get teh blacklist keyring, check the signatures etc [15:38] barry, i need a really quick check to see if we already know === gnu is now known as Guest50222 [15:38] kenvandine: so the response would be: 1) yes, there is at least an update available, but it might not be the latest; 2) i can't tell, i have to check the server [15:39] right, but not do the check [15:39] unless i ask [15:39] kenvandine: asking would be calling CheckForUpdate [15:39] right [15:40] tvoss: ping (good and bad news) [15:40] barry, i'll call the checkForUpdate a little later [15:40] nik90, shoot [15:40] kenvandine: right now, we don't cache the information about whether an update is available, so that would be a new feature request. i would have to think about it some more, do some experiments, etc. could you open a wishlist bug on system-image (upstream)? [15:40] but i want to determine visibility on load [15:40] barry, so what adds the emblem to the launcher icon? [15:41] tvoss: so the good news is that when I "deny" clock app access in the location trust store, then it shows the correct source error "do not have permissions to access service...". [15:41] kenvandine: i'm not sure since i don't know the system-settings code, but i do believe they call CFU and wait for the UAS signal [15:41]