Re: Rewriting the GettingTraces page

["Elijah Newren" <newren gmail com>]

Hi Andre,

Thanks for the feedback.  :)

On 10/19/06, Andre Klapper <ak-47 gmx net> wrote:
> #1
> we do not only link to this page when we ask people for a better
> stacktrace, but also when a stacktrace is entirely missing
> (need_stacktrace).
> however, i wouldn't change the second sentence on the wiki page, as i
> hope that it encourages people to provide a good stacktrace.

Yeah, I wanted to word it to handle both cases but still make sure
that people install debuginfo packages in both cases.  :-)  I'm not
sure the best way of doing that.  Here's an alternative wording for
the second sentence:

"This extra bit of information they asked for is a stack trace (also
known as a backtrace), and it is important that the stack trace you
obtain contains debugging symbols."

Not sure which is better or if someone else has an alternative
suggestion.  Thoughts?

> #2
> perhaps something like this?:
>
> "You need to install additional debug packages to get the requested
> so-called "debugging symbols" for the program that crashed.

Hmm...I'm not a fan of the "so-called" part of the sentence.  ;-)
Also, if the user could have been worried about reinstalling, wouldn't
they also have worries about what additional packages would do?  Maybe
we should change this to something like:

"You need to install debug packages for the program that crashed.
These debug packages are additional packages that do not affect the
operation of your existing program, but provide debugging symbols
needed by developers to help pinpoint problems when they occur."

> Most likely
> you also need to install debug packages for some of the program's major
> dependencies.
> Installing debug packages for GNOME's major libraries like glib, gtk+,
> and gnome-vfs is also a good idea (note that distros often rename these
> to e.g. glib2, gtk2, and gnome-vfs2 to allow parallel installation with
> GNOME 1.x libraries), because most of the GNOME programs depend on those
> major libraries and make use of their functionality."

I like your changes here.

> #3
> "You can then cut-and-paste it from bug-buddy into your bug report."
>
> we always have and had a "Copy" button in the left bottom corner, right?
> whatever "cut-and-paste" means, let's make it easy and say
>
> "You can then click on Bug-Buddy's "Copy" button and after that, you can
> paste the information into your bug report."

The general idea sounds fine, but I don't see any copy button.  Am I blind?


Thanks,
Elijah