Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1017427 > unrolled thread

Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Rene Engelhard <rene@debian.org> - 2020-07-10 17:00 +0200
    Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Rene Engelhard <rene@debian.org> - 2020-07-10 17:40 +0200
      Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Thorsten de Jong <hallo@tdejong.de> - 2020-07-10 23:10 +0200
      Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Rogério Brito <rbrito@ime.usp.br> - 2020-07-15 16:20 +0200
        Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Rene Engelhard <rene@debian.org> - 2020-07-15 17:40 +0200
          Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Rene Engelhard <rene@debian.org> - 2020-07-15 17:50 +0200
            Bug#954849: Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Rene Engelhard <rene@debian.org> - 2020-07-16 18:20 +0200
              Bug#954849: Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Rogério Brito <rbrito@gmail.com> - 2020-07-17 01:30 +0200
                Bug#954849: Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5 Rene Engelhard <rene@debian.org> - 2020-07-17 07:20 +0200

#1017427 — Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5

severity 964780 important
tag 964780 + moreinfo
tag 964780 + unreproducible
thanks

On Fri, Jul 10, 2020 at 02:12:26PM +0200, Thorsten de Jong wrote:
> Package: libreoffice-writer
> Version: 1:7.0.0~rc1-5
> Severity: grave
> Justification: renders package unusable

Erm, no, how?

It _obviously_
- starts in a clean VM
- starts in autokpgtest. Which starts writer up a gazillion of times to
  check the UI.

>    * What led up to the situation?
> Starting libreoffice-writer

It really hard to write a bit more?

You write "crashes". I didn't see a crash in strace? You it actually
crash and did you attach gdb as written in the reportbug message? Or did
it fail to start? (That isn't a crash.)

> Debian Release: bullseye/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
> 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')

Not related, but:

I'll never undertsand why people do bullshit lile this. Especially
stable and testing.. (You are completely on unstable away, so there's no
point in this)

[ attached strace.log ]

No idea whether it is related, but I see gazillions of stuff like

11267 14:00:25.991198 stat("/usr/lib/libreoffice/program/tech/units/indriya/AbstractConverter$Pair.class", 0x7f3a9fff8b80) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden
)
11267 14:00:25.991231 stat("/home/thaden/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu7352qashpo.tmp_/LanguageTool-4.8.oxt/tech/units/indriya/AbstractConvert
er$Pair.class", 0x7f3a9fff8b80) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)

/usr/lib/libreoffice/program/tech/units/indriya/AbstractConverter$Pair.class
would be wrong in any case, sd the files would never be there.

How did you install LanguageTool (which is known to cause problems like
instability)? What happens if you remove it?

And why 4.8? There's 5.0.1 on languagetool.org? Maybe it has fixes?

In a quick test in a clean VM writer still starts after LT 4.8 was
installed, though.

What happens if you start in safe mode and/or move your
.config/libreoffice away and start with a clean profile?

Regards,

Rene

[toc] | [next] | [standalone]

#1017432

Hi,

Am 10.07.20 um 16:44 schrieb Rene Engelhard:
> You write "crashes". I didn't see a crash in strace? You it actually
> crash and did you attach gdb as written in the reportbug message? Or did
> it fail to start? (That isn't a crash.)
Actually there's SIGSEGV at the end ...
>
> No idea whether it is related, but I see gazillions of stuff like
>
> 11267 14:00:25.991198 stat("/usr/lib/libreoffice/program/tech/units/indriya/AbstractConverter$Pair.class", 0x7f3a9fff8b80) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden
> )
> 11267 14:00:25.991231 stat("/home/thaden/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu7352qashpo.tmp_/LanguageTool-4.8.oxt/tech/units/indriya/AbstractConvert
> er$Pair.class", 0x7f3a9fff8b80) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)

but I wouldn't be surprised if that was because of those


> In a quick test in a clean VM writer still starts after LT 4.8 was
> installed, though.

.. and doesn't show the above.

Regards,


Rene

[toc] | [prev] | [next] | [standalone]

#1017488

Hello,

deactivating LanguageTool did not help,

starting in safe mode and with all settings restored to factory
defaults as suggested in the earlier mail did help, though.

Regards,
Thorsten.


Am Freitag, den 10.07.2020, 17:31 +0200 schrieb Rene Engelhard:
> Hi,
> 
> Am 10.07.20 um 16:44 schrieb Rene Engelhard:
> > You write "crashes". I didn't see a crash in strace? You it
> > actually
> > crash and did you attach gdb as written in the reportbug message?
> > Or did
> > it fail to start? (That isn't a crash.)
> Actually there's SIGSEGV at the end ...
> > No idea whether it is related, but I see gazillions of stuff like
> > 
> > 11267 14:00:25.991198
> > stat("/usr/lib/libreoffice/program/tech/units/indriya/AbstractConve
> > rter$Pair.class", 0x7f3a9fff8b80) = -1 ENOENT (Datei oder
> > Verzeichnis nicht gefunden
> > )
> > 11267 14:00:25.991231
> > stat("/home/thaden/.config/libreoffice/4/user/uno_packages/cache/un
> > o_packages/lu7352qashpo.tmp_/LanguageTool-
> > 4.8.oxt/tech/units/indriya/AbstractConvert
> > er$Pair.class", 0x7f3a9fff8b80) = -1 ENOENT (Datei oder Verzeichnis
> > nicht gefunden)
> 
> but I wouldn't be surprised if that was because of those
> 
> 
> > In a quick test in a clean VM writer still starts after LT 4.8 was
> > installed, though.
> 
> .. and doesn't show the above.
> 
> Regards,
> 
> 
> Rene
> 

[toc] | [prev] | [next] | [standalone]

#1018057

Hi there.

On Jul 10 2020, Rene Engelhard wrote:
> Am 10.07.20 um 16:44 schrieb Rene Engelhard:
> > You write "crashes". I didn't see a crash in strace? You it actually
> > crash and did you attach gdb as written in the reportbug message? Or did
> > it fail to start? (That isn't a crash.)
> Actually there's SIGSEGV at the end ...

Right after the upgrade to the version mentioned in the subject, I started
seeing the problem.

I tried to find bug reports about this, found only this one and expected to
find more, waited a few days, and this is still the only problem reported so
far, which I found strange.

Nevertheless, what I am seeing may or may not be related to the bug that
Thorsten reported (in which case a new bug should be filed, of course), but
removing ~/.config/.libreoffice and invoking libreoffice on the command line
briefly shows the splash screen and, then, shows the following message on my
terminal:

,----
| $ libreoffice 
| : CommandLine Error: Option 'polly' registered more than once!
| LLVM ERROR: inconsistency in registered CommandLine options
`----

I will send the compressed strace log to this bug right after this message.

If you need further information, please let me know.


Thanks,

Rogério Brito.

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

[toc] | [prev] | [next] | [standalone]

#1018067

Hi,

Am 15.07.20 um 16:10 schrieb Rogério Brito:

> I tried to find bug reports about this, found only this one and expected to
> find more, waited a few days, and this is still the only problem reported so
> far, which I found strange.

Why? That just shows it works in most cases, and breaks in "special" ones. And of course if it works in most cases people don't report a bug ;-)

> Nevertheless, what I am seeing may or may not be related to the bug that
> Thorsten reported (in which case a new bug should be filed, of course), but
> removing ~/.config/.libreoffice and invoking libreoffice on the command line

Given Thorsten says it works with a clean profile, how should it? You
said you removed it and got *AN OTHER* error.

Can "bugs" please be kept separate?

> briefly shows the splash screen and, then, shows the following message on my
> terminal:
>
> ,----
> | $ libreoffice 
> | : CommandLine Error: Option 'polly' registered more than once!
> | LLVM ERROR: inconsistency in registered CommandLine options
> `----

I'd have a look what causes this. Wherever this "polly" "command-line"
option is set.

LO doesn't set it.


(And only a subset of LO is built with clang but not linked with LLVM or
otherwise using it, so

that can't be it either, especially since googling for it (and I think
there was a similar bug months ago with an other option) predates 7.0s
clang usage)

Regards,

Rene

[toc] | [prev] | [next] | [standalone]

#1018068

Hi,

Am 15.07.20 um 17:34 schrieb Rene Engelhard:
>>
>> ,----
>> | $ libreoffice 
>> | : CommandLine Error: Option 'polly' registered more than once!
>> | LLVM ERROR: inconsistency in registered CommandLine options
>> `----
> 
> I'd have a look what causes this. Wherever this "polly" "command-line"
> option is set.
> 
> LO doesn't set it.

And given
https://www.google.com/search?q=LLVM+ERROR%3A+inconsistency+in+registered+CommandLine+options+LibreOffice

this also seems to happen in all possible situations. Also not only for
LibreOffice. Also in cmake usage, OpenCL stuff, ...

"Good", now we have two non-bugs mangled in one bug.

Actually I already wanted to ask Thorsten whether this "bug" could have
be closed...

Regards,

Rene

[toc] | [prev] | [next] | [standalone]

#1018205 — Bug#954849: Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5

Hi,

Am 15.07.20 um 17:42 schrieb Rene Engelhard:
> Am 15.07.20 um 17:34 schrieb Rene Engelhard:
>>>
>>> ,----
>>> | $ libreoffice 
>>> | : CommandLine Error: Option 'polly' registered more than once!
>>> | LLVM ERROR: inconsistency in registered CommandLine options
>>> `----
>>
>> I'd have a look what causes this. Wherever this "polly" "command-line"
>> option is set.
>>
>> LO doesn't set it.
> 
> And given
> https://www.google.com/search?q=LLVM+ERROR%3A+inconsistency+in+registered+CommandLine+options+LibreOffice
> 
> this also seems to happen in all possible situations. Also not only for
> LibreOffice. Also in cmake usage, OpenCL stuff, ...

Also note https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954849.

We should discuss there, probably. Different option but... I still
believe it's not a LO problem but a problem of something using LLVM or
someone configuring something (using LLVM) badly.

> Actually I already wanted to ask Thorsten whether this "bug" could have
> be closed...

Which he agreed with so this is done :-)

Regards,

Rene

[toc] | [prev] | [next] | [standalone]

#1018259 — Bug#954849: Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5

Hi, Rene.

On Thu, Jul 16, 2020 at 4:11 PM Rene Engelhard <rene@debian.org> wrote:
> Am 15.07.20 um 17:42 schrieb Rene Engelhard:
> > Am 15.07.20 um 17:34 schrieb Rene Engelhard:
> >>> ,----
> >>> | $ libreoffice
> >>> | : CommandLine Error: Option 'polly' registered more than once!
> >>> | LLVM ERROR: inconsistency in registered CommandLine options
> >>> `----
> >>
> >> I'd have a look what causes this. Wherever this "polly" "command-line"
> >> option is set.

In the context of LLVM polly is the integer polyhedral optimization
"engine" (GCC also uses something similar called graphite, if I am not
mistaken). What causes it to be included multiple times, I don't know
(but I suspect, see below).

> We should discuss there, probably. Different option but... I still
> believe it's not a LO problem but a problem of something using LLVM or
> someone configuring something (using LLVM) badly.

I tested stuff a little bit more and, now, I can tell more about this
issue. Are you ready for a journey? :-) I hope that you are.

First, I completely removed libreoffice and everything that it
recommended or suggested.

Then, I went to snapshot.debian.org and installed version 1:6.4.5-1
(only writer). It worked.

Then, installed impress. It still worked.

Then, I upgraded everything to version 1:7.0.0~rc1-5. It *STILL*
worked, to my amazement.

Then, remembering that Calc started using OpenCL (at one point or
another), I installed calc. It *STILL* worked.

I installed the gtk3 component, because the default interface is
horrendous. It still worked.

Then, I installed beignet-opencl-icd. It *STILL* worked. (I have a
notebook with an integrated intel chip and a discrete AMD card)

Then, I installed mesa-opencl-icd. It pulled in a lot of packages,
including clang-common-10-dev and other stuff. It *still* worked, to
my amazement.

Then, I decided, just for fun, to remove the directory
~/.config/libreoffice (actually, I simply renamed it to
~/.config/libreoffice.old). NOW, it didn't work and showed again the
"polly" message.

If I copy back the contents from ~/.config/libreoffice.old to
~/.config/libreoffice and invoke libreoffice, then it works again.

OK, so, mesa-opencl-icd was the thing that caused some instabilities,
right? I then, decided to remove it (and its dependencies), just
keeping Intel's beignet and, bingo:

I can fire up libreoffice with both a prepopulated
~/.config/libreoffice or not and it works without any problems.

With mesa-opencl-icd/20.1.2-1 installed, I can only run libreoffice
successfully if I have a preexisting ~/.config/libreoffice from a
previous successful run (an empty directory prevents it from running).

So, part of the mystery is unveiled (but not solved)... The problem is
definitely not with libreoffice, but with LLVM & Co.

Just for the record, the packages that were installed when
mesa-opencl-icd/20.1.2-1 were:

* lib32gcc-s1/10.1.0-4
* lib32stdc++6/10.1.0-4
* libc6-i386/2.30-8
* libclang-common-10-dev/1:10.0.1~+rc4-1
* libclc-amdgcn/0.2.0+git20190
* libclc-dev/0.2.0+git20190
* libclc-r600/0.2.0+git20190

Based on this, I guess that this bug should probably be reassigned to
the LLVM people, perhaps (or to the mesa people)...

Oh, I just took a minute and tested the following:

If I remove beignet and keep the mesa icd, the problem still persists:
If I have an empty "profile", libreoffice doesn't start (and shows the
polly message from above). If I copy a "profile" that was used
successfully in the past, then libreoffice starts with the mesa icd &
Co.

Well, that's it for the moment. I hope that this is informative.

More precise information, straces and logs are available if needed.


Thanks for taking care of libreoffice in Debian,

Rogério Brito.

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

[toc] | [prev] | [next] | [standalone]

#1018278 — Bug#954849: Bug#964780: libreoffice-writer crashes on startup after upgrade to 1:7.0.0~rc1-5

reassign 954849 mesa-opencl-icd

forcemerge 964973 954849

affects 964973 libreoffice,libreoffice-calc

thanks


Hi,


Am 17.07.20 um 01:19 schrieb Rogério Brito:
> On Thu, Jul 16, 2020 at 4:11 PM Rene Engelhard <rene@debian.org> wrote:
>> Am 15.07.20 um 17:42 schrieb Rene Engelhard:
>>> Am 15.07.20 um 17:34 schrieb Rene Engelhard:
>>>>> ,----
>>>>> | $ libreoffice
>>>>> | : CommandLine Error: Option 'polly' registered more than once!
>>>>> | LLVM ERROR: inconsistency in registered CommandLine options
>>>>> `----
>>>> I'd have a look what causes this. Wherever this "polly" "command-line"
>>>> option is set.
> In the context of LLVM polly is the integer polyhedral optimization
> "engine" (GCC also uses something similar called graphite, if I am not
> mistaken). What causes it to be included multiple times, I don't know
> (but I suspect, see below).
>
>> We should discuss there, probably. Different option but... I still
>> believe it's not a LO problem but a problem of something using LLVM or
>> someone configuring something (using LLVM) badly.
> I tested stuff a little bit more and, now, I can tell more about this
> issue. Are you ready for a journey? :-) I hope that you are.
[...]
> Then, remembering that Calc started using OpenCL (at one point or
> another), I installed calc. It *STILL* worked.
[...]
> Then, I installed beignet-opencl-icd. It *STILL* worked. (I have a
> notebook with an integrated intel chip and a discrete AMD card)
>
> Then, I installed mesa-opencl-icd. It pulled in a lot of packages,
> including clang-common-10-dev and other stuff. It *still* worked, to
> my amazement.
>
> Then, I decided, just for fun, to remove the directory
> ~/.config/libreoffice (actually, I simply renamed it to
> ~/.config/libreoffice.old). NOW, it didn't work and showed again the
> "polly" message.
>
> If I copy back the contents from ~/.config/libreoffice.old to
> ~/.config/libreoffice and invoke libreoffice, then it works again.
>
> OK, so, mesa-opencl-icd was the thing that caused some instabilities,
> right? I then, decided to remove it (and its dependencies), just
> keeping Intel's beignet and, bingo:
>
> I can fire up libreoffice with both a prepopulated
> ~/.config/libreoffice or not and it works without any problems.
>
> With mesa-opencl-icd/20.1.2-1 installed, I can only run libreoffice
> successfully if I have a preexisting ~/.config/libreoffice from a
> previous successful run (an empty directory prevents it from running).

Probably with a clean profiile it sees the stuff is there and enables
OpenCL while it doesn't if the ICD is not present?

Maybe we generally should disable OpenCL per default?

(as Fedora apparently does:
https://src.fedoraproject.org/rpms/libreoffice/blob/master/f/0001-Resolves-rhbz-1432468-disable-opencl-by-default.patch)


> So, part of the mystery is unveiled (but not solved)... The problem is
> definitely not with libreoffice, but with LLVM & Co.
>
> Just for the record, the packages that were installed when
> mesa-opencl-icd/20.1.2-1 were:
>
> * lib32gcc-s1/10.1.0-4
> * lib32stdc++6/10.1.0-4
> * libc6-i386/2.30-8
> * libclang-common-10-dev/1:10.0.1~+rc4-1
> * libclc-amdgcn/0.2.0+git20190
> * libclc-dev/0.2.0+git20190
> * libclc-r600/0.2.0+git20190
>
> Based on this, I guess that this bug should probably be reassigned to
> the LLVM people, perhaps (or to the mesa people)...

Yeah.

I just noticed there is already
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964973

> More precise information, straces and logs are available if needed.

One could tell the mesa people :-)

Reassignig this bug :-)

> Thanks for taking care of libreoffice in Debian,
Thanks for trying and giving some light here.

And for the original one:

--- snip ---

in console I get message:
: CommandLine Error: Option 'limited-coverage-experimental' registered more
than once!
LLVM ERROR: inconsistency in registered CommandLine options

--- snip ---


there was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852746
(especially https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852746#76
?), too...


Regards,


Rene

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web