From noreply at ubuntu.com Wed Nov 2 21:53:14 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 02 Nov 2011 21:53:14 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_sense?=
Message-ID: <20111102215314.16773.82897@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/Tags" page has been changed by sense:
http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=187&rev2=188
Comment:
Ordering!
##
## The line below makes moinmoin explode why? It used to work before the upgrade on 2008-08-06
##<<Include(DebuggingNetworkManager,"Network Manager",5,from="== Bug Tags ==", to="^The previously described tags are specific")>>
- === Open Office ===
- <<Include(DebuggingOpenOffice, ,5,from="= Bug Tags =", to="= Debugging procedure =")>>
- === Network Manager ===
- <<Include(DebuggingNetworkManager, ,5,from="== Bug Tags ==", to="^The previously described tags are specific")>>
- === Update Manager ===
- <<Include(DebuggingUpdateManager,,5,from="= Bug Tags =", to="^The previously described tags are specific")>>
+
+
+ === Cheese Specific ===
+ Tags Apport adds while collecting information for Cheese Webcam Booth.
+ ||<rowbgcolor="#FFEBBB"> '''Tag''' || '''Use case''' ||
+ || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''||
+ || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-ok|`gstreamer-ok`]] || Video gstreamer input works fine (drivers seem fine), most likely a Cheese bug ||
+
=== Firefox/Xulrunner Stable Upgrade Regressions ===
||<rowbgcolor="#FFEBBB"> '''Tag''' || '''Use case''' ||
|| [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-hardy|`ffox36-hardy`]] || Regressions on Hardy due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 ||
|| [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-jaunty|`ffox36-jaunty`]] || Regressions on Jaunty due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 ||
|| [[https://launchpad.net/ubuntu/+bugs?field.tag=ffox36-karmic|`ffox36-karmic`]] || Regressions on Karmic due to the Stable Release Upgrade to Firefox 3.6/Xulrunner 1.9.2 ||
- === Cheese Specific ===
- Tags Apport adds while collecting information for Cheese Webcam Booth.
- ||<rowbgcolor="#FFEBBB"> '''Tag''' || '''Use case''' ||
- || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''||
- || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-ok|`gstreamer-ok`]] || Video gstreamer input works fine (drivers seem fine), most likely a Cheese bug ||
- == Other specific bug tags ==
+ === Network Manager ===
+ <<Include(DebuggingNetworkManager, ,5,from="== Bug Tags ==", to="^The previously described tags are specific")>>
+
+ === Open Office ===
+ <<Include(DebuggingOpenOffice, ,5,from="= Bug Tags =", to="= Debugging procedure =")>>
=== Unity ===
@@ -89, +90 @@
|| [[https://launchpad.net/unity/+bugs?field.tag=needs-design|`needs-design`]] || A bug that needs UI design done first. ||
|| [[https://launchpad.net/unity/+bugs?field.tag=backlog|`backlog`]] || Things that design has done and has finished on that needs to be implemented. ||
+ === Update Manager ===
+ <<Include(DebuggingUpdateManager,,5,from="= Bug Tags =", to="^The previously described tags are specific")>>
+
+ == Other specific bug tags ==
=== Ayatana ===
Specific bugs concerning parts of the [[https://launchpad.net/ayatana|Ayatana project]].
From brian at ubuntu.com Thu Nov 3 12:03:58 2011
From: brian at ubuntu.com (Brian Murray)
Date: Thu, 3 Nov 2011 05:03:58 -0700
Subject: [Ubuntu Wiki] Update of "Bugs/Tags" by sense
In-Reply-To: <20111102215314.16773.82897@mangaba.canonical.com>
References: <20111102215314.16773.82897@mangaba.canonical.com>
Message-ID: <20111103120358.GW3395@murraytwins.com>
On Wed, Nov 02, 2011 at 09:53:14PM -0000, Ubuntu Wiki wrote:
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
>
> The "Bugs/Tags" page has been changed by sense:
> http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=187&rev2=188
>
> Comment:
> Ordering!
>
> ##
> ## The line below makes moinmoin explode why? It used to work before the upgrade on 2008-08-06
> ##<<Include(DebuggingNetworkManager,"Network Manager",5,from="== Bug Tags ==", to="^The previously described tags are specific")>>
> - === Open Office ===
> - <<Include(DebuggingOpenOffice, ,5,from="= Bug Tags =", to="= Debugging procedure =")>>
> - === Network Manager ===
> - <<Include(DebuggingNetworkManager, ,5,from="== Bug Tags ==", to="^The previously described tags are specific")>>
> - === Update Manager ===
> - <<Include(DebuggingUpdateManager,,5,from="= Bug Tags =", to="^The previously described tags are specific")>>
> +
> +
> + === Cheese Specific ===
> + Tags Apport adds while collecting information for Cheese Webcam Booth.
> + ||<rowbgcolor="#FFEBBB"> '''Tag''' || '''Use case''' ||
> + || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''||
This reminds me that I modified the cheese apport hook in Oneiric so that
this happens now automatically. So perhaps this doesn't need to be
listed here any more.
--
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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111103/7eaa1423/attachment.sig>
From ankit28595 at gmail.com Sat Nov 5 08:11:22 2011
From: ankit28595 at gmail.com (Ankit saini)
Date: Sat, 5 Nov 2011 13:41:22 +0530
Subject: Asking guidance on triaging bugs.
Message-ID: <CAC9jQ5ot7Bge-DZH+YW-FtmJvqpV-gp9oVcwrTJXCPJqFBVYag@mail.gmail.com>
Hi, I have recently joined the Ubuntu bug squad so I am a bit confused
regarding the actions one should take during the triaging process
For example take bug #886450. In it the Gvim and Emacs hang when
started unmaximized. I was unable to reproduce the bug but the
reporter is sure that he is having this bug.
Now, I want to know what should be done now
Should it be reported to Vim and Emacs bug database
Or anywhere else
It surely is not due to the window manager since the bug persists even
after changing the window manager.
Thank you.
From lcpak at epoczta.pl Sat Nov 5 08:18:48 2011
From: lcpak at epoczta.pl (=?UTF-8?B?xYF1a2FzeiBPbHN6ZXdza2k=?=)
Date: Sat, 05 Nov 2011 09:18:48 +0100
Subject: Asking guidance on triaging bugs.
In-Reply-To: <CAC9jQ5ot7Bge-DZH+YW-FtmJvqpV-gp9oVcwrTJXCPJqFBVYag@mail.gmail.com>
References: <CAC9jQ5ot7Bge-DZH+YW-FtmJvqpV-gp9oVcwrTJXCPJqFBVYag@mail.gmail.com>
Message-ID: <4EB4F168.3090004@epoczta.pl>
The right thing to do now is to ask the reported for a proper backtrace
for hanging apps. Please refer to: https://wiki.ubuntu.com/Backtrace for
more details.
05.11.2011 09:11, Ankit saini:
> Hi, I have recently joined the Ubuntu bug squad so I am a bit confused
> regarding the actions one should take during the triaging process
> For example take bug #886450. In it the Gvim and Emacs hang when
> started unmaximized. I was unable to reproduce the bug but the
> reporter is sure that he is having this bug.
> Now, I want to know what should be done now
> Should it be reported to Vim and Emacs bug database
> Or anywhere else
> It surely is not due to the window manager since the bug persists even
> after changing the window manager.
>
> Thank you.
>
From noreply at ubuntu.com Tue Nov 8 00:47:09 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Tue, 08 Nov 2011 00:47:09 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_bria?=
=?utf-8?q?n-murray?=
Message-ID: <20111108004709.12520.90835@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/FindRightPackage" page has been changed by brian-murray:
http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=117&rev2=118
2. Open a Terminal (GNOME: Applications -> Accessories -> Terminal | KDE: K -> Applications -> System -> Terminal).
3. In the terminal, type `xprop WM_CLASS`. Your mouse pointer should now turn to crosshairs.
4. Click anywhere in the application's window.
- 5. The terminal will now list a line like `WM_CLASS(STRING) = "Picasa3.exe", "Wine"`. Write down the first value ("Picasa3.exe").
+ 5. The terminal will now list a line like `WM_CLASS(STRING) = "terminator", "Terminator"`. Write down the first value ("terminator").
- 6. In the terminal, type `locate -b "\[executable name]"`. (In this case, `locate -b "\Picasa3.exe"`.) The backslash (\) is important!
+ 6. In the terminal, type `locate -b "\[executable name]"`. (In this case, `locate -b "\terminator"`.) The backslash (\) is important!
7. Write down the line printed on the terminal. (If there are multiple lines, use the first one.) This is the full executable path.
==== Finding the Package Name ====
After you have found the executable path, finding the package name is easy. Just run `dpkg -S [full executable path]`. For example, `dpkg -S /usr/bin/gnome-display-properties`. This will print the package name: you're done!
- Another tool useful when triaging bugs is '''apt-file''': `apt-file search picasa.exe`. This utility works like `dpkg -S` but searches all packages instead of only those you have installed.
+ Another tool useful when triaging bugs is '''apt-file''': `apt-file search terminator`. This utility works like `dpkg -S` but searches all packages instead of only those you have installed.
=== When installing Ubuntu (or Derivatives) ===
@@ -72, +72 @@
=== When upgrading Ubuntu (or derivatives) ===
- If you encounter a bug while upgrading Ubuntu (for example, from 9.04 to 9.10), the problem package is `update-manager`. Please attach the log files contained in "/var/log/dist-upgrade/".
+ If you encounter a bug while upgrading Ubuntu (for example, from 11.04 to 11.10), the problem package is `update-manager`. Please attach the log files contained in "/var/log/dist-upgrade/".
=== During boot ===
If you encounter a bug with the boot splash screen (typically an Ubuntu logo displayed during boot), the package is:
+
- * `plymouth` since 10.04 Lucid Lynx,
+ * `plymouth` since 10.04 Lucid Lynx
- * `xsplash` in 9.10 Karmic Koala and
- * `usplash` in versions before that.
If the screen goes blank after the splash screen (about the time the login screen should come up), report the bug against `xorg`.
@@ -135, +134 @@
=== Sound ===
- If your sound or headphone jack does not work correctly, report the issue against `alsa-driver` in 9.04 Jaunty Jackalope and above. Report [[#Kernel|against the kernel]] in previous versions.
+ If your sound or headphone jack does not work correctly, report the issue against `alsa-driver` in 9.04 Jaunty Jackalope and above.
You might want to try [[https://help.ubuntu.com/community/SoundTroubleshooting|Sound Troubleshooting]] first.
@@ -165, +164 @@
Some packages have changed names through versions of ubuntu and others need special care while reporting. This section lists these caveats.
- === Kernel ===
-
- The correct package for bugs about the kernel is `linux`, unless you are running 6.06 Dapper Drake, in which case the package is `linux-source-2.6.15`.
-
- Please read [[KernelTeam/KernelTeamBugPolicies]] when reporting bugs against the kernel.
-
=== Firefox ===
Please put Firefox bugs in the appropriate package depending on the version of Firefox.
Currently we have:
+ * firefox-3.0 - the default version in Hardy (8.04)
- * firefox-3.0 - the default version in Hardy (8.04), Intrepid (8.10) and Jaunty (9.04)
- * firefox-3.5 - the default version in Karmic (9.10) also available in Jaunty (9.04)
* firefox - the default version in Lucid (10.04) -- This is Firefox 3.6 and up
=== Epiphany ===
From noreply at ubuntu.com Wed Nov 9 14:07:15 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 09 Nov 2011 14:07:15 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_kamstrup?=
Message-ID: <20111109140715.5493.40522@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/Responses" page has been changed by kamstrup:
http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=337&rev2=338
Comment:
Add repsonse "Hanging Application or Daemon"
||<tablestyle="background-color: #eee">Thanks for taking the time to report this bug in the upstream bug tracking system this is a tremendous help. Launchpad has the ability to watch lots of upstream bug trackers and this can be done by following the procedure documented at https://wiki.ubuntu.com/Bugs/Watches. I've added the bug watch for this bug report.||
+ == Hanging Application or Daemon ==
+
+ ||<tablestyle="background-color: #eee">Thanks for your interest in helping to resolve this issue. In order to get to the bottom of this we need to figure out where the program is hanging. If you can follow the steps on https://wiki.ubuntu.com/Backtrace#Already_running_programs and attach the generated text file to this bug it would be of great help. ||
+
== Links ==
Other projects have standard responses as well:
From noreply at ubuntu.com Sun Nov 13 12:16:22 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Sun, 13 Nov 2011 12:16:22 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/GettingInvolved=22_by_s?=
=?utf-8?q?witchdk?=
Message-ID: <20111113121622.8773.68743@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "BugSquad/GettingInvolved" page has been changed by switchdk:
http://wiki.ubuntu.com/BugSquad/GettingInvolved?action=diff&rev1=25&rev2=26
Comment:
Removed references to mentorship program
<<Include(BugSquad/Header)>>
== Bug Squad ==
+ Consider joining the [[BugSquad|Bug Squad]] to keep up to date on current issues with triaging. However, joining is entirely optional but recommended.
- Consider joining the BugSquad to keep up to date on current issues with triaging. However, joining is entirely optional. We also offer a mentorship program for triaging. Please see [[https://wiki.ubuntu.com/QATeam/Specs/SpecialisationWithinBugcontrol|Specialisation within BugControl]] for details, but basically, you need to:
- * Sign the [[http://www.ubuntu.com/community/conduct|Code of Conduct]]
- * Subscribe to the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad| Bug Squad Mailing List]]
- * Although not really required, read the [[https://wiki.ubuntu.com/Bugs/HowToTriage|How to Triage]] guide. It '''does''' help to read it ;-)
- * Request a mentor by following the instructions on [[BugSquad/Mentors]] where you will need to provide:
- * An area of specialisation (if you have any)
- * Timezone
- * Time when available
- Members of the Bug Squad, [[https://wiki.ubuntu.com/UbuntuBugControl|Bug Control]], and Canonical employees are available in #ubuntu-bugs to answer any questions you might have.
+ Should you have any questions relating to triaging or other questions with regards to the Bug Squad team/process you can raise your questions in the [[irc://irc.freenode.org/#ubuntu-bugs|#ubuntu-bugs]] channel on [[IRC|IRC]]. Members of the [[BugSquad|Bug Squad]], [[UbuntuBugControl|Bug Control]], and Canonical employees are available to answer any questions you might have.
== Assigning Packages ==
From noreply at ubuntu.com Sun Nov 13 12:31:17 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Sun, 13 Nov 2011 12:31:17 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/FAQ=22_by_switchdk?=
Message-ID: <20111113123117.14781.85687@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "BugSquad/FAQ" page has been changed by switchdk:
http://wiki.ubuntu.com/BugSquad/FAQ?action=diff&rev1=13&rev2=14
Comment:
Updated to remove references to mentorship program
== How do I start to Triage a bug ? ==
- We recommend to every new triager to read our [[https://wiki.ubuntu.com/Bugs/HowToTriage|Triage Guide]] and to request a [[https://wiki.ubuntu.com/BugSquad/Mentors|Mentor]], if you have doubts regarding any part of the document please contact us.
+ We recommend to every new triager to read our [[https://wiki.ubuntu.com/Bugs/HowToTriage|Triage Guide]] and to raise any questions in the [[irc://irc.freenode.org/#ubuntu-bugs|#ubuntu-bugs]] channel on [[IRC|IRC]].
== Do I need to have reproduced or recreated a bug to confirm it? ==
From noreply at ubuntu.com Sun Nov 13 12:33:47 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Sun, 13 Nov 2011 12:33:47 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/FAQ=22_by_switchdk?=
Message-ID: <20111113123347.14775.83132@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "BugSquad/FAQ" page has been changed by switchdk:
http://wiki.ubuntu.com/BugSquad/FAQ?action=diff&rev1=14&rev2=15
Comment:
Updated to fix formatting problems in welcome text
||<tablestyle="width:50%;" style="width: 40px; border: none; -moz-border-radius-topleft: 15px ;-moz-border-radius-bottomleft: 15px; background-color: #F1F1DD;text-align: left;">{{attachment:faq.png}}||<style="width: 90%; border: none; -moz-border-radius-topright: 15px;-moz-border-radius-bottomright: 15px; text-align: left; font-size: 1.5em; background-color: #F1F1DD;" >'''BugSquad Frequently Asked Questions'''||
+ Welcome to the [[https://wiki.ubuntu.com/BugSquad|Bug Squad]] FAQ!
+
- Welcome to the [[https://wiki.ubuntu.com/BugSquad|BugSquad]] FAQ! The aim of this page is to provide an up-to-date list of common questions that we get about the [[BugSquad/|BugSquad]] project. We encourage you to update this document when something is missing so it becomes a core source of information for the project.
+ The aim of this page is to provide an up-to-date list of common questions that we get about the [[BugSquad|Bug Squad]] project. We encourage you to update this document when something is missing so it becomes a core source of information for the project.
= General Questions =
- == How do I start to Triage a bug ? ==
+ == How do I start to Triage a bug? ==
We recommend to every new triager to read our [[https://wiki.ubuntu.com/Bugs/HowToTriage|Triage Guide]] and to raise any questions in the [[irc://irc.freenode.org/#ubuntu-bugs|#ubuntu-bugs]] channel on [[IRC|IRC]].
From brian at ubuntu.com Tue Nov 15 19:44:52 2011
From: brian at ubuntu.com (Brian Murray)
Date: Tue, 15 Nov 2011 11:44:52 -0800
Subject: Bugs without a package
Message-ID: <20111115194452.GH8364@murraytwins.com>
In an attempt to deal with bugs without a package in an automated
fashion I currently have the Ubuntu Foundations Bug Bot commenting on
them regarding the importance of reporting a bug about a package and
pointing them at a wiki page regarding determining the right package for
a bug report.
Right now I'm trying to run it as an experiment and get an idea of what
happens when bug reporters are provided with this information, however a
lot of the time a triager ends up assigning the bug to a package for the
reporter. While this is great and I really appreciate it, I'd have more
data if you were to refrain from assigning no package bug reports to a
package if the Ubuntu Foundations Bug Bot has commented on them - at
least for a couple of days so we can see if the reporter responds.
Thanks in advance!
--
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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111115/4d8d644d/attachment.sig>
From lukescharf at clusterbee.net Tue Nov 15 20:26:31 2011
From: lukescharf at clusterbee.net (Luke Scharf)
Date: Tue, 15 Nov 2011 14:26:31 -0600
Subject: List of untriaged bugs?
Message-ID: <4EC2CAF7.50601@clusterbee.net>
I'm new to the Bug Squad, and looking for a real-time list of untriaged
bugs.
I've started pulling bug announcements in to Thunderbird via RSS, but
since the time I can devote to it is spotty, and the state RSS feed in
my reader doesn't really reflect the current state of the bug database.
Is there a web-based page where I can browse bugs that need attention in
their current state?
Thanks,
-Luke
From daniel.manrique at canonical.com Tue Nov 15 20:32:53 2011
From: daniel.manrique at canonical.com (Daniel Manrique)
Date: Tue, 15 Nov 2011 15:32:53 -0500
Subject: List of untriaged bugs?
In-Reply-To: <4EC2CAF7.50601@clusterbee.net>
References: <4EC2CAF7.50601@clusterbee.net>
Message-ID: <4EC2CC75.407@canonical.com>
On 11-11-15 03:26 PM, Luke Scharf wrote:
> I'm new to the Bug Squad, and looking for a real-time list of untriaged
> bugs.
>
> I've started pulling bug announcements in to Thunderbird via RSS, but
> since the time I can devote to it is spotty, and the state RSS feed in
> my reader doesn't really reflect the current state of the bug database.
>
> Is there a web-based page where I can browse bugs that need attention in
> their current state?
>
> Thanks,
> -Luke
>
>
Depends a bit on what you want to focus on at the moment. For new bugs in Ubuntu
(status New, sorted newest to oldest) I find this search is a good starting point:
https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
You can use the search field at the top of that page, along with the status
selector and the "advanced" search link to fine-tune your search to what you
want to work on (perhaps Incomplete bugs, bugs with specific tags, etc).
The produced search URLs are usually bookmarkable so you can do that and come
back to the same bug list later if you want.
- Daniel
From dlbike76 at gmail.com Tue Nov 15 20:49:24 2011
From: dlbike76 at gmail.com (David C)
Date: Tue, 15 Nov 2011 15:49:24 -0500
Subject: Bugs without a package
In-Reply-To: <20111115194452.GH8364@murraytwins.com>
References: <20111115194452.GH8364@murraytwins.com>
Message-ID: <CAF25DqdGGxhiyf+jWt6P903Q7+TcjrLnCfLbURX+aYGX+9cMaA@mail.gmail.com>
Brian,
Is it possible to have the Ubuntu Foundations Bug Bot add a tag to the
bug report as well. The tag would make it easy to exclude these bugs
from searches.
Thanks,
David
On Tue, Nov 15, 2011 at 2:44 PM, Brian Murray <brian at ubuntu.com> wrote:
> In an attempt to deal with bugs without a package in an automated
> fashion I currently have the Ubuntu Foundations Bug Bot commenting on
> them regarding the importance of reporting a bug about a package and
> pointing them at a wiki page regarding determining the right package for
> a bug report.
>
> Right now I'm trying to run it as an experiment and get an idea of what
> happens when bug reporters are provided with this information, however a
> lot of the time a triager ends up assigning the bug to a package for the
> reporter. Â While this is great and I really appreciate it, I'd have more
> data if you were to refrain from assigning no package bug reports to a
> package if the Ubuntu Foundations Bug Bot has commented on them - at
> least for a couple of days so we can see if the reporter responds.
>
> Thanks in advance!
>
> --
> Brian Murray
> Ubuntu Bug Master
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAk7CwTMACgkQDTAwc5ER+zVFHwCghvGrGz9d5SY7i/9lyAFIy2+k
> EZAAoLscOrziQ9tuhFZRo3dDAn26Xvvq
> =iMIm
> -----END PGP SIGNATURE-----
>
> --
> Ubuntu-bugsquad mailing list
> Ubuntu-bugsquad at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
>
>
From brian at ubuntu.com Tue Nov 15 21:17:56 2011
From: brian at ubuntu.com (Brian Murray)
Date: Tue, 15 Nov 2011 13:17:56 -0800
Subject: Bugs without a package
In-Reply-To: <CAF25DqdGGxhiyf+jWt6P903Q7+TcjrLnCfLbURX+aYGX+9cMaA@mail.gmail.com>
References: <20111115194452.GH8364@murraytwins.com>
<CAF25DqdGGxhiyf+jWt6P903Q7+TcjrLnCfLbURX+aYGX+9cMaA@mail.gmail.com>
Message-ID: <20111115211756.GJ8364@murraytwins.com>
On Tue, Nov 15, 2011 at 03:49:24PM -0500, David C wrote:
> Brian,
>
> Is it possible to have the Ubuntu Foundations Bug Bot add a tag to the
> bug report as well. The tag would make it easy to exclude these bugs
> from searches.
Yes, that'd be quite smart - thanks for the idea. They will be tagged
'bot-comment'.
--
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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111115/16c04692/attachment.sig>
From lukescharf at clusterbee.net Wed Nov 16 04:54:38 2011
From: lukescharf at clusterbee.net (Luke Scharf)
Date: Tue, 15 Nov 2011 22:54:38 -0600
Subject: List of untriaged bugs?
In-Reply-To: <4EC2CC75.407@canonical.com>
References: <4EC2CAF7.50601@clusterbee.net> <4EC2CC75.407@canonical.com>
Message-ID: <4EC3420E.7090801@clusterbee.net>
On 11/15/2011 02:32 PM, Daniel Manrique wrote:
> On 11-11-15 03:26 PM, Luke Scharf wrote:
>> Is there a web-based page where I can browse bugs that need attention and
>> their current state?
>>
> Depends a bit on what you want to focus on at the moment. For new bugs in Ubuntu
> (status New, sorted newest to oldest) I find this search is a good starting point:
>
> https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
>
> You can use the search field at the top of that page, along with the status
> selector and the "advanced" search link to fine-tune your search to what you
> want to work on (perhaps Incomplete bugs, bugs with specific tags, etc).
>
> The produced search URLs are usually bookmarkable so you can do that and come
> back to the same bug list later if you want.
Cool -- thanks!
-Luke
From hggdh2 at ubuntu.com Thu Nov 17 14:39:52 2011
From: hggdh2 at ubuntu.com (C de-Avillez)
Date: Thu, 17 Nov 2011 08:39:52 -0600
Subject: List of untriaged bugs?
In-Reply-To: <4EC2CAF7.50601@clusterbee.net>
References: <4EC2CAF7.50601@clusterbee.net>
Message-ID: <4EC51CB8.60300@ubuntu.com>
On 15/11/11 14:26, Luke Scharf wrote:
> I'm new to the Bug Squad, and looking for a real-time list of untriaged
> bugs.
>
> I've started pulling bug announcements in to Thunderbird via RSS, but
> since the time I can devote to it is spotty, and the state RSS feed in
> my reader doesn't really reflect the current state of the bug database.
>
> Is there a web-based page where I can browse bugs that need attention in
> their current state?
>
Well. There is Harvest [1]; it proposes to give you a pre-selected
view of bugs, for example desktop bugs that are tagged
bugpatterns-needed. We -- to be precise, super-Daniel -- are
planning on expanding it this cycle. But it is fully functional,
although the interface sort of sucks.
..C..
[1] http://harvest.ubuntu.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111117/567db32f/attachment.sig>
From noreply at ubuntu.com Wed Nov 16 23:35:44 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 16 Nov 2011 23:35:44 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/OneiricWorkflowSurveyResult?=
=?utf-8?q?s=22_by_allison?=
Message-ID: <20111116233544.6146.85839@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/OneiricWorkflowSurveyResults" page has been changed by allison:
http://wiki.ubuntu.com/Bugs/OneiricWorkflowSurveyResults
New page:
The results of the bug workflow survey, run during the Oneiric cycle, in both a pretty graphical summary (PDF) and the raw result data (ODS).
From noreply at ubuntu.com Wed Nov 16 23:39:35 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 16 Nov 2011 23:39:35 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/OneiricWorkflowSurveyResult?=
=?utf-8?q?s=22_by_allison?=
Message-ID: <20111116233935.6125.56248@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/OneiricWorkflowSurveyResults" page has been changed by allison:
http://wiki.ubuntu.com/Bugs/OneiricWorkflowSurveyResults?action=diff&rev1=1&rev2=2
- The results of the bug workflow survey, run during the Oneiric cycle, in both a pretty graphical summary (PDF) and the raw result data (ODS).
+ The results of the bug workflow survey, run during the Oneiric cycle, in both a pretty graphical summary ([[attachment:bug_workflow_survey_results.pdf|PDF]]) and the raw result data ([[attachment:bug_workflow_survey_results.ods|ODS]]).
From noreply at ubuntu.com Wed Nov 16 23:37:10 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 16 Nov 2011 23:37:10 -0000
Subject: =?utf-8?q?New_attachment_added_to_page_Bugs/OneiricWorkflowSurveyResults_?=
=?utf-8?q?on_Ubuntu_Wiki?=
Message-ID: <20111116233710.6146.83497@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page "Bugs/OneiricWorkflowSurveyResults" for change notification. An attachment has been added to that page by allison. Following detailed information is available:
Attachment name: bug_workflow_survey_results.ods
Attachment size: 46154
Attachment link: http://wiki.ubuntu.com/Bugs/OneiricWorkflowSurveyResults?action=AttachFile&do=get&target=bug_workflow_survey_results.ods
Page link: http://wiki.ubuntu.com/Bugs/OneiricWorkflowSurveyResults
From noreply at ubuntu.com Sat Nov 19 14:56:24 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Sat, 19 Nov 2011 14:56:24 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?=
=?utf-8?q?till-kamppeter?=
Message-ID: <20111119145624.5779.83142@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "DebuggingPrintingProblems" page has been changed by till-kamppeter:
http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=62&rev2=63
= CUPS error_log =
This is a file where CUPS writes information about what it is doing. Almost all printing problems can be diagnosed from the error log, so it is the first place to look to start solving problems. To be useful, you must change the logging level: <<BR>>
- 1. In Ubuntu Gutsy or newer, select "System" -> "Administration" -> "Printing" in the main menu of your desktop. The printer setup tool system-config-printer will open. Select "Server Settings" in the list on the left. Then check the checkbox "Save debugging information for troubleshooting" and click "Apply".
+ 1. In Ubuntu Gutsy or newer, select "System" -> "Administration" -> "Printing" in the main menu of your desktop and in Oneiric or newer with Unity desktop click the gear icon at the upper right (the one also used to log out) and in the menu showing up then, click "Printer". The printer setup tool system-config-printer will open. Select "Server Settings" in the list on the left or in newer versions with the printers showing as icons choose erver" in the main menu and then "Settings". Note that the main menu will be in the bar at the top of the screen if Oneiric (or newer) with Unity is used. There it only appears if you move the mouse into the top bar. Then check the checkbox "Save debugging information for troubleshooting" and click "Apply".
2. In all Ubuntu flavors (also Kubuntu and server editions) you can run <<BR>> {{{$ cupsctl LogLevel=debug}}} <<BR>> to activate debug logging.
3. In Karmic and later (CUPS 1.4.x) there is an automatic debug logging only for failed print jobs. So if you problem was a failed print job, the error_log can already contain the desired information. Unfortunately, only 200 debug message lines get logged per failed job. Run the command <<BR>> {{{$ cupsctl LogDebugHistory=999999}}} <<BR>> for practically unlimited logging of failed jobs.
4. In older versions of all flavors, where there is not yet a "cupsctl" command, edit the file {{{/etc/cups/cupsd.conf}}}, find the line '''Log``Level ...''' and change it to '''Log``Level debug''', save the file. Then restart CUPS: <<BR>> {{{$ sudo /etc/init.d/cupsys restart}}}
@@ -59, +59 @@
= Troubleshooting Wizard =
- There is a troubleshooting wizard in system-config-printer (System -> Administration -> Printing). You find it by in the "Help" menu of system-config-printer. It produces a text file with a lot of useful information to attach to bug reports. Follow the instructions of the wizard. If you reach the test page step, you can either click the button to print the test page or you can print a job to the selected printer from any application or from the command line. The job will be shown in the integrated job viewer. Wait until it completes or goes into "Stopped" state. ONLY THEN AND NOT BEFORE mark the checkbox at the job, answer whether the job got printed correctly, and click "Forward". After that the file will get generated. Save it and attach it to your bug report.
+ There is a troubleshooting wizard in system-config-printer (System -> Administration -> Printing in GNOME classic, Gear icon at the upper right of the screen -> Printers in Unity). You find it by in the "Help" menu of system-config-printer. It produces a text file with a lot of useful information to attach to bug reports. Follow the instructions of the wizard. If you reach the test page step, you can either click the button to print the test page or you can print a job to the selected printer from any application or from the command line. The job will be shown in the integrated job viewer. Wait until it completes or goes into "Stopped" state. ONLY THEN AND NOT BEFORE mark the checkbox at the job, answer whether the job got printed correctly, and click "Forward". After that the file will get generated. Save it and attach it to your bug report.
= Print Error pop-up window =
@@ -72, +72 @@
Often it is needed to find out what actually got sent to the printer in order to determine whether the problem is caused by the application or by the printing subsystem. For that it is the easiest way to capture the job data from the application so that it can analyzed whether it is already broken or not. To do so, follow these steps: <<BR>>
1. Clear the print queues from old jobs. Either use the job viewer or run the command <<BR>> {{{$ cancel -a}}} <<BR>> in a terminal window.
- 2. Disable the print queue with which you have the problem. Use system-config-printer (System -> Administration -> Printing), right-click the appropriate printer icon, and click "Enabled" in the pop-up menu, so that the check mark disappears or run the command <<BR>> {{{$ cupsdisable <PRINTER>}}} <<BR>> in a terminal window (Replace "<PRINTER>" by the name of the print queue). This makes jobs staying in the queue so that you can capture them.
+ 2. Disable the print queue with which you have the problem. Use system-config-printer (System -> Administration -> Printing in GNOME classic, Gear icon at the upper right of the screen -> Printers in Unity), right-click the appropriate printer icon, and click "Enabled" in the pop-up menu, so that the check mark disappears or run the command <<BR>> {{{$ cupsdisable <PRINTER>}}} <<BR>> in a terminal window (Replace "<PRINTER>" by the name of the print queue). This makes jobs staying in the queue so that you can capture them.
3. Now print the job from your application. When the application has finished sending the job, check via the job viewer or the command <<BR>> {{{$ lpstat -o}}} <<BR>> whether it is in the queue.
4. Display the content of CUPS' spool directory using the command <<BR>> {{{$ sudo ls -1 /var/spool/cups}}} <<BR>> (Enter your password when getting asked).
5. There should be exactly one file beginning with a "d". Copy this file to your home directory: <<BR>> {{{$ sudo cp /var/spool/cups/d... ~/printout}}} <<BR>> {{{$ sudo chmod 777 ~/printout}}}
From REDACTED at example.com Sat Nov 19 21:45:56 2011
From: REDACTED at example.com (REDACTED)
Date: Sat, 19 Nov 2011 22:45:56 +0100
Subject: My membership in Ubuntu Bugsquad
Message-ID: <CAE7pT7BZ2H+MTXZOdbAoOF7NMfDcbkHkVtJA4jK3hN4d13U5FQ@mail.gmail.com>
Hi Bugsquad,
My membership there is about to expire...
Sorry, I haven't been very active in helping with bugs.
I really lack free time :(
Maybe I will re-apply for membership other time, when I will have more free
time...
Thanks and sorry, REDACTED.
--
https://launchpad.net/~redacted
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111119/8041ad76/attachment.html>
From brian at ubuntu.com Tue Nov 22 21:37:18 2011
From: brian at ubuntu.com (Brian Murray)
Date: Tue, 22 Nov 2011 13:37:18 -0800
Subject: Reviewing needs-packaging bug reports
Message-ID: <20111122213718.GX8364@murraytwins.com>
I came across a needs-packaging bug report[1], these are requests to get
software added to Ubuntu, and quickly discovered that it was Fix
Released. Here is what I did to check and see whether or not the
software was in Ubuntu.
I used 'apt-cache search opensync' to look for a package that would
meet the bug reporter's need. I thought I had a good match in
synce-sync-engine so used 'apt-cache show synce-sync-engine' to show the
package description. I then used 'rmadison synce-sync-engine' to verify
what releases of Ubuntu the package is in.
Generally, the needs-packaging bug reports name the software so it is
easier to search for a package with a similar name. Reviewing the
needs-packaging bug reports is a pretty easy thing to do and as there
are more than 2000 bug reports[2] it would be a huge help.
If you have any questions feel free to ask in #ubuntu-bugs.
[1] http://launchpad.net/bugs/146588
[2] http://bit.ly/v5VGtD
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: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111122/cba4a149/attachment.sig>
From gema.gomez-solano at canonical.com Wed Nov 23 18:44:56 2011
From: gema.gomez-solano at canonical.com (Gema Gomez)
Date: Wed, 23 Nov 2011 18:44:56 +0000
Subject: QA Team Meeting and Bugs Meeting split from next week
Message-ID: <4ECD3F28.5090708@canonical.com>
Dear all,
in an attempt to get more involvement from the community in
*bug analysis and triaging* and *quality assurance and testing*, the
BugSquad and QA Platform Teams have decided to split the Wed 18:00 GMT
Ubuntu QA Team Meeting in two separate meetings with separate objectives.
Since we are going to be putting a lot of effort this cycle into
ensuring testing and bug triaging are done better and we are going to be
contributing in different ways to improving the quality of Ubuntu, we've
decided to schedule two meetings so that people interested in bug
triaging do not need to hear all about the testing and vice versa.
Having said that, we are aware that some contributors are interested in
the two areas, so we've scheduled the new QA Team meeting one hour
earlier than the Bug Squad meeting, so that if someone wishes so, they
can attend both without too much disruption.
Please, for further information keep an eye on:
* https://wiki.ubuntu.com/QATeam/Meetings - Wed 17:00 GMT
*Focus*: QA platform activities, calls for testing, community
feedback, etc.
*Who should attend*: Anyone interested in contributing doing testing
for Ubuntu is welcome to attend and start sharing their views,
contributing. We'll make sure all the efforts count towards the quality
of the coming release.
* https://wiki.ubuntu.com/BugSquad/Meetings - Wed 18:00 GMT
*Focus*: Bug triaging, mentoring of new members, ongoing activities
discussion, etc.
*Who should attend*: Anyone interested in bug triaging, bug
management, bug metrics and classification of bugs.
Next week we will be discussing the new agendas and agreeing on a new
format that makes sense. Pedro will be chairing the Bugs meeting and I
will be chairing the QA Team meeting, we hope we see you all there!
The Ubuntu Fridge Calendar, already has the schedule information of the
meetings from next week onwards: http://fridge.ubuntu.com/calendars/fridge/
Best Regards,
Gema
--
Gema Gomez-Solano <gema.gomez-solano at canonical.com>
QA Team
Canonical Ltd. http://www.canonical.com
From dan at canonical.com Thu Nov 24 15:53:50 2011
From: dan at canonical.com (Dan Harrop-Griffiths)
Date: Thu, 24 Nov 2011 15:53:50 +0000
Subject: Beta feature: Customisable bug listings
In-Reply-To: <CABSaz1a8HxegoGYf_rfbnt35jy1-PqY90BUh0GcGvk1Wj02eTg@mail.gmail.com>
References: <CABSaz1a8HxegoGYf_rfbnt35jy1-PqY90BUh0GcGvk1Wj02eTg@mail.gmail.com>
Message-ID: <CABSaz1YVMKQSZ58eTPHEf0ddVjEr9bicux5Wai1MRhw0evttFg@mail.gmail.com>
Hello,
We've just launched our new customisable bug listings into beta.
If you're in the Launchpad Beta Testers team [1] bug listings now have:
 - a new, clearer, design
 - easy re-sorting without having to reload the page
 - customisable information: you get to choose what data you see in
bug listings.
Please let us know how you get on with the new bug listings.
You can report bugs in the usual place [2] or join us on the
launchpad-users mailing list [3].
Cheers!
Dan HG
Usability & Communications Specialist
Launchpad Team
1. https://launchpad.net/~launchpad-beta-testers
2. https://bugs.launchpad.net/launchpad/+filebug
3. https://launchpad.net/~launchpad-users
From bkerensa at ubuntu.com Sun Nov 27 22:37:53 2011
From: bkerensa at ubuntu.com (Benjamin Kerensa)
Date: Sun, 27 Nov 2011 14:37:53 -0800
Subject: Ubuntu Mentors for Western Oregon University
Message-ID: <CAGOdq5=pJ0k6Og9dF=CvCkrt+4Y_avoK2YuC4-P0+NaguZmB7g@mail.gmail.com>
Hello All,
In an effort to support FOSS/Ubuntu in Academia Becka Morgan a Professor at
WOU has reached out to Ubuntu Oregon. She is focusing a class around
contributing to the Ubuntu Community and will need mentors to mentor the 28
students in this class there will be 14 students in each 4 week session and
students are expected to meet with a mentor once per week for the duration
(I believe there are two four week sessions since it is 28 students total)
anyways the areas I need mentors in are:
* Bug Triage
* Documentation Contributing
* Bug Fixing Processes
I will need mentors who have a strong understanding in one of the above
areas and I personally will be mentoring for Bug Triaging and Documentation
but we will need plenty more due to the volume of students.
Mentoring will be performed virtually through Skype, IM and E-mail.
If you are interested in being a mentor please fill out the following form:
https://docs.google.com/spreadsheet/viewform?formkey=dFBtb21RSGdPSWNHTHpYU3FfbzlEMEE6MQ
I hope to have 10-20 mentors and I understand I may not find them all
within the LoCo so I will be reaching out to other LoCo's and likely
various teams to meet the quota and if you know someone please pass this
e-mail to them so I can get this important project sailing smoothly.
--
Benjamin Kerensa
Team Lead, Ubuntu Oregon
bkerensa at ubuntu.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111127/77f18ca1/attachment.html>
From noreply at ubuntu.com Sat Nov 26 22:15:23 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Sat, 26 Nov 2011 22:15:23 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=22_by_chrisccou?=
=?utf-8?q?lson?=
Message-ID: <20111126221523.8678.82817@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "MozillaTeam/Bugs" page has been changed by chrisccoulson:
http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=70&rev2=71
2. Now ~/tmp/gdb-firefox.txt will contain the info we need to initially process your crash bug. So, please attach that file to your bug report.
Please use the same steps for Thunderbird, but replacing "firefox" with "thunderbird" instead.
+
+ == "Secure Connection Failed" errors ==
+
+ If you see a warning with the title "Secure Connection Failed" and the text "The certificate is not trusted because the issuer certificate is unknown (Error code: sec_error_unknown_issuer)" when visiting a website with a https URL, then this means that Firefox is not able to chain the websites certificate to a trusted CA.
+
+ This could be a problem with the server, or it could be that somebody is impersonating the server. It is generally '''not a bug with Firefox'''
+
+ If a site provides a certificate signed by an intermediate CA (one which is not in the root store, but with a trust chain to an existing root), the server must provide the intermediate certificates. Failure to do this will result in this error.
+
+ === For certificates signed by RapidSSL (Geotrust) ===
+
+ On December 9, 2010, Geotrust updated their certificate signing process and all certificates issued after this date require the installation of the RapidSSL intermediate on the server. Some sites forget to do this, which results in this error. This is a '''bug with the website'''
+
+ See [[http://blog.clickssl.com/2010/12/rapidssl-error-on-firefox-this-connection-is-untrusted/|http://blog.clickssl.com/2010/12/rapidssl-error-on-firefox-this-connection-is-untrusted/]]
+
+ [[https://knowledge.geotrust.com/support/knowledge-base/index?page=content&actp=CROSSLINK&id=SO9557|This]] online validation tool can tell you which intermediate a server is missing
+
+ === Requests for inclusion of new CA's ===
+
+ In some cases when experiencing "unknown issuer" errors when visiting certain sites, it may be tempting to open a bug report to request that the issuer CA is added to the root store shipped with Firefox. Doing this would defeat the whole trust system. There is a '''well defined''' process for CA's to request that their certificate(s) be added and be shipped with Firefox. Details of this can be found at [[https://wiki.mozilla.org/CA:How_to_apply|https://wiki.mozilla.org/CA:How_to_apply]]
+
+ '''We will not bypass this process under any circumstances''', so please '''do not''' make these types of requests. Requests of this type '''will be rejected'''.
== Problems launching external applications ==
From hggdh2 at ubuntu.com Mon Nov 28 21:58:35 2011
From: hggdh2 at ubuntu.com (C de-Avillez)
Date: Mon, 28 Nov 2011 15:58:35 -0600
Subject: The BugSquad mentorship programme is ending
Message-ID: <4ED4040B.7090606@ubuntu.com>
Hello,
We discussed the BugSquad mentorship programme during UDS [1];
generically, we perceive it as not working as intended. The reasons
are varied but, on the whole, they show the mentees and the mentors
disconnected on expectations, the most prominent being:
* mentees expect a continuous hands-on approach from the mentors
* mentors expect to be contacted via IRC or the ML
In its previous incarnation, the mentorship programme was set
joining a small group of mentees with each available mentor; this
approach also did not work, with most mentees lagging behind.
As such, we decided to end the programme, and revert to the previous
state of affairs regarding bug triage work:
* the #ubuntu-bugs IRC channel on irc.ubuntu.com is, still, the
primary contact venue for people interested in contributing on bug
triage; questions asked there should be responded to in a timely
manner [3].
* the Ubuntu Bug Squad mailing list [2] is also a primary contact;
of course, the ML does not allow for an interactive approach -- for
this, the IRC channel is preferred. Bug triagers are extremely
encouraged to subscribe to this list.
Of course, we look forward to contributors (hell, we *depend* on
them!). Being present on the IRC channel is a very good way of
contacting us, and making you -- the beginner on Ubuntu bug triaging
-- known to us.
I am sorry this programme did not work, and I hope the current
mentees will keep on helping making Ubuntu, and free software in
general, better and better.
..C..
[1]
https://blueprints.launchpad.net/ubuntu/+spec/other-p-bugsquad-mentoring
[2] see http://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
[3] well, please keep in mind that we also have a life ;-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111128/129e283e/attachment.sig>
From noreply at ubuntu.com Mon Nov 28 18:05:43 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Mon, 28 Nov 2011 18:05:43 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUdev=22_by_serge-hallyn?=
Message-ID: <20111128180543.15919.28162@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "DebuggingUdev" page has been changed by serge-hallyn:
http://wiki.ubuntu.com/DebuggingUdev?action=diff&rev1=8&rev2=9
* To see the actions udevd is taking, you can run it in verbose debug mode:
* sudo pkill udevd
* sudo udevd --debug-trace --verbose --suppress-syslog
+ * To get more debug info from udev,
+ * edit /usr/share/initramfs-tools/scripts/init-top/udev, and change the line starting udev by adding --debug and sending stdout and stderr into a file under/dev/.initramfs. For instance:
+
+ /sbin/udevd --daemon --debug --resolve-names=never > /dev/.initramfs/udev.out 2>&1
+ * then run sudo update-initramfs -k all -u
+ * After reboot, /dev/.initramfs/udev.out will have the udev debug info.
+
= Known bugs =
From ubuntu at nailor.devzero.de Tue Nov 29 23:15:29 2011
From: ubuntu at nailor.devzero.de (Michael Nagel)
Date: Wed, 30 Nov 2011 00:15:29 +0100
Subject: Simple Scan triaging
Message-ID: <4ED56791.40600@nailor.devzero.de>
Hi there,
I am writing to this list because I would like to hear your opinion regarding the following problem:
I am triaging the bugs filed against the simple-scan package and the Simple Scan project itself. There are a lot of bug reports like [1] (randomly picked that one) where the hardware is not supported properly. Either it is not supported at all, or some features (ADF, ...) are missing. These bug reports do not bring forward the development of Simple Scan, but on the contrary clog the bug lists and slow down development progress. Keeping them is thus not worthwile in my opinion. (Note: In general I think not all bug reports should be accepted/kept. I prefer a deliberate decision with explicit downsides/compromises to the implicit decision to do nothing and avoid all downsides -- you do not get upsides that way, either.)
Different stakeholders are involved in these bug, namely the original reporter, the Simple Scan developers, the developers of SANE / other involved software, and other users owning the same hardware. Keeping these reports open helps none of them and harms some of them. The following approach would be much better for everyone in my opinion:
1) closing such bugs in a timely manner
2) pointing to a wiki where general tips about scanners can be much better maintained. might be an adapted version of [2]
3) structured information about what hardware works with what settings should be kept in a database (in the weak meaning of the word, might e.g. be another wiki page). might just be [3]
- The original reporter benefits from 1) because he no longer is ignored for some years. The reporter hopefully benefits from 2+3) as there is the chance (s)he gets the scanner to work.
- The Simple Scan developers benefit from happy users and from more helpful bug lists, letting them concentrate on the real issues in Simple Scan.
- SANE / other developers benefit from 3) because they get much more concise and structured information. See the following section about forwarding bugs.
- Other hardware owners profit from the database as well, because they can easily find out what hardware can be recommended to buy (use case 1) and what can be expected from a given piece of hardware (use case 2a) and how to get the most out of a given piece of hardware (use case 2b).
About forwarding such bug reports to e.g. sane-backends: I think it is monkey business, like some European countries moving around atomic waste that nobody wants but that does not vanish. It would just create the same situation we have with simple-scan now for sane-backends in some time. Someone has to accept responsibility, make the though decision (see above) and "solve" the issue.
Additionally, these bugs are often reported by new users, very vague and to not include enough technical detail. I am sure there has been some discussion how to handle that kind of bug reports, as Ubuntu continues to attract more and more non-technical users that cannot and/or do not want to contribute low-level.
A pointer to such discussion would be very welcome!
>From my experience those users are mostly thankful for some timely, helpful and honest reply, even if it boils down to "yes, we know, but sadly it will not be fixed soon -- if you need a solution right now and you cannot code: I am sorry to tell you, but your only option is to buy one of the better supported scanners. More info: see wiki: ..."
Once again: if the bug report is just another data point saying "does not work" it is better off in the device database.
Then, even trickier, are the crashes of Simple Scan (or more likely: SANE/something down the chain) that depend on the use of certain hardware (with bad drivers). To be honest, nobody will look into these issues because of a bug report. Either someone knowledgeable will look into such an issue because he is personally affected or because someone (s)he knows is affected.
But the mere statement that Simple Scan crashed (typically via an apport report) will once again lead to rotting/stale bug reports, where developers benefit from just deleting it and non-technical users benefit most from a timely pointer to the wiki and the database where they can get a tip how to maybe get it working. One prominent tip should read: "If you need a solution right now and you cannot code: I am sorry to tell you, but your only option is to buy one of the better supported scanners. More info: see wiki: ..."
What do you think about the suggested approach? Do you have experience with similar cases?
Best Regards
Michael
PS: over all that closing of bug reports we should not forget that:
- of course there are some high quality bugs related to scanner hardware, that can help improving the situation. I do not want to blindly close all bugs.
- the general situation regarding hardware support for scanners is somewhat sad :(
Context: Simple Scan internal discussion of this topic: https://bugs.launchpad.net/simple-scan/+bug/896729 (case "c)" is what this mail is about)
[1] https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/674817
[2] https://help.ubuntu.com/community/ScanningHowTo
[3] https://wiki.ubuntu.com/HardwareSupportComponentsScanners
From cyan.spam at gmail.com Wed Nov 30 00:33:17 2011
From: cyan.spam at gmail.com (David Tombs)
Date: Tue, 29 Nov 2011 19:33:17 -0500
Subject: Simple Scan triaging
In-Reply-To: <4ED56791.40600@nailor.devzero.de>
References: <4ED56791.40600@nailor.devzero.de>
Message-ID: <4ED579CD.9020408@gmail.com>
On 11/29/2011 06:15 PM, Michael Nagel wrote:
> Hi there,
>
> I am writing to this list because I would like to hear your opinion regarding the following problem:
>
> I am triaging the bugs filed against the simple-scan package and the Simple Scan project itself. There are a lot of bug reports like [1] (randomly picked that one) where the hardware is not supported properly. Either it is not supported at all, or some features (ADF, ...) are missing. These bug reports do not bring forward the development of Simple Scan, but on the contrary clog the bug lists and slow down development progress. Keeping them is thus not worthwile in my opinion. (Note: In general I think not all bug reports should be accepted/kept. I prefer a deliberate decision with explicit downsides/compromises to the implicit decision to do nothing and avoid all downsides -- you do not get upsides that way, either.)
>
> Different stakeholders are involved in these bug, namely the original reporter, the Simple Scan developers, the developers of SANE / other involved software, and other users owning the same hardware. Keeping these reports open helps none of them and harms some of them. The following approach would be much better for everyone in my opinion:
>
> 1) closing such bugs in a timely manner
> 2) pointing to a wiki where general tips about scanners can be much better maintained. might be an adapted version of [2]
> 3) structured information about what hardware works with what settings should be kept in a database (in the weak meaning of the word, might e.g. be another wiki page). might just be [3]
>
> - The original reporter benefits from 1) because he no longer is ignored for some years. The reporter hopefully benefits from 2+3) as there is the chance (s)he gets the scanner to work.
> - The Simple Scan developers benefit from happy users and from more helpful bug lists, letting them concentrate on the real issues in Simple Scan.
> - SANE / other developers benefit from 3) because they get much more concise and structured information. See the following section about forwarding bugs.
> - Other hardware owners profit from the database as well, because they can easily find out what hardware can be recommended to buy (use case 1) and what can be expected from a given piece of hardware (use case 2a) and how to get the most out of a given piece of hardware (use case 2b).
>
> About forwarding such bug reports to e.g. sane-backends: I think it is monkey business, like some European countries moving around atomic waste that nobody wants but that does not vanish. It would just create the same situation we have with simple-scan now for sane-backends in some time. Someone has to accept responsibility, make the though decision (see above) and "solve" the issue.
>
> Additionally, these bugs are often reported by new users, very vague and to not include enough technical detail. I am sure there has been some discussion how to handle that kind of bug reports, as Ubuntu continues to attract more and more non-technical users that cannot and/or do not want to contribute low-level.
> A pointer to such discussion would be very welcome!
>>From my experience those users are mostly thankful for some timely, helpful and honest reply, even if it boils down to "yes, we know, but sadly it will not be fixed soon -- if you need a solution right now and you cannot code: I am sorry to tell you, but your only option is to buy one of the better supported scanners. More info: see wiki: ..."
> Once again: if the bug report is just another data point saying "does not work" it is better off in the device database.
>
>
>
> Then, even trickier, are the crashes of Simple Scan (or more likely: SANE/something down the chain) that depend on the use of certain hardware (with bad drivers). To be honest, nobody will look into these issues because of a bug report. Either someone knowledgeable will look into such an issue because he is personally affected or because someone (s)he knows is affected.
> But the mere statement that Simple Scan crashed (typically via an apport report) will once again lead to rotting/stale bug reports, where developers benefit from just deleting it and non-technical users benefit most from a timely pointer to the wiki and the database where they can get a tip how to maybe get it working. One prominent tip should read: "If you need a solution right now and you cannot code: I am sorry to tell you, but your only option is to buy one of the better supported scanners. More info: see wiki: ..."
>
>
>
> What do you think about the suggested approach? Do you have experience with similar cases?
>
> Best Regards
> Michael
>
> PS: over all that closing of bug reports we should not forget that:
> - of course there are some high quality bugs related to scanner hardware, that can help improving the situation. I do not want to blindly close all bugs.
> - the general situation regarding hardware support for scanners is somewhat sad :(
>
> Context: Simple Scan internal discussion of this topic: https://bugs.launchpad.net/simple-scan/+bug/896729 (case "c)" is what this mail is about)
> [1] https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/674817
> [2] https://help.ubuntu.com/community/ScanningHowTo
> [3] https://wiki.ubuntu.com/HardwareSupportComponentsScanners
>
Hi Michael,
I am not an expert triager, but I do agree with a lot of your points.
Good thinking.
For a small improvement, adding an "unsupported hardware" message to the
canned responses[1] (and Firefox extension) would certainly save some
time. Ideally, however, this canned response would be accompanied by a
standard triaging practice for unsupported hardware bugs but I am not
sure if that exists.
Thanks for the email,
David
From pedro at ubuntu.com Wed Nov 30 14:21:19 2011
From: pedro at ubuntu.com (Pedro Villavicencio)
Date: Wed, 30 Nov 2011 11:21:19 -0300
Subject: Bugs Meeting Today! Nov 30 2011 1800 UTC
Message-ID: <4ED63BDF.5070102@ubuntu.com>
Hello Folks,
Just a reminder that today we're having our first Bugs meeting since the
QA team was divided last week. The meeting focus is: Bug Triaging,
Mentoring of new members, ongoing activities discussions, etc. If
you're interested on Bug Triaging, bug Management, Bug Metrics, etc then
you should attend to it. Remember Today at 1800 UTC at #ubuntu-meeting .
The Agenda can be found at:
https://wiki.ubuntu.com/BugSquad/Meetings
Thanks and see you at the meeting.
Have a nice day,
pedro.
From pedro at ubuntu.com Wed Nov 30 18:49:46 2011
From: pedro at ubuntu.com (Pedro Villavicencio)
Date: Wed, 30 Nov 2011 15:49:46 -0300
Subject: Monthly BugSquad Meeting
Message-ID: <4ED67ACA.6080101@ubuntu.com>
Hello Folks,
As you might know, we used to have a Monthly BugSquad Meeting but since
the QA Team meeting was divided in two (Testing/Bugs), we think that's
the best thing to do is to remove that Monthly BugSquad Meeting and
include such topics into the Weekly Bugs Meeting which is going to
happen each Wednesday at 1800 UTC at #ubuntu-meeting, so if you have any
topics you'd like to discuss please add those to :
https://wiki.ubuntu.com/BugSquad/Meetings
Thanks for your time!.
pedro.