Release-1.5.4

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/trouble.doc b/doc/trouble.doc
index 060a19b..343404b 100644
--- a/doc/trouble.doc
+++ b/doc/trouble.doc
@@ -89,11 +89,11 @@ know why.
 Bugs are tracked in GNOME's <a href="http://bugzilla.gnome.org">bugzilla</a> database.
 Before submitting a 
 <a href="http://bugzilla.gnome.org/enter_bug.cgi?product=doxygen">new bug</a>,
-first 
-<a href="http://bugzilla.gnome.org/buglist.cgi?product=doxygen&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_status=VERIFIED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&namedcmd=gnome-libs+past+20+days&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query"> 
-check</a> if the same bug has already been submitted by others.
+first <a href="http://bugzilla.gnome.org/query.cgi?format=advanced&product=doxygen">search</a>
+through the database if the same bug has already been submitted by others (the doxygen
+product will be preselected).
 If you believe you have found a new bug, 
-please <a href="http://bugzilla.gnome.org/enter_bug.cgi?product=doxygen">file it</a>.
+please <a href="http://bugzilla.gnome.org/enter_bug.cgi?product=doxygen">report it</a>.
 
 If you are unsure whether or not something is a bug, please ask help
 on the <a href="http://sourceforge.net/mail/?group_id=5971">users mailing list</a> 
@@ -103,7 +103,7 @@ If you send only a (vague) description of a bug, you are usually not very
 helpful and it will cost me much more time to figure out what you mean. 
 In the worst-case your bug report may even be completely ignored by me, so
 always try to include the following information in your bug report: 
-- The version of doxygen you are using (for instance 1.2.4, use 
+- The version of doxygen you are using (for instance 1.5.3, use 
   <code>doxygen --version</code> if you are not sure).
 - The name and version number of your operating system (for instance 
   SuSE Linux 6.4)
@@ -112,14 +112,14 @@ always try to include the following information in your bug report:
   to keep it small (use <code>doxygen -s -u [configName]</code> to strip
   the comments from an existing config file). 
 - The easiest (and often the only) way for me to fix bugs is if you can 
-  send me a small example demonstrating the problem you have, so I can
+  attach a small example demonstrating the problem you have to the bug report, so I can
   reproduce it on my machine. Please make sure the example is valid
   source code (could potentially compile) and that the problem is really 
   captured by the example (I often get examples that do not trigger the 
   actual bug!). If you intend to send more than one file please zip or tar
   the files together into a single file for easier processing.
-  When reporting a new bug you'll get a chance to attach a file to it 
-  immediately \e after opening the bug.
+  Note that when reporting a new bug you'll get a chance to attach a file to it 
+  only \e after submitting the initial bug description.
 
 You can (and are encouraged to) add a patch for a bug. If you do so
 please use PATCH as a keyword in the bug entry form.