[00:07] <lifeless> charlie-tca: UI :)
[02:00] <abuDawud> Can someone confirm if this bug needs to go to 'Invalid' status? https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/678330
[02:00] <ubot2> Launchpad bug 678330 in empathy (Ubuntu) "Empathy 2.32.2 Stable Release Update Request (affects: 1) (heat: 6)" [Undecided,New]
[02:01] <micahg> abuDawud: no, that's fine
[02:02] <abuDawud> So then the upstream data should be posted and it should be wishlisted?
[02:02] <micahg> abuDawud: no, it's an Ubuntu specific request
[02:07] <micahg> abuDawud: well, wishlisted yes, but that's it
[02:07] <abuDawud> micahg, still learning please excuse me, with an Ubuntu specific request the options would be to send for packaging, or to close it as invlaid and refer to brainstorm
[02:07] <abuDawud> correct?
[02:08] <micahg> abuDawud: what do you mean send for packaging?
[02:09] <abuDawud> set to wishlist and... I guess thats it
[02:09] <abuDawud> micahg, we don't actually assign to MOTU or anything correct?
[02:09] <micahg> abuDawud: correct
[02:10] <abuDawud> okay then, since I don't have privileges to set to wishlist could someone do that for me, and in the future is IRC really the best place to note something needing to be set to this status?
[02:11] <micahg> abuDawud: yes
[02:11] <micahg> abuDawud: also, the reporter of that was a bug control member
[02:12] <abuDawud> micahg, I saw he was a regular on launchpad, could he not wishlist it himself?
[02:12] <micahg> abuDawud: yes, he could
[02:12] <micahg> I've set it though
[02:12] <abuDawud> thanks.
[02:13] <abuDawud> micahg, got a sec for another question? If a bug can't be reproduced using the listed steps, whats the process
[02:13] <abuDawud> eg. https://bugs.launchpad.net/ubuntu/+source/bash/+bug/678354
[02:13] <ubot2> Launchpad bug 678354 in bash (Ubuntu) "after upgrade to 10.10 alt + . is not working anymore (affects: 1) (heat: 6)" [Undecided,New]
[02:13] <micahg> abuDawud: do you mind if we continue in about 15 minutes?
[02:13] <abuDawud> micahg, no problem, thanks for your help
[02:18] <charlie-tca> abuDawud: on the bash bug, you might ask the reporter for specific steps to reproduce it. The way the report reads, you don't actually know what is being done.
[02:19] <charlie-tca> Also, sometimes the specific keyboard layout used matters. I use US Int'l , which is different than the default for English
[02:21] <abuDawud> charlie-tca, thanks, the only thing I can think is he is trying to use right-alt. Thats why I was specific with the left alt part. Looks like an automated bug report though right?
[02:23] <charlie-tca> That is why we ask questions. If we guess at how to do it, we are usually wrong.
[02:23] <charlie-tca> Most bug reports are automated now, but that doesn't mean you can't ask how to reproduce it with specific steps
[02:24] <abuDawud> charlie-tca, I will remember that from now on, I didn't ask any questions due to the automated bug report but I guess its not a big deal to them if they are not following the bug correctly.
[02:25] <charlie-tca> There are a whole list of responses you can use, just copy and paste to the bug report. the URL is
[02:25] <charlie-tca> https://wiki.ubuntu.com/Bugs/Responses
[02:25] <charlie-tca> Note number 2
[02:25] <abuDawud> awesome, thanks charlie-tca
[02:26] <charlie-tca> It doesn't matter if the reports are automated or not, we still need information to reproduce them and to get them ready for the developers to work
[02:30] <charlie-tca> abuDawud: thank you very much for helping with bugs.
[02:30]  * yofel wonders if there's a way to dump the runtime bash configuration
[02:31] <yofel> alt+. depends at least on emacs mode being used (which should be the default)
[02:33] <charlie-tca> it depends on the keyboard setup, too. I don't have right-alt+ with this setup, but the default uses both left and right
[02:34] <yofel> right, left_alt + . works as described in emacs mode here, right_alt + . prints '…'
[02:58] <micahg> BTW, both my ALT keys + . produce the last argument
[03:03] <abuDawud> My rightalt+. does not work, but the workaround is noted here
[03:03] <abuDawud> http://jorgenmodin.net/index_html/archive/2010/10/25/alt-dot-not-working-in-ubuntu-1010---workaround
[03:36] <abuDawud> Opinion? https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/678319
[03:36] <ubot2> Launchpad bug 678319 in software-center (Ubuntu) "Integrate update-manager in Ubuntu Software Center (affects: 1) (heat: 6)" [Undecided,New]
[03:37] <micahg> abuDawud: that might be a duplicate, I believe that's on teh roadmap for software center, just don't know which release
[03:39] <abuDawud> micahg, looking through all the bugs for update-manager I did not see anything there, and there are no blueprints. Somewhere else to look?
[03:40] <micahg> abuDawud: look in software center
[03:42] <abuDawud> micahg, nothing @ https://bugs.launchpad.net/update-manager and the blueprints for that 'branch' are empty
[03:42] <micahg> abuDawud: no, search for the bugs in Ubuntu
[03:43] <micahg> https://bugs.launchpad.net/ubuntu/+source/software-center
[03:43] <abuDawud> ah, cerp
[03:43] <abuDawud> derp*
[03:45] <abuDawud> micahg, closest thing I found was an error when opening Software Center when update-manager was running, but no requests for a merge
[03:48] <micahg> abuDawud: I don't see anything either
[03:48] <abuDawud> micahg, since it appears to be an 'off-the-hip' opinionated request, would it go to opinion?
[03:49] <micahg> abuDawud: no
[03:49] <micahg> it's actually been discussed
[03:49] <micahg> abuDawud: also, opinion is only when the maintainer believes that a bug should not be worked on
[03:50] <abuDawud> so to get to opinion it needs to show an alternative thought process in the same bug?
[03:52] <micahg> abuDawud: in Ubuntu, we don't really use opinion that often, in fact, it might not be around for much longer (it was just an experiment)
[03:57] <abuDawud> Thanks for your help once again micahg.
[03:58] <micahg> abuDawud: np
[04:27] <abuDawud> how long should I wait before submitting an app to bugcontrol. I have a history of QA stuff for a medical software company IRL :)
[04:28] <micahg> abuDawud: the suggestion is 5 bugs where you can show evidence of triaging work, unless you're an upstream developer with a current bug control member to advocate for you
[04:29] <micahg> abuDawud: https://wiki.ubuntu.com/UbuntuBugControl
[04:30] <abuDawud> micahg, so since I can't show evidence of all the duplication stuff, it may be a couple of days...
[04:30] <abuDawud> thanks
[04:31] <micahg> abuDawud: take a while, the only difference for bug control is being able to set importance, and the triaged/won't fix status, so there's no rush
[13:51] <njin> Pedro_: hello fellow, Linux key + p is a hidden shortcut ?
[13:51] <njin> pedro_:^^
[14:02] <seb128> njin, hi, what is your issue exactly?
[14:03] <seb128> njin, it's a special keybinding win-7 is using for showing display control
[14:03] <seb128> njin, recent laptops got modified bios to handle that in a special way
[14:04] <njin> seb128: bug678423
[14:05] <njin> bug 678423
[14:05] <ubot2> Launchpad bug 678423 in ubuntu "Keyboard shortcut Super+p causes entire screen to redraw (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/678423
[14:05] <seb128> bug #678423
[14:05] <seb128> bug #539477
[14:05] <ubot2> Launchpad bug 539477 in linux (Ubuntu Natty) (and 9 other projects) "Video out hot key sends super + p + return on many upcoming Dell & HP systems (affects: 20) (dups: 2) (heat: 142)" [Undecided,Invalid] https://launchpad.net/bugs/539477
[14:05] <seb128> njin, ^
[14:05] <seb128> njin, see that bug, you can maybe comment there
[14:06] <njin> seb128:thanks
[14:34] <njin> seb128: can you reproduce it typing super + p ?
[14:37] <seb128> njin, no but I'm on natty and not uptodate
[14:42] <njin> seb128: not reproducible in natty by me too, but in maverick, hitted two times it change the resolution
[14:43] <seb128> njin, the g-s-d upload was not in natty so seems right
[14:52] <njin> seb128: then g-s-d is the same of maverick, so i'm thinking on a lower level, xserver-xorg-input-keyboard as it can be easily reproduced and in Natty we have an updated version of xorg
[14:53] <seb128> no it's not
[14:53] <seb128> did you read the bug I pointed before?
[14:53] <seb128> there was a stable update to fix the handle of that keybinding
[14:53] <seb128> which is not uploaded to natty
[15:59] <abuDawud> can someone please set bug# 678460 to wishlist after a quick review?
[16:11] <charlie-tca> bug 678460
[16:11] <ubot2> Launchpad bug 678460 in nux (Ubuntu) (and 2 other projects) "don't ship .bmp files but rather .png (affects: 1) (heat: 6)" [Critical,Triaged] https://launchpad.net/bugs/678460
[16:12] <charlie-tca> hm, not going to do that. critical to wishlist seems wrong
[16:41] <jcastro> pedro_: holler at me when you announce the banshee hug day pls
[16:41] <pedro_> oops
[16:42] <pedro_> jcastro, i'll do that today afternoon, just being too busy atm
[16:42] <jcastro> pedro_: nod, I just wanted to catch you before you did. :)
=== deryck is now known as deryck[lunch]
[18:20] <njin> pedro_: hello, can i disturb ?
=== deryck[lunch] is now known as deryck
[18:21] <njin> gdm-binary[1097]: WARNING: Unable to load file '/etc/gdm/custom.conf': Нет такого файла или каталога
[18:21] <njin> and various segfault during shutdown
[18:22] <njin> can be  a linuxissue ?
=== yofel_ is now known as yofel
=== bilalakhtar is now known as papercutter
=== papercutter is now known as bilalakhtar
[18:55] <Tiibiidii> hi
[18:55] <Tiibiidii> i have some general questions
[18:56] <Tiibiidii> for example: now some bugs that i've reported some time ago, are going to expire
[18:56] <Tiibiidii> and i'm realizing that for some bugs
[18:57] <Tiibiidii> (tipically these are the "most interesting" bugs: memory leaks, crashes...)
[18:57] <Tiibiidii> i've not been actually able to replicate them
[18:57] <Tiibiidii> (contrarly to user interface bugs or bugs found when testing and alpha/beta of ubuntu)
[18:58] <yofel> only incomplete bugs can expire, so either add the missing information to the bug or change the status if the information was added
[18:58] <Tiibiidii> and i was wondering.... do you think it's still relevant to report them?
[18:58] <Tiibiidii> yofel, that's the problem
[18:58] <Tiibiidii> i reported all the information that was needed
[18:59] <Tiibiidii> when i had this avilable
[18:59] <Tiibiidii> but since i can't replicate the bug
[18:59] <Tiibiidii> i cannot add more detail
[18:59] <Tiibiidii> i mean: i don't like this... because the bug is definitely still there somewhere
[19:00] <Tiibiidii> but indeed, keeping track of it seem quite useless
[19:00] <geekosopher> Tiibiidii: if the problem was in alpha/beta versions, but not in final, that seems the bugs are fixed
[19:00] <Tiibiidii> (actually, one time i remember i was able to replicate the bug, but wasn't able to report a valgrind log, due to valgrind crashing)
[19:01] <Tiibiidii> no, they were reported with a stable release (at least the one i'm talking about)
[19:01] <Tiibiidii> i mean...
[19:01] <Tiibiidii> i'm not a member of the bugsquad or anything
[19:02] <Tiibiidii> i don't actively search bugs most of the time
[19:02] <Tiibiidii> i just happen to report them when it happens
[19:02] <Tiibiidii> (btw, do you think it's fine this way? i mean: joining the bug squad seems like another responsibility to have to keep track of)
[19:02] <yofel> well, the auto-expiring is a bit annoying here, but we have so many bugs that those that we don't have stepst to reproduce them for are hardly going to get fixed
[19:03] <geekosopher> Tiibiidii: that itself is an important contribution
[19:03] <Tiibiidii> and so i was wondering how do you do in these cases
[19:03] <Tiibiidii> ok
[19:03] <Tiibiidii> so, do you report them nonetheless, and just don't bother if they expire without you being able to contribute any additional information?
[19:04] <Tiibiidii> (or wait until you've been able to define the steps needed to reproduce the bug, and only then trying to report it?)
[19:04] <Tiibiidii> (thank you for your attention in the meanwhile)
[19:05] <yofel> I would let them expire, If a bug still needs more information and I can't provide it, the bug is probably not going to get fixed, you can always reopen the bug or file a new bug once you can reproduce the issue again.
[19:05] <Tiibiidii> ok
[19:06] <Tiibiidii> i was also thinking
[19:06] <yofel> and no, report the bug once you see it, could be a one time failure that many people hit for example
[19:06] <Tiibiidii> ok, good to know it's fine this way
[19:06] <geekosopher> Tiibiidii: it is not just you, if someone else faces the same problem, he/she will confirm the bug and probably provide the required information, so it should be reported nontheless
[19:06] <Tiibiidii> i like launchpad a lot, and i find bugzilla quite clunky...
[19:07] <Tiibiidii> but for many projects, the upstream is not in launchpad
[19:07] <Tiibiidii> and since the resources for ubuntu developers are quite scarce...
[19:07] <geekosopher> nobody is perfect ;)
[19:08] <Tiibiidii> i mean: ideally we should report all the bugs... and then when relevant report them upstream
[19:08] <charlie-tca> Tiibiidii: it has taken 4 years to figure out how to reproduce reliably a panel crash in xubuntu
[19:08] <Tiibiidii> uh
[19:09] <charlie-tca> But i can now reliably reproduce it
[19:09] <Tiibiidii> the point is... often bugs in launchpad take a lot of time to be triaged (if ever), and often the triager is not a proper developer
[19:09] <yofel> that's called lack of manpower, sadly :/
[19:09] <charlie-tca> if the bug can not be reproduced, it is very difficult for the developer to reproduce it too
[19:09] <Tiibiidii> yeah
[19:09] <Tiibiidii> so i was thinking that from now i could directly report them upstream
[19:10] <geekosopher> charlie-tca: really!?
[19:10] <geekosopher> hehe
[19:10] <charlie-tca> yup
[19:10] <charlie-tca> reporting it directly upstream if it can be reproduced results in the same action
[19:10] <Tiibiidii> the problem is:  as i said before, i'm not doing it proactively... i already created accounts and used them in the mozilla bugzilla, in the gnome bugzilla ( and maybe also in a novell bugzilla)
[19:11] <Tiibiidii> does everybody of you have so many bug trackers accounts?
[19:11] <Tiibiidii> or maybe you specialize only with bugs in some certain software/frameworks
[19:11] <charlie-tca> abuDawud: bug 678460
[19:11] <ubot2> Launchpad bug 678460 in nux (Ubuntu) (and 2 other projects) "don't ship .bmp files but rather .png (affects: 1) (heat: 6)" [Critical,Triaged] https://launchpad.net/bugs/678460
[19:11] <Tiibiidii> (e.g. you happen to report mainly only firefox and thunderbird bugs)
[19:12] <charlie-tca> was filed by a developer, triaged and marked importance by the developer. We do not change status once the bug is changed to triaged
[19:12]  * yofel has accounts for: launchpad, sourceforce, gnome, kde, mozilla, quassel (and whatever I can't remember ATM) - debian doesn't need an account at least)
[19:12] <charlie-tca> I have so many I quit counting
[19:12] <Tiibiidii> ok, so it's a common problem
[19:12] <abuDawud> can someone please set the status of https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/678125 to triaged?
[19:12] <ubot2> Launchpad bug 678125 in openoffice.org (Ubuntu) (and 1 other project) "No A6 format preset in 'page' dialog (affects: 1) (heat: 8)" [Wishlist,Confirmed]
[19:12] <charlie-tca> abuDawud: Please do not touch the bugs that are already "triaged" status
[19:13] <abuDawud> charlie-tca, yea i have made two big mistakes today... part of the learning process I guess
[19:13] <charlie-tca> as long as we learn, it is okay to make mistakes. It is when we repeat them a number of times that it becomes a problem.
[19:14] <charlie-tca> abuDawud: done
[19:14] <Tiibiidii> a last question... this one is a little bit controversial... about meta-bugs
[19:14] <Tiibiidii> do you use evolution?
[19:15] <charlie-tca> I do not use evolution.
[19:15] <Tiibiidii> because i often chose to use thunderbird instead
[19:15] <Tiibiidii> ok
[19:15] <Tiibiidii> then i tried again to use it
[19:15] <Tiibiidii> for the usual reason:
[19:15] <Tiibiidii> dogfeeding
[19:15] <charlie-tca> I have not used it for 2 or 3 or 4 years
[19:15] <abuDawud> thanks charlie-tca, learnin as I go here. More mistakes to come most likely...
[19:15] <Tiibiidii> (i mean... if i want to measure how ubuntu is improving, and to report bug, and etc.)
[19:16] <charlie-tca> Great! Keep on, improvements usually come from mistakes.
[19:16] <Tiibiidii> (i have to keep using evolution...) it has the plus that's better integrated in the system
[19:16] <Tiibiidii> but, as i think you could agree, it has quite a lot of defects
[19:16] <Tiibiidii> and i've seen this "not using evolution" as a common trend among the ubuntu contributors
[19:17] <Tiibiidii> so i was thinking
[19:17] <Tiibiidii> this is a bug... but not actually...
[19:17] <Tiibiidii> i mean: it's a problem, but it doesn't have a single and easily identificable cause
[19:17] <charlie-tca> Evolution is a great email package for those who need all the things offered by it. For many of us, it is really overkill for reading email.
[19:18] <Tiibiidii> and the solution could be the improvement of evolution, or the switch of the default mail client... this thing would need a serious proposal and some blueprint
[19:18] <Tiibiidii> yeah, so i was thinking about meta-bugs
[19:18] <yofel> abuDawud: bug 678371 - what's your reasoning for marking that a duplicate?
[19:18] <ubot2> Launchpad bug 678371 in apport (Ubuntu) "apport-gtk speaker test message refers to "Close" button as "OK" (dup-of: 667451)" [Undecided,New] https://launchpad.net/bugs/678371
[19:18] <charlie-tca> Thunderbird was proposed at UDS this time, and will probably be proposed for the 11.10 release
[19:18] <ubot2> Launchpad bug 667451 in apport (Ubuntu) ""ubuntu-bug audio" hangs on speaker test (affects: 3) (dups: 2) (heat: 153)" [Undecided,Fix committed] https://launchpad.net/bugs/667451
[19:18] <Tiibiidii> but the point is... meta-bugs seems that could be quite subjective
[19:19] <charlie-tca> um, maybe I missed something. What is the "meta-bug" in evolution that you are referring to?
[19:19] <Tiibiidii> i mean... the sabdfl reported bug #1, but what is the practical use-case and procedure for reporting a meta-bug (if there is one)
[19:19] <ubot2> Launchpad bug 1 in tilix (and 20 other projects) "Microsoft has a majority market share (affects: 612) (heat: 3026)" [High,New] https://launchpad.net/bugs/1
[19:19] <Tiibiidii> it doesn't exist
[19:19] <Tiibiidii> i was just evaluating the possibility of reporting one
[19:20] <Tiibiidii> and i realized that maybe reporting a meta-bug like this one could be quite controversial (for all the reasons i listed: subjective, huge work, need blueprint, no single cause, etc.etc.)
[19:21] <charlie-tca> TBH, there is no such thing as a meta-bug of that nature. That was done because the distribution was brand new. It provided a purpose before the first release of Ubuntu
[19:21] <Tiibiidii> yeah, but it's not the only one
[19:21] <Tiibiidii> for example
[19:21] <Tiibiidii> (it has been fixed)
[19:21] <Tiibiidii> https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/614742
[19:21] <ubot2> Launchpad bug 614742 in gwibber (Ubuntu Maverick) (and 3 other projects) "[meta] cannot add facebook account, facebook does not update and more (affects: 306) (dups: 76) (heat: 1422)" [Undecided,Fix released]
[19:22] <Tiibiidii> since there were too many gwibber+facebook bugs
[19:22] <Tiibiidii> developers "decided to focus" on this
[19:22] <Tiibiidii> as well, evolution is a program with A LOT of bugs reported
[19:23] <charlie-tca> Most bugs marked as a meta bug will be there because it gives a master bug for the developers to work with. It allows them to combine all the suggestions without losing the original issues
[19:23] <charlie-tca> If they do not concern a single idea, they will not be combined into a single bug.
[19:23] <greg-g> Tiibiidii: meta bugs come after many specific bugs and group them together per the discretion of the developers of the application
[19:23] <Tiibiidii> that's why i was thinking about it... but maybe metabugs of this kind are better left to the ubuntu developers themselves to report for
[19:26] <Tiibiidii> ok, so...
[19:26] <Tiibiidii> (i realize that now this issue has been brought to attention during the uds)
[19:27] <Tiibiidii> but, in a similar case... if the number of bugs grows this huge https://bugs.launchpad.net/ubuntu/+source/evolution
[19:28] <charlie-tca> Do they all concern the same issue ( the gwibber bug was 'facebook' specific) ?
[19:28] <Tiibiidii> there isn't a standard way for someone to warn that things are not as optimal....
[19:28] <charlie-tca> all applications have bugs, if they don't, they usually stagnate and disappear, since they are never improved.
[19:28] <Tiibiidii> no, not exactly... but there a lot of segmentation fault for example
[19:28] <Tiibiidii> https://bugs.launchpad.net/ubuntu/+source/evolution?field.searchtext=sigsegv&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
[19:29] <Tiibiidii> (whoops, sorry for the ugly url)
[19:29] <Tiibiidii> i mean: i think it's a general problem of quality for evolution
[19:29] <charlie-tca> the segmentation fault can be caused by many different things, which require many different fixes
[19:29] <yofel> blame launchpad for adding redundant information to the URL :(
[19:29] <Tiibiidii> having this many bugs uncared is not a good thing
[19:30] <Tiibiidii> <Tiibiidii> having this many bugs uncared is not a good thing <-- again, i'm not complaining for the lack of work-force...
[19:30] <charlie-tca> I see a few in new status, but it looks most of them are cared about. They are not sitting in new status, they are instead looked at
[19:31] <charlie-tca> If you care that much, instead of taking all this time and effort to complain, start triaging them. Or better yet, fixing them.
[19:32] <charlie-tca> How many could you have triaged in the last 45 minutes?
[19:33] <Tiibiidii> you're right... i worry too much about these things
[19:34] <Tiibiidii> but i think that i wouldn't be able to make such a difference as you imply with this mere 40 minutes
[19:36] <abuDawud> tiibiidii, if everyone had that mindset nothing would ever get done, right?
[19:40] <Tiibiidii> eh, you're right too... however thank you for answering... at least now i have done this little reality check about how to work with bugs
[19:41] <charlie-tca> probably see a lot more difference than just talking
[19:50] <yofel> abuDawud: ping? (apport bug)
[19:59] <abuDawud> yofel, sorry whats up?
[20:00] <yofel> abuDawud: why did you mark bug 678371 as a duplicate?
[20:00] <ubot2> Launchpad bug 678371 in apport (Ubuntu) "apport-gtk speaker test message refers to "Close" button as "OK" (dup-of: 667451)" [Undecided,New] https://launchpad.net/bugs/678371
[20:00] <ubot2> Launchpad bug 667451 in apport (Ubuntu) ""ubuntu-bug audio" hangs on speaker test (affects: 3) (dups: 2) (heat: 153)" [Undecided,Fix committed] https://launchpad.net/bugs/667451
[20:01] <abuDawud> the cancel message bug is in that other bug
[20:02] <abuDawud> there was another exact dupe of 678371 marked as a duplicate of it
[20:02] <yofel> yes, the cancel message bug, but here he's talking about 'Close' being used instead of 'OK', not about Cancel hanging
[20:04] <yofel> ok, I mixed something up (looked at bug 678360)  - he's indeed talking about both issues in 667451, which is wrong since we never track more than one issue per bug
[20:04] <abuDawud> oh dammit. I was cleaning duplicates of that cancel hanging issue and wrapped that feature request in
[20:04] <ubot2> Launchpad bug 678360 in apport (Ubuntu) "apport-gtk hangs when cancel button is clicked during audio test tone (dup-of: 667451)" [Undecided,Confirmed] https://launchpad.net/bugs/678360
[20:04] <ubot2> Launchpad bug 667451 in apport (Ubuntu) ""ubuntu-bug audio" hangs on speaker test (affects: 3) (dups: 2) (heat: 153)" [Undecided,Fix committed] https://launchpad.net/bugs/667451
[20:05] <abuDawud> whats the proper process to break a bug in two?
[20:06] <yofel> I would undupe 678371 and 678360 and mark 667451 as a dup of 678360 - that has steps to reproduce and we get the issues properly seperated
[20:07] <abuDawud> mark an older report a dupe of a newer bug? Isn't that counter intuitive?
[20:08] <yofel> actually wait - I'm tired (the date it was reported doesn't matter, the amount of information does) the other one is already marked fix committed so it's better not to touch it
[20:10] <yofel> abuDawud: undupe 678371 and post a comment on 667451 that the 'close' issue is tracked there
[20:10] <abuDawud> yofel, thanks for the note regarding report order not mattering, i'll discard that thought process
[20:10] <abuDawud> i'll do that.
[20:10] <abuDawud> thanks for correcting me
[20:10] <yofel> thanks for helping ;)
[20:20] <abuDawud> yofel, can you mark 678371 as triaged for me?
[20:22] <yofel> abuDawud: sure, Importance? (https://wiki.ubuntu.com/Bugs/Importance)
[20:22] <abuDawud> low, correct?
[20:22] <yofel> ack
[20:23] <yofel> abuDawud: done
[20:23] <abuDawud> ty sir.
[21:01] <BUGabundo> o/
[21:29] <Awsoonn> hi all, what package is the network proxy config tool in?
[21:54] <hggdh> Awsoonn: if you know the binary name, you can search by 'dpkg -S <binary>', or 'apt-file search <binary>'
[21:57] <charlie-tca> Hello, hggdh. been hiding, huh?
[21:57] <hggdh> charlie-tca: hey
[21:57] <hggdh> just a bit, just a bit ;-)
[21:58] <charlie-tca> It's okay. Hiding sometimes is good for a person
[22:00] <hggdh> but I have been discovered now...