[02:11] <nullack> ping asac : re aus and nz language for FF and flash plugin
[02:12] <Hobbsee> nullack: it's a sunday....
[02:13] <nullack> Hobbsee: As much as Ive been known to be confused, Im aware its Sunday :) asac is reported as online in the users list
[02:13] <nullack> Hobbsee: Hello by the way :)
[02:13] <Hobbsee> nullack: I believe he uses a proxy, fwiw
[02:13] <Hobbsee> hello :)
[02:13] <Hobbsee> or leaves his client open over the weekend
[02:14] <nullack> yeah
[02:14] <Hobbsee> [12:14] [Whois] asac has been idle for 15 hours, 52 minutes, and 4 seconds.
[02:31] <scream> Ok.
[02:31] <scream> REally confused at this one...
[02:31] <scream> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/350672
[02:31] <scream> I've changed it to imcomplete because it needs more information.
[02:31] <scream> For example, what exactly is busybox, and what is the big exactly.
[02:31] <scream> I notice that the reported changed the status back to new without providing more information.
[02:32] <scream> What are the thoughts?
[02:34] <scream> Ok, I see what occured.
[02:34] <scream> nvmind
[02:34] <scream> :)
[05:52] <scream> Regarding old bugs, they are ok to close if no activity in say, four weeks?
[05:53] <dtchen> that's on the fast/not lenient side
[05:53] <dtchen> nothing wrong per se
[05:53] <scream> I see.
[05:54] <scream> On the older bugs (lenient side) comment about the oldness then set to INCOMPLETE or INVALID?
[06:00] <dtchen> scream: yeah, give or take a couple weeks
[06:01] <dtchen> scream: i tend not to move to invalid unless there's compelling reason (or it's one of the source packages i care for)
[06:01] <dtchen> scream: have you read https://wiki.ubuntu.com/Bugs/Status, BTW?
[06:02] <scream> dtchen, I have...
[06:03] <scream> However, I'm seeing it done both ways as I look around the tracker, and I wanted to know which way was preferred... before I go diving in.  I don't want to cause more work, I want to reduce it.
[06:03] <dtchen> scream: a good rule of thumb is not to be overzealous in adjusting statuses
[06:03] <scream> ok
[06:04] <dtchen> most of the "major" source packages have people tending them
[06:04] <scream> I see.
[06:04] <scream> I've applied to the bug control team today as well.
[06:06] <scream> dtchen, thank you for your advice.
[06:15] <scream> dtchen, I have just discovered that I can manipulate bugs via email.
[06:32] <scream> hmm
[06:32] <dtchen> scream: yes, it's quite useful. i tend to triage bugs using the G1 when i'm traveling.
[06:32] <scream> Why is the bug tracker not processing commands via email?
[06:32] <dtchen> are you sending them in gpg-signed e-mail?
[06:32] <scream> I am.
[06:33] <scream> Let me show a bug I sent a command...
[06:33] <scream> https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/334601
[06:33] <scream> see the very bottom
[06:33] <scream> The status is still "confirmed".
[06:34] <scream> I'm not sure how I'm screwing this up... but if I could issue the commands via email, I would be more efficient.
[06:38] <dtchen> doesn't look like you passed "done" after the "status incomplete"
[06:38] <scream> ah
[06:39] <dtchen> you don't need to mark it incomplete, BTW
[06:39] <scream> Not intended, that was a test of the email interface, for which I was going to undo myself.
[06:39] <dtchen> i'll be filing a bug against update-manager to insert logic for this situation
[06:39] <dtchen> it's one of those unfortunate situations arising from a wget wrapper
[06:40] <scream> yes
[06:52] <scream> dtchen, this one I have confirmed... and have attempted to mark it as such
[06:52] <scream> https://bugs.launchpad.net/ubuntu/+source/ffmpegthumbnailer/+bug/350737
[06:52] <scream> But I note here, the status is still "NEW".
[07:05] <scream> dtchen, ok I see
[07:05] <scream> The command need a leading space.
[07:05] <scream> :|
[07:05] <scream> commands
[07:05] <scream> I must have missed that part of the instructions.
[07:05] <scream> https://bugs.launchpad.net/ubuntu/+bug/350739
[07:05] <scream> It worked there... now if I can figure out how to keep the commands or signature from cluttering my comment, I'd be set.
[07:39] <scream> How do I link a bug in comments?
[07:40] <YoBoY> link?
[07:40] <scream> yeah... so it can be clicked on
[07:41] <scream> Do i just post the entire url
[07:41] <scream> ?
[07:41] <YoBoY> put "#NUMBER"
[07:42] <YoBoY> scream: oups, no its "BUG NUMBER" sorry no #
[07:43] <scream> ok
[07:43] <YoBoY> like here :p
[07:43] <scream> Is this a good triage?
[07:43] <scream> https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/350734
[07:46] <YoBoY> it's a duplicate ?
[07:46] <scream> Not exactly... I created a duplicate myself in order to include the log files when I reproduced the bug successfully.
[07:47] <YoBoY> why not including this log files in the firstbug report ?
[07:47] <scream> I did not see an option on the apport to save those files on the desktop, it wanted to do a bug report.
[07:48] <YoBoY> wait...
[07:48]  * scream waits.
[07:49] <YoBoY> https://wiki.ubuntu.com/Apport#Tools
[07:50] <YoBoY> for the next time ;)
[07:51] <YoBoY> so now, or you remake the upload oy you logs on the first repport and mark the second as duplicate, or you put more information onthe second and mark the first as duplicate :)
[07:51] <scream> I have already marked my bug as a duplicate of the original
[07:53] <YoBoY> ha yes :) (need coffee...)
[07:54] <scream> otherwise, good triage?
[07:54] <YoBoY> yes :)
[07:55] <scream> ok
[07:55] <YoBoY> can you estimate the importance of this bug ?
[07:56] <scream> Yes...
[07:56] <YoBoY> can you also try to reproduce this bug on Jaunty beta ?
[07:58] <scream> Low, because it has a moderate impact on the core app (ark).
[07:58] <scream> I have successfully reproduced this bug on Jaunty Beta.
[07:59] <YoBoY> ok it's on your collected data
[08:01] <scream> Have I estimated importance correctly?
[08:01] <YoBoY> i don't know, i think :)
[08:01] <scream> k
[08:03] <YoBoY> not for me.. it's to help the bugcontrol team, and to learn how to give the right importance, you can see with the time if you have a good feeling on identifying the importance of a bug
[08:05] <Laibsch> hey, does http://rafb.net/p/tEVJzi88.html make sense to anyone?  I don't understand it.
[08:05] <Laibsch> Running gourmet on Jaunty there
[08:06] <YoBoY> it says that the md5 module is deprecated...
[08:07] <YoBoY> no not the problem here...
[08:08] <Laibsch> yes, that is not the problem I think
[08:08] <Laibsch> thank you for taking a look
[08:09] <YoBoY> NUM_AND_FRACTION_REGEXP << it think this expression is "compiled" i don't know what this mean
[08:14] <yofel> Laibsch: It's a bug - two lines above the error in convert.py the expression already get's compiled in the else part. and you can't compile the expression twice
[08:14] <Laibsch> alright
[08:14] <Laibsch> why did this not seem to be a problem with python 2.5?
[08:15] <Laibsch> do you understand that?
[08:15]  * yofel wonders about the same thing
[08:15] <Laibsch> are you using gourmet?
[08:17] <yofel> Laibsch: no
[08:17] <yofel> Laibsch: I just tried it with python2.5 - it seems compiling something multiple times is no problem there o.O
[08:17] <Laibsch> OK
[08:18] <Laibsch> Thank you all the more for trying things out
[08:18] <yofel> np
[08:18] <yofel> maybe the guys in #python can help you more
[10:49] <askand> Hello, regarding bug 285746 . The programs has not changed a lot since it was declined for intrepid, is it then wise to put in Jaunty? It is still trating manually installed packages as cruft, and unacceptable behavior. Threads promoting it's removal until this is fixed; http://ubuntuforums.org/showthread.php?t=1109200 and http://ubuntuforums.org/showthread.php?t=1080116
[11:47] <giles> I have solved a problem with mysqld not starting in Jaunty 9.04 Beta
[11:49] <giles> firstly I had to install mysql-client-5.1  because the startup script has a dependency on mysqladmin
[11:50] <giles> secondly, I had to make the script create a /var/run/mysqld directory and chown mysql:mysql /var/run/mysqld
[11:51] <YoBoY> hi giles, this is an open bug on LP ?
[11:53] <Hobbsee> giles: do you have mysql-server-5.1 installed?
[11:54] <giles> I do now
[11:54] <giles> oh sorry
[11:55] <giles> no
[11:56] <giles> i didn't really want mysql in the first place, but I think KPackageKit apt backend depends on it.
[11:56] <Hobbsee> looks like that's the package that creates /var/run/mysqld, not the client.
[11:56] <Hobbsee> which probably makes sense - the server is a daemon, no?
[11:58] <giles> well I don't want the server
[11:59] <giles> I just want the bit that forfills the dependency for kpackagekit
[11:59] <giles> When I upgraded I think it installed mysql-common
[11:59] <giles> i think that creates a script that tries to start mysqld at startup
[11:59] <giles> so I think it is a bug
[12:04] <asac> hmm nullack is offline
[13:37] <maxb> Hmm... I thought apport-collect was supposed to provide all the attachments that initially reporting a bug with apport would?
[13:37] <maxb> Any thoughts on what might have gone wrong here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/350279
[13:47] <Indexbox> народ
[17:30] <scream> bdmurray, did my application look ok?
[17:44] <scream> question
[17:44] <scream> anyone active at the moment?
[17:46] <Ampelbein> scream: just ask. someone will reply sooner or later
[17:46] <scream> ok
[17:47] <scream> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/351050
[17:47] <scream> Just a little mentorship...
[17:47] <scream> Did I triage this correctly?
[17:48] <Ampelbein> scream: looks good. you tried recreating, succeeded in that and changed to confirmed.
[17:48] <Ampelbein> scream: you got a suggestion for importance?#
[17:50] <scream> Low, because it has a moderate impact on a non core.
[17:52] <scream> Is that correct?
[17:52] <Ampelbein> i'd agree. the user is supposed to run apport-collect with a bugnumber, not a package.
[17:53] <Ampelbein> though most crasher-bugs should get medium
[17:54] <Ampelbein> importance set
[17:55] <scream> second question
[17:56] <scream> Ok to assign bugs to myself when I am either investigating them or attempting to reproduce them?
[17:59] <scream> Ampelbein
[18:01] <Ampelbein> scream: you can assign them to you if you are investigating. but you should unassign as soon as you can confirm it.
[18:01] <scream> k
[18:01] <scream> ok
[18:01] <scream> Ampelbein, thank you for your advice.
[18:01] <Ampelbein> or if you are working on it. then set to "in progress" and assign to you.
[21:49] <penguin42> what should I do with #118840 - I merged a few together on this, and about a month ago asked whether anyone still had it (all reports were 7.04, 7.10) all replies say it's gone away - what's the right thing to do to it?
[21:59] <hggdh> bug 118840
[22:02] <hggdh> penguin42, I am guessing we can close invalid, with a note to reopen if someone is able to grab a nice backtrace of it
[22:02] <penguin42> ok, it looks pretty much like it was a 7.xism that's gone
[22:03] <hggdh> it might. Since then coreutils went to 6.10 on our archives, and is now (upstream) going on to 7.2
[22:03] <penguin42> done
[22:03] <hggdh> thanks penguin42
[22:03] <penguin42> no problem