| hggdh | same here :-) | 00:06 |
|---|---|---|
| charlie-tca | RedSingularity: didn't even have to wait until tomorrow - bug 655024 | 00:37 |
| ubot2 | Launchpad bug 655024 in transmission (Ubuntu) "Using higher cpu usage (affects: 2) (dups: 1) (heat: 16)" [Undecided,New] https://launchpad.net/bugs/655024 | 00:37 |
| slinker | charlie-tca - when you use thunderbird and retry your account, it works | 00:51 |
| slinker | I'll add that to the bug | 00:51 |
| slinker | if you want | 00:52 |
| charlie-tca | okay. That helps narrow it | 00:52 |
| === ivoks is now known as ivoks-afk | ||
| RedSingularity | bug 655024 | 02:14 |
| ubot2 | Launchpad bug 655024 in transmission (Ubuntu) "Using higher cpu usage (affects: 2) (dups: 1) (heat: 16)" [Undecided,New] https://launchpad.net/bugs/655024 | 02:14 |
| bcurtiswx | RedSingularity, what about it? | 02:22 |
| RedSingularity | bcurtiswx: sorry nothing, I just wanted to see it. | 02:38 |
| bcurtiswx | RedSingularity, there is something that you could do to it :) | 02:45 |
| RedSingularity | bcurtiswx: ?????????? You mean take it? | 02:46 |
| micahg | !msgthebot | RedSingularity | 02:46 |
| ubot2 | RedSingularity: Please investigate with me only with "/msg ubottu Bot" or in #ubuntu-bots. Search for factoids with "/msg ubottu !search factoid". | 02:46 |
| bcurtiswx | RedSingularity, are you a mentee? | 02:46 |
| bcurtiswx | micahg, ? | 02:47 |
| RedSingularity | bcurtiswx: I never "formally" signed up to be one but i would love the help...... | 02:47 |
| micahg | bcurtiswx: ? | 02:47 |
| hggdh | micahg, bcurtiswx: ?? | 02:47 |
| bcurtiswx | hggdh, micahg: ??? | 02:48 |
| hggdh | yes! A loop is created | 02:48 |
| * bcurtiswx starts evil laughter | 02:48 | |
| bcurtiswx | RedSingularity, have you read or are reading wiki.ubuntu.com/Bugs/HowToTriage ? | 02:48 |
| RedSingularity | bcurtiswx: I read it but i keep going back to re-read things all the time. | 02:49 |
| bcurtiswx | RedSingularity, great! So you can take on that bug then. You've got me and or hggdh and or micahg and or just about everyone in here to bug with questions | 02:50 |
| bcurtiswx | RedSingularity, What do you see as the first step to bug triage? | 02:50 |
| bcurtiswx | no pun intended.. either.. :) | 02:51 |
| RedSingularity | bcurtiswx: According to the site? | 02:52 |
| bcurtiswx | RedSingularity, sure | 02:53 |
| RedSingularity | bcurtiswx: ........I have not scene a step by step guide...is there one available? That would be a big help to me! | 02:54 |
| bcurtiswx | RedSingularity, hmm, there used to actually be one. not sure where it is. The first thing you want to do is make sure the bug is not a duplicate | 02:56 |
| bcurtiswx | the most common approach is by using google search and typing in site:bugs.launchpad.net <package> <some keywords from bug> | 02:56 |
| bcurtiswx | RedSingularity, its easy to get confused, and if you are unsure about a bug being a duplicate don't worry about it and move to the next step | 02:57 |
| bcurtiswx | RedSingularity, try that out with this bug and let me know if this bug is potentially a duplicate | 02:59 |
| RedSingularity | bcurtiswx: Ok | 03:00 |
| RedSingularity | bcurtiswx: I dont see any duplicates when searching in google.... | 03:02 |
| bcurtiswx | RedSingularity, good, neither do I. There is one, but it's already been marked as a duplicate of our current bug | 03:03 |
| bcurtiswx | remember to be slightly vague in your search, it will give you more potential duplicates | 03:04 |
| RedSingularity | bcurtiswx: and you used google correct? | 03:04 |
| bcurtiswx | i think the most time consuming part of bug triage is seeing if your bug is a duplicate, lots of searching. | 03:04 |
| bcurtiswx | RedSingularity, yes | 03:04 |
| bcurtiswx | my search was site:bugs.launchpad.net transmission cpu | 03:05 |
| RedSingularity | oh ok | 03:05 |
| RedSingularity | why put site: in before th e rest? | 03:05 |
| bcurtiswx | that will search only that specific site | 03:05 |
| RedSingularity | ohhhhh i see | 03:05 |
| RedSingularity | thats a great feature! | 03:06 |
| bcurtiswx | RedSingularity, Next what we'll want to check is to make sure that the bug has certain pieces of information. | 03:06 |
| bcurtiswx | Most common is first, that it has a package assigned to it (not just "ubuntu" as the package name) | 03:07 |
| bcurtiswx | Second: the version of the package this bug is being reported against | 03:07 |
| RedSingularity | Ok looks like it is assigned to transmission | 03:07 |
| RedSingularity | transmission 2.04-0ubuntu2 | 03:08 |
| bcurtiswx | now type in your terminal 'apt-cache policy transmission' | 03:08 |
| RedSingularity | ok did that | 03:09 |
| bcurtiswx | im assuming your sources are fully up to date, done by running 'apt-get update; apt-get upgrade' | 03:09 |
| bcurtiswx | so the versions should match up, correct? | 03:10 |
| RedSingularity | Candidate: 1.93-0ubuntu0.10.04.1 | 03:10 |
| RedSingularity | thats what i have | 03:10 |
| bcurtiswx | RedSingularity, running Lucid ? | 03:10 |
| RedSingularity | Yeag | 03:10 |
| RedSingularity | yeah | 03:10 |
| bcurtiswx | OK, http://launchpad.net/ubuntu/+source/transmission | 03:10 |
| bcurtiswx | you can see in the bug report that the user is reporting against Ubuntu 10.10 | 03:11 |
| RedSingularity | Yeah | 03:11 |
| bcurtiswx | (Maverick Meerkat) | 03:11 |
| RedSingularity | Yep | 03:11 |
| bcurtiswx | so verify the two package versions match from the website and the report. You'll get times when the bug is reported against an older package | 03:12 |
| RedSingularity | Looks like they do | 03:12 |
| bcurtiswx | RedSingularity, yup. Next you'll want to check to make sure it has the Ubuntu version (which we've already verified) | 03:13 |
| RedSingularity | By version you mean "maverick"? | 03:13 |
| bcurtiswx | yeah or ubuntu 10.10 | 03:14 |
| RedSingularity | ok | 03:14 |
| bcurtiswx | just so we know what distro to test the bug against | 03:14 |
| bcurtiswx | Next we'll want to make sure the user has provided us with enough information to reproduce the bug. Most of the time this should be in the form of a step by step list on how it's reproduced | 03:15 |
| bcurtiswx | depending on the bug, you may only need a screenshot of the issue, other times you'll both | 03:15 |
| RedSingularity | Looks like its missing a step guide | 03:15 |
| bcurtiswx | RedSingularity, very good :) | 03:16 |
| bcurtiswx | After seeing what information is still needed , you'll then have to do a few things | 03:16 |
| bcurtiswx | click the down arrow next to the package name (the one typically with (ubuntu) after it) | 03:17 |
| RedSingularity | lets me assign a different package | 03:17 |
| bcurtiswx | and comment and (i don't remember) but you can change the status? | 03:17 |
| RedSingularity | yes | 03:18 |
| bcurtiswx | So what do you think you would set the status to at this point? | 03:18 |
| RedSingularity | incomplete? | 03:18 |
| bcurtiswx | RedSingularity, yup :) | 03:18 |
| RedSingularity | Should i make a comment? | 03:18 |
| bcurtiswx | Then you'll want to leave a comment requesting the information. We typically start comments with "Thanks for reporting this bug and helping to make Ubuntu better"... | 03:19 |
| bcurtiswx | (mostly when you're the first to work on triaging a bug" | 03:20 |
| bcurtiswx | ) | 03:20 |
| RedSingularity | What do i ask for though......the step by step reproducible guide? | 03:21 |
| bcurtiswx | Since that is all you're missing, yes | 03:21 |
| RedSingularity | Seems like someone already has this bug.......i dont want to take it from that person though :) | 03:21 |
| bcurtiswx | RedSingularity, I can see why you'd think that. If I don't see it marked as incomplete after requesting information, I typically go and make it "official" b y requesting the information and setting the status | 03:23 |
| RedSingularity | Oh ok | 03:23 |
| bcurtiswx | RedSingularity, if you want you can leave it as is, and just set status to incomplete | 03:24 |
| bcurtiswx | since technically the information's already requested | 03:24 |
| RedSingularity | whoops i did it already.....:( | 03:25 |
| bcurtiswx | RedSingularity, it's fine, really. | 03:25 |
| bcurtiswx | You did a good job. Now the only thing I forgot was to make sure you subscribe to the bug. This way you'll get an e-mail when the reporter replies | 03:27 |
| RedSingularity | Ok thats done too. | 03:27 |
| RedSingularity | bcurtiswx: You cant find the step by step triaging guide anywhere? That would be a great reference item. | 03:31 |
| bcurtiswx | hggdh, micahg, bdmurray ^^ ? | 03:31 |
| micahg | RedSingularity: from where? what about the HowTo Guide? | 03:32 |
| RedSingularity | micahg: That doesnt really say what to do step by step. The information seems scattered through the document. | 03:33 |
| micahg | RedSingularity: well, there is no exact step by step, there are generalities since each bug is different | 03:34 |
| bcurtiswx | micahg, there was a step by step at one point.. | 03:35 |
| micahg | RedSingularity: this is as close as it gets: https://wiki.ubuntu.com/Bugs/HowToTriage/Charts | 03:35 |
| bcurtiswx | micahg, it could have been eaten by the intermonster | 03:35 |
| bcurtiswx | micahg, thats it :) | 03:35 |
| bcurtiswx | a visual roadmap on where to go | 03:35 |
| micahg | bcurtiswx: I don't see it as possible, we can have a sample step by step triage of a few different bugs, but what questions need to be asked vary | 03:35 |
| RedSingularity | micahg: thanks a lot!! :) | 03:36 |
| bcurtiswx | micahg, that was it.. muchas gracias | 03:36 |
| micahg | bcurtiswx: RedSingularity, BTW, that's linked on the how to triage page :) | 03:36 |
| RedSingularity | thats a nice chart to follow! | 03:36 |
| bcurtiswx | too much reading.. lol | 03:37 |
| RedSingularity | I need to step away for a moment. Be back soon :) | 03:38 |
| === zyga is now known as zyga-gone | ||
| === JayFo is now known as JFo | ||
| === bilalakhtar_ is now known as cdbs | ||
| === ivoks-afk is now known as ivoks | ||
| === maxb_ is now known as maxb | ||
| === cdbs is now known as bilalakhtar | ||
| sulumar | Greetings | 10:47 |
| === sulumar is now known as Sulumar | ||
| jibel | Hi Sulumar | 10:54 |
| Sulumar | Greetings | 10:54 |
| === ivoks is now known as ivoks-afk | ||
| === drizztbsd_ is now known as drizztbsd | ||
| === greg_g is now known as greg-g | ||
| === ivoks-afk is now known as ivoks | ||
| alynwiz | Hello | 14:05 |
| === andreas_ is now known as anoteng | ||
| === drizztbsd_ is now known as drizztbsd | ||
| === ara__ is now known as ara | ||
| === deryck is now known as deryck[lunch] | ||
| === ivoks is now known as ivoks-afk | ||
| === deryck[lunch] is now known as deryck | ||
| === ivoks-afk is now known as ivoks | ||
| jonnor | In Ubuntu packages, which status should I use when the bug has been fixed upstream? (that is, in the applications development version) | 18:46 |
| micahg | jonnor: none | 18:47 |
| bdmurray | jonnor: do you have an example bug? usually you wouldn't change the ubuntu bug task status | 18:47 |
| jonnor | bdmurray: https://bugs.launchpad.net/ubuntu/+source/mypaint/+bug/581962 | 18:47 |
| ubot2 | Launchpad bug 581962 in mypaint (Ubuntu) "Manipulating view slow after using rotate (affects: 1) (heat: 26)" [Undecided,Incomplete] | 18:47 |
| micahg | jonnor: or rather, depends, if it's part of the desktop team packages, they set Fix Committed | 18:47 |
| bdmurray | it could at least be confirmed or triaged | 18:47 |
| bdmurray | you might be able to add a bug watch for that upstream bug report | 18:48 |
| jonnor | But if that is not possible, there is no way to track things that are fixed upstream? | 18:48 |
| bdmurray | well you could open a "fake" upstream task to show that it is fix released. When I say fake I mean one without a bug watch. | 18:49 |
| mrand | In a similar vein, it's very unfortunate that when upstream bugs are fixed (especially in debian), and those fixes are automatically pulled into ubuntu, that someone has to manually either add them to to the changelog or manually mark them as fix released. | 19:01 |
| mrand | (pulled into and then released in the next version of ubuntu, I mean). | 19:01 |
| bdmurray | in that case something could parse the changelog for debian bug numbers look for bug watches with that bug number and close the ubuntu task too? | 19:02 |
| mrand | yeah, that's what I was kinda hinting at. Something like that should be possible, but I don't know enough nitty gritty to know if something might block that being possible. | 19:03 |
| mrand | But it kinda gets more tricky than that... because it is fixed in a particular version, and so it's that version that has to be pulled into Ubuntu for it to be fixed. So that info has to get attached and then parsed/checked later. | 19:04 |
| === ivoks is now known as ivoks-icecream | ||
| jonnor | bdmurray: I added an upstream task now | 19:05 |
| jonnor | but I have to remove the connection to set the status of the upstream task (LP does not support my tracker) :(( | 19:05 |
| mrand | jonnor: can you set the status for both tasks? | 19:06 |
| mrand | sorry, you did set it to confirmed for Ubuntu. Were you going to mark it as resolved on the other task? | 19:07 |
| jonnor | mrand: https://bugs.launchpad.net/mypaint/+bug/565664 shows a nice link to the upstream task | 19:08 |
| ubot2 | Launchpad bug 565664 in mypaint (Ubuntu) (and 1 other project) "MyPaint freezes upon start because input device reports infinite pressure (affects: 1) (heat: 8)" [Undecided,Confirmed] | 19:08 |
| jonnor | however, try to set the status of the upstream task | 19:08 |
| jonnor | you then have to choose if you want to keep the nice "assigned to" link, or if you really want to set the status manually | 19:09 |
| jonnor | I see it as ideal if you could have both | 19:09 |
| === ivoks-icecream is now known as ivoks | ||
| jonnor | you could argue that the real bug is that LP does not support the Savannah tracker.. | 19:10 |
| mrand | yeah, looks like support is less than ideal: https://bugs.launchpad.net/malone/+bug/197250 | 19:12 |
| ubot2 | Launchpad bug 197250 in malone "Savannah bug watches should match longer URL (dups: 1) (heat: 1)" [Undecided,Triaged] | 19:12 |
| njin | hello, i'm testing ubuntu amd64 2010107, everythings ok, but at the start just after grun i've modprobe fatal error ....kernel 2.6.35..-generic. then plymouth stat regularry. In logs don't seems to be nothing relevant, but can you tell me where to look to found track of this ? | 19:13 |
| njin | Thanks | 19:13 |
| micahg | njin: maybe try #ubuntu-quality or #ubuntu+1? | 19:14 |
| njin | micahg: thanks | 19:14 |
| micahg | njin: actually, #ubuntu-testing | 19:15 |
| njin | ok thanks again | 19:15 |
| === ara__ is now known as ara | ||
| === ara__ is now known as ara | ||
| algnod | hi all, i am wondering, an application that stores passwords in clear text would that be considered a bug ? | 20:53 |
| penguin42 | algnod: Does it have an alternative? | 20:53 |
| micahg | algnod: can be | 20:53 |
| hggdh | algnod: generically, it is not a good idea | 20:53 |
| algnod | its liferea | 20:53 |
| penguin42 | algnod: i.e. does it need to pass the password in cleartext to something else? | 20:53 |
| micahg | algnod: hmm, I would think that should integrate with the gnome-keyring | 20:54 |
| algnod | penguin42 but it could still store it in gnome keyring or scramble it or whatever | 20:54 |
| algnod | i feel uncomfortable with my google email account password stored like that | 20:55 |
| micahg | oh, for some reason I thought it was a gnome project :-/ | 20:56 |
| greg-g | there was a bug against FileZilla about that exact issue, it went upstream and the upstream author said, effectively "it is the distribution's job to protect user specific files from other users" | 20:57 |
| greg-g | ie: he just wanted to keep his plaintext list of hosts/username/passwds for ease and have the distributions make sure that all user config files are only readable by that user | 20:57 |
| algnod_ | sorry guys i missed your prior responses | 20:59 |
| === gamerchick02_ is now known as gamerchick02 | ||
| m0ar | Gah, I wont get any unsubscription-message when I try to do that on the website. Anyone know why? | 21:48 |
| m0ar | I don't want to get spammed with the mailing list when I'm not even active/using ubuntu | 21:48 |
| hggdh | m0ar: you did unsibscribe, right? | 21:54 |
| m0ar | Tried, yes | 21:55 |
| hggdh | you either did, or did not | 21:55 |
| m0ar | No, since the page seems to be somewhat buggy for me | 21:56 |
| m0ar | I fill in my email, I click unsubscribe. I get no message, I try to reset my password with that form; no email then either | 21:57 |
| m0ar | But the emails from the list keeps failling in, it's annoygin | 21:57 |
| hggdh | which mailing list? | 21:58 |
| m0ar | ubuntu-bugsquad | 21:58 |
| m0ar | https://lists.ubuntu.com/mailman/options/ubuntu-bugsquad | 21:59 |
| hggdh | m0ar: PM me your email address | 21:59 |
| m0ar | hggdh: Done | 21:59 |
| hggdh | got it. Give me a sec | 22:00 |
| m0ar | Yeah, thanks | 22:01 |
| hggdh | m0ar: OK. Please send me an email from your email address -- send it to hggdh2 at ubuntu dot com | 22:01 |
| hggdh | m0ar: I need to verify if you are indeed the owner | 22:02 |
| m0ar | Done and done | 22:02 |
| hggdh | now we wait for the email to arrive... | 22:02 |
| hggdh | m0ar: I just replied. Can you please write here my response? | 22:05 |
| m0ar | hggdh: ça va | 22:05 |
| hggdh | oui, ça va bien | 22:05 |
| m0ar | Moi? | 22:06 |
| m0ar | ca va bien, merci | 22:06 |
| m0ar | Ah, thanks. Got the unsubscription mail now, thanks | 22:06 |
| hggdh | mon plaisir | 22:06 |
| hggdh | OK. Now for a reboot to clean up a persistent window | 22:17 |
| === ivoks is now known as ivoks-afk | ||
| jcastro | hggdh: around? | 22:49 |
| jcastro | oh nevermind, you're cloud guy | 22:50 |
| hggdh | but I am here | 22:51 |
| drizzle | how do you assign the 1000 paper cuts tag? | 22:54 |
| micahg | drizzle: you mean nominate for 100 papercuts project? | 22:57 |
| drizzle | yea | 22:57 |
| drizzle | is that something that we tag bugs as | 22:57 |
| drizzle | or was that a one-off deal | 22:57 |
| micahg | drizzle: Also affects project hundredpapercuts | 22:57 |
| MichealH-iPod | And that's how you get it in hundredpapercuts | 22:58 |
| jcastro | can someone help me reassign a task? | 22:59 |
| jcastro | bug #636311 | 22:59 |
| ubot2 | Launchpad bug 636311 in xserver-xorg-input-evdev (Ubuntu) (and 1 other project) "Keyboard special keys interfere with mouse (affects: 11) (dups: 1) (heat: 64)" [Undecided,Confirmed] https://launchpad.net/bugs/636311 | 22:59 |
| micahg | jcastro: what;s the issue? | 22:59 |
| jcastro | I would like to have it affects the release-notes-team | 22:59 |
| micahg | in addition to what's there? | 22:59 |
| jcastro | no | 23:00 |
| jcastro | in place of the upstream link | 23:00 |
| micahg | hmm, let me see | 23:00 |
| micahg | jcastro: no, we can't anymore | 23:00 |
| micahg | jcastro: have to ask an LP admin | 23:00 |
| jcastro | @#$%^#$% | 23:00 |
| meetingology` | jcastro: Error: "#$%^#$%" is not a valid command. | 23:00 |
| micahg | jcastro: wait | 23:00 |
| micahg | I got logged out :-/ | 23:01 |
| micahg | jcastro: done | 23:01 |
| jcastro | ok how did you do that? | 23:02 |
| MichealH-iPod | I think you need to be in BugControl | 23:02 |
| micahg | jcastro: you should see a pencil next to the upstream project, click it and select a new project | 23:02 |
| micahg | MichealH-iPod: no | 23:02 |
| jcastro | I'm an admin on bug control. :) | 23:03 |
| MichealH-iPod | Okay micahg | 23:03 |
| jcastro | ok, I clicked on the pencil the first time | 23:03 |
| micahg | jcastro: you type a search term for the project and then select the one you want | 23:03 |
| jcastro | ok | 23:04 |
| jcastro | thanks for the help. <3 | 23:04 |
| micahg | jcastro: np | 23:05 |
| MichealH-iPod | jcastro: Can I PM you? | 23:09 |
| jcastro | sure | 23:11 |
| === MichealH-iPod is now known as SuperHark | ||
| SuperHark | This.... thing! | 23:17 |
| === SuperHark is now known as Guest96652 | ||
| Guest96652 | I can't /privmsg, /msg or /query GRr | 23:17 |
| Guest96652 | jcastro: Were you getting PM's off MichealH-iPod? | 23:18 |
| === Guest96652 is now known as MichealH_ | ||
| jcastro | yes | 23:19 |
| MichealH_ | Good It works | 23:19 |
| MichealH_ | But This iPod lags! | 23:20 |
| MichealH_ | jcastro: Have you replied to my /msg? | 23:23 |
| layn | hi | 23:27 |
| MichealH-iPod | Hi | 23:27 |
| layn | MichealH-iPod hello how are you? | 23:28 |
| MichealH-iPod | I'm okay | 23:29 |
| layn | MichealH-iPod, what do you think of the new server settings with regard to the expiration bug? | 23:29 |
| MichealH-iPod | Ubuntu Server? Woah.. I have never used it | 23:30 |
| layn | MichealH-iPod, I was not referring to ubuntu launchpad server but you are aware of the new settings on the management of the platform and the triaging bugs? | 23:33 |
| MichealH-iPod | Huh? | 23:33 |
| layn | MichealH-iPod, ok | 23:36 |
| MichealH-iPod | layn: Can you explain it | 23:37 |
| micahg | layn: Ubuntu will be using it AFAIK | 23:38 |
| MichealH-iPod | Micahg: Can you explain? | 23:38 |
| micahg | MichealH-iPod: http://blog.launchpad.net/general/enabling-automatic-bug-expiry | 23:39 |
| layn | MichealH-iPod, ohh! yes | 23:41 |
| MichealH-iPod | So if I makes a bug incomplete it expires? | 23:41 |
| hggdh | right now, no. If (and when) expiry is set | 23:42 |
| hggdh | then the bug will be invalidated after (say) 60 days of no response | 23:42 |
| MichealH-iPod | Anyway I'm off | 23:42 |
| layn | hggdh, yes | 23:43 |
| MichealH-iPod | huffy: Okay | 23:43 |
| MichealH-iPod | Bye all | 23:43 |
| layn | hggdh thanks | 23:43 |
| hggdh | layn: welcome | 23:43 |
| layn | In fact I think it's a positive change in that regard, it has a more powerful even as regards the data that is then uploaded to the database | 23:45 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!