Bug 125656 - LibreOffice Writer crash at start after update from 6.2.3.2 to 6.2.4.2
Summary: LibreOffice Writer crash at start after update from 6.2.3.2 to 6.2.4.2
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.4.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: corruptProfile
Depends on:
Blocks: User-Profile-Upgrade
  Show dependency treegraph
 
Reported: 2019-06-03 13:04 UTC by opensuse.lietuviu.kalba
Modified: 2019-06-04 13:54 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
archive of several dmp files from ~/.config/libreoffice/4/crash/ (375.45 KB, application/zip)
2019-06-03 13:04 UTC, opensuse.lietuviu.kalba
Details
content of problematic directory ~/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/ (4.74 KB, application/zip)
2019-06-03 13:16 UTC, opensuse.lietuviu.kalba
Details

Note You need to log in before you can comment on or make changes to this bug.
Description opensuse.lietuviu.kalba 2019-06-03 13:04:42 UTC
Created attachment 151870 [details]
archive of several dmp files from ~/.config/libreoffice/4/crash/

After update from LibreOffice 6.2.3.2 to LibreOffice 6.2.4.2, LibreOffice Writer crash at start. It proposes to send crash report to LibreOffice site but fails to do so. It restarts automatically and crash if I select Writer (Calc start fine) and proposes to send crash report (but fails to do so). Its loop.


I updated LibreOffice from

Versija: 6.2.3.2
Darinio identifikatorius: aecc05fe267cc68dde00352a451aa867b3b546ac
Procesoriaus gijos: 4; OS:Linux 4.4; Sąsajos pateikimas: numatytasis; VCL: kde4; 
Lokalė: lt-LT (lt_LT.UTF-8); UI-Language: lt-LT
Calc: threaded

to

Versija: 6.2.4.2
Darinio identifikatorius: 2412653d852ce75f65fbfa83fb7e7b669a126d64
Procesoriaus gijos: 4; OS:Linux 4.4; Sąsajos pateikimas: numatytasis; VCL: kde4; 
Lokalė: lt-LT (lt_LT.UTF-8); UI-Language: lt-LT
Calc: threaded

both are from LibreOffice site RPM packages.
Comment 1 opensuse.lietuviu.kalba 2019-06-03 13:06:04 UTC
Now I found workaround:
after removing ~/.config/libreoffice/4/user/uno_packages/cache directory,
LibreOffice Writer starts again
Comment 2 opensuse.lietuviu.kalba 2019-06-03 13:14:26 UTC
After investigation, I found, that problematic directory is this:
~/.config/libreoffice/4_/user/uno_packages/cache/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/
Comment 3 opensuse.lietuviu.kalba 2019-06-03 13:16:53 UTC
Created attachment 151871 [details]
content of problematic directory ~/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/

It would be better if LibreOffice could automatically remove old cache after version update.
Comment 4 Xisco Faulí 2019-06-03 19:43:40 UTC
thanks for reporting this issue.
It's a corrupted profile issue which can be fixed by removing the user profile directory. I know it might be annoying but the profile rarely gets corrupted.
We have the policy to close this kind of bugs as RESOLVED WONTFIX
Comment 5 Adolfo Jayme Barrientos 2019-06-04 11:28:00 UTC
Then we should change that policy. Firefox does have checks to upgrade and clean up its user profile on upgrading versions, whenever necessary. Why can’t we do the same? Why do we have to pretend our profile doesn’t often get corrupted, and when it happens it’s never our fault? This really annoys me.
Comment 6 Dieter 2019-06-04 13:02:47 UTC
(In reply to Adolfo Jayme from comment #5)
> Then we should change that policy. Firefox does have checks to upgrade and
> clean up its user profile on upgrading versions, whenever necessary. Why
> can’t we do the same?

Adolfo, might be a good idea, if you open a new bug with this proposal.
Comment 7 Alex Thurgood 2019-06-04 13:50:06 UTC
(In reply to Adolfo Jayme from comment #5)
> Then we should change that policy. Firefox does have checks to upgrade and
> clean up its user profile on upgrading versions, whenever necessary. Why
> can’t we do the same? Why do we have to pretend our profile doesn’t often
> get corrupted, and when it happens it’s never our fault? This really annoys
> me.

1) I agree wholeheartedly with this.
 
2) This is not as uncommon as Xisco claims.

3) It simply shouldn't happen. Especially not between point releases (one might discuss whether it is allowable between major version releases, but even there, I would argue for it not to be allowable).

This happened to me recently when a mysql connector extension in my profile conflicted with the newly integrated built-in mysql connector, causing LO to crash on startup.

I had to manually experiment with each extension to try and find out which one was causing the problem, losing all of my previous settings in the process until I had isolated the problematic one and purged it.

We shouldn't be expecting users to deal with this.
Comment 8 Xisco Faulí 2019-06-04 13:54:00 UTC
(In reply to Adolfo Jayme from comment #5)
> Then we should change that policy. Firefox does have checks to upgrade and
> clean up its user profile on upgrading versions, whenever necessary. Why
> can’t we do the same? Why do we have to pretend our profile doesn’t often
> get corrupted, and when it happens it’s never our fault? This really annoys
> me.

Fair enough.
Please create a new enhancement for this where we can discuss how to proceed.
Closing this one as RESOLVED WONTFIX