Loaded 13.2 (KDE) this week end and have been having all sorts of fun getting things like I want (been a while since I last played with Suse).
One thing I can’t get my head around is the fact that I can get onto our main server in the office (Windows Server 2008) and see everything as per normal. What I can’t do is open any of my documents. The pointer indicates that it’s busy with something for a while and then … nothing.
I’m assuming it’s a permissions issue as when I use Dolphin with SU privileges it works fine, but I don’t want to permanently use that, could be dangerous
I can copy the file to my home folder and then I am able to open it. I also right-clicked to check permissions and both show me as User and Group as users.The file on the server does not indicate anything next to read/write for user or group etc.
On 02/03/2015 05:56 AM, rafiqc wrote:
> Hi ab
> I can copy the file to my home folder and then I am able to open it. I
> also right-clicked to check permissions and both show me as User and
> Group as users.The file on the server does not indicate anything next to
> read/write for user or group etc.
> What does this indicate?
It’s not a permissions problem, at least for reading, since
copying/opening should use the same read permissions
Perhaps it’s an application issue. If you open (presumably)
LibreOffice (Alt+F2: soffice) and then choose to ‘Open’ the file (vs.
clicking on it somewhere to open it) does that work?
What happens if you try to open the file from a
shell/terminal/commandline, assuming you have the volume where the file
resides mounted somehow?
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
It did work when I was running Ubuntu still, unless there are differences in functionality between the two LibreOffice’s.
I have tried to use Konquerer also and it does the same.
I tried mounting the share as per your suggestion (and some other suggestions from the wiki) and I’m just not getting any joy. When running the command with the “-t” it displays the “help page” and when I try the “-a” switch it does not give me any errors or anything, but still does not mount it.
For some reason, the openSUSE version of LibreOffice cannot write to a Windows directory. It cannot create the lock file for a document, so does not open the file. This occurs with openSUSE 13.1, 32-bit, KDE, LibreOffice 4.3; accessing a flie on a Windows 7 machine. It appears LibreOffice is not doing samba. In LibreOffice, if I try to use its Open File feature, I have found no way the navigate to a file on a Windows machine on the network, even though Dolphin gets there.
When I use Dolphin on machine 1 to go to a directory on a Windows machine, machine 2, it can move files on and off and delete them. If I click a file, I get the same response described by OP.
If I reboot machine 1 into Windows 7 and navigate to a directory on machine 2, right-clicking and selecting open with LibreOffice, it does open the document on machine 1 (now in Windows), and creates the lock file in the machine 2 directory.
Maybe there is a setting somewhere in the openSUSE version of LibreOffice that enables or disables samba. Anyone know what’s happening?