[00:09] <JonCharge> Can any one here set importance?
[00:14] <JonCharge> Ampelbein, ping
[00:14] <Ampelbein> JonCharge:
[00:14] <JonCharge> https://bugs.launchpad.net/apt/+bug/351076
[00:15] <JonCharge> Suggest medium
[00:15] <JonCharge> And the bug I think has enough information for a dev to start working on it.
[00:15] <Ampelbein> looking
[00:18] <Ampelbein> JonCharge: why medium? i would set it to low, it's an unsual hardware.
[00:19] <JonCharge> It meets two of the criteria for medium I think.
[00:19] <JonCharge> A bug that has a severe impact on a non-core application.
[00:19] <JonCharge> A problem with a non-essential hardware component (network card, camera, webcam, music player, sound card, power management feature, printer, etc.)
[00:19] <JonCharge> But I defer to your judgement.
[00:19] <JonCharge> You are more experienced. :)
[00:20] <JonCharge> When I looked at     * Bugs/Importance
[00:21] <JonCharge> I'll go with low if that is what you want to do.
[00:21] <Ampelbein> JonCharge: you could also argument that it meets two criteria for low: uncommon hardware and usability issue.
[00:21] <JonCharge> Ah...
[00:21] <JonCharge> Your right.
[00:21] <Ampelbein> i think we should not discuss to deeply about importance.
[00:21] <JonCharge> Ok
[00:22] <JonCharge> I'm new at this.
[00:22] <JonCharge> :)
[00:22] <Ampelbein> JonCharge: no problem, thanks for helping ;-)
[00:22] <JonCharge> Anytime.
[00:22] <Ampelbein> JonCharge: another thing: launchpad uses tags to identify some issues. there is a tag "packaging" which would apply here.
[00:23] <Ampelbein> see https://wiki.ubuntu.com/Bugs/Tags
[00:24] <JonCharge> tagged, and I'll read that doc
[00:24] <Ampelbein> and if you use pgp/mime we won't see your pgp-signature on the comments ;-) (just cosmetical)
[00:24] <JonCharge> I'll do that.  Do you know how to keep the commands out of the comments?
[00:29] <Ampelbein> JonCharge: don't know. but they don't cause harm.
[00:29] <JonCharge> ok
[00:30] <Ampelbein> i've set it to triaged/medium, following your suggestion.
[00:30] <JonCharge> ok
[00:30] <Ampelbein> thanks for your work.
[00:30] <JonCharge> No problem :)
[00:32] <JonCharge> I have applied to the bug control team, should hear back shortly I think.
[00:40] <Ampelbein> JonCharge: have you already sent a mail with your application?
[00:45] <JonCharge> Ampelbein, yes, I have...
[00:46] <Ampelbein> JonCharge: found it already, commenting a bit.
[00:46] <JonCharge> oh ok, I was about to link it
[01:04] <Ampelbein> JonCharge: wrote a reply, sadly i can't give a +1 yet. please read my comments and the documentation provided again.
[01:05] <JonCharge> I will, and thank you for the feedback.
[04:59] <torkiano> hello all, can someone help me triaging bug #344705
[04:59] <torkiano> Is needed more info?
[06:14] <dholbach> good morning
[06:38] <YoBoY> hi
[07:35] <thekorn> good morning bugsquad
[08:50] <dominiks> morning bugsquad
[08:52] <dominiks> bug 98626 was closed in Debian 3 days ago.. how long does it take for LP to reflect status changes of bugs in remote watch please?
[08:52] <xhochy> Could I please get a wishlist importance for bug 351427 ?
[13:20] <liw> could someone mark #349653 as "triaged"? (I'm the developer of the package, it has all the info I need, but I don't have the LP priviledges to change to triaged, just confirmed)
[13:25] <pedro_> liw: done
[14:00] <Hobbsee> liw: why don't you have the developer privs?
[14:00] <liw> Hobbsee, because I suck, mainly
[14:00] <liw> (by being lazy)
[14:00] <Hobbsee> ah
[14:00] <Hobbsee> it probably only takes a mail saying "please add me to the team", based on who you are, though
[14:17] <BUGabundo> asac: around?
[14:18] <BUGabundo> I did ran that comand line you gave me to see why wifi would not connect with low signal
[14:18] <BUGabundo> nothing to special there....
[14:18] <BUGabundo> it didn't hopped channel
[15:17] <bddebian> Boo
[15:18] <thekorn> hello bddebian
[15:19] <Hobbsee> argh!  you scared me, bddebian!  ;)
[15:19] <bddebian> Hi the
[15:19] <bddebian> Err thekorn
[15:19] <bddebian> Heya Hobbsee!
[15:20] <BUGabundo> foo
[15:30] <dominiks> bug 98626 was closed in Debian 3 days ago.. how long does it take for LP to reflect status changes of bugs in remote watch please?
[15:53] <hggdh> dominiks, should be at most one day
[16:01] <yofel> could somebody with the rights mark bug 351389 as wishlist please
[16:04] <BUGabundo> yofel: they better!
[16:04] <BUGabundo> its going to take a while on both counts
[16:04] <BUGabundo> adobe flash install package is no where to be fund
[16:04] <BUGabundo> *found
[16:05] <BUGabundo> and even if we have java 64 bits
[16:05] <BUGabundo> there is not applet
[16:05] <dominiks> hggdh: thanks for info.. i'll just wait bit more then :)
[16:06] <hggdh> yofel, we cannot sanely provide an alpha version of flash as the official distribution
[16:06] <yofel> ok
[16:07]  * hggdh also wishes for the 64-bit flash...
[16:08] <BUGabundo> hggdh: I use 64bits no prob there
[16:08] <BUGabundo> just don't have source :(
[16:08] <BUGabundo> java on the other hand is trieker
[16:08] <BUGabundo> but that's over my head.... no idea what lacks to make the applet
[16:13] <hggdh> BUGabundo, the issue is not if it seems to work, but the fact it is *alpha*: guaranteed to be unstable...
[16:14] <BUGabundo> hggdh: hasn't give me any trouble
[16:14] <BUGabundo> other then some PA issues
[16:14] <BUGabundo> but latest PA works fine
[16:14] <BUGabundo> as you can see on my webcam stream
[16:15] <hggdh> I do not doubt it; I just do not see a reason to add an alpha version of a package in an official distribution. Of course, nothing against having it in a PPA, for example
[16:16] <BUGabundo> that's the 2nd prob
[16:16] <BUGabundo> gnomefreak already tried ti
[16:16] <BUGabundo> but there is no secure sourse of the package
[16:16] <gnomefreak> huh?
[16:16] <BUGabundo> no md5, nothing
[16:16] <BUGabundo> hey gnomefreak
[16:17] <gnomefreak> hi BUGabundo
[16:17] <BUGabundo> just talking about flash 64bits packaign
[16:17] <BUGabundo> someone oned yet another wish bug to packaged it
[16:17] <gnomefreak> let one of the motu guys worry about that there is alot of changes to files/scripts
[16:17] <gnomefreak> that are needed
[18:05] <bond`> who maintains flashplugin-nonfree?
[18:05] <jpds> I think it's being replaced by adobe-flashplugin in the partner repo.
[18:06] <BUGabundo> gym time ppl! see you tomorrow
[18:12] <bond`> jpds: so flashplugin-nonfree should not be used anymore?
[18:49] <kees> bdmurray: is there a bzr tree anywhere for scripts for doing common bug repsonses?
[18:49] <bdmurray> kees: via launchpadlib?
[18:49] <kees> right
[18:49] <bdmurray> no, I think that would fit well in ubuntu-qa-tools though
[18:50] <bdmurray> I've a couple I've been meaning to add
[18:50] <kees> what's the url for that?
[18:50] <sbeattie> mutt-scripts/b-tool should be easy to extend in that direction.
[18:50] <kees> the security team wants to push our scripts out into the public
[18:50] <bdmurray> lp:ubuntu-qa-tools ;-)
[19:21] <kees> bdmurray: okay, I just shoved a mess of stuff in there.  I'll probably move lpl_common.py to ubuntu-dev-tools when karmic opens
[19:30] <jpds> kees: You can do so now if you like, I  don't plan to make any more u-d-t uploads till karmic.
[19:31] <kees> jpds: okay
[19:40] <greg_> Can anyone confirm that, while using the 9.04 beta, a "side by side" install might take a while, without any notification, before progressing to the "who are you? page?
[20:23] <Ryan52> kees: heh. should I just ask you directly instead of filing bugs next time? :P
[20:23]  * Ryan52 notes that ryanakca's changes didn't even work..
[20:52] <kees> Ryan52: well, file bugs, but ping me, yeah.  I've reworked the whole thing now, so one can use --distro=debian and it should work.
[20:53] <kees> Ryan52: mostly I didn't like the multiple tests for "if debian".  it needed to be much more generalized
[20:53] <kees> however, having a patch to work from helps greatly to see which pieces needed to be abstracted.
[20:56] <Ryan52> ok, thanks.
[21:19] <donspaulding> python's virtualenv utility is broken with python2.6 on jaunty.  The only bug I can find for this is https://bugs.launchpad.net/bugs/339904 which doesn't have any solution in sight.  A similar issue (though I'm not sure it is an identical problem) is reported as fixed upstream at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518826 .  How can I verify if the upstream package fixes the virtualenv issue?
[21:22] <donspaulding> i.e.  I'm willing to go out and install the debian package, if that won't totally hose my system.
[23:19] <maxb> hosing potential is sufficiently high that I wouldn't try that on *my* system
[23:27] <maxb> donspaulding: What does virtualenv do and how might I test it, anyway?
[23:27] <Bodsda> Hi, im having problems using gdb, the wiki says to use ctrl+c after continue to go to the next step of debugging an already running application, but ctrl+c stops gdb completely
[23:28] <Bodsda> O1;2P
[23:28] <Bodsda> oops
[23:29] <maxb> Bodsda: Which wiki page do you refer to?
[23:29] <Bodsda> maxb: https://wiki.ubuntu.com/Backtrace#Already%20running%20programs
[23:33] <maxb> Bodsda: I think you are misreading the wiki. It says to use Ctrl-C to break into the (gdb) prompt
[23:35] <Bodsda> maxb: im not sure what you mean, step 5: The program will continue running. Perform any actions necessary to reproduce the crash. If the program hangs but doesn't crash you can press ctrl+c in gdb while the program is frozen and then continue with the next step. -- i read that as meaning press ctrl+c to get back to the (gdb) prompt
[23:37] <Ampelbein> Bodsda: only if the program freezes
[23:37] <Ampelbein> Bodsda: if it crashes you are back at the gdb-prompt
[23:38] <Bodsda> Ampelbein: the program is already frozen -- the section of the wiki im quoting is headed "Already running programs"
[23:38] <Bodsda> the program is gnome-panel, and it is frozen upon login
[23:39] <Ampelbein> Bodsda: can you give a screenshot explaining? you attach via gdb --pid <pidofgnome-panel> ?
[23:41] <Bodsda> Ampelbein: I attach by doing exactly as it says in step three of the already running programs section https://wiki.ubuntu.com/Backtrace#Already%20running%20programs  A screenshot wont help, the panels appear normal, but are completely non-responsive
[23:41] <Ampelbein> a screenshot of the gdb-prompt
[23:42] <Bodsda> Ampelbein: what are you hoping to see?
[23:42] <Ampelbein> Bodsda: where you want to type ctrl-c.
[23:43] <Ampelbein> ctrl-c only makes sense after continuing
[23:43] <Ampelbein> otherwise you can just do the backtrace
[23:43] <seb128> Bodsda: just run gdb --pid $(pidof gnome-panel)
[23:43] <seb128> and they you can "bt"
[23:44] <Bodsda> sorry, im trying something someone suggested in #ubntu+1, il be back in a sec
[23:47] <Bodsda> got it to work
[23:47] <Bodsda> followed these instructions: < syockit> Bodsda: (1) run gdb without any parameters, i.e. just gdb (2) follow the steps until before attach (3) do  the following: set logging file gdb-<program>.txt (4) do: set logging on (5) attach the process (6) do: c   to continue (7) ctrl-c to return to gdb (8) q to quit at any time
[23:47] <Bodsda> thanks guys
[23:47] <Bodsda> hey Rocket2DMn
[23:47] <donspaulding> maxb: sorry, wasn't watching this window
[23:47] <maxb> donspaulding: Looks to me like the package may be completely broken by the Python changes in Jaunty...
[23:48] <donspaulding> you can sudo a-g install virtualenv
[23:48] <donspaulding> err, python-virtualenv, that is
[23:48] <donspaulding> maxb: yes, that's what it looks like
[23:48] <donspaulding> maxb: virtualenv let's you isolate working environments when developing python applications.
[23:49] <donspaulding> e.g. you can install two different versions of django on the same machine and each environment keeps track of which library it has installed.
[23:50] <maxb> The package builds fine if you add an --install-layout=deb to the setup.py install command, but it still doesn't work.  I think it's going to require source changes to accomodate the changed python default layout
[23:51] <donspaulding> maxb: it's an incredibly useful tool, and it'll be the first thing hundreds of python devs try to use as soon as jaunty is released, so I think it ought to get fixed before jaunty rolls out, if at all possible.
[23:51] <donspaulding> what caused the shift from site-packages to dist-packages?
[23:55] <JanC> avoiding problems with some upstream python libraries when you install them manually, I think
[23:57] <JanC> donspaulding: so partially the same reason why you use virtualenv I suppose...  ;-)
[23:57] <donspaulding> JanC: yeah, virtualenv will one day rule the python packaging world, it's just not there yet ;-)
[23:59] <JanC> well, it's mainly useful if you want to "container" a specific python + libraries for one application, right?
[23:59] <JanC> OTOH I think that what Debian/Ubuntu want is that their system-wide install keeps working