-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Files from a network folder (smb) #111
Comments
I have experienced a similar issue. I'm on Debian 12 using KDE Plasma. Everything is up to date package-wise. When opening a file from an Samba share hosted on a Windows server through Dolphin, the file opens normally. However, after installing kio-fuse package to allow Samba files to be mounted locally on my system, a blank "Word" document opens up when trying to open the same file. After installing the .deb package and testing the same operation, the file opened normally and saved normally. This was done a a fresh installation of Debian 12, so I think it is clearly a Flatpak bug. |
Same issue here, after installing a fresh fedora with kde and only office from discover. Navigating to a smb share using dolphin (KIO linked share) a blank file opens. Inconvenient for normal use: have to mount the smb share by comandline or other means, each time the user changes on a pc - and for each eval pc at our company (we evaluate moving away from windows). Is there any extra config needed? |
I'm using 8.01 here. I was able to open a file from a smb folder, but saving did not work. After saving the file and reopening it the changes were not applied. LibreOffice doesn't have the same issue though. |
As a Plasma desktop user, I'm unable to save or open files on a remote SAMBA share with OnlyOffice. The Open and Save As dialog box do not show my bookmarked servers, nor can I navigate to them via URL. Also double clicking on a remote file via my file manager open OnlyOffice with just a blank file.
|
When opening a file from a network folder (smb), an empty document opens.
The text was updated successfully, but these errors were encountered: