[02:06] <Ahmuck_> bug reporting has got a major bug
[02:06] <Ahmuck_> any chance the bugsquad could fix the spamming bug?
[02:47] <Ahmuck_> i've gotten at least 30+ messages today about the same bug, repeat, repeat, repeat, this bug is a duplicate of ...
[02:47] <Ahmuck_> 30+ yesterday
[02:47] <Ahmuck_> 30+ the day before
[03:07] <JanC> Ahmuck_: you can always unsubscribe, but I guess that's not what you want  ;)
[03:27] <Ahmuck_> JanC: unsubscribe from that bug?
[03:28] <Ahmuck_> the bug reporting is subscribing automatically when reporting a bug?
[03:29] <Ahmuck_> a better solution would to not e-mail when it's marked as a duplicate
[03:29] <JanC> you can unsubscribe, but in most cases that's not what we want, because users might be asked for more info, to try a test-package, etc.
[03:30] <JanC> so maybe, file a bug against launchpad
[03:30] <JanC> and developers who are subscribed probably want to get the duplicate mails
[03:30] <Ahmuck_> well, the spamming has caused me to now close any bugs that happen rather than report
[03:31] <JanC> eh, thats' not exactly the right way to deal with it
[03:31] <Ahmuck_> so your getting no bug reports from me at all now, and people are asking all over how to unsubscribe
[03:31] <Ahmuck_> which really defeats the purpose
[03:31] <JanC> like I said, this could be considered as a launchpad bug
[03:32] <JanC> maybe an option whether you want those or not
[03:32] <JanC> which defaults to no
[03:32] <JanC> so develoeprs can enable it
[03:32] <JanC> https://bugs.launchpad.net/launchpad
[03:33] <JanC> and maybe ask in #launchpad
[03:34] <JanC> but certainly file a bug about it
[03:35] <Ahmuck_> eh, i'll just blacklist the bug as spam in my e-mail and let someone else file a bug
[03:39] <JanC> Ahmuck_: *sigh* and thanks for being unhelpful
[03:40] <JanC> could you please at least say what's the "master bug" causing this?
[03:40] <Ahmuck_> Thank you for taking the time to report this crash and helping to make
[03:40] <Ahmuck_> Ubuntu better.  This particular crash has already been reported and is a
[03:40] <Ahmuck_> duplicate of bug #429322, so is being marked as such.
[03:41] <ubot4> Launchpad bug 429322 in seahorse-plugins "seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)" [High,Confirmed] https://launchpad.net/bugs/429322
[03:41] <Ahmuck_> Jan, i just tried to search for that bug on bugs.launchpad, and launchpad spit out an error
[03:48] <nigel_nb> Hi, I have a problem with my system's audio and noticed a bug logged with the same problem.  I have subscribed to the bug, and reported that I too have the bug.  Is there anything more I should do?
[03:49] <JanC> nigel_nb: if you have the *exact* same hardware (down to the subsystem vendor & device ID) then you can maybe set it as confirmed, otherwise you better file a new bug
[03:51] <nigel_nb> JanC: when I do an lspci, I get my audio driver as Intel 82801I
[03:51] <nigel_nb> JanC: same as the bug
[03:51] <JanC> you need to compare lspci -vv
[03:52] <JanC> which basically speaking indicates how the manufacturer integrated that component on the motherboard  ;)
[03:52] <nigel_nb> JanC: oh, thats not given with the bug
[03:52] <JanC> it should be, if it was reported correctly (in the attachments)
[03:52] <nigel_nb> JanC: so I need to log a separate bug?
[03:53] <JanC> what bug is it?
[03:53] <nigel_nb> JanC: oh yeah :P sorry.. will check
[03:53] <JanC> https://wiki.ubuntu.com/DebuggingSoundProblems might be useful
[03:54] <nigel_nb> tried all that, no avail.
[03:54] <nigel_nb> there is a difference in the subsystem and vendor ID
[03:54] <nigel_nb> I guess I'll have log a new bug then
[03:54] <JanC> but did you compare those 4 lines with what's in the bug report?
[03:54] <JanC> ah, okay, file a new bug then
[03:55] <nigel_nb> I put the status as "New" ?
[03:56] <JanC> for a new bug, it will be new by default?
[03:56] <nigel_nb> JanC: been using Ubuntu for long, never filed a bug, its my buddy's laptop
[03:57] <nigel_nb> thanks a lot for your help :)
[03:57] <JanC> fiel a bug with: ubuntu-bug alsa-base
[03:57] <JanC> run that fro ma terminal, and it will include all the info needed
[03:58] <nigel_nb> JanC: oh, thanks a lot
[03:58] <JanC> (you need a Launchpad account, but you can create one "on the fly")
[03:58] <nigel_nb> ok
[03:59] <JanC> nigel_nb: (almost) always best to use "ubuntu-bug <source-package-name>" to file bugs
[04:00] <nigel_nb> that way includes all the info that you need?
[04:00] <JanC> normally it includes all the info Daniel needs
[04:01] <JanC> if not he'll ask, but it includes a lot, you'll see
[04:01] <JanC> maybe you can mention it looks the same as the other bug
[04:01] <nigel_nb> daniel does the triaging?
[04:01] <JanC> in the bug description
[04:02] <nigel_nb> ok :)
[04:02] <JanC> and upstreaming and fixing  ;)
[04:02] <nigel_nb> wow
[04:02] <nigel_nb> u mean daniel holbach?
[04:02] <JanC> well, as far as he has free time
[04:03] <JanC> no daniel chen
[04:03] <nigel_nb> ah
[04:03] <nigel_nb> the same person who answered the previous bug
[04:04] <JanC> yep, he's the sound hero/volunteer of Ubuntu   ;)
[04:04] <nigel_nb> hehe
[04:30] <nigel_nb> JanC: logged the bug, thanks for guiding me through it
[06:28] <astechgeek> anyone alive in here/
[06:29] <astechgeek> Reading the ubuntuwiki/bugsquad/gettinginvolved page, and had some general questions
[06:32] <jmarsden> astechgeek: Just ask your real question(s), and see who answers :)
[06:33] <astechgeek> what do I need to put in the email to request a mentor?
[06:37] <astechgeek> :-/ I can not hear anyone over the deafening chirp of crickets
[06:52] <astechgeek> mentor email sent now what?
[06:53] <astechgeek> i
[06:54] <jmarsden> astechgeek: Now wait... and be aware there is a long waiting time for mentors, if I remember rightly.  Meanwhile just get involved in whatever area you want to get started in, you don ot have to wait for a mentor.
[06:55] <astechgeek> How... I haven't got a clue where to start
[06:55] <jmarsden> What is that you want to do -- bugsquad type things or packaging stuff?
[06:57] <astechgeek> since Im new it would logical to start small right?
[06:57] <dtchen> how is it reading https://wiki.ubuntu.com/MOTU/GettingStarted ?
[06:58] <jmarsden> Well, you could start by going through examples in the packaging stuff, per the six steps in that GettingStarted page ...
[08:14] <brad_> has anyone else had a bug with setting emblems?
=== YDdraigGoch is now known as WelshDragon
=== erhesrhsrtb54vyh is now known as Elbrus
=== maco_ is now known as maco
=== maco_ is now known as maco
=== nightwis- is now known as nightwish
[14:43] <Narc> Hi everyone. Is someone able to explain to me how I can start helping triaging bugs without being a member of the BugSquad yet, to train myself a little... Thanks.
[14:44] <maco> Narc: chck out wiki.ubuntu.com/BugSquad to learn now
[14:44] <maco> *how
[14:45] <maco> you dont need to be in BugSquad to set status on bugs
[14:45] <maco> and BugSquad cant do Importance, so...
[14:46] <Narc> Oh, okay, that's what I wanted to know. That's the wiki I'm reading. Thanks
[14:47] <geser> what's the correct status for an open bug which got filed for a release which is EOL now (edgy)? Invalid or Won't fix?
[14:49] <maco> geser: check to see if it still exists in currently supported versions
[14:50] <geser> maco: see bug #78407
[14:50] <ubot4> Launchpad bug 78407 in gnupg2 "Missing translation strings in edgy" [Undecided,Confirmed] https://launchpad.net/bugs/78407
[14:51] <maco> oh... hmm well its fix released in current development version (lucid) right...?
[14:52] <maco> blah i dont like these situations
[14:55] <geser> maco: I assume so, the translation page for gnupg2 in karmic list over 1600 untranslated strings for some languages
[14:57] <maco> wow
[15:48] <_Narc_> Can someone explain to me what am I supposed to do of a bug (badly) filled in a language other than english ? Sorry about the stupid question, I'm trying to learn how to triage. Thanks.
[15:54] <maco> _Narc_: find someone to translate it
[15:55] <_Narc_> maco: well, I did, it's really not long, in spanish, but what am I supposed to do, answer in English ?
[15:56] <maco> i tend to ask questions in their language if i know it and then in english "I just asked for..."
[15:59] <_Narc_> Good idea. I can't speak spanish though. How can I found a bug triager who speaks spanish and suggest the bug to him ?
[16:00] <maco> andreasmoog speaks spanish and is a bugcontrol person, but he's not online right now...
[16:01] <_Narc_> Okay, I'll sort it out, thanks for your help. I'm afraid of doing something wrong, would be counter-productive.
[16:01] <maco> can always try google translate, but....
[16:02] <_Narc_> Well, they're not that good :)
[16:21] <hacktick> https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport is outdated - how do I start apport with karmic?
=== kees__ is now known as kees
[16:31] <kklimonda> hacktick: by editing /etc/default/apport
[16:37] <hacktick> thanks kklimonda
[17:05] <_Narc_> My last stupid question for today : Does the LaunchPad comment box supports html ? For links, etc...
[17:10] <greg-g> _Narc_: I don't believe so, no. But if you paste a link, it makes it "clickable" so people don't have to copy/paste
[17:10] <_Narc_> Oh, okay
[17:10] <_Narc_> Good
[17:10] <_Narc_> Thanks
[17:10] <greg-g> _Narc_: you can also use short hand for bug numbers, for instance "Bug #1234" is made clickable to launchpad bug #1234
[17:10] <ubot4> Launchpad bug 1234 in launchpad-foundations "Gina is an unmaintainable mess of command line options, environment variables and shell scripts" [Medium,Fix released] https://launchpad.net/bugs/1234
[17:10] <ubot4> Launchpad bug 1234 in launchpad-foundations "Gina is an unmaintainable mess of command line options, environment variables and shell scripts" [Medium,Fix released] https://launchpad.net/bugs/1234
[17:10] <greg-g> no prob
[17:11] <_Narc_> greg-g: That's what I wanted. Pretty good then.
=== yofel_ is now known as yofel
[18:42] <v0xel> Hi all!
[18:42] <v0xel> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/463654
[18:42] <ubot4> Launchpad bug 463654 in software-center "software center wont start with my locale variables set to sr_RS" [Undecided,New]
[18:42] <v0xel> this is affecting lots of serbian users
[18:42] <v0xel> but this is not filled in right place
[18:43] <v0xel> how can i file it against python 2.6?
[18:47] <maco> click the dropdown where it says software-center
[18:47] <maco> theres a little arrow next to the text...
[18:47] <maco> click that and itll show edit mode
[18:47] <maco> theres a textbox that says software-center. change it to say python2.6
[18:54] <v0xel> maco, tnx done it
[18:54] <v0xel> i will update it with some more info
[19:12] <v0xel> anyone here using localized Ubuntu?
=== maco_ is now known as maco
[19:24] <jmarsden> v0xel: I've added language packs and played with logging into sessions in French, German, Spanish etc. for test purposes... I've not tried Serbian :)
[19:25] <v0xel> jmarsden, could you go to /usr/lib/python2.6/ and run python locale.py when you're logged in with anything non-english?
[19:25] <v0xel> and paste the output or see if there's an error, please?
[19:26] <v0xel> i'm trying to debug bug #463654
[19:26] <ubot4> Launchpad bug 463654 in python2.6 "Python  programs wont start with locale variables set to sr_RS and sr_RS@latin" [Undecided,New] https://launchpad.net/bugs/463654
[19:26] <jmarsden> OK... I'm running in English now... back soon :)  BTW you could add a language pack and test this yourself, too...
[19:35] <jmarsden> v0xel: http://pastebin.com/f6ef2f60c
[19:35] <jmarsden> Looks fine to me.
[19:35] <v0xel> jmarsden, what's your $LANG now?
[19:35] <jmarsden> I'm back to English again now.
[19:36] <jmarsden> en_US.UTF-8
[19:36] <v0xel> jmarsden, tnx for trying, i'll try to install some l10n packages and debug further on
[19:36] <jmarsden> OK, no problem.
=== markus__ is now known as thekorn
=== YDdraigGoch is now known as WelshDragon
[20:08] <Narc> Hello everyone. Can someone tell me if it's okay to mark a bug as confirmed if I and the submitter are the only people to experience it or does it need more people commenting ? Thanks... Sorry about the naive questions.
[20:11] <maco> as long as someone other than submitter can reproduce it
[20:16] <Narc> Well, I do.
[20:17] <Narc> You're always the one answering to my questions today, thanks. Sorry if I sound noob.
[20:18] <maco> haha its no problem
[20:18] <hggdh> chance, and the fact that most of us are doing something else ;-)
[20:19] <Narc> Haha, of course
[20:19] <Narc> So, if I'm able to replicate a bug, I can mark it as confirmed right away, right ?
[20:20] <maco> yes
[20:20] <Narc> Ok, thanks
[20:20] <maco> though if you can clarify steps to reproduce, extra awesome
[20:21] <Narc> I got xp points for this ? :P
[20:22] <maco> actually..yes
[20:22] <Narc> Ok, this one is already crystal clear but I will.
[20:22] <maco> its called "Karma" on launchpad
[20:22] <Narc> Haha, I know, was doing a lousy joke
[20:24] <Narc> Karma, yes. Reminds me of Reddit. Not as easy to earn though.
[20:25] <dtchen> it's actually ridiculously easy to earn karma
[20:25] <Narc> Oh really
[20:25] <dtchen> just branch everything in bzr or do translations
[20:26] <maco> hahahaha
[20:26] <Narc> I was actually thinking about doing some translations.
[20:26] <dtchen> please do. translations are one of the best ways to contribute.
[20:26] <Narc> If it's too easy to earn it'll loose it's value :)
[20:29] <maco> i think dtchen  is referring to how people sponoring translation changes would get more karma than those actually translating...and i think it was fixed
[20:30] <maco> my translations karma's only 2...its been 2.5y since my last translation (im too out of practice to translate anymore)
[20:30] <hggdh> actually, translation is not as easy as it seems
[20:30] <maco> (karma decreases over time)
[20:32] <Narc> Well, I'm fluent in English but it's not my native language so I figured I'd translate some parts of Ubuntu. Sounded easy but I'm a bit confused with the process.
[20:33] <maco> i was a bit confused too. i think you can either say "this existing translation fits" or supply your own
[20:33] <maco> if you supply your own, the leader of your language's translation team then has to approve it, i think
[20:33] <hggdh> AFAIR, yes.
[20:33] <maco> so you dont write "monkey butt monky butt monkey butt"
[20:33] <Narc> Haha
[20:34] <Narc> People wouldn't do this
[20:34] <hggdh> you would be surprised
[20:34] <Narc> Well... I hope.
[20:37] <hggdh> also, consistency is important. For example, if there are two ways in a language to translate the word 'byte' (say, by the idiotism 'byte' and by the word 'octet'), you should keep using just one of them
[20:37] <hggdh> either one, but just one, all over the place
[20:38] <Narc> Yes, I read about that on my language's translation team. That and other stuff.
[20:38] <Narc> But they confused me more than they helped.
[20:38] <hggdh> heh
[21:00] <Narc> Ok, last question then I stop bothering you : What do we do of what I call "casual" reports that looks like " firefox/nautilus/whatever crashed while not doing anything special"...They're not really reproducible, you cannot ask for more info, but I figured maybe there could be useful to a programmer (usually a segfault), so..?
[21:00] <hggdh> Narc: can you give us a bug as an example?
[21:00] <Narc> of course
[21:01] <dtchen> you ask for more info
[21:01] <Narc> https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/477754 for example
[21:01] <ubot4> Launchpad bug 477754 in firefox-3.5 "firefox crashed with SIGSEGV in gtk_widget_style_get_valist()" [Undecided,New]
[21:02] <hggdh> this one should wait until apport processing is complete
[21:02] <hggdh> no, wait
[21:02] <Narc> Oh, ok
[21:02] <Narc> Ah
[21:03] <dtchen> huh, this is odd.
[21:03] <hggdh> weird. There is no coredump, but the bug was driven by apport
[21:03] <hggdh> I guess the reporter decided by the summary apport report
[21:03] <hggdh> well, then
[21:03] <Narc> Great. That's me. I always pick something odd as example.
[21:03] <dtchen> for those of you running ext4, what does the following command return?  grep ext4 /proc/mounts
[21:04] <hggdh> dtchen: http://pastebin.com/f181df7c7
[21:05] <hggdh> Narc: I do not deal much with FFox, but I am not sure how this bug can be used
[21:05] <hggdh> since the stacktraces are incomplete
[21:06] <Narc> Well, I just wanted to know the usual procedure with casual reports like these, because I saw plenty of them especially with Nautilus and FF.
[21:07] <hggdh> Narc: for *apport* bug reports, if the stacktrace is complete, then it can be pursued
[21:07] <hggdh> (I mean stackTrace and ThreadStackTrace)
[21:08] <hggdh> Of course, if the reporter has a way of triggering the error every time, this is a very good bit of information
[21:09] <hggdh> otherwise, you can look at https://wiki.ubuntu.com/Bugs/Responses and select one response as a good one
[21:09] <Narc> Yes, of course. I picked this one as an example because it seemed that the user wouldn't be able to replicate it.
[21:10] <Narc> Oh, thanks for the link
[21:10] <hggdh> a response that would fit, I think, is https://wiki.ubuntu.com/Bugs/Responses#Firefox%20crash%20report%20that%20fails%20retrace
[21:11] <hggdh> so -- following FF bug triaging, you can close INVALID with this message
[21:11] <hggdh> you might want to read https://wiki.ubuntu.com/BugSquad/KnowledgeBase for a general overview
[21:11] <hggdh> and -- Narc: thank you for helping
[21:12] <Narc> Oh, it's okay, thank YOU for helping me help
[21:12] <Narc> hggdh: so, if I get this right, it should be marked invalid because of the missing coredump, right ?
[21:13] <hggdh> either because the bug was not opened with a Coredump.gz attachment, or because the stack traces are incomplete, yes
[21:14] <Narc> Ok
[21:14] <Narc> I'll read the links now :)
[21:15] <dtchen> hggdh: thanks
=== Admiral_1hicago is now known as Admiral_chicago
[23:34] <_Narc_> Anybody can tell me under which package I should put a JRE bug report ? Thanks
[23:35] <dtchen> depends on the jre
[23:36] <dtchen> e.g., see 'java -version'
[23:37] <hggdh> you have Sun java, and OpenJDK java, for example. Then there are the different java versions
[23:38] <_Narc_> Well, maybe I'm not clear enough, but I'm not the submitter, I just triage bugs. And I got a JRE bug report and wondered if it goes under opensdk or something else
[23:40] <_Narc_> openjdk * sorry
[23:44] <dtchen> which bug #?
[23:47] <_Narc_> dtchen: https://bugs.edge.launchpad.net/ubuntu/+source/openjdk-6/+bug/477615
[23:47] <ubot4> Launchpad bug 477615 in openjdk-6 "Java/eclipse error" [Undecided,New]
[23:47] <_Narc_> But I figured it's openjdk-6
[23:47] <hggdh> correct
[23:48] <_Narc_> I'm learning
[23:48] <hggdh> _Narc_: :-)
[23:48] <dtchen> nicely done
[23:48] <hggdh> bonus points if you rephrase the bug title
[23:48] <hggdh> it is OpenJDK that sigsegv-ed
[23:49] <_Narc_> Ya, I wanted to, but the guy is very vague about "founding this log file" so I hesitated.
[23:49] <_Narc_> Ok, thanks
[23:50] <hggdh> although... the reporter *found* this on the user folder, yes. No instructions on how to reproduce
[23:51] <dtchen> that's a pretty nasty one to debug -- no useful info, really
[23:52] <_Narc_> Really ? If you say so I believe you. I'm still a beginner programmer :)
[23:52] <hggdh> yeah, the stacktrace does not show any symbolic entry points, only memory addresses
[23:52] <hggdh> so not really much to be done there.
[23:52] <_Narc_> What about the fact that I marked it as a duplicate with his first submission ? That must happen often, users submitting the exact same report twice... Is there anything to do except marking one of them invalid ?
[23:53] <hggdh> _Narc_: I would close it INVALID, with a comment stating that, unfortunately, there is nothing in the log that would help us pinpoint the error
[23:53] <_Narc_> Okay then
[23:53] <hggdh> oops -- this answer was for the previous issue
[23:53] <_Narc_> Ah, yes Firefox
[23:53] <_Narc_> Sounded familiar
[23:54] <hggdh> _Narc_: when the same bug is submitted twice (yes, it happens) we usually mark the most recent as a dup of the least recent
[23:54] <_Narc_> Carp... I did the opposite because his first report didn't include the "found" log file...
[23:55] <hggdh> now, if the least recent cannot be worked on (like on bug 477615), then we close INVALID as I just wrote
[23:55] <ubot4> Launchpad bug 477615 in openjdk-6 "Java/eclipse error" [Undecided,New] https://launchpad.net/bugs/477615
[23:55] <hggdh> no prob
[23:55] <hggdh> now you know ;-)
[23:55] <hggdh> and there is no real need to readjust in this case
[23:56] <hggdh> anyway. Usually we try to keep the oldest bug open, and mark as dups all others
[23:57] <hggdh> now, there is leeway here. If a more recent bug has a better-description/steps/whatever, we can use this bug, then, as the one to keep open
[23:57] <_Narc_> Yes, logical. I'll do that from now on. But what if, like in this case, the newer one is better than the older ?
[23:57] <_Narc_> Ah
[23:57] <_Narc_> You answered when I typed
[23:57] <_Narc_> Ok :)
[23:57] <hggdh> heh