=== vying is now known as Guest93059 [02:31] mhall119: that problem is the next in the pipeline. We are working on the wizard to help developers to set up their chroots and eulators on the first SDK start and on the project opening. === _salem is now known as salem_ [03:30] mhall119, media-hub makes the call to powerd to keep the screen turned on during video playback === cul_ is now known as cul [04:10] achiang: hey Alex [04:10] pitti: guten morgan [04:10] morgen? [04:11] achiang: thomi says you had a question about whoopsie? (not my biggest area of expertise, but maybe I happen to know) [04:11] achiang: "Morgen", yes :) [04:11] ahh, German and their love of Capitals For Every Noun :) [04:11] thomi: awfully nice when you're learning it though. :) [04:12] nhaines: Just Capitalise All The Things! [04:12] pitti: we thought that whoopise should display an oops id in syslog, but no one could find it yesterday [04:12] pitti: the goal was to be able to find app crash reports on errors.ubuntu.com [04:13] achiang: try /var/log/upstart/whoopsie.log? [04:13] my /var/log/upstart/whoopsie.log.2.gz has [04:13] Uploading /var/crash/_bin_dash.1000.crash. [04:13] Sent; server replied with: No error [04:13] Response code: 200 [04:13] Reported OOPS ID 4e11e74c-1706-11e4-b105-fa163e22e467 [04:14] pitti: thanks. thomi - we are officially dumb! [04:14] heh [04:14] achiang: don't worry -- this changed just a few days ago [04:15] achiang: do you know about the errors.u.c. link that shows all your reports? [04:16] achiang: control-center -> Security & Data protection -> Diagnosis -> Show earlier reports (freely translated from German, YMMV) [04:18] pitti: very neat. thanks [04:19] pitti: it asks me to login? [04:19] achiang: yes, it's a per-user page, and crash reports are sensitive [04:19] pitti: makes sense. i'll log in later when i feel like opening lastpass on my desktop and typing in a 20 char modem noise ;) === chihchun_afk is now known as chihchun === chriadam is now known as chriadam|away [06:15] pitti: hi, ok i'm ready to start tracking down some crashes... i logged into errors.ubuntu.com, but can't find the oops? [06:16] http://pastebin.ubuntu.com/7911732/ [06:16] achiang: that's now something for bdmurray or ev, I'm afraid [06:16] pitti: fair enough. i should sleep then :) [06:17] pitti: do you know how to analyze it locally? [06:17] achiang: you can install apport-retrace on the device [06:18] achiang: then you can either use the apport-retrace command or pick "analyze locally" in the apport-cli menu [06:18] that will give you the option to retrace the .crash, or toss you into an interactive gdb session, both with all debug symbols [06:18] pitti: will it work on an amd64 host if i adb pull the crash log? [06:19] achiang: retracing yes; interactive gdb, no; but you need to collect the info through apport-cli [06:19] i. e. apport-cli foo.crash, show the details, then save [06:19] i. e. the .crash file needs to have "Package:" and "Dependencies:" [06:20] pitti: ok, thanks. i do indeed see a stack trace on my host [06:53] good morning [07:00] dholbach: good morning! [07:00] hi nhaines === salem_ is now known as _salem === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [07:38] ogra_: hey Oli, guten Morgen [07:38] ev, ogra_: so on a freshly installed mako, /var/lib/apport/autoreport does not exist, and thus apport doesn't auto-upload [07:38] I suppose that flag file should be created during image build? [07:39] was that changed recently? (I just flashed 162, with complete wipe) [07:43] nope [07:44] pitti, so i guess we need a livecd-rootfs hook then [07:44] mardy, ping [07:44] ogra_: I'm not sure how this is designed to work; it must be changeable from the privacy settings, thus be a writable file; so it's either image build or the first-time wizard? [07:45] ev: do you know what the design was for /var/lib/apport/autoreport? i. e. when/where to create/change it? [07:45] should be at image build [07:46] Yeah, it should be there as part of the image and deleted/recreated by the preferences page or the first use wizard. [07:46] That was the intent anyway [07:48] pitti, maybe it is not created by the wizard because it crashes [07:50] i'm not so sure the wizard creates it at all [07:51] i have an install here sitting on build 111 ... that didnt have a wizard, the dir is writable and the file exists [07:52] I just flashed 162, and it's not there [07:52] i dont see what would have initially created it though (and this istall never had the GUI used) [07:53] speaking of which, I just uploaded the three crashes which are there after a fresh install (upstart, the wizard, url-dispatcher) [07:53] ev: is there any way to go from https://errors.ubuntu.com/oops/e57a4008-1886-11e4-a5f7-fa163e4ccdf2 to the "bug" page? [07:54] I puzzled together this URL from /var/log/upstart/whoopsie.log === psivaa is now known as psivaa-brb [07:57] pitti: no, because it has a corrupt stacktrace. It can't generate a signature, so there's nothing to bucket against or link a bug to. [07:58] ev: ah, ok; usually there would be a link somewhere? [07:58] ev: so even after the recent apport and ddeb fixes we still can't retrace? :/ [07:59] You should be able to go from crash instance to bucket to bug by clicking successive links, yes. [07:59] Not all retracing on armhf works yet, but bdmurray and team are making good progress. They have graphs [08:03] pitti: if you still have the .crash it might make a good test case. [08:07] ev: yes, they are on my u phone [08:11] plars, poke when you're awake -- I'm going to see if I can reproduce that unlock failure [08:13] ogra_, pitti I filed bug 1350722 [08:13] bug 1350722 in livecd-rootfs (Ubuntu) "/var/lib/apport/autoreport doesn't exist on freshly installed phone" [Undecided,New] https://launchpad.net/bugs/1350722 === psivaa-brb is now known as psivaa [08:35] seb128, bug 1350734 is for your team ? [08:35] bug 1350734 in ubuntu-system-settings (Ubuntu) "system-settings-wizard crashed with SIGSEGV" [Undecided,New] https://launchpad.net/bugs/1350734 [08:39] dholbach: hey :) I'd really like to get the scope publishing thing figured out asap [08:40] jibel, no [08:40] jibel, it's for kevin or pat's teams [08:40] pat owns settings [08:40] seb128, ok, thanks [08:40] dholbach: I'm happy to do any code changes to the review tools, I just need to know what the rules should be [08:40] but in practice mterry did most of the wizard work [08:41] seb128, yeah, that's what confuses me [08:41] pete-woods, let me take a quick look [08:41] thanks! [08:41] seb128, jibel: marked as dup of bug 1335298 [08:41] bug 1335298 in ubuntu-system-settings (Ubuntu) "ubuntu-system-settings-wizard crashes on stop" [High,Triaged] https://launchpad.net/bugs/1335298 [08:42] jibel, I have some ideas of what causes it, but haven't tracked it down yet. Note that the crash isn't why you see the spinner -- that's expected regardless [08:42] dholbach: I think it's only chance that makes the current system work. It basically checks whether lists.ubuntu.com (email) is >= appname.ubuntu.com (package name) [08:42] which seems like a totally arbitrary check [08:46] it seems like all the special case checks should happen inside the check: [08:46] elif domain_rev == pkg_domain_rev[:len(domain_rev)]: [08:48] Elleo, did you see any improvements with the last udm? [09:05] Good morning all; happy Uncommon Instrument Awareness Day! :-D === renato is now known as Guest78593 === Guest78593 is now known as renatouy === renatouy is now known as renatou [09:17] mdeslaur, oh by the way -- on the topic of pam_tally2... it doesn't provide any feedback at all that a UI might consider useful. Things like "X more failures before something bad happens" or "adding a delay because of too many failures" or some such. In order to implement the design for wipe-after-too-many-fails, I would need to know that "one more failure is bad" and even to make a delay after 5 failures look nice, it would be good to know [09:17] that's why PAM is taking a bit to respond, so we can tell the user. Are we wedded to pam_tally2 vs a tally that the greeter keeps track of itself? [09:20] pete-woods, jdstrand: https://code.launchpad.net/~dholbach/click-reviewers-tools/scope-email/+merge/228993 [09:21] pete-woods, do you know if anyone did a security review of the particular scope? [09:24] dholbach: no, so far it's just me who's looked at it [09:25] well, looked at == wrote [09:25] pete-woods, because for 'accounts' we currently require reviews [09:25] sorry, I mean for the security policy group [09:25] dholbach: sure, that makes sense [09:26] pete-woods, is 'accounts' necessary in this case? [09:26] dholbach: well you're supposed to be able to log into your google account [09:26] and use your credentials for video recommendations, subscriptions [09:26] ah ok, that makes sense then [09:27] dholbach: although technically that functionality isn't complete yet in the scope [09:27] but I need to finish it soon! [09:27] in that case it might be easier to get the scope in now without 'accounts', ping the security team in the meantime and add the security policy group later on? if that makes sense [09:28] dholbach: if I get it reviewed this time, will it keep needing to be security reviewed in future? [09:29] pete-woods, I don't think that's what happened with the core apps [09:29] dholbach: it might be sensible to get it approved this once, assuming it doesn't take days for the review [09:29] it basically wants read-only access to the user's youtube account [09:31] pete-woods, with nobody of the security team here to give guidance, would it be possible to upload the scope for now without 'accounts' and then figure out the details with Jamie or anyone else later on? [09:31] I wouldn't like to override the security team's request just now [09:31] dholbach: okay, that works for me [09:32] pete-woods, thanks a bunch! [10:32] dholbach: just wanted to check if there was anything else you wanted me to change for the youtube upload? (if you're busy with other stuff, then sorry for nagging) [10:45] pete-woods, no, it should just be the security policy [10:47] cool, well 1.0.3 has that change, so hopefully that is all good then :) [10:50] pete-woods, approved [10:55] :D [10:55] Saviq, after your last e-mail on ubuntu-phone I can't stop thinking of http://i.imgur.com/SYcnzPL.jpg [10:56] Elleo, hello! did you get my message last night? [10:56] Elleo, were you able to test the udm bins? [11:03] dpm, ;) [11:12] mterry: can't the greeter use the tally2 database to figure that information out? [11:13] mdeslaur, it could use the pam_tally2 executable, yes... [11:14] mterry: no, I mean use pam_tally2 with pam, but then look at the database to figure out how many tries are remaining, etc. [11:14] mdeslaur, database is binary, only API is the executable [11:14] I gather we also need to display something like "your phone is locked for 5 minutes" [11:15] mdeslaur, I don't think it gives that sort of information though (about what the configuration is) [11:15] mdeslaur, that would be nice [11:16] mdeslaur, to do this via pam_tally2.so, I think we'd need two bits of info -- what the configuration is (parsing pam.d files) and what the current tally is (parsing pam_tally2 output) [11:16] We could maybe get away with *assuming* the config, but seems fragile [11:16] the reason I wanted it to be done with pam is so that we get the same restrictions when using ssh or adb [11:17] but I guess if the screen is locked, adb doesn't answer, so maybe we don't care [11:18] mdeslaur, is there any PAM api for the config? [11:18] * mterry doesn't want to bother following pam.d include directives and all that [11:18] seems like madness [11:19] hrm, probably not [11:19] perhaps it would be better to implement it in the greeter after all [11:19] I suppose for some features, like wiping your phone after X tries, pam_tally2 doesn't even have a config [11:19] But we could use a proxy value like "lock phone for 365 days" as a code for that === MacSlow is now known as MacSlow|lunch [11:20] does pam_tally2 provide any sort of feedback that the phone will be locked for 5 minutes? [11:20] mdeslaur, this is not the first time I've wished PAM was much more expressive and let modules feed back hints to the UI. Things like display hints for a pin vs password would be lovely [11:20] mdeslaur, when I did a quick test, it just seemed to silently deny [11:20] ugh [11:21] I think not telling the user their phone is blocked is pretty much a showstopper [11:21] mterry: what do you think> [11:22] mdeslaur, I am sympathetic to wanting it in PAM (that way we also affect anybody brute-forcing on command line). But I don't think pam_tally2 is going to give us the info we want [11:22] yeah [11:22] that would have been too easy :) [11:23] mdeslaur, I can put the value in AccountsService (this is what I was going to do for wipe-logic). For pre-split-greeter, we can allow user access to the field, but post-split-greeter, we can deny them write access to the failed-login count [11:23] so...for an ideal situation...1- we write our own pam module that has a helper that the user can interrogate or 2- we implement it in the greeter [11:24] mdeslaur, true, I hadn't considered writing a PAM module [11:24] for the phone, it can be in the greeter [11:24] but at some point, we may want to move it [11:25] mdeslaur, we could fork pam_tally2 and add an associated daemon? [11:25] once we become more converged [11:25] mdeslaur, or patch pam_tally2 [11:25] to feed a new daemon the info it needs [11:25] yeah [11:25] mdeslaur, but yeah I'm selfishly interested in a quick and dirty solution for now... [11:25] or at least store the current settings along with the status in whatever database file it uses [11:26] and then accountsservice could be extended to read that database file for interrogation [11:26] mterry: but I'm ok with having it in the greeter for now [11:26] mterry: if that's what you mean [11:26] mdeslaur, yeah that was my quick and dirty === tvoss is now known as tvoss|lunch [11:27] we need to discuss all the authentication bits more thoroughly post rtm and converged [11:27] anyway [11:27] mdeslaur, keep config in greeter, store tally in a private AccountsService field, and we could change in future easily enough. If we ever change the tally backend, it's not the end of the world to wipe the tally count [11:27] yeah, no big deal [11:28] I'm don't think using dbus and stuff from a pam module is a sane thing to do [11:28] but we can figure it out then [11:28] and like you say, even if we change, losing count is no big deal [11:28] mdeslaur, well when we write a pam module for this, we don't need to go via AS [11:28] mdeslaur, but I thought some pam modules already use DBus? [11:29] * mterry can't remember which [11:29] do they? maybe [11:29] mdeslaur, the pam module that GNOME wants to write for PIN support would I think, if I read their plans correctly. [11:29] mdeslaur, maybe existing ones don't [11:29] well, I did say sane :) [11:29] heh [11:30] mdeslaur, OK thanks for the discussion [11:30] * mterry goes ahead [11:30] cool, thanks mterry === greyback is now known as greyback|away === chihchun is now known as chihchun_afk === alan_g is now known as alan_g|lunch === tvoss|lunch is now known as tvoss [12:18] mandel: do you work on powerd? (specifically bug 1342351 is looking for someone to triage) [12:18] bug 1342351 in Ubuntu Music App "Music Player won't advance to next song if screen is blank and device is unplugged" [Critical,Confirmed] https://launchpad.net/bugs/1342351 [12:20] ogra_, did the lxc-android-config change you helped me with yesterday make it into 161 or 162? [12:21] jhodapp, http://people.canonical.com/~ogra/touch-image-stats/ shows it in 161 [12:21] ogra_, I guess I can find out, updating right now [12:21] perfect, I'll double check it [12:32] pete-woods and dholbach: so, accounts is a reserved policy group right now and not available to app developers. it is allowed for Canonical employees, so I don't have a problem letting it in if this is a Canonical supported scope. that said, accounts should become a common policy group as soon as mardy's online accounts/trust session work is done [12:32] and that is currently supposed to happen for rtm [12:32] jdstrand: cool, thanks for reading back :) I was hoping this would be the case [12:33] mardy: is that still on track? ^ [12:33] jdstrand: did you get chance to fix the cache dir permissions in the scope template, btw? [12:34] ah yes [12:34] I see you did [12:34] pete-woods: yes, uploaded in apparmor-easyprof-ubuntu 1.2.13 [12:34] oh no [12:34] cool [12:34] * pete-woods misread log for a second there [12:35] pete-woods: https://launchpad.net/ubuntu/utopic/+source/apparmor-easyprof-ubuntu/1.2.13 [12:35] :) [12:35] :) [12:35] yeah, I clicked on 1.2.12 by mistake [12:35] :$ [12:35] I had another request shortly after that upload [12:35] ah, 1.2.14 is latest and it wouldn't have been too enlightening either [12:36] :) [12:37] jdstrand, thanks for the quick review [12:38] dholbach: of the MR? sure thing! :) [12:38] Hi all! I have a fast quesiton: Where can I find the phone releases (like r133, r163, etc) and changelogs? [12:40] jorge133: http://people.canonical.com/~ogra/touch-image-stats/ [12:40] jorge133: http://system-image.ubuntu.com/ === _salem is now known as salem_ [12:41] Thanks, I just now seeing that it's in the header :) [12:42] What are the difference between mako, flo, mantra and gerenic? [12:43] they are for specific devices [12:43] (and will only run on the respective hardware) [12:44] thanks :) [12:46] popey, not yet, sorry, ping ChickenCutlass to see who to assign that [12:57] ogra_, did you see my question about reducing ubuntu boot image? it doesn't fit on flo recovery partition any more, so dual boot is impossible on it :| [12:58] Saviq, i thought i even answered [12:58] ogra_, oh, then must've been me who missed the answer [12:58] * Saviq reads logs [12:59] ogra_, hey, stupid question... do you know/think we could reduce the boot image size? it doesn't fit on flo's recovery partition any more, which means dual booting flo is impossible now [12:59] how much is it over ? [12:59] (if it is megabytes i fear there isnt anything we can do ) [12:59] ogra_, good question, how do I find out do you think? [13:02] -rw-r--r-- 1 ogra ogra 3,3M Jul 27 04:06 initrd.img-touch-0.74 [13:02] so the initrd is 3.3M [13:03] ondra-, do you know the recovery size on flo? === alan_g|lunch is now known as alan_g [13:06] -rw------- 1 ogra ogra 6,8M Jul 16 13:25 boot/vmlinuz-3.4.0-3-flo [13:06] so in summary that makes ~10M [13:07] Saviq, looks like the kernel grew wiht the last build [13:08] i doubt there is anything we can do apart from dropping kernel options or some such [13:08] ondra-, ↑ :| [13:09] we need a smart boot [13:11] Saviq, hmm, seems the initrd also grew a bit (i guess due to xnox re-arranging plymouth) [13:12] I know what is stable channel. But what are difference between devel and devel proposed? [13:15] stable is a dead end that carries very old (but stable ... as in not changing)images [13:15] if you want something that is up to date and usable you use the devel channel ... if you like to ive on the edge with totally untested stuff you use devel-proposed [13:16] tvoss: http://paste.ubuntu.com/7914486/ - seen this? [13:17] thanks ogra :) [13:17] Laney, nope [13:18] Laney, where is that from? [13:18] was building gst-bad but it seems to be entirely in platform-api [13:19] Laney, hmmm, that's weird. jhodapp ^, got an idea? [13:20] barry, around? [13:20] tvoss, Laney, that's news to me...what exactly do you mean by it being in platform-api? are you talking about the source package? [13:20] janimo: yep! [13:21] barry, I'd like to get some guidance on how to write the test for the --skip-ssl-verify MR [13:21] jhodapp: I don't think it's your problem [13:21] barry, which test to use as a starting point [13:21] Laney, because you were pointing to gst-bad [13:21] Laney, ok [13:22] tvoss: That's what I was building but I don't think it is at fault [13:22] the same struct is defined twice [13:23] Laney, oh sorry, missed the bug report [13:23] Laney, seems to me the _deprecated header is the offending bit here === Cat is now known as Guest21837 [13:23] yes, agreed tvoss [13:23] seems so === ValicekB_ is now known as ValicekB === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [13:27] jhodapp: is media-hub used for HTML5 video playback? [13:28] mhall119, you mean in Oxide? [13:31] jhodapp: hmmm, hadn't thought of that, does it make a difference whether it's oxide or webkit? [13:31] jhodapp: btw this was me building gst-bad 1.4 with your stuff rebased [13:32] mhall119, no I just mean that you're asking if it uses media-hub to play video back in our web browser app [13:32] Laney, ah ok, thanks [13:33] jhodapp somebody was asking about it yesterday, they were playing a video in an HTML5 app and the screen was turning off on them [13:33] I'm not sure our HTML5 app launcher is using oxide yet though [13:34] mhall119, well if it's either browser backend, they don't use media-hub [13:34] mhall119, and as a result, yes they will not prevent the screen from blanking [13:45] Wellark: ping [13:46] ToyKeeper: ponh [13:46] whoops [13:46] robotfuel: pong [13:46] off by one [13:47] Wellark: this is the most common crash the phone has currently. can you triage it? https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service%3A6%3A__gnu_cxx%3A%3A__verbose_terminate_handler%3A__cxxabiv1%3A%3A__terminate%3Astd%3A%3Aterminate%3A__cxxabiv1%3A%3A__cxa_throw%3Acore%3A%3Adbus%3A%3ABus%3A%3Asend_with_reply_and_block_for_at_most === agafsfsf is now known as stevew [13:47] Laney, mind checking https://code.launchpad.net/~jonas-drange/gsettings-ubuntu-touch-schemas/phone-settings/+merge/228620 again? I've renamed the schema. [13:47] thanks [13:49] robotfuel: oh, good. an actual stacktrace! \o/ :D [13:50] Wellark: yes, not easy to get :P [13:50] jgdx: isn't it "Mapping from modem paths to SIM names"? [13:50] i.e. the other way around [13:51] robotfuel: I guess you can't get me the what() of that std::runtime_error :) [13:51] robotfuel: ok, I will take a look [13:52] at least I can catch the exception to stop it from leaking, but would be nice to know what actually goes wrong [13:53] robotfuel: oh, it's hitting hard [13:53] Laney, oops. Pushd r42 [13:53] Wellark: most of these I assume are invalid password attempts to log in to my neighbors wireless routers, as the test is randomly clicking and swiping. [13:53] jgdx, you have a spacing issue as well, just commented [13:53] robotfuel: :D [13:54] robotfuel: be careful. in some countries it's illegal to log to your neightbors free wifi :) [13:55] Wellark: it's okay in New Hampshire where I live. :D [13:56] robotfuel: are you able to reproduce this reliably? [13:56] Wellark: yes 15 times yesterday [13:56] Wellark: I didn't reproduce it.. the random clicking and swiping test did. [13:57] Wellark: fixing this will help improve our time before crash happens the most. [13:57] Saviq, did the sensitive area for the left edge change somehow ? i find it hard to type on the most left column of the keyboard ... [13:57] ogra_, shouldn't have [13:57] ogra_, it was always kind of difficult to do anything near the edges (2gu) [13:57] ah wait [13:58] my password has an "a" in it ... i havent managed once to hit it on the first tap [13:58] always need to be very precise to make it recognized [13:58] seb128, puushed r43 [13:59] jgdx, thanks [14:00] ogra_, I think one thing changed indeed [14:01] ogra_, the launcher is now on top of the keyboard [14:01] ogra_, let me have a chat with designers here [14:01] Saviq, ah, that might cause it [14:01] ogra_, can you please file a bug against unity8 and ubuntu-ux in the mean time? [14:01] Saviq, well, try it yourself ... set a passwor in 162 and try to unlock [14:01] ok [14:07] jgdx, oh, if I was to nitpick, one of your key descriptions ends with a "." and not the other ones, being consistent would be nicer [14:10] ogra_, yeah, we'll just put the edge detection below OSK for now [14:15] Saviq, great, thanks [14:17] seb128, in Norway we say, "Skal det være, så skal det være." Is it too late for me to push now? [14:19] ogra_, file the bug anyway please (didn't see it) [14:19] havent filed it yet [14:19] :) [14:19] ;) [14:19] jgdx, no it's not [14:19] is a SIM needed to test ubuntu-touch? [14:19] jgdx, we do manually landing, until somebody gets your change built in a silo and landed you can push changes [14:19] K1773R: no [14:20] t1mp: ty [14:20] seb128, k, thanks for the review. [14:20] jgdx, yw! [14:21] Saviq, bug 1350881 [14:21] bug 1350881 in unity8 (Ubuntu) "with recent unity8 changes the left column of the keyboard is not very responsive anymore" [Undecided,New] https://launchpad.net/bugs/1350881 [14:23] kenvandine, wanna take a look at https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/sim-name-editor/+merge/229053 and https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/1219793-reset ? [14:24] i was just looking at the sim-name-editor branch [14:24] kenvandine, cool === gnu is now known as Guest43249 === alan_g is now known as alan_g|tea [14:29] seb128, when do you think jgdx's schema changes will land? [14:29] kenvandine, when it's reayd [14:29] :p [14:29] haha [14:30] you top approved it :) [14:30] kenvandine, we can do a landing now if you want [14:30] it'd be nice... i'm reviewing his settings branch that needs it [14:30] would make it easier to test it, etc [14:30] we also need a gsettings-qt landing [14:32] achiang: you can look up the OOPS ID as seen in line 6 of your pastebin https://errors.ubuntu.com/oops/4923130e-1879-11e4-ab04-fa163e339c81 [14:32] achiang: at the bottom of that page we can see "Problem: ... failed" [14:33] achiang: that's a link to the bucket - https://errors.ubuntu.com/bucket/?id=failed%3A/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene%3A6%3A/lib/arm-linux-gnueabihf/libc-2.19.so%2B178e6%3A/lib/arm-linux-gnueabihf/libc-2.19.so%2B2605e%3A/lib/arm-linux-gnueabihf/libc-2.19.so%2B26d4e%3A/lib/arm-linux-gnueabihf/libc-2.19.so%2B4f838 === greyback|away is now known as greyback [14:33] achiang: and that OOPS in the only instance of it === boiko__ is now known as boiko [14:34] kenvandine, k, I can do those now [14:34] seb128, you rock! [14:34] ;-) [14:34] https://code.launchpad.net/~larsu/gsettings-qt/lp1349787/+merge/228841 [14:34] kenvandine, question for you btw [14:34] sure [14:35] kenvandine, how are you supposed to access content-hub on images from the webbroser? clicking on a png url opens the image in the webbrowser, it doesn't give you the "open with" screen [14:35] I tried to hold the click to get the other actions [14:35] but that doesn't include it [14:35] it should have a "Save" [14:36] when you long hold on the image [14:36] where? [14:36] oh, once the image is open [14:36] yeah [14:36] not on the link? [14:36] let me try [14:36] not the link [14:36] k, I didn't want to open the image, so I didn't even try there [14:36] you can also long press on any image [14:36] i think [14:36] without opening it [14:37] well, that was an url [14:37] not an image in a page [14:37] Elleo, ^^ why can't we trigger the download when long press on a link? [14:37] s/when/with [14:37] kenvandine, I tested on http://people.canonical.com/~seb128 [14:37] there is an image in there === alan_g|tea is now known as alan_g [14:39] kenvandine, holding press on the image works, thanks ;-) [14:39] np [14:39] :) [14:59] boiko, renatou: I would need to free up silo 15, we're low on silos and I see it's marked as a test silo [14:59] boiko, renatou: would that be ok? [15:00] sil2100: we are trying to land that toda, so not sure :/ [15:00] today [15:00] Ah ;) [15:00] Ok then, let me look for some other silo then :) [15:02] sil2100: in case you really need it, ping us again === gatox is now known as gatox_lunch [15:07] Hi! How can I set a language on Ubuntu Touch? [15:07] in the language settings [15:09] but it is only temporary, If I restart the emualator it is english again [15:09] and the apps are english always [15:09] oh, i dont know about the emulator ... it is definitely working on devices [15:11] I think I found the solution: https://www.mail-archive.com/ubuntu-translators@lists.ubuntu.com/msg05653.html [15:11] Saviq, there is also bug 1350862 if you didnt see it yet [15:11] bug 1350862 in Unity 8 "SigKilled webapps (mostly) when pulled to the front open under the top panel" [Undecided,New] https://launchpad.net/bugs/1350862 [15:12] Chipaca, hi, MacSlow just told dferrai that apps can’t trigger vibrations as notifications after all. Can you and he come to an agreement, please? [15:13] is it normal that the 3 buttons at the bottom cant be used? === pete-woods1 is now known as pete-woods|lunch [15:15] K1773R: what 3 buttons? [15:15] the "touch buttons", go back, home and the other one [15:15] we dont support those [15:15] i c [15:15] so everything is fine :) [15:16] actual phones you will be ablet to buy with ubuntu will most likely not have such buttons at all [15:16]