[01:14] hi, is there anyone here with a dedicated GPU card ? [02:20] !nano [02:20] Text Editors: gedit (GNOME), Kate (KDE), mousepad (Xfce4) - Terminal-based: nano, vi/vim, emacs, ed - For HTML/CSS editors, see !html - For programming editors and IDE, see !code [02:20] is nano a default app for 13.10? [02:28] IS anyone online with a working 13.10 install? [02:28] if so, is nano still a default app? [03:37] Noskcaj, nano a default app? well nano is command line :-) [03:44] balloons: one of the hardware test cases uses nano, i was wondering if we still ship it [03:44] yes.. [03:45] ok [03:45] dumb question [04:15] Can someone check the multiple hard drive part of the Entire disk install testcase. it is outdated and confusing [05:39] balloons, if you're online. i have another big merge comming up [06:24] phillw: yep [06:25] phillw: have a : 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Seymour [Radeon HD 6400M/7400M Series] [06:26] hmm ... when trying out otto + kubuntu I get : lxc container failed to recieve answer for command [06:26] also : lxc container failed to send command [07:31] jibel: hmm ... when trying out otto + kubuntu I get : lxc container failed to recieve answer for command [07:31] also : lxc container failed to send command [07:35] I am unsure as to what command it's trying to send there ... [07:35] ( that is right after sudo bin/otto -d start saucy-otto ) [09:58] gema, i was asking for the sheet you do have [11:52] apw: I don't have a sheet [11:53] apw: I am trusting the driver implementation [11:53] gema, i was asking for the sheet for the one you said you had a sheet for, i have since found it [11:53] ahh, sorry [11:53] I thought you meant the nexus 4 [12:49] Good afternoon :-) === _salem is now known as salem_ [13:57] balloons: https://wiki.ubuntu.com/QATeam/Hardware is alive. Just need someone else to also check it, as Linda's link is wrong..... [14:50] gema, this n4 driver, its remaining charge is calculated purely using the integer percentage, which seems utterly inaccurate [14:53] apw: otp [14:54] phillw, :-) [15:06] apw: sorry, lost context completely [15:06] I am back [15:07] apw: I am not sure what you mean, it seems to me that full charge would be the result of doing something like calculate_fcc_uah - calculate_unusable_charge [15:07] gema, i was saying in this n4 driver, the raw coulombs output are already exposed, and that the remaining_charge as calculated is simply made up from teh full capacity and the integer [15:07] and remaining charge should be charge now [15:07] remaining charge is (full_charge * current_percentage) [15:08] so it is woefully inaccurate [15:08] i may be able to use the raw coulombs to make that more accurate but, thats not how it is now [15:10] apw: the state of charge is calculated based on charge now (which we don't have) not the other way around [15:11] apw: I think we are wasting more time discussing than it would take to just expose that [15:11] apw: then we can do the calculations if you want and see what's more accurate [15:12] gema, the driver exposes percentages and raw coulombs, it uses raw coulombs and a significant amount of guess work to generate the percentage [15:12] gema, it them makes its idea of charges internally using those percentages, at 1% resolution === mzanetti is now known as mzanetti|food [15:13] exposing those is not going to give you any accuracy (even asuming for now that the device has accuracy) [15:13] apw: I'd like to be able to validate that empirically [15:13] rather than argue each other to death [15:13] gema, and i am working to expose them, and when writing the code and testing it, i can see how it is calculated [15:14] gema, and i can see that the value i am exposing changes like every time the percentage changes, which is how i _know_ it is based on the percentage [15:14] gema, and why am i asking if it is any use what so ever given your comment on the percentage from the GN [15:14] apw: what percentage are you talking about? [15:15] capacity? [15:15] the driver as it stands is calculating its remaining_charge from its (estimate of full charge * 100) / current percentage [15:15] its percentage charge remaining estimate. [15:17] remaining_charge_uah = calculate_remaining_charge_uah() .... that is using: [15:17] return (fcc_uah * pc) / 100; [15:17] ie, it is taking estimated full and using the percentage previously reported, and returning some other estimate in 100's of the maximum capacity [15:17] i am trying to get you to confirm that is of little use [15:19] and that therefore i need to try and expose something more granular [15:19] gema, ^^ [15:26] apw: are you saying that there is a circular dependancy in the driver? (I haven't really seen enough of it to be able to pinpoint that) in any other case, I am pretty sure the value you are getting is a good start, I can run a test if you give me a kernel with it and figure out if it makes sense [15:28] gema, i am saying the value you asked to be exposed is in 100th's of full capacity, i am asking if there is any value in that value, or do i need to work out how to make a better value [15:28] gema, to my mind it is pretty clear it is useless as it doesn't change for 10s of seconds [15:29] apw: can you give me some example values === mzanetti|food is now known as mzanetti [15:31] gema, the actual value would be like 2088105 and remains like that while the percentage is 91 (ish) and changes only when the reported percentage changes to 90 [15:32] gema, never mind, i am taking an executive decision that these values are too low resolution to be useful [15:32] gema, and i am going to figure out how to get more accurate values out === mmrazik is now known as mmrazik|afk [15:32] apw: ack, thanks === TheLordO- is now known as TheLordOfTime|EC === TheLordOfTime|EC is now known as LordOfTime|EC2 [19:43] balloons, about my merge proposal [19:45] i think you should let this one in as the hardware tests are less agonistic currently and netboot has a glitch where dd was dt and vice-versa [20:08] Noskcaj, howdy [20:08] hello [20:10] I like your changes, although I'm on the fence about the is vs should be stuff [20:10] but yea, there still needs to be some work done on some of them. [20:10] I can't merge everything as-is.. that's why we like the smaller merge proposals that are more on point.. [20:11] balloons, i did all this at school. i can't make merge proposals on the school laptop [20:12] Noskcaj, ahh.. well, your editing all those files right? Just make several branches [20:12] does that make sense? [20:12] make a branch, fix netboot [20:12] make a branch fix is vs should be [20:13] makes sense [20:13] make a branch fix hw tests [20:13] then it's 3 mp's, but it can be reviewed easier [20:20] balloons, i've just fixed netboot. uploaded. could you explain you issues with "should be" [20:20] Hi I have a laptop with a broken screen and i wanted to know how i can install ubuntu on it [20:21] oops [20:21] wrong room [20:21] samgabbay, you might have to replace the screen. tht's pretty simple though [20:22] Noskcaj, well, I'm wondering about how it reads [20:22] Noskcaj, but the laptop is too old for that [20:22] samgabbay, then plug an external screen in [20:22] yea but when i do i dont know what key it is to choose what to boot and like i want to make the external monitor the default [20:23] balloons, we need a wording that is constant, so do we want "should" or "is"? [20:23] is there a way to make like the external monitor input like the main one [20:23] just on like desktop pcs [20:23] samgabbay, should be, once you're in ubuntu [20:24] but it can't be too old to replace the screen [20:24] it is its like 6 years old or so [20:24] like how do i know what key to press on boot [20:24] cause on the external monitor it wont display like when you first turn it on and it says dell for example and it shows like f1 is bios [20:25] Noskcaj balloons I'm not sure what you're talkign about exactly - but if it's testcases - then there shouldn't be should - it either is and a pass or it's a fail [20:26] elfy, the wording of

[20:26] Noskcaj, in theory you should read the test as do this, expect that. it should be written as fact.. so we don't want should, might, could, etc in there [20:26] i have to go, i'll be back later [20:26] guys anything i can do to make the external monitor primary so i can see when it first boots and know the boot keyu [20:26] however when I explained it to you, yes, the result is what should happen, else it's a back :-) [20:26] pleaaassasseee [20:26] :? [20:26] :/ [20:26] samgabbay: you need a support channel - try #ubuntu [20:27] but like no one is responding : [20:27] :/ [20:27] it's a non-ubuntu problem to be fair.. and laptops are laptop specific.. likely no one can help you but yourself, google, and trial and error [20:27] :/ [20:28] i will say ubuntu has a screenreader mode that will talk to you during installation.. but again, without a screen there's no point.. and it's impossible to know what's going on [20:28] hello elfy ! [20:28] hi balloons :) [20:28] * elfy is back for a week again :) [20:29] aweosme [20:29] can you make the hackfest tomorrow? [20:29] so get ready for the next installment of how do I upload this again ... [20:30] balloons, like im gonna be using the computer with an external monitor, keyboard, and all i just wanna get it working until i get a new pone [20:30] balloons: eventually - got some r/l to attend to and a xubuntu meeting [20:30] balloons: but if it's autopilot then I'll wander off :) [20:34] balloons, so we want it worded as "this happens" ? [20:34] elfy, it's for everyone.. we've just specifically invitied new folks who might want t hack on autopilot for qml [20:34] don't be scared ;-) [20:34] lol [20:35] so that's 2 things that I'll go pfft at then [20:35] balloons, let me know if there's a hackfest i can attend [20:35] I thought qml was a downmarket sports shop chain ... [20:37] balloons: and of course the other thing being that 99% of anyone will be fiddlign with ubuntu things too ;) [20:37] Noskcaj, there is tomorrow [20:37] it runs through this time, so if your around as normal, you can be a part :-) [20:37] balloons, i mean a time when i'm not sleeping [20:37] ok, i'll try and attend [20:38] Noskcaj, tomorrow at this time we'll be finishing up, so you can attend :-) However, we can try something later on a weekend and see if more folks from down-under and asia can make it [20:38] I shall be attending my own hackfest and working away on xubuntu testcases [20:38] elfy, lol.. just know I'll be dedicating my time to helping whomever get testcases in [20:38] elfy, let's have an official xubuntu test hackfest [20:38] all day long you'll get me [20:39] balloons: I know :) [20:39] Noskcaj: afaik there are 2 people working on xubuntu testcases [20:39] though I think sergio is working on gnumeric [20:40] then mabe a hackfest is wasteful [20:40] *maybe [20:41] balloons: do I remember us having a conversation about the dates on the release schedule staying as they are even though they are patently wrong? [20:42] elfy indeed.. [20:42] heh [20:42] ping in #ubuntu-release about it [20:42] but cadence week dates are right? [20:44] balloons: ^^ [20:44] elfy, what do you mean? [20:44] the dates on https://wiki.ubuntu.com/QATeam/Cadence/Saucy are right ? [20:45] I need to talk with xubuntu about what we're going to do and when [20:45] balloons, you have more stuff to merge [20:46] elfy, yes I don't plan to change them unless we discuss first and have a reason [20:46] * elfy thinks it's absolutely ridiculous that release schedule is wrong because someone in the past set them up and no-on can be assed to deal with it now things have changed [20:47] balloons: k - just need something concrete to work with [20:47] elfy, there was a note and action item to change the release schedule rpoperly [20:47] lol [20:48] but again, I haven't seen any changes [20:48] well - if it doesn't get soon it can be marked as invalid :p [20:48] I have to work on getting our first week ready :-) [20:49] that's my concenr [20:49] yep [20:49] I understand that - that'll be your job :) [20:50] I don't suppose it matters much as long as we get 'week' with the same image to test [20:51] anyway - I should be about at some point tomorrow - now I am off === elfy_ is now known as forestpiskie [20:53] Noskcaj, ok, let me go look at th enew mp === balloons changed the topic of #ubuntu-quality to: Welcome to Ubuntu Quality | http://wiki.ubuntu.com/QATeam | Hackfest June 13th: https://wiki.ubuntu.com/QATeam/Hackfest/20130613 [21:15] Noskcaj, so what's this? https://code.launchpad.net/~noskcaj/ubuntu-manual-tests/xfce4panel/+merge/168858 [21:16] balloons, i re-based that, it's enough for the guy to merge into ubuntu-manual-tests [21:16] Noskcaj, ok [21:16] i'm re-merging your branch :-) [21:19] balloons, there's more changes, tell me when you want them [21:19] ok on testcases/hardware/1480_USB Mouse I think the bit about creating a file is a bit silly. we can just ask them to test left, right and dragging [21:20] Noskcaj, you can push whatever you have :-) [21:21] * balloons just realized he has media keys on the top of his keyboard [21:21] huh.. [21:21] lol [21:21] Noskcaj, I'm curious about this one:

Press the Search key

[21:21] [21:21] 91 [21:21]

The tracker desktop search tool should open

[21:21] balloons, i don't know what that is, it was already there [21:22] right.. I wonder what "search" tool they could mean [21:22] there is no more tracker [21:22] go ahead and remove it if you would :-) [21:22] ok [21:22] all the new changes look better [21:22] I saw up to rev 123 [21:23] 124 is uploading now [21:24] i made the search test agnostic [21:38] balloons, you have merges waiting [21:39] * balloons looks [21:41] Noskcaj, (might be call "monitor" or "display") to might be "called" [21:41] i approved slickymaster's one, but it needs merging [21:41] all those changes look good [21:41] I'll merge his [21:41] so I think the only thing left is the is -> should be stuff right? [21:42] balloons, that and the wireless networking test [21:42] excellent [21:43] Noskcaj, this https://code.launchpad.net/~noskcaj/ubuntu-manual-tests/xfce4panel/+merge/168858 has to be done by david [21:43] ohh nvm, I see it ;-) [21:43] :) [21:49] balloons, the last upload is going now. i think that's all the hardware tests [21:54] i'm looking over [21:55] ok, everything looks good [21:55] let me do a full review again Noskcaj [21:55] ok, ty [21:58] Noskcaj, :-( This is still using unity stuff for no reason.. [21:58] /home/nskaggs/projects/ubuntu-manual-tests/testcases/hardware/1477_Builtin Keyboard [21:58] can you make it generic? [21:58] one sec [21:58] sure.. I'll just keep rambling my thoughts here [22:02] balloons, uploaded [22:05] Noskcaj, another small tweak..

Insert a media card into the reader.

A suggestion window should open for the card

[22:05] I'm not sure we can assume or need to assume a suggestion window will appear on every flabor [22:05] ok [22:06] this is from 1484_Internal Data Card Reader [22:06] you can simplify the whole thing and just say open the card up with a file manager [22:06] we want to test the read and writing to the card, etc [22:07] in the suspend and resume, you don't need to mention using firefox specifically [22:07] 1486_Suspend & Resume [22:07] ok [22:07]

Open a few applications in on the desktop, including Firefox

[22:07] pushing now [22:09] ok, the final tweaks I see [22:09] balloons, can you explain test 1399_unity startup? it seems to have a translation part [22:10] 1300,1301,1302,1465,1504,ubuntu touch/1518 and ubuntu touch/1519 all should drop the 'should be' language and keep the 'is' language. The other tweaks in those files are good [22:10] Noskcaj, let me look at it [22:11] ohh right [22:11] that was imported from the old unity manual tests [22:11] ok [22:11] essentially it's just a gut check that unity starts up and the desktop loads [22:11] including translations.. [22:12] I just updated it so it made sense, but i doubt it will every be looked at [22:16] * Noskcaj leaves for school === salem_ is now known as _salem === alesage is now known as alesage|afk [23:57] hello!