[00:00] How come sailfish os have android bindings? [00:00] Couldnt ubuntu do the same? [00:01] That way we can easily get over all opensource java apps from android into ubuntu. [00:03] I didn't know they had android bindings. [00:04] But the reason would be: because no-one has written them :) [00:04] (Also, because Android bindings get you less and less benefit over time, as things move into Play services, where Google can actually keep them updated) [00:13] tmpRAOF, is it possible to run android in dual boot mode with eg. sailfish or cyanogenmod? [00:13] or stock android. [00:14] Yes; IIRC there's an app in the (Google) store that does exactly that. [00:14] Probably requiring root :) [00:14] tmpRAOF, sorry. I meant. ubuntu and cyanogenmod at the same time? [00:15] Yeah, that's the question I answered :) [00:15] what is the app name? [00:39] sander^home: fyi there is already a java app in the store. the bitcoin app uses (and ships) a full JRE inside the click package [00:39] this is why it's the biggest app in the store, last time I checked :) === chriadam|away is now known as chriadam === _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 === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [07:52] Wellark_, putting [1] into a silo. Do you know when it'll be top approved? [1] https://code.launchpad.net/~unity-api-team/indicator-network/lp1411714-14.09/+merge/247407 === dholbach_ is now known as dholbach [09:45] Hi [09:46] can someone help me with a problem I'm having with Ubuntu touch recording, with mirscreencast [09:47] Good morning all; happy Friday, and happy Fun At Work Day! *8OD [10:51] Elleo, ping [11:04] cwayne: are you not on a flight [11:04] davmor2, tomorrow [11:05] cwayne: blame john-mcaleely he said it was today we thought you'd be able to get 14hours of shut eye today ;) [11:05] cwayne, can blame me for most things davmor2 [11:06] john-mcaleely: don't we all ;) [11:08] cwayne: pong? === _salem is now known as salem_ [11:16] Elleo, how are new keyboard layouts installed? do we plan to have them as click pkgs? [11:17] cwayne: thats the eventual plan, currently they're only available as preinstalled debs though [11:17] Elleo, when do we plan to fix that? [11:18] at the very least, we'd like to be able to include them in the custom tarball [11:19] cwayne: its on the list for this cycle, but not currently high in the schedule (but that might chamge after mondays planning meeting) [11:20] cwayne: theres a few things we need to do first like confining maliit and/or simplifying the layout format [11:20] Elleo, its something we would definitely want/need for future images [11:20] Elleo, yeah, i figured that for clicks [11:21] at the moment each layout is QML + a .so plugin, which isnt great [11:21] Elleo, clicks would be ideal, but being able to include them in /custom would be a big step forward already [11:22] cwayne: I can probably adapt maliit to search for plugins there, would anything else be needed for that? [11:23] Elleo, not that I would know of, but I could check [11:24] cwayne: okay cool, if you can get me any details about the /custom process and the prefered location and file it in a bug report I can see abput getting it scheduled before the .click stuff [11:25] Elleo, cool, thanks, I'll get some info and get it over to you ASAP [11:25] cwayne: thanks === boiko_ is now known as boiko [11:44] pitti, morning! one small question, do you know how I could debug an interaction I have with Udisk. I have an obj path with the FileManager interface and no Mount Points that I want to mount, I call Mount with auth.no_user_interaction=true yet the reply for dbus never reaches me [11:45] pitti, all this in golang (so,something in the dbus packaged could be wrong) [11:49] pitti, looking at dbus-monitor the properties changed does send an update with the new mount point => http://paste.ubuntu.com/9954928/ [12:08] jgdx: top approved. [12:08] jgdx: do you have vivid silo as well? [12:08] jgdx: if you do, it takes me 10 minutes to get you a corresponding vivid MP [12:30] what's the general linux API for touch programming? === MacSlow is now known as MacSlow|lunch [12:34] jgdx: vivid counter part: https://code.launchpad.net/~unity-api-team/indicator-network/lp1411714-15.04/+merge/248104 === alan_g is now known as alan_g|lunch [13:17] Wellark_, I was aiming for vivid. Thanks [13:18] seb128, hi, the fix in [1] actually fixes the test and as you can see the test failures in the most recent AP run are new. [1] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/fix-background-test/+merge/247955 [13:19] i.e. the most recent AP run did not fail the test_background tests. [13:21] jgdx, great [13:22] jgdx: so, be careful not to mix up the MP's :) [13:22] Wellark_, right! [13:22] rtm has 14.09 in the name and vivid 15.04 respectly :) [13:23] danguafer, in #ubuntu-touch that would be Qt [13:25] Wellark_, subtle, I like it === MacSlow|lunch is now known as MacSlow === alan_g|lunch is now known as alan_g [14:21] Wellark_, cyphermox, bug #1416424 might be for you, could it be due to the new n-m in vivid? [14:21] bug 1416424 in ubuntu-system-settings (Ubuntu) "Wifi list is empty" [Undecided,New] https://launchpad.net/bugs/1416424 [14:39] seb128: could be [15:18] cyphermox: confirmed here on image84, no wifi in welcome wizard, indicator or uss [15:18] Wellark_: ^ [15:30] cyphermox, Wellark_: is there any useful info I can get you? before I start rolling back to see where the issue was introduced? [15:32] not especially. file a bug including /var/log/syslog, make sure 'nmcli dev wifi list' shows the list of networks, and it's pretty much good [15:33] cyphermox: I assume it is the issue that seb128 just pointed you at so I'll add some logs there for you [15:33] ok [15:36] davmor2: O.o [15:38] cyphermox: any dbus-api changes between NM 0.9.8 and 1.0 ? [15:39] you mean 0.9.10 [15:40] I don't know, depends what API you use [15:40] well, if it worked with 0.9.10, then yes [15:40] Wellark_, cyphermox: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424 added syslog and output of 'nmcli dev wifi list' [15:40] Launchpad bug 1416424 in ubuntu-system-settings (Ubuntu) "Wifi list is empty" [Undecided,New] [15:42] I'm assuming the seg fault bit isn't good :( [15:42] mzanetti: Looks like parts of the internal flash storage in my BayTrail tablet died :/ I'll see what I can do to revive it or circumvent the problem [15:43] davmor2: nmcli dev wifi list wlan0 [15:44] davmor2: the segfault is not great but you get the wifi list, that's what I wanted to know [15:45] cyphermox: so I get the there is wifi available empty icon on the device but then nothing. [15:46] cyphermox: did you test i-network and friends before uploading nm 1.0 ? [15:46] I'm flashing now [15:46] of course I did, and as I recall things were working [15:46] had to check [15:48] davmor2: please augment the bug description with full system-image-cli version information [15:50] Wellark_: done [15:50] davmor2: thanks [15:50] will test krillin now [15:50] Wellark_: anything else you need? [15:51] davmor2: well, you could check if .cache/upstart/indicator-network.log contains anything [15:51] or .log.1.gz [15:51] Wellark_: sure give me 5 [15:51] davmor2: just slam them in pastebin or something [15:51] thanks! [15:52] Wellark_: lets not waste the pastebin it says this twice :) *** Received Terminated. *** [15:55] davmor2: ok, so nothing interesting there [15:56] davmor2: just to double check, mako == n4, right? [15:57] yes [15:57] davmor2: btw, di you do an ordinary flash, or with --wipe or --bootstrap? [15:59] Wellark_: I always bootstrap [15:59] Wellark_: kills any modified config files so tests are fresh [16:00] davmor2: yep [16:00] davmor2: I'm just wondering.. in the bug report you say "even when the phone has automatically connected to a saved network" [16:01] so was the wifi list OK in the wizard? [16:01] and was it working after the first boot? [16:01] Wellark_: Nope there was no wifi listed anywaere [16:01] davmor2: how were you able to have a "saved network" then? [16:01] Wellark_: I rebooted the device after first boot + setup and still no wifi [16:02] Wellark_: I didn't someone else reported the bug and I assume they ota'd [16:02] Wellark_: I can soon test that theory though [16:02] davmor2: oh, right. [16:02] davmor2: that explains [16:03] oh, well.. this is one way to spent the Friday evening.. [16:06] cyphermox: is there a doc that explains the D-Bus API changes in NM between 0.9.10 and 1.0 ? [16:08] Wellark_: it's not the first time I'm trying to tell you there is no 1.0, we're not there yet. [16:08] https://developer.gnome.org/NetworkManager/0.9/spec.html [16:09] fwiw, I just flashed my krillin with devel-proposed and things came up #1 from the start. [16:10] cyphermox: so what version did you upload to vivid, and what was the previous version it replaced? [16:10] 0.9.8.8 to 0.9.10 [16:10] right. [16:10] so is there a delta doc somewhere on the dbus api changes from 0.9.8.8 to 0.9.10 ? [16:12] I also finished flashing devel-proposed on krillin and everything seems ok [16:13] next, mako [16:18] Wellark_, each time i go to Carrier->APN it I see a new "Internet" named APN in the list, without even opening the editor [16:18] i can back out and go back and the list has one more [16:18] and... it now never activates the provisioned context [16:19] meaning... no mobile data for me [16:19] Wellark_, this is vivid-proposed on mako [16:19] kenvandine: that's the bug we discussed yesterday [16:19] jonas should be on it [16:19] ok... surprised it's adding a new context just going to the page [16:19] basically the values that are stored in apn editor never reach ofono [16:19] not even going to the editor [16:20] or trying to activate one [16:20] this is the page that lists the contexts [16:20] yes. [16:20] it's weird [16:20] and... mobile data doesn't work [16:20] it won't activate the provisioned one [16:20] i can't see how going to the page could make it try to activate a new context [16:21] Wellark_, note also... i removed all the contexts and rebooted [16:21] it still happens [16:21] and... now wifi seems broken... not seeing my network [16:21] the list is from earlier, when i wasn't at home [16:21] kenvandine: yes, as the editor sees an empty context and tries to turn that into a custom context, but as the modifications don't go through [16:21] but the provisioned one isn't empty [16:21] as there is $breakage [16:22] list-contexts shows all the info, looks right [16:22] but it won't activate it [16:22] jgdx: have you had a chance to look at the apn editor problem on vivid? [16:22] Wellark_, this is more than just the apn editor [16:22] if i remove all the contexts and reboot [16:22] never open settings at all [16:22] it won't connect [16:22] Wellark_, kenvandine, not yet. It's not targeted for w7 yet, is it? [16:23] probably should [16:23] so i don't think this is really a settings issue [16:23] i can get it back to a state where there is the single provisioned context [16:23] that worked fine until wednesday [16:23] kenvandine: not connecting after you remove everything and reboot would be ofono/nm problem then [16:23] reboot the phone and never open settings [16:23] right [16:24] cyphermox: ^ [16:24] and might be the root cause of why the APN editor is doing what it's doing [16:24] kenvandine: I'm pretty sure the APN editor is a separate issue [16:24] Wellark_, also note, earlier this morning the indicator showed the 3g icon... but still no data [16:26] right. [16:27] Wellark_, rebooting fixed the wifi problem [16:27] but it was stuck with a list of access points from where i was this morning [16:27] never rescanned [16:28] kenvandine: mako wifi driver acts weird sometimes [16:29] I've noticed it missing access points that I know are around [16:29] and usually my own [16:29] even if you force an active scan with "sudo iwlist scan" [16:29] they aren't reported by the drived [16:29] driver [16:29] oh my.. jgdx check this out [16:29] jgdx, so after removing all my contexts and rebooting [16:30] i do have working data... and the icon shows 3g [16:30] but the tech pref in settings is set to 2g [16:30] before rebooting it was set to 3g [16:31] TechnologyPreference = umts [16:31] Hi, I need some help. I installed Ubuntu Touch on my Nexus 7 2013. I saw some images of the tablet version of Ubuntu Touch. How do I put it into this mode.? [16:32] cyphermox: confirmed. no access points shown on mako with devel-proposed, krillin was just fine [16:33] except there is no reason for this to be any different between mako and krillin [16:33] ok... confirmed it does seem to be the APN page that messes things up... mobile data was actually working (with the tech pref weirdness) [16:33] until i navigated into Carrier->APN [16:33] never opened the custom APN editor [16:33] just loading the page added a second internet context [16:33] and i can no longer connect to the internet [16:34] jgdx, so it gets into this situation from that page in settings [16:35] and once that bogus context is created, nothing works :/ [16:40] jgdx, i bumped the priority to critical, since this easily gets you into a situation that can't be recovered from. [16:40] not without connecting to it with phablet-shell in developer mode [16:40] hopefully it never affects krillin [16:42] kenvandine, ack. I'm on my way out. I'll take a look this weekend. [16:42] jgdx, thx [16:42] jgdx, the tech pref thing is weird to [16:43] after removing all the contexts and rebooting [16:43] it always switches back [16:43] maybe that's expected [16:43] kenvandine, could you put that bit in the appropriate apn bug too? [16:43] thanks! [16:43] yeah [16:43] that is interesting [16:51] well, something is different between krillin and mako [16:55] cyphermox: when was the p2p0 added to mako? [16:55] i'm going to flash vivid on my krillin and see [16:55] cyphermox: nm is reporting it as wifi device [16:56] i-network is not handling multiple wifi devices in the system [16:56] Wellark_: wasn't added, it was always there [16:56] cyphermox: reported by NM? [16:56] p2p0 is an AP-mode interface for Wifi-Direct [16:56] yes [16:56] wait, no [16:56] but it shouldn't make a difference [16:56] we'll need it anyway for hotspot [16:56] it does. right now [16:57] as i-network just grabs the first wifi device it gets from NM and ignores the rest [16:57] awe_: as suggested, it's a matter or multiple devices ^ [16:57] Wellark_: isn't that a very bad assumption? [16:58] and the one it obviously is grapping on mako is the p2p0 hence no access points visible [16:58] Wellark_: tbh, I'm happy either way, I could disable them again (that patch must have slipped), but it's something we *will* need [16:58] cyphermox, it's mako only, krilling works fine [16:58] Wellark_: I'm flashing 81 so far no networking [16:58] awe_: yes, because krillin needs to be poked via hybris to enable p2p0 [16:58] cyphermox: not for a phone release... [16:58] fresh devel-proposed on both [16:58] Wellark_: yes. [16:58] Wellark_: I mentioned this because we'll need it for wifi hotspot [16:59] Wellark_: now whether it is needed for a release *right now* is a different matter [16:59] cyphermox, p2p used to be ignored by NM [16:59] awe_: yes [16:59] awe_: see above, it will be needed for hotspot. it's possibly just too early to enable it now. [17:00] sure, understood. but the code in i-network just is not yet capable of handling two wifi interfaces [17:00] maybe it should just be ignored by indicator-network for now [17:00] that would possibly be better because later when you want to enable handling two wifi devices, it will be a centralized change [17:00] seems like the easiest patch for now, is have i-network ignore p2p device ( just like NM used to do ) [17:01] ;) [17:01] awe_: I can also just have them ignored in NM, but there are further complexities to this that I hadn't thought of initially [17:01] that said, not all devices may use the same naming scheme, so we probably need a property that exposes the P2P device name that i-network could query [17:02] there isn't a clear way to identify them [17:02] the P2P device can be a separate device but not necessarily [17:02] and the main wifi device can still export having P2P/AP mode capability [17:03] regardless, NM should be able to handle the "p#p#" string because that's used elsewhere too -- for instance, when biosdevname is installed [17:04] cyphermox: what is the NM_802_11_MODE of p2p0 ? [17:04] can you look at it yourself? my mako isn't charged enough to boot yet [17:04] probably very close, but it's not starting just now [17:04] will try [17:12] cyphermox, I agree that we can use a default pattern, however on devices that are shipped with ubuntu, if the p2p devices don't fit the pattern, we can use a property to override the default pattern [17:12] hmm, what? [17:12] sorry, I'm not following :) [17:13] a property where? [17:14] awe_, cyphermox: could you restore the old behaviour of not exposing p2p0 through NM, please, to quickly restore the wifi functionality on mako [17:15] Wellark_, doing so kills WiFi hotspot and we're going to need the fix in indicator-network anyways... [17:15] should be a trivial patch, no? [17:15] awe_: to be fair, we haven't exactly expose hotspot anywhere. [17:15] awe_: wifi hotspot is not released yeẗ́ [17:15] cyphermox, Wellark_, ack [17:15] Wellark_: so as I was saying above, I sure can, but the question was *should we* [17:15] awe_: ^ [17:16] I think it would be better if ChickenCutlass or somebody else could take a decision [17:16] well, it's 7pm on a friday night here [17:16] cyphermox, do you have an existing patch that could be applied to NM? or is it more complicated than that? [17:16] and people are being ota'ed in a broken system [17:17] this should at minimum warrant an email to the ml [17:17] Wellark_: it's not going to change that they've OTA'd, and that they will need to get online somehow to get a new image, or apt-get upgrade [17:17] to give people a heads-up now [17:17] awe_: I do have an existing patch for 0.9.8 that should apply just fine. [17:17] Wellark_: so image 81 works any thing after that doesn't [17:17] awe_, cyphermox: --^ [17:17] cyphermox, to be clear... if someone had already connected WiFi [17:18] it *should* automatically connect when WiFi is enabled, indicator-network withstanding... [17:18] right? [17:18] Wellark_: next I'm trying flo manta and you say that krillin works right? [17:18] davmor2: krillin works [17:18] awe_: yes [17:18] davmor2, I just flashed krillin and yes it works [17:18] awe_: so a fair point, for OTA things will still work [17:18] so trying manta and flo then [17:18] cyphermox, seems like an NM upload is the way to go now [17:18] it's the quickest fix [17:19] I'm not convinced it's necessary to be *that* quick about it, but whatever [17:19] that said, we should open a bug against i-network so that we can revert the change [17:19] cyphermox, awe: I'm just doing an update now from 81 which was the last working to 84 [17:20] davmor2: ok [17:20] cyphermox, see my comment about ML above. If we tell people now, it's probably OK to do the upload on Mon [17:20] davmor2, do you concur? [17:20] awe_: I mean i-n upload, really ;) [17:21] but I'm preparing the patch, checking out what got wrong because I don't think it should have just gone away [17:21] ok [17:22] awe_: lets double check with the upgrade first then I can update the bug, then yes I see no reason it can't land Monday, one thing you guys need to be aware of though is from Monday vivid comes under QA scrutiny so at that point it will be a critical flaw, just a heads up on that :) [17:22] awe_: p2p patch is still there [17:22] it's applied, too [17:22] it's just not doing what it should due to changes in the backend [17:23] davmor2: for vivid? [17:23] aren't we trying to release RTM? [17:23] cyphermox: last image was passed today for rtm [17:23] right [17:24] rtm is a thing of the past [17:24] so why is vivid becoming super-critical? [17:24] :-) [17:24] cyphermox, so with the patch applied, technically I shouldn't see it exposed when I run 'nmcli d', right? [17:24] cause I do... [17:24] awe_: right [17:24] because we're trying to stabilize vivid now [17:24] cyphermox: because it is the next target [17:24] awe_: the patch needs to be different, that's all [17:24] http://pastebin.ubuntu.com/9959774/ [17:24] rsalveti: oh, I see, stabilizing vivid to branch again, kind of [17:24] mako ( 'nmcli d' ) [17:24] yes yes [17:24] cyphermox: yeah [17:25] awe_: I'm aware of how it looks, I did the dance before for rmnet. [17:25] so the patch is applied, but doesn't work with the new version, so needs to be re-worked [17:25] cyphermox, can you own sending the email to the list once we get results from davmor2? [17:26] kenvandine, https://code.launchpad.net/~charlesk/indicator-power/lp-1416096-publish-primary-device-state-on-bus-15.04/+merge/248145 [17:26] charles, woot [17:26] need to go to get some food [17:26] back soon [17:27] charles, is that exposed just for phone? [17:27] or desktop too? [17:28] kenvandine, action states aren't tied to a menu profile, so it's exposed for all [17:28] great [17:28] awe_, cyphermox, Wellark_: http://people.canonical.com/~davmor2/wifi-broken-but-connected.png so it works if you are connected to something (So auto connects work) but you are screwed if you move away from it. [17:29] kenvandine, ie the states are published in /com/canonical/indicator/power, not /com/canonical/indicator/power/phone [17:31] awe_, cyphermox, Wellark_: updated the bug. [17:33] hey giffgaff, I remember that! [17:34] cyphermox: :) [17:34] awe_: running in sbuild nao. [17:34] k [17:35] I know it isn't relevant to the conversation and just my opinion, but the picture posted by davmor2 looks quite well-done. GJ art team and dev teams. :) [17:36] Fishscene: yeah. you should look at the terminal app ;) [17:37] I can't tell if it looks terrible, or it looks awesome enough to win over GUI enthusiasts. :P [17:54] cyphermox, awe: Flo is broken on 84 checking manta next [17:55] ok === alan_g is now known as alan_g|EOW [18:04] man I forgot that manta took so long to charge [18:12] charles, and my branch that needs your branch https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/lp1329702_battery_charging_status/+merge/248149 [18:47] I remember that one of the examples for scopes was an Open Clipart scope. [18:47] Is there a reason that's not in the store? [18:49] kenvandine: both of 'em together WfM on mako r84 [18:51] charles, thanks! [18:52] charles, feel free to add a review for my uss branch :) [19:00] charles, kenvandine, stupid question, but why don't you just watch the upower property on the bus? [19:01] seb128, i could add that to our battery backend, wrapping upower's dbus interface [19:01] but i'd rather keep it simple, and keep that logic in the indicator [19:02] which watches it anyway [19:02] k [19:02] it would be nice if we had a way to create a qml property binded to a dbus property :/ [19:02] indeed [19:02] without a pile of cpp code :) [19:02] some qml generator :) [19:03] some qml/dbus binding generator :) [19:04] I think in this case you want i-power to do the aggregation of multiple batteries for you. That way it's done the same way everywhere. [19:05] and... we can be sure that things like the upower transition get caught early, you couldn't miss the indicator icon not getting updated [19:06] but it's easy to not notice the little sting in system-settings not changing :) [19:06] so if it breaks again, it'll be quickly obvious [19:13] yeah [19:13] kenvandine, speaking about icon, the new upower has a property with the icon to use for the device [19:13] that's cool [19:13] we could use that to display the proper icon in the settings grid [19:14] yeah, but we need to look that up to display it on the grid [19:14] slower... [19:14] it would be nice though [19:14] but i still want to speed up startup time more [19:17] hey guy on vivid you get the volume osd popup at some random point on boots any idea where I should file it? [19:18] davmor2, Random point on boots? [19:19] tedg: when you flash, or boot the system, mako/flo/manta so far, the volume bar notify-osd just pops up [19:20] * tedg reboots [19:22] davmor2, Hmm, I don't see one one boot. [19:23] davmor2, But WRT where to file, it's indicator-sound [19:24] tedg: d'oh it might only be flash, I forgot it was the reboot where I ota'd so that might of been treated as a flash too right? [19:25] davmor2, Could be, it could happen in the case where AS and Pulse have different saved values. [19:25] We sync them, but it counts as a volume change. [19:26] We should just disable AS reading in the user session. [19:26] Hmmm [19:26] That'd make life simpler. [19:29] tedg: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1416520 set it to only after flash for now [19:29] Launchpad bug 1416520 in indicator-sound (Ubuntu) "vivid: Sound indicator pops up on initial boot after a flash" [Undecided,New] [19:34] kenvandine, approved [19:35] kenvandine, I'll put the two branches in the train spreadsheet [19:35] charles: is that like the new Government Approved, If ken likes it, it must be good, this product is kenvandine approved ;) [19:36] davmor2, correct, except "new"... it's always been "if ken likes it" [19:36] hahahahaha [19:37] :-D [19:57] Is there a general icon or symbol for ubuntu touch? [20:14] AkivaAvraham: the normal Ubuntu logo it's all ubuntu :) [20:14] davmor2, WRONG! http://itsfoss.itsfoss.netdna-cdn.com/wp-content/uploads/2012/10/Ubuntu-Unity-Logo.png [20:14] Thumbs down, unsubscribed! === salem_ is now known as _salem === blake_r is now known as blake_r-travel [22:23] mm its weird i cannot reboot my phone.. stuck at the rotating logo... My phone worked ok all day decided to restart as i had no bluetooth and now i am stuck [22:27] reflashing now but wonder what happened could not restart at all. by the way i was on mako vivid 84 [23:59] How do I create a web shortcut? [23:59] when I try to push the star button in the browser.. I can't find that page again. Dont know where I see shortcuts.