[01:02] <lfaraone> Hey, where do you put needspackaging requests?
[01:02] <lfaraone> (what package)
[01:02] <RAOF> No package; ubuntu.
[01:07] <lfaraone> Can someone in bugcontrol set this to wishlist? https://bugs.edge.launchpad.net/ubuntu/+bug/165135
[01:10] <chrisccoulson> lfaraone - it could do with being assigned a package really
[01:11] <chrisccoulson> i know that the intrepid alternate CD now supports fakeraid. have you checked the server edition to see if support exists?
[01:13] <lfaraone> chrisccoulson: It's not my bug.
[01:13] <lfaraone> chrisccoulson: Moreover, I'm not sure what he's using.
[01:14] <lfaraone> Also, what's the component for Ubuntu website bugs?
[01:14] <Hobbsee> the project 'ubuntu-website'
[01:15] <chrisccoulson> i'll have a look at that bug in the morning. we should be able to assign it a package really, but I'm not sure what
[01:15] <chrisccoulson> and it's getting late here for me
[01:15] <lfaraone> Hobbsee: Thanks.
[01:16] <Hobbsee> lfaraone: you're welcome
[01:41] <lfaraone> Can a bugcontroller set this to "Low": https://bugs.edge.launchpad.net/ubuntu/+bug/208240 ?
[01:41] <jdong> lfaraone: sounds reasonable; done.
[01:42] <lfaraone> jdong: Thanks.
[01:43] <lfaraone> jdong: Could you also set https://bugs.edge.launchpad.net/ubuntu/+bug/212492 to "Wishlist" ?
[01:44] <jdong> lfaraone: ok
[04:52] <lfaraone> hey maco.
[04:53] <maco> lfaraone: hi. i fail at reproducing my own bug.
[04:54] <emet> how long does it typically take to get on the bug control team?
[04:55] <lfaraone> maco: which one?
[04:55] <maco> emet: wondering the same thing
[04:55] <maco> lfaraone: evolution error followed by crash. log out, delete gconf keys, log in = all fixed
[04:56] <emet> maco, did someone named Brian Murray reply to your request?
[04:56] <maco> emet: no, bdmurray hasn't replied yet. 3 others have (though oddly, only 2 of them show in the list archives) with +1s
[05:16] <hggdh> emet, maco, it just takes experience -- maco, BTW, should be in in a few
[05:20] <hggdh> and -- from the response to the questions, it is usually about 7 days, to give others in bug control time to review and + or - the request
[05:23] <maco> hggdh: thanks
[05:25] <hggdh> maco, welcome. Of course, this is a democracy: we all vote, and Brian's vote is equal to all of us + 1 ;-)
[05:26] <maco> lol
[05:27] <lfaraone|zzz> maco: I was on the waiting list for 2~months before I got a "we need more data"
[05:32] <hggdh> lfaraone|zzz, I do not remember seeing your application there
[05:33] <maco> hggdh: i applied on launchpad but never sent in the questionaire a few months ago, then went "eh, i need more practice. nevermind."
[05:33] <maco> but ive been practicing, so i sent the email app now
[05:34] <hggdh|away> you had the + votes, you should have no problem.
[05:35] <hggdh|away> g'night to all
[05:35] <maco> hggdh|away: night night
[05:35] <hggdh|away> all y'all
[08:48] <Hew__> Hey guys. I'm trying to get a backtrace for bug 269120, but as soon as I attach gdb to compiz.real, my system completely freezes (except for the mouse cursor) and even alt-sysrq-k doesn't work. Any ideas?
[10:27] <danage> can someone help me find the correct package for a bug report?
[10:28] <persia> danage: Which bug report?
[10:28] <danage> it's a vnc viewer, but i seem to have two installed. i access it through terminal server client
[10:28] <danage> persia: this one: https://bugs.launchpad.net/ubuntu/+source/vnc/+bug/275089
[10:29] <danage> did i report this correctly?
[10:29] <persia> Probably not, but we can sort that.
[10:29] <danage> sounds good :)
[10:29] <persia> Firstly, it's not clear if the problem is with the client or the server.
[10:29] <persia> It's also not clear whether you are running Ubuntu on the client or the server or both.
[10:30] <persia> It's also not clear which versions of which client and server you are using.
[10:30] <persia> I think everything else is there.
[10:30] <danage> let me add all of that
[10:31] <persia> danage: Thanks.  If you get stuck on figuring out if it's the client or the server, that's OK, but the last two are critical to being able to reproduce and investigate.
[10:36] <danage> persia: i can get the vnc viewer both via xvncviewer and vncviewer in shell - is this normal? two different programs? they look 100% the same
[10:37] <persia> danage: There are probably about 10 different VNC clients in the archives.  I'm not sure how different they look.
[10:37] <danage> persia: i updated the description, can you check?
[10:39] <persia> OK.  Great.  You've identified the issue is with xvnc4viewer 4.1.1+xorg1.0.2-0ubuntu7
[10:40] <persia> Next step is to adjust the bug to apply to the xvnc4 package.  You can determine this by looking at the top line of the output of `apt-cache showsrc xvnc4viewer`
[10:42] <persia> So, if you click the arrow to the left of "vnc", you can change the package name.
[10:42] <danage> done.
[10:43] <persia> danage: Excellent.  I'd say the bug is now reported correctly.  Thanks for the adjustments.
[10:44] <persia> danage: Next step would be to track down what is happening, and where.  Trying several different VNC clients might help to see if any of them work.
[10:44] <danage> of course. if i would like to have it fixed, i better report it correctly. that's why i came and asked :)
[10:44] <danage> persia: they do, i tried a windows client. no problems.
[10:44] <persia> If nothing works, it might be some disagreement about the protocol.  If some things don't work, and some do, then it might be a library.
[10:45] <danage> i'll wait and see what happens
[10:45] <persia> danage: Yes, but it's hard to check how UltraVNC client works.
[10:45] <danage> i tried tightvnc (ubuntu) too, it works
[10:45] <danage> maybe i should add that?
[10:45] <persia> Trying other clients in Ubuntu might help determine if it's really a problem with xvnc4 or with some vnc library used by xvnc4.
[10:46] <persia> tightvnc doesn't have the bug?  Adding that would be useful.  Remember to include the version of tightvnc.
[10:46] <persia> At this point, you not only definitely know the problem is with the xvnc4 client, but you can point people at another client in ubuntu that works for comparison.
[10:48] <danage> done.
[10:48] <danage> i hope not all the people on the right get an email every time i change the description...
[10:49] <persia> They do, but they get one everytime anyone changes any bug in launchpad, so most of their email accounts don't work anymore.
[10:49] <danage> lol
[10:50] <persia> As the bug gets older, more people will be subscribed, and these people are more likely to actually read the email on the bug.  It's OK to adjust as much as you need in the beginning, but once it starts getting triaged, it's better to just work with the triagers and developers towards a solution.
[10:52] <danage> i doubt anything will happen soon. the maintainers have been asked to sync with current debian in june and nothing has happened since
[11:24] <murdok> Can anyone mark bug 117044 as xubuntu specific?
[11:26] <james_w> murdok: I don't know of a way to do that, if it only happens in Xubuntu then just state so in a comment
[11:27] <james_w> also, the reporter says they were using GNOME, so I'm not sure how it can be Xubuntu-specific
[11:28] <murdok> the last comment
[11:28] <murdok> says he has tried in gnome and its solved, but in xubuntu it persists
[11:29] <murdok> I thought that ubuntu-bug-control team had rights to do that. Now it says gparted (Ubuntu) to -> gparted (Xubuntu).
[11:29] <murdok> I will change the title
[11:40] <james_w> it sounds like re-assigning to thunar might be the correct thing to do
[11:40] <james_w> is the problem that something else mounts a partition when it is unmounted in gparted?
[11:51] <murdok> james_w: good point, i'll do that too
[12:06] <chrisccoulson> what do we do about bug reports against packages because they have no -dbg package?
[12:06] <chrisccoulson> even if they have a -dbgsym package in http://ddebs.ubuntu.com
[12:09] <afflux> chrisccoulson: what exactly do you mean? For manually retracing the reporter (or you) can use the -dbgsym package.
[12:09] <chrisccoulson> i'm looking at bug 275082 for selinux, by someone who is probably trying to backtrace a crash in a program they are developing
[12:10] <chrisccoulson> there are no -dbg packages in the main repository anymore, but there used to be
[12:11] <chrisccoulson> but they are in  http://ddebs.ubuntu.com. should i just close the report and forward them to https://wiki.ubuntu.com/DebuggingProgramCrash?
[12:11] <afflux> chrisccoulson: Yes, I think so.
[12:11] <chrisccoulson> i'll do that then. thanks:)
[12:12] <afflux> you're welcome
[12:53] <Hew> I'm still getting bug 206432, even though it has been marked as a duplicate of fixed bug 192888. Should I unmark it as a dupe?
[13:02] <lfaraone|zzz> hggdh|away: It was in march-mayish, iirc
[13:54] <nhandler> When did Launchpad edge get the "Does this bug affect you?" button?
[13:55] <Hobbsee> last rollout, iirc.
[13:56] <nhandler> Hobbsee: What happens when a person says a bug affects them? Does it mark the bug as confirmed? Does it increment a number showing how many people are affected by the bug?
[13:57] <Hobbsee> i've *no* idea.  i've not used it
[13:57] <Hobbsee> i presume the latter
[13:57] <Hobbsee> as in, the third latter
[13:57] <persia> It marks it as affecting them.  There's supposed to be a counter somewhere.
[13:57] <persia> It's the oft described "Me Too" button, intended to stave off the "Me Too" comments.
[13:58] <nhandler> So am I able to say that a bug that I report affects me? I don't want to be confirming my own bug report. Or am I already listed as being affected by the bug by reporting it on Launchpad?
[13:59] <persia> No idea.  Read the documentation :)
[13:59] <james_w> nhandler: I would guess you are already listed as being affected, but I don't think pushing it would hurt, and I doubt it has the same problems as confirming your own reports
[13:59] <james_w> I could well be wrong though
[13:59] <nhandler> persia: Where is it documented? I haven't seen it in any of the triaging guides on the wiki.
[14:00] <persia> nhandler: That is an interesting question.  I'm glad you asked.  I suspect you want to ask in #launchpad, as for any LP feature.
[14:00] <persia> (alternately said: "No idea.  LP docs are something of which I've never found enough")
[14:01] <nhandler> persia: Ok, I'll ask and report back here. Someone should probably update the triaging pages to contain this new feature
[14:12] <nhandler> According to wgrant in #launchpad, saying a bug affects you increments a counter somewhere. However, that counter is not displayed anywhere. It does not look as if the feature is complete yet. There is also no known documentation for the feature.
[14:16] <pochu> nhandler: well, it's in edge and not in production. I guess they are still working on it
[14:16] <pochu> edge receives daily code updates AFAIK
[14:16] <nhandler> pochu: I hope you are right. I would hate to see this feature enter the non-edge launchpad as-is
[14:18] <persia> It needs watching then.  production LP gets updated from edge once a month or so.  Just before the release, there's usually some warning, and anything only partially broken at that point is good to make noise about.
[14:35] <lfaraone> What should I do if I cannot reproduce a bug?
[14:36] <persia> lfaraone: In what are you finding the bug?
[14:37] <lfaraone> persia: https://bugs.edge.launchpad.net/ubuntu/+bug/270045
[14:37] <persia> lfaraone: You're using the same version of totem?
[14:38] <lfaraone> persia: yes, afaict.
[14:39] <persia> lfaraone: OK.  And you're using the i386 architecture?
[14:39] <lfaraone> persia: Yes.
[14:40] <copyofjohan> hi, Im getting a bit frustrated about bug 147464. Anyone got an idea how to help with the bug (adding useful informations) or, at least findout if theres work going on?
[14:40] <persia> lfaraone: Also, you might try launching totem in French, in case it's language specific, but it sounds like either there is something else wrong with the system, or it's a support question.
[14:47] <lfaraone> Can someone on bugcontrol set this to low: https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/268356
[14:50] <lfaraone> persia: What about something like https://bugs.edge.launchpad.net/ubuntu/+bug/267999 ?
[14:51] <persia> That's usually indicative of a hardware issue.  I have a few input devices where I can force the sense of the LED indicator to be incorrect: essentially they aren't reporting the current state to the kernel, and can only be flipped.
[14:51] <lfaraone> persia: so not an ubuntu problem ?
[14:52] <persia> For that, I'd start by getting the information on the specific affected keyboard, and maybe someone who has that keyboard can investigate to see if there's a way to quirk it.
[14:52] <persia> Well, I'd call it wishlist, but I like bugs like that.  They ought to be fixed, even if it just means sending some reset code on device inititialisation.
[14:53] <persia> Where it can't be fixed, and it's known it can't be fixed, the hardware vendor can be notified, and maybe new firmware can be issued.
[14:53] <lfaraone> persia: so it's a "linux" bug?
[14:53] <persia> When this also isn't possible, it can be turned into a hardware support note: "If you have this keyboard, you may need to ensure that the Caps Lock light is off before you boot".
[14:54] <persia> Yeah.  I'd assign it to linux.  The bits that let you turn on and off the light are in the kernel.
[14:54] <lfaraone> persia: plz set to wishlist, then.
[14:55] <lfaraone> persia: as well as 267999.
[14:55] <persia> bug #267999
[14:55] <persia> ubottu: That's OK.  You gave me a URL, which is what I wanted.
[14:56] <lfaraone> Lol: https://bugs.edge.launchpad.net/ubuntu/+bug/267624
[14:56] <persia> But you are wise, which is sufficient for today.
[14:57] <persia> 267999 is already wishlist.
[14:57] <persia> Oh.  It's the same bug :)
[14:58] <lfaraone> persia: Lol.
[15:04] <lfaraone> persia: https://bugs.edge.launchpad.net/ubuntu/+bug/264478 is prolly a bad ram issue, right?
[15:05] <lfaraone> bdmurray: ping
[15:05] <persia> lfaraone: failed to import memory block points in that direction, but I'm not sure.  memtest might be a good place to start.
[15:06] <lfaraone> persia: How long should he run it for?
[15:07] <persia> lfaraone: Dunno.  I've not used memtest much.
[15:22] <lfaraone> persia: The plot thickens: https://bugs.launchpad.net/bugs/267999 - happens on multiple systems.
[15:23] <persia> lfaraone: Yep.  Like I said, I have a couple devices for which I can make that happen.  The make & model of the keyboard is important, or the make & model of the laptop, if it's a laptop.
[15:24] <persia> It might be that someone accidentally commented out the "reset on initialise" behaviour, but I suspect it's more likely that the keyboards are just different.
[15:24] <lfaraone> persia: I really don't have a clue on how to handle this.
[15:24] <wgrant> Mark it as something other than wishlist, and let the kernel team deal with it.
[15:25] <lfaraone> persia: ok, plz set to low then.
[15:25] <persia> lfaraone: It's just a matter of explaining it's probably that the keyboard isn't properly defined in the device database, and that information about any affected hardware is required in order to help add it to the database.
[15:25] <persia> I don't personally know where that DB lives, so I can't point you at it, but I have sent some input device definitions to people previously, and the devices worked with later updated kernels.
[15:27] <persia> For a workaround, the user should be able to make sure Caps Lock is off when they are in BIOS, and the resulting boot should be correct.  There are still ways to get it wrong, especially if actively switching between virtual consoles and X, but it's harder.
[15:52] <niadh> I have here a bug that I believe exists in gutsy, but not hardy, what do I do?
[15:56] <persia> niadh: Nominate for gutsy, and ask someone to approve the nomination and mark it Fix Released in hardy.
[15:58] <niadh> so status, fixed released (since I can't recreate the bug in hardy) and how do I nominate something?
[15:59] <niadh> The bug in question is this one: https://bugs.launchpad.net/ubuntu/+bug/161862
[15:59] <niadh> wait, not that one
[15:59] <niadh> this one: https://bugs.launchpad.net/ubuntu/+bug/159629
[15:59] <niadh> Sorry, ignore my first link.
[16:05] <persia> niadh: I'd wait for the nomination to be approved first, so it shows up in the bug lists: I think there's an issue with nominations and bug lists, and haven't heard of it being solved.
[16:05] <niadh> So leave the bug as it is?
[16:08] <persia> Well, nominate it for gutsy.
[16:10] <niadh> How do I do that? I see no option for nominate.
[16:10] <niadh> ait
[16:10] <niadh> never mind
[16:11] <niadh> Yeah it's nominated for gutsy now.
[16:12] <gourgi> how can i obtain backtrace for firefox in intrepid?
[16:12] <gourgi> i use this wiki , but have some problems installing https://wiki.ubuntu.com/MozillaTeam/Bugs#Obtain a backtrace from an apport crash report (using gdb)
[16:12] <gourgi> sudo apt-get install firefox-dbg
[16:12] <gourgi> Reading package lists... Done
[16:12] <gourgi> Building dependency tree
[16:12] <gourgi> Reading state information... Done
[16:12] <gourgi> Package firefox-dbg is not available, but is referred to by another package.
[16:12] <gourgi> This may mean that the package is missing, has been obsoleted, or
[16:12] <gourgi> is only available from another source
[16:12] <gourgi> However the following packages replace it:
[16:12] <gourgi>   firefox-2-dbg
[16:12] <gourgi> E: Package firefox-dbg has no installation candidate
[16:13] <gourgi> ops sorry for the chat flood :(
[16:21] <niadh> this bug: https://bugs.launchpad.net/ubuntu/+bug/161862 says in a comment it's a libc6 issue, but I can't find a libc6 package, to attach it to
[19:02] <Hamra> hi, i want to mark bug 275199 as a dup of bug 185479, but 185479 has been incorrectly marked as a dup of bug 132001
[19:14] <hggdh> Hamra, so 185479 will not be a dup anymore?
[19:15] <hggdh> Hamra, if this is the case, just select 'Mark as a duplicate', and clear the bug number there
[19:15] <Hamra> some one noted that 185479 has been accidentally duped, but it was already triaged
[19:17] <Hamra> this comment should explain https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/185479/comments/3
[19:18] <Hamra> never mind, i un-duped it
[19:18] <Hamra> i thought  i had no control over triaged bugs, my mistake
[19:20] <greg-g> thanks for helping Hamra
[21:23] <Hamra> i think bug 275243 is a wishlist
[21:27] <hggdh> Hamra, I have always thought it sort of weird. Yes, I agree it is a wish. A good one, as far as I can understand. Have you checked http://bugs.debian.org to see it this was reported there? If it is, then we could also link the debian bug in here
[21:28] <Hamra> i'll check it in a jiffy
[21:32] <greg-g> I personally see that as a bug, not a feature request
[21:34] <Hamra> is apt-get NOT doing what it's supposed to be doing?
[21:35] <pochu> I agree with greg-g, IMHO it's a low priority bug
[21:35] <pochu> very low though :-)
[21:38] <greg-g> pochu: very low indeed
[21:38] <Hamra> i don't think this is reported in debian's bugs
[21:38] <greg-g> Hamra: a bug in the user interface/display of information is none-the-less a bug
[21:41] <Hamra> maybe, it's just that i'm not the type that fusses about such minor problems
[21:42] <greg-g> Hamra: understandable, however since it show inconsistency and is most liekly an easy fix, why not?
[21:44] <Hamra> so what should i do with this bug?
[21:45] <pochu> I would mark it as triaged and low
[21:50]  * txwikinger wundert sich warum ihn jemand laufend fragt ob es schon schneit
[21:50] <Hamra> i'm not from bug control, i can only confirm it
[21:50] <txwikinger> wrong channel :)
[21:56] <hggdh> :-)
[21:57] <hggdh> Hamra -- so it is a bug, right?
[21:58] <hggdh> Hamra, add in a comment that discussions on the -bugs channel agreed this is a bug, not a wish, and that you are then marking it as such
[21:58] <hggdh> and then I will mark it triaged
[21:58] <hggdh> hi pochu, long time
[22:00] <pochu> hey hggdh, how are you?
[22:00] <Hamra> done
[22:00] <hggdh> good, although life in the US is, right now, ah, interesting
[22:03] <hggdh> thanks Hamra
[22:03] <Hamra> no problem