[01:09] <bddebian> Boo
[01:11] <Pici> ack!, scared me
[01:11] <bddebian> :)
[11:36] <salty-horse> every once in a while, random buttons in the window list panel have their titles replaced with a running clock. I think it started happening after I fiddled with intlclock. has anyone noticed that too?
[11:37] <salty-horse> clicking on the intlclock applet to open the window makes the bad title go away
[11:40] <pedro_> haven't seen that before, i don't use intlclock that might be the issue
[11:52] <afflux> mornin
[11:56] <secretlondon> hi
[12:34] <Iulian> Hey
[13:47] <bddebian> Boo
[13:50] <charle1> how do some bugs start out as invalid?
[13:54] <pedro_> catterly: if you're referring to the ones listed at ubuntu-bugs-announce, it's because they have been made public or the triager was way faster :-P
[14:06] <qense> hello
[14:13] <secretlondon> hi
[14:14] <catterly> pedro_: I was, thanks!
[14:32] <Pres-Gas> Has anyone looked at https://bugs.launchpad.net/ubuntu/+bug/200064
[14:32] <ubotu> Launchpad bug 200064 in ubuntu "the iwl3945 driver will not connect to my open, 802.11 b, linksys  AP" [Undecided,New]
[14:33] <Pres-Gas> I would think that all the intel wireless people would be concerned about this?
[14:36] <james_w> Pres-Gas: can you connect without network manager?
[14:37] <seb128> assigning the bug to network-manager would be better than having it on no component
[14:37] <seb128> where is it now you can be sure nobody out of the bugsquad will look at the bug
[14:38] <james_w> yeah, I was wondering it if was n-m or linux-ubuntu-modules
[14:38] <Pres-Gas> james_w: I guess that will be the next step
[14:39] <seb128> james_w: in any case better to reassign to network-manager
[14:39] <seb128> if that's wrong it can be changed later
[14:39] <Pres-Gas> This is a similar one...
[14:39] <Pres-Gas> https://bugs.launchpad.net/ubuntu/+bug/198006
[14:39] <ubotu> Launchpad bug 198006 in ubuntu "Dell Inpriron and IPW3945" [Undecided,New]
[14:40] <Pres-Gas> Though we have not posted logs to it like in 200064
[14:40] <Pres-Gas> So, I am assuming I should use iwconfig?
[14:41] <james_w> yes please
[14:42] <Pres-Gas> crap...I will have to do this after work
[14:42] <Pres-Gas> should I just post to 200064?
[14:45] <james_w> they look similar, but there is not enough information to say if they are the same
[14:45] <james_w> I think you should mark one a duplicate of the other and provide as much information as possible, that gives it the best chance of being fixed.
[14:48] <catterly> would anyone mind setting an importance on this? my bugcontrol app is still pending I suppose, bug #201555
[14:48] <ubotu> Launchpad bug 201555 in checkgmail "checkgmail dependencies not met/checked" [Undecided,Confirmed] https://launchpad.net/bugs/201555
[14:49] <catterly> it seems Medium, maybe High, any opinions?
[14:49] <Pres-Gas> james_w: Does this mean I have to power to do so or are you talking to the bug gods?
[14:49] <catterly> well, anyone with the power to do so haha
[14:49] <catterly> I don't know if you do!
[14:49] <catterly> unless you are a dev or BugControl, I assume not
[14:49] <james_w> Pres-Gas: you have the power
[14:49] <Pres-Gas> I am pretty new to lauchpad, catterly
[14:49] <Pres-Gas> I have the glow?!?!
[14:50]  * Pres-Gas begins to RTFM Launchpad
[14:50] <james_w> Pres-Gas: you can mark the bugs you were talking about as duplicates, but you can't fulfil catterly's request
[14:51] <Pres-Gas> Thanks for the clarification, james_w
[14:52] <afflux> anyone able to forward bug 199157 to gcin upstream? I'm not able to find any, (except one page that consists only of chinese symbols)
[14:52] <ubotu> Launchpad bug 199157 in gcin "gdmgreeter crashed with SIGSEGV in gcin_im_client_forward_key_press()" [Medium,Incomplete] https://launchpad.net/bugs/199157
[14:53] <Pres-Gas> I think I will convert 198006 to question instead of marking as duplicate...jfree143 says it is solved.
[14:54] <james_w> catterly: bug 68671
[14:54] <ubotu> Launchpad bug 68671 in checkgmail "should depend on libcrypt-simple-perl" [Undecided,Confirmed] https://launchpad.net/bugs/68671
[14:54] <james_w> you will probably want to read that and then unify the two somehow
[14:54] <secretlondon> may want to look at debian bugs too
[14:54] <james_w> and add the tags "bitesize packaging"
[14:54] <james_w> hi secretlondon
[14:54] <secretlondon> hi james_w
[14:56] <Pres-Gas> james_w: I see your mod of the ticket, thanks.  I will follow up on that ticket tonight
[14:56] <Pres-Gas> I assume that you are now subscribed to it?
[14:56] <james_w> afflux: http://directory.fsf.org/project/gcin/
[14:56] <james_w> I think I did, yes
[14:56] <secretlondon> debian has http://packages.debian.org/sid/checkgmail 13-2, we have 13-1
[14:56] <Pres-Gas> or should I ping you here, james_w
[14:56] <afflux> james_w: now check the "homepage" link
[14:57] <secretlondon> changelog just a desktop file though
[14:57] <james_w> afflux: check the "development" tab
[14:57] <james_w> I current link directly to it
[14:57] <secretlondon> no quick fix - bah!
[14:57] <afflux> tab? huh
[14:57] <james_w> sorrry, I couldn't link directly to it
[14:57] <afflux> ah, javascript
[14:58] <james_w> secretlondon: yeah, the .desktop is from Ubuntu anyway I expect
[14:58] <secretlondon> yeah ;)
[14:58] <james_w> secretlondon: in the second bug I pasted it explains why it isn't fixed in Debian.
[14:58] <secretlondon> no debbugs that refer
[14:58] <secretlondon> ok
[14:58] <james_w> it is an easy fix though
[14:58] <secretlondon> I always try and check debian when we use their packaging
[14:58] <secretlondon> cool :)
[14:58] <afflux> james_w: okay, I'll write an email... Hope that wont get lost, I'd like to see a real bug tracker *mumble*
[14:59] <afflux> oh, it has a trac o.o
[14:59] <james_w> ooh, where?
[14:59] <afflux> that was hidden :)
[14:59] <afflux> the VCS link
[14:59] <james_w> Pres-Gas: yes, I'm subscribed, you can see the list on the left of the bug
[14:59] <afflux> but you can't register and you can't open tickets... *!$!"§%
[15:00] <secretlondon> arrgh
[15:00] <secretlondon> I was trying to explain to $upstream why having it's own bts (rather than using debians) would be cool..
[15:01] <secretlondon> some upstreams just prefer an email though
[15:03] <afflux> quodlibet is like that, too
[15:03] <afflux> they have a full trac, with wiki and svn and stuff, and everything links to that, but they still use their ML for bugs. (the ticket system is closed)
[15:04] <secretlondon> catterly, Bug #151226 too
[15:04] <ubotu> Launchpad bug 151226 in checkgmail "Synaptic recommends libsexymm2, which is useless (missing Perl bindings)" [Undecided,New] https://launchpad.net/bugs/151226
[15:04] <catterly> oh boy
[15:05] <secretlondon> its all really the same issue
[15:06] <catterly> yeah I guess, which is the "master" bug though
[15:07] <secretlondon> bug #68671, even bug #157436
[15:07] <ubotu> Launchpad bug 68671 in checkgmail "should depend on libcrypt-simple-perl" [Undecided,Confirmed] https://launchpad.net/bugs/68671
[15:07] <ubotu> Launchpad bug 157436 in checkgmail "package checkgmail 1.12-1ubuntu1 failed to install/upgrade: " [Undecided,New] https://launchpad.net/bugs/157436
[15:07] <catterly> gahh
[15:08] <catterly> alright, I can sort these out I think, however I think the libcrypt should be one, and libsexy another
[15:08] <secretlondon> sure
[15:08] <catterly> because libcrypt just needs to be recommended/req'd, but sexy is broken apparently
[15:08] <qense> jcastro: are you available now?
[15:09] <secretlondon> arrgh bug #155594 is the libsexy bug
[15:09] <ubotu> Launchpad bug 155594 in checkgmail "Checkgmail doesn't start" [Undecided,Incomplete] https://launchpad.net/bugs/155594
[15:09] <secretlondon> the same issue displays itself in different ways ;)
[15:10] <jcastro> qense: yep!
[15:10] <qense> ok
[15:10] <jcastro> qense: give me a minute or so to clear my schedule
[15:10] <secretlondon> yet people are reporting other probs with the package so it must start for some people ;)
[15:12] <qense> ok. I'm curious to your ideas :) But I've already mailed the mailinglists of freedesktop, libmtp and mtps before I read your mail.
[15:12] <secretlondon> catterly the 'other' bug with this package seems to be a localisation issue
[15:13] <secretlondon> one of the best bits of bug triage (for me) is identifying the same underlying issue in it's different presentations :)
[15:15] <james_w> I agree that there are two bugs, but the libsexy one is harder to solve.
[15:15] <james_w> you could open a [needs packaging] bug for the perl bindings and point it there.
[15:16] <james_w> ah, https://bugs.launchpad.net/ubuntu/+bug/151564
[15:16] <ubotu> Launchpad bug 151564 in ubuntu "[Wish] Please include Gtk2::Sexy Perl bindings into Ubuntu" [Wishlist,Triaged]
[15:17] <jcastro> qense: yeah, I have found that "general" blasting to maintainers and/or lists isn't really effective
[15:18] <qense> ok
[15:18] <jcastro> which is why heno felt it would be useful for me to be more involved in hug days
[15:18] <sroecker> hi
[15:18] <sroecker> asac, are you online?
[15:18] <catterly> phew alright, thanks james_w, secretlondon
[15:18] <jcastro> so when an upstream hug day happens we can (hopefully) get some participation from upstreams and then we can work together with them on bugs.
[15:18] <qense> yeah, if we can 'forward' the bug day also upstream, I think it can have a lot more ffect :)
[15:19] <jcastro> and get a working relationship going
[15:19] <jcastro> let me dig up a chart for you
[15:19] <james_w> the Amarok one was a great success wasn't it?
[15:19] <jcastro> james_w: yeah the wolf brigade is pretty rocking
[15:19] <jcastro> qense: https://edge.launchpad.net/ubuntu/+upstreamreport
[15:20] <jcastro> those are the top packages in ubuntu, sorted by open bugs
[15:20] <jcastro> the watch % column (second to last) basically shows how well we do linking bugs to upstream trackers
[15:20] <james_w> ah cool
[15:20] <james_w> poor mvo
[15:21] <jcastro> james_w: heh, yeah
[15:21] <seb128> jcastro: GNOME rocks there ;-)
[15:21] <qense> yes, it quite does :)
[15:22] <jcastro> seb128: yes, by a long shot.
[15:22] <jcastro> seb128: that's because you guys are heroes.
[15:22] <qense> we could try to mail the upstream contacts with a request
[15:22] <jcastro> qense: so one thing specifically bdmurray and I were looking at
[15:22] <seb128> we try our best, and we have some rocking contributors ;-)
[15:23] <jcastro> was bugs where people paste in an upstream bug tracker but don't bother to link it in launchpad.
[15:23] <jcastro> basically, the linking part isn't discoverable, etc, but they will fix that.
[15:23] <jcastro> in the meantime bdmurray has a query he runs that shows us these bugs, I was thinking that we could generate a page of these, and target 5-a-day people to do the linking
[15:23] <qense> that would indeed be nice
[15:23] <jcastro> since they're real easy to fix
[15:24] <jcastro> that would directly affect the numbers on the upstream report and get us more green boxes.
[15:24] <jcastro> the upstream contact field is also something that is generally not used, so we need to think about how to fix that
[15:25] <jcastro> the general concensus seems to be "someone who is involved upstream and uses ubuntu"
[15:25] <jcastro> pure upstream developers don't seem to be keen on being the contact. (General observation)
[15:26] <jcastro> If we can form teams around specific upstreams of people who are interested in forwarding bugs upstream, that would be a huge help.
[15:26] <jcastro> Like how the amarok people do it.
[15:26] <seb128> jcastro: do we have an easy way to give upstream guys control on the bugs for the corresponding package in ubuntu.
[15:26] <seb128> ?
[15:26] <qense> But what we need to do is get the upstream maintainers to send us a list with information to help us with checking bug reports for completecy
[15:26] <jcastro> seb128: no, ongoing issue.
[15:26] <asac> sroecker: yeah
[15:26] <seb128> ok
[15:26] <sroecker> asac, what patch system does network-manager use?
[15:26] <jcastro> seb128: for example if I were a pidgin guy and wanted to change the status of a lp bug I can't. But we can fix that manually.
[15:27] <seb128> how?
[15:27] <jcastro> seb128: It's something I will bring up with bdmurray when he returns from holiday
[15:27] <seb128> ok
[15:27] <sroecker> I have an atheros base wlan chip and newest network-manager can't connect to my hidden net
[15:27] <jcastro> seb128: he can manually add someone to give them permission
[15:27] <jcastro> but there's no general "Hi I am upstream I would like to manage ubuntu bugs about my project" button.
[15:27] <seb128> well, they are added to the bugsquad and can edit any ubuntu bug then, no?
[15:27] <sroecker> I works manually with AP_SCAN=1, so I want to try that
[15:27] <jcastro> yes, exactly
[15:29] <Pres-Gas> Okay, can anyone tell me the purpose of #ubuntu-laptop?
[15:30] <asac> sroecker: quilt
[15:30] <Pres-Gas> I tried to talk about forward momentum of 200064 to them and they seemed rather rude IMHO
[15:30] <asac> (with cdbs)
[15:30] <asac> sroecker: which package version?
[15:30] <jcastro> qense: my short term focus is going to be getting upstreams involved in hug days, and then participating in them, forwarding bugs upstream, etc.
[15:31] <asac> sroecker: test 0.6.6-0ubuntu4 first please
[15:31] <sroecker> asac, I have
[15:31] <asac> sroecker: otherwise file a bug with summary [ath_pci] cannot connect to hidden
[15:31] <qense> but how are we going to gather the triage data and are we going to keep the DebuggingProcdedures page or move it all to a new page?
[15:31] <sroecker> k
[15:31] <asac> sroecker: please attach your complete syslog after connect attempt
[15:32] <qense> WE can ask at hug days the involved packages for this
[15:32] <qense> We*
[15:32] <jcastro> qense: well, I am going to update this page here: https://wiki.ubuntu.com/Bugs/Upstream
[15:32] <jcastro> which are basically guides for each big upstream on how to forward bugs
[15:33] <qense> you could add e.g . Bugs/Triaging/GNOME to the GNOME page
[15:33] <jcastro> yeah
[15:33] <qense> but the pages should get some content
[15:33] <qense> and how are we going to get that?
[15:34] <jcastro> we have to write them. :D
[15:34] <asac> sroecker: please give me bug id
[15:34] <jcastro> also, I think it would be good to check with each upstream to make sure the info we put on there is correct.
[15:35] <james_w> what's the page that has all bugs without a package on?
[15:35] <qense> we can ask all projects to extend their triaging page at their bug days
[15:36] <qense> and what about basic information like ubuntu version and package information?
[15:36] <qense> or architecture
[15:36] <qense> should we put that everytime again on the specific pages or just once at the main page and remind them at the specific pages
[15:37] <james_w> qense: I don't understand what you mean
[15:37] <jcastro> qense: I think we should just link to the packaging information page on lp.
[15:37] <qense> I mean information about the bugs, the version of ubuntu and program you're using
[15:38] <jcastro> oh, how they can get the information for their bug report you mean?
[15:38] <qense> I mean the information required for all bug reports
[15:39] <qense> sould we put it once at the main page with the risk that people might forget it or everytime at the specific bug triaging pages, which will cost a  lot of extra work and space
[15:39] <jcastro> I think it should be on the general page, and keep the upstream-specific pages with just details on how different upstreams do things
[15:40] <qense> yeah, that sounds as the best option to me too
[15:40] <sroecker> asac, bug #208306
[15:40] <ubotu> Launchpad bug 208306 in network-manager "[ath_pci] cannot connect to hidden ap" [Undecided,New] https://launchpad.net/bugs/208306
[15:41] <qense> ok, I think we also should decide what to do with DebuggingProcedures and the information on it
[15:41] <qense> should we copy it or link to it
[15:41] <qense> inclusion, like I suggested at the mailinglist, doesn't work
[15:42] <jcastro> I think linking to it would be sufficient
[15:42] <james_w> I think you can include pages using Moin, so you can have each specific page include the general stuff if you want
[15:42] <jcastro> can you include just sections of a page in moin?
[15:42] <qense> for inclusion you need to install macro
[15:42] <james_w> no, I don't think so
[15:43] <james_w> it works on wiki.u.c, ask dholbach, he uses it for the packaging guide
[15:44] <qense> I've just got three things that need to be include by default: ubuntu version, arch and package version. Is anything else needed?
[15:44] <james_w> is it reproducible every time?
[15:45] <qense> good one
[15:45] <jcastro> find out what apport reports, it seems to be complete
[15:46] <james_w> https://wiki.ubuntu.com/PackagingGuide/Complete?action=raw
[15:46] <secretlondon> qense some packages need their own log files
[15:46] <james_w> that has "[[Include(PackagingGuide/Intro/General)]]"
[15:46] <jcastro> Ah, so basically we should just split up debugging procedures and include them everywhere else
[15:46] <secretlondon> the main bug squad page has an included header
[15:47] <qense> I really have to go now. :( I'm going to try to mail some more upstream maintainers this weekend, if you need me don't hestitate to mail me
[15:47] <qense> bye
[15:47] <secretlondon> bye
[15:47] <secretlondon> good work!
[16:06] <sroecker> asac, when I add a patch like the 42b_fix_ap_scan_hidden.patch ipw2200 patch for ath_pci I can connect to the hidden ap
[16:10] <asac> sroecker: if possible upload a bzr branch
[16:10] <asac> or paste the path :)
[16:10] <asac> patch
[16:20] <james_w> https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/200527
[16:20] <ubotu> Launchpad bug 200527 in yelp "声卡无驱动" [Undecided,New]
[16:20] <james_w> anyone able to translate that?
[16:25] <sroecker> asac, I just added this http://paste.ubuntu-nl.org/61380/ to 42b_fix_ap_scan_hidden.patch before the else if
[16:54] <bcurtiswx> i am nowhere near good with programming. but i want to help manage bugs so they can be taken care of in a timely manner.. how can i "officially" become involved? im part of the bugs mailing list
[16:54] <afflux> bcurtiswx: hanging around here and maybe in #ubuntu-bugs-announce is a good place to start
[16:55] <Tuv0k> bcurtiswx, check the website
[16:55] <Tuv0k> "how to get involved"
[16:55] <afflux> bcurtiswx: this wiki page gives you a lot of information on how to triage bugs: https://wiki.ubuntu.com/Bugs/HowToTriage
[16:56] <bcurtiswx> how do i private message like everyone.. is it /msg?
[16:56] <Tuv0k> bcurtiswx, http://www.google.com/search?q=ubuntu+how+to+get+involved&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:unofficial&client=firefox-a
[16:57] <afflux> yes. Note that usually people don't like being queried by unknowns, just highlight them by saying their name in the channel.
[16:58] <bcurtiswx> ah ok
[16:58] <bcurtiswx> afflux, this is a test
[16:58] <bcurtiswx> thx
[16:58] <afflux> working ;)
[16:59] <bcurtiswx> im used to mIRC so please don't mind the noobie-ness with xchat
[17:00] <afflux> bcurtiswx: no problem. Note that you can still query people by doubleclicking on their name on the right hand user list. It's just that it's preferred to do this in the channels, if it's on-topic.
[17:19] <sroecker> asac, I think my Bug 208306 is the same as Bug 200950, missing scan_capa
[17:19] <ubotu> Launchpad bug 208306 in network-manager "[ath_pci] cannot connect to hidden ap" [Undecided,New] https://launchpad.net/bugs/208306
[17:19] <ubotu> Launchpad bug 200950 in linux-ubuntu-modules-2.6.24 "[iwl3945] network manager not able to associate to hidden SSID (scan_capa = 0x0)" [High,Fix committed] https://launchpad.net/bugs/200950
[17:27] <asac> sroecker: yes
[17:27] <asac> sroecker: please don't merge them
[17:27] <asac> sroecker: they are not the same, because they deal with different chipsets
[17:29] <sroecker> asac, ok
[17:33] <afflux> what does an application need to show up in alacarte?
[17:34] <afflux> just a desktop file in usr/share/applications?
[17:34] <pochu> I think so
[17:54] <afflux> where can I find logs from gnome-settings-daemon when it's not starting?
[18:02] <james_w> afflux: ~/.xsession-errors might have it
[18:08] <afflux> okay, thanks
[18:11] <seb128> afflux: logs are usually not useful, get a stacktrace
[18:13] <afflux> seb128: I'm not sure if it's crashing: http://launchpadlibrarian.net/12950962/Screenshot-x-session-manager.png
[18:14] <seb128> afflux: run gnome-settings-daemon on a command line and see what it's written there
[18:14] <afflux> seb128: jep, that's what I asked for. thanks!
[18:14] <afflux> *him
[21:50] <marnanel> How do I mark a bug in launchpad as being the same as a bug in the upstream tracker?
[21:51] <marnanel> oh wait
[21:51] <marnanel> I found it, I think
[21:51] <secretlondon> you make a link - also affects project
[21:52] <marnanel> oh, hello there
[21:53] <secretlondon> hi
[21:54] <marnanel> so, I am talking about bug 106903
[21:54] <ubotu> Launchpad bug 106903 in gnome-alsamixer "error message when gnome-alsamixer is launching" [Undecided,New] https://launchpad.net/bugs/106903
[21:54] <marnanel> this is identical to http://bugzilla.gnome.org/show_bug.cgi?id=429012
[21:54] <ubotu> Gnome bug 429012 in general "Sound Blaster Live 5.1  - `,' an invalid character for SigmaTel_STAC9708,11" [Normal,Assigned]
[21:55] <marnanel> (which I have submitted a working patch for)
[21:55] <marnanel> someone has pointed this out in the comments on LP
[21:55] <marnanel> but it doesn't have the thing in the header of that page which says "upstream bug" and gives its status
[21:56] <marnanel> just posting a link should do that?
[21:56] <secretlondon> i'm just loading it
[21:56] <marnanel> sure, no hurry
[21:56] <secretlondon> but you should click on "also affects project" then choose gnome-alsamixer and give the link to the upstream bug tracker
[21:58] <secretlondon> "There is no project in Launchpad named "gnome-alsamixer". Please search for it as it may be registered with a different name"
[22:00] <secretlondon> it looks like gnome-alsamixer needs registering as a project first
[22:02] <secretlondon> I presume alsautils is the wrong package, that's the only hit for alsamixer
[22:05] <marnanel> I am confused, then.  How come it says "Bug #nnnnnn in gnome-alsautils" if gnome-alsautils isn't a project?
[22:05] <catterly> could someone explain a general question, I am just wondering why a bug fix seems to often require updates to multiple packages (judged by 2-4 things having the same text in the "changes" field.)
[22:05] <secretlondon> it isn't a project registered by itself (I think), it's gnome-alsautils in Ubuntu
[22:05] <catterly> is it that code is duplicated throughout different packages?
[22:05] <sistpoty> hi, just a small side note, since I've seen that from jelmer right now: please don't mark bugs as duplicates to FreezeExceptions (we might set the exception to invalid, if we reject it, but of course the duplicate (real) bug shouldn't be invalid then)... thanks!
[22:06] <marnanel> oh, I see-- it's the Ubuntu package of that name, not a launchpad project
[22:06] <secretlondon> marnanel yep
[22:06] <secretlondon> I think we'll have to make a launchpad project ofr that name first
[22:06]  * marnanel thinks I will be perilously close to volunteering as the maintainer if I fix bugs *and* set up launchpad :)
[22:07] <secretlondon> marnanel, I'll do it as a bugsquad member...
[22:07] <marnanel> okay, sure
[22:07] <marnanel> oh, would you?
[22:07] <marnanel> thanks a bunch
[22:07] <secretlondon> yeah sure
[22:07] <james_w> marnanel: it just needs a pointer setting to say that it uses the gnome bugtracker I think
[22:07] <james_w> secretlondon: is that correct?
[22:07] <secretlondon> james_w it's not letting us link to upstream bugs
[22:08] <secretlondon> as "also affects project" doesn't know of gnome-alsamixer
[22:08] <james_w> secretlondon: yeah, I mean the bit about creating the upstream project for gnome-alsamixer
[22:08] <james_w> do you have to create a whole project, or is there a shortcut for when we just want to link bugs?
[22:09] <secretlondon> I hope i've found a shortcut
[22:09] <marnanel> I mailed the maintainers yesterday, but since last checkin was two years ago I suspect this is an abandoned project anyway
[22:10] <secretlondon> well it's done it
[22:12] <secretlondon> james_w I think it made me make a new project
[22:12]  * secretlondon hopes they are not counted as "# of projects that are registered in launchpad" or something
[22:12] <marnanel> AWESOME.  Thank you
[22:13] <secretlondon> marnanel, no problem :)
[22:13] <james_w> great
[22:13] <james_w> marnanel: do you want to get your patch in to Hardy?
[22:14] <james_w> secretlondon: https://blueprints.launchpad.net/gnome-alsamixer/ is a bit odd
[22:14]  * secretlondon looks
[22:15] <secretlondon> what's odd?
[22:15] <secretlondon> the fact that it would take any?
[22:16]  * secretlondon didn't do anything to do with blueprints, answers or anything else
[22:16] <james_w> the fact that you are listed as a driver
[22:16] <secretlondon> argh
[22:16] <secretlondon> https://edge.launchpad.net/gnome-alsamixer/ says it doesn't use anything
[22:18] <james_w> but if you click on the blueprints tab your name is there
[22:18] <secretlondon> yeah,  I can see "Since you are a driver of Gnome Alsamixer, any items you propose will be accepted automatically."
[22:18] <catterly> hmm before I mark as a duplicate, can I get a vote of agreement for bug #203423 being a dup bug #195159?
[22:18] <ubotu> Launchpad bug 203423 in ubiquity "Timezone map zooming is too sudden and disorienting" [Undecided,New] https://launchpad.net/bugs/203423
[22:18] <ubotu> Launchpad bug 195159 in ubiquity "The new time zone / city choosing is annoying" [Medium,Confirmed] https://launchpad.net/bugs/195159
[22:18] <james_w> ah, ok
[22:19] <secretlondon> james_w so what to do? that was the only way it allows you to link upstream afaik
[22:20] <james_w> secretlondon: yeah, you did the right thing, I was just commenting that it was odd it made you a driver for blueprints for that project now.
[22:20] <james_w> it's a bug in launchpad in my opinion
[22:20] <secretlondon> I agree
[22:20] <james_w> catterly: yeah, they're duplicates
[22:21] <catterly> james_w: thanks, just wanted to make sure :]
[22:21] <james_w> no problem
[22:32] <mrooney> what is the proper thing to do in a case such as bug #208512, I tried to leave a good comment. it seems logical to mark as invalid however that seems rude to new launchpad users and might push them away. hmm!
[22:32] <ubotu> Launchpad bug 208512 in ubuntu "hardy 6 firefox beta is too buggy to use" [Undecided,New] https://launchpad.net/bugs/208512
[22:35] <james_w> yeah, I think invalid is correct, but I would spend some time to explain that the bugs he has filed will have been looked at, and that there will likely be more firefox updates before the final release that may fix them.
[22:36] <james_w> I would also say that one of the reasons it is included even though it is beta is to increase testing and to find out all of these issues.
[22:36] <james_w> and also that if it is decided that it really is too buggy the default can be changed back to firefox 2 very easily.
[22:37] <mrooney> james_w: okay, thanks again for your expertise!
[22:39] <mrooney> there is just so much to learn
[22:39] <james_w> mrooney: I think you had the right instinct though
[22:40] <secretlondon> always.. we'll never know it all
[22:59] <Dat1> Hi all, I have a question on bug 183209
[22:59] <ubotu> Launchpad bug 183209 in update-manager "doesn't let user examine installation process any more" [Medium,Fix released] https://launchpad.net/bugs/183209
[22:59] <Dat1> this bug was marked "fix released" although it still exists.
[22:59] <Dat1> So normally I would just change its status back to confirmed
[23:00] <Dat1> But this bug was milestoned hardy-beta, and I am not sure if it will be milestoned automatically again after changing the status
[23:00] <Dat1> I do not want to mess up the beta-milestone
[23:04] <sistpoty> Dat1: milestone's are always set by hand, so don't worry about that
[23:06] <sistpoty> Dat1: the interesting question is more, if you can confirm it (happens for you as well), as there's only one person saying that its still present after beta (so it would be new imho, instead of confirmed
[23:06] <sistpoty> +)
[23:24] <Dat1> sistpoty: thanks for your answer. I can actually confirm it ;)
[23:24] <sistpoty> :)