[01:29] <virtuald> lastlog ipv6
[01:31] <charlie-tca> virtuald: what is that?
[01:31] <charlie-tca> virtuald: Please don't do that.
[01:32] <virtuald> it was i mistake, i forgot /
[01:33] <charlie-tca> Thank you
[02:59] <andrewmiller57> bug 668318 should be set to medium I think
[02:59] <ubot2> Launchpad bug 668318 in evolution (Ubuntu) "evolution calendar cannot change first day of week (affects: 3) (heat: 70)" [Undecided,Confirmed] https://launchpad.net/bugs/668318
[03:02] <charlie-tca> andrewmiller57: did it work in the previous version?
[03:04] <rusivi> andrewmiller57: Cursory glance at bug 668318 suggests it's Low-Medium importance, leaning towards Low.
[03:04] <ubot2> Launchpad bug 668318 in evolution (Ubuntu) "evolution calendar cannot change first day of week (affects: 3) (heat: 70)" [Undecided,Confirmed] https://launchpad.net/bugs/668318
[03:05] <charlie-tca> A bug that has a moderate impact on a core application
[03:06] <andrewmiller57> ok, yes it worked in 10.04 just fine.  I figured with evolution being the main email app, it would be medium :-)
[03:06] <charlie-tca> Evolution is a core application, and there are a lot of users whose week does start on Sunday instead of Monday
[03:06] <charlie-tca> and it is a regression.
[03:06] <charlie-tca> That is not low.
[03:07] <rusivi> charlie-tca: I was grinding on the core application part, could not find the link for importance I saved to my bookmarks (potential Firefox bug!)
[03:07] <andrewmiller57> https://wiki.ubuntu.com/Bugs/CommonTasks
[03:08] <charlie-tca> andrewmiller57: that will need to be sent upstream to gnome bugzilla
[03:08] <andrewmiller57> ok, is there a specific url for it
[03:08] <rusivi> andrewmiler57 / charlie-tca: May want to check out a search on Evolution for calendar problems -> https://bugzilla.gnome.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=Evolution&content=calendar
[03:09] <charlie-tca> rusivi: https://wiki.ubuntu.com/Bugs/Importance
[03:09] <rusivi> charlie-tca: ty
[03:09] <charlie-tca> be my guest in searching for it
[03:10] <andrewmiller57> do you know what the url would be for forwarding this one upstream?
[03:10] <charlie-tca> andrewmiller57: I did add the link for upstreaming the bug to it
[03:10] <charlie-tca> just refresh the page
[03:11] <andrewmiller57> ok thanks
[03:11] <rusivi> andrewmiller57 / charlie-tca: https://bugzilla.gnome.org/enter_bug.cgi
[03:11] <charlie-tca> rusivi: look at the bug
[03:11] <charlie-tca> are you even reading what I am telling andrewmiller57 ?
[03:12] <andrewmiller57> yes i am, I just had to refresh, I didnt know you posted that
[03:12] <rusivi> charlie-tca: just refreshed the Launchpad bug looks good!
[03:18] <rusivi> charlie-tca: Is their a link for a list of all core applications?
[03:18] <charlie-tca> no
[03:19] <charlie-tca> None that I know of. It is consists mostly of those applications installed by default in Ubuntu. the core applications are all packages in Main repository
[03:20] <charlie-tca> If you use "apt-cache policy PACKAGE", it tells you if the package is in main
[03:23] <rusivi> charlie-tca: Is their a website/command that quickly shows all packages in Main repo? I know website for package search -> http://packages.ubuntu.com/
[03:26] <charlie-tca> hm, most if not all of https://launchpad.net/~desktop-bugs/+packagebugs are core
[03:26] <rusivi> charlie-tca: Just was reading -> https://help.ubuntu.com/community/Repositories/Ubuntu it mentions I can just use Synaptic and use filter "main"
[03:27] <charlie-tca> That is another way, yes. I never look at the whole thing at once, since I can't remember them all anyway
[03:27] <charlie-tca> :-)
[03:28] <charlie-tca> The problem is not every package in main will be a core package, but every core package will be in main
[03:29] <rusivi> charlie-tca: right, not every package is an application, but every application is a package/combination of packages
[03:30] <charlie-tca> Main thing is if it is a default application in Ubuntu, count it as core
[03:31] <rusivi> k ty
[03:31] <charlie-tca> Xubuntu, Kubuntu, Lubuntu, etc, do not usually have core packages
[07:53] <rusivi> Regarding bug https://bugs.launchpad.net/ubuntu/+source/apt/+bug/641673 seems Low importance.
[07:53] <ubot2> Launchpad bug 641673 in apt (Ubuntu) "grammatical mistake in 'apt-cache show awk': "as it purely virtual" (affects: 1) (heat: 36)" [Undecided,Confirmed]
[08:09] <micahg> rusivi: done, thanks
[08:09] <rusivi> micahg: ty
[10:35] <PaoloRotolo> Hi all
[14:44] <wolffu> Does anyone have a chance to double check that I handled bug 296336 correctly?
[14:44] <ubot2> Launchpad bug 296336 in nasm (Ubuntu) "nasm global directive sometimes not working with elf output (heat: 2)" [Undecided,Fix released] https://launchpad.net/bugs/296336
[14:47] <charlie-tca> wolffu: if you are asking the reporter to confirm whether or not it is working, it is not fixed-released. It should be incomplete
[14:50] <wolffu> charlie-tca: So it should not be considered an "old bug" from https://wiki.ubuntu.com/Bugs/CommonTasks
[14:50] <yofel> wolffu: also, please replace <bug #> with the actual bug number next time you use the stock response please, it can be confusing like this
[14:50] <charlie-tca> wolffu: you marked it fixed, and asked for more information. You should mark it incomplete instead.
[14:50] <wolffu> yofel: I was wondering about that. Thanks for the info.
[14:51] <wolffu> charlie-tca: O.k. thanks.
[14:51] <charlie-tca> Fixed bugs do not require the reporter to give you more information. The comment was correct, but the status is wrong
[14:53] <wolffu> Is there anyone available to mark bug 296336 to incomplete?
[14:53] <ubot2> Launchpad bug 296336 in nasm (Ubuntu) "nasm global directive sometimes not working with elf output (heat: 2)" [Undecided,Fix released] https://launchpad.net/bugs/296336
[14:53] <charlie-tca> done
[14:54] <wolffu> charlie-tca: Thanks...again.
[14:54] <charlie-tca> wolffu: thank you for helping with bugs. It is appreciated!
[16:49] <nisshh> hmmmm, does anyone know if the nick 'em' is a bot, they just pmed me as soon as i joined
[16:49] <nisshh> connected rather
[16:59] <charlie-tca> nisshh: as far as I know, em is a person
[16:59] <charlie-tca> em: ^ ^ ^
[16:59] <nisshh> charlie-tca, yeah, i just figured it out, sorry, i was just connecting after a power outage and em pmed me, i was just confused :)
[17:00] <charlie-tca> no problem
[17:00] <charlie-tca> it happens
[17:00] <nisshh> heh
[17:00] <nisshh> yeah
[17:00]  * charlie-tca is one of the fortunate ones; his power failed during the night, so he was sleeping
[17:01] <nisshh> charlie-tca, yeah, except its new years eve, so im not asleep :)
[17:01] <charlie-tca> heh, well then, Happy New Years
[17:02] <nisshh> same to you :)
[17:04] <charlie-tca> Best wishes for a very Happy New Year - 2011!
[17:06] <ElPasmo> Thanks charlie-tca, I wish you all a happy 2011 also!
[17:20] <ElPasmo> I'm having problems with bug 692562, last few days I've been trying to add a bugwatch with no joy. Can anyone try to click the "also affects project" link and figure out how should I proceed with the error: OOPS-1826K1261 ?
[17:20] <ubot2> Launchpad bug 692562 in bash-completion (Ubuntu) "completion of inserted option after command throws bash error (affects: 2) (heat: 16)" [Undecided,Confirmed] https://launchpad.net/bugs/692562
[17:20] <ubot2> https://lp-oops.canonical.com/oops.py/?oopsid=1826K1261
[17:22]  * penguin42 looks
[17:22] <ElPasmo> thanks penguin42
[17:22] <penguin42> ElPasmo: Yeh it oopses for me as well, so ask on #launchpad quoting the OOPS id
[17:22] <ElPasmo> Ok, ty
[17:22] <penguin42> ElPasmo: although I guess there probably aren't many people around at this time
[17:23] <ElPasmo> yup, bad day huh? :P
[17:24] <charlie-tca> hm, oops here too
[17:24] <charlie-tca> at least it is consistent, right?
[17:25] <penguin42> ElPasmo: I guess you could file a bug against launchpad
[17:25] <ElPasmo> mmm never did it before! :D
[17:25] <ElPasmo> mmm lets try
[17:26] <micahg> check to see if one is filed, tag timeout
[17:26]  * micahg is assuming it timed out
[17:26] <penguin42> it's not affecting all bugs though is it?
[17:27] <penguin42> micahg: It oops's quite fast
[17:27] <ElPasmo> No penguin42
[17:27] <micahg> penguin42: does it say timeout?
[17:27] <ElPasmo> I think its the only bug where it occurs
[17:27] <penguin42> micahg: No
[17:28] <penguin42> micahg: Oops! Sorry, something just went wrong in Launchpad. We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience. (Error ID: OOPS-1826D1516)
[17:28] <ubot2> https://lp-oops.canonical.com/oops.py/?oopsid=1826D1516
[17:30] <penguin42> micahg: It  looks more like something specific to that bug
[17:31] <micahg> penguin42: so file a bug against launchpad and add an oops tag
[17:32] <penguin42> micahg: Which if you scroll back is what I suggested
[17:32] <micahg> penguin42: right, I'm adding the part about the oops tag ;)
[17:35] <ElPasmo> I file it or you file it?
[17:35] <ElPasmo> I don't mind, I have time now :)
[17:35] <penguin42> ElPasmo: You found it!
[17:35] <ElPasmo> and?
[17:35] <ElPasmo> :D
[17:35] <penguin42> you file it!
[17:35] <ElPasmo> Ok :D
[17:37] <ElPasmo> ok noob question, how I file a bug against launchpad? :P
[17:37] <micahg> ElPasmo: bugs.launchpad.net/launchpad
[17:38] <ElPasmo> I knew it'd to be obvious :P
[17:40] <ElPasmo> oops tag?
[17:40] <ElPasmo> I just add an "oops" in the tag field?
[17:40] <penguin42> the OOPS-xxxxxxx number from the error
[17:40] <ubot2> https://lp-oops.canonical.com/oops.py/?oopsid=xxxxxxx
[17:40] <ElPasmo> ok
[17:40] <penguin42> or does micahg mean a launchpad tag?
[17:41] <micahg> launchpad tag :)
[17:41] <micahg> ElPasmo: yes
[17:41] <ElPasmo> check bug 696052
[17:41] <ubot2> Launchpad bug 696052 in launchpad "Error OOPS-1826D1516 when adding a bugwatch (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/696052
[17:41] <ElPasmo> plz :)
[17:42] <penguin42> ElPasmo: I'd change the title to say repeatable and say it's repeatable by many different people
[17:42]  * charlie-tca learned something today about launchpad. Thanks 
[17:42] <micahg> ElPasmo: FTR, just oops in the tag, not the oops code
[17:42] <ElPasmo> lol
[17:42] <ElPasmo> thanks :)
[17:43] <penguin42> ElPasmo: I assume the lp guys get loads of reports of oops that diappear, but ones that are completely repeatable are much easier to deal with
[17:43] <micahg> there's a zero oops policy, so even if it wasn't repeatable, it would be a high priority
[17:43] <ElPasmo> Like that?
[17:50] <ElPasmo> Well thanks to all of you... I hope you'll have a happy new year!!! see you in 2011! :)
[17:53] <penguin42> ElPasmo: Have a good one ElPasmo
[17:55] <yofel> ElPasmo: bash completion oopsing is a known issue
[17:56] <penguin42> yofel: so it's all bash completion bugs that oops lp?
[17:58] <yofel> penguin42: yes, see bug 370117
[17:58] <ubot2> Launchpad bug 370117 in launchpad "oops getBugFilingAndSearchLinks need more than 1 value to unpack (affects: 5) (dups: 2) (heat: 24)" [High,Triaged] https://launchpad.net/bugs/370117
[17:58] <yofel> penguin42: my dup bug 615123 has the complete trace
[17:58] <ubot2> Launchpad bug 615123 in launchpad "Oops on production when opening +choose-affected-product (dup-of: 370117)" [High,Triaged] https://launchpad.net/bugs/615123
[17:59] <micahg> yofel: do you want to add a note on the bug elpasmo filed and LP people can confirm?
[17:59] <yofel> sure
[17:59] <micahg> yofel: thanks
[18:00] <penguin42> yofel: For this one it's oopsing before it's asked for the other project that it affects; so it sounds different from the 370117
[18:00] <yofel> penguin42: well, same error
[18:01] <penguin42> ok, I don't get to see the error itself
[18:02] <micahg> that's why I suggesting commenting and not duping
[18:18] <em> Hi
[18:25] <penguin42> Hi indeed
[18:35] <penguin42> don't suppose anyone understands the details of udisks do they?
[18:43] <yofel> penguin42: well, what's the problem?
[18:43] <penguin42> do you know what the 'presentation nopolicy' flag is supposed to mean?
[18:44] <penguin42> there is a 'presentation hide' and a presentation nopolicy; hide is obvious
[18:48] <penguin42> hmm it's listed as a 'hint if the device (or e.g. the multi-disk device that the device is part of) shouldn't be automatically mounted / assembled'
[18:52]  * penguin42 hates it when there are so many layers in systems, I need a ball of string and bread crumbs to follow them through
[20:25] <penguin42> for segfaults of an fglrx X server what do we put things against - fglrx ?
[20:26] <charlie-tca> yup
[21:51] <hggdh> just a note -- I updated https://wiki.ubuntu.com/UbuntuBugControl#Application .1.5, trying to make it clearer that applicants *have* to provide importance and reasoning for such for each bug they submit for review
[21:51] <hggdh> so... is it clearer now?
[22:09] <njin> happy new year to all the buggers
[22:30] <penguin42> it's an interesting collective name
[22:31] <hggdh> indeed. I wonder if something has been lost in translation
[22:32] <hggdh> :-)
[22:32] <hggdh> but happy new yoaer to all bug-triagers
[22:38] <crimsun> I think it's most probably "people who work on bugs"
[22:38] <crimsun> but yes, que interesante
[22:52]  * penguin42 doesn't think debuggers sounds right either
[23:21] <hggdh> well, de-buggers really sounds, ah, suggestive?
[23:26] <penguin42> heck, the number of packages generated from a build of kd4libs is scary
[23:27] <penguin42> hmm - 42 in fact - hmmmm
[23:29] <hggdh> there may be something there...
[23:40] <penguin42> hmph, I've half fixed a bug
[23:46] <yofel> happy new year everyone that's online ;)
[23:48] <penguin42> yofel: Happy new year Yofel