=== scream is now known as JonCharge [00:09] Can any one here set importance? [00:14] Ampelbein, ping [00:14] JonCharge: [00:14] https://bugs.launchpad.net/apt/+bug/351076 [00:14] Ubuntu bug 351076 in xserver-xorg-input-aiptek "Package xserver-xorg-input-aiptek does not install (Januty beta)" [Undecided,Confirmed] [00:15] Suggest medium [00:15] And the bug I think has enough information for a dev to start working on it. [00:15] looking [00:18] JonCharge: why medium? i would set it to low, it's an unsual hardware. [00:19] It meets two of the criteria for medium I think. [00:19] A bug that has a severe impact on a non-core application. [00:19] A problem with a non-essential hardware component (network card, camera, webcam, music player, sound card, power management feature, printer, etc.) [00:19] But I defer to your judgement. [00:19] You are more experienced. :) [00:20] When I looked at * Bugs/Importance [00:21] I'll go with low if that is what you want to do. [00:21] JonCharge: you could also argument that it meets two criteria for low: uncommon hardware and usability issue. [00:21] Ah... [00:21] Your right. [00:21] i think we should not discuss to deeply about importance. [00:21] Ok [00:22] I'm new at this. [00:22] :) [00:22] JonCharge: no problem, thanks for helping ;-) [00:22] Anytime. [00:22] JonCharge: another thing: launchpad uses tags to identify some issues. there is a tag "packaging" which would apply here. [00:23] see https://wiki.ubuntu.com/Bugs/Tags [00:24] tagged, and I'll read that doc [00:24] and if you use pgp/mime we won't see your pgp-signature on the comments ;-) (just cosmetical) [00:24] I'll do that. Do you know how to keep the commands out of the comments? [00:29] JonCharge: don't know. but they don't cause harm. [00:29] ok [00:30] i've set it to triaged/medium, following your suggestion. [00:30] ok [00:30] thanks for your work. [00:30] No problem :) [00:32] I have applied to the bug control team, should hear back shortly I think. [00:40] JonCharge: have you already sent a mail with your application? [00:45] Ampelbein, yes, I have... [00:46] JonCharge: found it already, commenting a bit. [00:46] oh ok, I was about to link it === scream is now known as JonCharge [01:04] JonCharge: wrote a reply, sadly i can't give a +1 yet. please read my comments and the documentation provided again. [01:05] I will, and thank you for the feedback. === ApOgEE__ is now known as ApOgEE-- [04:59] hello all, can someone help me triaging bug #344705 [04:59] Launchpad bug 344705 in openjdk-6 "IcedTea Plugin Doesnt Work" [Undecided,Confirmed] https://launchpad.net/bugs/344705 [04:59] Is needed more info? [06:14] good morning [06:38] hi [07:35] good morning bugsquad [08:50] morning bugsquad [08:52] 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] Launchpad bug 98626 in checkstyle "please add command line program" [Wishlist,In progress] https://launchpad.net/bugs/98626 [08:52] Could I please get a wishlist importance for bug 351427 ? [08:52] Launchpad bug 351427 in gnome-control-center "Add "use max resolution checkbox+functionality" to gnome-display-properties" [Undecided,New] https://launchpad.net/bugs/351427 === asac_ is now known as asac [13:20] 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] liw: done === thunderstruck is now known as gnomefreak [14:00] liw: why don't you have the developer privs? [14:00] Hobbsee, because I suck, mainly [14:00] (by being lazy) [14:00] ah [14:00] it probably only takes a mail saying "please add me to the team", based on who you are, though [14:17] asac: around? [14:18] I did ran that comand line you gave me to see why wifi would not connect with low signal [14:18] nothing to special there.... [14:18] it didn't hopped channel === bromic94 is now known as thewrath [15:17] Boo [15:18] hello bddebian [15:19] argh! you scared me, bddebian! ;) [15:19] Hi the [15:19] Err thekorn [15:19] Heya Hobbsee! [15:20] foo [15:30] 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:30] Launchpad bug 98626 in checkstyle "please add command line program" [Wishlist,In progress] https://launchpad.net/bugs/98626 [15:53] dominiks, should be at most one day [16:01] could somebody with the rights mark bug 351389 as wishlist please [16:01] Launchpad bug 351389 in ubuntu-restricted-extras "64bit restricted extras should use 64bit flash and java plugins" [Undecided,Confirmed] https://launchpad.net/bugs/351389 [16:04] yofel: they better! [16:04] its going to take a while on both counts [16:04] adobe flash install package is no where to be fund [16:04] *found [16:05] and even if we have java 64 bits [16:05] there is not applet [16:05] hggdh: thanks for info.. i'll just wait bit more then :) [16:06] yofel, we cannot sanely provide an alpha version of flash as the official distribution [16:06] ok [16:07] * hggdh also wishes for the 64-bit flash... [16:08] hggdh: I use 64bits no prob there [16:08] just don't have source :( [16:08] java on the other hand is trieker [16:08] but that's over my head.... no idea what lacks to make the applet [16:13] BUGabundo, the issue is not if it seems to work, but the fact it is *alpha*: guaranteed to be unstable... [16:14] hggdh: hasn't give me any trouble [16:14] other then some PA issues [16:14] but latest PA works fine [16:14] as you can see on my webcam stream [16:15] 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] that's the 2nd prob [16:16] gnomefreak already tried ti [16:16] but there is no secure sourse of the package [16:16] huh? [16:16] no md5, nothing [16:16] hey gnomefreak [16:17] hi BUGabundo [16:17] just talking about flash 64bits packaign [16:17] someone oned yet another wish bug to packaged it [16:17] let one of the motu guys worry about that there is alot of changes to files/scripts [16:17] that are needed === jtisme is now known as jtisi === jtisi is now known as jtisme === nanomad_ is now known as nanomad [18:05] who maintains flashplugin-nonfree? [18:05] I think it's being replaced by adobe-flashplugin in the partner repo. [18:06] gym time ppl! see you tomorrow [18:12] jpds: so flashplugin-nonfree should not be used anymore? === erhesrhsrtb54vyh is now known as Elbrus === jgoguen_ is now known as jgoguen [18:49] bdmurray: is there a bzr tree anywhere for scripts for doing common bug repsonses? [18:49] kees: via launchpadlib? [18:49] right [18:49] no, I think that would fit well in ubuntu-qa-tools though [18:50] I've a couple I've been meaning to add [18:50] what's the url for that? [18:50] mutt-scripts/b-tool should be easy to extend in that direction. [18:50] the security team wants to push our scripts out into the public [18:50] lp:ubuntu-qa-tools ;-) === ejat is now known as e-jat === ivoks_ is now known as ivoks [19:21] 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] 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] jpds: okay [19:40] 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? === fader_ is now known as fader|late_lunch [20:23] 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] 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] Ryan52: mostly I didn't like the multiple tests for "if debian". it needed to be much more generalized [20:53] however, having a patch to work from helps greatly to see which pieces needed to be abstracted. [20:56] ok, thanks. === yofel_ is now known as yofel === fader|late_lunch is now known as fader_ === jdstrand_ is now known as jdstrand [21:19] 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:19] Ubuntu bug 339904 in python-virtualenv "python-virtualenv doesn't work with Python 2.6.x" [Undecided,Confirmed] [21:22] i.e. I'm willing to go out and install the debian package, if that won't totally hose my system. [23:19] hosing potential is sufficiently high that I wouldn't try that on *my* system === ccooke_ is now known as ccooke [23:27] donspaulding: What does virtualenv do and how might I test it, anyway? [23:27] 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] O1;2P [23:28] oops [23:29] Bodsda: Which wiki page do you refer to? [23:29] maxb: https://wiki.ubuntu.com/Backtrace#Already%20running%20programs [23:33] Bodsda: I think you are misreading the wiki. It says to use Ctrl-C to break into the (gdb) prompt [23:35] 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] Bodsda: only if the program freezes [23:37] Bodsda: if it crashes you are back at the gdb-prompt [23:38] Ampelbein: the program is already frozen -- the section of the wiki im quoting is headed "Already running programs" [23:38] the program is gnome-panel, and it is frozen upon login [23:39] Bodsda: can you give a screenshot explaining? you attach via gdb --pid ? [23:41] 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] a screenshot of the gdb-prompt [23:42] Ampelbein: what are you hoping to see? [23:42] Bodsda: where you want to type ctrl-c. [23:43] ctrl-c only makes sense after continuing [23:43] otherwise you can just do the backtrace [23:43] Bodsda: just run gdb --pid $(pidof gnome-panel) [23:43] and they you can "bt" [23:44] sorry, im trying something someone suggested in #ubntu+1, il be back in a sec [23:47] got it to work [23:47] 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-.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] thanks guys [23:47] hey Rocket2DMn [23:47] maxb: sorry, wasn't watching this window [23:47] donspaulding: Looks to me like the package may be completely broken by the Python changes in Jaunty... [23:48] you can sudo a-g install virtualenv [23:48] err, python-virtualenv, that is [23:48] maxb: yes, that's what it looks like [23:48] maxb: virtualenv let's you isolate working environments when developing python applications. [23:49] 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] 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] 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] what caused the shift from site-packages to dist-packages? [23:55] avoiding problems with some upstream python libraries when you install them manually, I think [23:57] donspaulding: so partially the same reason why you use virtualenv I suppose... ;-) [23:57] JanC: yeah, virtualenv will one day rule the python packaging world, it's just not there yet ;-) [23:59] well, it's mainly useful if you want to "container" a specific python + libraries for one application, right? [23:59] OTOH I think that what Debian/Ubuntu want is that their system-wide install keeps working