LibreOffice 7.3 not working on Fedora 34??

users
#1

Yesterday, Downloaded and installed and it reports a
crash, but just gives option to submit it, but no details.
Come up in safe mode, but opening calc just drops to
command prompt.
Tried running with strace, and don't see anything that
looks like error.
Have the Fedora 34 regular latest version running fine,
and have the had 7.2.x versions up to 7.2.5 and both work
fine.
Thought perhaps having 7.2.5 and 7.3 caused issue, so
uninstalled both, and then reinstalled 7.3, but same
results.
Have uninstalled 7.3, and put the 7.2.5 back, and it is
working.
Only tested with Calc, so not sure if 7.3 had other items
working?
Don't know what it actual submitted with the error it
found, or if includes any way to contact me of issue?
Thanks.

#2

Hi,

Yesterday, Downloaded and installed and it reports a
crash, but just gives option to submit it, but no details.
Come up in safe mode, but opening calc just drops to
command prompt.
Tried running with strace, and don't see anything that
looks like error.
Have the Fedora 34 regular latest version running fine,
and have the had 7.2.x versions up to 7.2.5 and both work
fine.
Thought perhaps having 7.2.5 and 7.3 caused issue, so
uninstalled both, and then reinstalled 7.3, but same
results.
Have uninstalled 7.3, and put the 7.2.5 back, and it is
working.
Only tested with Calc, so not sure if 7.3 had other items
working?
Don't know what it actual submitted with the error it
found, or if includes any way to contact me of issue?
Thanks.

Seems like this bugreport: https://bugs.documentfoundation.org/show_bug.cgi?id=146990

Best regards.
JBF

#3

Date sent: Sun, 6 Feb 2022 23:28:29 +0100
<jbfaure@libreoffice.org>
working on Fedora 34??
Copies to: mikes@guam.net
Organization: The Document Foundation

Hi,

> Yesterday, Downloaded and installed and it reports a
> crash, but just gives option to submit it, but no details.
> Come up in safe mode, but opening calc just drops to
> command prompt.
> Tried running with strace, and don't see anything that
> looks like error.
> Have the Fedora 34 regular latest version running fine,
> and have the had 7.2.x versions up to 7.2.5 and both work
> fine.
> Thought perhaps having 7.2.5 and 7.3 caused issue, so
> uninstalled both, and then reinstalled 7.3, but same
> results.
> Have uninstalled 7.3, and put the 7.2.5 back, and it is
> working.
> Only tested with Calc, so not sure if 7.3 had other items
> working?
> Don't know what it actual submitted with the error it
> found, or if includes any way to contact me of issue?
> Thanks.
>

Seems like this bugreport: https://bugs.documentfoundation.org/show_bug.cgi?id=146990

Thanks for info. Checked that bug report, and it links as
dup to another report. Does show more info than what I
am seeing, but no solution yet.

Downloaded the latest daily dev build I seem to find that
shows the date of the 2/5 and 7.3.0.0 and it does the
same.

One of the messages talks about a version 7.3.0.3 that
works, but I can't seem to find it on any of the links.
Perhaps it fixed this issue, but caused others??

Did try, and document and impress options do open, but
calc option just fails. It again sends report sometimes.

Will watch for an update, but again. Thanks.

#4

Hi Michael,

One of the messages talks about a version 7.3.0.3 that
works, but I can't seem to find it on any of the links.
Perhaps it fixed this issue, but caused others??

Have a look here: https://dev-builds.libreoffice.org/pre-releases/

or here: https://www.libreoffice.org/download/download/

7.3.0.3 is the current release of LO.

Regards

Robert

#5

Date sent: Mon, 7 Feb 2022 15:04:37 +0100
working on Fedora 34??
<robert@familiegrosskopf.de>

Hi Michael,
>
> One of the messages talks about a version 7.3.0.3 that
> works, but I can't seem to find it on any of the links.
> Perhaps it fixed this issue, but caused others??

Have a look here: https://dev-builds.libreoffice.org/pre-releases/

or here: https://www.libreoffice.org/download/download/

7.3.0.3 is the current release of LO.

The link just 7.3.0, but downloaded again, and file was
exactly the same as the earlier download. So, guess
7.3.0.3 might work with Fedora 35, but doesn't work on
any of my Fedora 34 machines.

#6

Now https://bugs.documentfoundation.org/show_bug.cgi?id=147135

This bug has been reported in the forums of a number Linux distros. The
issue is very random and appears to only arise in some hardware
environments.

For example, I run PCLinuxOS with either Intel or AMD based hardware on
a number of machines and I cannot reproduce the crash. For others with
near equivalent hardware and software environments to mine, the crash is
100% reproducible.

This is going to be a difficult one for the devs to track down.

Regards
Dave

#7

=On 7 Feb 2022 at 17:17, Dave Barton wrote:</div>
working on Fedora 34??
Date sent:      Mon, 7 Feb 2022 17:17:07 +0000

> Hi,
>
>> Yesterday, Downloaded and installed and it reports a
>> crash, but just gives option to submit it, but no details.
>> Come up in safe mode, but opening calc just drops to
>> command prompt.
>> Tried running with strace, and don't see anything that
>> looks like error.</font>
>> Have the Fedora 34 regular latest version running fine,
>> and have the had 7.2.x versions up to 7.2.5 and both work
>> fine.
>> Thought perhaps having 7.2.5 and 7.3 caused issue, so
>> uninstalled both, and then reinstalled 7.3, but same
>> results.> >> Have uninstalled 7.3, and put the 7.2.5 back, and it is
>> working.> >> Only tested with Calc, so not sure if 7.3 had other items
>> working?> >> Don't know what it actual submitted with the error it
>> found, or if includes any way to contact me of issue?
>> Thanks.> >>
>
> Seems like this bugreport:
> https://bugs.documentfoundation.org/show_bug.cgi?id=146990
>
> Best regards.> > JBF

Now https://bugs.documentfoundation.org/show_bug.cgi?id=147135

This bug has been reported in the forums of a number Linux distros. The
issue is very random and appears to only arise in some hardware
environments.

For example, I run PCLinuxOS with either Intel or AMD based hardware on
a number of machines and I cannot reproduce the crash. For others with
near equivalent hardware and software environments to mine, the crash is
100% reproducible.>
This is going to be a difficult one for the devs to track down.

Did notice something in message log file.
If run libreoffice7.3 but don't try calc there is nothing,
but if try calc and it crashes the log has these lines??

Feb  8 11:04:04 setzconote audit[513755]: ANOM_ABEND auid=1000 uid=0 gid=0 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=513755 comm="soffice.bin" exe="/opt/libreoffice7.3/program/soffice.bin"
sig=4 res=1
Feb  8 11:04:05 setzconote abrt-server[513792]: Package 'libreoffice7.3' isn't signed with proper key

Unfortuantely, the lines on abrt at time don't seem to show anything to me.
Feb  8 11:04:05 setzconote abrt-dump-journal-oops[2039]: abrt-dump-journal-oops: Found oopses: 1
Feb  8 11:04:05 setzconote abrt-dump-journal-oops[2039]: abrt-dump-journal-oops: Creating problem directories
Feb  8 11:04:05 setzconote abrt-server[513792]: Package 'libreoffice7.3' isn't signed with proper keyFeb  8 11:04:05 setzconote abrt-server[513792]: 'post-create' on '/var/spool/abrt/ccpp-2022-02-08-11:04:05.227869-513755' exited with 1
Feb  8 11:04:05 setzconote abrt-server[513792]: Deleting problem directory '/var/spool/abrt/ccpp-2022-02-08-11:04:05.227869-513755'
Feb  8 11:04:06 setzconote abrt-server[513791]: Can't find a meaningful backtrace for hashing in '.'</font>
Feb  8 11:04:06 setzconote abrt-server[513791]: Preserving oops '.' because DropNotReportableOopses is 'no'</span>
Feb  8 11:04:06 setzconote abrt-notification[513811]: System encountered a non-fatal error in ??()
Feb  8 11:04:06 setzconote abrt-dump-journal-oops[2039]: Reported 1 kernel oopses to Abrt

#8

=On 7 Feb 2022 at 17:17, Dave Barton wrote:</div>
working on Fedora 34??
Date sent:      Mon, 7 Feb 2022 17:17:07 +0000

> Hi,
>
>> Yesterday, Downloaded and installed and it reports a
>> crash, but just gives option to submit it, but no details.
>> Come up in safe mode, but opening calc just drops to
>> command prompt.
>> Tried running with strace, and don't see anything that
>> looks like error.</font>
>> Have the Fedora 34 regular latest version running fine,
>> and have the had 7.2.x versions up to 7.2.5 and both work
>> fine.
>> Thought perhaps having 7.2.5 and 7.3 caused issue, so
>> uninstalled both, and then reinstalled 7.3, but same
>> results.> >> Have uninstalled 7.3, and put the 7.2.5 back, and it is
>> working.> >> Only tested with Calc, so not sure if 7.3 had other items
>> working?> >> Don't know what it actual submitted with the error it
>> found, or if includes any way to contact me of issue?
>> Thanks.> >>
>
> Seems like this bugreport:
> https://bugs.documentfoundation.org/show_bug.cgi?id=146990
>
> Best regards.> > JBF

Now https://bugs.documentfoundation.org/show_bug.cgi?id=147135

This bug has been reported in the forums of a number Linux distros. The
issue is very random and appears to only arise in some hardware
environments.

For example, I run PCLinuxOS with either Intel or AMD based hardware on
a number of machines and I cannot reproduce the crash. For others with
near equivalent hardware and software environments to mine, the crash is
100% reproducible.>
This is going to be a difficult one for the devs to track down.

Did notice something in message log file.
If run libreoffice7.3 but don't try calc there is nothing,
but if try calc and it crashes the log has these lines??

Feb  8 11:04:04 setzconote audit[513755]: ANOM_ABEND auid=1000 uid=0 gid=0 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=513755 comm="soffice.bin" exe="/opt/libreoffice7.3/program/soffice.bin"
sig=4 res=1
Feb  8 11:04:05 setzconote abrt-server[513792]: Package 'libreoffice7.3' isn't signed with proper key

Unfortuantely, the lines on abrt at time don't seem to show anything to me.
Feb  8 11:04:05 setzconote abrt-dump-journal-oops[2039]: abrt-dump-journal-oops: Found oopses: 1
Feb  8 11:04:05 setzconote abrt-dump-journal-oops[2039]: abrt-dump-journal-oops: Creating problem directories
Feb  8 11:04:05 setzconote abrt-server[513792]: Package 'libreoffice7.3' isn't signed with proper keyFeb  8 11:04:05 setzconote abrt-server[513792]: 'post-create' on '/var/spool/abrt/ccpp-2022-02-08-11:04:05.227869-513755' exited with 1
Feb  8 11:04:05 setzconote abrt-server[513792]: Deleting problem directory '/var/spool/abrt/ccpp-2022-02-08-11:04:05.227869-513755'
Feb  8 11:04:06 setzconote abrt-server[513791]: Can't find a meaningful backtrace for hashing in '.'</font>
Feb  8 11:04:06 setzconote abrt-server[513791]: Preserving oops '.' because DropNotReportableOopses is 'no'</span>
Feb  8 11:04:06 setzconote abrt-notification[513811]: System encountered a non-fatal error in ??()
Feb  8 11:04:06 setzconote abrt-dump-journal-oops[2039]: Reported 1 kernel oopses to Abrt

Regards
Dave

What I am about to say has no bearing on anything related to reality, but, this is what I had to do to make VMWare work on Fedora after I built my own  binaries. The likliehood that this will work for you is very small indeed.

I think you will need to create a password for signing. I do not remember when, but, just think of a password and write it down or something.

(1) Generate a key, but do NOT use CN=VMware, use something like CN=LibreOffice
openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=VMware/"

(2) Import said key
mokutil --import MOK.der

(3) Sign the file of importance. In my case it was vmmon and vmnet (I ran this twice) for oyu it is probably soffice.bin
/usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vmmon)

Will this work? Probably not. If you are using Fedora, why not just use the version in the repo?

I only mention all this because if it were me I would try it, but I am on Fedora 35 now and I am using the version from the fedora repo.

Andrew

#9

<andrew@pitonyak.org>
Date sent: Mon, 07 Feb 2022 21:24:32 -0500
Copies to: "Dave Barton" <daveb@libreoffice.org>,
users@global.libreoffice.org
<msetzerii@gmail.com>
working on Fedora
  34??

=On 7 Feb 2022 at 17:17, Dave Barton wrote:</div>
Subject:          Re: [libreoffice-users] LibreOffice 7.3 not
working on Fedora 34??
To:                  users@global.libreoffice.org
From:        0;    Dave Barton <daveb@libreoffice.org>
Date sent:      Mon, 7 Feb 2022 17:17:07 +0000

> > Hi,
> >
> >> Yesterday, Downloaded and installed and it reports a
> >> crash, but just gives option to submit it, but no details.
> >> Come up in safe mode, but opening calc just drops to
> >> command prompt.
> >> Tried running with strace, and don't see anything that
> >> looks like error.</font>
> >> Have the Fedora 34 regular latest version running fine,
> >> and have the had 7.2.x versions up to 7.2.5 and both work
> >> fine.
> >> Thought perhaps having 7.2.5 and 7.3 caused issue, so
> >> uninstalled both, and then reinstalled 7.3, but same
> >> results.> >> Have uninstalled 7.3, and put the 7.2.5 back, and it is
> >> working.> >> Only tested with Calc, so not sure if 7.3 had other items
> >> working?> >> Don't know what it actual submitted with the error it
> >> found, or if includes any way to contact me of issue?
> >> Thanks.> >>
> >
> > Seems like this bugreport:
> > https://bugs.documentfoundation.org/show_bug.cgi?id=146990
> >
> > Best regards.> > JBF
>
> Now https://bugs.documentfoundation.org/show_bug.cgi?id=147135
>
> This bug has been reported in the forums of a number Linux distros. The
> issue is very random and appears to only arise in some hardware
> environments.
>
> For example, I run PCLinuxOS with either Intel or AMD based hardware on
> a number of machines and I cannot reproduce the crash. For others with
> near equivalent hardware and software environments to mine, the crash is
> 100% reproducible.>
> This is going to be a difficult one for the devs to track down.
>

Did notice something in message log file.
If run libreoffice7.3 but don't try calc there is nothing,
but if try calc and it crashes the log has these lines??

Feb  8 11:04:04 setzconote audit[513755]: ANOM_ABEND auid=1000 uid=0 gid=0 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=513755 comm="soffice.bin" exe="/opt/libreoffice7.3/program/soffice.bin"
sig=4 res=1
Feb  8 11:04:05 setzconote abrt-server[513792]: Package 'libreoffice7.3' isn't signed with proper key

Unfortuantely, the lines on abrt at time don't seem to show anything to me.
Feb  8 11:04:05 setzconote abrt-dump-journal-oops[2039]: abrt-dump-journal-oops: Found oopses: 1
Feb  8 11:04:05 setzconote abrt-dump-journal-oops[2039]: abrt-dump-journal-oops: Creating problem directories
Feb  8 11:04:05 setzconote abrt-server[513792]: Package 'libreoffice7.3' isn't signed with proper keyFeb  8 11:04:05 setzconote abrt-server[513792]: 'post-create' on '/var/spool/abrt/ccpp-2022-02-08-11:04:05.227869-513755' exited with 1
Feb  8 11:04:05 setzconote abrt-server[513792]: Deleting problem directory '/var/spool/abrt/ccpp-2022-02-08-11:04:05.227869-513755'
Feb  8 11:04:06 setzconote abrt-server[513791]: Can't find a meaningful backtrace for hashing in '.'</font>
Feb  8 11:04:06 setzconote abrt-server[513791]: Preserving oops '.' because DropNotReportableOopses is 'no'</span>
Feb  8 11:04:06 setzconote abrt-notification[513811]: System encountered a non-fatal error in ??()
Feb  8 11:04:06 setzconote abrt-dump-journal-oops[2039]: Reported 1 kernel oopses to Abrt

> Regards
> Dave
>

What I am about to say has no bearing on anything related to reality, but, this is what I had to do to make VMWare work on Fedora after I built my own  binaries. The likliehood that this will work for you is very small indeed.

I think you will need to create a password for signing. I do not remember when, but, just think of a password and write it down or something.

(1) Generate a key, but do NOT use CN=VMware, use something like CN=LibreOffice
openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=VMware/"

(2) Import said key
mokutil --import MOK.der

(3) Sign the file of importance. In my case it was vmmon and vmnet (I ran this twice) for oyu it is probably soffice.bin
/usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vmmon)

Will this work? Probably not. If you are using Fedora, why not just use the version in the repo?

I only mention all this because if it were me I would try it, but I am on Fedora 35 now and I am using the version from the fedora repo.

Andrew

Thanks for info, but I'm just installing from the rpm files
included in the libreoffice downloads, so not building
anything from source? Not sure if perhaps they used a
Fedora 35 key for the rpm that is not compatible with
Fedora 34. I build kernels from source for my g4l project.
Just strange that calc seems to fail, but others work.
Something that some libreoffice developer might know.

#10

This is not just Fedora.
I am facing the same problem in RHEL 8.5 installed using RPMS.

#11

Hi,

I installed a new RHEL 8.5 instance on a laptop.
LO 7.3 did not crash after installation.
It looks like moving from 7.2.5 to 7.3 or some problem with leftover files
in the RHEL upgrade caused the issue.

Thanks