Bug 105761 - libreoffice-gtk3 causing longer time to open documents from file explorer on Ubuntu systems
Summary: libreoffice-gtk3 causing longer time to open documents from file explorer on ...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.0.2 rc
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-05 06:49 UTC by Ljiljan
Modified: 2019-03-21 11:25 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ljiljan 2017-02-05 06:49:35 UTC
Description:
After update to LibreOffice 5.3, it takes longer time to open documents from Nautilus file explorer (Ubuntu 16.04) than in previous versions (comparing to previous version and comparing to time for starting the libreoffice and then opening the file). In case of some documents, LibreOffice does not manage to open it. 

I tried to restart profile, to disable Hardware accelerator and to increase memory in View -> Memory settings but it didn't help.

Steps to Reproduce:
1. Open Nautilus File explorer while all LibreOffice windows are closed
2. Select LibreOffice document to open
3. Wait

Actual Results:  
It takes longer to open the document. I compare it to my previous experiences (in LibreOffice 5.2. as well as to the time it takes to start the libreoffice and then to open the file). Some documents are not opened and I am forced to close LibreOffice by sending so called "kill signal".

Expected Results:
It takes the same time as in previous versions or even faster. 


Reproducible: Always

User Profile Reset: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Builds ID: LibreOffice 5.3.0.3


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Comment 1 Ljiljan 2017-02-05 06:50:44 UTC
If I first start LibreOffice (it takes two seconds), opening the file from File -> Open is not the problem.
Comment 2 Ljiljan 2017-02-05 11:14:05 UTC
Workaround is to enable Quickstart, so LibreOffice is always running in the background and no this problem. 

But so far I wasn't able to open some LibreOffice documents even from command prompt ("libreoffice document.odt"). So it is not Nautilus related problem.
Comment 3 Ljiljan 2017-02-14 06:41:17 UTC
In my case, I discovered that libreoffice-gtk3 when removed the problem does not exist. So I believe this problem is only Gnome-specific issue. People using other Linux distributions or Windows users should not experience this.
Comment 4 Jean-Baptiste Faure 2017-02-21 17:25:26 UTC
I do not experience this behavior with LO 5.3.0 from the PPA provided by the Ubuntu LibreOffice team.

1/ Do you use Unity or another window manager?
2/ As you have the possibility to use the quickstart, I guess you installed the generic Linux version of LibreOffice (build by TDF). I suggest you to replace it by the version from the LibreOffice PPA. Does that fix the problem?

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the infos are provided.

Best regards. JBF
Comment 5 Ljiljan 2017-02-22 07:59:20 UTC
(In reply to Jean-Baptiste Faure from comment #4)
> I do not experience this behavior with LO 5.3.0 from the PPA provided by the
> Ubuntu LibreOffice team.
> 
> 1/ Do you use Unity or another window manager?

Yes, I use Ubuntu with Unity.

> 2/ As you have the possibility to use the quickstart, I guess you installed
> the generic Linux version of LibreOffice (build by TDF). I suggest you to
> replace it by the version from the LibreOffice PPA. Does that fix the
> problem?

I installed LibreOffice from http://ppa.launchpad.net/libreoffice/libreoffice-prereleases/ubuntu


but QuickStarter option was missing for some reasons. 

> 
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' once the infos are provided.
> 
> Best regards. JBF

Since at the moment I am the only one affected (and who knows why), we could leave it with 'NEEDINFO'. I will try to find causes and/ or solutions. If someone else have similar problem, they should change it.
Comment 6 Jean-Baptiste Faure 2017-02-22 08:10:17 UTC
(In reply to Ljiljan from comment #5)
> [...]
> Since at the moment I am the only one affected (and who knows why), we could
> leave it with 'NEEDINFO'.

No, the correct status in this case is UNCONFIRMED.

Best regards. JBF
Comment 7 Xisco Faulí 2017-11-01 22:54:11 UTC
> Steps to Reproduce:
> 1. Open Nautilus File explorer while all LibreOffice windows are closed
> 2. Select LibreOffice document to open

Once you select the document, what happens if you move the cursor? Does it take the same amount of time?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the question is answered
Comment 8 Ljiljan 2017-11-03 08:13:01 UTC
(In reply to Xisco Faulí from comment #7)
> > Steps to Reproduce:
> > 1. Open Nautilus File explorer while all LibreOffice windows are closed
> > 2. Select LibreOffice document to open
> 
> Once you select the document, what happens if you move the cursor? Does it
> take the same amount of time?
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' once the question is answered

The problem is not in  Nautilus. It starts LibreOffice... but then LibreOffice is not responding for some time. I tried moving the cursors but it did not help.

However, I noticed something. Opening ODT file from Nautilus is just fine (normal time) but opening DOC file takes longer time (like 20-30 seconds)... when libreoffice-gtk3 is removed, no such problem! Everything is tested on my Ubuntu 16.04 with Unity.
Comment 9 Ljiljan 2017-11-03 08:18:02 UTC
.. however, as Ubuntu Unity is not going to be default user interface, we should check if this is only Unity related. So investing someone's effort in fixing this is probably not worth his/her time.
Comment 10 Ljiljan 2017-11-08 16:55:23 UTC
the problem appears only when no LibreOffice window is opened. 

I opened document from terminal (libreoffice filename.odt).... this is the message I receive:
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments

However, when LibreOffice is opened and I try to open the file from the terminal, no such message. 

I hope this could be useful in detecting the possible causes of error.
Comment 11 Jean-Baptiste Faure 2018-06-20 21:02:32 UTC
Do you still encounter this issue with the current LO version provided by Ubuntu PPA ? In my case with Ubuntu 16.04 I get the version 6.0.4.

Status set to NEEDINFO, please set it back to UNCONFIRMED once requested
informations are provided.

Best regards. JBF
Comment 12 QA Administrators 2019-01-11 15:23:08 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2019-03-21 11:25:36 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

MassPing-NeedInfo-20190321