Created attachment 128586 [details]
error dialog on attempted 'save as'
18.104.22.168 on Archlinux
'Remote Files' Add Service fails for simple SSH or Windows Shares (smb). Attempting to define a service for SSH or Windows Shares access to local network server fails in KDE Frameworks 5.27. This effectively prevents any meaning use or 'save as' of a libreoffice document to local network locations.
Additionally, attempting to save as Network causes a race condition causing soffice-bin to take 100% of the CPU while the 'save as' dialog is open.
I have attached screenshots of the error dialog and the top CPU usage.
Created attachment 128587 [details]
top screenshot showing 100% CPU use while 'save as' dialog open
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 am using Libre Office 5.3.2 on Slackware Linux, and I still can't create an SSH remote-file service.
Whatever options I put into the option window, all I get is a popup that says something like "no such file" (I'm not at home right now, so I can't get the exact message). I can see from my logs that there is no attempt to connect to the remote host.
When I try to edit the service, I have only two lines I can type in (again, I'm not home to recreate the exact window), and the "OK" button is greyed out.
I can successfully delete the service.
Please tell me (as specifically as you can) what further info I can provide.
Created attachment 136576 [details]
Popup error when creating "SSH" remote service
When I try to create an SSH Remote Files service, I immediately get this pop-up error.
Created attachment 136577 [details]
Edit Remote File Service, OK grayed out
When I try to edit the Remote Files service entry, I get this pop-up window. I can type in both fields, but the OK button is greyed out.
Hi David, Eric,
it seems you're using an old version of LibreOffice.
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.
Is this a duplicate of #98897 ? It looks so from the dialogues, but I am hesitant to merge it myself as the CPU usage point is not mentioned in the other BZ entry.
Dear David C. Rankin,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
I have a similar issue. If I try to open a file directly from a GVfsd mount point... Nothing happens. I get the loading notification 'pointer spinner' and a loading splash banner with a progress bar of (what looks like) 10-15%-ish, but Libre Office just exits. I see nothing in any system logs.
To circumvent this, I created soft links to the GVfsd mount points (as I know they have special characters, which some non-POSIX apps fail with) and tried again. This time, after the progress bar stopped at the same place, I got a 'General input/output error while accessing /home/user/.gvfs/softlinkname/path/filename' error box.
I have made suggestions to the GVfsd team to use more compatible characters in the mount points, which has helped with oper applications, but I don't think that is the issue in this case.
- Libre Office 22.214.171.124
- GVfsd 1.28.2
- OS :
Distributor ID: Zorin
Description: Zorin OS 12.4
I will try the latest version of LO and see if anything is different.
Would you like any further information?
Thank you for any help or advice you can give. :)
(In reply to Stin from comment #9)
> I have a similar issue. If I try to open a file directly from a GVfsd mount
> point... Nothing happens. I get the loading notification 'pointer spinner'
> and a loading splash banner with a progress bar of (what looks like)
> 10-15%-ish, but Libre Office just exits. I see nothing in any system logs.
> To circumvent this, I created soft links to the GVfsd mount points (as I
> know they have special characters, which some non-POSIX apps fail with) and
> tried again. This time, after the progress bar stopped at the same place, I
> got a 'General input/output error while accessing
> /home/user/.gvfs/softlinkname/path/filename' error box.
> I have made suggestions to the GVfsd team to use more compatible characters
> in the mount points, which has helped with oper applications, but I don't
> think that is the issue in this case.
> - Libre Office 126.96.36.199
> - GVfsd 1.28.2
> - OS :
> Distributor ID: Zorin
> Description: Zorin OS 12.4
> Release: 12
> Codename: xenial
> I will try the latest version of LO and see if anything is different.
> Would you like any further information?
> Thank you for any help or advice you can give. :)
Just got round to installing 188.8.131.52 and it seems to work fine from the 'Open...' dialogue and directly from an SMB share.
Thank you so much, Libre Office developers. :D
I'll shut up, now.
Dear David C. Rankin,
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