Bug 129894 - LOOL: Menu "Insert > Image ..." causes CRASH
Summary: LOOL: Menu "Insert > Image ..." causes CRASH
Status: RESOLVED DUPLICATE of bug 129895
Alias: None
Product: LibreOffice Online
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL: https://github.com/NixOS/nixpkgs/pull...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-09 01:33 UTC by Martin Milata
Modified: 2020-01-30 16:36 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
backtrace from gdb (40.28 KB, text/plain)
2020-01-09 01:33 UTC, Martin Milata 		Details
journald snippet (7.59 KB, text/plain)
2020-01-09 01:34 UTC, Martin Milata 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Milata 2020-01-09 01:33:55 UTC 
Created attachment 157021 [details]
backtrace from gdb

Hi! I'm trying to package LibreOffice Online for the NixOS linux distribution. It's mostly working now however there are some crashes. Please note that NixOS has unusual filesystem layout, meaning that the systemplate setup script had to be rewritten from scratch and may possibly be missing files.

Versions:
core: git tag CODE-4.2.0-2 (commit 3d7bdc46)
online: git tag CODE-4.2.0-2 (commit 3b4be91f)
nextcloud: 17.0.2
collabora app: 3.5.1
(loolwsd is running behind https nginx proxy)

Steps to reproduce:
1. create New Document in Nextcloud
2. use menu Insert > Image... > choose a png image from nextcloud files > click Choose
3. observe child process segfaulting
Comment 1 Martin Milata 2020-01-09 01:34:35 UTC 
Created attachment 157022 [details]
journald snippet
Comment 2 Aron Budea 2020-01-24 08:06:45 UTC 
I tested with a CODE 4.2.0-3 install, and didn't get any crash when inserting an image. The point of the crash seems to indicate this could be related to an unverifiable (eg. self-signed) certificate, though I haven't seen it crash, just not work in that case (it tries to show a confirmation dialog in core that isn't routed to the UI).

If the setup indeed uses some kind of self-signed certificate, I'd suggest trying with a proper certificate.
Comment 3 Martin Milata 2020-01-28 16:50:49 UTC 
Thank you very much for looking into this! I've tested it with nginx proxy configured to use LetsEncrypt certificate and haven't seen the crash since. Will update if I find out any new information.
Comment 4 Martin Milata 2020-01-30 16:36:13 UTC 
I believe the root cause is the same as tdf#129895, closing this as a duplicate.

*** This bug has been marked as a duplicate of bug 129895 ***