[00:24] <kees> I'm trying to output some json for harvest.
[00:24] <kees> I see from http://harvest.ubuntu.com/opportunities/ things like "karmic" and "merges"
[00:24] <kees> how do I define those metadata for my exported json items?
[00:25] <bdmurray> kees: I think that is based on the filename for the opportunity
[00:26] <kees> bdmurray: oh! so it is.
[00:27] <kees> I guess I should rename mine from "index.json" to something more interesting. :)
[00:27] <bdmurray> kees: yes you need to sell it better
[00:28] <kees> bdmurray: I'll name it aaaaawesome ;)
[00:30] <kees> http://people.canonical.com/~ubuntu-security/d2u/debian-security.json there
[00:35] <bdmurray> kees: merged keep an eye out harvest to make sure it works out okay
[00:39] <kees> bdmurray: oooh, thanks!
[00:39] <kees> bdmurray: how often does harvest consolidate from its opportunities lists?
[00:40] <bdmurray> kees: don't know really
[00:42] <kees> oaky, cool
[10:23] <ubv16> hi. if I connect my laptop to monitor through VGA port and use xrandr (resolution 1920x1200), my taskbar is getting unsorted like this: http://image.bayimg.com/mahmlaadi.jpg
[14:15] <kamusin> I am having an issue that I am not sure who is the guilty..  if I open a music file from nautilus this launched totem as media player but should be banshee instead, should I reassign this issue to gnome-control-center (is already reported in banshee)?
[14:17] <om26er> kamusin, check in preferred apps if banshee is the default music player
[14:17] <om26er> it should not be banshee-
[14:17] <om26er> banshee-1
[14:18] <kamusin> om26er, banshee is checked as my default media player of course heh
[14:19] <om26er> kamusin, try 'custom' and 'banshee' as the executable
[14:21] <kamusin> same behaviour, by the way I wrote banshee and automatically sets again to default (banshee)
[14:31] <yofel> kamusin: what are the file associations for the music file in nautilus?
[14:33] <kamusin> yofel, give me a second (checking..)
[14:34] <JanC> Totem has always been the default for opening any media files, including music files?
[14:35] <kamusin> yofel, totem is marked heh.. that could be due to my system upgrade .. but original reporter said (apport) that is using Natty from a fresh installation
[14:36] <yofel> well, I have no idea what gnome-control-center is supposed to do there, but this is actually how I would expect it to work, as the used application is defined by the mime type settings
[14:38] <JanC> g-c-c sets the application that gets started when you plug in a mediaplayer or when you press the "mediaplayer key" on your keyboard & such?
[14:39] <JanC> at least, I think that's what it does
[14:39] <JanC> probably not even the mediaplayer thing
[14:41] <kamusin> got it,  any way by default nautilus has set to totem as default media player, maybe this should be replaced by banshee instead to be more consistent
[15:45] <trinikrono> how long is the meeting from now?
[15:46] <charlie-tca> trinikrono: 2hrs and 15 minutes
[16:22] <trinikrono> thanks charlie-tca thats 1pm for me
[16:23] <trinikrono> ima shutdown now
[17:11] <tomtiger11> am i late
[17:15] <tomtiger11> Hello
[17:15] <tomtiger11> Hello!
[17:17] <yofel> hi tomtiger11, if you mean the meeting it's in 45m
[17:17] <tomtiger11> i just found out!
[18:00] <bdmurray> Happy 2nd Tuesday everyone
[18:00] <yofel> o/
[18:01] <bdmurray> Since its the 2nd Tuesday that means it is time for the Bug Squad Meeting
[18:01] <trinikrono> im there
[18:01] <trinikrono> bdmurray: we are after the kernel meeting?
[18:02] <bdmurray> trinikrono: we've been having the bug squad meeting here
[18:02]  * charlie-tca waves
[18:02] <pedro_> hello
[18:03]  * hggdh waves
[18:03] <micahg> o/
[18:03] <bdmurray> however maybe we should think about moving it to #ubuntu-meeting - we can discuss that towards the end of the meeting
[18:03] <trinikrono> o/
[18:04] <bdmurray> Some action items came out of our last meeting
[18:04] <bdmurray> 1) Follow up with nigelb regarding edit bugsquad headers to be similar or link to each other appropriately
[18:05] <bdmurray> IIRC he indicated after the meeting he was still planning on working on this
[18:05] <bdmurray> Its been a fair bit though so I'll check in with again
[18:06] <bdmurray> micahg you updated the needs-packaging wiki page correct?
[18:06] <nigelb> bdmurray: yes, I still am :)
[18:06] <micahg> bdmurray: about an hour ago :)
[18:06] <bdmurray> micahg: well it got done though!
[18:08] <bdmurray> vish was to add more people to the bugsquad mentorship group alpha and I know this has happened
[18:08] <bdmurray> there have been some good discussions on that team's mailing list
[18:09] <bdmurray> Lastly - BrianMurray to email bugsquad regarding #ubuntu-bugs channel watchers
[18:09] <bdmurray> That hasn't happened but will today.
[18:09] <bdmurray> So those are all the actions from the last meeting
[18:10] <bdmurray> vish: Are you around to discuss the mentorship program?
[18:11] <bdmurray> I'm pretty happy with the renewed activity and discussions.  Does anybody have anything else to discuss regarding the program?
[18:13] <bdmurray> Okay then, moving on.  We have no new bug control members to announce since the last meeting.
[18:13] <charlie-tca> I like the idea that things are being discussed, too
[18:14] <hggdh> finally!
[18:15] <bdmurray> From UDS natty I had a work item to investigate making karma more informative on the +karma page for people.  From looking at the Launchpad database there really isn't a way to make that page more informative.
[18:16] <bdmurray> The table just has a record of the action taken and the project it happened on.
[18:17] <bdmurray> So we can't find out what bug someone set to Triaged or what have you.
[18:17] <micahg> I was told karma might be going away in any case
[18:17] <bdmurray> I didn't immediately recall why we specifically wanted this.  Does anyone remember the use case?
[18:18] <trinikrono> i believe the plan was to see what bugs karma was gotten from
[18:18] <bdmurray> okay, but why?  How would that help someone do their work?
[18:19] <charlie-tca> You can see that by clicking on the bugs information on the page
[18:19] <trinikrono> well for one you would be able to see what bugs a new triager worked on and received karma
[18:20] <bdmurray> charlie-tca: hmm, where?
[18:20] <micahg> karma is irrelevant in that though
[18:20] <charlie-tca> If you are looking at an individual, you click on Bugs
[18:21] <charlie-tca> It shows all the bugs they worked on
[18:21] <charlie-tca> Whether they are a new triager or not, the bugs they touched are still there
[18:22] <bdmurray> charlie-tca: I'm pretty sure not everything shows up there, but regardless I'm still not clear on the use case.
[18:22] <bdmurray> It sounds like following the work of a triager is the goal
[18:22] <charlie-tca> I am not clear on it either. It seems like too much emphasis on getting karma, to me.
[18:24] <micahg> that's bug 379893
[18:24] <ubot4> Launchpad bug 379893 in launchpad "no way to stalk other users (affects: 6) (dups: 1) (heat: 9)" [Low,Triaged] https://launchpad.net/bugs/379893
[18:24] <bdmurray> micahg: thanks, I'll email the mailing list and see if that is really what we were looking for.
[18:26] <bdmurray> micahg: that brings us to your item re multiarch
[18:26] <yofel> what was the difference between non-/official tags again?
[18:27] <bdmurray> official bug tags show up when you are adding tags to a bug report
[18:27] <yofel> k
[18:27] <bdmurray> for example if you click the pencil by the exisiting bug tags
[18:27] <micahg> ok, so, just a simple request to add this tag to track multiarch issues which will be ongoing through oneiric and probably P
[18:28] <bdmurray> so the official ones are a decent way to get people to use the same tags
[18:30] <bdmurray> micahg: seems reasonable to me is there a good example of when to use it?
[18:31] <micahg> if a build system or installer has a problem due to the new /usr/lib/*triplet* paths
[18:32] <bdmurray> micahg: and what is the advantage to making it official? I'd think must people who would use that tag don't need a hint.
[18:32] <bdmurray> s/must/most/
[18:32] <micahg> lack of typos? documented on tags page?
[18:32] <bdmurray> yofel: they also appear first in the list of tags on the bug's web page
[18:33] <yofel> ah, good to know
[18:33] <bdmurray> micahg: okay, lets do it then
[18:34] <micahg> done
[18:35]  * micahg goes to document
[18:35] <bdmurray> Okay, that covers everything on the agenda.  Are there any other topics to discuss?
[18:36] <yofel> we were talking about moving to -meeting at the beginning. Any benefit in doing that?
[18:36] <trinikrono> well i thought thats where the meeting was
[18:36] <trinikrono> since it was in the fridge agenda
[18:37] <charlie-tca> the issue with using #ubuntu-meeting is finding a time slot that is open
[18:37] <bdmurray> and convenient
[18:38] <bdmurray> this time seems to have been working reasonably well
[18:38] <duanedesign> o/
[18:39] <bdmurray> I think we should stay here fwiw
[18:40] <bdmurray> duanedesign: do you have something?
[18:40] <duanedesign> bdmurray: sorry, was just saying hi :P
[18:41] <bdmurray> cool, anything else?
[18:41] <duanedesign> bdmurray: i know ddecator has been working on an outline for /bugs/HOwToTriage
[18:41] <charlie-tca> +1 for here
[18:42] <bdmurray> duanedesign: great I saw an email about that
[18:43] <bdmurray> I'd like to remind everyone that Natty is due very soon now.  So keep and eye out for High and Critical bugs and please ping me if you find one you think needs fixing in Natty.
[18:43] <duanedesign> I talked too some people in the Beginners Team Documentation Focus Group wwho would like to help implement that outline once it getds hammered out
[18:44] <duanedesign> so if any help is needed implementing the changes, that is an option
[18:44] <bdmurray> cool, thanks!
[18:44] <micahg> oh, reason to go to #ubuntu-meeting might be non-bugsquad people participating?
[18:45] <charlie-tca> um, what reason would non-bugsquad people have to do that? They can join here, too, right?
[18:45] <micahg> charlie-tca: lots of people idle in -meeting
[18:47] <bdmurray> micahg: true, my thought was it would be complicated to find a time.
[18:48] <charlie-tca> I see that as more reason to keep the meeting here. People that idle in -meeting don't necessarily pay any attention to the meeting that is going.
[18:48] <charlie-tca> Here, at least they join specifically to attend, if they want to.
[18:49] <trinikrono> and in the calender it does say that the meeting is in #ubuntu-bugs
[18:49] <micahg> well, lots of people idle here too, but I figure -meeting might get more cross team participation
[18:49] <micahg> trinikrono: calendar can be updated ;)
[18:50] <trinikrono> well i have a thought
[18:50] <trinikrono> i noticed something looking at the meeting logs
[18:50] <trinikrono> https://wiki.ubuntu.com/MeetingLogs/BugSquadTeam
[18:50] <trinikrono> its empty :o
[18:51] <bdmurray> yes, having a meeting bot would be another advantage
[18:51] <bdmurray> micahg: would you mind looking for a free time in #ubuntu-meeting?
[18:51] <charlie-tca> Yes, that would be an advantage.
[18:51] <micahg> bdmurray: sure, I can do that
[18:52] <bdmurray> micahg: thanks, I'd think something around the time this started or -1 would work
[18:52] <yofel> would be nice if the time would be close to the current one, I don't really care about the day though
[18:53] <micahg> bdmurray: do we care which day?
[18:53] <bdmurray> I don't think so Tuesday was rather random as it was
[18:53] <micahg> k
[18:54] <micahg> I'll follow up on the ML, hopefully we can use the new time next month
[18:54] <micahg> are we planning to meet at UDS or push off a week?
[18:54] <bdmurray> A week earlier than UDS makes some sense to me
[18:55] <bdmurray> In case there are any natty issues to discuss or items for UDS
[18:55] <micahg> k, has there been a call for blueprints yet on the ML?
[18:55] <bdmurray> No
[18:59] <bdmurray> okay, thanks everyone!  Have a good day.
[18:59] <jtaylor> can someone adapt the importance/milestone of bug 752647 so that it won't get overlooked before the release?
[18:59] <ubot4> Launchpad bug 752647 in matplotlib (Debian) (and 1 other project) ""import pylab" in a python console flags error "No module named _tkagg" (affects: 11) (heat: 744)" [Unknown,Unknown] https://launchpad.net/bugs/752647
[18:59] <charlie-tca> bdmurray: thanks for chairing
[19:00] <velle_frak> thx
[19:23] <ilea> can i report a bug that ubuntu 11.04 haves?
[19:24] <yofel> !bugs | ilea
[19:24] <ubot4> ilea: If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs - Bugs in/wishes for the IRC bots (not Ubuntu) can be filed at http://bugs.launchpad.net/ubuntu-bots
[19:25] <ilea> i am using kiwi now not ubuntu 11.04
[19:25] <ilea> i instaled ubuntu 11.04 and haved a problem with the DSL conection
[19:26] <ilea> after i configured it ( username, service, password) i tryed to conect and after a time it failed
[19:26] <ilea> i didn't have this problem on ubuntu 10.04, 10.10
[19:26] <ilea> so this must be a bug
[19:27] <yofel> hm, do it like that: run 'apport-cli --save report.apport network-manager' in a terminal in 11.04 after doing such a failed attempt to connect
[19:28] <yofel> copy the report.apport file somewhere you can access it from in an older release and then file the bug with 'ubuntu-bug report.apport' from a release where the connection works
[19:29] <ilea> i have to write in termianal apport-cli or how to do it ?
[19:30] <ilea> i am not using linux for a long time to know
[19:30] <yofel> yes, you'll need a terminal for that
[19:30] <yofel> !terminal
[19:30] <ubot4> The linux terminal or command-line interface is very powerful. Open a terminal via Applications -> Accessories -> Terminal (Gnome), K-menu -> System -> Konsole (KDE), or Menu -> Accessories -> LXTerminal (LXDE). Guide: https://help.ubuntu.com/community/UsingTheTerminal
[19:30] <Pici> You'll need an internet connection for that though.
[19:30] <njin> Hello, can someone reproduce and set to low bug 759040 . Thanks
[19:30] <ubot4> Launchpad bug 759040 in aptdaemon (Ubuntu) "<type 'exceptions.NameError'>: global name 'logging' is not defined (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/759040
[19:31] <yofel> Pici: that's why I told him to use --save
[19:31] <Pici> yofel: Oops, I missed that,.
[19:32] <ilea> after i have the bug report how to send it?
[19:34] <yofel> ilea: as I said, save the file somewhere you can access it from an older release and then file it from there. Using a live disk will work too
[19:35] <yofel> njin: I do indeed get an aptd crash, but with Traceback: TypeError: watch_lock() takes exactly 1 argument (2 given)
[19:36] <ilea> ok i will save the report and then get back to ask where to send it and how
[19:37] <yofel> ah, my crash seems to be bug 759023
[19:37] <ubot4> yofel: Bug 759023 on http://launchpad.net/bugs/759023 is private
[19:41] <ilea> can you please tell me a more exactly witch comand to write in terminal so that i will have the report for the internet conection bug?
[19:41] <ilea> i am a little new in linux and dont know that
[19:43] <njin> yofel: mine is just "Failed to lock the cache"
[19:44] <njin> but aptd is crashed
[19:52] <njin> i've got also Title: <type 'exceptions.NameError'>: global name 'TransactionCancelled' is not defined even related to the cash locked by Synaptic
[20:12] <mvo> yofel: this is fixed in bzr and uploaded (but in the queue)
[20:12] <yofel> :)
[21:56] <gondoi> is there a channel that I can join to talk about missing kernel modules?
[22:02] <charlie-tca> I would think #ubuntu-kernel knows the most about kernels.
[22:02] <gondoi> charlie-tca: awesome.. didn't see that channel on the list
[22:02] <gondoi> i'll check it out
[22:03] <charlie-tca> It's hard to spot channels, with as many as there are.
[23:18] <mikesergio> can someone confirm something a simple bug in natty for me before i submit it as a bug
[23:20] <mikesergio> the launcher in unity recognizes input with a control key as a garabge character. For example, typing Ctrl+V into the launcher
[23:25] <patrickmw> hello, mikesergio.  please submit a bug and provide detailed steps to reproduce the issue.