Version: (using KDE 4.3.0) Installed from: SuSE RPMs After extensive work has been done to fix the initial fish failing to connect bug under http://bugs.kde.org/show_bug.cgi?id=189235, fish will connect, but now disconnects or fails with the active document open leaving you unable to save your work and often time causing your work to be lost. This bug is filed at the request of the developers there, because this differs from the scope of that bug. See: https://bugs.kde.org/show_bug.cgi?id=189235#c128 Thus, this report. The specific problem with opening documents to edit via fish is that after a text file has been open for 15-30 minutes using the fish:// protocol (for example: to access the file on another box on the LAN), additional attempts to save the document result in the "Connection Broken" message that was received originally when all the "cannot connect" fish bugs were being filed. A regression possibly? Dunno. But once the "broken connection" messages start, you will never be able to reconnect and save the file in the original location and you end up having to "save as" to a local file and then either re-establish a fish connection to move it back or transfer the modified file back by some other means (rsync, sftp, USB-card, floppy, etc...) Another consequence of this bug is that once a fish connection has been made and you attempt to upload files using the fish kio, the connection fails during the transfer leaving partially copied files (as when using quanta and pressing F8 to upload files to your web server, some files make it before the fish broken connection error, some don't) This probably happens during one out of every 3 uploads or so. The issue isn't a normal ssh timeout, this is another actual bug in fish. In /etc/ssh/ssh_config, I have the following set to explicitly set to prevent any ssh connection timeout: ServerAliveInterval 300 ServerAliveCountMax 15 I can leave a ssh connection open and idling in konsole all night, wake up and it's still just happy as can be. so *that is not* the issue. The error dialogs received come in two flavors, the old "Connection Broken" message, and the "Could not write to fish file://filename....." Hopefully when this one is found and squashed, then fish will be back to its old reliable and convenient self. Let me know what type of tests I can do to help and I'm happy to do it. Thanks.
I opened a file on a remote web server via Fish in Konqueror for editing in Kate Version 3.3.0 Using KDE 4.3.00 (KDE 4.3.0). When I went to save the file, I got the connection error. Checking the file in a web browser revealed an empty file! So even worse than not saving my update, the situation left me with an erased file on the server! I had to SSH in with Konsole and paste the contents that were still visible in the Kate window with VI. Had the local system crashed during this time, I would have lost a lot of work.
*** Bug 206758 has been marked as a duplicate of this bug. ***
I am running openSUSE 12.2 with Konqueror Version 4.9.5 "release 3" Using KDE Development Platform 4.9.5 "release 3", at home on an ADSL 2+ link, via a wireless connection. When using fish: in Konqueror to up load a directory or a large number of files, I often see the Connection Broken message. Perhaps fish: is timing out prematurely or responding badly to transient delays? The reason I suspect this is that I do not see the same behaviour at work using Kubuntu 12.04 with Ethernet and a high speed connection. In other words, maybe fish does not work well when uploading large files over an ASDL connection?
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!
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!