Bug 106778 - LibreOffice show Splash Screen and not run
Summary: LibreOffice show Splash Screen and not run
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Splash-Screen
  Show dependency treegraph
Reported: 2017-03-26 16:48 UTC by Renat
Modified: 2018-07-03 14:19 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

strace -f -o ~/outputfile libreoffice5.2 (9.07 MB, text/plain)
2017-03-26 16:49 UTC, Renat
strace -f -o ~/outputfile53 libreoffice5.3 (732.91 KB, application/gzip)
2017-03-26 17:03 UTC, Renat
dump.ini (314.42 KB, application/vnd.tcpdump.pcap)
2017-03-26 17:19 UTC, Renat

Note You need to log in before you can comment on or make changes to this bug.
Description Renat 2017-03-26 16:48:42 UTC
LibreOffice show Splash Screen and not run

$cat /etc/redhat-release 
Fedora release 24 (Twenty Four)

I probe this with:
LibreOffice_5.2.5.1 and LibreOffice_5.3.1.2

I probe with two version java
$ java -version
java version "1.7.0_79"

java openjdk

Steps to Reproduce:
1. rm -rvf ~/.config/libreoffice/*
2. strace -f -o ~/outputfile libreoffice5.2
run: show splash screen and closed
3. file output include at letter

Actual Results:  
Not started

Expected Results:
Not started

Reproducible: Always

User Profile Reset: No

Additional Info:

User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Renat 2017-03-26 16:49:29 UTC
Created attachment 132151 [details]
strace -f -o ~/outputfile libreoffice5.2

strace -f -o ~/outputfile libreoffice5.2
Comment 2 Renat 2017-03-26 17:02:51 UTC
$strace -f -o ~/outputfile53 libreoffice5.3 
$java -version
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-b14)
OpenJDK 64-Bit Server VM (build 25.121-b14, mixed mode)
$libreoffice5.3 -version
Warning: -version is deprecated.  Use --version instead.
LibreOffice e80a0e0fd1875e1696614d24c32df0f95f03deb2

(Second attachment)
Comment 3 Renat 2017-03-26 17:03:40 UTC
Created attachment 132153 [details]
strace -f -o ~/outputfile53 libreoffice5.3

New Java
New LibreOffice
strace -f -o ~/outputfile53 libreoffice5.3
Comment 4 Renat 2017-03-26 17:19:02 UTC
Created attachment 132154 [details]

Comment 5 Renat 2017-03-26 17:45:09 UTC
If I remove and install LibreOffice from official Fedora repository:
LibreOffice 10(Build:2)

They are work and started.
Comment 6 Xisco Faulí 2017-03-28 07:31:23 UTC
are you using GTK3? Does LibreOffice get launched if you run it like 'SAL_USE_VCLPLUGIN=gtk soffice' ?
Comment 7 Renat 2017-04-01 15:35:22 UTC
(In reply to Xisco Faulí from comment #6)
> are you using GTK3? Does LibreOffice get launched if you run it like
> 'SAL_USE_VCLPLUGIN=gtk soffice' ?

After test with this LibreOffice started. Why? Whe is not started before?
Comment 8 Renat 2017-04-01 15:35:49 UTC
Tested with this parameters. Thats all ok.
Comment 9 Xisco Faulí 2017-11-15 10:50:46 UTC
Hi Renat,
Is this issue still reproducible with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
Comment 10 QA Administrators 2018-05-30 16:39:47 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2018-07-03 14:19:24 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team