Re: Amarok 1.92 crashes on powerpc.

[Cédric Boutillier <cedric.boutillier@gmail.com>]

Hi Michel,

> A bug is a bug, and the Debian BTS version tracking makes this kind of
> thing easy. What exactly did you try, and what happened?

I launched 'reportbug amarok', and I got the following disclaimer when I tried 
to create a new bug report:
------------------
  Please DO NOT report UPSTREAM bugs in this Amarok version to the
                        Debian Bug Tracking System

  The experimental version of Amarok you have installed is either alpha, beta,
  release-candidate (RC), a snapshot of upstream development tree or other
  type of pre-release. Hence crashes, missing or partially working features
  and other types of bugs ranging from minor to grave are expected depending
  on the current development stage. Therefore it would be overwhelming for me,
  Debian maintainer of the Amarok package, to provide support for Amarok
  upstream bugs (i.e. problems with Amarok itself) at this stage. So UNLESS:

    1) you are sure that you've found a problem with Debian packaging or just 
       want to suggest a packaging related improvement
    -- OR --
    2) the bug is grave (e.g. like Amarok does not start) so Amarok is
       completely unusable or Amarok completely breaks unrelated software or
       eats unrelated data (i.e. it might be dangerous for other users systems
       or data),

  DO NOT report it to the Debian Bug Tracking System. If you do, the bug will 
be
  discarded and closed. You should report problems with pre-release versions
  directly to Amarok developers (unless they explicitly discourage bug
  reporting) by visiting http://bugs.kde.org/ or choosing "Report Bug..."
  from the "Help" menu in the main Amarok window. If you're about to report a
  crash, make sure the backtrace was generated with the amarok-dbg package and
  preferably its recommends installed on your system. This way the most 
accurate
  information will be provided to the Amarok developers.
------------------

I continued, filed my bug report with a 'serious' level, and when I tried to 
send it, I got a similar message. Then, I had a problem with my relayhost 
smtp, and the bug report got stuck for a while, but seemed to have been sent 
at some point. I will try again to see if the same scenario repeats.

I saw that a new version of amarok 1.92.2 landed on experimental today. I 
tried to build it, but still got the same error.

Best regards,

Cédric