/srv/irclogs.ubuntu.com/2008/11/30/#ubuntu-bugs.txt

=== theseinfeld is now known as theseinfeld_
=== theseinfeld_ is now known as theseinfeld
anakronhi01:50
anakroni have one question01:50
anakronif a bug is related to a bad translated word into a po file, can i change that file and then make a patch for this program?01:50
anakron¿?01:54
PrivateVoidhello01:58
PrivateVoidanakron, I think that is how it works... but I am far from an expert01:58
theseinfeldyes. did you submit the bug?01:58
theseinfeldif you did, you can add the patch there01:58
theseinfeldthe maintainer should see it, push it upstream, etc...01:59
anakroni want to make a patch for it01:59
anakroni know how to01:59
theseinfelddo you want people to know about the patch?01:59
theseinfeldor you want to make it for yourself?01:59
anakronbut i dont know if i can change that bad translation into the po file?01:59
anakronor it must be by a translation team02:00
anakroni think that i can02:00
anakronbut i dont know if this must be done by me or Translation team member+02:03
hggdhanakron, you can change it, and propose it in  a patch02:26
anakronok thanks a lot02:27
anakronmmm02:27
anakronbut i have a question02:27
anakronsomeone know a right translation of "Cheese Webcam Booth" to german??02:28
=== Hurtz_ is now known as Hurtz
Taz.07:56
macowell that was lengthy08:00
ajmorrishello all, i have a question with pbuilder...09:25
ajmorriswhen trying to run a pbuilder build, i get this error:09:25
ajmorrishostname: Host name lookup failure09:25
ajmorrisi get that error if i run pbuilder from /var/cache/pbuilder if i run it from the directory where i want to build the package from, i get:09:29
ajmorrishostname: Unknown host09:29
ajmorrisbeen trying to fix it, but been unsuccessfull, anyone here have any insight?09:29
macoajmorris: er, don't you have a pbuilder script that you created when you set it up? i have a ~/pbuilder-hardy and i use "./pbuilder-hardy build src/blablah.dsc"09:36
=== Igorot_ is now known as Igorot
=== BaD-IPv6 is now known as BaD^CrC
krychekwhat can be done about these feisty/gaim crash reports: https://bugs.launchpad.net/ubuntu/+source/gaim ?17:08
mrooneykrychek: hmm yes that looks like a good area to clean up17:59
krychekmrooney: will you do it? :)18:00
mrooneyhaha I don't think I could handle that many bugs18:00
krychekwhat should be the standard reply here?18:00
mrooneybasically for all the ones without recent activity, you would want to ask if they still experience it and if so can they try with the most recent pidgin (via backports or perhaps an intrepid livecd)18:01
mrooneyand mark the status incomplete18:01
krychekFeisty/gaim are not supported anymore. Please reopen if this is still an issue with pidgin in a later version of Ubuntu. ?18:01
krychekwhy not directly to invalid?18:02
mrooneyOh yes I forgot Feisty isn't supported18:02
mrooneyso if they are bugs from Feisty then sure that seem reasonable, though maybe a little friendlier :)18:03
krychek:)18:03
krychekcould you check this: bug 2081218:04
ubottuLaunchpad bug 20812 in synaptic "Error messages for failed downloads should be less complicated" [Low,Confirmed] https://launchpad.net/bugs/2081218:04
mrooneyI was going to say you could recommend enabling backports if they still want to use Feisty to get a newer version but, there doesn't appear to be one for Feisty?18:04
krycheki think this is the most least recently commented18:05
mrooneysure I can triage that one better18:05
mrooneybut that isn't gaim, how did you find that one18:05
krychekthat is the most "least recently changes" bug as i mentioned18:06
krychekchanged18:06
mrooneyOh I see!18:07
mrooneyOkay I just asked if it was still an issue and marked it as Incomplete18:08
mrooneythat way it will automatically expire if no one cares about it18:09
krychekbut that doesnt mean itll get set to invalid18:09
krycheki dont think that was an issue anyway..18:10
krychekit was rather a suggestion18:10
mrooneykrychek: I thought that was exactly what happened, after the period of time they are Invalidated. Although because that synaptic bug has an assignee, it may not.18:13
krycheki dont think they will be invalid18:14
krychekitll just say "this bug has expired 241 days ago"18:15
krychekThis bug report was marked for expiration 40 days ago.18:18
=== mdz__ is now known as mdz
=== mdz__ is now known as mdz
jsmidtHow do I change the importance of a feature request to wishlist?  Launchpad seems to indicate I don't have permissions.  Is there something I need to do to get permissions?20:05
jsmidtI am trying to learn this 5 a day stuff out.20:06
mrooneyjsmidt: BugControl has the permissions to do so, if you point it out I can do so20:07
mrooneyjsmidt: https://wiki.ubuntu.com/UbuntuBugControl20:07
mrooneyYou may also want to apply yourself if you have been doing bug stuff for a bit!20:08
jsmidtmrooney, this is the bug: 303757.  So, after spending some time doing 5 a day stuff I could join the team?20:11
mrooneyjsmidt: yeah, are you in BugSquad now?20:11
mrooneybug 30375720:11
ubottuLaunchpad bug 303757 in gnome-applets "Let the weather in gnome clock display forecast" [Undecided,Confirmed] https://launchpad.net/bugs/30375720:11
jsmidtYes20:11
jsmidtBut an just beginning to try the 5 a day thing.20:12
mrooneyjsmidt: yes, that sounds good. Once you feel you have a good handle on triaging you can apply to BugControl and you can do a few more things like set importance and change status to triaged and wontfix20:13
jsmidtmrooney, okay, sounds great.20:13
RAOFjsmidt: You know what would be _really_ useful on that bug report?  Bouncing it upstream to the Gnome bugzilla.20:14
mrooneyjsmidt: also you aren't supposed to confirm your own bug reports :)20:14
mrooneythat doesn't really do anything20:14
jsmidtRAOF, good idea.20:14
jsmidtmrooney, yeah, makes since, I won't do that any more. :)20:15
RAOFObviously, search for existing feature requests first.20:15
mrooneyhm Launchpad is acting up a little, or something today20:15
krychekSorry, there was a problem connecting to the Launchpad server.         :)20:31
krychektoo many ppl triaging at the moment?20:31
krychekNew (40%) wow :)20:32
krychekwhy do ppl set their own bugs to confirmed?20:40
krycheki dont think the confirmed status makes any sense anyway20:41
krychekif a bug has 5 duplicates that means its confirmed20:42
RAOFNot necessarily, but it's a data point.20:43
krychekdo you think confirmed or new bugs get more attention?20:45
raboofi'd hope the former :)20:46
krychekim not sure about that.. since anyone can set it to confirmed20:51
krychekand triagers look at "new" bugs first, dont they?20:52
jjessekrychek: some bug triagers look at specific packages20:52
krychekye, sure, but they dont care about if its new or confirmed.. ?20:54
jjessekrychek: it depends i think some maintain packages while others look at all bugs20:55
raboofif i was looking for something to fix i'd probably look at confirmed bugs first - assuming i'd be confident there are enough triagers around to look at and confirm/reject 'new' ones20:56
krycheknobody should be allowed to set their own bugs to confirmed anyway20:56
jjessecorrect20:57
raboofagreed (unless it's someone intimite to the package)20:57
krychekmaybe only priviliged users should be allowed to set them to confirmed?20:58
raboofdo we have a concept of 'priviliged users'?20:59
greg-gyes20:59
krycheksame ppl who can change the status20:59
krychekimportance20:59
krycheki mean20:59
krycheksame ppl who can change the importance.21:00
raboofperhaps this is kept open to make it as easy as possible for a new triager to get started?21:02
hggdhraboof, indeed. A beginner triager can do most21:21
hggdhkrychek, anyone can set a bug confirmed. Only bug-control can set it traiged21:22
hggdhmrooney, I will not be able to be at UDS as I wanted -- I am stuck in Toronto for 4 weeks21:22
mrooneyhggdh: oh how sad, alas!21:23
mrooneyhggdh: doing anything fun in Toronto at least?21:23
hggdhyes, looking at sleet/snow/rain, all at the same time21:24
hggdhhere just a normal contract -- being available for a potential crisis during the black friday sell period21:24
xteejxHi guys21:58
xteejxThe needs-packaging bug reports: Once they have been confirmed as not in ubuntu or debian, do we nominate them for release for jaunty?21:59
xteejxanyone?22:18
xteejxAlso, everyone keep an eye on the amount of bugs, I'm clearing loads of old crap out that hasn't been touched since April - don't worry I'm going by the Procedures :) But these needs-packaging I'm checking them against Ubuntu and Debian package search and confirming them if they're not there per the guidelines, but do they need nominating for release or is that down to the reporter to do that, as22:23
xteejxI haven't seen anything on the Wiki about it.22:23
krychekxteejx: todays drop in the number of bugs wasnt only your work ;)22:30
krycheki dont touch needs-packaging bugs22:32
krycheki dont know if theyre official or just somebody wants to get his program packaged22:32
nhandlerxteejx: You do not need to nominate them. They will get added to the repositories once someone chooses to package it and go through the REVU process22:38
xteejxnhandler: Ok one less thing to worry about. Thanks :)22:40
xteejxI don't normally touch needs-packaging either but I'm working on the New bugs in reverse order, as there's a hell of a lot of bugs over 6 months old22:41
xteejxCan't be good for the stats, and most are for older versions, yes I know they're still supported but a majority are kernel related22:41
nhandlerYou're welcome xteejx. One thing you can do (although it isn't a big deal) is check to see if the package has been uploaded to REVU or mentors.debian.net. If it has, you can add a link to the package on LP. But like I said, only do this if you really have nothing better to do with your time22:41
xteejxnhandler: I haven't lol22:42
xteejx:)22:42
nhandler:)22:42
krychekwhat do you with really old wishlist bugs?22:42
xteejxCan't work cuz of a disability so a lot of my time is bug hunting - usually crap on TV during the day anyway22:43
nhandlerkrychek: It depends on the bug22:43
nhandlerkrychek: Is the bug still valid?22:43
krychekim just asking generally.. since there are a lot of them22:43
nhandlerkrychek: If the bug is still valid, just leave it alone.22:44
xteejxold wishlist ones i check against ubuntu and debian package search facilites and see if any are already available, ie have been packaged since the original bug report. If so, invalidate them and explain why. if not, confirm them22:44
nhandlerxteejx: I would mark them Fix Released, but it isn't a big deal22:44
xteejxi only found 1 anyway but i'll remember for the next one i come across :) didn't think about fix released to be honest22:45
krycheki wont care about them then..22:45
xteejxit's kool krychek i'm going through them all anyway, i'm setting that as my main task, clearing old crap out :)22:45
krychekwhat about old fix commited ones?22:45
krychekxteejx: im doing bugs in least recently changed order :)22:46
xteejxcheck with the package maintainer if these have been committed to PPA first see if they're activaly working on them22:46
nhandlerkrychek: Same as wishlist. If they have been released (in the repos), change them to Fix Released. Otherwise, if they are still just in VCS, leave them as Fix Committed22:46
xteejxkrychek: lol probably see some disappear then22:46
nhandlerxteejx: Fix Committed should be for a VCS, not really a PPA22:47
xteejxI see. So what about the ones that people have uploaded to their PPA, should we leave as Incomplete and link it?22:47
nhandlerxteejx: Do you have an example of one?22:47
nhandlerFor most types of bugs, a PPA is really pointless22:48
xteejxNot off hand no I havent come across one yet22:48
xteejxJust hypothetically :)22:48
nhandlerUsually, if they have it in a PPA, it is already Confirmed, so I would just leave it that way22:48
xteejxOK cool.22:48
nhandlerIf the bug hasn't been confirmed, they really shouldn't have bothered fixing it ;)22:49
xteejxTrue I suppose lol :)22:49
xteejxBy the way I've got rid of about 100 or so in 3 hours - 100 less New status bugs :)22:49
krychekcould you check on my own bug: i dont think pedro was fair: bug 294264        just check the screenshot22:50
ubottuLaunchpad bug 294264 in gnome-panel "workspace switcher shows twice as many workspaces than the value has been set" [Low,Incomplete] https://launchpad.net/bugs/29426422:50
krychekhe wants exact steps22:50
krychekbut the bug only occurs in every 10th or so bootups22:50
xteejxany chance of a dmesg log?22:51
xteejxforgot that22:51
xteejx*forget22:51
krychekthere is a second screenshot with my other bug, but i didnt want to report it22:52
nhandlerkrychek: The bug is incomplete until someone else can confirm it on their machine.22:52
xteejxHas the user rebooted after this and it still appears? It could eb that workspace-switcher is not saving the setting until user logout22:52
krychekhappens very rarely22:52
xteejxvery strange bug22:52
krycheknhandler: the bug should be new until someone else confirms it :)22:53
krychekxteejx: im the user22:53
xteejxor incomplete if more info is needed22:53
xteejxohhhhh right sorry krycheck didnt realise :)22:53
xteejx*krychek22:53
nhandlerkrychek: The bug does not have the appropriate information for someone to confirm it22:53
krychekyou but i cant give exact steps..22:53
nhandlerkrychek: Which is why it is incomplete ;)22:54
krychekyou=ye22:54
xteejxkrychek: Are you able to grab a backtrace of some sort when it happens next time?22:54
krychekbut how am i supposed to give exact steps? turn on the comp and sometimes its happening22:54
nhandlerkrychek: If there aren't exact steps, a developer will not be able to reproduce it. If they can't reproduce it, they won't fix it22:54
krycheki understand that..22:55
xteejxkrycheck: Your best option is to try and somehow get a backtrace just after the problem occurs, if possible. This will definately help devs to sort it out. :)22:56
krychekhow can i do it?22:56
xteejx1 sec22:56
xteejxhttps://wiki.ubuntu.com/DebuggingProcedures22:56
krychekhttps://wiki.ubuntu.com/Backtrace ? ill read this tomorrow22:57
xteejxPretty much everything you need to provide the required info will be on that wiki page. In your case try GNOME applets22:57
krychekok thx22:58
xteejxno probs :)22:58
krychekcould you check the second screenshot on the same bug?22:58
krycheki mean its another bug22:58
krychekhave you seen it before?22:59
krychekhttp://launchpadlibrarian.net/19889385/systemmonitor.png22:59
xteejxI have seen it, the 4 thin lines where the workspaces should be....but I haven't come across it before no.23:00
krychekno, not the workspaces23:00
krychekthe system monitor23:00
krychekcheck the first screenshot :)23:00
krychekhttp://launchpadlibrarian.net/19394998/workspacebug.png23:01
krychekok im going to bed now23:05
krychekbye23:05

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!