Dear Maintainer,

I would love to have the LO crash tracker in Debian, so that I could use Deb packages to report bugs with a good trace. Would it be
possible?

Regards

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

tag 992925 + moreinfo
thanks

Hi,
them? (Let alone think about external libraries). Do we really want our
LO to "phone home" on a crash? Do we want to set up a web service for
those reports? (The latter one definitely is no)

For a meaningful backtrace you just need the *-dbgsym's, not necessarily
the "crash reporter".

And then there's it using libbreakpad. Which TTBOMK is not packaged, and
I am not going to do that (and I am not going to use the internal
library for this either).

And if I read upstreams configure.ac right the default for
--enable-breakpad even is no.

So no: won't do it.

Regards,

Rene

Well I am not a familiar with QA, but according to what I understand, in
TDF releases (I tried nightly before going back to Debian as it was
useless), when LO crashes, a crash report is somewhere on the TDF infra.
It also is stored on the locl computer. From this file, a user can check
wether a bug is opened or not and if not, fill one with reproducible
steps and this file to help upstream devs.

Nethertheless I understand that if our build config is different, it may
be less relevant. But then, how should users address crashes? Reporting
on Debian BTS? Upstream explaining this differences? Only a reproducible
scenario and not any trace?

See for example

Yes but it also requirs skills related to gdb then, doesn't it? I mean,
-dbgsym are a base to get relevant crash reports, but how to generate 
them? The only way I know is running gdb, but il Libreoffice the problem
is knowing on which binary.

I perfectly admit that I am not a tchnician, and that is exactly why I
try having solutions to help trace and fix bugs upstream without
programming skills.

I can understand, I did not know what implied such wish, hence my will
to open the topic.
relevant? If yes, should not we write something to assist users doing it
(a short wiki page about how to help debugging LO from a Debian release)?

Regards

I know. That needs infrastructure, though, as you say.

Yes, you can still do so manually...

Yes.

There's basically just soffice.bin as a binary.

https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace ?

Regards,

Rene

Dear submitter,

as the package libreoffice has just been removed from the Debian archive
experimental we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1069123

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Humanitarian Grant of 1.5M for you. Reply for claims