[Reportbug-commits] [SCM] Reportbug - reports bugs in the Debian distribution branch, master, updated. 4.9-55-ge09e19b

[Sandro Tosi]

The following commit has been merged in the master branch:
commit e09e19be33aadb0c6cde00691d0b573f6c478d33
Author: Sandro Tosi <morph at debian.org>
Date:   Tue Feb 9 13:40:58 2010 +0100

    clarified to not repot bugs against reportbug in case of GTK+ crashes

diff --git a/debian/changelog b/debian/changelog
index 9f2302d..881b9ab 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -15,8 +15,9 @@ reportbug (4.10.3) UNRELEASED; urgency=low
   * share/presubj
     - specified the pager exit key doesn't apply to GTK+ UI; thanks to Éric
       Araujo for the report; Closes: 568196
+    - clarified to not repot bugs against reportbug in case of GTK+ crashes
 
- -- Sandro Tosi <morph at debian.org>  Thu, 04 Feb 2010 07:19:32 +0100
+ -- Sandro Tosi <morph at debian.org>  Tue, 09 Feb 2010 13:40:32 +0100
 
 reportbug (4.10.2) unstable; urgency=low
 
diff --git a/share/presubj b/share/presubj
index cf43eab..0d6a593 100644
--- a/share/presubj
+++ b/share/presubj
@@ -31,5 +31,12 @@ REPORTING: It is useful to include the full transcript of reportbug
    (with text ui) output, so we can see what it's trying to do and
    provide a faster and more precise response.
 
+GTK+ UI: There are some situation when the GTK+ stack crashes,
+   reporting "Floating point exception" or GTK+ stack traces; those
+   are bugs in GTK+ or misconfigurations (for example, using 'testing'
+   suite can lead to such errors) on the current machine. Do nor
+   report bugs against reportbug in such situations but consult users
+   support forums.
+
 (You may need to press 'q' to exit your pager and continue using
 reportbug at this point. Doesn't apply to GTK+ UI.)

-- 
Reportbug - reports bugs in the Debian distribution