Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 May 2019 14:01:33 +0200
From:      Jan Beich <jbeich@FreeBSD.org>
To:        Joan Picanyol i Puig <pica@biaix.org>
Cc:        office@freebsd.org, Greg Veldman <freebsd@gregv.net>, Li-Wen Hsu <lwhsu@freebsd.org>
Subject:   Re: reproducible crash after libreoffice update
Message-ID:  <sgtg-apuq-wny@FreeBSD.org>
References:  <20190514115233.GA9791@grummit.biaix.org> <CAKBkRUzCx=h20Jv%2BkocguNByhzPyPA6L8phvrmJgCUvfoqbntQ@mail.gmail.com> <20190514150206.GB11862@grummit.biaix.org> <sgth-m3hq-wny@FreeBSD.org> <20190514175041.GA14247@grummit.biaix.org> <r290-kem8-wny@FreeBSD.org> <20190515075117.GA23790@grummit.biaix.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Joan Picanyol i Puig <pica@biaix.org> writes:

> * Jan Beich <jbeich@FreeBSD.org> [20190514 21:30]:
>> Joan Picanyol i Puig <pica@biaix.org> writes:
> [...]
>> >> >> On Tue, May 14, 2019 at 8:11 AM Joan Picanyol i Puig <pica@biaix.org> wrote:
>> >> >> >
>> >> >> > Hi there,
>> >> >> >
>> >> >> > On FreeBSD 12.0-RELEASE-p3, after a recent update using quarterly pkg repo
>> >> >> > libreoffice-6.2.2_3 (+ icu-64.2,1) crashes repeatedly:
>> >> 
>> >> libreoffice from either /latest (6.2.3) or /quarterly (6.2.2_3) doesn't
>> >> crash here:
>> >> 
>> >>   1. start 12.0 amd64 jail
>> >>   2. pkg install libreoffice mesa-dri
>> >>   3. libreoffice /COPYRIGHT
>> >> 
>> >> Can you provide steps to reproduce?
>> >
>> > Trying to edit a cell in Calc. With two different worksheets so far,
>> > (both xlsx and ods formats), the second one extremely simple.
>> 
>> Can you upload those spreadsheets or describe their contents in a little
>> more detail? The following didn't crash here:
>
> Find attached a problematic spreadsheet. I get the gdb trace with
>
> libreoffice --backtrace ~/_wd/assets_rename.ods
>
> as soon as I try to enter some text in the selected cell.

Doesn't crash here. Which cell did you select? I've tried randomly
editing both empty and non-empty cells.

> However, I've found that setting $LANG to en_US.UTF-8 instead of
> ca_US.UTF-8 avoids the issue.

ca_US.UTF-8 doesn't exist unlike ca_ES.UTF-8 or en_CA.UTF-8.
I've tried C (default), ca_ES.UTF-8, en_US.UTF-8 locales.

>> > What icu do you have installed?
>> 
>> Whatever was in /latest or /quarterly at the time. Both had 64.2.
>> My runtime testing environment is poudriere-empty at the start.
>
> I've tried cleaning my user profile (rm ~/.config/libreoffice/4) without
> improvement.
>
> What would your next suggestion be?

Other than "pkg upgrade -f" or bisecting environment? If you need help
with debugging pilot errors questions@ maillist maybe a better place.

I'm interested in whether there's an ICU bug, not getting your system
back to a working state.

> Is it still worth to try /latest ?

/latest is a fast moving, bumpy target. Packages tend to disappear only
to reappear after a few days/weeks. If you still want to try make a
backup first and don't forget to read UPDATING.

As for libreoffice 6.2.3 it should've been MFH'd to 2019Q2. Releases
that improve stability are welcome on /quarterly. However, I'm neither
on ports-secteam@ nor use libreoffice.

https://blog.documentfoundation.org/blog/2019/04/18/libreoffice-6-2-3/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?sgtg-apuq-wny>