Bug 129395 - Libreoffice6.3.4 crashes on opening as a user but not as root
Summary: Libreoffice6.3.4 crashes on opening as a user but not as root
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.3.4.2 release
Hardware: x86-64 (AMD64) other
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: wantBacktrace
Depends on:
Blocks:
 
Reported: 2019-12-13 22:03 UTC by leon244@comcast.net
Modified: 2020-01-29 14:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
gdbtrace.log on running 6.5.0 debug (266.88 KB, text/x-log)
2020-01-21 15:45 UTC, leon244@comcast.net
Details

Note You need to log in before you can comment on or make changes to this bug.
Description leon244@comcast.net 2019-12-13 22:03:38 UTC
Libreoffice 6.3.4 crashes when I try to open it. I have to prepend SAL_USE_VCLPLUGIN=gen  to get it to open. However it does open if I run it as root.
I am using Mageia 7
Comment 1 Julien Nabet 2019-12-14 08:11:43 UTC
Could you give a try to https://wiki.documentfoundation.org/QA/FirstSteps ?
Comment 2 leon244@comcast.net 2019-12-14 11:36:33 UTC
I did try removing my profile but that did not change the problem. Also rendering is not by OpenGL
thank you
Comment 3 Julien Nabet 2019-12-14 11:54:11 UTC
Thank you for your feedback.

Would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Comment 4 leon244@comcast.net 2019-12-14 14:02:00 UTC
Thank you. As per the instructions I ran "soffice --backtrace"
No gdbtrace.log was created. The feedback from the CLI is as follows:
[user is leon]$>/opt/libreoffice6.3/program/soffice --backtrace
GNU gdb (GDB) 8.2-8.mga7 (Mageia release 7)
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-mageia-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /opt/libreoffice6.3/program/soffice.bin...(no debugging symbols found)...done.
/opt/libreoffice6.3/program/gdbtrace: No such file or directory.

(gdb) run
Starting program: /opt/libreoffice6.3/program/soffice.bin --backtrace
Missing separate debuginfos, use: debuginfo-install libreoffice6.3-6.3.4.2-2.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[Detaching after fork from child process 19190]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000001110 in ?? ()
(gdb) quit
A debugging session is active.

        Inferior 1 [process 19185] will be killed.

Quit anyway? (y or n) y

ih ope this is useful. thank you
Comment 5 Julien Nabet 2019-12-14 14:13:03 UTC
When you see "??" you can type "c" (for "continue", of course without quotes)

At a moment, there won't be "??" or "?" but something else.
At this moment, type "bt"
Comment 6 Julien Nabet 2019-12-14 14:19:48 UTC
(In reply to Julien Nabet from comment #5)
> When you see "??" you can type "c" (for "continue", of course without quotes)
> 
> At a moment, there won't be "??" or "?" but something else.
> At this moment, type "bt"
BTW, I updated the doc to take this into account
Comment 7 leon244@comcast.net 2019-12-14 15:39:03 UTC
So I am confused. to me the instructions say that if you are returned to a (gdb) prompt type "quit". I did that.

I reran the backtrace and this time typed 'bt' at the prompt and got this:

(gdb) bt
#0  0x0000000000001110 in  ()
#1  0x00007ffff7fe512a in call_init.part () at /lib64/ld-linux-x86-64.so.2
#2  0x00007ffff7fe5226 in _dl_init () at /lib64/ld-linux-x86-64.so.2
#3  0x00007ffff7fe8c03 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#4  0x00007ffff3867ac5 in _dl_catch_exception () at /lib64/libc.so.6
#5  0x00007ffff7fe84fa in _dl_open () at /lib64/ld-linux-x86-64.so.2
#6  0x00007ffff274f246 in dlopen_doit () at /lib64/libdl.so.2
#7  0x00007ffff3867ac5 in _dl_catch_exception () at /lib64/libc.so.6
#8  0x00007ffff3867b3f in _dl_catch_error () at /lib64/libc.so.6
#9  0x00007ffff274f945 in _dlerror_run () at /lib64/libdl.so.2
#10 0x00007ffff274f2c6 in dlopen () at /lib64/libdl.so.2
#11 0x00007ffff3989373 in osl_loadModule () at /opt/libreoffice6.3/program/libuno_sal.so.3
#12 0x00007ffff396674c in osl_loadModuleRelative () at /opt/libreoffice6.3/program/libuno_sal.so.3
#13 0x00007ffff698ab48 in  () at /opt/libreoffice6.3/program/libmergedlo.so
#14 0x00007ffff698af02 in  () at /opt/libreoffice6.3/program/libmergedlo.so
#15 0x00007ffff6907b27 in InitVCL() () at /opt/libreoffice6.3/program/libmergedlo.so
#16 0x00007ffff6909725 in ImplSVMain() () at /opt/libreoffice6.3/program/libmergedlo.so
#17 0x00007ffff58bc815 in soffice_main () at /opt/libreoffice6.3/program/libmergedlo.so
#18 0x000000000040069b in  ()
#19 0x00007ffff374eb0b in __libc_start_main () at /lib64/libc.so.6
#20 0x00000000004006cf in  ()

I still ended back at the (gdb) prompt and  typed 'quit' and got the message:

(gdb) quit
A debugging session is active.

        Inferior 1 [process 7303] will be killed.

Quit anyway? (y or n) y

Should I respond 'n' and just let it run?

If I respond 'y' then there is no gdbtrace.log file created
Comment 8 Julien Nabet 2019-12-14 16:11:57 UTC
I don't know how to be more clear so I can't help you then => uncc myself.
Comment 9 Xisco Faulí 2020-01-21 12:53:58 UTC
Could you please download a debug build from here: http://dev-builds.libreoffice.org/daily/master/ ( the ones with -dbg at the end ), and get a backtrace as explain here: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace ?
Comment 10 leon244@comcast.net 2020-01-21 15:45:22 UTC
Created attachment 157308 [details]
gdbtrace.log on running 6.5.0 debug
Comment 11 leon244@comcast.net 2020-01-21 15:48:05 UTC
As per Xisco Fauli, I ran the debug version of 6.5.0. This did not crash like 6.3.4 did, but I created the gdbtrace.log as requested and it is attached.
Comment 12 QA Administrators 2020-01-22 03:39:13 UTC Comment hidden (obsolete)
Comment 13 leon244@comcast.net 2020-01-29 13:53:17 UTC
This is no longer a problem in 6.4.0.3. It works as usual
Comment 14 Xisco Faulí 2020-01-29 14:02:59 UTC
(In reply to leon244@comcast.net from comment #13)
> This is no longer a problem in 6.4.0.3. It works as usual

Thanks for retesting the issue with the latest version.
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.