[00:00] <Odd-rationale> But i remember in the video, he said that hibernate/suspend goes under acpi...
[00:06] <pwnguin> all roads lead to matthew garrett
[00:07] <emma> pwnguin: What are your thoughts about this one -- https://bugs.launchpad.net/ubuntu/+bug/153665
[00:08] <pwnguin> i love the "bumps"
[00:08] <pwnguin> thank you ubuntu forums, i love stupid pings
[00:08] <emma> heh.
[00:09] <mrooney> howdy everyone, what an active channel today
[00:09] <emma> What package does that one belong with, or is that a 'do you still have this problem in a newer Ubuntu?'
[00:09] <emma> mrooney: it's the GBJ maybe that's why.
[00:09] <pwnguin> its probably gnome-panel or somethnig else
[00:09] <emma> I was thinking gnome pannel or metacity
[00:10] <pwnguin> not metacity
[00:10] <mrooney> I would imagine gnome-panel
[00:10] <mrooney> unless there is a more specific package for the applets, but not that I know of
[00:10] <pwnguin> or perhaps the app that closed it
[00:11] <Odd-rationale> maybe he just locked it to the panel.
[00:12] <emma> gnome-pannel is not a source package.
[00:12] <emma> oops typo
[00:13] <mrooney> emma: I would mark it against gnome-panel and Incomplete it, asking if it still occurs and in which distribution and version of gnome-panel (apt-cache policy gnome-panel)
[00:14] <hggdh> I would say gnome-panel indeed
[00:15] <emma> Thanks!
[00:16] <emma> Can you guys tell me what is it about it that tells you 'gnome-panel' ?
[00:16] <Odd-rationale> the notification tray is part of gnome-panel i beleive...
[00:17] <Odd-rationale> Is it ok to simply suggest to the reported to file upstream? or do I actually have to go do it?
[00:18] <Odd-rationale> s/reported/reporter
[00:18] <mrooney> Odd-rationale: no, a reporter rarely even would know what you mean by that :)
[00:18] <Odd-rationale> mrooney: so i have to actually do it?
[00:18] <mrooney> emma: right, it is a gnome-panel applet
[00:19] <emma> Okay great. Thanks very much. I think helping with bugs might help me learn more deeply about Ubuntu.
[00:19] <mrooney> emma: you definitely will, and learn about all sorts of applications and commands you never knew existed!
[00:19] <mrooney> Odd-rationale: you don't HAVE to, you can leave it for another triager, and can suggest in the comments that it should be
[00:19] <emma> That's fantastic. :)
[00:20] <Odd-rationale> ok. thanks
[00:20] <Odd-rationale> i would hate to create an account in like 5 different bug trackers..
[00:20] <mrooney> Odd-rationale: but it isn't, IMO, reporters responsibility to file upstream, they are using Ubuntu, and that's part of our "job"
[00:20] <mrooney> Odd-rationale: which bug is this, specifically?
[00:21] <mrooney> pretty much all of gnome uses the same one so it isn't really that bad.
[00:21] <Odd-rationale> https://bugs.launchpad.net/ubuntu/+bug/230652
[00:21] <Odd-rationale> it is kde
[00:21] <Odd-rationale> kde4 for that matter
[00:21] <pwnguin> mrooney: what should i do when upstream basically ignores launchpad?
[00:21] <pwnguin> (we can take this to PM if you don't want to spam the channel)
[00:22] <mrooney> pwnguin: hmm, what do you mean by ignores? it isn't really an upstream projects job to worry about Ubuntu, usually
[00:23] <Odd-rationale> i think he has the wrong settings...
[00:23] <Odd-rationale> and there are quite a lot of settings for a single app in kde...
[00:23] <mrooney> pwnguin: so you mean a bug reported upstream that the project doesn't care about fixing? in that case we can patch it on our package and give it to them, though that is less than optimal
[00:24] <yuriy> Odd-rationale: it's OK to suggest, but then somebody else has to do the work, so it would be great if you'd actually do it
[00:24] <emma> What if we find a bug report where it appears that someone has solved the problem in one of the comments?
[00:24] <Odd-rationale> :(
[00:24] <pwnguin> mrooney: say someone reports a wacom bug in ubuntu, and I'm pretty sure it's upstream's fault, but I can't reproduce it
[00:24] <yuriy> Odd-rationale: it's part of the process of triaging...
[00:25] <Odd-rationale> ok. Thanks!
[00:25] <yuriy> Odd-rationale: and of course, provide the appropriate cross linking
[00:25] <mrooney> Odd-rationale: but if you don't want to get into that yet, you can just not triage those bugs to begin with. I started by just subscribing to bug reports to learn what other people did with them
[00:25] <emma> mrooney: now there's a good idea.
[00:25] <mrooney> emma: well, it depends if it was actually a bug or not. did someone come up with a workaround for it?
[00:26] <pwnguin> https://sourceforge.net/tracker/?func=detail&atid=525124&aid=2030106&group_id=69596
[00:26] <pwnguin> actually, wrong bug
[00:26] <emma> mrooney: I'm also thinking, after this GBJ is over maybe I will just concentrate on a couple of packages I know more about or have an interest in.
[00:26] <yuriy> Odd-rationale: however, I think that bug could be helped with a screenshot and maybe some settings that he has set...
[00:26] <pwnguin> https://sourceforge.net/tracker/?func=detail&atid=525124&aid=1987565&group_id=69596
[00:27] <emma> mrooney: I think it looks like it was not a bug but more of a need to know how to configure x-org. https://bugs.launchpad.net/ubuntu/+bug/152214
[00:27] <yuriy> Odd-rationale: and of course mark it against the right package (kdebase)
[00:27] <Odd-rationale> yuriy: i would look through the settings if i had kate. But i don't use kde, much less kde4...
[00:27] <mrooney> emma: yeah, I would recommend when you find incoming bugs (say from the RSS or #ubuntu-bugs-announce) that seem interesting to you, just subscribe to them, I do that with 2-3 every day, and you will get the emails of what happens and see it triaged and ideally eventually fixed
[00:29] <yuriy> Odd-rationale: also, often you don't have to file anything upstream, just search
[00:29] <yuriy> Odd-rationale: in this case, searching for "kate word wrap" at bugs.kde.org turns up dozens of reports
[00:29] <Odd-rationale> yuriy: oh, i didn;t think of that...
[00:30] <yuriy> Odd-rationale: and don't forget to search launchpad for duplicates as well when you work on bugs. same idea.
[00:30] <emma> yuriy: what is that about? If you find a duplicate bug what are you supposed to do with the two bugs?
[00:31] <Odd-rationale> report one as duplicate
[00:31] <greg-g> you mark one as a duplicate of the other.  making the one with more information the master
[00:31] <mrooney> emma: you mark the new one as a duplicate of the other, and leave in a comment in the duplicate bug thanking them for the report, saying it has already been filed, and asking them to read the duplicate for possible workarounds, and add any new information
[00:31] <yuriy> emma: pick the one that's a better report (clearer, more information) then mark the other one as a duplicate of it (there is a link for that)
[00:31] <Odd-rationale> https://wiki.ubuntu.com/Bugs/MarkingDuplicate
[00:31] <yuriy> and leave an appropriate comment
[00:31] <emma> okay great.
[00:31] <greg-g> heh, and have 4 people provide duplicate answers to the question ;)
[00:31] <mrooney> :)
[00:32] <mrooney> emma: also, with that report you linked, it depends on if the conf file is actually "misconfigured"
[00:32] <Odd-rationale> The master one is the one you type the number of? or ther other way around?
[00:32] <pwnguin> greg-g: hey, more eyes is better
[00:32] <greg-g> pwnguin: yep
[00:32] <mrooney> Odd-rationale: the first, you type in the master bug #
[00:32] <emma> mrooney: yes, perhaps I should ask if the person's problem has been resolved and mark it as incomplete?
[00:33] <mrooney> emma: sure, you want to find out if it previously worked, say in a previous version of Ubuntu, which would make it a regression and a bug
[00:33] <mrooney> if it has never worked out of the box, that would be a 'wishlist' importance bug, I would say
[00:34] <mrooney> emma: a crucial thing though, when marking things as incomplete (or making any change, I would say) is to subscribe to the bug so when the person provides more information you can change the status appropriately, otherwise it could stay in incomplete!
[00:35] <yuriy> Odd-rationale: report fix'd
[00:36] <Odd-rationale> to that kate bug?
[00:36] <Odd-rationale> yuriy: ^
[00:37] <yuriy> Odd-rationale: yeah, it was already fixed, but I did all the stuff anyway (add upstream link since I'd already found it anyway, set right package, set status to fixed, set importance to wishlist, thank the reporter)
[00:37] <Odd-rationale> k thanks a lot!
[00:37] <yuriy> s/wishlist/low
[00:37] <emma> mrooney: Okay, I was under the impression that if something is marked as incomplete then it eventually is deleted ?
[00:38] <mrooney> emma: well, it is "expired", after 60 days of no response
[00:38] <emma> Is that for all bug reports or just ones marked incomplete?
[00:38] <mrooney> which makes sense, if you need more information and the reporter hasn't gotten back to you in two months, those aren't useful bugs for developers/triagers to look at, there is nothing to be done with them
[00:38] <mrooney> just Incomplete!
[00:39] <nellery> emma, you should look at https://wiki.ubuntu.com/Bugs/Status
[00:42] <emma> Invalid:
[00:42] <emma> * This status should be used when the bug report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter
[00:42] <emma> Doesn't this constitute a criterion by which we could mark almost all of these as invalid and be done with it? :)
[00:43] <mrooney> yes that wording does seem sub-optimal
[00:43] <mrooney> Invalid is used when the behavior is not actually a bug, essentially
[00:44] <emma> I know I was being ironic. :)
[00:44] <mrooney> yes, it would save us some time :)
[00:44] <mrooney> I'll just make a script to mark all incoming bugs as Invalid and we can go do other things :)
[00:45] <pwnguin> like complain about how ubuntu sucks and crashes on us, and totally lost that term paper
[00:46] <mrooney> haha yeah, everyone definitely will come across a really angry, obnoxious report every once and awhile
[00:47] <pwnguin> heh, the only one i came across was an upstream developer
[00:47] <mrooney> I really want to keep a "best of" bug list, but I worry about offending the reporters :)
[00:47] <pwnguin> how dare we ship xournal when there's a point release avalable days after freeze
[00:48] <mrooney> haha you should look at the X-Fi bug
[00:48] <pwnguin> i think i'll pass
[00:48] <mrooney> an untested alpha driver came out 2 days before Hardy final and someone was pretty upset we weren't shipping it
[00:49] <daradib> I think this bug should have wishlist status: https://bugs.launchpad.net/wesnoth/+bug/256345
[00:49] <_stink_> i'm getting a bunch of errors from the command line 5-a-day app when trying to add a bug... any advice? http://paste.ubuntu.com/36028/
[00:51] <pwnguin> im always amused when volunteers are short on time
[00:51] <Odd-rationale> _stink_: did you upload your ssh keys ro launchpad?
[00:51] <daradib> pwnguin: i don't get it
[00:51] <Odd-rationale> s/ro/to
[00:52] <pwnguin> daradib: the global bug jam is on; you're short on time but participating anyways?
[00:52] <_stink_> Odd-rationale: i did - they're shown at https://launchpad.net/~adamjlincoln
[00:52] <daradib> pwnguin: i am working regardless of jam
[00:53] <pwnguin> daradib: ok then
[00:53] <daradib> there is no jams close to me
[00:53] <daradib> are*
[00:54] <emma> This person seems to have fixed their own problem -- https://bugs.launchpad.net/ubuntu/+bug/154809
[00:55] <Odd-rationale> _stink_: you have 2 keys uploaded?
[00:56] <_stink_> Odd-rationale: i had one for a while that worked fine as far as I could tell. earlier today when i ran into this problem, i added the second hoping it would help.  it didn't - i get the same error
[00:56] <_stink_> they were generated on two different machines
[00:56] <_stink_> each of which i now get the same error on
[00:57] <Odd-rationale> well thr first line says "Permission denied (publickey)."
[00:57] <Odd-rationale> so i think it has somthing to do with that...
[00:57] <greg-g> it is ok having more than one key, I do and 5-a-day works
[00:57] <Odd-rationale> maybe try over again>
[00:57] <Odd-rationale> ?
[00:57] <greg-g> he has ;)
[00:58] <_stink_> i know, which is strange. i assumed the line after that about concurrent connections was the error assocatied with the failed connection
[00:58] <Odd-rationale> yeah i know more than one key is ok
[00:58] <_stink_> but if no one else is getting this, then there must not be a limit problem
[00:59] <mrooney> emma: so in that case, if they fixed it themselves and it was their own fault, a misconfigured file or something, then you can just thank them for the report and mark it Invalid, but in this case it seems like it is potentially a legitimate bug
[00:59] <_stink_> maybe I'll just file a bug on it :)
[00:59] <Odd-rationale> _stink_: maybe you have more than one running
[00:59] <mrooney> it is sort of disturbing that all that work took place out of launchpad
[00:59] <_stink_> Odd-rationale: more than one... one what?
[01:00] <Odd-rationale> or more than one bzr connections running...
[01:00] <_stink_> i don't have the applet going, just using the command line
[01:00] <emma> mrooney: how so?
[01:01] <mrooney> emma: well there is a lot of information in that forum thread, you could try to figure out the relevant stuff and leave it in a comment
[01:01] <mrooney> emma: I think you are picking hard bugs :)
[01:03] <emma> I'm trying to find good ones.
[01:03] <mrooney> if you are new to triaging you probably don't want to look at old bugs since every one else passed them up already, if they were easy they are already triaged probably
[01:03] <emma> True.
[01:03] <emma> I'm looking at the list of ones without a package and trying to put them with the package.
[01:03] <mrooney> I would recommend looking at incoming bug reports and subscribing to ones you want to know more about
[01:03] <mrooney> yeah, that is a worthy effort
[01:03] <emma> Okay.
[01:04] <emma> Yes I'm going to do that, but I'm trying to do stuff for the GBJ today and tomorrow.
[01:04] <mrooney> still you may want to focus your efforts on newer ones and not the ones no one else knew where to assign either :)
[01:05] <greg-g> heh
[01:05] <mrooney> although certainly finding old ones and asking is a great way to learn, and get attention to old bugs that maybe fell through the cracks
[01:05] <mrooney> emma: so, I guess you can't go wrong, in conclusion :)
[01:05] <daradib> Could someone please mark Bug 256345 as wishlist status (or low)?
[01:06] <emma> :)
[01:06] <greg-g> heh, is that a "this game is hard" bug?
[01:06] <emma> You have a good style mrooney :)
[01:06] <pwnguin> greg-g: no, its a "this game should work" bug
[01:06] <pwnguin> what it really needs is a low and a forward to upstream
[01:07] <greg-g> yeah, looks like it
[01:07] <greg-g> I'll set it to low, you wanna take care of forwarding?
[01:07] <pwnguin> not really =/
[01:07] <greg-g> :) me neither
[01:07] <pwnguin> if it means i might meet esr, i'll pass
[01:08] <Odd-rationale> the wesnoth server is not working very well right now anyways...
[01:08] <greg-g> what? esr is a dev for wesnoth?
[01:08] <Odd-rationale> his name appears in the credits...
[01:09] <greg-g> ah
[01:09] <pwnguin> yes, he is
[01:09] <pwnguin> check ohloh on wesnoth
[01:11] <mrooney> emma: thanks :) by the way, if you are focusing on bugs without a package, bdmurray has a great stock response for that
[01:11] <mrooney> if I can find it...
[01:15] <emma> What package is involved with system > shutdown ?
[01:15] <mrooney> emma: anyway it is something like "Thanks for your bug report. This bug was filed without a package specified, which is important for getting it looked at by the right people. I have marked this as a bug against PACKAGENAME. See https://wiki.ubuntu.com/Bugs/FindRightPackage for more information."
[01:16] <hggdh> a colleciton of stock responses is at https://wiki.ubuntu.com/Bugs/Responses
[01:16] <hggdh> s/colleciton/collection/
[01:16] <mrooney> hggdh: ooh, I wasn't so far off :)
[01:16] <mrooney> emma: good question about that package
[01:17] <hggdh> you were good, mrooney... I just thought the collection could help
[01:17] <mrooney> hggdh: no I appreciate it, that's what I was hoping someone would provide
[01:18] <_stink_> Odd-rationale: filed bug with bzr. thanks for taking a look :)
[01:19] <mrooney> emma: one trick is to search for bugs in ubuntu that would probably be in it, and look at the package, like "gnome logout" or "gnome shutdown" or something
[01:20] <danmulvey> exit
[01:20] <danmulvey> oops
[01:22] <pedro_> emma: gnome-session
[01:24] <emma> mrooney: that's a good idea.
[01:27] <emma> Does every package in Ubuntu have a bug supervisor ?
[01:27] <pwnguin> no, sadly
[01:27] <pwnguin> well, maybe supervisor means something extra special
[01:29] <pwnguin> but if every package had someone paying special attention to it, we could just take the whole unassigned queue, assign it to a random package and let them figure it out ;)
[01:29] <crimsun> except that's what happens
[01:30] <crimsun> the Ubuntu package and ~ubuntu-bugcontrol
[01:30] <pwnguin> well
[01:30] <pwnguin> i didnt mean one specific random package
[01:30] <pwnguin> maybe you didnt either?
[01:31] <emma> Who looks at it then, the motu who packaged the package in the first place?
[01:31] <crimsun> emma: sometimes
[01:32] <crimsun> otherwise you have to assume~motu does
[01:32] <emma> do the motus have developer skills or do they just need packagers skills?
[01:32] <jarosser06> i think bug #256491 should be set to wishlist
[01:32] <crimsun> emma: many of both
[01:32] <mrooney> pwnguin: you theoretically could do that, but all that would happen is they would mark it invalid against their package
[01:32] <pwnguin> heh
[01:32] <emma> crimsun: some of them just have packaging skills ?
[01:32] <hggdh> emma, yes
[01:32] <pwnguin> mrooney: but some fraction of them would be right!
[01:32] <crimsun> emma: sure, but "just" is misleading.
[01:33] <mrooney> pwnguin: haha yeah, just keep cycling around the invalid ones until there aren't any left :)
[01:33] <hggdh> :-)
[01:39] <effie_jayx> jarosser06, I think not
[01:39] <effie_jayx> jarosser06,  there are two references to computer in nautilus
[01:39] <mrooney> emma: by the way another excellent resource is https://wiki.ubuntu.com/Bugs/Checklist
[01:39] <emma> Okay let me read that.
[01:40] <effie_jayx> one is a big buton nexto the the navigation arrows ... anything that would enable it to be more "accesible" would include neon lights with google maps directions on how to find it ;)
[01:45] <jarosser06> alright i wasnt sure how to label it im new sorry
[01:47] <daradib> greg-g: thanks
[01:49] <effie_jayx> jarosser06,  it's cool :D
[01:49] <effie_jayx> jarosser06,  good call on refering to brainstorm :D
[01:50] <jarosser06> Thanks i got it off the Triage tutorial lol, so just curious what would you mark something like that as b/c i totally agree with you the computer button is right there
[01:51] <emma> I seem many people start their bug report with: binary package hint: <packagename> why do they do that and where did they learn to do that? Is there some rubric some place that advises people how to file a report?
[01:52] <snap-l> emma: That's part of the "Report a Problem" link in GNOME
[01:52] <snap-l> It's under 'Help > Report a Problem'
[01:52] <emma> Ahh.
[01:57] <effie_jayx> jarosser06, mark it invalid, if the reported strongly feels he is right... let him reopen it
[01:57] <jarosser06> alright thanks
[01:57] <effie_jayx> but once well argumented it is rarely chanllenged
[02:01] <jarosser06> so do you have any advice for someone just beginning with bugs
[02:04] <effie_jayx> jarosser06,  keep it coming :D
[02:05] <effie_jayx> https://bugs.edge.launchpad.net/ubuntu/+source/cfv/+bug/256500
[02:06] <effie_jayx> is it resonable to change the package to suggest transmission then?
[02:06] <hggdh> jarosser06, read http://wiki.ubuntu.com/HelpingWithBugs
[02:06] <hggdh> its a good start
[02:06] <hggdh> and feel free to ask questions
[02:07] <jarosser06> i read that and How to triage
[02:08] <hggdh> so... keep it simple. Start looking at bugs, and grab one you feel confortable with (or less unconfortable with ;-)
[02:08] <hggdh> and then try to apply what you read
[02:08] <hggdh> if in doubt, ask. We do not bite, most of the time
[02:09] <jarosser06> lol thanks
[02:09] <hggdh> you are welcome, jarosser06. Thank you for helping
[02:09] <jarosser06> i think this is a wishlist item bug # 256476
[02:09] <hggdh> bug 256476
[02:09] <mrooney> jarosser06: did you look at the bug checklist page I sent emma a few minutes earlier? that has some great tips
[02:10] <mrooney> yeah that looks like Triaged/Wishlist at first glance
[02:10] <hggdh> I will set it so
[02:11] <jarosser06> yeah i started looking at it a little i kinda wish i had a printer so i dont have to keep switching screens
[02:12] <hggdh> jarosser06, good catch, thank you
[02:12] <jarosser06> yall are very helpful
[02:12] <hggdh> jarosser06, this is a community effort. Community efforts only work if all work together and help each other
[02:13] <hggdh> jarosser06, just a question: have you registered in launchpad?
[02:13] <jarosser06> yeah its great i have used Ubuntu for about 2 years and i dont think i have ever had a question or problem that i have not been helped with
[02:14] <jarosser06> i try to do the same through the mailing list and thought i might try my hand at bugs now
[02:14] <jarosser06> yes
[02:14] <hggdh> good, then you can add your comments in
[02:14] <hggdh> and we need all help we can get -- lots of bug reports, and not enough bug triagers
[02:15] <hggdh> huh
[02:16] <hggdh> a question, jarosser06: when you said ' yall' you meant 'all yall', or just ' yall' ?  ;-)
[02:16] <jarosser06> all of you
[02:16] <hggdh> ah, all yall
[02:16] <jarosser06> yeah
[02:16] <jarosser06> ill clarify next time
[02:16] <jarosser06> lol
[02:16] <hggdh> pure old texan ;-)
[02:17] <jarosser06> yeah im actually in Huntsville right now going to Sam Houston
[02:18] <jarosser06> i think bug #256478 and bug #256477 are wishlist candidates as well
[02:19] <hggdh> and I am in DFW
[02:20] <jarosser06> what does that stand for
[02:21] <jarosser06> Dallas Fort Worth ?
[02:21] <hggdh> yes
[02:21] <jarosser06> gotcha
[02:21] <jarosser06> ive never been to Dallas
[02:21] <hggdh> another way of saying dallas metroplex
[02:21] <jarosser06> Oh
[02:21] <hggdh> bug 256478 taken care of.
[02:22] <hggdh> bug 256477 will need a bit more of work
[02:22] <hggdh> there is no upstream pointing to it, so we need to find if it has been reported upstream to link
[02:23] <jarosser06> how do you do that
[02:24] <yoda_van> bug #30910 should be set to Wishlist
[02:26] <hggdh> empathy is a gnome application, so it should be described in gnome.org; also, it's native BTS (Bug Tracking System) is http://bugzilla.gnome.org
[02:26] <lifeless> is patricio gonzalez here?
[02:31] <hggdh> yoda_van, why?
[02:32] <hggdh> jarosser06, so you can go to the gnome BTS and search in for a matching bug
[02:33] <yoda_van> it been addressed for awhile now, in brainstorm - just haven't taken action on making the db searchable/readable
[02:33] <hggdh> (this is all part of bug triaging)
[02:33] <yoda_van> its actually broken by design, if you read through the comments
[02:34] <hggdh> I did, and I agree. Still, ogra put it out of in progress to new
[02:34] <hggdh> he could have put it as wishlist
[02:35] <jarosser06> ok so i should look in the gnome db after looking through launchpads if it is related to gnome
[02:35] <hggdh> so I think we should ask him about that
[02:35] <yoda_van> k
[02:36] <yoda_van> let me check and see if ogra is on email list
[02:36] <hggdh> jarosser06, if we could find an upstream bug, or the project plan for it, it would help. It does not really help just to set it wishlist, if upstream (the actual developers) do not get to know about it
[02:37] <jarosser06> ok that makes since
[02:37] <hggdh> (the other two bugs you pointed out had nice upstream bugs already linked
[02:37] <yoda_van> hggdh, ogra is on email list so they will see the request - ty
[02:38] <hggdh> welcome, yoda_van. Thank you for helping
[02:38] <yoda_van> np
[02:38] <yoda_van> this is a blast - albeit tedious
[02:42] <jarosser06> what if you dont see a bug listed in gnomes database
[02:43] <hggdh> it is hard work... usually any hard work is tedious ;-)
[02:43] <jarosser06> yeah
[02:43] <jarosser06> and a little confusing at first
[02:43] <jarosser06> but still pretty fun
[02:43] <hggdh> jarosser06, in this case we would have to check for the empathy project plan
[02:44] <hggdh> the reporter stated it is in line for next**2 or next**3 gnome version
[02:44] <jarosser06> so does that mean the empathy project is already working on it
[02:44] <hggdh> that is what the reporter stated. We need to confirm it
[02:45] <jarosser06> and we need to look in the upstream project plan not the one in launchpad correct
[02:46] <jarosser06> I dont even see empathy under gnomes project listing
[02:47] <jarosser06> nm i found it
[02:48] <hggdh> http://live.gnome.org/Empathy
[02:48] <jarosser06> alright so i see the feature listed for future developement
[02:48] <jarosser06> now do i mark it as confirmed on launchpad
[02:49] <hggdh> yes, you can. Add the link to the roadmap also
[02:49] <jarosser06> when i add the link is there a special way to do that or do i just add it in a comment
[02:50] <jcastro> do they use gnome bugzilla?
[02:50] <jcastro> ah yes
[02:51] <hggdh> :-)
[02:51] <hggdh> jarosser06, since it is the roadmap, just as a comment. You edit the description to add it there also
[02:52] <hggdh> these 3 bugs, in fact, will have no immediate use... but they were opened, so we need to deal with them
[02:53] <jcastro> jarosser06: with empathy being proposed for the desktop if would be awesome if you could help be the link between launchpad and the upstream bug tracker
[02:53] <effie_jayx> bug #255019 should be marked as wishlist
[02:53] <hggdh> jcastro, good idea
[02:54] <jarosser06> yeah this is actually cooler than seeing my architectural drawings being built
[02:54] <jarosser06> lol
[02:54] <jarosser06> alright i added a comment and updated the description
[02:55] <jarosser06> so how did i do
[02:55] <jarosser06> lol
[02:55] <jcastro> jarosser06: ah, don't people to post on brainstorm for that!
[02:55] <mrooney> hey, can anyone confirm or deny that visiting yodlee.com with javascript enabled crashes firefox?
[02:55] <jarosser06> huh
[02:56] <jarosser06> it opened fine for me
[02:56] <jcastro> jarosser06: you told one guy to post his bug on brainstorm, they'll just tell him to post it on launchpad.
[02:56] <jcastro> hggdh: wow, nearly every bug is linked to upstream.
[02:56] <hggdh> jarosser06, very good. I set it to triaged now
[02:57] <jarosser06> sweet
[02:57] <jcastro> this makes me a happy camper
[02:57] <hggdh> jcastro, which bugs?
[02:57] <jcastro> empathy bugs
[02:57] <hggdh> thanks to jarosser06, actually
[02:57] <jcastro> all 6 of them. :)
[02:57] <hggdh> LOL
[02:57] <jarosser06> i only delt with like one lol
[02:57] <jcastro> if we can keep that up it would be really fantastic
[02:58] <hggdh> jarosser06, I do not use firefox
[02:58] <hggdh> jcastro, I agree
[02:59] <jcastro> I'll blog about this, since I suspect more bugs will be incoming
[02:59] <jcastro> this is inspirational.
[02:59] <hggdh> thanks, jcastro. As you very well know, all help is appreciated.
[03:00] <hggdh> jarosser06, you picked 3 of them up
[03:00] <mrooney> can anyone else try yodlee.com, I disabled all extensions and still get a segfault
[03:00] <jarosser06> oh yeah but i only did the upstream stuff for one
[03:00] <hggdh> OK, I changed two of them, but because you raised the issue
[03:01] <jcastro> jarosser06: determining if something is upstream by bringing it up still counts!
[03:01] <hggdh> absolutely correct
[03:03] <mrooney> jarosser06: do you have flash installed?
[03:03] <jarosser06> would bug #256507 be considered a wishlist bug as well
[03:03] <jarosser06> yes i do
[03:03] <jarosser06> mrooney, yes i do along with java should i disable them
[03:03] <jarosser06> and try a gain
[03:03] <jarosser06> again*
[03:03] <mrooney> nope, I just wanted to make sure you had everything enabled that I did
[03:03] <mrooney> thanks for testing
[03:03] <hggdh> jarosser06, no, this is a workflow bug. Bugsquad does not deal with workflow bugs.
[03:04] <anakron> Happy Global Bug Jam
[03:04] <anakron> Hi all
[03:04] <anakron> hi rooney
[03:04] <jarosser06> ok i am on a 64 bit Ubuntu if that makes a difference
[03:04] <jarosser06> ok
[03:06] <hggdh> jarosser06, see https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs
[03:25] <anakron>  Hi all
[03:31] <jarosser06> i found a bug about firefox not saving bookmarks and i found a duplicate but the duplicate states some other problems as well so is it still a duplicate
[03:32] <jarosser06> ?
[03:33] <hggdh> hi anakron
[03:33] <anakron> :O
[03:33] <anakron> Hi hggdh...
[03:33] <hggdh> jarosser06, it is one issue per bug
[03:34] <hggdh> so a bug with more than one issue has to be split
[03:34] <hggdh> by the reporter
[03:34] <jarosser06> oh well it seemed that the issue was resolved in fact the only mention of other problems was in the heading itself
[03:35] <hggdh> so it is not really a duplicate?
[03:35] <jarosser06> i think it is they both have the same problem, the firefox bookmarks are not saved after firefox is shutdown
[03:36] <jarosser06> its bug#256512 and the duplicate is bug #224985
[03:37] <hggdh> bug 256512
[03:40] <hggdh> jarosser06, although it sounds the same, the descriptions of the error are different
[03:41] <jarosser06_> sorry i got booted
[03:41] <hggdh> ah. they do not seems to be the same issue
[03:42] <jarosser06_> ok
[03:42] <hggdh> for bug 256512 you might ask the reporter to run firefox from a terminal, then save the output and attach to the bug
[03:45] <jarosser06_> alright so mark it as incomplete
[03:45] <hggdh> yes
[03:47] <jarosser06_> done thanks
[03:52] <anakron> Hi all
[03:53] <anakron> https://bugs.launchpad.net/ubuntu/+source/purple-plugin-pack/+bug/256419  >> Must be in Wishlist!
[03:53] <anakron> Thanks you
[03:54] <Awsoonn> GBJ is rocking!
[03:54] <Awsoonn> 1880 bugs left w/o a package? not bad!
[03:55] <anakron> Hi Awsoonn
[03:55] <anakron> https://bugs.launchpad.net/ubuntu/+bug/256513 >> Must be in Wishlist
[03:55] <anakron> how i can show you packages that must be in wishlist?
[03:55] <anakron> https://bugs.launchpad.net/ubuntu/+bug/256513 >> Must be in Wishlist
[03:55] <anakron> its a good way?
[03:55] <emma> Yes these stats are pretty cool --- http://daniel.holba.ch/5-a-day-stats/
[03:55] <emma> Especially the Team and Tags
[03:59] <Hobbsee> oh dear.  i've almost fallen off the top contributors ever.
[04:02] <Hobbsee> anakron: yes, you can.  but you could find something actually useful to do.
[04:02] <anakron> ok
[04:03] <anakron> so, its a package that enabled pidgin to work with facebook and...lots of people will be happy with this integration
[04:03] <Hobbsee> i'm sure they would.
[04:03] <emma> anakron: But I think people are grateful for what you do here.
[04:03] <Hobbsee> however, one of the primary aims of the bugsquad is to find actual bugs, and to get them to a useful enough state that people can actually fix them.
[04:04] <anakron> ok
[04:04] <anakron> yeah i know
[04:04] <anakron> and im working with real bugs there, in LP
[04:04] <Hobbsee> and while it's helpful from a splitting bugs perspective, it's a much better use of your time to fulfil the primary aim.
[04:04] <anakron> but there are some bugs that are called wishlist
[04:05] <anakron> i only report it here and then, people that can do it, could choose if its necessary or not
[04:05] <Hobbsee> there are.
[04:06] <Hobbsee> okay..
[04:06] <anakron> :-) sorry
[04:06] <hggdh> anakron, actually bug 256419 sounds more like a workflow bug
[04:07] <anakron> ok
[04:07] <anakron> thanks
[04:07] <hggdh> bugsquad does not deal with workflow bugs. Please see https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs
[04:07] <anakron> thanks all
[04:08] <Hobbsee> hggdh: that could do with being filed in debian.
[04:08] <Hobbsee> or linked, if there's a debian one open
[04:09] <hggdh> Hobbsee, yes, but... you know the story... I tend to stay clear of potential workflow bugs
[04:09] <Hobbsee> hggdh: fair enough, but there's no one touching on it, so you coudl deal with that one.
[04:09] <Hobbsee> there's no commitment for someone to actually work on the bug.
[04:10] <Hobbsee> oh, debian BTS has changed.  interesting.
[04:10] <hggdh> but same place?
[04:10] <hggdh> yes.
[04:10] <Hobbsee> sorry?
[04:11]  * Hobbsee adds the debian bug
[04:11] <hggdh> I was still trying to open the link to debian bugs
[04:11] <hggdh> oh, you did it already
[04:11] <Hobbsee> yeah, sorry :)
[04:11] <hggdh> :-)
[04:11] <hggdh> no prob, Hobbsee
[04:13] <hggdh> anyway, the comment in the bug was not warranted
[04:13] <Hobbsee> yeah, i know.
[04:13] <Hobbsee> this is one fo the problems with the bugsquad - they don't seem to use their brains, or just arne't taught what is useful or not, and rely too much on predefined responses.
[04:14] <hggdh> well, in this case, actually, no reading of wiki
[04:14] <hggdh> Hobbsee, what is a "brain"? ;-)
[04:14] <Hobbsee> hahahaha
[04:15] <hggdh> the empty space behind my eyes, methinks
[04:15] <Hobbsee> ahhh
[04:51] <emma> What is the definition of a workflow bug?
[04:59] <Hobbsee> emma: https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs
[05:00] <emma> Thank you Hobbsee
[05:02] <Hobbsee> you're welcome.
[05:13] <emgent> moin LaserJock :)
[05:13] <techno_freak> morning all
[05:13] <emgent> LaserJock: i have a bad news for you
[05:13] <LaserJock> hi emgent
[05:13] <LaserJock> emgent: oh?
[05:13] <emgent> new bind is already vulnerable to cache poissoning
[05:14] <LaserJock> wonderful :/
[05:14] <emgent> http://tservice.net.ru/~s0mbre/blog/devel/networking/dns/2008_08_08.html
[05:21] <jarosser06_> does anyone have amsn on their system
[05:29] <nellery> jarosser06_, are you having a problem logging in?
[05:29] <jarosser06_> yeah i installed it to test a bug i found
[05:30] <jarosser06_> and it would not let me on pretty much as it was reported
[05:30] <jarosser06_> and i noticed that if i run it through the terminal it doesnt give me any sort of messages
[05:31] <jarosser06_> so i was wondering if anyone else has had this problem and if anyone knows how to get an error message out of it
[05:31] <jarosser06_> do you have it on your computer hellery
[05:32] <nellery> jarosser06_, no, sorry
[05:32] <jarosser06_> nellery*
[05:32] <jarosser06_> oh would you know how to get an error message out of it
[05:32] <nellery> are you referring to Bug 137048
[05:32] <jarosser06_> no its bug 256516
[05:33] <nellery> ah
[05:33] <nellery> them I'm clueless :)
[05:34] <jarosser06_> they do seem very similar the only difference is the version
[05:34] <jarosser06_> thanks for the try
[05:35] <jarosser06_> im pretty new at this stuff
[05:46] <jarosser06_> could bug #256522 be closed as it doesnt actually appear to be a bug
[05:47] <nellery> jarosser06_, that should be converted into a question
[05:47] <Hobbsee> jarosser06_: i'd turn that into a question
[05:47] <Hobbsee> bah.
[05:47] <nellery> hehe
[05:47] <nellery> jarosser06_, see https://wiki.ubuntu.com/Bugs/ConvertToQuestion
[05:48] <nellery> I just created that yesterday :D
[05:48] <jarosser06_> thanks
[05:49] <Hobbsee> neat!
[05:49] <nellery> jarosser06_, if you find that it is troublesome to follow, then that was my intention :)
[05:49] <jarosser06_> lol
[05:50] <nellery> hehe, just kidding
[05:50] <jarosser06_> i got it, took me a minute to find the button though lol
[05:50] <nellery> could the screenshot be improved?
[05:51] <jarosser06_> um you might make it just a little bigger or something i just kinda glanced at it and wasnt sure at first what it was
[05:51] <jarosser06_> actually i think its fine im just running on half a brain lol
[05:52] <nellery> I was trying to keep it small to keep the table smaller
[05:52] <nellery> but I think I will expand it a bit
[05:53] <nellery> make it a little more obvious
[05:53] <jarosser06_> yeah for people like me lol that cant catch the obvious
[06:00] <jarosser06_> i think bug 256520 should be marked wishlist
[06:01] <nellery> jarosser06_, that's really an upstream thing
[06:02] <nellery> you should report this upstream here: http://bugs.winehq.org/
[06:02] <nellery> then set a bug watch using the instructions from https://wiki.ubuntu.com/Bugs/Watches
[06:03] <jarosser06_> alright thanks
[06:03] <nellery> I'll mark the Ubuntu one as wishlist for you
[06:04] <jarosser06_> ok thanks, i need to put the link of the upstream bug reported right?
[06:07] <teKnofreak> Hobbsee, can you look bug 243828 and tell me whether I really need to go for SRU or not. persia asked me to nominate and follow it up yesterday night, but the latest comments from upstream leaves me confused :)
[06:31] <jarosser06_> i think bug #256331 needs to be labeled wish list
[06:33] <tuxmaniac> hello nellery . I wanted to know whether you are working on bug 251281 or I can have a shot at that? I see your comment on that bug. hence thought better to ask.
[06:33] <anakron> Hi all
[06:33] <jarosser06_> howdy
[06:33] <nellery> tuxmaniac, nope, I was just confirming it
[06:33] <nellery> your free to take it
[06:33] <tuxmaniac> nellery: thanks.
[07:11] <anakron> Hi all
[07:11] <Odd-rationale> hi!
[07:16] <tuxmaniac> warp10: hi
[07:16] <warp10> heya tuxmaniac!
[07:45] <cactaur> Hey everyone. If you're triaging a bug and you can confirm it, and if there's something the original reporter didn't mention that you might think should be helpful, should you put that in your comment, or get the original poster to describe it?
[07:45] <Hobbsee> go ahead and add it yourself
[07:45] <cactaur> All right. Thanks.
[07:57] <cactaur> Oh, and another thing I was wondering. How exactly do you triage a wishlist?
[08:13] <cactaur> https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/200780/+editstatus <---- Does this seem like a wishlist entry?
[08:14] <nellery> cactaur, yea it does
[08:14] <nellery> you should forward it upstream
[08:19] <Odd-rationale> what package do bugs that have to do with updating from one version to another? like updating to 8.04 removes hosts in /etc/hosts? update-manager?
[08:21] <Hobbsee> not usually
[08:21] <Hobbsee> it usually belongs to whatever package has done teh change.
[08:23] <Odd-rationale> Hobbsee: so which packages owns /etc/hosts ?
[08:27] <Odd-rationale> anyone else know?
[08:31] <Hobbsee> dpkg -S /etc/hosts?
[08:31] <Odd-rationale> i'm not currently on a debian system...
[08:37] <emma> Odd-rationale: I'm not sure becuase I missed the context here but becareful about bugs that have to do with updates or versions because it may be a workflow bug, which we don't touch.
[08:38] <Odd-rationale> k
[08:38] <emma> workflow bugs are bugs being used by the developers to fasciliate their communication. I have a link, hold on..
[08:38] <emma> https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs
[08:38] <emma> https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs
[08:39] <Odd-rationale> no, this is not one of them...
[08:40] <emma> oh okay
[08:40] <Odd-rationale> emma: do you know what is the output of "dpkg -S /etc/hosts"?
[08:40] <Odd-rationale> i;m not on a debian system atm...
[08:40] <Hobbsee> bah.
[08:41] <Odd-rationale> sorry, i'm just curious...
[08:41] <Hobbsee> dpkg: /etc/hosts not found.
[08:41] <Odd-rationale> oh...
[08:41] <cactaur> Yeah, got that too.
[08:41] <Hobbsee> therefore, it's not in any package, but autocreated somewhere.
[08:41] <Hobbsee> what does packages.ubuntu.com say?  same thing?
[08:42] <Odd-rationale> well, i'm on Arch Linux. and if i query for /etc/hosts, it tells me it is owned by the package "filesystem" which i don't find in ubuntu, but it might give us a hint...
[08:43] <emma> dpkg: /etc/hosts not found.
[08:43] <Odd-rationale> libboost-filesystem1.34.1?
[08:43] <Hobbsee> !search libboost
[08:44] <Hobbsee> ubottu: fail.
[08:44] <Hobbsee> !search libboost-dev
[08:45] <Hobbsee> !info libboost-dev
[08:45] <Hobbsee> Odd-rationale: i *doubt* it's from there
[08:45] <Odd-rationale> yeah, probably not the equivilent of filesystem for arch..
[08:46] <Hobbsee> Odd-rationale: that sounds like a good question to ask in #ubuntu-devel on a weekday.
[08:47] <Hobbsee> (i doubt anyone's there now)
[08:47] <Odd-rationale> Hobbsee: ok.
[08:48] <Odd-rationale> the description of the filsystem package in arch is "Description    : Base filesystem" Is there any package in Ubuntu that installs the base filesystem?
[08:48] <Odd-rationale> Another hint, is that filesystem is the first package to be installed... What is the first package ubuntu installs?
[08:49] <Odd-rationale> could you find out in an apt log or something?
[08:49] <anakron> Hi all
[08:49] <Odd-rationale> hi!
[08:49] <anakron> HI again
[08:50] <Hobbsee> Odd-rationale: pass.  and i'd guess debootstrap, but i doubt that's the answer of what it should be.
[08:50] <Hobbsee> maybe it's squashfs.  or something before that.  i don't remember :(
[08:50] <Odd-rationale> k, thanks for the help!
[08:51] <Hobbsee> that's definetly a question for u-d
[08:51] <anakron> https://bugs.launchpad.net/ubuntu/+source/nasm/+bug/202095 >> Must be in Wishlist
[08:52] <Hobbsee> that's arleady in debian.
[08:52]  * Hobbsee pokes rmadison
[08:52] <anakron> so, must be like a sync?
[08:52] <Hobbsee> anakron: that's already in intrepid.  you can finish that bug off.
[08:52] <anakron> ok
[08:52] <Hobbsee> packages.ubuntu.com would have told you that.
[08:52] <anakron> i cant see it
[08:53] <anakron> Every time when i tried it i cant access to the page
[08:53] <Hobbsee> http://packages.ubuntu.com/search?keywords=nasm&searchon=names&suite=intrepid&section=all ?
[08:53] <anakron> ok thanks
[08:54] <anakron> now i can
[08:54] <anakron> thanks
[08:54] <Hobbsee> otherwise, there's a tool called rmadison
[08:54] <Hobbsee> i think it's in ubuntu-dev-tools.
[08:54] <Hobbsee> you can use that to look up versions in debian and ubuntu.
[08:54] <Hobbsee> (which is quicker)
[08:55] <Hobbsee> anakron: this is the sort of useful triage to do.  While you could just get it marked as wishlist, it's much more useful to check if the version is anywhere else, and get it to a final state.
[08:57] <manishtech> anyone using 8.10 Alpha 3?
[08:57] <anakron> me
[08:58] <Hobbsee> unlikely - they've done updates since then.
[08:58] <manishtech> anakron: Did you experience any problems while shutting down
[08:58] <anakron> no
[08:58] <anakron> which problem have you
[08:58] <manishtech> anakron: When I click on restart, it logs me out and shows the login screen, from there i have to select restart
[08:58] <Hobbsee> manishtech: known bug.
[08:59] <anakron> :O
[08:59] <Hobbsee> it's supposed to get fixed soonish
[08:59] <anakron> yeah!
[08:59] <anakron> i got it
[08:59] <manishtech> Hobbsee: Soon? You mean in next testing release?
[08:59] <manishtech> anakron: You experienced it?
[08:59] <Hobbsee> i think the plan was for after that.
[08:59] <anakron> yes
[08:59] <anakron> all times
[08:59] <Hobbsee> manishtech: everyone's getting that.
[09:00] <manishtech> Hobbsee: Thanks.. I thought only I was experiencing it? Does anyone know the bug #
[09:00] <anakron> someone knows something about netbooks?
[09:00] <anakron> of intel
[09:01] <anakron> forget it
[09:01] <Hobbsee> manishtech: search for it?  i think it's part of gdm, from memory?
[09:01] <manishtech> Hobbsee: Checking
[09:01] <Hobbsee> it certainly does exist.
[09:02] <Hobbsee> manishtech: in fact, it's listed in the release notes, according to google.  http://www.ubuntu.com/testing/intrepid/alpha3
[09:02] <manishtech> Hobbsee: Is it this https://bugs.launchpad.net/gdm/+bug/126797
[09:03] <Hobbsee> don't thikn so
[09:03] <Hobbsee> no
[09:03] <Hobbsee> bug 250506
[09:04] <manishtech> ubottu: Yeah its 250506...
[09:05] <manishtech> ubottu: I am experiencing 250506 exactly and not 126797 though the latter is also confusing to be the same
[09:05] <Hobbsee> !bot
[11:48] <effie_jayx> good morning /afternoon / evening
[11:49] <qense> hello
[12:07] <Hew> anyone know how gvfsd-trash starts? Trying to triage/valgrind for bug #252174
[12:13] <Hew> if I kill it, it respawns. Does someone know what that sounds like? I've checked /etc/init.d as well as sessions, and can't find a mention of gvfs
[12:25] <RAOF> Hew: It's probably started by gvfs itself.   That's pretty new, so I don't know exactly how it determines stuff.
[12:26] <RAOF> Hew: You could always move the real gvfsd-trash executable to gvfsd-trash.real and create a gvfsd-trash script which calls the real executable under valgrind or something.  That'd be worst-case fallback, I think.
[12:26] <Hew> RAOF: Any idea where gvfs is started? I need to find the line that starts gvfsd-trash so that I can change it into a valgrind command
[12:26] <Hew> hmm ok
[12:27] <RAOF> Hew: It's possible that it's started via dbus, but it's also possible that it's started automatically as soon as some gnome/gtk/glib app starts.
[12:27] <RAOF> gvfs is low level stuff; it's going to be started somewhere core.
[12:29] <Hew> init is the parent process, but I can't find it in init.d, and being a novice on this stuff that's where I got stuck
[12:29] <RAOF> init is the parent process of everything :)
[12:29] <Hew> RAOF: I'll give the script idea a try, I should be able to handle that :-)
[12:29] <RAOF> Aha.
[12:29] <RAOF> dpkg --listfiles gvfs
[12:30] <RAOF> Or, dpkg --listfiles gvfs-backends.
[12:30] <Hew> ah good idea. I know it's in gvfs-backends, so I'll have a look at those files
[12:30] <Hew> yep
[12:30] <RAOF> Survey says: /usr/share/gvfs/mounts/trash.mount
[12:31] <RAOF> dpkg is frikkn awesome.
[12:31] <Hew> indeed :-)
[14:09] <techno_freak> persia, am still confused with bug 243828 that I haven't yet nominated for SRU. Can you check the new comments?
[14:12] <persia> techno_freak: I'd suggest avoiding the debate about 1.2.0 vs. 1.2.5.  That said, if the application doesn't start, or doesn't work, or is otherwise nonfunctional, that is a valid reason for SRU.
[14:12] <persia> (or at least *I* think it is, and remember that once being part of SRU policy, but I'm not on any SRU review teams, so may be mistaken)
[14:12] <techno_freak> persia, ok
[14:23] <effie_jayx> can someone reproduce bug #256611
[14:27] <tuxmaniac> Can someone please review bug 255224 and sponsor if found OK. Thanks in Advance
[14:48] <hggdh> morning to all
[14:48] <techno_freak> morning hggdh
[14:49] <jibel> effie_jayx: this is a duplicate of bug #147146 and #256614.
[14:50] <effie_jayx> jibel,  is it?
[14:50] <persia> I don't think those are duplicate, although it may depend on the specific artist generating the additional glyphs.
[14:51] <effie_jayx> jibel, there is no reference to á
[14:51] <jibel> but it's reference to missing glyphs.
[14:52] <jibel> You won't fill a report for every missing glypth, do you ?
[14:52] <jibel> From the changelog : "
[14:52] <jibel> Ubuntu-title currently provides the following Unicode coverage:
[14:52] <jibel> Basic Latin: 93/128 (72.66%)
[14:52] <effie_jayx> jibel, but the bug's name is " Swedish letters åäö (and som more) are absent "
[14:52] <jibel> Latin-1 Supplement: 2/128 (1.56%)
[14:53] <effie_jayx> how is a spanish contributor going to find a spanish related issue with the package in a font that is intended for a sweedish issue
[14:53] <effie_jayx> ?
[14:55] <effie_jayx> jibel,  I understand your point. but how does the definition of that bug relate to the bug I reported
[14:56] <effie_jayx> the title does not relate to the issue and the description.
[14:57] <effie_jayx> jibel,  I think it's the point of the exercise.
[14:58] <jibel> swedish report is about missing glyphs in the font, spanish report is about a character with wrong rendering because the glyph is missing. This is the same issue.
[14:58] <effie_jayx> jibel,  they are related yes
[14:58] <effie_jayx> it is the same issue
[14:58] <effie_jayx> no
[14:59] <effie_jayx> as I am not trying to write in sweedish
[15:00] <effie_jayx> my keyboard settings are different from the oher reporters and all
[15:00] <effie_jayx> I can't reproduce that bug.
[15:00] <jibel> From a user point of view there are 2 different issues, but from the developper point of view it's the same.
[15:01] <jibel> When you watch the font with e.g. gucharmap, you'll see the missing glyphs.
[15:01] <effie_jayx> right
[15:02] <persia> No, even from a developer point of view, they are different: they are different glyphs.
[15:02] <effie_jayx> jibel,  well I reported a bug, with hopes some day I can write titles to my slides in spanish with the ubuntu-title font
[15:02] <persia> Mind you, having a master "Glyphs are missing" bug listing all the missing glyphs might address the developer point of view.
[15:03] <persia> effie_jayx: Can you generate the right glyph for review?
[15:03] <effie_jayx> persia,  I have not worked with fonts, but I could give it a shot
[15:04] <persia> effie_jayx: If you could, and perhaps add various diacriticals to other letters that you know are missing, I'm sure that the appropriate party would be pleased at the expansion.
[15:05] <effie_jayx> persia,  I am on it then
[15:05] <hggdh> and then mark those bugs as duplicates
[15:05] <hggdh> of the new master
[15:05] <persia> effie_jayx: Cool.
[15:05] <persia> hggdh: A new master?  Why not retitle/redescribe the oldest one, and dup to it?
[15:05] <jibel> and add the tag "metabug" ?
[15:06] <persia> saves bug numbers for future use (and saves us typing as many digits in conversation)
[15:06] <hggdh> thats good.
[15:06] <persia> Personally, I'd like to see more redescription going on: sometimes we do a good job of triage, but the title and description still aren't clear, so the bug doesn't get the attention it deserves.
[15:07] <hggdh> I fully agree
[15:08] <hggdh> and, when updating a bug description, please try to follow https://wiki.ubuntu.com/Bugs/Description
[15:09] <hggdh> all -- a good wiki page to bookmark is https://wiki.ubuntu.com/BugSquad/KnowledgeBase
[15:11] <hggdh> jibel, yes, then tag it metabug. You can see all the current tags at https://wiki.ubuntu.com/Bugs/Tags
[16:09] <markvandenborre> I've just had bug #34523 rejected as invalid
[16:10] <markvandenborre> with the mention "please use brainstorm.ubuntu.com"
[16:11] <markvandenborre> is that documented policy, or just someone trying to score launchpad karma?
[16:12] <markvandenborre> hm, that might sound a bit negative... whatever the reason, the intention is probably good
[16:14] <markvandenborre> but is this ubuntu bug policy?
[16:15] <alex-weej> markvandenborre: if it's that vague, then it should probably be on brainstorm
[16:15] <alex-weej> if you're willing to thrash out a technical solution
[16:15] <yoda_van> is 'invalid' the part that is bothering you?
[16:15] <alex-weej> try blueprints.launchpad.net/
[16:15] <yoda_van> i believe that is just the easiest way to say, not a bug, but something you'd like to see added to the app
[16:16] <yoda_van> it doesn't mean the thought is invalid
[16:16] <markvandenborre> yoda_van: I had it set to wishlist myself...
[16:16] <yoda_van> ahnh
[16:16] <markvandenborre> (before this came about, before brainstorm even existed)
[16:18] <techno_freak> markvandenborre, may be because we dont have a way to convert a bug (which is invalid as a bug) to a wishlist, we comment so and mark it as invalid bug :)
[16:18] <techno_freak> err.. sorry s/wishlist/brainstorm idea/
[16:21] <markvandenborre> so, right now, if I hadn't been very active and come around here, this idea would just be lost
[16:21] <markvandenborre> now I appreciated the fact that there has at least been some kind of feedback after 2 1/2 years
[16:23] <markvandenborre> but the way this was tackled, to a newcomer would sound a lot like "not interested, don't annoy us with this kind of stuff"
[16:24] <yoda_van> markvandenborre, all of the above is sort of true, that's why this weekend is global bug jam, and everyday people are trying to address bugs as they come in
[16:24] <yoda_van> it is an all volunteer army - all are welcome
[16:26] <yoda_van> the reality is, to a newcomer and an old-timer; no, we are *very* interested, and trying our best to get all the bugs triaged and sent to the right place
[16:26] <markvandenborre> ok, so something went wrong here
[16:26] <markvandenborre> if I hadn't been an 10+ year free software veteran
[16:26] <markvandenborre> I would feel like "whatever, I'm not putting my time in things that get neglected"
[16:27] <yoda_van> https://wiki.ubuntu.com/HelpingWithBugs
[16:27] <hggdh> markvandenborre, the triager could have been a bit more courteous indeed
[16:28] <markvandenborre> hggdh: which is exactly what I'm saying: at least in the way of bringing the message, there should have been more information
[16:29] <techno_freak> markvandenborre, i agree that the triager could have given an explanation why it is marked as invalid :)
[16:29] <markvandenborre> maybe it should have been marked needsinfo or something
[16:29] <markvandenborre> because it would need a formal specification
[16:29] <hggdh> I agree. Courtesy should be always maintained.
[16:30] <markvandenborre> but the contents of the bug is a different thing of course
[16:30] <markvandenborre> than the way the message is brought
[16:31] <markvandenborre> or the other way would have been for this person to have moved the bug to brainstorm
[16:31] <hggdh> markvandenborre, please bear with us. There are many new triagers, and some, huh, mistakes, should be expected
[16:31] <markvandenborre> yes, no problem
[16:31] <markvandenborre> I'm not screaming out loud "you guys did a lousy job"
[16:31] <markvandenborre> quite to the contrary
[16:31] <hggdh> unfortunately there is no way of automatically converting to a brainstorm
[16:32] <markvandenborre> then it should have happened manually, or whatever
[16:32] <hggdh> and this is your idea. I would not feel comfortable opening a brainstorm for you
[16:32] <hggdh> (and getting the credits)
[16:33] <markvandenborre> policies have changed from having wishlist bugs accepted in launchpad to wanting them in brainstorm
[16:33] <markvandenborre> that's allright
[16:34] <markvandenborre> but the reason I'm here was 1) to find out about new policies I was unaware of 2)to point you guys at a communication problem that might be solved by better documentation/process in the bug squad
[16:34] <hggdh> wishlists are still accepted, but yours is a bit more than that. Wishlist will depend on developers having the time to implement, whereas brainstorms can be "voted"
[16:35] <hggdh> markvandenborre, a triager is always expected to be courteous, and this is well documented. All that is needed is the willingless to read it
[16:35] <hggdh> and, of course, follow it
[16:36] <markvandenborre> the point is that a bug like the one I filed two years ago would rightly be considered invalid if filed now
[16:36] <markvandenborre> because there is brainstorm
[16:36] <hggdh> markvandenborre, you can re-open it, if you wish, and state the reasons for doing so
[16:37] <markvandenborre> so what I think is not clearly documented is what needs to happen to old wishlist bugs that actually belong in brainstorm right now
[16:37] <markvandenborre> hggdh: I'm thinking of doing the following:
[16:38] <markvandenborre> reopen, ask the triager to give more information why he closes bugs in the future, file it on brainstorm, close it
[16:38] <markvandenborre> does that sound right?
[16:40] <hggdh> markvandenborre, it works. You do not even need to re-open it. May I also suggest you send an email to ... (hold on)
[16:42] <markvandenborre> hggdh: ubuntu-devel?
[16:42] <hggdh> Ubuntu Bug Control (ubuntu-bugcontrol@lists.launchpad.net) stating what happened, and what you think about it? This will give a chance for all of us in bug-control to discuss the issue
[16:42] <markvandenborre> ok
[16:43] <hggdh> and, of course, you can send an email to ubuntu-devel-discuss (not ubuntu-devel). u-d-d would be a correct place to present the idea (which, BTW, I personaly like)
[16:44] <hggdh> markvandenborre, finally, on behalf of all, I apologise
[16:44] <markvandenborre> hey, no need to
[16:44] <markvandenborre> you guys are doing great work
[16:44] <hggdh> thank you. Huh, would you be willing to help triage bugs ;-)
[16:44] <markvandenborre> as I said before, I appreciate that, really
[16:44] <markvandenborre> I'm just concerned about newcomers and their reaction to this
[16:45] <hggdh> so am I
[16:45] <techno_freak> :)
[16:45] <hggdh> and this is another reason I elected to discuss it here, so that everybody could see it
[16:46] <techno_freak> and know where we usually do mistakes, and ahem.. correct them :)
[16:46] <markvandenborre> hggdh: sorry, I have 1 1/2 full time job, and I keep my ubuntu involvement limited to going to trying to coordinate a Locoteam, and going to a few Ubuntu Developer Summits
[16:46] <markvandenborre> heheh
[16:46] <hggdh> heh
[16:47] <hggdh> so am I, so am I... and I also have to throttle down my involvement (as I said elsewhere, I have family, dogs, and professional life to worry about, in this order)
[16:48] <markvandenborre> kthxbye
[16:48] <hggdh> techno_freak, we learn from our mistakes, that is true
[16:48] <hggdh> bye. Thank you
[16:49] <techno_freak> :)
[16:49] <techno_freak> we also learn by looking at other's mistakes and being careful not to commit them ;)
[16:49] <hggdh> yes... :-)
[16:51] <hggdh> but this is actually important: we should respect the reporters, and maintain a courteous exchange always. This is a requirement for bug-control, but I just checked, and do not see it clearly stated for triagers. I wIll raise the issue.
[16:51] <techno_freak> yes, agreed
[16:51] <hggdh> ogasawara, ping
[16:54] <hggdh> techno_freak, for example, persia just corrected me when I wrongly suggested opening a new master bug. It was obviously the incorrect choice, and I still erred...
[16:54] <techno_freak> I have been corrected a lot of times, thanks to those corrections I have been improving :)
[16:57] <techno_freak> sometimes it also happens to be a communication error where the triager misses few pleasantries that the reply looks a bit arrogant :)
[16:58] <yoda_van> yeah, it seems that curt replies come off as nasty - even though probably not intended to be
[16:59] <hggdh> yes
[17:00] <hggdh> the problema is not what you actually meant, but how it is perceived
[17:19] <effie_jayx> anyone here can help with a package... I have modified ttf-ubuntu-title and I am hiaving problems building the package
[17:20] <effie_jayx> buidling fails due to changes in the binary file,,, (ttf)
[17:20] <effie_jayx> they seem irrepresentable
[17:26] <jpds> effie_jayx: Are they in the source tarball?
[17:28] <effie_jayx> jpds,  yes, and that is how they came when I did apt-get source
[17:28] <jpds> effie_jayx: Does the error say what is unreprsentable?
[17:28] <effie_jayx> jacob,  the tty file
[18:13] <ogasawara> hggdh: pong
[18:18] <hggdh> ogasawara, morning to you and all; I will call you private
[18:51] <tuxmaniac> can someone set the bug 239179 importance to Low ?
[18:56] <hggdh> tuxmaniac, done
[18:56] <tuxmaniac> hggdh: thanks
[18:57] <hggdh> I thought you would be able to set importance to low yourself...
[18:57] <tuxmaniac> hggdh: I am not part of that team which will be able to do that
[18:57] <hggdh> ah, ok, sorry
[19:40] <alexadranghi> ﻿Hi guys. Just wanted to let me know I'm using Hardy on Linux corus 2.6.24-18-generic #1 SMP 686 GNU/Linux, and just apt-get update & upgrade-ed, and for some reason Thunderbird is now crashing whenever I hit send if I enable signing with Enigmail. Where's the best place to report this problem. I can't see anything in the main log files - where are thunderbird's own log file located? Cheers.
[19:45] <mrooney> alexadranghi: the best thing to do is probably to file a bug in launchpad against thunderbird (ubuntu) and let someone who knows more tell you what they need
[19:46] <mrooney> alexadranghi: check https://bugs.launchpad.net/ubuntu/+source/thunderbird to see if the bug has already been reported, otherwise click the "Report a bug" link
[19:47] <alexadranghi> Cheers
[19:49] <alexadranghi> Heh. Look's like firefox died too.
[23:55] <LimCore> how to get source for "p7zip-full" ?   apt-get source "p7zip-full" -> E: Unable to find a source package for p7zip     (I want to edit it's documentation)