[01:27] <Ampelbein> Hi! Could some member of bug-control please set bug 219593 to wishlist? thanks in advance.
[01:46] <hggdh> Ampelbein, it was already wishlisted. I set it to triaged, though
[01:46] <Ampelbein> hggdh: yeah. but for the record: it was not wishlisted as i posted here. ;-) thanks.
[01:47] <hggdh> :-)
[02:29] <Hobbsee> hggdh: repong.
[02:31] <hggdh> Hobbsee, reping
[02:31] <Hobbsee> hggdh: what did you want yesterday?
[02:33] <hggdh> Hobbsee, nothing, you were pointing your bubblegun at me (or my my general direction, which is the same, given that bubbleguns are known to have a wide range)
[02:33] <Hobbsee> hggdh: oh, fair enough :P
[02:33]  * Hobbsee covers hggdh in bubbles
[02:34]  * hggdh swims for safety
[02:34] <hggdh> huh, floats, methinks
[16:13] <Ampelbein> Hi! Could some member of bugcontrol please set bug #260659 to wishlist? Thanks in advance.
[16:17] <persia> Ampelbein: Why is that wishlist?  Is it not possibly Low, as forgetful users might fail to lock the workstation, andsomeone else could run `rm -rf /`without a password?
[16:17]  * persia is open to "Wishlist", but would like to hear a justification
[16:19] <qense> Ampelbein: I agree with the reporter of the bug in this issue. However, you could consider it as a small usability bug. It's surely not a wishlist, since it's a really small change.
[16:19] <qense> I would set it to Low.
[16:19] <Ampelbein> Just thought it might be wishlist because its just a change of default behavior.
[16:20] <Ampelbein> but after rethinking persia's comment i agree to low.
[16:20] <qense> Are you a member of the bugsquad?
[16:21] <Ampelbein> bugsquad yes, bugcontrol no.
[16:21] <qense> OK
[16:23] <qense> Do you want to confirm the bug and tell the user about that to collect bugs for your (possible) application to bugcontrol, or shall I do that?
[16:23] <Ampelbein> am just writing the confirmation.
[16:24] <qense> ok
[16:25] <Ampelbein> done
[16:25] <qense> nice
[16:25] <qense> I'm going to set the importance to low
[16:26] <qense> aargh!
[16:26] <qense> done, btw
[16:26] <qense> But the status was set to new in some way when I set the importance to low, so I had to set that again to confirmed
[16:27] <qense> That's really weird
[16:29] <Ampelbein> yeah, sometimes the webinterface seems to not do what i want it to do. but most of the time it just works ok.
[16:40] <persia> qense: I'm confused.  Why is it not wishlist because it's a small change?
[16:41] <qense> It's not something new, a new feature.
[16:41] <qense> It's a change of something that could be a security riks, or a usability bug
[16:41] <qense> (in its current state)
[16:41] <persia> Sure, but wishlist isn't only that.  If I say that I think the links in xchat-gnome ought to be human brown by default, surely that's also wishlist.
[16:42] <persia> In the case of this bug, I also think it's "Low", but I'm not sure that there aren't trivial wishlist bugs.
[16:42] <qense> I agree with that.
[16:42] <qense> Your example is a wishlist, because it doesn't cause problems when it isn't, just you not liking the colour.
[16:43] <qense> (that was probably a horrible sentence)
[16:44] <persia> Sure.  I think "wishlist" is for anything that doesn't actually cause a problem today.  This might be changling a colour, or it might be adding a feature, or it might be fixing a spelling mistake, or anything, really.
[16:46] <qense> That's my opinion too. :) I just used a bad argument.
[16:48] <persia> qense: With the right conclusion :)  I only pick on you for the benefit of those reading the logs.
[16:49] <qense> I don't mind :) It learned me to use better arguments when telling people why I agree with something and it was a good example to learn other people about the wishlist importance.
[16:50] <persia> qense: Excellent.  Sometimes I worry when I pick on people even when they got it right
[16:52] <qense> I have that too sometimes. You can't send body language over IRC
[16:52] <persia> Indeed.
[16:54] <Ampelbein> Another importance question: bug #256820 - i think this should get high priority, because it affects a small portion of users (those with the same card). I googled for the problem and found some similar reports. other opinions?
[16:55] <Ampelbein> (just using the chance seeing some of bugcontrol round here, if its not ok to ask such questions, please say so)
[16:55] <persia> Ampelbein: Asking such questions is one of the primary reasons for this channel.
[16:56] <Ampelbein> ok.
[16:56] <persia> I'm undecided between "Medium" and "High" for that one.  Lots of people who use that package doesn't have that hardware.  On the other hand, it could be considered to fall under "A problem with an essential hardware component".
[16:57] <persia> On the other hand, it only happens when watching movies, which makes me thing it's not quite as essential.
[16:57] <persia> Nor really that severe.  I guess it depends on whether one considers watching movies to be a core application.
[16:58] <Ampelbein> for the standard user i think watching movies IS important.
[16:58] <persia> (On a related note, why is "network card" considered a non-essential hardware component, and "laptop built-in wireless" considered an essential component?
[16:58] <Ampelbein> nothing worse than sitting pants down and having to debug xserver-crashes ;-)
[16:58] <persia> Heh.  Maybe so.
[16:59] <qense> About that related note: I think that nowadays you should consider networking as essential, since it's often the main reason why people buy computers and all updates are downloaded.
[17:00] <persia> qense: That's what I'm thinking.  Even on some of my laptops, I'm more likely to use the network adapter than wireless.
[17:00] <Ampelbein> back to the bug, i'd say though it affects a small number it renders ubuntu for them quite useless.
[17:01] <qense> Not completely, they still can check their email and flashplayers aren't affected, are they?
[17:01] <persia> Ampelbein: I disagree entirely that it renders Ubuntu useless, but I'll mark it High anyway, as Xv *really* ought work.
[17:03] <Ampelbein> depends. i'm trying to take my colleagues and friends as example. they want to browse, hear music and watch video. if one of this fails -> useless. but i agree that for the more technical interested users its not useless without video.
[17:04] <persia> Not just the technical folk.  I know a bunch of very serious music fans who spend all day in front of their computers (and the nights at the livehouses).  These people almost never watch video, but text and sound are vital.
[17:19] <stefanlsd> When should the status be set to fix released?
[17:20] <qense> When the fix is accpeted in the repositories
[17:20] <qense> Launchpad should do that by itself, actually
[17:21] <stefanlsd> qense: Whats the diff between fix commited then?
[17:21] <qense> When the fix is comitted it still needs to be tested and accepted.
[17:22] <persia> Well, it's more complicated than that.
[17:22] <qense> There is a good explanation of both statuses here: https://wiki.ubuntu.com/Bugs/Status
[17:22] <persia> In the case of most projects on launchpad, "Fix Committed" means that the fix is in bzr, and "Fix Released" means that the fix is in a tarball.
[17:23] <persia> In the case of Ubuntu, "Fix Committed" is nearly meaningless.  It tends to be used to indicate that an upload happened, but maybe the upload is waiting for something, and it will be closed in 5 minutes (if the changelog included the appropriate syntax)
[17:24] <persia> Sometimes it's also used for some special processes.  I don't remember if the SRU process uses it right now, but at one point it was used to indicate a fix was in -proposed.
[17:25] <persia> Generally, for Ubuntu, don't use "Fix Committed" unless you have a special reason to do so, and someone instructed you to set it that way.
[17:27] <stefanlsd> persia: thanks for that. If i upload a debdiff and subscribe u-u-s. What status should i be setting?
[17:27] <stefanlsd> in progress?
[17:50] <persia> stefanlsd: Confirmed.  In Progress is when you are working on it.  There's a bug aganst LP about this, but it's not closed yet.
[17:50] <persia> Ideally there should be a "Needs Review" status to indicate we have a fix not yet committed.
[17:51] <persia> LP assumes that everyone who is capable of suggesting a fix is also a developer, which while true in a sense, doesn't really match the permissions configuration in launchpad.
[19:29] <stefanlsd> persia: thanks. makes sense
[19:41] <Ampelbein> Could someone from bugcontrol please set the importance of bug #85439 to low? I think it should be low because this only affects a minor part of the system.
[19:45] <Rocket2DMn> Ampelbein, done
[19:45] <Ampelbein> thx
[19:45] <Rocket2DMn> np
[20:07] <Ampelbein> Another Request: Bug #172343 - I think it could be set to status triaged, importance low. I reproduced the problem myself and verified with a non-ubuntu-version of ktorrent, then reported the bug upstream. Opinions?
[20:22] <persia> Ampelbein: Done.
[20:22] <Ampelbein> thx
[22:13] <Ampelbein> hi! i have a question about bug #259387 ? i'm unsure whether it deserves medium or high importance. i tend to medium because it causes moderate impact on a non-core application. What is your opinion on this case?
[22:14] <Ampelbein> Also, I think this could be set to triaged.
[22:22] <Ampelbein> Another request: Bug #260356 - Could some member of bug-control please set it to status triaged, importance low? I have reproduced the problem myself and submitted the issue upstream.
[22:31] <asomething> Ampelbein: I think you are right... I set the importances and marked as triaged. thanks for linking upstream!
[22:33] <Ampelbein> thank you.
[23:09] <bcurtis> anyone alive in here?
[23:30] <Ampelbein> bcurtis: me ;-)
[23:31] <bcurtis> Ampelbein, thank you.  Is there any way that traigers can set a bug as wishlist?
[23:31] <bcurtis> or just permissions issues u can't
[23:31] <Ampelbein> only members of bug-control can set wishlist
[23:31] <Ampelbein> you can post a request in here and someone will set it for you.
[23:32] <bcurtis> https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/260747
[23:32] <bcurtis> wishlist
[23:32] <bcurtis> how am i faster than ubottu?
[23:33] <bcurtis> and that was just me scrounging through bugs
[23:34] <Ampelbein> bcurtis: i usually write something like "can some member of bug-control please set status blah on bug #12345"
[23:34] <Ampelbein> so when later on someone looks in the channel he can act upon it.
[23:34] <bcurtis> ohhhhh, ok
[23:35] <bcurtis> Can someone please set status "wishlist" on bug #260747
[23:35] <bcurtis> ty :-)
[23:35] <Ampelbein> np
[23:36] <bdrung> bcurtis: done
[23:36] <bcurtis> bdrung: ty
[23:36] <bdrung> np
[23:36] <bdrung> easiest thing to do.
[23:45] <bcurtis> what gives you the permissions to do so? j/w
[23:46] <bdrung> bcurtis: you have to be member of ubuntu-bugcontrol
[23:46] <bcurtis> ahhh ok.
[23:47] <bcurtis> i've just recently started triaging bugs, so its all a new experience to me.
[23:49] <bdrung> if you like triaging and think you know how all these things work you can request to join
[23:51] <bcurtis> bdrung: the only thing i've done is take really old bugs and marked them for closure, and/or taken a package and tested the issue other users are having.. i've gone nowhere into the higher level triage.. i'd love to, but have no idea what to do and worry about being more of a nuisance than a benefit