From brian at ubuntu.com Fri Dec 3 22:58:23 2010 From: brian at ubuntu.com (Brian Murray) Date: Fri, 3 Dec 2010 14:58:23 -0800 Subject: Packages to investigate In-Reply-To: <4CF4D727.4010700@ubuntu.com> References: <20101122212222.GU7786@murraytwins.com> <4CF4D727.4010700@ubuntu.com> Message-ID: <20101203225823.GA7786@murraytwins.com> On Tue, Nov 30, 2010 at 11:51:19AM +0100, Jean-Baptiste Lallement wrote: > On 11/22/2010 10:22 PM, Brian Murray wrote: > > As we all know there are a lot of packages and bugs to keep track of in > > Ubuntu. One idea that occurred to me recently, to help identify > > packages in need of triage, was to calculate an average bug heat for the > > particular package. I've made a first pass at this using all the > > packages in the ubuntu-desktop package set. Here are the top 10 > > packages: > > > > usb-modeswitch-data - median: 764, mode: 1448 > > language-pack-gnome-fa-base - median: 408, mode: 408 > > language-pack-gnome-pt - median: 318, mode: 318 > > couchdb-glib - median: 210, mode: 210 > > netbook-meta - median: 145, mode: 408 > > pyopenssl - median: 136, mode: 259 > > shotwell - median: 124, mode: 6 > > appmenu-gtk - median: 122, mode: 408 > > gnome-python-extras - median: 114, mode: 3 > > telepathy-gabble - median: 104, mode: 49 > > > > As I ran this last Friday there might be some variance in the numbers. > > I'm curious whether or not you think the bug reports for these packages > > really need reviewing. > > > > Thanks, > > > Thanks Brian. This is really interesting. If we apply this calculation > to the packages installed by default in Natty, the top 10 looks like: > shotwell - median: 189 > empathy - median: 91 > gcalctool - median: 86 > gbrainy - median: 86 > gwibber - median: 81 > simple-scan - median: 76 > software-center - median: 68 > pitivi - median: 68 > transmission - median: 60 > gnome-bluetooth - median: 59 > > Compared to the list based on the number of bugs: > evolution > firefox > gdmsetup > nautilus > nm-connection-editor > ooffice > software-center > totem > update-manager > > So I can not say that this is the list that I had in mind, but the > result is expected. > When we build the list based on volume of bugs, we get the most used > applications. But when we use the bug heat we get the applications with > fewer bugs but which are in need of triage (I'm not saying that the > applications with a large number of bugs don't need triage) > > The list needs a closer look though. For instance: > - shotwell is in 1rst position, but when I look at the reports, there > are 2 bugs with a heat of 3491, and I don't see anything specific that > could explain such a value. Is it the weight of untriaged report being a > bit too important or something else ? It doesn't seem to match the bug > heat algorithm. Looking closer at the bug heat algorithm it seems that a fair bit of it is based on recent activity. From some of the documentation the theory follows: Bug has been active within the past 24 hours Add 25% of the project's hottest bug's score divided by the number of days since the first activity on the bug in question Bug has not been active* in within the past 24 hours Subtract 1% of the bug heat score for every day of inactivity So it seems to follow that the newest bugs will the highest heat. I guess there is a larger question of what we think makes a bug hot. Initially, I thought the number of users affected, number of subscribers and number of duplicates (among some other things) was a good indicator. Two out of those three things are now cached on the bug table so we could recreate the bug heat without taking into account recent activity. I feel like this might provide a more useful number. > - gbrainy, I was surprised to find a game in the list. In fact, there is > a very limited number of bugs filed against this package and some of > them with high heat. I've triaged the report with the highest heat > (>300) and it fell to a heat of 12. So the next run of your script > should move it lower into the list. > - gcalctool, same thing, the first bug had a heat of 237, and after > asking for more information it fell to 8. > > So, yes, this is useful to help us to direct our testing and triaging > effort. But the calculation of the bug heat needs to be clarified. > Maybe this could be added to the 'Opportunities' list in harvest ? By this do you mean the hottest, those outside the standard deviation, bugs for a package should be listed as an opportunity in harvest? Thanks, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From lakshay94 at gmail.com Sat Dec 4 13:08:12 2010 From: lakshay94 at gmail.com (Lakshay Pushkarna) Date: Sat, 04 Dec 2010 13:08:12 -0000 Subject: [Bug 685150] Re: Link in BurningIsoHowto Only For 2000/XP/Vista/7 References: <20101204120110.21747.19914.malonedeb@gandwana.canonical.com> Message-ID: <20101204130815.22720.2087.launchpad@palladium.canonical.com> ** Changed in: ubuntu-docs (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-docs (Ubuntu) Assignee: (unassigned) => Ubuntu BugSquad (bugsquad) ** Changed in: ubuntu-docs (Ubuntu) Assignee: Ubuntu BugSquad (bugsquad) => Lakshay Pushkarna (lakshay94) -- You received this bug notification because you are a member of Ubuntu BugSquad, which is a bug assignee. https://bugs.launchpad.net/bugs/685150 Title: Link in BurningIsoHowto Only For 2000/XP/Vista/7 From marconifabio at ubuntu-it.org Sun Dec 5 16:46:14 2010 From: marconifabio at ubuntu-it.org (njin) Date: Sun, 5 Dec 2010 17:46:14 +0100 Subject: Please assign status --linux bug Message-ID: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/538650 --Wishlist -------------- next part -------------- An HTML attachment was scrubbed... URL: From nightnaiad at gmail.com Sun Dec 5 18:34:28 2010 From: nightnaiad at gmail.com (Calla) Date: Sun, 5 Dec 2010 10:34:28 -0800 Subject: Please unsubscribe me Message-ID: Will you please hake me off your mailing list? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyan.spam at gmail.com Sun Dec 5 18:38:06 2010 From: cyan.spam at gmail.com (David Tombs) Date: Sun, 05 Dec 2010 13:38:06 -0500 Subject: Please unsubscribe me In-Reply-To: References: Message-ID: <4CFBDC0E.1070009@gmail.com> You can do this yourself. Please see the link at the bottom. Thanks, David On 12/05/2010 01:34 PM, Calla wrote: > Will you please hake me off your mailing list? > From noreply at ubuntu.com Sun Dec 5 16:25:29 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 05 Dec 2010 16:25:29 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_cro?= Message-ID: <20101205162529.611.79255@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by cro: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=21&rev2=22 The comment on the change is: Fixed a typo: weather -> whether ------------------------------------------------------------------------------ $ xinput --list }}} You will see the same name of Touchpad as above. - 3. Check weather synaptics module is correctly loaded in xserver or not in. {{{ + 3. Check whether synaptics module is correctly loaded in xserver or not in. {{{ $cat /var/log/Xorg.0.log | grep -i synaptics }}} From sysadmin at ngocentre.org.vn Mon Dec 6 10:26:05 2010 From: sysadmin at ngocentre.org.vn (Rakesh Ambati) Date: Mon, 06 Dec 2010 17:26:05 +0700 Subject: Request Membership Renewal Message-ID: <1291631165.2391.27.camel@arky-laptop> Hi List, My Ubuntu BugSquad is due to expire soon. Can someone renew my Ubuntu Bugsquad membership. LP ID: arky Wiki: https://wiki.ubuntu.com/arky TIA --arky From hggdh2 at ubuntu.com Mon Dec 6 17:15:32 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Mon, 06 Dec 2010 11:15:32 -0600 Subject: Request Membership Renewal In-Reply-To: <1291631165.2391.27.camel@arky-laptop> References: <1291631165.2391.27.camel@arky-laptop> Message-ID: <4CFD1A34.9090009@ubuntu.com> On 12/06/2010 04:26 AM, Rakesh Ambati wrote: > Hi List, > > > My Ubuntu BugSquad is due to expire soon. Can someone renew my Ubuntu > Bugsquad membership. > > LP ID: arky > Wiki: https://wiki.ubuntu.com/arky Hello arky, You should be able to renew your bugSquad membership yourself -- the email you received should have a link for doing so. If this did not happen, please get back to us with details and a copy for the email you received about the membership expiring. Cheers, ..C.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: From lyz at ubuntu.com Tue Dec 7 04:34:21 2010 From: lyz at ubuntu.com (Elizabeth Krumbach) Date: Mon, 6 Dec 2010 20:34:21 -0800 Subject: Triaging session for #ubuntu-classroom? Message-ID: Hi folks, We've had a couple requests in the past month for a stand-alone bug triaging #ubuntu-classroom session. Would someone on the Bug Squad team be willing to do such a session this month or next? It doesn't need to be complicated, just a run through the basics of triaging and then some Q&A for attendees. If you're not familiar with Ubuntu Classroom, see the project wiki page, which includes links to past sessions: https://wiki.ubuntu.com/Classroom Thanks! -- Elizabeth Krumbach // Lyz // pleia2 http://www.princessleia.com From ilidrissiamine at gmail.com Tue Dec 7 14:17:07 2010 From: ilidrissiamine at gmail.com (ilidrissiamine at gmail.com) Date: Tue, 7 Dec 2010 14:17:07 +0000 Subject: Triaging session for #ubuntu-classroom? In-Reply-To: References: Message-ID: I'm available every day from 17:00UTC to 18:00 UTC, if you would like me to do this session :) Mohamed Amine IL Idrissi On Tue, Dec 7, 2010 at 4:34 AM, Elizabeth Krumbach wrote: > Hi folks, > > We've had a couple requests in the past month for a stand-alone bug > triaging #ubuntu-classroom session. Would someone on the Bug Squad > team be willing to do such a session this month or next? It doesn't > need to be complicated, just a run through the basics of triaging and > then some Q&A for attendees. > > If you're not familiar with Ubuntu Classroom, see the project wiki > page, which includes links to past sessions: > https://wiki.ubuntu.com/Classroom > > Thanks! > > -- > Elizabeth Krumbach // Lyz // pleia2 > http://www.princessleia.com > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > From jeremy.foshee at canonical.com Tue Dec 7 14:24:31 2010 From: jeremy.foshee at canonical.com (Jeremy Foshee) Date: Tue, 7 Dec 2010 09:24:31 -0500 Subject: Reminder: Kernel Bug Day Today! Message-ID: <20101207142431.GA26168@nightcrawler> Folks, This is a gentle reminder that today is the Kernel Bug Day focusing on bugs that have patches attached. Our goal is to close out all of the old bugs and work through the bugs that are relevant from an SRU or development standpoint. One major aspect of this effort will be to correctly identify and remove the indicator on those bugs that do not have valid patches. I'll be available in #ubuntu-bugs and #ubuntu-kernel on the Freenode IRC server if there are any questions. :-) Thanks! ~JFo From dlbike76 at gmail.com Tue Dec 7 15:47:13 2010 From: dlbike76 at gmail.com (David C) Date: Tue, 7 Dec 2010 10:47:13 -0500 Subject: [Bug 669459] Ubuntu installation writes into foreign partitions and MBR without permission Message-ID: Could someone familiar with ubiquity look into this bug? https://bugs.launchpad.net/bugs/669459 Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy.foshee at canonical.com Tue Dec 7 16:01:31 2010 From: jeremy.foshee at canonical.com (Jeremy Foshee) Date: Tue, 7 Dec 2010 11:01:31 -0500 Subject: CORRECTION:Re: Reminder: Kernel Bug Day Today! In-Reply-To: <20101207142431.GA26168@nightcrawler> References: <20101207142431.GA26168@nightcrawler> Message-ID: <20101207160131.GB26168@nightcrawler> On Tue, Dec 07, 2010 at 09:24:31AM -0500, Jeremy Foshee wrote: > Folks, > This is a gentle reminder that today is the Kernel Bug Day focusing > on bugs that have patches attached. Our goal is to close out all of the > old bugs and work through the bugs that are relevant from an SRU or > development standpoint. One major aspect of this effort will be to > correctly identify and remove the indicator on those bugs that do not > have valid patches. > It seems I incorrectly identified this for bugs with patches (one of my work items for today) The correct focus should be the bugs tagged regression-update as identified in my previous e-mail on the subject as well as the bug day page on the wiki. Apologies for any confusion. :-) ~JFo > I'll be available in #ubuntu-bugs and #ubuntu-kernel on the Freenode IRC > server if there are any questions. :-) > > Thanks! > > ~JFo > From phillw at ubuntu.com Tue Dec 7 17:19:10 2010 From: phillw at ubuntu.com (Phill Whiteside) Date: Tue, 7 Dec 2010 17:19:10 +0000 Subject: Bug Day. Message-ID: Hiyas folks, whilst it is specifically for lubuntu bugs (hence it being held on #lubuntu), there is a hug a bug day on #lubuntu on 10th December. If anyone wants to attend and watch / take part, you're more than welcome to do so. Julien has the pots of strong coffee ordered as it is an all day session (European time). Regards, Phill. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kamusin at gmail.com Tue Dec 7 18:19:08 2010 From: kamusin at gmail.com (Kamus) Date: Tue, 7 Dec 2010 15:19:08 -0300 Subject: Announcing the Next Ubuntu Bug Day! December 9th 2010 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Compiz! * 100 New bugs need a hug * 33 Incomplete bugs need a status check * 100 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * December 9th 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20101209 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [from bugsquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From florenvanolden at gmail.com Mon Dec 6 20:32:53 2010 From: florenvanolden at gmail.com (Floren van Olden) Date: Mon, 06 Dec 2010 21:32:53 +0100 Subject: server USB installer cd-rom not detected Message-ID: <4CFD4875.5010001@gmail.com> Dear debuggers, Related Bug #234185Fixed One of the official installation methods of installing Ubuntu 10.10 server does not work. Tried on multiple different machines bug in both i386 and AMD64 versions. The kernel option 'cdrom-detect/try-usb=true' does not have desired effect. Yours sincerely, Floren -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Tue Dec 7 20:33:35 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 07 Dec 2010 20:33:35 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingGwibber=22_by_kamus?= Message-ID: <20101207203335.13017.58264@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by kamus: http://wiki.ubuntu.com/DebuggingGwibber?action=diff&rev1=2&rev2=3 ------------------------------------------------------------------------------ '''The Hotest''' || '''Bug''' || '''Subject''' || '''Symptom''' || || [[https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/614742|614742]] || Facebook problems || Problems related to Facebook authentication and stuffs || + || [[https://bugs.launchpad.net/gwibber/+bug/645512|645512]] || Twitter doesn't update || Twitter stop to update because you are following a 'special' user || From noreply at ubuntu.com Tue Dec 7 21:31:43 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 07 Dec 2010 21:31:43 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_brian-mur?= =?utf-8?q?ray?= Message-ID: <20101207213143.27661.7344@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=139&rev2=140 The comment on the change is: Adding in guidelines for converting a bug to a question ------------------------------------------------------------------------------ Only valid and well described bugs can be processed efficiently and swiftly by the developers. A small guide at [[Bugs/Improving]] helps with handing over a good bug to the developers when setting the status 'Triaged'. + == Converting a bug report to a question == + + Some bug reporters aren't actually reporting a bug but rather are looking for support with using Ubuntu. These bug reports should be converted to questions so that they will appear in the Launchpad answer tracker and can be answered there. Telling whether or not a bug report is actually a support is subjective but these guidelines may help you determine if it is a bug or a support request. + + 1. Is the reporter looking for help to accomplish a task? + * Installing printer drivers for a printer is a good example of this + + 1. Is the reporter missing a package to accomplish a task? + * Missing codecs to watch DVDs is a good example of this + + 1. Is the bug report in a foreign language? + + 1. Has the reporter misconfigured their system? + * Mangled lines in {{{/etc/apt/sources.list}}} + == Invalidating == Sometimes, you will have to invalidate a bug report. This may be because the problem is not reproducible, or the program was designed to behave a certain way. From nightnaiad at gmail.com Wed Dec 8 01:20:12 2010 From: nightnaiad at gmail.com (Calla) Date: Tue, 7 Dec 2010 17:20:12 -0800 Subject: Unsubscribed Message-ID: I have tried and tried to unsubscribe, but the emails just keep coming. Please remove me fromt eh mailing lisrt! -------------- next part -------------- An HTML attachment was scrubbed... URL: From yofel at gmx.net Wed Dec 8 01:55:01 2010 From: yofel at gmx.net (Philip Muskovac) Date: Wed, 08 Dec 2010 02:55:01 +0100 Subject: Unsubscribed In-Reply-To: References: Message-ID: <4CFEE575.1060305@gmx.net> On 12/08/2010 02:20 AM, Calla wrote: > I have tried and tried to unsubscribe, but the emails just keep coming. > Please remove me fromt eh mailing lisrt! > As David said, go to https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad At the bottom it says "To unsubscribe from Ubuntu-bugsquad, get a password reminder, or change your subscription options enter your subscription email address: " Then there's a button to unsubscribe or edit your options. Follow the instructions from there. Philip From lyz at ubuntu.com Wed Dec 8 02:01:43 2010 From: lyz at ubuntu.com (Elizabeth Krumbach) Date: Tue, 7 Dec 2010 18:01:43 -0800 Subject: Triaging session for #ubuntu-classroom? In-Reply-To: References: Message-ID: On Tue, Dec 7, 2010 at 6:17 AM, ilidrissiamine at gmail.com wrote: > I'm available every day from 17:00UTC to 18:00 UTC, if you would like > me to do this session :) Great! Can you do this upcoming Tuesday, December 14th at 17:00 UTC? -- Elizabeth Krumbach // Lyz // pleia2 http://www.princessleia.com From brian at ubuntu.com Wed Dec 8 03:53:22 2010 From: brian at ubuntu.com (Brian Murray) Date: Tue, 7 Dec 2010 19:53:22 -0800 Subject: Unsubscribed In-Reply-To: <4CFEE575.1060305@gmx.net> References: <4CFEE575.1060305@gmx.net> Message-ID: <20101208035322.GV7786@murraytwins.com> On Wed, Dec 08, 2010 at 02:55:01AM +0100, Philip Muskovac wrote: > On 12/08/2010 02:20 AM, Calla wrote: > > I have tried and tried to unsubscribe, but the emails just keep coming. > > Please remove me fromt eh mailing lisrt! > > > > As David said, go to > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > At the bottom it says > "To unsubscribe from Ubuntu-bugsquad, get a password reminder, or change > your subscription options enter your subscription email address: " > Then there's a button to unsubscribe or edit your options. Follow the > instructions from there. I used my mailing list superpowers and took care of this. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From ilidrissiamine at gmail.com Wed Dec 8 14:53:31 2010 From: ilidrissiamine at gmail.com (ilidrissiamine at gmail.com) Date: Wed, 8 Dec 2010 14:53:31 +0000 Subject: Triaging session for #ubuntu-classroom? In-Reply-To: References: Message-ID: Excellent, let's do it! Thanks for replying, Mohamed Amine IL Idrissi (btw, not ccing classroom-management anymore since it bounces back. sorry :( ) On Wed, Dec 8, 2010 at 2:01 AM, Elizabeth Krumbach wrote: > On Tue, Dec 7, 2010 at 6:17 AM, ilidrissiamine at gmail.com > wrote: >> I'm available every day from 17:00UTC to 18:00 UTC, if you would like >> me to do this session :) > > Great! Can you do this upcoming Tuesday, December 14th at 17:00 UTC? > > -- > Elizabeth Krumbach // Lyz // pleia2 > http://www.princessleia.com > From lyz at ubuntu.com Wed Dec 8 17:58:49 2010 From: lyz at ubuntu.com (Elizabeth Krumbach) Date: Wed, 8 Dec 2010 09:58:49 -0800 Subject: Triaging session for #ubuntu-classroom? In-Reply-To: References: Message-ID: On Wed, Dec 8, 2010 at 6:53 AM, ilidrissiamine at gmail.com wrote: > Excellent, let's do it! Added to the calendar! I'll follow up with instructor instructions off-list/on IRC. > (btw, not ccing classroom-management anymore since it bounces back. sorry :( ) No problem, it's moderated to non-subscribers so I let your last post through manually. -- Elizabeth Krumbach // Lyz // pleia2 http://www.princessleia.com From webmaster at ubuntu.com Wed Dec 8 17:48:00 2010 From: webmaster at ubuntu.com (=?utf-8?q?Help_Ubuntu_?=) Date: Wed, 08 Dec 2010 17:48:00 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_brian-murray?= Message-ID: <20101208174800.23952.84625@acerola.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The following page has been changed by brian-murray: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=154&rev2=155 The comment on the change is: Modify support request section ------------------------------------------------------------------------------ You should not file a bug if you are: * '''Requesting new software:''' you should follow the guidelines at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages - * '''Requesting support:''' there are a multitude of ways you can get support, such as the [[https://answers.launchpad.net/ubuntu|Launchpad answer tracker]], the [[http://www.ubuntuforums.org/|Ubuntu forums]], the [[irc://irc.freenode.net/#ubuntu|#ubuntu]] channel on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server, the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-users|ubuntu-users]] mailing list, and the [[http://ubuntu.stackexchange.com|Ubuntu Stack Exchange]] site. + * '''Requesting support:''' there are a multitude of ways you can get help using Ubuntu, such as the [[https://answers.launchpad.net/ubuntu|Launchpad answer tracker]], the [[http://ubuntu.stackexchange.com|Ask Ubuntu]] site, the [[http://www.ubuntuforums.org/|Ubuntu forums]], the [[irc://irc.freenode.net/#ubuntu|#ubuntu]] channel on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server, and the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-users|ubuntu-users]] mailing list. * '''Discussing features and existing policy:''' this belongs to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. * '''Proposing features and ideas:''' you should submit your idea to [[http://brainstorm.ubuntu.com/|Ubuntu Brainstorm]] or to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. * '''Filing a bug against a program not provided by an Ubuntu package:''' You should file a bug in that program's bug tracking interface. Instructions are generally available on the program's web site. From noreply at ubuntu.com Wed Dec 8 22:53:42 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 08 Dec 2010 22:53:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_bryc?= =?utf-8?q?e?= Message-ID: <20101208225342.23118.4940@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by bryce: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=111&rev2=112 ------------------------------------------------------------------------------ === Graphical Environment === - The Ubuntu graphical environment is provided by the X Window System, also known just as "X". If you have any of the following symptoms, the issue is with X and the package to report against is `xorg`: (See [[X/Troubleshooting]] if you want to pin-point the problem.) + The Ubuntu graphical environment is provided by a combination of the Linux kernel and the X Window System (aka X.org). + + The following symptoms typically are due to GPU issues in the kernel DRM driver: * Blank or solid-colored screen instead of login screen, or immediately after login + * System freezes completely - * Wrong screen resolution + * Wrong default screen resolution - * System freezes completely (but not with a blinking CAPS lock light) + + If you have any of the following symptoms, the issue is with X and the package to report against is `xorg`: (See [[X/Troubleshooting]] if you want to pin-point the problem.) + + * The graphical session terminates and returns to the login screen * Fonts extremely big or small If your problem is with the actual desktop (for example, with desktop icons): From noreply at ubuntu.com Tue Dec 14 18:51:23 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 14 Dec 2010 18:51:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/Meeting/Minutes=22_by_h?= =?utf-8?q?ggdh2?= Message-ID: <20101214185123.17124.49101@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by hggdh2: http://wiki.ubuntu.com/BugSquad/Meeting/Minutes?action=diff&rev1=10&rev2=11 ------------------------------------------------------------------------------ <> == 2010 == + * [[BugSquad/Meeting/Minutes/2010-12-14]] * [[http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-10-12-16.57.moin.txt|2010-10-12]] <--- Started using meetingology a meeting bot. * [[BugSquad/Meeting/Minutes/2010-01-19]] From noreply at ubuntu.com Tue Dec 14 19:14:32 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 14 Dec 2010 19:14:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/Meeting/Minutes/2010-12?= =?utf-8?q?-14=22_by_hggdh2?= Message-ID: <20101214191432.24676.42679@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by hggdh2: http://wiki.ubuntu.com/BugSquad/Meeting/Minutes/2010-12-14?action=diff&rev1=5&rev2=6 ------------------------------------------------------------------------------ ## Only topics discussed during the meetings should be put in the minutes. ## Status reporting is done via another channel. - ==== Proper place to file translation bugs in packages ==== + ==== Mentorship Updates ==== - The bugsquad and the translations team discussed the current approach on handling translation bugs and ways to optimize it. + Not much here, most of the mentors were not present. hggdh will add more mentees to the alpha team. - This general approach and its background are described on the [[Translations/KnowledgeBase/HandlingBugs#Background|page on handling Ubuntu Translations bugs]], and to summarize translation bugs are reported against the [[https://launchpad.net/ubuntu-translations|Ubuntu Translations project in Launchpad]], with the [[UbuntuTranslationsCoordinators|Ubuntu Translations Coordinators]] team acting as the bug supervisor. + ==== BugSquad wiki pages update ==== - The main points of discussion were the duplication of work in having a task for the ubuntu package and the ubuntu-translations project, and the difficulty in the bugsquad and UTC teams to collaborate in setting the status of the bugs for the tasks, i.e. the lack of permissions for both teams involved. + nigelb will keep on on the header consolidation. Carrying over. + ===== Split of HowToTriage into basic and advanced pages ===== - * It was agreed that given the low number of translations bugs, having a separate, additional task for ubuntu-translations would not be a problem for the Bugsquad. - * It was agreed that the Bugsquad would be added as a Bug Supervisor for the Ubuntu Translations project (`ubuntu-translations`) in a way that does not affect the permissions of any of the teams (`ubuntu-translations-coordinators`, `ubuntu-bugcontrol`) - * It was also agreed that an ubuntu-translations task should be opern for all translation bugs straight away, without the need to wait until they've been marked as triaged. The reason being that the ubuntu-translationa project was mostly meant for keeping track of all translation bugs, what would you say. Furthermore, translation bugs are easily identifyable, i.e. when one is spotted it is generally quite obvious that it is a translations-related bug, so it makes sense to file it against ubuntu-translations directly. - * `qense` will document the translations bug workflow on [[Bugs/HowtoTriage]] - * `dpm` will create a new team `ubuntu-translations-bugsupervisors`, add `ubuntu-translations-coordinators` and `ubuntu-bugcontrol` as members and set this new team as the Bug Supervisor for `ubuntu-translations` - ===== Use of bug tags for translation bugs ===== + devildante is working on this, but was MIA this meeting. Will carry over. - `dpm` asked for some advice and feedback on the usage of tags for translations-related bugs, as documented on the [[Translations/KnowledgeBase/HandlingBugs#Tagging|page on handling Ubuntu Translations bugs]]. Some pieces of advice from the Bugsquad: + ==== Gnome3 bug handling ==== + Gnome3 is being currently published on the Desktop PPA. The desktop team would like to tag Gnome3 bugs, in order to allow to separate them from the in-progress work for Natty. As of now it is unknown if we will be able to provide Gnome3 on Natty (so the PPA). It has not yet been decided how to deal with Gnome3 bugs generically. We agreed that: - * Tagging is still very much ad hoc. It might help for to prefix the translation tags with -- say -- 'tr', or 'trans' -- so that there will be less chance of conflicts - * The translations team could look into getting some of their tags listed as [[http://blog.launchpad.net/cool-new-stuff/official-bug-tags|official]], adding them to [[Bugs/Tags]] and sending an email to bugsquad/control explaining why they are being added there - ==== Additional topics ==== + * we will add 'gnome3' as an official tag; ''only''bugs relating to Gnome3 will be so tagged; + * we will add a comment on the tag stating that these are (right now) PPA bugs, and should not be touched by the triager community at-large (developers/maintainers will deal with them, until a clear course of action is defined); + * to allow easier/immediate identification, the bug title should start with '[GNOME3]'. - It was agreed to discuss the rest of the topics on the next meeting: + An additional note: since these packages come from a PPA, there will be no automatic apport triggering. The only way is to manually enter the bug. + bdmurray will add the tag to the official list. - * What to do with obsolete packages regarding bugs in Ubuntu -- micahg - * Mention of #ubuntu-bugs for Triage in LP -- micahg - * Open Discussions - Additional topics Proposed: + ==== Open Discussion ==== - * Defining a Roadmap for the BugSquad -- qense - * Pollution caused by pending release nominations -- hggdh2 - * Going through release nominations (more accessible [[https://bugs.launchpad.net/ubuntu/hardy/+nominations?field.searchtext=&orderby=date_last_updated&search=Search&field.status:list=FIXCOMMITTED&field.status:list=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=|search]], creation of "Hardy driver" LP group with privs to reject tasks) -- Laibsch (please invite me to the discussion, I should be online) - * Backporting of newest apport (if possible) to all stable releases (in concept) -- micahg + * charlie-tca reminded the team that a launchpad bug jam is currently in progress, and help is appreciated ([[https://dev.launchpad.net/BugJam|launchpad bugJam]]. + + ==== next chair ==== + + hggdh was self-elected (I forgot to ask for a next chair...) == Log == {{{ + [16:58] hi, will the bugsquad meeting be now here? + [17:00] i think so , it says 1700 UTC + [17:01] great, thanks pedro_ + [17:01] hggdh, are you chairing the meeting? the wiki says so :-P + [17:12] anyone here? + [17:12] c2tarun: we're searching for hggdh + [17:12] ok :) - [16:00] bdmurray, micahg, pedro_, adiroiban, and others: meeting! - [16:00] Yeah, saw that. I've been a huge fan (and user, and debugger) of Firefox since it was born as Phoenix - [16:01] hi - [16:02] As usual, I'll contribute what and when I can, but I can't get too distracted. - [16:02] the agenda is at , for those interested but unaware of the agenda - [16:02] ah, forgot one, ping: hggdh - [16:02] hi all - [16:02] Moin! - [16:02] hello - [16:02] pong - [16:03] * micahg thinks translation bugs should be top priority - [16:03] yep - [16:04] for this meeting at least ;) - [16:04] dpm, maybe you could start with a quick explanation of the way Translations uses LP now, for those who haven't followed the maillist discussion? - [16:04] qense, sure - [16:06] here is some background (https://wiki.ubuntu.com/Translations/KnowledgeBase/HandlingBugs). Basically, the way the translations team handles bugs is: - [16:06] we've got a LP project - [16:06] called ubuntu-translations - [16:06] the idea is to report all translations-related bugs there - [16:07] the UTC (ubuntu-translations-coordinators) is set as the project driver - [16:07] dpm: what about the tasks for the ubuntu package/ - [16:07] and takes care of triaging and fixing - [16:07] should they be marked as triaged pending action from the translators team? - [16:07] dpm: reported ubuntu-translations even if the translation for that app is handled upstream? - [16:08] micahg, that's what i've been doing so far - [16:09] pedro_: me too, but I want to verify if that's the process we want to keep - [16:09] btw the ubuntu-translators team is *pretty* fast to solve issues there - [16:09] micahg, it sounds good to me if it sounds good to the bugsquad - [16:09] :) - [16:09] Currently we have mostly two tasks: one for the source pacakge -- often filed by a user via the ubuntu LP project -- and one for the ubuntu-translations project. Most bugs are handled pretty fast by teh translators. However, they can't use all statuses for the source package task. - [16:10] the problem we had on the last hugday was that the bugsquad could not set "our" bugs as confirmed - [16:10] and what qsense is pointing out ^ - [16:10] On top of that the two different tasks cause extra work and mail noise. - [16:10] hmm, confirmed should be allowed on any project that's public - [16:11] triaged can't be set - [16:11] the only thing I am not sure about (not even if it is needed) is that -- by assigning the bug to ubuntu-translators we lose track of the real affected package - [16:11] hggdh: that's why we mark the ubuntu task as triaged - [16:11] micahg, sorry for the confusion. yeah, triaged - [16:11] The Translators did say to prefer a separate ubuntu-translations project so they can keep track of all translation bugs. - [16:11] hggdg: there are two tasks iirc - [16:11] oh + [17:13] oh + [17:13] sorry, busy + [17:13] so... + [17:13] #startmeeting + [17:13] hellooooo + [17:13] hi there! + [17:13] 8 + [17:13] where's the bot? + [17:13] hi there :) + [17:13] busy too .. :P + [17:14] mistook the 1 in the date for a 2 and went on vacation too early + [17:14] OK. The meeting is officially started (late, though, sorry). The bot does not seem to be here + [17:15] first, on the actions from the previous meetings + [17:15] er. This does not seem to be correct, but there I go: + [17:16] 1. Bug Day to be created for regression-potential tags + [17:16] did we not already discuss this? + [17:16] i think we already did that, yes + [17:17] heh. So the agenda is out-of-date... at least for the "previous meetings" + [17:17] so let's jump over to Mentorship programme update + [17:17] it was ran on 2010 10 21 + [17:18] * charlie-tca waves + [17:18] mentors -- please update on status + [17:19] from my side: ojap is slowly going on + [17:20] pedro_, vish, charlie-tca, yofel, & co: any updates on mentorship - [16:11] * hggdh is slow as usual - [16:12] and I beg all pardon - [16:12] I agree that the extra bug task is a downside, but is it that much of a problem given the number of translation bugs? - [16:12] pardon granted - [16:13] dpm: one task isn't much of a problem - [16:13] it's the same as upstreaming - [16:13] It is not much of a problem to me, but I could imagine that when you handle a lot of bugs it could cause you extra time. What seems to be the biggest problem here is the lack of permissions for both teams involved. - [16:13] mrand, if the translation is handled upstream, we tend to point the reporters to upstream and close the ubuntu-translations task as invalid - [16:13] I assume the permissions could be fixed - [16:13] qense: I don't think that we should have triage permissions for the translators team - [16:14] dpm: cool. thanks. - [16:14] ok, so we seem to agree that additional tasks in this particular case is not much of an issue - [16:14] and that the issue is permissions - [16:14] the whole point of triage permissions is to verify that a real issue exists - [16:14] the translators team would know best where that effort should be - [16:15] Now there are two people with permissions necessary to properly mark one translation bug. - [16:15] hence, we can confim the issue, and if they can fix it mark triaged and take the appropriate action - [16:15] qense: adding translators team to bug control might be an option - [16:16] So first 'Confirmed', then a ubuntu-translations tasks and when they're done a 'Triaged' to the ubuntu task - [16:16] ? - [16:16] but I don't think it makes sense the other way - [16:16] or add bug control to ubuntu-translations project :) - [16:16] or leave it as it is right now ;) - [16:16] :) - [16:17] btw, there is not explanation for this type of bug on Bugs/HowToTriage, shall I add one after this meeting? - [16:17] qense, sounds great to me :) - [16:17] qense: I thought that was the point of the meeting agenda item, to nail down the specifics - [16:17] because that's (part of) the main problem, I feel, the process isn't/wasn't well-known by the traigers. - [16:18] yes, the specifics - [16:18] is there a specific translators team for bug handling? - [16:18] qense, we can then even remove the HandlingBugs page on the Translations wiki and point folks to the Bugs/HowToTriage one - [16:18] hmm,maybe it does make sense to have bug control set triaged on the translators bugs - [16:18] qense, ubuntu-translations-coordinators - [16:18] triaged in ubuntu mean ready for dev to look at - [16:19] dpm: I wouldn't remvoe that page completely, but instead point to it from the HowTotTiage page - [16:19] qense, ok, sounds good - [16:19] the translators are the devs here, so technically they shouldn't have to do anything with the Ubuntu task - [16:20] qense: ok, so maybe my initial proposal was wrong... - [16:20] however, that would be a bit inefficient, so maybe adding the translators team to the bugcontrol, or a bug handling subset of the translators team, would be indeed the best solution - [16:20] I agree - [16:20] qense: I think adiroiban had the better proposal - [16:21] I also think adding bug control to ubuntu-translations might be a good idea - [16:21] then the triager in Ubuntu can set the translations task as triaged which tells them they need to look at it - [16:21] That would make sense. people join the bugsquad to triage bugs and they join the translation team to translate, not to triage other bugs - [16:21] Maybe we could have some kind of Adopt-a(n)-Upstream/Package subgroup later on that focuses on translation bugs? - [16:21] dpm +1 - [16:22] qense: I think that will divide our efforts further - [16:22] ok, it was just something that came up in my mind - [16:23] qense: maybe one day when we have better coverage - [16:23] so we agree that the Ubuntu Bug Control team shouold get bug permissions for the ubuntu-translations project? - [16:23] +1 - [16:24] +1 - [16:24] +1 from me too - [16:24] feels weird having a meeting w/out bdmurray - [16:24] +1 if we write down something about the process in our wiki - [16:25] I'll add a section to Bugs/HowToTriage, would that be sufficient? - [16:25] YES, great - [16:25] btw, who will write down the minutes of this meeting? - [16:25] qense, I'll subscribe to that page in order to add a link to it on the Translations/HandlingBugs page when finished - [16:26] bug 509376, I really don't think this should have been Invalidated, it is clearly a bug if jockey is blacklisting the nvidia driver!! - [16:26] Launchpad bug 509376 in jockey "[lucid] nvidia-current failed to initialise" [Undecided,Invalid] https://launchpad.net/bugs/509376 - [16:26] dpm: okay - [16:26] if no one else volunteers, I can take care of the minutes - [16:27] re: the adopt-apackage/upstream proposal, I think for now what we can do is to simply use the ubuntu-translations project as a target for regular hugdays like the one some weeks ago - [16:28] okay, that means this topic is done now? - [16:28] just one sec - [16:29] the translations team is still learning on bug triaging, etc and I've got one quick question: - [16:29] We discussed the use of tags for translation bugs in the past - [16:29] We've made a list here: https://wiki.ubuntu.com/Translations/KnowledgeBase/HandlingBugs#Tagging - [16:29] Do you guys havve got any feedback, tips, advice on bug tagging? - [16:30] xteejx: it could have to do with the transition to the new proprietary nvidia drivers packaging layout, in that case users upgrading in a later stage wouldn't suffer from this bug and Invalid would be the right state. - [16:31] qense: Ahh ok, thanks for clearing that up :) - [16:32] tagging is still very much ad hoc. It might help for you to prefix the translation tags with -- say -- 'tr', or 'trans' -- so that there will be less chance of conflicts - [16:32] dpm: are you aware of the difference between official and unofficial tags? I'm not sure how tags behave when the bug has tasks for multiple projects, though/ - [16:32] qense, I've heard about them, but I'm not too clear on the distiction right now - [16:33] Official tasks get listed on the bugs overview page - [16:33] although in the past there has been discussions on making the i18n or l10n tags official to give more relevance to translations-related bugs - [16:34] You could use tags to help the different i10n teams - [16:34] some tags are used "everywhere" -- like the regression* ones; these are the official ones. Others are specific to a project/usage, and completely out of control - [16:35] how can we "apply" for translation-related tags to be made official for the ubuntu project? - [16:35] (when relevant) - [16:36] not sure, bug control administrators maybe? - [16:36] I'll look into it, then, thanks - [16:37] pretty much by adding your tags to the https://wiki.ubuntu.com/Bugs/Tags page (since you are dealing with bugs also) - [16:37] thanks a lot for the advice and the feedback - [16:37] and sending out an email to bugsquad/control explaining why you are adding them there - [16:38] ok, thanks - [16:38] otherwise, I think that's all from my part on translations, unless adiroiban or ArneGoetje have something else to add - [16:38] hggdh: does the ubuntu bug project admin have to mark them in LP in any wya? - [16:39] micahg: to my knowledge, no -- tags are still ad hoc. But I do not know the internals of LP/Malone - [16:40] hggdh: iirc there is a list of official tags on bugs.launchpad.net/{project} - [16:42] was that a split? - === Pici` is now known as Pici - [16:43] yeah - [16:44] qense: I am not sure these are real official tags, or tags found in bugs. For example, Evolution lists a 'junk' tag... - [16:45] hggdh: found it! http://blog.launchpad.net/cool-new-stuff/official-bug-tags - [16:46] cool, qense, thank you - [16:46] ah, great, thanks - [16:48] one question: should people open a ubuntu-translations task for all translation bugs, or only after they've been marked as triaged? - [16:49] I'd go for right away since the u-trans project was mostly meant for keeping track of all translation bgs, what would you say? - [16:50] qense, yes, I think so. Furthermore, translation bugs are easily identifyable. What I mean is that when you spot one it is generally quite obvious that it is a translations-related bug - [16:50] so it makes sense to file it against u-t straight away - [16:51] yes - [16:57] It's now almost 17.00 UTC. What shall we do with the points that weren't discussed. Micahg, you added most of them, what do you think? - [16:57] heh, wait till next month :) - [16:57] translations was the big ting - [16:57] thing - [16:57] yeah, the meeting was quite productive from my pov anyway - [16:57] very - [16:58] good - [16:58] so, dpm if you can add ubuntu-bugcontrol as a member of the translations-coordinators team, that allow us to set the triaged status - [16:58] dpm, if you or someone else from your team has got any questions about the bug triaging process, please feel free to mail the bugsquad maillist or come to this IRC channel - [16:59] dpm: maybe setting us as bug supervisor would be enough? idk if that would remove your teams abilities though - [16:59] You could make a separate Ubuntu Translations Bug Supervisor team and make both teams a member of it, - [17:00] That way you wouldn't give away permissions to both teams - [17:00] that works too - [17:00] micahg, I'll have to look into that, since adding bugcontrol to the team might not be an option (otherwise everyone can modify LP translation templates) - qsense's suggestion seems like the best option to me - [17:01] dpm: k - [17:01] dpm: the translation team -- is it a restricted tem? - [17:01] team + [17:20] ? - [17:01] yep - [17:01] so why not just add it to bug-control? - [17:01] * micahg checked earlier + [17:20] * yofel isn't a mentor + [17:20] as in now , i don't have any student + [17:20] I am going to have the logo images broken down for us + [17:20] * hggdh considers yofel *should* be one ;-) + [17:20] I have no mentees + [17:20] yeah yofel, definitely ;-) + [17:20] +1 for yofel to have at least oen + [17:21] * charlie-tca should hide now + [17:21] oen? + [17:21] heh + [17:21] * yofel hides and put's on an invisibility cape before anything more happens.. + [17:21] s/oen/one ? :-) + [17:21] :P + [17:21] dyslexia, please pardon me + [17:21] See, I knew you would know what I meant + [17:22] what I see: mentorship is still slow + [17:22] * charlie-tca trying to use three keyboards and two mice at once again + [17:22] mentees propose themselves, but do not really devote time + [17:22] Have we added people to group A yet? + [17:23] we have two there, yes + [17:23] did the beginners team cooperation result in anything yet btw.? + [17:23] Can't we add a few more to the team? + [17:24] yes, we should + [17:24] [ACTION] I will look at the pending list and add some more + [17:24] next + [17:24] nigelb to edit bugsquad headers to be similar or link to each other appropriately + [17:24] yofel, as far as i know there's no much input on that + [17:25] nigelb: how has that gone? + [17:25] In fact I have a question about mentees, Should I have done some contributions before asking for a mentor or anyone can ask without any previous contribution? + [17:25] hggdh: I delayed it waiting for wiki update. NOw that the update has hit, I'll get on it. + [17:25] ElPasmo: ask anytime you desire a mentor. Experience is not needed first + [17:25] ElPasmo: anyone can ask, as long as the pre-requisites are fulfilled + [17:25] ElPasmo, anyone can ask for it + [17:25] thanks :) + [17:25] heh + [17:25] charlie-tca: check into synergy for the multiple mouse and keyboards + [17:26] why i didn't say : no! ? + [17:26] [ACTION] nigelb to keep on with update of bug page headers + [17:26] mrand: on different computers with three monitors? + [17:26] charlie-tca: yes + [17:26] okay + [17:26] thanks + [17:26] next: devildante to split HowToTriage page up into a simple page and an advanced page + [17:27] devildante is MIA today. Anybody knows how this is progressing? + [17:27] i know he was working on it, but don't know the real progress as in today + [17:27] we can ask him on the ML though + [17:27] yes + [17:28] [ACTION] check with devildante about the split on basic/advanced HowToTriage + [17:28] and before I forget + [17:29] [ACTION] find out what happened with the meetingcology bot + [17:29] indeed + [17:29] now + [17:29] GNOME3 bug handling -- micahg + [17:29] micahg: please take over + [17:30] heh. micahg seems to be here only physically, mind elsewhere + [17:31] so + [17:31] Open Discussions. + [17:31] ok, sorry + [17:31] micahg: please go on + [17:31] :-) + [17:31] micahg: I did the same just a few ago + [17:32] so, the desktop team would like a way to tag bugs for the GNOME3 transition, most of it won't happy until natty+1, but they would like to be able to track bugs against their GNOME3 staging PPA + [17:32] I wanted to propose a GNOME3 tag to be official at least for the next 2 cycles, how does everyone feel about that + [17:33] only one tag? + [17:33] do we need more? + [17:33] what for you'd need more? + [17:33] IDK, I am not familiar with the desktop effort on Gnome3 + [17:34] there is nothing specific there + [17:34] a gnome3 tag works for me + [17:34] rather than landing the usual GNOME updates to natty we use a ppa + [17:34] we might decide to move the ppa to natty if it's ready + [17:34] otherwise it will land in natty+1 + [17:34] it's just that we are not confident yet that GNOME3 will be ready for natty + [17:35] OK. So bugs on the Gnome3 PPA are valid Ubuntu bugs -- folks, please do not forget this + [17:35] well, they are valid but not targetting natty so far + [17:35] so the same settings might not apply + [17:35] they should not show on the r-t list + [17:36] or the rc bugs listing + [17:36] seb128: the warning was mostly due to the fact that PPA-based bugs usually are not accepted + [17:36] seb128: so no targeting/milestoning these bugs, correct? + [17:36] yeah, I'm still not sure we want to accept bugs about upstream issues + [17:36] we do want bugs about distribution integrations issues though + [17:37] or patches to updates + [17:37] seb128: can't you have your own project for that bugs like kubuntu-ppa does? + [17:37] seems suboptimal + [17:37] you'll need an apport hook anyway since they're ppa packages + [17:37] there is that, yes + [17:38] not sure we want apport bugs + [17:38] and if you add a hook, then you can make to hook add the gnome3 tag + [17:38] s/to/the/ + [17:39] seb128: it sounds to me that you expect most of these bugs to be opened by developers or "official" testers, is this correct? + [17:39] i.e. manually opening them + [17:39] w/22 + [17:39] sorry. + [17:40] hggdh, well micahg raised the topic + [17:40] I didn't think about it yet + [17:40] but we don't want to be spammed with upstream bugs + [17:40] hello to all, does we have a 2.6.37 kernel-pae ? + [17:40] we just want to know about integration issues + [17:40] njin: please wait a bit, in the middle of a meeting + [17:41] hggdh: I would think mostly yes, but some things like gnome-shell will only be in the PPA unless GNOME3 lands, so we might get some users as well + [17:41] OK. Would it be fair to say, then, that we are adding the gnome3 tag, and details on how to deal with the _triaging_ will be ironed out later? + [17:41] If we at least get them tagged for gnome3, the ones that are not ours, someone who knows the package could delete, couldn't they? + [17:42] sounds plausible, charlie-tca. But I worry about triagers doing the Wrong Thing + [17:43] hggdh, well we can start by adding the tag and see how it goes + [17:43] I'm wondering if we want the topic to reflect that as well + [17:43] ups + [17:43] topic -> title + [17:44] so those bugs are spotted easily from a bug list + [17:44] micahg, seb128: how about adding the tag to the official list, and adding a note on the HowToTriage asking to leave these bugs alone right now? + [17:44] If the tag is added to the tags page, it can explain what is happening with it + [17:44] hggdh, works for me + [17:45] wfm, too + [17:45] we can tweak later when required + [17:45] and, of course, there will be hundreds of bugs we get questions about :-) + [17:45] or if required + [17:45] seb128: a [GNOME3] in the title would make is immediately visible + [17:45] yes + [17:45] I like that + [17:45] yes + [17:46] and, since right now they would have to be entered manually (no apport hook), this limits the number of probable OPs + [17:46] these pretty much know what to do + [17:46] How will update the tag list? + [17:47] /How/who/ + [17:47] I will + [17:48] [ACTION] bdmurray to add 'gnome3' as an official (temporary) tag, with a comment to leave these bugs alone for now + [17:48] anything else on GNOME3? + [17:48] thanks hggdh, bdmurray, seb128 + [17:49] OK + [17:49] Open Discussion + [17:49] anyone would like to share/comment/ask anything related to triaging? + [17:50] + [17:50] o/ + [17:50] charlie-tca: please go ahead + [17:50] Launchpad is having a 2010BugJam + [17:50] They would like to close 6500 bugs + [17:50] oooohhhh + [17:50] OOOOHHHH + [17:50] when? + [17:50] https://dev.launchpad.net/BugJam + [17:50] now + [17:51] 13th-24th December 2010 + [17:51] charlie-tca: I believe those are launchpad project bugs :) + [17:51] Is tomorrow a class at #ubuntu-classroom about Basic Triaging at 17:00 UTC? + [17:51] Does that mean we can't help? + [17:52] but important to us also ;-) + [17:52] charlie-tca: no, it only means it's tangentially related ;) + [17:52] ElPasmo: I think yes + [17:52] * micahg thought it was today + [17:52] I thought the class was today? + [17:52] charlie-tca: on the 15th + [17:52] well, calendar says tomorrow, but I thought it was today + [17:53] Isn't that where devildante is today? + [17:53] Yeah, I think the wrong date was entered + [17:53] oh no... I've missed it :( + [17:53] classroom is dead silent though + [17:54] yes, nothing happening there + [17:54] and, on the Fridge calendar, it is scheduled for tomorrow + [17:55] so... + [17:55] ElPasmo: it is indeed tomorrow, I guess ;-) + [17:55] Well, and excuse my ignorance, but I suppose that the mentoring processs you talked before is the motu mentoring process? + [17:55] Thanks hggdh + [17:55] ElPasmo: no, not at all + [17:56] we deal with *triaging*, not with packaging/development + [17:56] although a lot of us also do that + [17:56] I see, Are they incompatible? + [17:56] not incompatible, just two completely different things + [17:57] MOTUs also do triaging + [17:57] but not necessarily triagers do packaging/developing + [17:57] Can you point me a link with the bugsquad mentoring? + [17:57] ElPasmo: https://wiki.ubuntu.com/BugSquad/Mentors + [17:57] thanks :) + [17:58] any other questions? + [17:59] given the silence... + [17:59] #endmeeting + [17:59] and yes, I know the bot is not there ;-) + [17:59] uffff + [17:59] sorry for the delay again, folks }}} From noreply at ubuntu.com Tue Dec 14 19:15:33 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 14 Dec 2010 19:15:33 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/Meeting/Minutes/2010-12?= =?utf-8?q?-14=22_by_hggdh2?= Message-ID: <20101214191533.24679.77334@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by hggdh2: http://wiki.ubuntu.com/BugSquad/Meeting/Minutes/2010-12-14?action=diff&rev1=6&rev2=7 ------------------------------------------------------------------------------ ## page was copied from BugSquad/Meeting/Minutes/2010-01-19 <> - - == Agenda == - - Topics discussed at this meeting: - - * Proper place to file translation bugs in packages -- micahg - o https://wiki.ubuntu.com/Translations/KnowledgeBase/HandlingBugs == Minutes == From kamusin at gmail.com Wed Dec 15 13:32:53 2010 From: kamusin at gmail.com (Kamus) Date: Wed, 15 Dec 2010 10:32:53 -0300 Subject: Announcing the Next Ubuntu Bug Day! December 16th 2010 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* software-center! * 100 New bugs need a hug * 69 Incomplete bugs need a status check * 100 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * December 16th 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20101216 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [from bugsquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From brian at ubuntu.com Thu Dec 16 21:42:51 2010 From: brian at ubuntu.com (Brian Murray) Date: Thu, 16 Dec 2010 13:42:51 -0800 Subject: Bugs not reported in English Message-ID: <20101216214251.GB7960@murraytwins.com> A bit ago[1] there was a discussion regarding how to handle bug reports in a foreign, non-English, language. This was discussed in some detail at UDS for Natty and it was decided that the best way to currently deal with these bug reports is to convert them into a question in Launchpad. Converting them to a question allows us to keep the information in the bug report and specify the language that the question / bug is written in. The steps for doing this follow: 1) Click "Convert to a question" 2) Add a comment regarding the bug not being reported in English 3) Click "Convert this Bug into a Question" 4) Click the link to the newly created question on the bug report 5) Under Question information click the edit icon next to English 6) Choose the right language (hopefully a word or two looks familiar!) To make this process easier I'm looking at being able to set the language in the convert to question page. (Step 2) [1] https://lists.ubuntu.com/archives/ubuntu-bugsquad/2010-October/002767.html -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Sat Dec 18 20:58:54 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 18 Dec 2010 20:58:54 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20101218205854.11133.36942@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=22&rev2=23 The comment on the change is: restructured 'In case your Touchpad doesn't work at all (No response from the Touchpad)' ------------------------------------------------------------------------------ 1. Manufacturer of the Touchpad. 1. When the symptom first appeared. - Sample Description - 'ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Sony Vaio VPCCW16FG' after the kernel upgrade. + Sample Description - ''''ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Sony Vaio VPCCW16FG' after the kernel upgrade.''' However if you think that the bug is a general one with the type of the Touchpad and is irrespective of the Laptop model you could omit mentioning the Laptop model in the description. But only consider doing this, when you are very sure that the bug is affecting all laptops with that Touchpad model. == In case your Touchpad doesn't work at all (No response from the Touchpad) == - This is generally a case of kernel('''linux''') or '''xorg''' bug. Check by connecting a mouse that if it works or not. If no, then you should file the bug against '''HAL''' and follow the steps below. + This is generally a case of kernel('''linux''') or '''xorg''' bug. Check by connecting a mouse that if it works or not. + *If no, then you should file the bug against '''HAL''' and follow the steps below. - 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} + * See [[DebuggingTouchpadDetection/evtest|this]] for help on how to enter VT and log evtest events. - 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ + 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ - $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} + $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} - 4. Press Crtl+Alt+F7 to switch back to X. + 4. Press Crtl+Alt+F7 to switch back to X. - 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. + 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. + *Check your {{{ cat /proc/bus/input/devices }}} , if you do not find something like this {{{ - Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - - {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 - {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} + N: Name="SynPS/2 Synaptics TouchPad" - {{{ P: Phys=isa0060/serio2/input0 }}} + P: Phys=isa0060/serio2/input0 - {{{ S: Sysfs=/devices/platform/i8042/serio2/input/input8 }}} + S: Sysfs=/devices/platform/i8042/serio2/input/input8 - {{{ U: Uniq= }}} + U: Uniq= - {{{ H: Handlers=mouse2 event8 }}} + H: Handlers=mouse2 event8 - {{{ B: EV=b }}} + B: EV=b - {{{ B: KEY=420 0 70000 0 0 0 0 0 0 0 0 }}} + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 - {{{ B: ABS=11000003 }}} + B: ABS=11000003 }}} - Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} + *In that case the bug is in the kernel itself and follow these steps: - If you do not find a Touchpad in you /proc/bus/inpus/devices, in that case the bug is in the kernel itself and you should follow these steps: - - 1. File the bug against '''linux''' + 1. File the bug against '''linux''' - 1. Provide the [[#generalinfo|general information]]. + 1. Provide the [[#generalinfo|general information]]. - 1. Enter the following command in a terminal/console: {{{ + 1. Enter the following command in a terminal/console: {{{ $ dmesg > ~/dmesg }}} - 1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. + 1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. == In case your Touchpad stops working after a while == From noreply at ubuntu.com Sat Dec 18 21:30:53 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 18 Dec 2010 21:30:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20101218213053.18810.54839@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=25&rev2=26 ------------------------------------------------------------------------------ 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} * See [[DebuggingTouchpadDetection/evtest|this]] for help on how to enter VT and log evtest events. - 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ + 2. Add identifier, Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit {{{ $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} 4. Press Crtl+Alt+F7 to switch back to X. 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. @@ -68, +68 @@ 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} * See [[DebuggingTouchpadDetection/evtest|this]] for help on how to enter VT and log evtest events. - 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ + 2. Add identifier, Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} 3. Press Crtl+Alt+F7 to switch back to X. 4. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in separate attachments. @@ -102, +102 @@ == In case Touchpad features like scrolling, tapping, etc do not work at all. == - This happens when 'Touchpad' Tab is not there in System>Preferences>Mouse. + Common symptom is absence of ''''Touchpad'''' Tab is not there in System>Preferences>Mouse. This may be a wrong detection by the '''xserver''' or the '''kernel''' itself. So xserver-xorg-input-synaptics has nothing to do with it. In case, filing a bug against the kernel('''linux'''), please note that you should not mark the bug as duplicate even if you can find a closely related bug and you have a strong feeling that the bug should be duplicate. This is a new policy of Kernel Team and it help them to handle the bugs better. @@ -126, +126 @@ 1. Enter the following command in a terminal/console: {{{ $ xmodmap -pp >~/xmodmap $ xinput --list-props >~/xinput }}} + * In {{{ xinput --list-props }}}, is of your Touchpad in {{{ xinput --list }}}. 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} + * See [[DebuggingTouchpadDetection/evtest|this]] for help on how to enter VT and log evtest events. - 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. + 2. Add identifier, Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. 4. Press Crtl+Alt+F7 to switch back to X. + 5. Include the xev log. + * See [[DebuggingTouchpadDetection/xev|this]] for help on how to report xev logs. - 5. Attach {{{~/xmodmap}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. + 5. Attach {{{~/xmodmap}}}, {{{~/xev}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. - - In {{{ xinput --list-props }}}, is of your Touchpad in {{{ xinput --list }}}. - - Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - - {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} - {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} - {{{ P: Phys=isa0060/serio2/input0 }}} - {{{ S: Sysfs=/devices/platform/i8042/serio2/input/input8 }}} - {{{ U: Uniq= }}} - {{{ H: Handlers=mouse2 event8 }}} - {{{ B: EV=b }}} - {{{ B: KEY=420 0 70000 0 0 0 0 0 0 0 0 }}} - {{{ B: ABS=11000003 }}} - - Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} === In case your multitouch features does not work === @@ -159, +147 @@ 1. For any other case, include the outputs in the bug report in separate comments. {{{ $ xinput --list-props >~/xinput }}} + * In {{{ xinput --list-props }}}, is of your touchpad in xinput --list. - 2. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} + * See [[DebuggingTouchpadDetection/evtest|this]] for help on how to enter VT and log evtest events. - 3. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. + 2. Add identifier, Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. 4. Press Crtl+Alt+F7 to switch back to X. 5. Take your pointer in the windows and hold down your two fingers on the Touchpad and raise. Also try to tap with two fingers. {{{ $ xev | grep -i button > ~/xev}}} 6. Attach {{{~/xev}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. - In {{{ xinput --list-props }}}, is of your touchpad in xinput --list. - - Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - - {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} - {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} - {{{ P: Phys=isa0060/serio2/input0 }}} - {{{ S: Sysfs=/devices/platform/i8042/serio2/input/input8 }}} - {{{ U: Uniq= }}} - {{{ H: Handlers=mouse2 event8 }}} - {{{ B: EV=b }}} - {{{ B: KEY=420 0 70000 0 0 0 0 0 0 0 0 }}} - {{{ B: ABS=11000003 }}} - - Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} - - Before filing new bug please look in the '''common bugs''' section. + '''Before filing new bug please look in the '''common bugs''' section.''' = Some general work flow for Triagers = From noreply at ubuntu.com Sat Dec 18 22:21:18 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 18 Dec 2010 22:21:18 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20101218222118.25353.42268@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=26&rev2=27 The comment on the change is: Updated Known isses ------------------------------------------------------------------------------ = Known bugs = - *Synaptics Touchpad Multitouch https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/308191 + *[[https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/308191|Synaptics Touchpad Multitouch]] - *Jumpy cursor https://bugs.edge.launchpad.net/xorg-driver-synaptics/+bug/365943 + *[[https://bugs.edge.launchpad.net/xorg-driver-synaptics/+bug/365943|Jumpy cursor]] - *Synaptics Touchpad is incorrectly detected by kernel https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/565543 + *[[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/565543|Synaptics Touchpad is incorrectly detected by kernel]] + * [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/565543|AlPS touchpad misdetected as PS/2 mouse in sony VAIO E series and some ACER laptops]] ---- CategoryBugSquad CategoryDebugging CategoryCleanup From noreply at ubuntu.com Sat Dec 18 21:08:09 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 18 Dec 2010 21:08:09 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20101218210809.11691.49472@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=23&rev2=24 The comment on the change is: Reconstructed 'In case your Touchpad stops working after a while' ------------------------------------------------------------------------------ == In case your Touchpad stops working after a while == - This is generally a case of kernel('''linux''') or '''xorg''' bug. In this case, in description field, specify the steps to make the touchpad stop working. eg- hit a key, drag or something. Now check by connecting a mouse that if it works or not. If no, then you should file the bug against '''HAL''' and follow the steps below. + This is generally a case of kernel('''linux''') or '''xorg''' bug. In this case, '''in description field, specify the steps to make the touchpad stop working'''. eg- hit a key, drag or something. Now check by connecting a mouse that if it works or not. + *If no, then you should file the bug against '''HAL''' and follow the steps below. + + 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + $ sudo evtest /dev/input/eventX > ~/evtest }}} + * See [[DebuggingTouchpadDetection/evtest|this]] for help on how to enter VT and log evtest events. + 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ + $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} + 3. Press Crtl+Alt+F7 to switch back to X. + 4. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in separate attachments. + + *Check your {{{ cat /proc/bus/input/devices }}} , if you do not find something like this {{{ + I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 + N: Name="SynPS/2 Synaptics TouchPad" + P: Phys=isa0060/serio2/input0 + S: Sysfs=/devices/platform/i8042/serio2/input/input8 + U: Uniq= + H: Handlers=mouse2 event8 + B: EV=b + B: KEY=420 0 70000 0 0 0 0 0 0 0 0 + B: ABS=11000003 }}} + + *If you do not find a Touchpad in you /proc/bus/inpus/devices, in that case the bug is in the kernel itself and you should follow these steps: + + 1. Provide the [[#generalinfo|general information]]. + 1. Direct after logging in to GNOME, KDE or Xfce open a terminal and enter the following commands: {{{ + $ dmesg > ~/dmesg_boot + $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} + 1. Wait until your touchpad stops working. + 1. Open a Virtual Terminal by pressing Ctrl-Alt-F1. + 1. Enter the following commands: {{{ + $ LANG=C + $ dmesg > ~/dmesg + $ diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff + $ cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp + $ diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff }}} + 1. Attach {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}} to the bug report in separate attachments. + + == In case Touchpad features like scrolling, tapping, etc do not work at all. == + + This happens when 'Touchpad' Tab is not there in System>Preferences>Mouse. + + This may be a wrong detection by the '''xserver''' or the '''kernel''' itself. So xserver-xorg-input-synaptics has nothing to do with it. In case, filing a bug against the kernel('''linux'''), please note that you should not mark the bug as duplicate even if you can find a closely related bug and you have a strong feeling that the bug should be duplicate. This is a new policy of Kernel Team and it help them to handle the bugs better. + + To check whether to report for kernel or not {{{ + $ cat /proc/bus/input/devices >~/devices }}} + If the output includes the name of your Touchpad eg Name="SynPS/2 Synaptics TouchPad", then kernel has detected it right. In this case, please don't report the bug against the kernel, rather report it against '''HAL'''. For more information on reporting bugs against HAL, refer DebuggingHal + + In any case, include the outputs of the following commands: {{{ + $ cat /proc/bus/input/devices >~/devices + $ xinput --list > ~/xinput + $ cat /var/log/Xorg.0.log > Xorg.0.log }}} + + Attach all four, to the bug report in separate attachments. + + '''IMP :''' Please do not file bug against the kernel unless you are very sure that it should be filed and do it only after reading this whole document. If you are unsure, file it against xserver-xorg-input-synaptics, somebody will change to kernel if is so. + + == In case at least one of Touchpad features works but does not work correctly and as expected == + + eg - Jumpy cursor, scrolling problems, Touchpad area is misdetected, circular scrolling, buttons not correctly mapped. + + 1. Enter the following command in a terminal/console: {{{ + $ xmodmap -pp >~/xmodmap + $ xinput --list-props >~/xinput }}} 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} - 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ + 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. - $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} 4. Press Crtl+Alt+F7 to switch back to X. - 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in separate attachments. + 5. Attach {{{~/xmodmap}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. + + In {{{ xinput --list-props }}}, is of your Touchpad in {{{ xinput --list }}}. Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this @@ -84, +148 @@ Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} - If you do not find a Touchpad in you /proc/bus/inpus/devices, in that case the bug is in the kernel itself and you should follow these steps: + === In case your multitouch features does not work === + This bug is common in Synaptics Touchpad V7.2 where multitouch works perfect in windows but not in linux. This is not a bug related to xserver-xorg-input-synaptics. Multitouch capabilities are not detected but the kernel itself as evident in {{{ xinput --list-props }}} shows + {{{ Synaptics Capabilities (277): 1, 1, 1, 0, 0 }}} - 1. Provide the [[#generalinfo|general information]]. - 1. Direct after logging in to GNOME, KDE or Xfce open a terminal and enter the following commands: {{{ - $ dmesg > ~/dmesg_boot - $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} - 1. Wait until your touchpad stops working. - 1. Open a Virtual Terminal by pressing Ctrl-Alt-F1. - 1. Enter the following commands: {{{ - $ LANG=C - $ dmesg > ~/dmesg - $ diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff - $ cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp - $ diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff }}} - 1. Attach {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}} to the bug report in separate attachments. - == In case Touchpad features like scrolling, tapping, etc do not work at all. == + This bug is already known (see the '''Known bugs''' below). In this case please don't file any new bugs and instead add a comment in the existing bug for any relevant information that you have. - This happens when 'Touchpad' Tab is not there in System>Preferences>Mouse. + '''NOTE :''' Synaptics is not willing to disclose the protocol it uses for the multitouch support for its newer Touchpads. As soon as Synaptics come up with its protocol, this issue will be fixed. So this is not a bug in general. So it has been classified as a wishlist. + 1. For any other case, include the outputs in the bug report in separate comments. {{{ - This may be a wrong detection by the '''xserver''' or the '''kernel''' itself. So xserver-xorg-input-synaptics has nothing to do with it. In case, filing a bug against the kernel('''linux'''), please note that you should not mark the bug as duplicate even if you can find a closely related bug and you have a strong feeling that the bug should be duplicate. This is a new policy of Kernel Team and it help them to handle the bugs better. - - To check whether to report for kernel or not {{{ - $ cat /proc/bus/input/devices >~/devices }}} - If the output includes the name of your Touchpad eg Name="SynPS/2 Synaptics TouchPad", then kernel has detected it right. In this case, please don't report the bug against the kernel, rather report it against '''HAL'''. For more information on reporting bugs against HAL, refer DebuggingHal - - In any case, include the outputs of the following commands: {{{ - $ cat /proc/bus/input/devices >~/devices - $ xinput --list > ~/xinput - $ cat /var/log/Xorg.0.log > Xorg.0.log }}} - - Attach all four, to the bug report in separate attachments. - - '''IMP :''' Please do not file bug against the kernel unless you are very sure that it should be filed and do it only after reading this whole document. If you are unsure, file it against xserver-xorg-input-synaptics, somebody will change to kernel if is so. - - == In case at least one of Touchpad features works but does not work correctly and as expected == - - eg - Jumpy cursor, scrolling problems, Touchpad area is misdetected, circular scrolling, buttons not correctly mapped. - - 1. Enter the following command in a terminal/console: {{{ - $ xmodmap -pp >~/xmodmap $ xinput --list-props >~/xinput }}} - 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ + 2. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} - 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. + 3. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. 4. Press Crtl+Alt+F7 to switch back to X. + 5. Take your pointer in the windows and hold down your two fingers on the Touchpad and raise. Also try to tap with two fingers. {{{ + $ xev | grep -i button > ~/xev}}} - 5. Attach {{{~/xmodmap}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. + 6. Attach {{{~/xev}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. - In {{{ xinput --list-props }}}, is of your Touchpad in {{{ xinput --list }}}. + In {{{ xinput --list-props }}}, is of your touchpad in xinput --list. Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this @@ -148, +183 @@ Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} - === In case your multitouch features does not work === - - This bug is common in Synaptics Touchpad V7.2 where multitouch works perfect in windows but not in linux. This is not a bug related to xserver-xorg-input-synaptics. Multitouch capabilities are not detected but the kernel itself as evident in {{{ xinput --list-props }}} shows - {{{ Synaptics Capabilities (277): 1, 1, 1, 0, 0 }}} - - This bug is already known (see the '''Known bugs''' below). In this case please don't file any new bugs and instead add a comment in the existing bug for any relevant information that you have. - - '''NOTE :''' Synaptics is not willing to disclose the protocol it uses for the multitouch support for its newer Touchpads. As soon as Synaptics come up with its protocol, this issue will be fixed. So this is not a bug in general. So it has been classified as a wishlist. - - 1. For any other case, include the outputs in the bug report in separate comments. {{{ - $ xinput --list-props >~/xinput }}} - 2. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ - $ sudo evtest /dev/input/eventX > ~/evtest }}} - 3. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. - 4. Press Crtl+Alt+F7 to switch back to X. - 5. Take your pointer in the windows and hold down your two fingers on the Touchpad and raise. Also try to tap with two fingers. {{{ - $ xev | grep -i button > ~/xev}}} - 6. Attach {{{~/xev}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. - - In {{{ xinput --list-props }}}, is of your touchpad in xinput --list. - - Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this - - {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} - {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} - {{{ P: Phys=isa0060/serio2/input0 }}} - {{{ S: Sysfs=/devices/platform/i8042/serio2/input/input8 }}} - {{{ U: Uniq= }}} - {{{ H: Handlers=mouse2 event8 }}} - {{{ B: EV=b }}} - {{{ B: KEY=420 0 70000 0 0 0 0 0 0 0 0 }}} - {{{ B: ABS=11000003 }}} - - Here your {{{ /dev/input/eventX }}} is {{{ /dev/input/event8 }}} - Before filing new bug please look in the '''common bugs''' section. = Some general work flow for Triagers = From hggdh2 at ubuntu.com Tue Dec 21 14:53:42 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Tue, 21 Dec 2010 08:53:42 -0600 Subject: Changes to eeeBotu (bug announcer bot) Message-ID: <4D10BF76.4000804@ubuntu.com> Hello all, As you may (or may not) know, we have a bot -- eeeBotu -- that announces new Ubuntu bugs on the #ubuntu-bugs-announce channel on irc.freenode.net. -- History Interlude -- This bot was written by Mike Rooney in 2008, after we lost the then-offical bug-announcing bot. The name 'eeeBotu' came from the fact that Mike originally was running the bot on his eeePC, and that it was a bot for Ubuntu (as expected, for this last part). After a while, Mike had a problem on the eeePC, and was looking for someone to host the bot. Well, I had the equipment and excess bandwidth, so I started running it. eeeBotu transferred itself to an old Pentium-4 machine, and has been happily there since. (The P4 is starting to complain of age, so I will probably be moving eeeBotu to a not-so-old box in the future.) Anyway. At the time I started running eeeBotu Mike and I had a lot of ideas of what the bot could/should do. But... it was working nice, and we had other things to do... so it was left alone, just grabbing new bugs for Ubuntu, and announcing them on the channel. Then... yesterday Jorge Castro pinged me, and asked if eeeBotu could also monitor Ayatana bugs. Sure, I said. "I want the bugs announced on the -- say -- #ayatana-bugs channel", said Jorge. "Sure" -- I said -- "just give me a few minutes to code it in". Well, it took a bit more than "a few minutes", and it was more than a quick hack. -- End History Interlude -- I am happy to announce that: 1. The #ayatana-bugs channel will now have eeeBotu announcing bugs affecting (ayatana|compiz|unity). Please note that these are upstream projects on LP, *not* the Ubuntu packages; 2. eeeBotu is now capable of monitoring bugs for different sets of projects on different channels. The only restriction -- right now -- is that the channels must be on freenode.net. Please ping me on questions. Cheers, ..C.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: From autumneagle at verizon.net Fri Dec 24 23:03:34 2010 From: autumneagle at verizon.net (Mark Eastabrooks) Date: Fri, 24 Dec 2010 18:03:34 -0500 Subject: NVIDIA Message-ID: <000001cba3be$cac0d560$60428020$@net> Hello everyone, I hope this the right place to look for advice, if not I apologize in advance. I have been trying to install Ubuntu 10.10 and it won't display video correctly. The screen goes patchy and won't display properly so I cannot finish the install. I have an NVIDIA GT 240 card for reference. Any advice would help. Respectfully, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Wed Dec 22 19:16:56 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 22 Dec 2010 19:16:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_nav=2Ecod?= =?utf-8?q?er?= Message-ID: <20101222191656.23289.45034@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by nav.coder: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=143&rev2=144 ------------------------------------------------------------------------------ || ''' <> ''' || - ||Contents<
>    1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20Types|Bug Types]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20reports|Apport reports]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports|Apport crash reports]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirmed%20bugs|Confirmed bugs]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Feature%20Requests|Feature Requests]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Regressions|Regressions]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged%20bugs|Untriaged bugs]]<
>        6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20reports%20not%20in%20English|Bug reports not in English]]<
>        7. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs|Special types of bugs]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Developer%20Process%20Bugs|Developer Process Bugs]]<
>            2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs|Needs Packaging Bugs]]<
>            3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Security%20Bugs|Security Bugs]]<
>            4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Translation%20Bugs%20and%20Launchpad%20integration|Translation Bugs and Launchpad integration]]<
>    2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Actions|Actions]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming|Confirming]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding%20upstream|Forwarding upstream]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20a%20Bug%20as%20Requiring%20Forwarding|Marking a Bug as Requiring Forwarding]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20duplicate|Marking duplicate]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Improving%20a%20bug%20report|Improving a bug report]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Converting%20a%20bug%20report%20to%20a%20question|Converting to a question]]<
>    6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Invalidating|Invalidating]]<
>    3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Status%20and%20Importance|Status and Importance]]<
>    4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Looking%20through%20your%20bugs|Looking through your bugs]]|| + ||Contents<
>    1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20Types|Bug Types]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20reports|Apport reports]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports|Apport crash reports]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirmed%20bugs|Confirmed bugs]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Feature%20Requests|Feature Requests]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Regressions|Regressions]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged%20bugs|Untriaged bugs]]<
>        6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20reports%20not%20in%20English|Bug reports not in English]]<
>        7. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs|Special types of bugs]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Developer%20Process%20Bugs|Developer Process Bugs]]<
>            2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs|Needs Packaging Bugs]]<
>            3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Security%20Bugs|Security Bugs]]<
>            4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Translation%20Bugs%20and%20Launchpad%20integration|Translation Bugs and Launchpad integration]]<
>    2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Actions|Actions]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming|Confirming]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding%20upstream|Forwarding upstream]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20a%20Bug%20as%20Requiring%20Forwarding|Marking a Bug as Requiring Forwarding]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20duplicate|Marking duplicate]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Improving%20a%20bug%20report|Improving a bug report]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Converting%20a%20bug%20report%20to%20a%20question|Converting to a question]]<
>        6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Invalidating|Invalidating]]<
>    3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Status%20and%20Importance|Status and Importance]]<
>    4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Looking%20through%20your%20bugs|Looking through your bugs]]|| In a hospital, triage happens the instant a patient arrives through the emergency room doors. His vital signs are checked, his status assessed, and he gets sorted in amongst all the other patients waiting for treatment. From neshuagarwal1909 at gmail.com Thu Dec 30 13:36:42 2010 From: neshuagarwal1909 at gmail.com (Aman (neshu) Agarwal) Date: Thu, 30 Dec 2010 19:06:42 +0530 Subject: Want to participate as a student Message-ID: Hello, I am Aman Agarwal (neshuagarwal1909 Launchpad Username) want to participate as a student I read the information available on https://wiki.ubuntu.com/BugSquad/Mentors and already installed the https://wiki.ubuntu.com/BeginnersTeam/FocusGroups/Development/Devbeginnings#Thorough%20Install:%20Ubuntu%20Development%20Toolstools required for development in my ubuntu. Since I am a novice Developer and want to start with some sort of fixing bugs in ubuntu by this way I wish to start contributing in it, So I request admin to assign me a mentor. Right now I too don't know about my interest in terms of project but still I am reading docs available on site and trying to figure it out ;). I can code in C or C++ and hope that you guys will give me initial direction. Regards Aman Agarwal neshuagarwal1909 : Launchpad fat0ss : IRC -------------- next part -------------- An HTML attachment was scrubbed... URL: From marconifabio at ubuntu-it.org Fri Dec 31 12:39:21 2010 From: marconifabio at ubuntu-it.org (njin) Date: Fri, 31 Dec 2010 13:39:21 +0100 Subject: [Ubuntu-bugcontrol] Application for the bugcontrol team In-Reply-To: <1293784323.11991.107.camel@Aspire-5670> References: <1293784323.11991.107.camel@Aspire-5670> Message-ID: Please remember that i can only assign packages, set status (incomplete, confirmed, invalid) and in the case send upstream. > > -Is there a particular package or group of packages that you are > > interested in helping out with? ****Ubiquity, Debian-installer. > > https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/684083 the only things that i can do is assign package, and as i'm the only reporter i cannot confirm. > This bug was reported by you and it was triaged by Colin instead. > > reproduced looking at top ghostscript at 100% of cpu > > https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/642888 > > > > You did identify the package, but the bug here was triaged by Charlie > (comment#1). > > Remembering the debugging of gpm i've decided to switch off plymouth at > > boot, hight set by chris as makes ubuntu unusable for nvidia cards I cannot triage bugs > > https://bugs.launchpad.net/launchpad/+bug/692291 > I think you might have quoted the Wrong bug # here? > This is not an Ubuntu package bug, this is a bug in launchpad itself. > > But why on this pc don't work and on the other works, ah it's not > > maximized....i'm the only reporter, importance set by another Yes, here i get wrong not assigning the package, but at now i cannot remeber why.... > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/390959 > You could have just asked the reporter to run the following command: > $ apport-collect 390959 > That would have collected all the info that was required , rather than > the reporter having to attach one file at a time. It would have been a > lot more easier for the reporter. > This looks like one of your earlier bugs, but We need to remember the > tools available to us. > > > just following how to triage > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/480903 > > In this bug you did mention apport :) > But, when requesting information you changed the status from: > incomplete -> confirmed , rather you should have left the status as > incomplete until the apport info was collected. > > Luckily the reported did add info using apport. > But what if the bug reporter had not? The bug would have been marked > confirmed without any info. Yes, too sure of the number of afflicted person > > missed driver in the kernel. reporter sayd that installing drivers from > > producer site make it working. > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/674663 > > The tagging for this bug is weird and introduces custom tags. > The correct tag to be used here is `needs-upstream-testing` and once > done it just needs to be removed. no need for any new tag. > Are you sure about the tag 'regression-update' here? There is no > indication that an update from the maverick-updates caused the bug. > It seems more like a `regression-release` since the bug was also later > re-titled. > What would have helped was, if the reporter was asked if the problem did > not exist when he installed Ubuntu 10.10 fresh. And started happening > only after a particular update. It would narrow-down the cause of the > bug here. Ok for the tags, i'm learning, but this is a regression-update, because reporter said 'after first update', and Stenten has modified the title, and looking the procversionsignature the installed kernel is 2.6.35-22.35, but the release ship the 2.6.35-22.33 > for more info on tags: > > > Thanks! > > > > as john lennon sing "with a little help from my friends" > > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/668800 > > This one seems fine. Would have preferred info from the original > reporter though, but a triager adding the info is also good. > > > IMO, The list here would only be 4 bugs that you had triaged for others. > However, I'v noticed that you have been doing a lot of triaging, but the > bugs you selected are not a great list. If i had not noticed the work > you've been doing , based on the bugs listed here I would have -1'd your > application. > > But, I'm pretty sure you would have a better list of bugs that *you* > have triaged for others. > So +0 for now. > > > i don't remember > > And many others > > > > Have a look at: > > > > Try to choose bugs where you have made less mistakes, preferable > none. :) i'll look at it this evening > > Have a look at the BugControl criteria: > 20Process> > And a few example applications: > Thanks again! > > Everyone makes mistakes when starting with bug triage, but when > submitting an application for Bug Control it is better that you list the > bugs where you have done your *best* work. Everytime i do my best, there's no one bug different from the other, also expalining how to set the system is a usability bug. I don't like to play with the works of other persons. > If you are not able to find any bugs without mistakes, I'd suggest you > focus on the packages you are interested in(Ubiquity, Debian-installer) > and get back with a good bug list. See you soon > Looking forward for a better list of bugs.. :) I think that is more fastest go on > Also do mention the bug importance that you think is appropriate, > BugControl are the folks who set these, so it's kinda important that you > mention along with the bug list too . (Yes, the wiki is ambiguous, looks > like the wiki needs to be updated and more clear about this. Every > 'triaged' bug,which is what we request for bugcontrol application, would > have an importance set, so adding the clause of "does not have an > importance" is a moot point. Have a look at the application examples.) > > Thanks vish to look into this. Fabio