[01:39] <andresmujica> good night!!
[01:46] <tat_> hello, after updating to ubuntu intrepid none of my wlan adapters is sending or reciving data anymore, i can connect to a network but i cant ping dhcp etc, the same with all of my 5 different adapters, when i reboot with kernel 2.6.24-19-generic instead of 2.6.27-9-generic everything works again, so it is a problem with the kernel, any idea what that could be
[01:48] <andresmujica> hi tat, do u have a bug #?
[01:51] <hggdh> yo andresmujica
[01:51] <tat_> no i was looking trough the buglist but every bug that sounds like myne is specific to a wlan driver, my problem is on 5 different driver, i think it is rather the 80211 kernel stack
[01:54] <andresmujica> ok...
[01:54] <andresmujica> i believe that we would need a different bug for each wlan driver....
[01:54] <andresmujica> is different HW after all...
[01:54] <andresmujica> isn't it?
[01:56] <tat_> andresmujica, : i think the driver do work fine it must be something different like the 80211 modeule or so,
[01:57] <andresmujica> hmmm, can you pastebin the lsusb  / lspci / lsmod for your wlan cards
[01:57] <andresmujica> !pastebin
[02:40] <andresmujica> i'm adding the ubuntu-co bugjam to the GBJ Wiki page, but i've got a doubt, what's the meaning of TBD??
[02:57] <Hobbsee> andresmujica: "to be decided"
[03:01] <hggdh> "to be done" later
[03:32] <bdmurray> "to be determined"
[03:38] <hggdh> :-)
[03:38] <thekad> "to be defined"
[03:38] <hggdh> "totaly bogus decision"
[03:54] <trevor_kemp> hi, all. this is my first use of IRC, so please forgive me if i am violating well-known etiquette. I am wondering if there is a way to get access to Ubuntu bug report exports. I am working on a triage project for my master's graduation that attempts to classify bugs as duplicates as appropriate. ideally, i would like to have a very large collection of bugs, including those identified as duplicates so i can train my system. i will be 
[03:56] <Ryan52> trevor_kemp, you got cut off after "i will be"
[03:56] <trevor_kemp> i will be happy to provide any additional information required. thank you for any and all assistance!
[04:03] <trevor_kemp> Does anybody know of a place where I could download an export of bug reports for such a project? If specific information would be more helpful in giving an answer, please let me know.
[04:09] <trevor_kemp> ok, thank you all for your time. please enjoy your day/evening.
[04:18] <hggdh> why are they so fast?
[04:26] <persia> hggdh, Those without long exposure to IRC don't generally have a reason to leave a window open for a long time.
[05:00] <hggdh> persia, yes... it was an interesting idea, though. Pitty.
[05:25] <dholbach> good morning
[06:51] <Zetto> Someone can include Bug #251173 in the milestone of jaunty-alpha-5 ?
[07:36] <thekorn> good morning
[07:45] <jpds> morgen thekorn.
[07:46] <thekorn> morgen jpds :)
[08:21] <MTecknology> Flannel: I love you :)
[08:26] <dholbach> MTecknology, Flannel: awwww, sweet! :-)
[08:26] <dholbach> That's what the Ubuntu Community is all about! :-)
[08:26] <MTecknology> dholbach: ya, he's my special friend
[08:27] <Flannel> MTecknology: As long as we don't have to kiss.
[08:27] <MTecknology> and the guy i resort to any time a channel can't help me
[08:27] <MTecknology> Flannel: don't worry - too tired rigth now
[08:27] <dholbach> MTecknology: I'm not going to inquire the "specialities of your friendship" any further :-)
[08:28] <MTecknology> he's helped me a lot
[08:28] <MTecknology> I wanna ask more - but too tired
[09:57] <BUGabundo> pidgin is needing a hugday!
[09:57] <BUGabundo> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/321800 is one of many segfaults or crash i've been having on jaunty
[10:29] <andresmujica> g'morn
[11:49] <cornucopic> persia, Hello!
[11:49] <cornucopic> Let's talk here?
[11:49] <cornucopic> persia, Sorry.
[11:49] <cornucopic> meant pedro_
[11:49] <cornucopic> pedro_, here?
[11:51] <pedro_> cornucopic: yeah sorry, xchat just crashed
[11:51] <cornucopic> pedro_, ahhuh.
[11:51] <tuxmaniac> pedro_: file a bug.
[11:51] <pedro_> cornucopic: first please read the how to triage guide https://wiki.ubuntu.com/Bugs/HowToTriage
[11:52]  * tuxmaniac ducks
[11:52] <BUGabundo> so its not only pidgin that keeps crashing on irx
[11:52] <BUGabundo> lol
[11:52] <tuxmaniac> All hail screen + irssi :-)
[11:52] <pedro_> cornucopic: if you want some easy targets to triage we collected some here: https://wiki.ubuntu.com/Bugs/EasyTasks
[11:52] <cornucopic> pedro_, seen the how-to sometime back.
[11:53] <pedro_> cornucopic: those are sorted by difficulty, so you can start with the easy ones for now and then try the other ones
[11:53] <cornucopic> Hmm..going through that now..
[11:54] <ccooke> Tuxmaniac: It surprises me that automatically setting yourself away when screen detaches isn't already in the standard install, to be honest :-)
[11:54] <ccooke> argh
[11:54] <ccooke> wrong window :-)
[11:54] <pedro_> cornucopic: I'd suggest you to go trough the list of bugs without a package first, those are easier to triage
[11:55] <tuxmaniac> ccooke: hey thanks for that tip.
[11:55] <cornucopic> pedro_, yeah..this is a ideal Triage: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-panel/+bug/315973 ?
[11:56] <ccooke> tuxmaniac: heh
[11:57] <pedro_> cornucopic: that's an example, yes, the bug didn't had a package assigned to it, if you look at the first comment the triager assigned it to gnome-panel which is correct
[11:58] <pedro_> cornucopic: and that comment is a stock response, we have a bunch of them that you can use in your daily triaging work
[11:58] <cornucopic> pedro_, yeah..would be better off saving them somewhere :-)
[11:58] <pedro_> cornucopic: https://wiki.ubuntu.com/Bugs/Responses <- stock responses
[11:58] <cornucopic> cornucopic, Oh! so..that is how the process works? Easy..i guess :-)
[12:00] <pedro_> cornucopic: yes the bugs without a package are an easy target, you only need to assign it to the right one
[12:00] <cornucopic> pedro_, cool!
[12:01] <cornucopic> pedro_, Your help much appreciated :-)
[12:05] <pedro_> cornucopic: no problem, if you have any question just ask here in the channel ;-)
[12:05] <pedro_> cornucopic: btw if you want to learn some more, this Thursday (29) we have a bug day based on compiz
[12:07] <cornucopic> cornucopic, Ah..i will look up the timings..
[12:11] <cornucopic> pedro_, Can't seem to find here at https://wiki.ubuntu.com/Bugs/Events
[12:12] <pedro_> cornucopic: uh right, updating it now
[12:12] <cornucopic> pedro_, cool!
[13:36] <LimCore> hi, what an epic fail today I discovered \o/
[13:36] <LimCore> hard drive works x10 slower O_o what the hell
[13:36] <LimCore> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/119730
[13:37] <LimCore> Is any of you up to date on this bug?  (very long comments)?  I guess it is being fixed right now and in 8.04 I will be able to soon use fixed version?
[13:39] <pedro_> LimCore: better to ask in #ubuntu-kernel
[13:40]  * LimCore tries to figure out why _x10_ slower hard drive is only Undedicded importance.....
[13:41] <pedro_> LimCore: the importance is set to Medium not to Undecided...
[13:42] <LimCore> ah right, I was looking at ubottu here.
[14:39] <LimCore> well, typical workarounds (blacklist module & rebuild initrd) didnt work for me...
[14:39] <LimCore> still I get x10 slower hard-drive transferts.
[14:40] <bddebian> Boo
[16:20] <davideotape> Hi guys
[16:22] <hiberis> Hi all, I just joined the bugsquad.
[16:22] <davideotape> Hi, I've just joined too
[16:23] <hiberis> Hi davideotape!
[16:23] <hiberis> I am doing some triaging and have a question about setting the bug status.
[16:23] <hiberis> bug 195271
[16:24] <hiberis> bug 195271
[16:25] <hiberis> This bug is already fixed in gnumeric upstream trunk, but has had no upstream release yet. To what should I set the bug status?
[16:27] <hiberis> btw, the upstream bug status in launchpad is set to 'fix released', in gnome bugzilla it is set to 'fixed', which means 'fixed in svn'.
[16:27] <MrKanister> hiberis: You can set the status for the Ubuntu package to "fix commited"
[16:30] <hiberis> MrKanister: From https://wiki.ubuntu.com/Bugs/Status, I see "Fix Committed: For a bug task about an upstream project: the fix is in CVS/SVN/bzr or committed to some place".
[16:31] <hiberis> Isn't this supposed to indicate only bugs monitoring upstream?
[16:31] <hiberis> I mean: what does this mean "a bug task about an upstream project"?
[16:31] <MrKanister> hiberis: Bugs that are monitored can just be "fix released" not "fix commited". I think that depends on how the monitoring was implemented
[16:32] <hggdh> hiberis, on the bug you are talking about, this is the entry for the gnome bug
[16:33] <hggdh> hiberis, and I agree with your point of view re. the wiki
[16:34]  * hggdh had a problem not long ago about it
[16:35] <hggdh> for ubuntu bugs (i.e. bugs that will have to be dealt with an updated package, 'fix committed' is restricted to when the package is put available (usually on -updates)
[16:35] <hggdh> (although the desktop team used to work a bit different)
[16:38] <hiberis> hggdh: seams reasonable. So what should I do with the status of the ubuntu bug: leave it at confirmed, although a fix is committed upstream?
[16:51] <LimCore> I have 6 MB/s transfer on modern hardware (SATA hard drive). Perhaps this bug should be High priority?   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/119730
[16:59] <greg-g> LimCore: the original report said it was fixed, then said it wasn't, then said he needed to find out more information (which he never did)
[17:00] <greg-g> it is hard to make sense of a bug report that has that amny people giving input, so if you want to help, you can try to make a concise summary of the bug
[17:13] <klotz> Can I get help here on installing linux-crashdump metapackage to create kernel core dumps?  (I have debugged kernel modules under SunOS and maintained Linux modules before).
[17:19] <hggdh> hiberis, leave it as "triaged"
[17:21] <hggdh> LimCore, please see https://wiki.ubuntu.com/Bugs/Description on how to summarise the issue
[17:21] <hggdh> klotz, it should install & configure itself
[17:24] <klotz> thanks hggdh I installed it and found I had to run update-grub to get crashkernel=x@y into the grub menu.lst but when I reboot it always complains there is no memory reserved.  I have cat /proc/iomem at http://graflex.org/klotz/2009/01/iomem.txt
[17:25] <klotz> linux-crashdump is version 2.6.27.9.13 and kernel line is crashkernel=384M-2G:64M@16M,2G-:128M@16M
[17:26] <hggdh> klotz, did you search on LP for this issue?
[17:26] <klotz> hggdh yes and feature is new in Intrepid; only developers of feature saying it works now and is in intrepid.
[17:28] <hiberis> hggdd: I can't set it to triaged. Only confirmed. Is that because I am not in bugcontrol?
[17:29] <klotz> hggdh so is it ok for me to file bug now with info likei have presented or should i go to another channel to ask for help?  I'm happy to do either.
[17:29] <hggdh> hiberis, I will do it
[17:30] <hggdh> klotz, opening a bug is a good idea no matter what. Also, you may get more on
[17:30] <hggdh> klotz, #ubuntu or #ubuntu-kernel
[17:31] <klotz> hggdh thank you and I will switch to ubuntu-kernel and file bug if they don't know what I've done wrong; thank you.
[17:33] <hggdh> klotz, welcome
[17:34] <hiberis> hggdh: okay, thanks. Is this the normal procedure 'just ask someone on ubuntu-bugs to change is for you'. I remember to have read this somewhere but I cannot find it anymore.
[17:38] <chrisccoulson> ping kees - how familiar are you with vte?
[17:38] <chrisccoulson> the only reason I ask is because you submitted quite a large patch to gnome bugzilla a while ago
[17:40] <hggdh> hiberis, to set a bug to triaged/wishlist yes. You have to be a member of bug-control to do that
[17:40] <hggdh> hiberis, BTW -- tahnk you for helping
[17:42] <hiberis> hggdh: no, thank you!
[17:58] <kees> chrisccoulson: yup
[17:58] <kees> chrisccoulson: been working on getting it upstream for a long time now.
[18:01] <chrisccoulson> cool. upstream removed the ability to build it without ncurses in the new version, and i was going to ask if you could review a patch colin watson just did to make this to work again
[18:01] <chrisccoulson> bug 321848
[18:01] <chrisccoulson> it builds with the correct dependencies, but it needs a sanity check from someone who's slightly more familiar
[18:02] <kees> sure, do you have a straight diff of the change somewhere?
[18:05] <chrisccoulson> its in bzr, but I just posted the actual patch in debian/patches here: http://paste.ubuntu.com/110373/
[18:05] <chrisccoulson> the configure.in change was already in the last version, but colin modified it as I made a mistake (which is why it ended up being linked against ncurses)
[18:05] <chrisccoulson> the other source changes look very similar to what was already in the old version
[18:06] <kees> chrisccoulson: that patch looks fine to me.  Hopefully upstream will take it.
[18:06] <chrisccoulson> it would be nice, but they already removed this functionality from the new version :(
[18:06] <chrisccoulson> hence the new patch to add it back in again
[18:07] <chrisccoulson> i'll leave a comment on the bug report so colin uploads it if you like
[18:08] <kees> yeah.  I'm not sure I understand your comment about upstream though?
[18:08] <chrisccoulson> which comment was that?
[18:09] <kees> chrisccoulson: does ssfe.c even need termcap at all?
[18:09] <kees> chrisccoulson: you said upstream might not take this patch?
[18:09] <chrisccoulson> ah yeah. i doubt upstream will take the patch, as they already removed this functionality (ability to build without ncurses) from the latest version
[18:10] <chrisccoulson> i was wondering whether ssfe.c needed termcap too
[18:10] <kees> chrisccoulson: I think it need to be demonstrated that it's important, and a trivial fix
[18:10] <kees> if you remove the entire chunk of headers does it still compile?  :)
[18:11] <chrisccoulson> yeah, maybe i'll discuss this with upstream. i haven't tried removing that chunk of headers from ssfe.c, but I guess it will still compile. It compiles with the new patch which basically removes those headers (in a more long-winded way) anyway
[18:14] <chrisccoulson> thanks for looking at that anyway kees
[18:19] <kees> chrisccoulson: sure!
[18:32] <tawmas> Hello!
[18:33] <tawmas> I have a bug where multimedia keys and other extended keys are totally ignored. I followed https://wiki.ubuntu.com/Hotkeys/Troubleshooting and found that neither keypresses nor ACPI events are generated. Do I file a bug against the kernel?
[18:35] <[swb]> hey guys
[18:35] <seb128> hi bracket named guy
[18:35] <[swb]> wondering if anyone would be interested in trying to reproduce a bug in gnome-panel behaviour for me
[18:35] <[swb]> heh
[18:35] <[swb]> I am called seb
[18:35] <[swb]> I normally go by swb but it was taken on freenose
[18:35] <[swb]> so I have to have brackets
[18:36]  * ogra sneezes ... 
[18:36] <ogra> freenose, heh
[18:36] <[swb]> hehe yeah
[18:36] <[swb]> thats my pet name for it
[18:36] <seb128> describe your bug
[18:36] <[swb]> its to do with panel position and lockedness
[18:36] <seb128> usually people add ___ to their nickname rather
[18:36] <[swb]> bug is
[18:37] <[swb]> seb128, aye if its temporary but I wanted to register
[18:37] <seb128> I need to use a modifier to type a [ so I will avoid using it ;-)
[18:37] <[swb]> haha ok
[18:37] <[swb]> are you using a happy hacker?
[18:37] <seb128> happy hacker?
[18:37] <[swb]> its a leet little keyboard
[18:37] <seb128> I'm using an azerty layout
[18:37] <seb128> ie french keyboard
[18:37] <[swb]> where everything is on modifiers
[18:37] <ogra> [swb], he is using one of these weird kbd setups
[18:37] <[swb]> ic
[18:38] <seb128> anyway gnome-panel bug you were saying?
[18:38] <[swb]> anyway, the bug, you make a new gnome panel, set it to be at the bottom, and then unclick the expand
[18:38] <[swb]> lock it or dont, it doesnt seem to matter, then gnome-session, low and behold the panel is at the top and locked
[18:38] <seb128> "then gnome-session"?
[18:38] <[swb]> if you unlock it, go into properties and try and select bottom it flicks back to top
[18:39] <[swb]> and you cant drag it
[18:39] <seb128> what ubuntu version do you use?
[18:39] <[swb]> sorry
[18:39] <[swb]> then restart your gnome session
[18:39] <[swb]> or X
[18:39] <[swb]> Intrepid
[18:39] <[swb]> 64 bit
[18:39] <[swb]> on a core 2 duo
[18:40] <seb128> that's a known issue
[18:40] <seb128> I though it was fixed in intrepid though
[18:41] <[swb]> apparently not...
[18:41] <seb128> there is bug #15442 but that's a different one
[18:42] <seb128> [swb]: yours seems similar to bug #39856
[18:43] <[swb]> middle of screen would be REALLY annoying
[18:43] <seb128> ok, that one got fixed
[18:43] <seb128> so yours is similar to the other one
[18:44] <[swb]> kind of
[18:44] <[swb]> except mine is appearing below the top panel
[18:44] <[swb]> rather than switching positions with it
[18:44] <[swb]> I want it at the bottom but it cant actually be set to be at the bottom
[18:44] <[swb]> but only when not expanded
[18:45] <[swb]> sorry I should have mentioned that, it will go to the bottom when its expanded but not when its not, ie you cant actually make that setting in properties without it flicking back instatnyl
[18:45] <seb128> is that specific to the lock option?
[18:45] <[swb]> no
[18:46] <[swb]> when locked the top,bottom. etc sleector is grayed out
[18:46] <seb128> open a bug and describe exactly what you do to trigger the issue
[18:46] <[swb]> aye ok
[18:46] <[swb]> I was wondering if anyone could make a panel, set it not to expand and have it set at the bottom
[18:46] <[swb]> in that order
[18:47] <[swb]> I wanted to know before filing
[18:47] <seb128> I've to run for now but I'll give it a try later
[18:47] <[swb]> it works if you set it to expand then set it to the bottom
[18:47] <[swb]> aye
[18:47] <[swb]> ok cya later
[19:29] <kees> bdmurray: say, I have a question about bug search URLs that is confusing me.
[19:30] <bdmurray> kees: okay, go
[19:30] <kees> (sorry was, pasting together an example)
[19:30] <kees> http://pastebin.osuosl.org/23567
[19:30] <kees> okay... the first is limited to "in ubuntu", by starting at bugs.lp/ubuntu/ before going to "advanced"
[19:30] <kees> the second one is global, all bugs ubuntu-security is subscribed to
[19:31] <kees> however, 239894 doesn't show up in the first, where I'd expect it to.
[19:31] <bdmurray> This that malone bug I mentioned the other day
[19:32] <bdmurray> Or similar
[19:32] <kees> oh!  I thought that was limited to the API goo
[19:32] <bdmurray> It doesn't show up because the non-release task is Fix Released
[19:33] <kees> yeah.. hmpf
[19:33] <bdmurray> They milestoned that bug the other day
[19:34] <kees> hrm, I set the non-release task to "new" and it still doesn't show up.  malone bug?
[19:34] <bdmurray> your first limit is inprogress not new
[19:35] <kees> right, but it doesn't see _any_ of the non-release tasks.  :(
[19:35] <kees> if I set it to "in progress" then only the release task appears
[19:36] <bdmurray> I see 4 tasks with that search now
[19:36] <bdmurray> for 239894
[19:36] <kees> but not in the first search (which is limited to ubuntu only)
[19:38] <askand> I dont think bug 304981 should be marked incomplete anymore
[19:38] <calc> heh somehow someone managed to not know how to report a bug in ubuntu but managed to find my email address and send me the bug report directly
[19:39] <calc> i guess Help->Report a bug never occurred to them
[19:39] <bdmurray> kees: as I understand it searching searches the non-release tasks and because that bug doesn't meet your criteria for the search it doesn't show up.
[19:40] <kees> bdmurray: yeah, makes sense.  I'll open a bug report about it.
[19:40] <bdmurray> kees: it's already open
[19:40] <kees> bdmurray: I don't think that task bug is the same -- you said it was due to the top-level task being open or closed?
[19:41] <bdmurray> kees: did you try changeing 239894 to In Progress?
[19:41] <kees> bdmurray: yeah, it'll show up only if I mark the top task to In Progress.  the per-release tasks never show up.
[19:42] <bdmurray> right and that's the "master task" I think
[19:42] <bdmurray> see bug 314432
[19:43] <bdmurray> and or bug 290125
[20:01] <kees> bdmurray: okay, thanks.  I've updated 322009 to reflect that.
[21:00] <lfaraone> Can someone confirm bug 322051 for me?
[21:07] <james_w> lfaraone: doesn't normal dget work there?
[21:08] <lfaraone> james_w: isn't there a reason we have dgetlp?
[21:08] <lfaraone> james_w: normal dget refuses to extract citing invalid sigs for me
[21:08] <james_w> because you didn't used to be able to dget some of the source packages on lp
[21:08] <james_w> dget -u
[21:09] <james_w> or dpkg-source -x afterwards
[21:09] <lfaraone> james_w: ah. then shall I change the bug to "delete dgetlp" instead?
[21:09] <james_w> probably
[21:09] <james_w> I can't remember if all the places where dgetlp was needed have been fixed
[22:28] <victorbrca> Hi all, I've found a bug that seems to be reported multiple times under different bug number on launch pad.
[22:28] <victorbrca> should I report as duplicate?
[22:29] <victorbrca> I'm not really familiar with launch pad. :-/
[22:29] <chrisccoulson> no need to report a new one if you're sure that the problem you're experiencing is the same
[22:29] <victorbrca> I haven't
[22:29] <victorbrca> just wondering if I should flag the existing ones as duplicates
[22:30] <chrisccoulson> which bugs?
[22:30] <victorbrca> http://pastebin.com/m782138bb
[22:30] <chrisccoulson> bug 286489
[22:31] <chrisccoulson> bug 293661
[22:31] <chrisccoulson> bug 212497
[22:31] <chrisccoulson> bug 141343
[22:31] <chrisccoulson> bug 205374
[22:31] <victorbrca> cool
[22:31] <victorbrca> I ddn't the bot could do that
[22:32] <victorbrca> They are all related to the same chipset and module on Ubuntu
[22:32] <victorbrca> Very similar problems present on different versions of Ubuntu and different kernel versions
[22:33] <chrisccoulson> the problem is with kernel bugs is it can be difficult deciding if they are duplicates. very often, very different bugs can have the same symptoms
[22:33] <chrisccoulson> unless you are absolutely sure they are the same, then i'd leave them as they are for now
[22:33] <victorbrca> ok!
[22:34] <victorbrca> what happens if I do select the option of "Mark as duplicate"?
[22:34] <victorbrca> how much editing power do I have over bugs?
[22:34] <victorbrca> I'm just a normal user!
[22:35] <chrisccoulson> you can do most things. you can add comments, edit the description, mark as duplicates, change the status, subscribe people, add tags, re-assign etc
[22:35] <loic-m> victorbrca: normal users can mark bugs as a duplicate. However, unless you're sure the bugs are exactly the same, you'll end up with 2 things:
[22:35] <loic-m> ictorbrca: more launchpad points, and far less friends
[22:36] <loic-m> s/ictorbrca/victorbrca/
[22:36] <loic-m> ;)
[22:36] <victorbrca> loic-m: lol
[22:36] <victorbrca> loic-m: Thanks for the info. I'm more interesting in helping fixing the problem.
[22:37] <victorbrca> loic-m: Sometimes having multiple entries for the same problem can be a draw back.
[22:37] <chrisccoulson> i have to admit, i have wrongly marked bugs as duplicates before, and people aren't happy when you do that
[22:37] <loic-m> victorbrca: marking bugs as duplicate is more harmful than leaving them as they are
[22:37] <victorbrca> loic-m: Good to know!
[22:37] <chrisccoulson> its sometimes a pain to undupe bugs afterwards, especially if theres a lot of them
[22:38] <chrisccoulson> and everyone subscribed to the main bug and its duplicates get bug spam ;)
[22:38] <loic-m> victorbrca: it's easy for the dev fixing the bug to mark other bugs as duplicate when he's confirmed the fix works for everybody (or gets enough logs to check they're the same)
[22:39] <victorbrca> Is there a "guide" or "code of behaviour" I can find for launchpad?
[22:39] <loic-m> victorbrca: while if you mark bugs as duplicate who aren't, it means some of them are going to take far longer before one notice they're not solved
[22:39] <victorbrca> I'm glad I ddn't!
[22:40] <loic-m> victorbrca: and people filing the bugs might have "gone away" in the sense they relly on other people to provide the information
[22:40] <victorbrca> Would be doing bad when what I really wanted to do was help.
[22:40] <chrisccoulson> victorbrca - there is a code of conduct you can sign
[22:40] <chrisccoulson> how do i get ubottu to show the link to the CoC?
[22:41] <victorbrca> If I find a solution, which bug should I report it under? All of them (like I did before)?
[22:42] <loic-m> victorbrca: we all learn by trial and error (or by seeing mistakes), but for duplicate the idea is it's really hard when it's related to hardware/kernel/drivers, and easier for software
[22:43] <chrisccoulson> although it can be hard for some other software too
[22:50] <victorbrca> So I should really just take another look at all the bugs and try to find out which is the most applicable to my situation,
[22:50] <victorbrca> the add my resolution there.
[22:50] <victorbrca> **then
[23:08] <Craig73> Would someone be able to assist me in switching bug #110873 to "won't fix".  Thanks.  [technically the developers updated the comments in the config file, but as the defaults didn't change it is won't fix]
[23:13] <hggdh> Craig73, can you add a link to the maillist archives with this dialog?
[23:14] <hggdh> and -- even if upstream decided not to change it, we could have a local patch to do it (which I am, personally, against: too many ports)
[23:24] <hggdh> Craig73, never mind. I added it in & closed wont fix. Thanks for the help
[23:26] <Craig73> Oh I could have done that /sorry I grabbed some dinner
[23:26] <hggdh> Craig73, np. I am very glad you helped. Thank you, really.
[23:27] <Craig73> Thank-you as well (and I know to link to the mailing list in the future rather than cut and paste)
[23:27] <hggdh> it is always a good thing to provide the links -- helps when somebody tries to backtrack
[23:29] <Craig73> I agree though that patching it ourselves should be avoided... I could see writing the patch for them (well not this case) assuming it's just a matter of resources.
[23:29] <Craig73> ok ... later