[00:05] <hggdh> bdmurray, already sent it to ogasawara, did not notice he was online
[00:05] <hggdh> thanks for the follow up
[00:06] <mrooney> can bugsquad edit descriptions/titles of bugs, or only bugcontrol?
[00:06] <nhandler> Anyone is able to edit bug descriptions/titles mrooney
[00:06] <bdmurray> mrooney: any one
[00:08] <mrooney> ah, thanks :)
[00:08]  * mrooney is responding to a bug control application
[00:09] <nhandler> Who is the application for mrooney ?
[00:10] <mrooney> not yours :)
[00:10] <jjesse> wow havent checked ubuntu bug mail, holy messages from launchpad batman
[00:11] <nhandler> mrooney: I already got approved for Bug Control ;)
[00:11] <mrooney> nhandler: I figured! You had like 6 raving reviews :)
[00:11] <mrooney> I would have added one but it seemed like overkill at that point
[00:12] <nhandler> lol mrooney.
[00:12] <mrooney> But I am replying to Marcus's now
[04:05] <mrooney> bdmurray: around by any chance?
[04:11] <anakron> Hi all
[04:40] <bdmurray> mrooney: what's up? I've got a minute or two to spare
[04:41] <mrooney> bdmurray: oh hi, I just found a bug that I thought might be up your alley
[04:41]  * mrooney searches...
[04:41] <mrooney> bdmurray: bug 256071
[04:44] <bdmurray> mrooney: hmm, I can't recreate it with intrepid
[04:45] <bdmurray> It might actually be firefox-launchpad-plugin not firefox
[04:47] <bdmurray> mrooney: do you have that installed?
[04:48] <mrooney> bdmurray: I don't know, this isn't the same machine I confirmed it on, I just did a sudo aptitude install firefox-2, so if it isn't depends or stock hardy, I don't think
[04:48] <bdmurray> hrm
[04:49] <mrooney> bdmurray: so you were using firefox 2 in Intrepid?
[04:49] <mrooney> maybe it was fixed there and the patch wasn't sent back
[04:50] <bdmurray> mrooney: okay, I'll look at it more tomorrow.  thanks!
[05:13] <pheeror> is anybody working on fixing those minor flaws in intrepid dark theme?
[05:15] <persia> pheeror: You might check with #ubuntu-artwork, but I suspect so.
[05:19] <pheeror> the dark theme looks unbeatable with bunch of green-on-black terminals, gutsy-elephant-skin background on top of a old-fashioned thinkpad  :-)
[05:22] <greg-g> that was an easy bug to mark as fix released.
[05:29] <mrooney> greg-g: which one is that?
[05:36] <greg-g> mrooney: https://bugs.launchpad.net/bugs/257178
[05:37] <greg-g> actually, now that I think about it, I wonder if we could backport it (or apply a patch that will make it work) for hardy
[05:40] <persia> Probably.  Failure-to-install is often considered SRU-worthy (as it breaks upgrades)
[05:41] <greg-g> persia: well there we go.  I've never dealt with that kind of request, what is the next (first) step?
[05:41] <persia> greg-g: There are two interesting paths: the bugfix and the bug management.
[05:41]  * greg-g looks for the SRU wiki page
[05:42] <persia> Taking the latter first, you'll want to redescribe the bug in terms of test case, etc.  Also, you'll want a Hardy task to track the status in Hardy.
[05:42] <greg-g> persia: ok
[05:43]  * greg-g changes description to include test case
[05:43] <persia> Next, you'll want to investigate the bugfix.  I'm guessing it's available (in part) from the debdiff between 0.825 and 0.826.  Get someone to backport that to 0.822.
[05:43] <persia> After that, you just need a developer to upload, and someone to organise testing once it hits the SRU queue.
[05:45] <greg-g> persia: awesome.  good overview, thanks.
[05:48] <persia> greg-g: Just in case you haven't already looked there, snapshot.debian.net can be a handy way to check specific changes in Debian packages.
[05:49] <greg-g> persia: ooo, I haven't seen that before, thanks again.
[05:56] <greg-g> from a quick look at the changelog, it looks like all that is needed is a change for the build depends to use cdd-dev >=4.7 from 4.4
[05:56] <greg-g> but, Hardy only has 4.4
[05:56] <greg-g> hrmm
[05:57] <persia> greg-g: Next would be to see what the change was for cdd-dev 4.7
[06:01] <greg-g>   * Build-Depends: cdd-dev (>= 0.4.7)
[06:01] <greg-g>     Reason: The change in cdd to enable builds of Arch any for some CDDs leaded to the error that postinst/postrm files now contained
[06:01] <greg-g>     two copies of the same code.  This is fixed in cdd-dev 0.4.7 and thus debian-edu has to be rebuilded.
[06:02] <greg-g> that is why, I can dig deeper and see exactly what needs to change in cdd-dev to get that fix and only that fix
[06:02] <persia> So the problem is really in cdd-dev: debian-edu just needs a rebuild for a fixed cdd-dev.
[06:02] <greg-g> s/that is why,/that is the why./
[06:02] <greg-g> right
[06:03] <persia> Right.  The next step would be to identify the specific fix.  At about this level of specificity, it's a good idea to either get a developer who is going to work on it, or decide to be that developer yourself.
[06:03] <persia> Otherwise, you've just agressively triaged the bug, and with appropriate comments, it ought be easy for a developer to pick it up, approve the Hardy task, and chase the SRU team.
[06:05] <greg-g> I would love to be that developer myself.  We'll see how far I can get into figuring out the changes needed
[06:06] <greg-g> so, I guess I should change the affected package to cdd and re-tool the description.
[06:10] <persia> greg-g: Well, no.  You'll want to add a cdd task, as there are two packages that need to be adjusted.
[06:11] <greg-g> ok
[06:11] <greg-g> good thing I was looking at the diff of cdd rather than messing with the bug
[06:11] <greg-g> the diff is really small for cdd_0.4.4 to 0.4.7
[06:12] <persia> greg-g: Also, just as a note, when you get to the point that you know what patch you want to apply, if you're the developer, #ubuntu-motu is the place to chat about getting it applied.
[06:13] <greg-g> right right
[06:13] <persia> This being a good place for bug report through patch, but after that, it becomes less interesting to some people.
[06:13] <greg-g> thanks for the guidance persia
[06:13] <persia> greg-g: Thanks for chasing and fixing the bug :)
[06:14] <greg-g> 'tis what I'm here for ;)
[06:18] <kgoetz> hi all. i'm about to make a debdiff to https://bugs.launchpad.net/ubuntu/+source/clearsilver/+bug/86685 and i was wondering what i'm meant to tag it after i do so. is it ubuntu-universe-sponsors still?
[06:19] <nellery> kgoetz, have a look at the tags page here: https://wiki.ubuntu.com/Bugs/Tags
[06:19] <kgoetz> nellery: cheers
[06:19] <nellery> no problem :)
[06:20] <kgoetz> :)
[06:20] <persia> kgoetz: For a debdiff, the tags aren't so important, and #ubuntu-motu is probably a better forum.
[06:20] <persia> Specifically, if you seek sponsorship, you need to subscribe ubuntu-universe-sponsors
[06:21] <kgoetz> persia: thanks
[06:43] <dholbach> good morning
[06:45] <greg-g> morning dholbach
[06:45] <dholbach> heya greg-g
[06:55] <kgoetz> persia: thanks, i've subscribed u-u-s
[12:25] <Achim> hello I don't know if this is the right place but I would like to know if someone can help me with a bug report.
[12:25] <Achim> My problem is that there is a patch and a debdiff (hardy) available and nobody seems to be interested.
[12:25] <Achim> Maybe I have done something wrong?
[12:25] <Achim> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/253587
[12:26] <Achim> ubottu, hey nice to see someone is taking care about this report.
[12:27] <Achim> okay
[12:29] <techno_freak> Achim, as the bug is confirmed someone will look into the patch and test it out
[12:30] <Achim> techno_freak, I have confirmed the bug. At the moment it is more like a monologue.
[12:30] <techno_freak> Achim, it takes some time for people to respond, if not you can poke people back here after a few days
[12:30] <techno_freak> :)
[12:31] <techno_freak> Achim, and ubottu is a bot, it gives you information, especially on bugs when you specify `bug <number>` to it
[12:31] <persia> Achim: As you've a debdiff attached, you may want to subscribe the relevant sponsors queue (only the debdiff author should do this).  In this case, it is ubuntu-main-sponsors.
[12:34] <Achim> I am the debdiff author. but I am not subscribed to the sponsors queue. Maybe I will take a look at the ubuntu-main-sponsors.
[12:39] <persia> Achim: Rather, subscribe the bug to the sponsors queue.  You don't want to be a sponsor, you want one of the sponsors to notice your bug.
[12:39] <persia> You can ask more questions about getting sponsorship in #ubuntu-motu
[12:40] <Achim> thanks for your help.
[14:14] <mcas_away> hellp
[14:14] <mcas_away> hello
[14:14] <mcas> can someone please look at bug 257255
[14:15] <mcas> i think this could be set to triaged
[14:16] <pedro_> mcas: if you reproduce it and can confirm, yes it could be triaged
[14:18] <mcas> i thought that if i can confirm it it could be set to confirmed...
[14:19] <pedro_> so are you setting things to triaged without verified if that's a valid report?
[14:19] <mcas> i have no rights to set it triaged
[14:20] <pedro_> m? why not?
[14:20] <mcas> because i am not member of bug control
[14:20] <pedro_> mcas: please send an email to the bug control mailing list if you want to
[14:20] <pedro_> I've seen you working in a lot of bugs
[14:21] <pedro_> i thought you had the permissions
[14:21] <mcas> i sent the mail a few days ago and today i got an answer from mrooney
[14:21] <mcas> he wants to see some more bugs
[14:21] <pedro_> mcas: https://wiki.ubuntu.com/UbuntuBugControl <-
[14:21] <mcas> i wrote him a new email wiht some more bugs
[14:22] <pedro_> alright i haven't looked to the list...
[14:23] <mcas> there were problems with the list administration so i sent the new mail directly to mike
[14:23] <mcas> the other mail was sent directly to brian
[14:27] <mcas> so pedro_ about this special bug.. i thought if i set it to triaged the bug report has all information needed and confirmed is set if i can reproduce the problem
[14:27] <mcas> please correct me
[14:27] <mcas> pedro_: because i am not sure with this i am asking here ;-)
[14:29] <pedro_> mcas: yes, that's correct
[14:30] <mcas> i think we have all informations about this bug, but i can't reproduce it with my 128mb usb stick
[14:30] <mcas> there i have an fat16 header
[14:31] <pedro_> well in that case i prefer to not set that to triaged and wait for someone to confirm it first
[14:32] <pedro_> it could be a non valid report
[14:33] <mcas> ok
[14:39] <bddebian> Boo
[14:42] <pedro_> buu
[14:42] <bddebian> :-)
[14:48] <tuxmaniac> can someone help with triaging this bug 123765. I think it isnt a valid bug since US keyboard settings works fine and in Brazilian KBD settings the " and ' could be mapped to some other key.
[14:48] <tuxmaniac> oops missed out the "please"
[14:48] <tuxmaniac> :)
[17:20] <bdmurray> pedro_: bug 257347 is my gnome-terminal crash
[17:20] <emgent> bdmurray: can you subscribe me too ?
[17:21] <bdmurray> emgent: you should be able to see it based on being in bugcontrol
[17:21] <pedro_> bdmurray: ok, thanks
[17:21] <emgent> bdmurray: i cant.
[17:21] <pedro_> mm i'm getting a "Not allowed here"
[17:21] <emgent> Not allowed here
[17:21] <emgent> Sorry, you don't have permission to access this page.
[17:21] <emgent> You are logged in as Emanuele Gentili.
[17:22] <bdmurray> I'm looking into it
[17:22] <bdmurray> Oh right the retracer hasn't gotten to it yet
[17:24] <bdmurray> pedro_: you are subscribed now
[17:24] <pedro_> there's no hurry we can wait ;-). btw based on your description of yesterday it could be a dup of bug 256769
[17:24] <pedro_> bdmurray: rock will look
[17:25] <pedro_> yes it indeed looks like a dup of it, will wait for the retrace just in case of
[17:25] <pedro_> thanks bdmurray
[17:26] <bdmurray> pedro_: thanks for pointing me at the master
[17:28] <bdmurray> pedro_: for a while I've no places "run" menu item and pressing alt+f2 does nothing what package would that be?
[17:29] <bdmurray> bug 257323
[17:30] <hggdh> wow, cool
[17:30] <bdmurray> maybe some chemicals on the CD?
[17:30] <pedro_> bdmurray: ah that's gnome-panel
[17:30] <bdmurray> pedro_: hmm, I wonder why it is missing then
[17:31] <pedro_> bdmurray: are you running intrepid? it's working for me with it
[17:31] <hggdh> perhaps, but it is doubtful... more probably the unit burnt something (a capacitor?)
[17:32] <bdmurray> pedro_: it's been like this since Hardy at least
[17:34] <pedro_> bdmurray: maybe something else is disabling the keys?
[17:35] <pedro_> ie: bug 200540
[17:35] <bdmurray> maybe but the menu item doesn't even show up
[17:38] <pedro_> bdmurray: ah that's ok, the Run application menu was removed during the 2.11.X cycle IIRC
[17:53] <chrisccoulson> not sure how to respond to this: https://bugs.edge.launchpad.net/ubuntu/+bug/257323
[17:53] <chrisccoulson> :S
[18:04] <hggdh> chrisccoulson, the only options I can imagine are: (1) a really, really, bad CD (but it should have smoked a LOT when burning), or a faulty drive
[18:06] <chrisccoulson> yeah, thanks for that. it's very unfortunate that it happened with his Ubuntu CD
[18:13] <chrisccoulson> we spoke about this bug a little while ago on here because I wasn't sure what other information to ask from the reporter: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/240437
[18:14] <chrisccoulson> james_w made the suggestion of monitoring dbus activity as a start, but I said I was unsuccessful with this when I tried it on my machine, and then it all went a bit quiet I think
[18:14] <chrisccoulson> i tried contacting the developer of system-tools-backends to see if he had any suggestions, and i got no response :?
[18:15] <chrisccoulson> and now a second person is claiming that they are seeing the same behaviour
[18:15] <chrisccoulson> any ideas?
[18:15] <hggdh> another one??
[18:15] <hggdh> then chances are faulty CD disk
[18:15] <hggdh> a faulty batch of them
[18:15] <chrisccoulson> i suppose that could be a possibility
[18:16] <chrisccoulson> it would be nice to be able to debug this though, just in case there might be something else
[18:16] <hggdh> chrisccoulson, one chance would be to verify when the CD requests were made, and try to backtrack to a CD disc batch
[18:17] <hggdh> then get one of these CD discs, and try on
[18:17] <chrisccoulson> ah! i think we're confused now
[18:17] <chrisccoulson> i'm talking about a different bug;)
[18:17] <hggdh> well, I am
[18:17] <chrisccoulson> https://bugs.edge.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/240437
[18:17] <chrisccoulson> ^^^that one;)
[18:17] <hggdh> completely different...
[18:18] <hggdh> let me see this one... blame my old age
[18:18] <chrisccoulson> lol
[18:18] <chrisccoulson> it was discussed on here a few weeks ago, and then it went a bit quiet
[18:18] <chrisccoulson> and now a second person is saying that users-admin trashes their /etc/passwd file as well
[18:19] <chrisccoulson> and it has a duplicate
[18:19] <chrisccoulson> or it did earlier:/
[18:51] <hggdh> I do remember something about user-admin doing that, but it was not related to a specific architecture
[18:51] <chrisccoulson> yeah, i think the architecture in the title is just a red herring
[18:52] <hggdh> ah
[18:52] <hggdh> I remember now
[18:52] <chrisccoulson> i might edit the architecture out of it actually
[18:52] <hggdh> by default -- keep in mind Gnome is all about making the user experience simpler, with less options
[18:52] <hggdh> users-admin will *NOT* show users below 1000, and groups below 100
[18:54] <chrisccoulson> i don't think that is the issue with this bug report though
[18:54] <hggdh> there is a gconf2 key dealing with that, let me see if I remember it
[18:54] <chrisccoulson> the problem is that the reporter claims their /etc/passwd file was hosed after using users-admin
[18:54] <chrisccoulson> yeah, there's a gconf key for toggling displaying of users below UID 1000
[18:55] <chrisccoulson> /apps/gnome-system-tools/users/showall
[18:55] <hggdh> thats it
[18:55] <hggdh> not only uid, but also gid
[18:55] <hggdh> a boolean
[18:56] <hggdh> this, in turn, seems like an issue with g-s-t, a real one (and, again, this has happened before)
[18:56] <hggdh> look at the changelog for g-s-t
[18:56] <chrisccoulson> i'm not sure whether bug 240437 is an issue with g-s-t or system-tools-backends though.
[20:34] <nellery> afternoon
[20:34] <bdmurray> howdy
[21:45] <Ampelbein> Hi! Could some experienced user check on Bug 255826 and tell me if I done the examination in the correct way? Thank you.
[22:13] <MasterPa> Hey everyone, i've got a question about a bug in the ubuntu kernel. can anyone help?
[22:51] <Ampelbein> Sorry to ask again, but could some experienced user check on Bug 255826 and tell me if I done the examination in the correct way? Thank you.
[22:52] <bdmurray> Ampelbein: you might check in #ubuntu-x as there are X specific triagers there
[22:54] <bdmurray> That one sounds like a duplicate to me. You might look for other xorg bugs like that
[22:54] <Ampelbein> I already looked at other bugs, but could not find a similar one with the savage-driver.
[22:54] <bdmurray> I don't think it is driver specific
[22:54] <Ampelbein> I'll ask in #ubuntu-x, thanks for the hint.
[22:55] <Ampelbein> And I'll go have a look on other bugs.
[23:44] <mrooney> bdmurray: is the bugcontrol list working alright for subscribers? or should I copy you?
[23:45] <bdmurray> its only non-member postings that are problematic
[23:45] <bdmurray> so you should be good!
[23:48] <mrooney> alright thanks, I'll give it a shot
[23:57] <mrooney> bdmurray: did my original reply come through okay, for mcas's application?
[23:58] <mrooney> okay, the archive appears to have it.