No timeout in gedit when connection is lost
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit |
Won't Fix
|
Wishlist
|
|||
gedit (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
If connection is lost when editing a document in gedit that is on a remote sftp/ssh server, gedit gets stuck in an endless loop when trying to save the document. It will also fail even if the connection is reestablished
To reproduce:
1. Open Nautilus and connect through it to your SFTP/SSH server
2. Open a .txt document with gedit and do some changes
3. Close connection to simulate a lost network situation
4. Reconnect to your SFTP/SSH server
5. Try to save the document in gedit. Gedit will now get stuck in a never ending loop trying to save the document and will need to be killed manually
Expected:
5. Gedit will eventually timeout if it can't find the location.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gedit 3.2.3-0ubuntu0.1
ProcVersionSign
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Dec 7 10:54:16 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
SourcePackage: gedit
UpgradeStatus: Upgraded to oneiric on 2011-11-01 (35 days ago)
Changed in gedit (Ubuntu): | |
status: | New → Triaged |
Changed in gedit: | |
importance: | Unknown → Medium |
status: | Unknown → New |
tags: | added: testcase |
Changed in gedit: | |
status: | New → Invalid |
Changed in gedit: | |
importance: | Medium → Unknown |
status: | Invalid → Unknown |
Changed in gedit: | |
importance: | Unknown → Wishlist |
status: | Unknown → Confirmed |
Changed in gedit: | |
status: | Confirmed → Won't Fix |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.