Hi, I am sorry for Stephanes premature bug closings.
On Mon, May 13, 2019 at 05:08:32PM +0200, Oliver Sander wrote: > > This kind of bug is not specific to Debian. I recommend you register on the > > bugtracker of LO and follow it. > > This is indeed what I did before filing the Debian report. In particular, > my Debian report says: > > > I filed an upstream bug: > > https://bugs.documentfoundation.org/show_bug.cgi?id=124607 > > but upstream cannot reproduce it. So could this be a packaging bug... and I am not convinced it is. We don't patch that place, and if a build with sane build options (or a different compiler, ..) exhibits this bug it is STILL a upstream bug. That upstreams ia fast at blaming thers is now, but.. (We also split the package differently, but I don't believe this can be the case here.) That upstreams test on obsolete distros with old libraries is also not very helpful. > And later in that bugreport I note that I get the bug with the Debian package > of LO > but not with the same LO version downloaded directly from the Document > Foundation site. > > So I am not convinced yet that this is not a Debian issue. See above, I am not conviced it's a Debian issue and not a upstream issue. Regards, Rene