← Back to team overview

ubuntu-bugcontrol team mailing list archive

Re: Application for Bug Control Team - Ahmed Shams(~ashams)

 

On 16/09/11 12:07, Ahmed Shams wrote:
> Hello Everybody,
> My name is Ahmed Shams(ashams), a bug triager, and I request to
> join Bug Control Team.
> https://launchpad.net/~ashams <https://launchpad.net/%7Eashams>
> https://wiki.ubuntu.com/AhmedShams
>
> Here are the requested answers:
>
>   * Do you promise to be polite to bug reporters even if they are
>     rude to you or Ubuntu? Have you signed the Ubuntu Code of Conduct?
>
> Of course Yes.
>
>  *
>
>     Have you read Bugs/HowToTriage
>     <https://wiki.ubuntu.com/Bugs/HowToTriage>, Bugs/Assignment
>     <https://wiki.ubuntu.com/Bugs/Assignment>, Bugs/Status
>     <https://wiki.ubuntu.com/Bugs/Status> and Bugs/Importance
>     <https://wiki.ubuntu.com/Bugs/Importance>? Do you have any
>     questions about that documentation?
>
> Yes I read them. No I don't have questions anymore!
>
>  *
>
>     What sensitive data should you look for in a private Apport
>     crash report bug before making it public? See Bugs/HowToTriage
>     <https://wiki.ubuntu.com/Bugs/HowToTriage> for more information.
>
> This point requires some detailed explaination, but in short:
> 'Coredump.gz' if exists check for 'Stacktrace.txt' if exist too
> check 'Stacktrace.txt' and 'ThreadStacktrace.txt' for sensitive
> data(ie passwords, server names, or any other data that can harm
> it's owner if opened to public) if found sensitive data in
> 'Stacktrace.txt' and/or 'ThreadStacktrace.txt' keep the bug
> private through it's life, if didn't find any sensitive data
> anywhere in both files remove 'Coredump.gz'(if it still exists)
> and mark as public. In all cases it won't harm if bug kept private
> through it's life, but can harm if marked public(counting human
> error to recognize sensitive data).
>
>   * Is there a particular package or group of packages that you
>     are interested in helping out with?
>
> I like 'xserver-xorg-input-synaptics' and I work in it most of my
> time, but I like to get outside Xorg when it gets hellish!.
>
>  *
>
>     Five bug reports which I have triagged and Explanation of my
>     decisions:
>
> *[1]*=======================
> *Bug#*: pad.lv/825548 <http://pad.lv/825548>
> *Bug*: Touchpad cursor moves twice as fast horizontally after
> connecting an external monitor
> *Decision*: Enhanced title, Requested information and set to
> 'Incomplete. After investigating files reporter attached, bug
> 'Confirmed' then forwarded upstream.       
>
> *Importance*: 'Medium'
> *Importance* *Explanation*: Known bug + affects wide range of
> users of default installation.
>
> *[2]*=======================
> *Bug*#: pad.lv/822144 <http://pad.lv/822144>
> *Bug*: Touchpad with integrated click buttons: right button
> missing, both mouse buttons act as left
> *Decision*: Requested information and set to 'Incomplete.  After
> investigating files reporter attached, bug 'Confirmed' then
> forwarded upstream.
> *Decision* *Explanation*: bug lacked documentation, after reporter
> replied continued triagging.   
>
> *Importance*: 'High'
> *Importance* *Explanation*: Severe impact on users of a popular
> machine.
>
> *[3]*=======================
> *Bug*#: pad.lv/815163 <http://pad.lv/815163>
> *Bug*: [EEPC-1215p] touchpad does weird things after a few minutes
> of use
> *Decision*: Moved to Kernel(linux)
> *Decision* *Explanation*: Xorg failed to read device(recorded in
> 'XorgLog.txt')
>
> *Importance*: 'Low'
> *Importance* *Explanation*: Workaround existed(though hard)
>
> *[4]*=======================
> *Bug*#: pad.lv/833840 <http://pad.lv/833840>
> *Bug*: synaptics touchpad doesnt enable after disabling from fn+f6
> key on dell xps l702x. Even after restart just doesn't work now
> *Decision*: Requested info and marked incomplete, after reporter
> replied and made some investigation, moved to
> 'gnome-settings-daemon' (which is out of my experience, so we need
> help overthere!)
> *Decision* *Explanation*: proplem troubleshooted for every
> potential cause one by one but seemed to be clear, so moved to
> it's latest potential cause(in my opinion).
>
> *Importance*: 'Low'
> *Importance* *Explanation*: Caused by defined user action which
> can be easily worked around (though it can be annoying)
>
> *[5]*=======================
> *Bug*#: pad.lv/844892 <http://pad.lv/844892>
> *Bug*: No mouse (touchpad & nipple) after installation, usb mouse
> works (thinkpad t43/p) [oneiric beta-1]
> *Decision*: Marked to 'Incomplete' then 'Confirmed' in kernel
> after reporter's response. Not forwarded to Kernel BTS as
> kernel.org <http://kernel.org> is under maintenance till now!.
> *Decision* *Explanation*: Xorg doesn't detect device at all, in
> order to move to kernel(linux) and forward upstream I requested
> more testing/info to confirm it in kernel. Thanks to the
> reporter(latrom) the devices file confirmed it.
>
> *Importance*: 'High'
> *Importance* *Explanation*: Causes total inusability in touchpad
> and even in mouse(see comment#5).

(Simplest to add my comment at the end of the bug list)

Agree with all. Also, I really appreciate the upstream bug you
opened and linked in bug 825548. Good work all in all!

+1


>
> /I would like to express appreciation to Gursimran Singh Mohar
> (simar) for his great effort on helping me down the road to here,
> Thanks man :)/

+1. Thank you, simar :-)

Cheers,

..C..

Attachment: signature.asc
Description: OpenPGP digital signature


Follow ups

References