How to report a bug in KDE

  Send mail to [email protected], as described below.

  Please don't report several unrelated bugs - especially ones in
  different packages - in one message. Also, please don't mail your bug
  report to any mailing lists or recipients other than submit@bugs (for
  details of how to do this right, see below).

  Lists of currently-outstanding bugs are available on the World Wide
  Web and elsewhere - see other documents for details.

  You should put a pseudo-header at the start of the body of the
  message, with the Package: and Version: lines giving the name and
  version of the package which has the bug. (The pseudo-header fields
  must start at the very start of their lines, and the bug system does
  not currently understand them if they're buried in MIMEd or PGPd
  mail.) XXX-DETERMINEPACKAGE See below for further requirements.

  The packages available for putting in the Package line when reporting
  a bug are listed on the bugs WWW pages.

Example

  A bug report, with mail header, looks something like this:
 To: [email protected]
 From: [email protected]
 Subject: Hello says `goodbye'

 Package: hello
 Version: 1.3-2

 When I invoke `hello' without arguments from an ordinary shell
 prompt it prints `goodbye', rather than the expected `hello, world'.
 Here is a transcript:

 $ hello
 goodbye
 $ /usr/bin/hello
 goodbye
 $

 I suggest that the output string, in hello.c, be corrected.

 I am using Debian 1.1, kernel version 1.3.99.15z
 and libc 5.2.18.3.2.1.3-beta.

Please include in your report:

    * The exact and complete text of any error messages printed or
      logged. This is very important!
    * Exactly what you typed or did to demonstrate the problem.
    * A description of the incorrect behaviour: exactly what behaviour
      you were expecting, and what you observed. A transcript of an
      example session is a good way of showing this.
    * A suggested fix, or even a patch, if you have one.
    * Details of the configuration of the program with the problem.
      Include the complete text of its configuration files. XXX-XBUGINFO

  Include any detail that seems relevant - you are in very little danger
  of making your report too long by including too much information. If
  they are small please include in your report any files you were using
  to reproduce the problem (uuencoding them if they may contain odd
  characters etc.).

  Of course, like any email, you should include a clear, descriptive
  Subject line in your main mail header. The subject you give will be
  used as the initial bug title in the tracking system, so please try to
  make it informative !

Sending copies of bug reports to other addresses

  Sometimes it is necessary to send a copy of a bug report to somewhere
  else besides kde-bugs-dist and the package maintainer, which is where
  they are normally sent.

  You could do this by CC'ing your bug report to the other address(es),
  but then the other copies would not have the bug report number put in
  the Reply-To field and the Subject line. When the recipients reply
  they will probably preserve the [email protected] entry in the
  header and have their message filed as a new bug report. This leads to
  many duplicated reports.

  The right way to do this is to use the X-KDE-CC header. Add a line
  like this to your message's mail header (not to the psuedo header with
  the Package field):
X-KDE-CC: [email protected]

  This will cause the bug tracking system to send a copy of your report
  to the address(es) in the X-KDE-CC line as well as to kde-bugs-dist.

  This feature can often be combined usefully with mailing quiet - see
  below.

Severity levels

  If a report is of a particularly serious bug, or is merely a feature
  request that, you can set the severity level of the bug as you report
  it. This is not required, however, and the developers will assign an
  appropriate severity level to your report if you do not.

  To assign a severity level put a Severity: severity line in the
  psuedo-header, together with Package and Version. The severity levels
  available are described in the developers' documentation.

Not forwarding to the mailing list - minor bug reports

  If a bug report is minor (for example, a documentation typo or other
  trivial build problem), or you're submitting many reports at once,
  send them to maintonly@bugs or quiet@bugs. maintonly will send the
  report on to the package maintainer (provided you supply a correct
  Package line in the pseudo-header and the maintainer is known), and
  quiet will not forward it anywhere at all but only file it as a bug
  (useful if, for example, you are submitting many similar bugs and want
  to post only a summary).

  If you do this the bug system will set the Reply-To of any forwarded
  message so that replies will by default be processed in the same way
  as the original Multiple recipients of list" <[email protected]>]
Cc:
Subject:       ANNOUNCE:  kspaceduel-0.2.1.tar.gz

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.

       VNM3042:  [email protected]@BELGACOM



VNM3042 -- NAME NOT FOUND

  Mail cannot deliver the message for one of the
  following reasons:  the appropriate StreetTalk is not
  available; the recipient's user name was deleted; the
  recipient's name was not entered correctly.  Verify
  the accuracy of the name entered.  If the name you
  entered is a user name, check to see if the user was
  deleted. If the name is correct and the user exists,
  check the connections between the recipient and
  the sender.

  You may see this error if you send a message to a list,
  but one of  the names on the list is incorrect or in

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.