[02:02] <nexeh> Hey everyone. I'm a developer and ahve been reading through all the documentation (phew... theres some reading there!) I've been looking through some tickets to get familiar... I had a simple triaging question if someone is around?
[02:05] <nexeh> Anyone around?
[02:05] <yofel> nexeh: just ask you question, if anyone knows the answer they'll reply
[02:07] <nexeh> Ok, There is a note in the documentation that is a bug is not writen in English that we should ask them to translate it. My question is should anything else be updated on the ticket as the same time, ie status?
[02:07] <yofel> nexeh: also since there are times when nobody will be around, if you don't have time to wait you can send your question to the mailing list too
[02:07] <nexeh> yofel: thanks i will do that
[02:08] <nexeh> yofel: any suggestions on picking up a mentor?
[02:11] <yofel> as for the mentors you can request one as described here https://wiki.ubuntu.com/BugSquad/Mentors
[02:25] <micahg> nexeh: you could also try google translate, if the request seems reasonably translated, you can run with it
[02:25] <nexeh> Ok this seems like a stupid question but the directions say "Set up your Ubuntu Wiki-page, and add the following information to it: " however i dont see anywhere that allows me to do then
[02:26] <nexeh> micahg: thank i was thinking that too but i didn't want anyone to complain about a bad translation? but seeing as you suggested it i will
[02:26] <micahg> nexeh: once you log into the wiki, you can add or edit any page
[02:27] <micahg> nexeh: you can also add a task for ubuntu-translations and they can translate
[02:28] <micahg> nexeh: do you have a link to the page that requests asking the user to translate, I thought we decided not to do that
[02:28] <nexeh> micahg: ive used wikis before and i can find the edit buttern but no where to add... ill keep looking tho... I'll get that link now
[02:29] <micahg> nexeh: just go to the page you want to add and there should be a button to edit
[02:42] <nexeh> OMG, that was not easy to find...
[02:42] <nexeh> https://wiki.ubuntu.com/Bugs/HowToTriage
[02:45] <micahg> nexeh: thanks, I'll discuss it w/the team
[02:45] <nexeh> Let me know what is decided
[04:25] <Omega> Where should a bug in the Ubuntu Installer go?
[04:26] <micahg> Omega: ubiquity?
[04:27] <Omega> Thank you.
[05:03] <stlsaint> vish: well since im no longer part of team i will just continue to triage bugs on my own then apply for membership afterwards
[05:08] <vish> stlsaint: hey, i sent you a mail and havent heard back... without knowing what the progress is, i couldnt suggest anything else..
[05:09] <vish> stlsaint: i have no clue if being part of that team was helping you or not
[05:10] <stlsaint> vish: meh, not really
[05:10] <stlsaint> i rarely saw my mentor in here which is where majority of my time is spent
[05:11] <vish> stlsaint: exactly! and you should have replied
[05:11] <stlsaint> vish: i will just continue on my bug traiging and let you know when i feel i am ready to apply for membership
[05:11] <stlsaint> vish: i did reply i said my mentor was drew212
[05:11] <stlsaint> vish: i replied either in here or on email...lemme check one sec
[05:12] <stlsaint> nope, guess it was in here
[05:12] <stlsaint> oh yea you asked about how much i had done
[05:13] <vish> stlsaint: no, i mailed again with a set of questions, and there was no reply back.. there is a different team where it is not one on one, but more of a team with a student..  if this did not work for you, you could have been moved to that team..
[05:13] <vish> oh well..
[05:13] <vish> stlsaint: triaging on your own is also fine..  which ever makes you comfortable.. :)
[05:13] <stlsaint> well i have done 3 solid bug triages so i am aiming to do more, most bugs i attempt either fail in one way or another
[05:14] <vish> there is no win with bugs!
[05:14] <stlsaint> lack of info, failure on poster to post more info, im unable to reproduce or any other various reason
[05:14] <vish> ;p
[05:14] <vish> stlsaint: those are not your failures :)
[05:15] <stlsaint> vish: aye, but it makes it much harder for me to triage bugs, especially with the rest of the entire community doing them also ;D
[05:15] <stlsaint> lol, i more or less get the ones that fall in between the cracks
[05:15] <vish> stlsaint: nah, there are so many bugs where we dont hear back from..
[05:15] <micahg> stlsaint: there are more than enough bugs to go around
[05:16] <stlsaint> micahg: yea plenty bugs true, but plenty of them properly ready to be traiged...not so much
[05:16] <stlsaint> micahg: especailly when it comes to the part of reproducing the bug
[05:16] <micahg> stlsaint: that's part of learning how to triage bugs :)
[05:16] <vish> stlsaint: everyone starts the same.. ;)
[05:17] <stlsaint> i have already installed random apps that i never use just to try and reproduce a bug, but i dont want a slew of apps installed that i dont even use
[05:17] <stlsaint> then i go through uninstalling and what not
[05:17] <stlsaint> and i use vbox as well
[05:17] <micahg> stlsaint: you could try a chroot as well
[05:18] <stlsaint> micahg: :|
[05:18] <vish> stlsaint: nah, triage the apps you have.. not necessary to install fresh apps and triage
[05:18] <stlsaint> crap
[05:18] <micahg> stlsaint: or focus on apps you have installed :)
[05:18] <stlsaint> micahg: dang i never thought of that, but most of them need DE's
[05:18] <micahg> stlsaint: a chroot can piggy back on your current DE
[05:19] <stlsaint> micahg: im sure some binding is possible but ive never really had the need to with any chroot i use so i am unaware of how to :(
[05:21] <micahg> stlsaint: xhost +localhost should work as long as no one else is on teh machine
[05:21] <stlsaint> nope just me
[05:23] <stlsaint> then i found out i was triaging bugs that really didnt count towards membership because they werent ubuntu specific :( bummer
[05:24] <stlsaint> vish: thanks
[05:24] <stlsaint> micahg: thanks
[05:25] <stlsaint> i guess i will just report progress on wiki and then apply in a few weeks/months
[05:25] <stlsaint> night folks
[05:25] <micahg> stlsaint: hmm, xhost +localhost doesn't work :-/
[05:25] <vish> yw
[05:25] <stlsaint> micahg: lol, alright
[05:25] <micahg> stlsaint: but someone in #ubuntu might know how to do it
[05:25] <stlsaint> micahg: but your saying that IT IS possible, just have to figure out how?
[05:26] <stlsaint> micahg: cool, i know some folks who will know how ;)
[05:26] <micahg> stlsaint: yes
[05:26] <stlsaint> thanks
[06:24] <micahg> c2tarun: so, I'm not convinced there's an actual issue
[06:24] <c2tarun> micahg: ya i also figured that out. the bug is only to change the name of the package i think???
[06:24] <micahg> c2tarun: but since the papercutters took it on, maybe vish can shed some light on it
[06:24] <micahg> c2tarun: no, it's to modify the description
[06:26] <c2tarun> micahg: vish is not here. who is actually going to fix the bug??
[06:26] <micahg> c2tarun: vish is here somewhere
[06:27] <c2tarun> micahg: ok i'll wait for him. can you please tell me by bug triaging we mean only to change its importance by comments???
[06:28] <micahg> c2tarun: triaging is making sure there's enough information for a developer to work on the bug which can include, steps to reproduce and getting the importance set
[06:29] <c2tarun> micahg: ok and for being a developer do we have some requirements of just anyone can fix the bug (as in this case change the description)??
[06:29] <vish> hey.. which bug?
[06:29] <c2tarun> bug: #602671
[06:30] <vish> bug #602671
[06:30] <ubot2> Launchpad bug 602671 in p7zip (Ubuntu) (and 1 other project) "Description: p7zip (affects: 5) (heat: 24)" [Low,Confirmed] https://launchpad.net/bugs/602671
[06:30] <micahg> c2tarun: nope, no requirements on who, that's just a different hat to wear :)
[06:32] <c2tarun> micahg: ok ( i m a newbie and may b not the proper person to do this) if I want to change the description then what i have to do. download the tarball change the description and then what???
[06:32] <vish> hmm, ok.. not sure what the confusion is, but c2tarun, ssj6akshat is already working on that bug
[06:32] <micahg> vish: it's not assigned :)
[06:32] <vish> micahg: yea, ^ ssj6akshat pls assign yourself to the bug
[06:32] <c2tarun> i m not going for ssj*'s work. i just wanted to know something about bugging and packaging and all this
[06:33] <vish> ssj6akshat: just assign the bug to yourself and mark it as 'In-Progress'
[06:33] <c2tarun> its my first time i m even looking at a bug and i have absolutely no idea what to do now. so i was just asking...
[06:34] <micahg> c2tarun: so, basically, if you want to fix a bug, you can create a debdiff and then follow the sponsorship process
[06:34] <vish> c2tarun: have you read a little bit of the wiki pages? or are you just starting?
[06:34] <ssj6akshat> vish, wait, i thought it was assigned to Papercuts Ninja so I didn't assign myself
[06:34] <c2tarun> i read the recepies on the wiki page for packaging and creating debdiff. the thing is they just tell the steps never explain them and their technicality and internal functioning
[06:35] <micahg> ssj6akshat: yes, but there's the Ubuntu task as well
[06:35] <vish> ssj6akshat: nah, we are assigning all bugs to the ninja team now, the team gets notified and when someone in the team finds the bug interesting they 'claim' the bug, hence they assign it tot themselves
[06:35] <vish> s/tot/to
[06:37] <c2tarun> ssj6akshat: are you working on that bug???
[06:37] <ssj6akshat> c2tarun, yes
[06:37] <c2tarun> ssj6akshat: may b its too much to ask, but can you please tell me little bit what you are doing in order to fix that???
[06:39] <ssj6akshat> c2tarun, PM
[06:40] <c2tarun> ssj6akshat: PM??
[06:41] <ssj6akshat> c2tarun, private message
[06:44] <vish> ssj6akshat: i thought you already have the patch..
[06:44] <vish>  or i am a bad teacher ;p
[08:53] <c2tarun> anyone looked on  # Bug #685415
[08:53] <ubot2> Launchpad bug 685415 in firefox (Ubuntu) "error writing about:mozilla (XML non-well formed) (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/685415
[08:53] <micahg> c2tarun: I saw it...
[08:54] <c2tarun> micahg: i ran about:mozilla on my system and found just a message with red background.
[08:54] <c2tarun> is it really a bug??
[08:55] <micahg> if there's an error, yes
[08:55]  * micahg tries in 3.6
[08:55] <c2tarun> no that was not an error i think. that was  a quote from book of mozilla, 11:9
[08:56] <micahg> as it should, let me try in another langauge
[08:56] <c2tarun> ok.
[08:57] <micahg> ah, indeed it's valid :)
[08:57] <c2tarun> are you getting an error??
[08:57] <micahg> c2tarun: in german
[08:57]  * micahg will mark triaged, thank
[08:57] <micahg> thanks
[08:58] <c2tarun> ok let me try in my language....
[09:01] <c2tarun> there was no error in hindi
[09:01] <c2tarun> :(
[09:02]  * micahg doesn't know if there's a hindi langpack
[09:02] <c2tarun> there is hindi langpack for indians .. dont know how to explaint
[09:02] <c2tarun> there is hindi langpack for indians .. dont know how to explain
[09:03] <c2tarun> but i installed it from language support into my system
[09:03] <micahg> c2tarun: right, but does firefox end up in hindi
[09:04] <c2tarun> ya firefox printed the quote in hindi. and it was correct translation for its english counterpart. but for that testing i logged out and logged in with hindi gnome. how did you  testd??
[09:04] <micahg> I set LC_ALL on teh cli
[09:05]  * micahg tries in Hebrew
[09:06] <micahg> fails in hebrew as well
[09:38] <ssj6akshat> help on bug #602462
[09:38] <ubot2> Launchpad bug 602462 in grsync (Debian) (and 2 other projects) "Too geeky description of grsync in software center (affects: 1) (heat: 8)" [Unknown,New] https://launchpad.net/bugs/602462
[09:38] <ssj6akshat> What should I change the description to?
[09:39] <nisshh> ssj6akshat, that doesnt seem overly geeky to me
[09:40] <nisshh> maybe get rid of the GTK2 reference
[09:41] <nisshh> i agree with vish's comment on it tbh, ssj6akshat
[09:42] <c2tarun> getting rid of GTK2 may not be the solution because anyone using rsync must be familiar with gtk
[09:42] <c2tarun> nisshh
[09:43] <micahg> I don't think either buzzword needs to go, but rather a simple explanation of what it does as well
[09:43] <nisshh> c2tarun, but a new user might not even know what GTK means
[09:44] <nisshh> micahg, i agree, the actual explanation of its purpose is not there
[09:44] <vish> c2tarun: why does anyone using rsync need to be familiar with GTK?
[09:44] <c2tarun> nisshh: its not that difficult, just by googling and reading few lines one can get GTK. its not something geeky.
[09:45] <ssj6akshat> c2tarun, see MPT's comment
[09:45] <nisshh> c2tarun, echoing vish why does someone need to be familiar with GTK to use grsync?
[09:45] <vish> c2tarun: an user must not have to google an explanation, for an explanation to the package he is trying to understand. :)
[09:46] <c2tarun> :)
[09:46] <nisshh> exactly
[09:46] <c2tarun> may b vish :0
[09:46] <c2tarun> :)
[09:47] <c2tarun> but these are very general terms gtk, gnu. etc. one cant explain everything in the package.
[09:47] <vish> c2tarun: yes, not needed to even exist.. ;)
[09:48] <nisshh> c2tarun, its best not to assume a new user might know those terms, in most cases they probably dont
[09:48] <micahg> yeah, I think the buzzwords are fine as long as there's some explanation of funciton
[09:48] <vish> https://wiki.ubuntu.com/SoftwareCenter/PackageDescriptions
[09:49] <vish> hmm, where is the user-testing data..
[09:49]  * vish reverts wiki
[09:54] <c2tarun> ssj6akshat: are you working on this rsync bug??
[09:55] <ssj6akshat> c2tarun, i want to work on them all
[09:55] <ssj6akshat> :P
[09:56] <c2tarun> what changes are you planning to make in descriptions??
[10:00] <c2tarun> ssj6akshat: PM
[10:51] <ssj6akshat> vish, so i just remove the GTK2 reference?
[11:11] <njin> Hello, who is responsible to unmount storage media during shutdown ? Thanks
[11:13] <njin> *USB storage media, sorry
[11:15] <njin> bdmurray. can i disturb ?
[11:15] <c2tarun> can anyone please tell me where can i find the source code manual for empathy??
[11:16] <ssj6akshat> nisshh, what do you think about it?
[11:20] <nisshh> ssj6akshat, i agree with vish's comments on the bug
[11:21] <ssj6akshat> c2tarun, man empathy ?
[11:21] <ssj6akshat> c2tarun, do you mean source code?
[11:22] <c2tarun> yup
[11:23] <ssj6akshat> c2tarun, bzr branch lp:empathy
[11:24] <njin> charlie-tca: can i disturb?
[11:25] <yofel> njin: I *think* the kernel, since all drives are unmounted directly before poweroff, but I'm not sure
[11:28] <njin> yofel: i'm thinking too, thanks
[11:39] <c2tarun> ssj6akshat bzr branch just created the branch and gave me the source code. but there is no manual on the source code. are you aware of source code manual???
[11:42] <ssj6akshat> c2tarun, http://telepathy.freedesktop.org/doc/book/ <-- maybe this?
[11:43] <c2tarun> ssj6akshat: this may help. thanks :)
[11:48] <ssj6akshat> vish, what does potpourri mean?
[13:56] <BUGabundo> boas
[14:19] <c2tarun> can anyone please tell me how to look at the bug list in launchpad. all i see there is recently reported bugs
[14:20] <vish> c2tarun: https://bugs.launchpad.net/ubuntu/+source/PACKAGENAME
[14:21] <vish> c2tarun: usually when you are viewing a bug, you can just click on the "BUGS" header on the top
[14:22] <c2tarun> vish: clicking on bugs on top is directing me to the same page of recently reported bugs
[14:24] <vish> c2tarun: no it does not, for example if you are viewing a TB bug, clicking on the "BUGS" header gives you » https://bugs.launchpad.net/ubuntu/+source/thunderbird
[14:24] <vish> c2tarun: do you see on *top* : Overview , Code , Bugs , .... ,
[14:24] <c2tarun> vish: got it thanks :)
[14:24] <vish> :)
[14:34] <c2tarun> what is difference between a triaged bug and confirmed bug??
[14:39] <charlie-tca> c2tarun, confirmed means someone else could have it too. Triaged means the bug is ready for a developer to work on it
[14:39] <charlie-tca> Confirmed does not mean there is enough information there to actually fix the bug
[15:14] <c2tarun> i m not getting the triaged option after clicking on the pencil adjacent to status..???
[15:17] <charlie-tca> Changing status to triaged requires being in bug-control. Normally, when just learning, you set it to confirmed and then ask here to have to changed to triaged.
[15:17] <charlie-tca> That allows for a good verification that there is enough information
[15:18] <c2tarun> what if someone reported an error but i didnot find it valid on my system.
[15:18] <charlie-tca> Did you try in the same version as the report?
[15:19] <c2tarun> nope, it was reported for maverick, mine is lucid
[15:19] <charlie-tca> You can not verify an issue using an earlier release.
[15:19] <c2tarun> ok
[15:19] <charlie-tca> Maverick is later than lucid, so to verify the issue, you have to use maverick or natty
[15:20] <c2tarun> ok
[15:36] <c2tarun> i was going through a tutorial on this link: https://wiki.ubuntu.com/MeetingLogs/devweek0809/FixingBugs2 and stuck into an error. can anyone please help
[17:02] <njin> hello, have you already see something similar ? Nov 21 20:28:34 andrex-notebook gdm-simple-slave[1181]: WARNING: Unable to load file '/etc/gdm/custom.conf': ÐÐµÑ‚ Ñ‚Ð°ÐºÐ¾Ð³Ð¾ Ñ„Ð°Ð¹Ð»Ð° Ð¸Ð»Ð¸ ÐºÐ°Ñ‚Ð°Ð»Ð¾Ð³Ð°
[17:03] <njin> is this line hacked ?
[17:08] <penguin42>  'hacked'
[17:09] <penguin42> it's a bit odd, probably just a bug somewhere
[17:22] <njin> penguin42: thanks
[17:23] <htorque> bug 647979 - this bug is back again: reopen, open a new one?
[17:24] <ubot2> Launchpad bug 647979 in unity (Ubuntu) (and 3 other projects) "Nautilus' "File Operation" dialog gets stuck and prevents opening new Nautilus windows (affects: 3) (heat: 57)" [Medium,Fix released] https://launchpad.net/bugs/647979
[17:31] <vish> htorque: yes
[17:47] <micahg> njin: please don't upstream gnome-shell bugs unless it's an upstream issue
[17:48] <micahg> njin: please close gnome 636446 as we shouldn't be using mutter 2.91.x with gnome-shell 2.31.x
[17:48] <ubot2> Gnome bug 636446 in general "(mutter:7484): mutter-WARNING **: Could not load library [/usr/lib/mutter/plugins/libgnome-shell.so (/usr/lib/mutter/plugins/libgnome-shell.so: undefined symbol: mutter_plugin_get_type)]" [Blocker,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=636446
[17:50] <njin> micahg: done
[17:51] <micahg> njin: also WRT AC_INIT, were you building against the gnome3 libs?
[17:53] <njin> micahg: i've fixed it installing dconf, i'm building vala just now .
[17:53] <penguin42> gnome-shell won't install for me on natty, broken gjs package/dependency
[17:54] <micahg> penguin42: yes, I'm upgrading gnome-shell
[17:54] <penguin42> good, I'd like to try it again - I tried it a long time ago when it was new and didn't like it
[17:54] <penguin42> it seems right to try these things every so often
[17:55] <micahg> penguin42: just not sure if I'll finish today, but should be some time this week
[17:55] <penguin42> cool
[17:55] <njin> micahg:thanks
[17:56] <micahg> njin: np
[17:58] <njin> micahg: sorry, i've dont fix it with dconf, it exit just now with ****[dconf-1.o0.gir] Error1
[17:58] <micahg> njin: ok, I'll see what happens when I upgrade the build-dependencies
[17:58] <njin> *dconf-1.0.gir
[18:47] <htorque> vish, yes what? reopen or better open a new one? :-)
[18:48] <vish> htorque: oops, yea, open a new bug :)
[18:48] <htorque> vish, ok, thanks!
[18:48] <vish> np..
[19:26] <njin> micahg: it works without gnome power manager too !.
[20:45] <daker> hello
[23:13] <layn> Hi