Steps to reproduce:
1. type libreoffice4.0 at the shell prompt
2. select text document at the new document window
3. see the application crashing
the application segfaults (immediately on writer, after some time on draw, etc)
The application should be usable...
Operating System: Ubuntu
Version: 18.104.22.168 rc
Last worked in: 22.214.171.124 release
Created attachment 80530 [details]
michael & Bjoern - I can't test this as it seems like the mirrors are down for download but it looks pretty serious - thoughts on next steps?
Although it's not confirmed I am setting it as BLOCKER - HIGHEST so if it is confirmed the priority is correct
Joel: as you said, it could be a blocker IF it's confirmed (https://wiki.documentfoundation.org/Release_Criteria#Blocker_Bug_Definition), for the moment it's not. Perhaps someone who's got an Ubuntu may confirm (see https://wiki.documentfoundation.org/QA/QA_Team). If installed via dpkg, it could be a dependency problem.
- did you install any LO specific extensions?
- what's your Java version?
- did you try to rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile)?
- could you try to retrieve a complete backtrace? (see https://wiki.documentfoundation.org/BugReport#How_to_get_a_backtrace_on_Linux)
Some more details:
1) Installed LibO 4.0.4 RC1 over the previous debs of 126.96.36.199 keeping my working environment (user profile + user extensions), as I usually do to try release candidates. This means that I did not have the LibO debs from the distribution before, but 188.8.131.52 from Libreoffice site.
2) Java is version "1.7.0_21"
OpenJDK Runtime Environment (IcedTea 2.3.9) (7u21-2.3.9-1ubuntu1)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode).
This was also in the log file attached before:
JRE version: 7.0_21-b02
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libvclplug_genlo.so+0x36ebe] SalXLib::CheckTimeout(bool)+0xe
3) I have a couple of extensions: latest languagetool and texmaths. This in addition to the 'standard' extensions shipped with LibO.
4) All LibO modules segfault, but most of them seem to do it only on closing the application (draw, calc). Only write seem to segfault immediately
5) Launching LibO without opening any module (i.e. staying at the window showing buttons to open text document, spreadsheet, presentation, etc. and maybe exploring Add on or options) and then closing does not cause segfault.
6) Chosing a text document, LibO crashes immediately.
7) At first launch of LibO 4.0.4 RC1, after having moved away the current profile, before the window to open LibO modules there is briefly another window a progress bar and writings running over it. This is badly mangled, with the progress bar not being filled, another progress bar appearing halfway through the window and filling, text running over this new progress bar. But maybe this has nothing to do with the current issue.
8) LibO does anyway crash even after having started with an empty profile when opening the text document module.
9) I have a gdbtrace, but I do not know how useful this can be, since it seems not to have symbols resolved. I do not know how to get the equivalent of a -dbg package from the Libreoffice repo.
10) I have a strace.
Created attachment 80599 [details]
output from libreoffice --backtrace
Created attachment 80600 [details]
Some more details on my hardware too:
1) Intel graphics (gen4)
2) 64bit Ubuntu
Removed 4.0.4 RC1 I went back to 184.108.40.206 that works fine.
Moving back to unconfirmed as Sergio has provided a lot of info
Sergio: thank you for all these details! I rarely use dpkg so I'm not an expert at all but I would have uninstalled .deb before installing new ones.
Just to complete information, do you reproduce this with 4.1.0 beta2? (you can rename your LO directory profile and therefore make your test with a brand new LO profile).
I have quickly tested 4.1 beta 2:
1) I do not see the segfault
2) I see the same mangling of the very initial progress bar as in 4.0.4 RC1
I have also tested 4.0.4 RC1 /after completely manually removing 4.0.3/
1) In this way I do not see the segfault
2) There is still some mangling of the very intial progress bar
A note about debs
I have disinstalled all the distribution-provided libreoffice debs before testing, since these are quite different form the debs delivered by libreoffice.org (which is obvious, since libreoffice.org cannot finely control what the distribution does. Moreover, the distribution wants to use all the distribution libs).
However, I am typically installing debs from libreoffice.org over previous debs from libreoffice.org, as this is how debs and dpkg should work (i.e. dpkg should take care automatically of disinstalling the previous debs and installing the new ones). I believe that most people will do this, particularly upgrading between point releases 4.0.3 -> 4.0.4. If this does not work (as it now looks to be the case) there is probably some packaging bug. However, these are certainly not as serious as an application segfaulting on its own.
> I believe that most people will do this, particularly upgrading between
> point releases 4.0.3 -> 4.0.4. If this does not work (as it now looks to
> be the case) there is probably some packaging bug. However, these
> are certainly not as serious as an application segfaulting on its own.
Well - ideally we would fix the segfault too of course :-) but the stack-trace is ~nonsensical sadly.
If you can reproduce the system state where this crashes on startup - then I'd love to see a package list to see what files / packages are left over from the old packages - quite possibly we need to tweak that somehow.
Can you get it back into that state ?
I'll try to check removing everything installing 4.0.3 updating to 4.0.4 RC without wiping 4.0.3 and see if the segfaults comes out again. Unfortunately I do not think that I will be able to try it before the weekend.
I confirm the packaging bug for deb files for ubuntu.
1) completely uninstalled libreoffice.
2) installed libreoffice 4.0.3 from the provided debs
3) installed libreoffice 4.0.4 RC2 from the provided debs
during the installation dpkg says that it is removing the 4.0.3 components and installing the corresponsing 4.0.4 ones.
However, with this procedure libreoffice 4.0.4 does not work and segfault
This is because libreoffice4.0-gnome-integration from 4.0.3 remain installed.
Initially, with the great deal of things getting installed, I did not notice it.
For some reason the install of the 4.0.4 gnome-integration in my system fails unless the 4.0.3 gnome integration is manually removed.
So the issue in the end is really minor.
> For some reason the install of the 4.0.4 gnome-integration in my system
> fails unless the 4.0.3 gnome integration is manually removed.
Ok - that's still bad - we shouldn't have unexpected segfaults [!]
Let me turn this into an easy-hack - which I'll file separately to make that issue cleaner; see bug#65859
Does not make sense to not try to get the missing dependencies described in commeent 13 fixed for our "generic" installation sets downloadable from <http://www.libreoffice.org/download>.
See <https://gerrit.libreoffice.org/#/c/4344/> "Proper EPM %requires dependencies, at least for Linux" for the proposed fix.
[the missing dependencies are not a regression AFAICT; removing the keyword]
Stephan Bergmann committed a patch related to this issue.
It has been pushed to "master":
fdo#65541: Proper EPM %requires dependencies, at least for Linux
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.