--- Log opened Sat Jul 12 17:08:44 2008 18:01 <@tuxmaniac> ============= Global Bug Jam Preparatory session 1 begins =================== 18:01 -!- mode/#ubuntu-in-classroom [+o techno_freak] by ChanServ 18:01 -!- lut4rp|afk is now known as lut4rp 18:01 <@tuxmaniac> Welcome folks! Can we have a roll call of people in here??? 18:01 < lut4rp> hola 18:02 < punchagan> hi 18:02 * techno_freak is Parthan 18:02 * sumitc is Sumit 18:02 * lut4rp is Pratul 18:02 * parthan is Parthan-Log 18:02 * punchagan is Puneeth 18:02 * slytherin is Onkar 18:02 < riddle28> hi all 18:02 * tuxmaniac is Aanjhan Ranganathan 18:03 * bliZZardz is Venkatraman.S 18:03 -!- Sup3rkiddo [n=sudharsh@unaffiliated/sudharsh] has joined #ubuntu-in-classroom 18:03 <@tuxmaniac> This is in preparation of the global bug jam that is being organised from August 8th 2008. 18:03 -!- riddle28 [i=ca992984@gateway/web/ajax/mibbit.com/x-ed16afca05a7150e] has quit ["http://www.mibbit.com ajax IRC Client"] 18:04 <@tuxmaniac> Link: https://wiki.ubuntu.com/GlobalBugJam 18:04 <@tuxmaniac> Since there were a lot of queries wrt how I can join Ubuntu, contribute to Ubuntu, help out with bugs etc., we decided to hold a introductary session on Bug cycle and other basics. 18:04 <@techno_freak> Note: All questions should be asked at #ubuntu-in only. techno_freak will copy them here one by one during QnA breaks 18:05 -!- riddle28 [i=ca992984@gateway/web/ajax/mibbit.com/x-9b28917e273faf12] has joined #ubuntu-in-classroom 18:05 <@tuxmaniac> This is the first of the many such sessions to follow. Also this is the first such "Jam" organised by us, so any suggestions to imrpve it from the next time are most welcome. (flame baits even ;P) 18:05 * lut4rp holds his breath 18:06 <@tuxmaniac> For your info we have the bot "ubottu" with us on #ubuntu-in to point us to any bug report and other general queries. Please use the bot judicially and please do not abuse. 18:06 < bliZZardz> !ubottu 18:06 < lut4rp> bliZZardz: in #ubuntu-in 18:06 * riddle28 is vidyuth 18:07 <@tuxmaniac> The agenda (tentative and flexible) is like this. 18:07 <@tuxmaniac> Today will be a intro to Bug squashing. 18:07 <@tuxmaniac> Basically covering the following topics 18:08 <@tuxmaniac> 1. Intro to Launchpad and creation of Accounts. 18:08 <@tuxmaniac> Here I will be giving a short description of the future sessions that are planned too. 18:08 <@tuxmaniac> 2. Intro to Bug life cycle and triaging by Parthan 18:09 <@tuxmaniac> He will go through the entire basics of bug triaging , the bug control squalds we have and how to do effective bug triaging. (supported by Onkar ) 18:09 <@tuxmaniac> 3. After this we have a short list of untriaged bugs to work on. 18:09 * lut4rp has held his breath for too long now. 18:09 <@tuxmaniac> We shall all dive into the list and start squashing them right away 18:10 < lut4rp> aye aye 18:10 <@tuxmaniac> Tomorrow will be mostly on Packaging 18:10 <@tuxmaniac> So any doubts until now? 18:10 <@tuxmaniac> QA break 18:12 <@tuxmaniac> Can we proceed? 18:12 <@tuxmaniac> Assumed all are clear :-) 18:12 <@slytherin> tuxmaniac: please do 18:12 < lut4rp> hear hear 18:12 <@tuxmaniac> We are planong to conduct a few packaging jam sessions too in the future 18:13 <@techno_freak> ---- No Questions - Start Session 1 Part 1 ----- 18:13 <@tuxmaniac> and also as we get more acquainted with bug triaging we shall be focussing on more specific bugs related to some application and squash them 18:13 <@tuxmaniac> and a lot more is planned so that we get noticed in the ubuntu world :D 18:14 <@tuxmaniac> So.. How many here know what launchpad is? 18:14 < lut4rp> oh good 18:14 < lut4rp> tuxmaniac: i do! 18:14 < sumitc> I do 18:14 < punchagan> i do 18:14 <@techno_freak> i do 18:14 * riddle28 doesnt 18:14 <@tuxmaniac> For thos who dont know. please check the page http://launchpad.net/ 18:15 * bliZZardz does - also suggests that rollcounts need not be done for every Q ; if needed, can be done in #ubuntu-in 18:15 <@tuxmaniac> it is the single place where all the bug reports get tracked 18:15 <@tuxmaniac> bliZZardz: yes. agreed 18:15 <@tuxmaniac> Does everyone here carry an account with launchpad? 18:15 <@tuxmaniac> *That* is the first step 18:15 < lut4rp> i do 18:16 < sumitc> yes 18:16 < punchagan> yes 18:16 <@tuxmaniac> If someone is here without a LP account this is the time to do it 18:16 < lut4rp> riddle28: go ahead :) 18:16 <@techno_freak> i would suggest let us help riddle28 to set up his a/c if he is interested 18:17 < lut4rp> good idea 18:17 < riddle28> k 18:17 <@tuxmaniac> riddle28: please ask your doubts here. (permission to you only :-)) 18:17 <@tuxmaniac> we shall proceed together 18:17 < riddle28> ya doing it 18:17 < riddle28> ya i am interested 18:17 <@tuxmaniac> For those who have got an LP account, have you all become Ubunteros? 18:18 < sumitc> how do I become one? 18:18 < riddle28> k 18:18 < riddle28> regisetering 18:18 <@tuxmaniac> i.e signed the Code of Conduct? 18:18 <@tuxmaniac> sumitc: ^ 18:18 < lut4rp> yes, i did 18:18 <@tuxmaniac> that is the second step 18:18 < sumitc> tuxmaniac,ok 18:18 < riddle28> k registration done 18:19 <@tuxmaniac> riddle28: cool! 18:19 <@techno_freak> riddle28, cool 18:19 <@tuxmaniac> Q2: Please sign code of conduct everybody 18:19 <@techno_freak> punchagan> how do I sign code of conduct? 18:19 < riddle28> :) 18:20 <@tuxmaniac> hehe. Wait I am using the edge lp which is beta. let me redirect. 18:20 < riddle28> thnks 18:20 < riddle28> next step 18:21 <@tuxmaniac> OK1 once you guys have LP account you can edit and triage bug reports 18:21 <@tuxmaniac> from now on techno_freak will take you through the bug lofe cycle and other things alpong with slytherin 18:22 <@techno_freak> thanks tuxmaniac 18:22 <@techno_freak> tuxmaniac will copy questions for me, when i give QA breaks :) 18:23 <@techno_freak> ------- Session 1 Part 2 - Understanding Bugs in Ubuntu and LP -------- 18:23 <@techno_freak> We just now heard from tuxmaniac about Launch Pad, called as LP in short 18:24 <@techno_freak> LP serves multiple purposes, as a project management mechanism primarily 18:24 <@techno_freak> one important aspect of LP is it's issue tracker 18:25 <@techno_freak> which for Ubuntu is available at https://launchpad.net/ubuntu/+bugs 18:25 < lut4rp> mmhmm 18:25 <@techno_freak> the LP Bugs serves not only the users to report the bugs they encounter, but also for the QA and Devs 18:26 <@techno_freak> it gives a whole picture of the ubuntu project 18:26 <@techno_freak> From the user perspective, LP Bugs is a place where they can report the bugs they encounter when using Ubuntu 18:26 <@techno_freak> there are few underlying clauses to note in the above statement 18:27 <@techno_freak> [1] Ubuntu LP supports only bugs on packages which are officially supported and available in Ubuntu repositories 18:27 <@techno_freak> like main, universe, multiverse, restricted etc. 18:27 < punchagan> ok 18:28 <@techno_freak> if you are installing a package from a source other than ubuntu repository, we do not support the bugs on that s/w and the issues need to be reported to their source issue tracker only 18:28 <@techno_freak> [2] Bugs should be on the currently supported releases only, at any point of time 18:29 <@techno_freak> i.e a bug on breezy now is rather considered invalid 18:29 <@techno_freak> so at a point of release schedule, if a older release is losing its support then bugs on that release versions are not considered anymore 18:29 -!- Ghost-R [n=G_`@unaffiliated/g/x-763248] has joined #ubuntu-in-classroom 18:30 <@tuxmaniac> punchagan: [question] What are the supported versions as of now? 18:30 <@techno_freak> and such bugs need to be verified with latest release of Ubuntu (including the current development version) 18:32 * slytherin will answers punchagan's both questions 18:32 <@techno_freak> slytherin, sure, go on 18:34 <@slytherin> LTS version are supported for 3 years on desktop and 5 years on server. Standard releases are supported for 1.5 years. 18:34 <@techno_freak> [3] Considering X to be the current development release, Y to be the current stable release and Z to be previous stable release, the bugs reported on Z needs to be confirmed in Y (mandatory) and will need to be checked in Z as well 18:34 <@slytherin>  So as of now, Dapper LTS (6.06), Feisty (7.04), Gutsy (7.10) and Hardy LTS (8.04) are supported. 18:35 <@techno_freak> slytherin, thanks 18:35 <@techno_freak> Hope you got the basic idea of what can be reported 18:35 <@techno_freak> Next, there are basically two types of bugs 18:36 <@techno_freak> [1] bugs reported by apport with an apport crash report attached to the bug report 18:36 <@tuxmaniac> techno_freak: hold for QA? 18:36 <@techno_freak> tuxmaniac, sure 18:36 <@techno_freak> ------- QA for Part 2 --------- 18:37 <@tuxmaniac> proceed 18:37 <@techno_freak> ok 18:38 <@techno_freak> this kind of bugs generally consist of a list of files attached to the bug, mainly Dependencies.txt ProcStatus.txt and CoreDump.gz 18:39 <@techno_freak> coredump is a special case and might contain some confidential information 18:39 <@techno_freak> hence, bug squad team decided to make such bug reports as private and hidden 18:39 <@techno_freak> until the coredump is processed and necessary info is parsed out (non confidential info only) 18:40 <@techno_freak> this is an automatic process expected to happen 18:40 <@techno_freak> but at times, something goes wrong and the bug remains private 18:40 <@techno_freak> this is handled by the bug squad members who have experience in handling apport bugs 18:40 <@techno_freak> [2] bugs reported manually by users 18:41 <@techno_freak> What we are going to be interested in session is type [2] bugs 18:41 <@techno_freak> ----- Questions? ---------- 18:42 <@slytherin> yes 18:42 <@slytherin> (22:10:09) tuxmaniac: [question] what is apport 18:42 <@techno_freak> <ubot3> apport: automatically generate crash reports for debugging. In component main, is optional. Version 0.103 (hardy), package size 102 kB, installed size 452 kB 18:42 <@tuxmaniac> 22:10 < riddle28> what do u mean by confidential?? 18:42 <@tuxmaniac> 22:10 < riddle28> corresponding to the software? 18:43 <@slytherin> tuxmaniac: apport is a tool which automatically gather information needed to debug crashes. 18:43 <@techno_freak> confidential as in some user information might be present in the file, might be some password too at times 18:43 <@slytherin> riddle28: Sometimes crashes may contain some information that users may not want to expose ex. filename or some useraccount name. 18:44 < punchagan> techno_freak: and how is that[confidential info] removed manually right? 18:45 <@slytherin> punchagan: Not manually. Automatically. apport retrace is a process which will keep only necessary information like stack traces, symbol tables etc. 18:45 <@techno_freak> when a bug report contains a coredump, it is available to restricted audience which includes the bug reporter and subscribed members 18:46 < riddle28> hmm 18:46 < punchagan> ok. only when something goes wrong, the experienced bug squad members come in? 18:46 <@techno_freak> there is a very little chance of something going wrong. 18:46 < punchagan> ok. 18:46 <@techno_freak> please keep your questions to #ubuntu-in 18:46 < punchagan> ok. 18:47 <@techno_freak> ----- Contd. ----------- 18:47 <@techno_freak> The next important thing that every wannabe triager should understand is the Bug Cycle 18:47 <@techno_freak> this is the life cycle of a bug from the point it gets reported 18:47 <@techno_freak> lets go step by step and find out what happens in the process 18:48 <@techno_freak> [1] An user encounters something wrong, may be a crash, or something not working the way he expected it to 18:48 <@techno_freak> he reports the bug in launchpad, by filling in the fields he is sure of 18:49 <@techno_freak> [2] The bug gets recorded as a New, Uncomfirmed bug and appears in the list of untriaged bugs 18:49 <@techno_freak> this list is available in LP - https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&field.status%3Alist=New&field.importance%3Alist=Undecided&assignee_option=none&field.assignee=&field.owner=&field.component=1&field.component=2&field.component-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_no_package.used=&search=Search 18:50 <@techno_freak> from now, the bug triager gets involved with the bug.. 18:50 <@techno_freak> two terminologies to know 18:51 <@techno_freak> [i] Triage - this is very similar to the practise followed in hospitals, where any incoming emergency cases are attended by a triager (a nurse of junior doctor) who checks the vital signs, does some emergency measures and takes the patient to the appropriate section of the hospital 18:51 * slytherin raises question flag 18:52 <@techno_freak> slytherin, yes 18:52 <@slytherin> (22:18:14) riddle28: wat is meant by triager? 18:52 <@slytherin> riddle28: A bug triager is a person who helps bug reported provide as much as possible useful information so that bug can be tracked down to it's root cause. 18:52 <@techno_freak> am coming to that point 18:52 < riddle28> k 18:52 <@techno_freak> very similar to above process is what a bug also undergoes 18:52 <@techno_freak> a bug is much like an incoming patient with some problem 18:53 <@techno_freak> but only a doctor can recognize it correctly 18:53 <@techno_freak> but but which doctor? which department? which specialist? need operation? or just a band aid is enough? 18:53 < lut4rp> aah 18:54 <@techno_freak> similarly when a bug comes in, it needs a very few basic information available with it so the related developer can work on it 18:54 <@techno_freak> as we know there are 1000s of packages in Ubuntu that we maintain 18:54 * riddle28 is overjoyed by the terminology 18:54 <@techno_freak> and 1000s of developers and maintainers contribute 18:54 <@techno_freak> so when a bug comes in, it is not practical for the 1000s to keep looking for the bugs on their packages 18:55 <@techno_freak> remember devs are also contributors, volunteers who devote their time on their own interest 18:55 <@techno_freak> more importantly the amount of bugs reported every hour is quite numerous that it is not feasible for the devs to keep looking at LP all the time 18:56 < punchagan> hmm.. 18:56 <@techno_freak> dev time is precious and it needs to be put on further improvements too 18:56 <@techno_freak> thus we need some standing between the two ends - the users who report bugs and the devs who handle bugs and fix them 18:57 <@techno_freak> this middle (wo)men who perform the wonderful role of taking the incoming bugs, help improve them that they make sense to the devs, assign the bugs to appropriate people, montior the bugs and help them get fixed 18:57 <@techno_freak> thus as slytherin said, triager is one who improves the meaning and information contained in a bug that it makes more sense to the dev to work on it 18:58 < riddle28> hmm 18:58 < punchagan> cool! 18:58 <@techno_freak> so remember the meaning of [1] Triage and [2] triager 18:58 <@techno_freak> now lets come back to our topic of bug cycle 18:58 <@techno_freak> [1] user reports bug 18:58 <@techno_freak> [2] bug appears as new, unconfirmed bug 18:59 <@techno_freak> ... 18:59 <@techno_freak> the step [1] can be done by anyone who has registered with LP 18:59 <@techno_freak> all you need to report a bug is an LP a/c 18:59 <@techno_freak> ------ Questions? --------- 19:00 <@techno_freak> ok lemme proceed 19:01 <@techno_freak> [3] from now, the bugs moves into triager land 19:01 <@techno_freak> the triager is primarily a member of Ubuntu Bug Squad 19:01 <@techno_freak> the exclusive part of the community who spend their precious hours on caring about your problems 19:02 <@techno_freak> remember triager really care for the users, and hence need to be polite and helpful to those who report bugs 19:02 <@techno_freak> at no point show your frustration on them 19:02 < punchagan> hmm 19:03 <@techno_freak> they are users and they do not understand the internal fundas about development 19:03 <@techno_freak> and they need not 19:03 <@techno_freak> so it's triager's duty to help them provide all info that a dev requires 19:03 <@techno_freak> so a triager looks at the bug, looks at the information provided by the reporter 19:04 <@techno_freak> there is a minimal requirement that every bug needs to provide at minimum 19:04 -!- riddle28 [i=ca992984@gateway/web/ajax/mibbit.com/x-9b28917e273faf12] has quit ["http://www.mibbit.com ajax IRC Client"] 19:05 <@techno_freak> this is available in https://wiki.ubuntu.com/Bugs/HowToTriage 19:05 < punchagan> ok. 19:05 <@techno_freak> so the first thing a triager looks is whether the basic information such as Ubuntu release version, package release version is available or not 19:05 -!- riddle [i=ca992984@gateway/web/ajax/mibbit.com/x-c75c8675e4173e2f] has joined #ubuntu-in-classroom 19:05 <@techno_freak> the second thing the triager ensures is whether the bug is assigned to a package or not 19:06 <@techno_freak> every bug needs to be assigned to at least one package 19:06 -!- Sup3rkiddo [n=sudharsh@unaffiliated/sudharsh] has quit [Read error: 110 (Connection timed out)] 19:06 -!- riddle is now known as riddle28 19:06 -!- Sup3rkiddo [n=sudharsh@unaffiliated/sudharsh] has joined #ubuntu-in-classroom 19:06 <@techno_freak> this means, when in doubt and at certain odd cases more than one package might be related to a bug 19:07 <@techno_freak> so the task #2 is ensure there is an associated package for the bug 19:07 <@techno_freak> the 3rd task is somewhat tricky and there are people specializing in this task 19:08 <@techno_freak> it is checking for duplicates, which means the bug might have been reported by someone alredy 19:08 <@techno_freak> hence the new bug is just a repetition of the same bug and hence a duplicate 19:08 <@techno_freak> though this sounds simple, this is kind of a tar pit 19:09 <@techno_freak> new triagers are known to jump into conclusions of similar looking bugs and mark them as duplicates 19:09 <@techno_freak> remember one thing "similar symptoms do not mean similar problems" 19:09 <@techno_freak> it needs extra introspection into the bugs and hence not suggested for new triagers 19:09 < punchagan> ok. 19:10 <@techno_freak> this is very common during times when something broke in the package and every one encounters the same bug 19:10 <@techno_freak> Thus in [3] a triager tries to get all possible information from the bug reporter about the bug environment 19:11 <@techno_freak> [4] This is a second step of [3] that the reported bug should be reproducible by someone using the same package 19:11 <@techno_freak> thus we ask the reporter for steps of reproducing the bug 19:11 < riddle28> hmm 19:11 <@slytherin> if they are not available already 19:11 <@techno_freak> the reporter has to report how he actually encountered the bug, the process which he thinks actually caused the bug 19:12 <@techno_freak> and how any other person may try to get the same bug 19:12 <@slytherin> For example .... 19:12 <@techno_freak> thus, another ubuntu user/triager/devel may try to reproduce the bug and understand why it went wrong 19:13 <@slytherin> If a report is there against firefox "FF crashed" then one has to ask reporter on which site did it crash, does it use any flash, java. Was FF exxtensions was he using etc. 19:13 <@techno_freak> this is another chance for contribution in bugs - if you have the same reported package and same/similar environment you can try to check whether the bug happens at your end 19:14 <@techno_freak> if you also face the same issue, you can change the status of the bug to "Confirmed" 19:14 <@slytherin> 'New' -> 'Confirmed' 19:14 <@techno_freak> or, as a triager, if another person (not the original reporter) can reproduce the bug and if enough information are available regarding the bug, we confirm it as well 19:14 <@techno_freak> thus the bug now moves for [New] ---> [Confirmed] 19:15 <@techno_freak> [5] what if there wasn't enough information available in the bug report? 19:15 <@techno_freak> We looks what's missing in the bug report, ask the reporter(s) to provide the information, often telling them how to get those information and how to attach with the bug report 19:16 <@techno_freak> this includes certain outputs of terminal commands, certain log files, certain config files etc 19:16 <@techno_freak> sometime we also for screenshots for us to understand the reported bug better 19:17 <@techno_freak> when we do this, we change the status of the bug as [New] --> [Incomplete] 19:17 <@techno_freak> [6] Sometimes we might find that the bug is reported on packages not found or supported in official Ubuntu repos, or belongs to an unsupported version 19:18 <@techno_freak> on these occasions, we change the bug stats as [New] --> [Invalid] 19:19 <@techno_freak> this closes the bug as invalid as well 19:19 < punchagan> ok 19:19 <@techno_freak> bugs marked as incomplete will expire in 90 days if the reported doesnt file a response 19:19 <@tuxmaniac> Also note that one must be polite in informing the same. :-) 19:20 < punchagan> hmm 19:20 <@techno_freak> yes, when you reply to a bug report you might take the help of standard bug responses available at https://wiki.ubuntu.com/Bugs/Responses 19:20 < riddle28> ohh 19:20 <@techno_freak> Once a bug is confirmed, the bug moves into the developers/maintainers eyes 19:21 <@techno_freak> maintainers may check the bug and respond to it 19:21 <@techno_freak> it might be either an explanation, or asking for more info, or some status on the bug 19:21 <@techno_freak> -------- Questions? -------------- 19:22 <@slytherin> techno_freak: yes, two 19:22 <@slytherin> (22:44:47) punchagan: [question] can a bug report be improved by anybody? 19:23 <@techno_freak> yes, anybody with LP account can provide extra information if they can reproduce the bug 19:23 <@slytherin> techno_freak: ^^ 19:23 < punchagan> hmm 19:23 <@techno_freak> the important point is "if they can reproduce the bug" 19:23 < punchagan> yes. got it. 19:23 <@slytherin> next question ... 19:23 <@slytherin> (22:49:32) sumitc: [question] Do we inform the reporter as the status of a bug changes? 19:24 <@techno_freak> no, because once we assign the bug to a package, the corresponding maintainers of the package or members of the team handling that package/software gets subscribed to the bug 19:24 <@techno_freak> any changes on the bug are also reported to them 19:25 < sumitc> ok 19:25 <@slytherin> sumitc: Any chnages to a bug are sent by email to reporter, anyone who has ever added a comment and subcribers to the bug. 19:25 <@techno_freak> the bug squad team keeps their eyes wide open and tries to give attention to every incoming bug. that's why we always call for more people to join bug squad :) 19:25 < sumitc> got it 19:26 < lut4rp> hmm 19:26 <@techno_freak> in addition you can also subscribe to bugs of your interest and observe the process without getting involved with it 19:26 <@techno_freak> ------ Wrap up of Bug Cycle ------ 19:27 <@slytherin> techno_freak: You forgot 'Invalid' state 19:27 <@techno_freak> slytherin, covered in [6] 19:27 <@slytherin> techno_freak: Didn't notice. :-( 19:28 <@slytherin> I would like to reiterate few points about traiging 19:28 <@techno_freak> user files bug -- triager looks -- assigned to package -- checks for required info -- asks for more info -- changes status --- monitors comments and replies 19:28 <@techno_freak> slytherin, sure, take on... 19:29 -!- Sup3rkiddo [n=sudharsh@unaffiliated/sudharsh] has quit [Success] 19:29 <@slytherin> 1. It is extremely important to be polite and patient. 19:29 < riddle28> thts nice 19:29 <@tuxmaniac> 22:58 < punchagan> [question] so basically its the [New] bugs that doesn't have any triager looking at them, and those are the ones you pick. right? 19:29 <@techno_freak> punchagan, yes, that's the place where new triagers need to start 19:30 < punchagan> ok. 19:30 <@slytherin> 2. Do not assign bugs to wrong packages in hurry. 19:31 <@techno_freak> The rule of thumb is, when you have even the most slightest doubt, ask it in #ubuntu-bugs 19:31 <@techno_freak> bug squad strength is helping one another 19:32 < punchagan> yay! 19:32 <@techno_freak> slytherin will explain more on priorities now 19:32 < riddle28> ohhh nice there is a bug channel 19:32 <@tuxmaniac> 22:59 < tazz> [question] what is wishlist 19:32 <@slytherin> tazz: answer coming shortly 19:32 < riddle28> :) 19:33 <@slytherin> Bugs have 5 priorities. Critical, High, Medium, Low, Wishlist 19:33 <@slytherin> Critical - Blocks a release. 19:34 -!- ubunturos [n=chatzill@59.184.30.88] has joined #ubuntu-in-classroom 19:34 <@slytherin> High - Major problem in functionality of a package in 'main' section and the package 19:34 < ubunturos> tuxmaniac: there's a way you can change the mode of ubuntu-in 19:34 <@slytherin> High means no workaround is available 19:35 <@slytherin> Medium - Problem with easy workaround available. 19:36 <@slytherin> Low - Minor problem. Does not block use of application. ex. missing icon in menu 19:36 <@slytherin> Wishlist: Nice to have. Not a problem. Mostly an update request or feature addition request 19:37 <@slytherin> tazz: ^^ 19:37 <@slytherin> Now the questions. 19:37 <@slytherin> (23:05:31) punchagan: [question] who prioritizes the bugs? 19:38 <@slytherin> Bugs are prioritised by QA team bases on the policies explained above. To get QA membership, you have to be really good triager and demonstrate your understanding about bugs. 19:38 < punchagan> ok. 19:38 <@slytherin> (23:08:13) sumitc: [question] Did not get the wishlist category 19:39 <@techno_freak> we call them as Bug Control Team 19:39 <@slytherin> sumitc: If I file a bug about updating version of a package, it is wishlist, because it is nice to have. 19:40 < sumitc> hslytherin: ow is that a bug? 19:40 <@slytherin> sumitc: Or say I request for certain theme to be packaged, it is wishlist 19:40 < sumitc> slytherin:^^ 19:40 < sumitc> ok 19:40 <@techno_freak> sumitc, it is not a bug, as in it is in misfunctionality or misoperation, but a missing functionality which the users feels would be great to have it that way 19:40 < sumitc> got it 19:40 < riddle28> so we can ask for extensions also?? 19:40 -!- munichlinux [n=prashant@59.92.101.98] has joined #ubuntu-in-classroom 19:40 <@slytherin> riddle28: what extensions? 19:41 < riddle28> extensions or themes we like 19:41 < riddle28> to be included in the package? 19:42 <@slytherin> riddle28: yes, as I said it is wishlist. It will not be necessarily fixed immediately. 19:42 < riddle28> k, so we expect them to be released along with the new version 19:43 <@slytherin> riddle28: Mostly 19:44 < riddle28> hmm 19:44 <@slytherin> techno_freak: Can we move next part of session? I suggest that we consider one bug and have open discussion about what others think about it. 19:44 <@slytherin> techno_freak: Do you want a break? 19:45 <@techno_freak> slytherin, one minute, tuxie had added some new bugs to the wiki 19:45 <@slytherin> Ok. 19:48 <@techno_freak> check the wiki at http://ubuntu-in.org:81/index.php?title=Events/BugJamPrepSessions 19:48 <@techno_freak> at the end, there are three bugs mentioned 19:48 <@techno_freak> check them in LP 19:49 <@techno_freak> bug #247802 lacks package assigned to iy 19:49 <@techno_freak> it 19:50 <@techno_freak> you might also be not sure whether he is meaning FF3beta5 or FF3 from FF's website 19:51 <@techno_freak> also, there is a crash report as a .txt file 19:51 <@techno_freak> but it looks like he is not telling it clearly when he encountered this bug and how to get it again 19:53 <@techno_freak> he mentions two generalized info [1] "when new url is opened", what is the url, does it contain JS or flash? does all urls crash or only specific urls crash, if so what are they? 19:53 < sumitc> is it an open discussion? 19:53 <@techno_freak> [2] "closing and reopening firfox don't sovle the crash" does this mean he cant reopen firefox again? if so what he does to reopen, logout? reboot? 19:54 <@slytherin> sumitc: yes 19:54 <@techno_freak> see, how many information are missing for the bug 19:54 < punchagan> hmm 19:54 < riddle28> [question] what is that text file exactly?? 19:54 <@techno_freak> now, what will a triager do with this bug? 19:55 <@techno_freak> riddle28, it looks like a crash report. you can also ask him how he got that, he hasnt mentioned it. 19:55 <@techno_freak> slytherin, can you work on this bug and show them? (will have my dinner in the time) 19:56 <@slytherin> techno_freak: will try 19:56 <@techno_freak> ok :) 19:56 < riddle28> ya 19:56 < riddle28> do we get that in log files?? 19:57 < riddle28> ?? 19:57 <@techno_freak> tuxmaniac, back? 19:57 <@slytherin> Ok. Let's fist identify what is wrong with bug 19:57 <@slytherin> riddle28: Please be patient. 19:57 <@tuxmaniac> techno_freak: yes. at home. using slow connection. 19:58 <@slytherin> Following are problems identified with the bug 19:58 < riddle28> k 19:59 <@tuxmaniac> slytherin: you putting in the missing information for that bug? 19:59 <@slytherin> tuxmaniac: let me first explain it here. 19:59 <@tuxmaniac> ok 20:00 <@slytherin> 1. Package is wrong. 2. No url mentioned. 3. From stack trace it seems the flash is involved and it is adobe flash (not gnash). 20:01 <@slytherin> So as of now we can ask only 1 thing to him. 1. Which url. 20:01 <@slytherin> I will make changes so you guyes can take a look then. 20:02 < sumitc> what changes will you make? 20:02 -!- ubunturos [n=chatzill@59.184.30.88] has left #ubuntu-in-classroom [] 20:02 <@tuxmaniac> sumitc: He will add comment and description. Wait until he finishes 20:02 <@techno_freak> sumitc, check the bug report page after he triages it 20:03 < sumitc> alright 20:05 <@tuxmaniac> Some relatively easy untriaged bugs are being updated at the wiki page. after slytherin finishes explaining the bug sample, please feel free to pick a bug of your choice and triage. I am updating the wiki page as and when I find relatively easy bugs (AFAIK) 20:06 <@tuxmaniac> please ask help here if you have doubts 20:06 <@slytherin> Done. 20:06 < punchagan> tuxmaniac: I'll have to sign the CoC first right? 20:06 < riddle28> can anybody triage it?? i mean who has the account at launchpad 20:06 <@tuxmaniac> riddle28: yes. 20:06 <@tuxmaniac> punchagan: no 20:07 <@slytherin> Changes made - Package changed, state changed to incomplete since it lacks information and added dialog asking about information. 20:07 < riddle28> ?? 20:07 < riddle28> me too 20:08 <@tuxmaniac> Also one can see the "Activity Log" link to see what parameters have been changed by whom. 20:08 <@tuxmaniac> riddle28: yes you can triage too 20:09 < punchagan> tuxmaniac: This bug is not recorded as needing to be fixed in linux (Ubuntu). what does this mean? 20:09 < punchagan> I got some button saying "Also needs fixing here" and I clicked it. :( 20:09 <@techno_freak> punchagan, slytherin changed the assinged package from linux(Ubuntu) which is the default package for all unassigned bugs 20:10 < riddle28> k 20:10 <@techno_freak> to firefox-3.0 (Ubuntu) 20:10 <@slytherin> punchagan: bad job. never click a button if you don't understand what it says. Come out of windows world please. 20:11 < punchagan> yes. slytherin I understand I screwed. 20:11 < punchagan> sorry. 20:11 <@techno_freak> changed it 20:11 < punchagan> did I say, I reproduced the bug? 20:11 <@techno_freak> ? 20:11 < punchagan> what did that mean, actually? 20:12 <@tuxmaniac> punchagan: no. You just told that it needs to be fixed in Ubuntu, as against slytherin 's change of assigned package 20:12 <@techno_freak> it means, that bug is also related to the package which just now got unassigned from the bug 20:12 < punchagan> oh ok. got it. 20:12 <@tuxmaniac> punchagan: and you just learnt lesson 1, that to be careful while triaging bugs 20:12 < punchagan> yes. 20:12 < punchagan> and techno_freak how did you change it? 20:12 <@techno_freak> triage is a very responsible jobs 20:12 <@slytherin> Please note that default package of new bugs is none. But users many time report against linux which is related to kernel. 20:13 < punchagan> ok. 20:14 < sumitc> can we discuss Bug #247781? 20:14 <@slytherin> sumitc: sure, that is a tricky one. 20:14 < sumitc> yes, nothing seems wrong 20:16 < riddle28> now how does a terminal doesnt respond to its user 20:16 < sumitc> I have a question, does bash start if the .bashrc file is messed up? 20:17 < riddle28> interesting 20:18 <@slytherin> sumitc: it should, but i don't know for sure. But there is no reason a normal user will mess up .bashrc 20:19 < punchagan> why is it tagged apport-bug? 20:19 <@tuxmaniac> the last few bugs are fairly easy to handle IMO. And I am adding more. So keep track of that pagethroughout th session 20:19 -!- bliZZardz [n=venkat@59.92.71.148] has left #ubuntu-in-classroom [] 20:19 < sumitc> maybe we should find out what files bash needs to start up, then ask the reporter to revert all those files to their default state, and see what happens 20:20 <@slytherin> SO who can think of what to ask reporter about terminal bug? I can't think of anything. 20:20 < punchagan> slytherin: why is it tagged an apport-bug? 20:20 < sumitc> slytherin,what do you think of my idea? 20:21 <@slytherin> punchagan: don't know, perhaps terminal crashed and hence apport created the bug report. 20:21 < riddle28> but sumitc if a user is newly logging in 20:21 <@slytherin> sumitc: second lesson. If you are unsure, leave it as it is. Let someone smarter handle it. :-) 20:21 <@techno_freak> check now ;) 20:21 < sumitc> alright. :) 20:22 < sumitc> yes, riddle28? 20:22 < riddle28> i mean after restarting or installing 20:22 < riddle28> surely all files would have been installed required for bash starting 20:23 <@tuxmaniac> right 10 bugs to squahsh 20:23 <@techno_freak> cool tuxmaniac 20:23 < riddle28> hmm 20:23 < sumitc> riddle28, is it so? 20:23 < sumitc> riddle28, I dont have any idea about whether that is the case or not 20:24 < riddle28> that was a general answer by tuxmaniac 20:24 < riddle28> :P 20:24 <@slytherin> So let's move to next bug as no one has any idea what to do with it. 20:24 < riddle28> but obviously we were unsure whether it was a bug or not 20:25 <@techno_freak> have asked some more info from the reporter 20:25 <@tuxmaniac> slytherin: I suggest we come from last. Some relatively easy bugs are there. 20:25 <@slytherin> tuxmaniac: sure 20:25 < riddle28> this is corresponding to mysql 20:25 < riddle28> i dont know it 20:25 < riddle28> :( 20:26 <@slytherin> riddle28: right, and someone is already handling it 20:26 < sumitc> Bug 247861 should be easy to reproduce 20:27 <@slytherin> sumitc: yes, create a new use on your machine and try reproducing it. 20:27 <@tuxmaniac> can someone take up responsibility and try to reproduce the bug and confirm? we will guide if you make mistakes. 20:28 <@slytherin> sumitc: Do you think you can take up the task 20:28 < sumitc> yes 20:28 < sumitc> give me some time to reproduce it 20:28 <@tuxmaniac> sumitc: you might have to log out and login again :-) 20:28 < sumitc> yes. 20:28 -!- Raseel [n=raseel@121.243.211.134] has joined #ubuntu-in-classroom 20:29 < sumitc> So I'm trying it out guys 20:29 < riddle28> wat is this short login?? 20:29 < riddle28> didnt understand it 20:29 <@tuxmaniac> riddle28: can you try that one? atleast let us know what to ask? 20:29 < sumitc> see you later 20:29 <@slytherin> riddle28: he said he uses only one letter as username 20:29 -!- sumitc [n=chatzill@unaffiliated/sumitc] has quit ["ChatZilla 0.9.83 [Firefox 3.0/2008060309]"] 20:29 <@tuxmaniac> riddle28: a user with id 'l" etc 20:30 <@slytherin> Ok, next bug is 247930 20:30 < riddle28> ya but wat is short login 20:30 < riddle28> i didnt get that 20:30 <@tuxmaniac> riddle28: the next one I have asked on #ubuntu-india is also simple. Like to try it out? 20:30 <@tuxmaniac> riddle28: he just mentions short usernames to be short login 20:30 * punchagan too trying to reproduce. 20:30 < riddle28> ohh 20:30 <@tuxmaniac> so we will see so many people logging out now 20:30 -!- punchagan [n=user@59.93.85.120] has quit [Remote closed the connection] 20:30 <@tuxmaniac> :-) nice to see 20:31 <@slytherin> tuxmaniac: Does inkscape use launchpad for bug tracking? 20:31 <@tuxmaniac> slytherin: no. and hence I chose the bug. :-) 20:31 <@slytherin> tu, yes it does. Just checked there website 20:31 < riddle28> 247930?? 20:31 < riddle28> k i will not logout , i mean give me another 20:31 < riddle28> :P 20:31 <@tuxmaniac> oh ok 20:32 <@slytherin> tuxmaniac: http://www.inkscape.org/report_bugs.php?lang=en 20:32 <@slytherin> riddle28: the bug is not related to Ubuntu. rather It is related to inkscape on Mac OS X 20:32 <@tuxmaniac> slytherin: interesting. I did not know it :-) 20:33 <@slytherin> riddle28: Do you have Mac OS X? 20:33 < riddle28> do i have to install inkspace 0.45 for that 20:33 < riddle28> ya 20:33 < riddle28> btw is inkspace 0.45 there for ubuntu?? 20:34 <@slytherin> riddle28: Hardy has 0.46 20:35 < riddle28> nope 20:35 <@slytherin> We can see if bug is reproducible on Ubuntu version of inkscape. 20:36 -!- sumitc [n=chatzill@unaffiliated/sumitc] has joined #ubuntu-in-classroom 20:36 < sumitc> I reproduced the bug 20:36 < riddle28> ok 20:36 < sumitc> accurate description by reporter 20:36 <@tuxmaniac> sumitc: cool! now change the status of the bug as confirmed and update the description with what you did 20:37 < sumitc> tuxmaniac, alright 20:37 -!- punchagan [n=user@59.93.85.120] has joined #ubuntu-in-classroom 20:37 < riddle28> btw inkspace is not installed on my comp 20:37 < riddle28> nice sumitc 20:37 < riddle28> :) 20:37 < punchagan> sumitc: you reproduced it? 20:37 < sumitc> riddle28, thanks 20:38 < sumitc> punchagan, yes 20:38 <@slytherin> sumitc: You are talking about OOo bug right? 20:38 < sumitc> yes 20:38 < sumitc> slytherin, ^^ 20:38 < punchagan> yes. i tried using 'p'for login. I didn't reproduce it. 20:38 -!- lut4rp [i=7aa25f40@gateway/web/ajax/mibbit.com/x-ed430e1803da839c] has quit ["http://www.mibbit.com ajax IRC Client"] 20:38 < riddle28> ya he did it 20:38 < riddle28> not me 20:38 < sumitc> I tried with l itself 20:38 <@slytherin> Ok. Anyone want to check if inkscape bug is reproducible on Ubuntu? 20:39 <@tuxmaniac> punchagan: now thats interesting. Whetehr it fails only with login "l" 20:39 < punchagan> hmm.. 20:40 <@slytherin> We have to note that inkscape in Ubuntu might be different than official version. 20:40 <@tuxmaniac> sumitc: updating the bug report? 20:42 <@slytherin> any takers for inkscape bug? 20:44 <@slytherin> why is this channel suddenly so silent? 20:44 < riddle28> k next one? 20:44 <@tuxmaniac> slytherin: I think no takers for the previous bug. So we leave it as it is 20:45 <@slytherin> Next - https://edge.launchpad.net/ubuntu/+source/gnome-main-menu/+bug/247811 20:45 -!- techno_freak [n=parthan@unaffiliated/teknofreak] has quit ["Leaving"] 20:45 < riddle28> next bug no pls 20:47 <@slytherin> riddle28: ^^ 20:47 <@tuxmaniac> sumitc: ?? 20:48 <@tuxmaniac> Are people tired? Do we call it a day and start afresh tomorrow? 20:48 <@slytherin> tuxmaniac: yes. 20:48 < punchagan> ok. 20:48 < riddle28> hmm the person seemd to solve it 20:48 <@tuxmaniac> ok we close the sessions here. The logs will be made available and links sent to the mailing list 20:49 < riddle28> but we cant reproduce it without 20:49 <@tuxmaniac> Thanks for attending and make sure you are here tomorrow at 2100 hrs. More interesting stuff coming up tomorrow. 20:49 < punchagan> yeah! 20:50 <@tuxmaniac> and dont forget to spread the word 20:50 < riddle28> knowing wat caused it exactly 20:50 < riddle28> ? 20:50 <@slytherin> tuxmaniac: can you please send a reminder about time? I will also try to send mail about the tools to be used. 20:50 -!- sumitc_ [n=chatzill@unaffiliated/sumitc] has joined #ubuntu-in-classroom 20:50 < riddle28> ya thnks for the lecture 20:50 < riddle28> but do reply 20:50 < riddle28> for the last one 20:50 < riddle28> can we reproduce the bug 20:50 < riddle28> ? 20:50 < punchagan> ok tuxmaniac. but wouldn't it be a trouble if they join in tomorrow? 20:50 < riddle28> https://edge.launchpad.net/ubuntu/+source/gnome-main-menu/+bug/247811 20:50 < riddle28> ? 20:50 < sumitc_> sorry guys, was disconnected 20:50 <@tuxmaniac> ok done. tomorrow morning thats the first thing that will be done. Mail and logs will be published along with a Day 1 review :-) 20:51 < punchagan> may be they could look at the logs? 20:51 < punchagan> ok. 20:51 -!- lut4rp [i=7aa25f40@gateway/web/ajax/mibbit.com/x-cfad8828db831d2c] has joined #ubuntu-in-classroom 20:51 < sumitc_> is the session over? 20:51 <@tuxmaniac> its OK. people are tired and we have closed 20:51 -!- sumitc [n=chatzill@unaffiliated/sumitc] has quit [Nick collision from services.] 20:51 < lut4rp> hear hear, i have a question 20:52 < lut4rp> but its unrelated to today 20:52 < lut4rp> :) 20:52 -!- sumitc_ is now known as sumitc 20:52 <@slytherin> sumitc_: yes, it is a bit late. You Can hang about in daytime tomorrow and do triaging 20:52 <@tuxmaniac> logs will be published tomorrow very early in the morning. 20:52 < sumitc> alright, will do that 20:52 <@slytherin> lut4rp: in #ubuntu-in please. 20:52 < riddle28> kk 20:52 < riddle28> bye 20:52 < sumitc> tomorrow, or today? :P 20:52 < lut4rp> slytherin, yea, i thought so 20:53 -!- lut4rp [i=7aa25f40@gateway/web/ajax/mibbit.com/x-cfad8828db831d2c] has left #ubuntu-in-classroom [] 20:53 -!- riddle28 [i=ca992984@gateway/web/ajax/mibbit.com/x-c75c8675e4173e2f] has quit ["http://www.mibbit.com ajax IRC Client"] 20:53 -!- slytherin [n=Salazar@pdpc/supporter/base/slytherin] has left #ubuntu-in-classroom [] 20:53 -!- punchagan [n=user@59.93.85.120] has left #ubuntu-in-classroom ["Awesome!"]
This page was last modified on 30 July 2008, at 07:22. This page has been accessed 525 times.
