Bug 416084 - Dolphin restart required if remote server has problems
Summary: Dolphin restart required if remote server has problems
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-10 12:34 UTC by Peter
Modified: 2022-11-04 05:07 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2020-01-10 12:34:43 UTC
SUMMARY
If there are any temporary problems on the remote resource, a full restart of Dolphin is required. In order to be able to continue working with a remote resource.


STEPS TO REPRODUCE
1. Open Dolphin, open "remote:/", connect the remote resource.
2. Open any folder on the remote resource.
3. Connect to a remote resource.
4. For example, restart the remote resource.
5. Update folder in Dolphin. 


OBSERVED RESULT
I get an error.
"Internal error
Send an error message to https://bugs.kde.org
sftp://root@1.1.1.1:22/"


EXPECTED RESULT
Necessary:
- Just reconnect and display a message if a connection problem occurs.
- It is necessary to save the working directory on the remote resource, after reconnecting. For example, if I worked with the resource "sftp://root@1.1.1.1: 22/root/.config/", then after reconnecting - automatically return to this address.

It would be ideal:
- Have a network connection setup. The number of reconnection attempts and the timeout between attempts.
- Automatically reconnect in case of an error.

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: KDE neon 5.17
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2


ADDITIONAL INFORMATION
The error is reproduced not only when the remote resource is restarted. But also for any network connection problems both on the client side and on the server side. And she meets - often enough.
~$ dolphin -v
dolphin 19.12.1
Comment 1 Justin Zobel 2022-10-05 08:14:50 UTC
I've just tested this on Dolphin built from git master and I cannot replicate it.
I access my server via fish://192.168.0.100 and see my ~/ contents
I restart ssh on the remote server
I can still refresh the contents of the folder as it reconnects for me

Can you still reproduce this issue Peter?
Comment 2 Bug Janitor Service 2022-10-20 04:59:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-11-04 05:07:51 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!