=== yofel_ is now known as yofel === Pici` is now known as Pici === FFEMTcJ_ is now known as FFEMTcJ === Iggy1 is now known as Iggy === Iggy is now known as Iggy|afk === jussio1 is now known as Guest88592 === matti_ is now known as matti === yofel_ is now known as yofel === Adri2000 is now known as Guest25225 === Hobbsee is now known as Guest78837 === yofel is now known as Guest7105 === Pici is now known as Guest66795 === nhandler is now known as Guest15490 === dous_ is now known as dous === Guest15490 is now known as nhandler === wgrant_ is now known as wgrant === nixternal_ is now known as nixternal === nhandler is now known as evilnhandler === dous_ is now known as dous [04:59] what's the deal again for translation-related bugs? [04:59] there is a bug report of a program being in English when the locale is German [05:00] WeatherGod: at a minimum open a task with ubuntu translations [05:00] ok [05:02] micahg: I should use "Also affects distribution", right? [05:02] WeatherGod: no, also affects project [05:02] ah, that explains that [05:30] hggdh: ping === asac_ is now known as asac === Guest25225 is now known as Adri2000 === Adri2000 is now known as Guest438 === Guest438 is now known as Adri2000 === Adri2000 is now known as Guest14290 === Guest14290 is now known as Adri2000 === Adri2000 is now known as Adri2000` === yofel_ is now known as yofel === astechgeek is now known as techgeek === lifeless_ is now known as lifeless === Guest88592 is now known as jussi01 === nigel_nb__ is now known as nigel_nb === mr_steve_ is now known as mr_steve [08:12] Hi everybody... [08:20] hello how'll i produce a backtrace? [08:20] saji: Well, there's a couple ways. [08:20] * persia digs at the wiki [08:21] The easiest is to enable apport (description in https://wiki.ubuntu.com/Testing/EnableProposed) [08:21] hmmm... i went through- https://wiki.ubuntu.com/DebuggingProgramCrash and https://wiki.ubuntu.com/Backtrace [08:21] It confused me... :) [08:21] Yep, that's the other way :) [08:23] can you tell me specifically.. Wht i should be doing? [08:24] I have reported a bug in NAutilus, and they have asked me to upload a backtrace if possible.... [08:25] !backtrace [08:25] To get a backtrace of a failing application please read: https://wiki.ubuntu.com/Backtrace [08:26] hello... anybody please help me... [08:28] saji: Where is your bug report? [08:28] https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/489300 [08:28] Launchpad bug 489300 in nautilus "Nautilus closes when trying to open mounted NTFS volume" [Medium,Incomplete] [08:28] this is my bug report.. [08:30] Hi guys, I was wondering is anyone familiar with a workaround for a bug that I have? Bug #463396 [08:30] Launchpad bug 463396 in xserver-xorg-video-intel "[GM45] No monitor output on laptop" [Undecided,Confirmed] https://launchpad.net/bugs/463396 [08:31] It hasn't gotten any attention, maybe its solved somewhere else? [08:31] new update, still no video on my onitor!!! [08:31] *monitor [08:33] ping persia [08:34] persia, What should i do now? [08:35] saji: I'l admit I'M a bit confused. That looks lik it was already submitted with apport. [08:36] Hrm. autocomplete not working: perhaps he left :( [09:27] I just got my 9.10 installed again after a week of x server problems (when all i had to do was unplug 1 monitor for the live cd to work.) Now i have it all set up fine and it runs fine but after maybe 5 minutes of being logged in, it starts to freeze and jump and leave trails. Know what it is?? [09:31] anybody active? [09:32] I am having a real problem with that. idk how this window is still working. i cant do anything else without killing my computer and rebooting. [09:38] does anybody know why my screen would be freezing and stalling? I installed ubuntu today and i have the nvidia driver installed and active... [09:42] echotone: This is a fresh install? Were there any errors during install? [09:45] persia: no errors. [09:46] Very odd indeed. And you didn't have this sort of issue with the live session? [09:46] no. i used the alt cd. the live cd doesnt work when i have 2 monitors plugged in. [10:03] It was my mac4lin theme. i switched back to an ubuntu theme and it works fine again. === seb128__ is now known as seb128 === seb128 is now known as seb128_ === seb128_ is now known as seb128 === Guest78837 is now known as Hobbsee [12:40] morning kamusin [12:40] hey pedro_ === duanedes1gn is now known as duanedesign [14:07] hi there. I am curious about a thing that might have been discussed multiple times, but hasn't been documented well or there has been no "real" solution (I don't know) [14:08] Is it ok to use the status "fix committed" for Ubuntu tasks where there is an upstream task that has been fixed? [14:09] (The current situation of unsynchronized watches for the gnome bug tracker kind of justify it) [14:09] I found https://lists.ubuntu.com/archives/ubuntu-bugsquad/2008-September/001157.html on a mailing list, but there was been no final result === jrib1 is now known as jrib [14:16] MrKanister: the usual is for "Fix Committed" to be set only when the fix is in a local SCS (e.g., bazzar), or published in development (Lucid, now), or in a -proposed [14:17] usually, in fact, if it is published in Lucid it should go to fix released, sorry [14:18] some teams have (or had) a different interpretation. Although I did not agree, of old, with our position, it makes a bit of sense [14:19] hggdh: Thanks. I know that it is wrong (the wiki says that, too), but as I said, the current situation is that there are too many unsynchronized watches for the gnoem bug tracker that it causes additional [14:21] ... work... yes, I understand. This can be put in the agenda for next meeting, if you want. But, right now, I would rather keep it the way it is [14:21] hggdh: sorry, I forgot the "work" (wasn't by purpose) [14:21] np [14:22] MrKanister: I have to haul ass to my customer. I will be back in 30m [14:22] hggdh: Ok, thanks though [14:56] Boo [15:05] Hello bug triaging friends! I have a bug that needs to be re-directed (maybe to the kernel, but I'm not sure). Can someone please take a look? https://bugs.edge.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/471784 [15:05] Launchpad bug 471784 in ubuntuone-client "My system doesn't resume after stand-by" [Undecided,Incomplete] [15:07] jblount, so that bug is definitely not part of the ubuntuone-client package, but you are trying to find what package it should be moved to? [15:08] statik: Correct. I'm just not sure what package it should be pointed to. [16:07] bdmurray: Hey, can you renew my membership in bugcontrol? [16:18] Hi, I've contact th guy from this bug, https://bugs.launchpad.net/bugs/496039 What other infoshould I ask him to triage the bug? I can't reproduce it on my pc :D [16:18] Launchpad bug 496039 in rhythmbox "Sound output on Rhythmbox stopped working" [Undecided,Incomplete] [16:23] lfaraone: done [16:38] hggdh: are you around? [16:38] bdmurray: thanks. [16:42] nigelbabu: yes, I am [16:42] p/36 [16:45] hggdh: I'm going to teach a course during Ubuntu User Days about reporting bugs. I'll get my course ready soon and would like a review of it once I'm done :) [16:46] nigelbabu: It will be my pleasure. And thank you for that :-) [16:46] hggdh: thank you :) === ogasawara_ is now known as ogasawara === yofel_ is now known as yofel [17:06] hggdh: you're active in the GNOME Bugsquad, aren't you? Maybe it would be clarifying for upstream if upstream forwarders from downstream would be marked as such, don't you think? It would make it more clear they're just passing the bug on and provide them with slightly more authority than regular reporters. Maybe it could even be coupled with adding rights to add LP bug links to all/most bugs at Bugzilla. [17:12] Is gvfs responsible for the archive mounter? If so, what part of it? [17:23] qense: yes, I am active upstream. We can request (some) forwarders to be assigned more rights on b.g.o, indeed. This is also a process a bit involved, but I think I can sponsor *some* -- not a lot. This is indeed worthy of discussing [17:23] qense: Although anyone can add a LP link upstream, it is just a comment [17:24] hum. The more I think about it, the more I like the idea. We should also consider extending it to other upstreams [17:26] hggdh: yeah, it would make it more clear to upstream who they're dealing with. [17:28] However, we shouldn't give such recognition away too easily, maybe it could be a part of the Adopt-a-package program so only people who know what they're talking about/who they're talking to are associated with Ubuntu. [17:34] qense: something along these lines, yes. Gnome b.g.o access is not lightly given, so we will have to discuss this there also (which I intend to do this evening, no access to GIMP from here) === dreimark_ is now known as dreimark [17:34] pedro_: what do you think ^^^ [17:34] ? [17:35] hggdh, can't see the discussion, too much netsplits [17:35] hggdh: you're active in the GNOME Bugsquad, aren't you? Maybe it would be clarifying for upstream if upstream forwarders from downstream would be marked as such, don't you think? It would make it more clear they're just passing the bug on and provide them with slightly more authority than regular reporters. Maybe it could even be coupled with adding rights to add LP bug links to all/most bugs at Bugzilla. [17:35] qense: yes, I am active upstream. We can request (some) forwarders to be assigned more rights on b.g.o, indeed. This is also a process a bit involved, but I think I can sponsor *some* -- not a lot. This is indeed worthy of discussing [17:35] qense: Although anyone can add a LP link upstream, it is just a comment [17:35] hum. The more I think about it, the more I like the idea. We should also consider extending it to other upstreams [17:37] could be a good idea, yes , though as hggdh said anybody can add those comments, there's no special rights on bugzilla for it (nor in gnome or freedesktop for example) [17:38] That is true, but not everyone can add LP links to all bugzilla bugs, at least I can't. [17:39] i'm not sure about the more authority than other reporters part [17:39] if you become active in the community they're going to look a bit more into your reports anyways [17:39] I'd encourage the forwarders to become more active on those products rather than asking for more "authority" [17:40] products/upstream community/etc [17:40] It's not as much about authority, but more about clarifying for upstream who they're talking to. [17:41] pedro_: what I am thinking is that this -- in a quite selective way -- could also help integration between us and upstreams [17:42] perhaps as a part of "adopt-a-package"? There is something here... === seb128_ is now known as seb128 === seb128__ is now known as seb128 === yofel_ is now known as yofel [18:19] Hi, I'm with a bug about totem. And I don't know what information ask the reporter to triage the bug... can anyone help me? [18:20] I've been asking this for a while, but apparently the problems with freenode aren't helping too much [18:21] malev: What is the bug about? Could you provide the bug number? (If you say bug 12345 ubot4 will post a link in this channel if its nice [18:21] Launchpad bug 12345 in isdnutils "isdn does not work, fritz avm (pnp?)" [Medium,Fix released] https://launchpad.net/bugs/12345 [18:22] qense, oh, I'm sorry, here it si: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/496039 [18:22] Launchpad bug 496039 in rhythmbox "Sound output on Rhythmbox stopped working" [Undecided,Incomplete] === thekorn_ is now known as thekorn [18:26] malev: it could be something very simple like having pressed the mute button on the volume control in Rhythmbox itself. Please also note that there is no such thing as a separate Kubuntu kernel. You could also ask the reporter to run Rhythmbox in the console with the command 'rhythmbox --debug', try to play the file and attach the output in a separate file to the bug report. [18:27] qense, oks! I'm gonna ask those things. one more thing. for playing mp3 there are some codecs or something like that. those are commons for vlc and rhytmbox? or they are independent? [18:27] hey qense, [18:27] thanks for working on the zeitgeist bugs ;) [18:27] thekorn: you reported them, didn't you? ;) [18:28] malev: yes, they could use different codecs, so that could be an issue as well. Did he uninstall anything when messing with Audacity? [18:28] I'm gonna ask that too [18:28] good [18:29] qense, yeah, the one you set to invalid today, but I don't take it personal ;) [18:31] thekorn: well, I'm happy now there are no open bugs against that package anymore. I just had to sacrifice you for it, that's a bargain! [18:33] qense, done! I've sent him the answer. thanks [18:33] you're welcome [18:33] qense, I like this "zero open bugs"-initiative ;) [18:35] so do I [18:36] hmm, I always thought changing the affected package/project of a task is mentioned in the interleaved activity log [18:37] which seems to not be the case [18:37] thekorn: huh? it is mentioned in the full activity log [18:38] but not in the notices between the replies [18:39] it would be nice to have it there as well, would make the discussion a bit more understandable [18:39] oh yeah, that's true [18:39] of course, but having a semi complete lof of activities in the bugreport itself sometimes makes thinks hard to understand [18:39] this one is a good example: https://bugs.edge.launchpad.net/ubuntu/+source/zeitgeist/+bug/397186 [18:39] Launchpad bug 397186 in zeitgeist "python2.6 crashed with SIGSEGV in memmove()" [Medium,Invalid] [18:39] after reading this bug (which was reported by me) [18:40] I thought "what the hell is going on here, how could this bug be reported against zeitgeist" [18:40] is there already a bug for this against malone? [18:40] well, it was changed in the triaging process from python -> zeitgeist, without a comment [18:41] don't know, let's try to find out [18:41] I am, but I don't know the terminology LP uses for this kind of log. [18:43] can't find anything so far though [18:45] qense, I just asked intellectronica in #launchpad, let's see if he has more luck finding a bugreport about it [18:45] good, we'll see what he'll come up with [19:01] qense, have you seen the discussion on #launchpad, as you are also in this channel? [19:02] if not, there seems to be no bugreport about it [19:02] I did [19:02] having a complete activtylog interleaved would be nice, but need some javasrcibt way to toggle it on/off [19:02] okidoki [19:03] would be nice indeed === FlannelKing is now known as Flannel [19:17] trying to follow conversations on irc today is no fun :( [19:17] upps wrong channel, [19:17] but still true [19:17] very true [19:17] :S [19:18] great timing for that netsplit === cyphermo1 is now known as cyphermox === BUGabundo is now known as BUGabundo_lunch === BUGabundo_lunch is now known as BUGabundo === ikonia_ is now known as ikonia === asac_ is now known as asac === thekorn_ is now known as thekorn [23:16] can someone set bug 496879 to triaged? Thanks! (Not sure if Low or Medium) [23:16] Launchpad bug 496879 in software-properties "add-apt-repository should return exit code and not adding wrong repositories" [Undecided,Confirmed] https://launchpad.net/bugs/496879 [23:16] yofel: as if anyone was reading [23:17] true -.- [23:20] yofel, what did you do to confirm the bug? [23:20] malev: sudo add-apt-repository ppa:bxlsjs/sds [23:20] yofel clever :D [23:20] that ppa defenitely doesn't exist [23:20] and it gets added anyway [23:20] not good if you run that and include a typo [23:21] yofel, sure! thanks [23:22] yofel: please add version of python-software-properties; I will then mark the bug as triaged/Medium [23:23] heh, I just triaged/wishlist [23:23] feel free to bump the Importance [23:23] hggdh: mom [23:23] split the difference and call it low? :-) [23:24] dtchen: I thought about wishlist also, but this is really a bug... [23:24] hggdh: no argument from me [23:24] hggdh: single use apport is back! [23:25] micahg: yes... finally :-) [23:25] hggdh: doen [23:25] *done [23:26] micahg: about bug 233990 -- I am done with the OR, cannot stand the guy anymore [23:26] Launchpad bug 233990 in thunderbird "Thunderbird's mdn (receipt) message may contain 822bis-violating bare lf which is rejected by Qmail" [Low,Triaged] https://launchpad.net/bugs/233990 [23:26] hggdh: I saw your comments, I couldn't find an upstream, if it's not a problem in TB3, I'd close it invalid [23:26] or won't fix in TB2 [23:27] micahg: it is in tb3 also, I tested [23:27] and opened an upstream for it [23:29] yofel: thank you [23:29] np [23:31] brb -- ride back to the hotel [23:31] hggdh: eheh how's the COLD? [23:42] hi, where do you find new bugs? to work on them... because a went to https://bugs.launchpad.net/ubuntu/+bugs and all bugs looks like being commentend by others who are all ready working with them. even when i set the tag: new... [23:42] where to start looking for bugs ? :D [23:43] malev: choose a package, or click on new bugs on that page? [23:44] micahg, that what I did? shoul a keep searching? [23:44] micahg, wait, what do you mean with package: karmic, lucid? that? [23:45] malev: IF you want fresh new bugs, you can also try #ubuntu-bugs-announce [23:45] malev: no, like a program package [23:45] malev: here's 44k new bugs: https://bugs.edge.launchpad.net/ubuntu/+bugs?search=Search&field.status=New [23:46] if a bug has more than one suscriber it means that the suscribers all ready checked de bug? [23:47] malev: no, you should see comments if someone's done something [23:48] oks, and if I found one with no comments I can start working on it? [23:49] malev: even if you find comments you can start working on it unless it's requesting information from the OR [23:49] malev: basically anything new or confirmed probably needs to be addressed in some way by us unless it's old [23:49] excelent!!!! I going for it :D [23:49] malev: feel free to ask any questions you want here [23:55] hey it's me again [23:55] I've found this: [23:55] https://bugs.edge.launchpad.net/ubuntu/+source/netkit-telnet/+bug/41145 [23:55] Launchpad bug 41145 in netkit-telnet "Escape character does not work" [Medium,New] [23:56] I've got a latin american keyboard and I cant' reproduce the bug. ctrl + ] works really fine! [23:56] maybe I can recomend the user to update the system and... I don't know, close the bug. what do you think?