Download it now!
Bug 127724 - Multiple instances of LibreOffice from separate machines (shared homedir) not working
Summary: Multiple instances of LibreOffice from separate machines (shared homedir) not...
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Network
  Show dependency treegraph
 
Reported: 2019-09-23 17:58 UTC by Eric McAlvin
Modified: 2020-11-20 20:23 UTC (History)
2 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 Eric McAlvin 2019-09-23 17:58:32 UTC
Description:
If I try to open another instance of LibreOffice on another machine (with my home directory shared via NFS), when one is already running, the second instance only flashes the LibreOffice splash banner (like it is stuck in a loop). 

In another environment that I have, which is running an older version, 6.1.5.2-lp150.2.10.1.x86_64 (this is an openSUSE 15.0 Leap package in both environments), it works correctly by first telling me that another instance is accessing my personal settings, and asking if I want to continue.

Note that if I start libreoffice on the second instance in safe mode, it works. I have already reset my libreoffice profile and that did not correct the issue.

Steps to Reproduce:
1. Start LibreOffice on machine A (homedir is on NFS) via 'libreoffice' command.
2. Start 2nd instance of LibreOffice on machine B (homedir is on same NFS volume) via 'libreoffice' command.

Actual Results:
2nd instance won't start, looks to be stuck in a loop and just showing the splash/banner over and over.  ps shows that oosplash is spawning soffice.bin over and over again (PID changes for soffice.bin but not oosplash during every iteration of the splash banner flashing).

Expected Results:
LibreOffice shows warning 'Either another instance of LibreOffice is accessing your personal settings or your personal settings are locked.... Do you really want to continue?'  Selecting 'Yes' allows you to start the 2nd instance LibreOffice.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
-LibreOffice profile was reset but it did not correct the issue.
-Starting libreoffice --safe-mode allows the 2nd instance to start.
-disabling openGL did not fix the issue.
-Both machines are openSUSE 15.0 Leap (x86_64) with the libreoffice package from that distro. (libreoffice-6.2.6.2-lp150.2.16.1.x86_64)

Version: 6.2.6.2
Build ID: 20(Build:2)
CPU threads: 4; OS: Linux 4.12; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Eric McAlvin 2019-10-23 14:13:21 UTC
I can confirm that this problem also exists in libreoffice-6.2.7.1-lp151.3.6.1.x86_64  (tested on openSUSE Leap 15.1).
Comment 2 Xisco Faulí 2020-11-18 15:23:00 UTC
Hello Eric McAlvin,
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 3 Eric McAlvin 2020-11-18 21:22:37 UTC
(In reply to Xisco Faulí from comment #2)
> Hello Eric McAlvin,
> 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.

I have installed 7.0.3 RPMs from https://www.libreoffice.org/download/libreoffice-fresh/ on 2 test machines that have access to a shared NFS home dir.  The problem did not occur.  However, these test machines were CentOS 7.8 and not openSUSE Leap.

So, as a test, I removed 7.0.3 and installed 6.4.5.2 on those same test machines (as that version has the issue on openSUSE Leap 15.2 (using the RPM provided by openSUSE).  6.4.5.2 did not have the issue either using the RPM from www.libreoffice.org/download (and on CentOS 7.8).  

So it could either be openSUSE is modifying some code in their RPM repackaging, or an OS layer problem.

I am going to try and install 7.0.3 on openSUSE Leap 15.2 using packages from https://www.libreoffice.org/download/libreoffice-fresh/  as well as the packages that come with openSUSE Tumbleweed (as 15.2 comes with 6.4.5.2).
Comment 4 QA Administrators 2020-11-19 04:14:34 UTC Comment hidden (obsolete)
Comment 5 Eric McAlvin 2020-11-20 16:02:27 UTC
(In reply to Eric McAlvin from comment #3)
> (In reply to Xisco Faulí from comment #2)
> > Hello Eric McAlvin,
> > 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.
> 
> I have installed 7.0.3 RPMs from
> https://www.libreoffice.org/download/libreoffice-fresh/ on 2 test machines
> that have access to a shared NFS home dir.  The problem did not occur. 
> However, these test machines were CentOS 7.8 and not openSUSE Leap.
> 
> So, as a test, I removed 7.0.3 and installed 6.4.5.2 on those same test
> machines (as that version has the issue on openSUSE Leap 15.2 (using the RPM
> provided by openSUSE).  6.4.5.2 did not have the issue either using the RPM
> from www.libreoffice.org/download (and on CentOS 7.8).  
> 
> So it could either be openSUSE is modifying some code in their RPM
> repackaging, or an OS layer problem.
> 
> I am going to try and install 7.0.3 on openSUSE Leap 15.2 using packages
> from https://www.libreoffice.org/download/libreoffice-fresh/  as well as the
> packages that come with openSUSE Tumbleweed (as 15.2 comes with 6.4.5.2).

I installed the 6.4.5.2 LibreOffice packages from https://www.libreoffice.org/download/ on openSUSE 15.2 and the problem does NOT occur.  To verify, I removed those and installed the 6.4.5.2 packages provided by openSUSE Leap 15.2 and they DO have the problem.

testusr    30697 31590 23 10:56 pts/1    00:00:00 /usr/lib64/libreoffice/program/soffice.bin
testusr    30704 30697 10 10:56 pts/1    00:00:00 [soffice.bin] <defunct>
testusr    31589  2169  0 10:38 pts/1    00:00:00 /bin/sh /usr/bin/ooffice
testusr    31590 31589  0 10:38 pts/1    00:00:00 /usr/lib64/libreoffice/program/oosplash

Notice the process tree is /bin/sh /usr/bin/ooffice --> /usr/lib64/libreoffice/program/oosplash --which then is stuck in a loop starting child procs --> /usr/lib64/libreoffice/program/soffice.bin --> [soffice.bin] <defunct>

I guess I need to take this up directly with openSUSE, correct?
Comment 6 Eric McAlvin 2020-11-20 20:23:33 UTC
I opened a bug with OpenSUSE on this.  

https://bugzilla.opensuse.org/show_bug.cgi?id=1179034