Per subject: When rhythmbox crashes (which is, unfortunately, not too
rare), bug-buddy complains that it was not possible to generate a useful
bug report.

Іn fact, I have no idea what's wrong here, since bug-buddy does not
reveal any additional information about what exactly has gone wrong.

Thanks,

Johannes

tags 431396 + help unreproducible
stop

 Well, I have no idea what I can do.  Either the toolchain is broken, or
 you had bad luck and only met cases where the backtrace was corrupted,
 or bug-buddy is broken, but I can't tell.

 Please feel free to investigate further what's the source of the
 problem and whether rhythmbox-dbg is truly useless in all cases (which
 I doubt); I personally don't see how to go on from your report.

Maybe this is bug 401482 again, the kernel bug which results in useless
traces?

I ran into this myself when trying to reproduce bug #446288. I'm using
linux-image 2.6.22-4 so I don't think 401482 is to blame.

This error message was printed on the terminal;

        sa@zoe$ rhythmbox
        Multiple segmentation faults occurred; can't display error
        dialog
        sa@zoe$ ptrace: No such process.
        /home/sa/27873: No such file or directory.
        No stack.
        /usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file:
        No registers.

It haven't happened since, and I seem to get useful backtraces.

Hey,

Could you please still reproduce this issue with newer versions like
2.97-2.1 or 3.0.1-1+b1?

are backtraces producing useless information yet ?

thanks
regards
althaser