Bug 101400 - LO on Linux will not open SMB/CIFS hosted remote computer's file after recent updates
Summary: LO on Linux will not open SMB/CIFS hosted remote computer's file after recent...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.0.4 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-09 00:13 UTC by LKeithJordan
Modified: 2016-09-17 17:53 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 LKeithJordan 2016-08-09 00:13:14 UTC
Version: 5.2.0.4
Build ID: 1:5.2.0~rc4-0ubuntu1~trusty1
CPU Threads: 2; OS Version: Linux 3.19; UI Render: default; 
Locale: en-US (en_US.UTF-8)

Last updated 2016.0803 and 2016.0808

OS: Linux Mint 17.3 Cinnamon 64-bit version 2.8.8

Processor: Intel Core 2 Duo CPU T7700 @ 2.40GHz x 2
Memory: 2.0GiB

This bug report is similar to, but different from, #100055, so I am opening a new bug report.

I haven't made extensive tests (and I have not tested LO on my Win7 machine for this issue), but LO on my Linux machine has developed a problem since the most recent LO updates.

I can still connect my Linux machine to my Win7 machine, access folders, AND OPEN NON-LO files via the File Manager, but I cannot open LO files via File Manager and the remote connection. I can, however, transfer these files from the Win7 machine to the Linux machine and open them via the remote connection and File Manager.

I tried to open remote files in LO Calc via File > Open Remote File..., but I am still learning LO and Linux and was unable to quickly set up the remote service and get it to work for me. Perhaps with more time... -- but my schedule is full right now.

A quick search on the web indicates similar bugs have appeared on at least two or three separate occasions in the past after software updates.
Comment 1 LKeithJordan 2016-08-09 00:16:46 UTC
(In reply to LKeithJordan from comment #0)
> Version: 5.2.0.4
> Build ID: 1:5.2.0~rc4-0ubuntu1~trusty1
> CPU Threads: 2; OS Version: Linux 3.19; UI Render: default; 
> Locale: en-US (en_US.UTF-8)
> 
> Last updated 2016.0803 and 2016.0808
> 
> OS: Linux Mint 17.3 Cinnamon 64-bit version 2.8.8
> 
> Processor: Intel Core 2 Duo CPU T7700 @ 2.40GHz x 2
> Memory: 2.0GiB
> 
> This bug report is similar to, but different from, #100055, so I am opening
> a new bug report.
> 
> I haven't made extensive tests (and I have not tested LO on my Win7 machine
> for this issue), but LO on my Linux machine has developed a problem since
> the most recent LO updates.
> 
> I can still connect my Linux machine to my Win7 machine, access folders, AND
> OPEN NON-LO files via the File Manager, but I cannot open LO files via File
> Manager and the remote connection. I can, however, transfer these files from
> the Win7 machine to the Linux machine and open them via the remote
> connection and File Manager.
> 
> I tried to open remote files in LO Calc via File > Open Remote File..., but
> I am still learning LO and Linux and was unable to quickly set up the remote
> service and get it to work for me. Perhaps with more time... -- but my
> schedule is full right now.
> 
> A quick search on the web indicates similar bugs have appeared on at least
> two or three separate occasions in the past after software updates.

CORRECTION TO ORIGINAL POST:
I meant to say "I can, however, transfer these files via the remote connection from the Win7 machine to the Linux machine and open them and File Manager." Sorry for any confusion.
Comment 2 Aron Budea 2016-08-09 00:51:02 UTC
I'm a bit confused about some details here.
You're saying that accessing files on a remote computer was working in the previous version of LibreOffice you had, but not working anymore, is that correct? Which was the previous version you were using, and what is the "remote connection" you mentioned in the first part of the report? (is it samba?) Also, what happens exactly now, when it doesn't work?
Comment 3 LKeithJordan 2016-08-09 13:25:19 UTC
(In reply to Aron Budea from comment #2)
> I'm a bit confused about some details here.
> You're saying that accessing files on a remote computer was working in the
> previous version of LibreOffice you had, but not working anymore, is that
> correct? Which was the previous version you were using, and what is the
> "remote connection" you mentioned in the first part of the report? (is it
> samba?) Also, what happens exactly now, when it doesn't work?

No, you are not correct. Apparently, I was not clear. Please let me try again to explain the problem.

First let me note that my computer experience goes back to the MS-DOS days -- so I am adept with both GUI desktop and CLI use. However, I only began using Linux a few months ago. I loaded it to one of my machines to see if moving from Windows to Linux would be viable for my particular business.

My schedule since loading Linux Mint has permitted only limited exploration. I like much of what I have seen so far, but I am still early in the learning curve. Please excuse and translate if any of my terminology or explanation is not quite "Linux-appropriate."

Second, let me describe the portion of my work environment that is affected. I have two laptops.

The MSI machine is a gaming laptop customized for business use. It is currently running Windows 7.

The Toshiba laptop is an older business-class machine. I removed Vista a few months ago and replaced it with Linux Mint. The current OS is Mint 17.3.

I have shared folders on the Windows 7 machine with the Linux machine. I usually connect the Linux machine to the Win7 shared folders by clicking the  Files icon on the taskbar, selecting File > Connect to Server... from the menu, and entering the required information to complete the connection and gain remote access.

Once I have accessed the desired remote folder, I can open remote files by double-clicking them, or by right-clicking them and choosing the desired application.

Now let's discuss the current situation. For quite some time now, I have been opening remote files via File Manager and modifying them on the Linux machine while I work with other applications on the Win7 machine. The primary applications used on the Linux machine to modify the remote files have been LibreOffice and a PDF editor. As indicated in my original post, I am currently using LO 5.2.0.4.

Recently (on 2016.0803 and 2016.0808), LibreOffice was updated from the PPA. I can provide further information from dpkg.log if necessary.

After the 2016.0803 LO update, I left the office and did not try to access remote files again until after the 2016.0808 LO update. Before these updates, I had no problem opening and using remote files using LO as described earlier.

Now, LO will no longer open remote files as described -- although the PDF editor continues to function as before. On the other hand, I can copy remote files to the Linux machine and open them as local files via File Manager in LO with no problem.

I did some quick research on the web and found that this problem has happened before -- and on more than one occasion:

>LO version 4.1.3:
https://ask.libreoffice.org/en/question/26729/413-wont-open-files-over-the-network/

>LO version 4.4:
http://askubuntu.com/questions/634472/cant-open-files-through-the-network

(Reading the thread, the problem also appeared in LO version 4.2.8.2. The problem seemed fixed in LO version 4.4.5.2, but was found again in 5.1.3.2.)

>LO version 5.0.0.5:
https://www.reddit.com/r/libreoffice/comments/3ij405/libreoffice_cannot_open_files_on_a_network/?st=irngtr8a&sh=bbfe4103

>and now, LO version 5.2.0.4 (my report).

I have not yet attempted the possible fix mentioned in some the threads shown. Frankly, I don't have time right now -- and the lack of success indicated by some posters doesn't give me much encouragement to spend the time trying.

I have considered trying to roll-back the updates, but this, too, will take time to learn that I just don't have right now. For now, I'll probably just copy the files to the local Linux machine and return the modified files to the Win7 at the end of each day. It's not an optimal solution, but at least it will work until the bug is fixed (again).

Hopefully, this report will help get the bug fixed once and for all.
Comment 4 Alex Thurgood 2016-08-09 15:04:04 UTC
LKeithJordan : thank you for your explanation, which was very clear.

You are opening files on a Windows share hosted on a Win 7 machine from the Linux machine (LM17.3).

You are using a PPA version for this, and not the TDF official download - there might be some slight differences here, so worth experimenting if you can with a parallel installation of an official TDF latest production release of LO (see the LibreOffice wiki for how to install in parallel) and test whether the problem is also present in that version.

You are correct in noting that previous reports of similar problems have been noted here in bugzilla.

Have you had any updates to the Win7 machine recently ? There is/was a known issue with some versions of Windows (Win8/Win10 ?) that prevented CIFS/SMB fileshares from playing nicely when shared across a LAN with Linux machines running LO. This was linked to file locking on the Windows host.

As a first step, could you try it with a TDF official download version of LO on the LM17.3 machine to see if that solves the problem, in which case we can point the finger at the PPA version ?

Setting to NEEDINFO, please change back to UNCONFIRMED once you have reported your findings.
Comment 5 LKeithJordan 2016-08-10 13:48:23 UTC
(In reply to Alex Thurgood from comment #4)
> LKeithJordan : thank you for your explanation, which was very clear.
> 
> You are opening files on a Windows share hosted on a Win 7 machine from the
> Linux machine (LM17.3).
> 
> You are using a PPA version for this, and not the TDF official download -
> there might be some slight differences here, so worth experimenting if you
> can with a parallel installation of an official TDF latest production
> release of LO (see the LibreOffice wiki for how to install in parallel) and
> test whether the problem is also present in that version.
> 
> You are correct in noting that previous reports of similar problems have
> been noted here in bugzilla.
> 
> Have you had any updates to the Win7 machine recently ? There is/was a known
> issue with some versions of Windows (Win8/Win10 ?) that prevented CIFS/SMB
> fileshares from playing nicely when shared across a LAN with Linux machines
> running LO. This was linked to file locking on the Windows host.
> 
> As a first step, could you try it with a TDF official download version of LO
> on the LM17.3 machine to see if that solves the problem, in which case we
> can point the finger at the PPA version ?
> 
> Setting to NEEDINFO, please change back to UNCONFIRMED once you have
> reported your findings.

Hi Alex. No, There have been no updates to my Win7 during the period in question.

As for parallel installation, I briefly reviewed the Wiki. Before I attempt, I have a couple of questions.

FIRST, it appears to me that I will have to open the remote file from within the parallel LO Calc in order to test. IS THIS CORRECT?

If the previous assumption is correct, please continue below.

SECOND, I need some guidance, and so far I haven't found it on my own.

In the File Services window, I set the Type as "Windows Share." I entered the IP address of the Win7 machine for the Host (the Port is disabled).

I AM NOT SURE WHAT TO ENTER FOR THE "SHARE." I have tried a) specifying the workgroup and b) specifying the Windows shared folder, but I'm not sure that either is correct.

I entered the user and password as I do in the connection process I detailed earier (since I am using the Cinnamon desktop, am I correct that Nemo is the file manager?) and I leave the Label as auto-filled. WHAT SHOULD I ENTER FOR THE ROOT?

Thanks for your help and patience with a Linux/LO newb.
Comment 6 Alex Thurgood 2016-08-10 16:35:09 UTC
(In reply to LKeithJordan from comment #5)

> Hi Alex. No, There have been no updates to my Win7 during the period in
> question.
> 
> As for parallel installation, I briefly reviewed the Wiki. Before I attempt,
> I have a couple of questions.
> 
> FIRST, it appears to me that I will have to open the remote file from within
> the parallel LO Calc in order to test. IS THIS CORRECT?
> 

Hi,

Ah yes, I forgot that double-clicking would launch the system default install of LO rather than the parallel one.

Forget the LO File Services dialog from within LO, I can not figure it out, the help is useless (in fact inexistant) and I have been trying all day on and off to get this to work properly with a link to network stored templates).

I am assuming that your file manager allows you to see the shared folder as you mentioned that you can access this with :

"I usually connect the Linux machine to the Win7 shared folders by clicking the  Files icon on the taskbar, selecting File > Connect to Server... from the menu, and entering the required information to complete the connection and gain remote access."

Try this :
1) Open a terminal and type in the full path to the parallel LO executable :

e.g. pathtomyparallelLOinstallation/program/soffice 

Do not press enter for the moment

2) Open your file manager network folder and drag and drop a LO file from there onto the terminal window. It should add the file name to be opened to the end of the LO start command, and now you can press enter.

3) This should start the parallel version of LO and load the file. Note however that if your path to the file has spaces in it, you might need to surround the complete file path and name with double-quotes (otherwise it might fail to load when it encounters a space in the file path), i.e. something like 

pathtomyparallelLOinstallation/program/soffice "/WIN7/SHARED FILES/worksheets/myworksheet.ods"

HTH
Comment 7 LKeithJordan 2016-09-09 22:20:53 UTC
Alex:

I finally took a moment and uninstalled LO, then installed from TDF. The problem is GONE.

Before we assume the PPA LO install is at fault, I would mention that I made another change today -- this to the Linux boot process. I recently discovered a FAIL during boot load of SMB/CIFS. During research, I found that this was a default not needed for STANDALONE server installs. 

I created the file "samba-ad-dc.override" with "manual" as its content. The FAIL during boot disappeared.

I'll leave it to the experts here to conjecture whether one or both of my actions fixed the problem. My personal opinion is that the PPA install of LO was the problem.

In any event, thanks for your help. To make sure I don't mess up the reporting system, I'll leave it to you to mark the status "RESOLVED."


Take care,
--Keith
L. Keith Jordan
Comment 8 LKeithJordan 2016-09-10 12:02:22 UTC
Sorry. Forgot to change status to UNCONFIRMED.
Comment 9 Julien Nabet 2016-09-17 17:53:40 UTC
(In reply to LKeithJordan from comment #7)
> ...:
> I'll leave it to the experts here to conjecture whether one or both of my
> actions fixed the problem. My personal opinion is that the PPA install of LO
> was the problem.
> ...
If you've got some extra time, you can reinstall PPA LO to be sure.
However, since it's ok now (and without specific fix), let's put this one to WFM.