Bug 98723 - Remote File SSH Type does not connect on Windows
Summary: Remote File SSH Type does not connect on Windows
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.0.0.alpha0+
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 98897 108915 122157 137353 (view as bug list)
Depends on:
Blocks: CMIS
  Show dependency treegraph
 
Reported: 2016-03-17 12:27 UTC by Usama
Modified: 2023-10-16 03:15 UTC (History)
9 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 Usama 2016-03-17 12:27:07 UTC
Remote File SSH Type does not connect on Windows. It saves the connection but does not connect if you saved the password or not.

It works on Ubuntu 15.10 and not working on Windows 7

A user reported the issue at #libreoffice support channel and I confirm it.

How to reproduce:
1. Click remote files from the side bar
2. Chose add service and pick SSH
3. Fill the information of your SSH connection

Nothing happens

Version: 5.2.0.0.alpha0+
Build ID: 6eb7cd38e348e8a9d6498bfc2d41e91725eb34aa
CPU Threads: 1; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-03-16_12:53:35
Locale: en-US (en_US)
Comment 1 Buovjaga 2016-03-21 17:27:40 UTC
Reproduced.

I used the rebex read-only test server from here: http://www.sftp.net/public-online-sftp-servers
I confirmed the test server works otherwise.

Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+
Build ID: 6eb7cd38e348e8a9d6498bfc2d41e91725eb34aa
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-03-16_12:53:35
Locale: fi-FI (fi_FI)
Comment 2 Yousuf Philips (jay) (retired) 2016-03-21 18:57:07 UTC
@Giuseppe: Can you dig into why this isnt working?
Comment 3 Buovjaga 2016-03-21 19:19:28 UTC
UPDATE: both me and Usama are now seeing "Nonexistent file" error when trying to access on Linux (to a verified working SFTP host).

Arch Linux 64-bit, KDE Plasma 5
Version: 5.2.0.0.alpha0+
Build ID: 4bf2b6b2e6641c82e2b714e394482f1a1620b436
CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on March 21st 2016
Comment 4 Giuseppe Castagno (aka beppec56) 2016-07-03 09:19:02 UTC
Checked on current pre-release, using OpenSSH on a local VM:

Version: 5.2.0.1
Build ID: fcbcb4963bda8633ba72bd2108ca1e802aad557d
CPU Threads: 8; OS Version: Linux 3.13; UI Render: default; 
Locale: en-US (en_US.UTF-8)

On Ubuntu 14.04 64b was not reproducible using as SSH credentials name+password.
On the same platform I got the "Not existent file" error reported on comment 3 when I enabled the ssh server to accept public keys as authentication device.

On Windows 7 32b reproducible, in this case there is no lan activity towards the ssh server, probably internal problem platform specific.

I'm going to investigate further in Windows. Will be a lengthy business...
Comment 5 Giuseppe Castagno (aka beppec56) 2016-10-14 09:25:23 UTC
Found the time to do some investigation.

Using:
Version: 5.3.0.0.alpha0+
Build ID: 45a7137c6796f33fbf5b8f7cb64e293260d991cb
CPU Threads: 8; OS Version: Linux 3.13; UI Render: default; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-10-13_23:38:06
Locale: en-US (en_US.UTF-8); Calc: group

For me, it works correctly in Linux, with the following connection setting.
server:		test.rebex.net	        port: 22
user:		demo
password:	password

root: /

In Windows cannot work because it needs GNOME gio library, not available in Windows.

Back to NEW, not sure was state this bug should assume.
Comment 6 QA Administrators 2017-10-23 14:03:51 UTC Comment hidden (obsolete)
Comment 7 Eric 2017-11-29 12:34:56 UTC
I am still having this problem.

Version: 5.4.2.2
Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4
CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; 
Locale: en-US (en_US.utf8); Calc: group
Comment 8 QA Administrators 2018-11-30 03:58:57 UTC Comment hidden (obsolete)
Comment 9 Mike Kaganski 2019-11-30 15:10:52 UTC
This is clearly platform-specific issue; this one had been reported against Windows; as indicated in comment 5, it's not implemented on Windows; so possibly it's an enhancement request to implement missing functionality (although I keep it bug, since it creates discrepancy in feature set between supported platforms).

Similar problem on different platforms should be discussed in dedicated issues (be it macOS, or a Linux without Gnome, etc).

Of course, one universal solution could be to re-implement this using some portable library.
Comment 10 Mike Kaganski 2019-11-30 15:11:53 UTC
*** Bug 98897 has been marked as a duplicate of this bug. ***
Comment 11 Mike Kaganski 2019-11-30 15:13:20 UTC
*** Bug 122157 has been marked as a duplicate of this bug. ***
Comment 12 Julien Nabet 2020-10-09 18:49:34 UTC
*** Bug 137353 has been marked as a duplicate of this bug. ***
Comment 13 Justin L 2021-10-15 15:17:14 UTC
*** Bug 108915 has been marked as a duplicate of this bug. ***
Comment 14 QA Administrators 2023-10-16 03:15:12 UTC
Dear Usama,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug