Bug 144666 - LO crashes when trying to print any document in Ubuntu 16
Summary: LO crashes when trying to print any document in Ubuntu 16
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
7.0.3.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: wantBacktrace
Depends on:
Blocks:
 
Reported: 2021-09-22 14:35 UTC by Len Testa
Modified: 2021-09-24 18:55 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
gdb backtrace as requested (1003 bytes, text/x-log)
2021-09-23 12:27 UTC, Len Testa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Len Testa 2021-09-22 14:35:12 UTC
Description:
LibreOffice crashes when I attempt to print any document, of any type, in Writer, Calc, etc.

I've tried re-creating my user profile from scratch.  I've also tried disabling hardware acceleration in safe mode.

Steps to Reproduce:
1.Open a blank document
2.Type a sentence such as "This is a line of text." 
3.Press <CTRL-P> and the app will crash.

Actual Results:
The app crashed.

Expected Results:
I should've seen the Print dialog.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.0.3.1
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: CL
Comment 1 Xisco Faulí 2021-09-22 15:17:25 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 2 Len Testa 2021-09-22 18:14:39 UTC
The bug does not occur when using LO 7.1.6.2.  However, I must run the following command in order to get that version of LO to run:

export SAL_USE_VCLPLUGIN=gen

If I don't issue that command or I use 'kf5' instead of 'gen' then LO crashes after displaying the startup screen.



Version info:
Version: 7.1.6.2 / LibreOffice Community
Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 3 Julien Nabet 2021-09-22 19:18:09 UTC
2 things you can try:
- upgrade to last Ubuntu version 21.04 or at least last LTS (20.04)
- try to retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Comment 4 Len Testa 2021-09-23 12:27:09 UTC
Created attachment 175219 [details]
gdb backtrace as requested
Comment 5 Len Testa 2021-09-23 12:28:25 UTC
Backtrace attached.  To get this to happen, I have to comment out the line that reads "export SAL_USE_VCLPLUGIN=gen".

I can try upgrading from Ubuntu 16 to 20. That seems like it'll take some time and potentially break a bunch of other things, so I'm hesitant to do it.
Comment 6 Julien Nabet 2021-09-23 19:59:35 UTC
There's no backtrace in your file so we can't do anything with it.

So 7.0.3 crashes with gtk3 and 7.1.6 crashes with kf5.
BTW, I consider https://www.libreoffice.org/download/download/ ok for Windows or MacOs but for Linux, it's more for distrib repository maintainers.
Indeed, dependencies must be taken into account.

I think either you try again to retrieve a backtrace. (There shouldn't be "No stack" in it) or uninstall all LO versions from TDF and from your repository + clean you LO profile, then upgrade to last LTS Ubuntu (20.04) and install again LO from Ubuntu repo.
Comment 7 Len Testa 2021-09-24 14:19:32 UTC
Ah, I thought that output file would be helpful.  It's odd that --backtrace didn't create a backtrace. I'm not going to open at ticket on that though. :)

I'm okay with closing this ticket.  The issue seems to be somewhere in Ubuntu 16, which isn't the most recent rev.  And the ticket has documented a work-around, in case anyone else can benefit from it.  Upgrading seems like the permanent fix.

Thank you.
Comment 8 Julien Nabet 2021-09-24 18:55:43 UTC
Let's rather put WORKSFORME since there's no specific patch here to fix this.