After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757343 - Gedit needs a long time to launch when opening even a small file in a sftp context
Gedit needs a long time to launch when opening even a small file in a sftp co...
Status: RESOLVED DUPLICATE of bug 756258
Product: gedit
Classification: Applications
Component: file loading and saving
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2015-10-30 08:41 UTC by yweb
Modified: 2015-11-01 20:00 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
illutration of the situation (153.34 KB, image/png)
2015-10-30 08:41 UTC, yweb 		Details

Description yweb 2015-10-30 08:41:12 UTC 
Created attachment 314436 [details]
illutration of the situation

Since Gedit 3.18 the editor needs a very long time to open a file in a sftp context.

The reactivity is so long that Gedit gives me the choices either to force to quit or wait.

The thing is when Gedit gives me those two choices, he is already open in background.


Se the screenshot attached of an illustration.


I'm willing to give you what ever information you need, just ask me. Sorry, the screenshot is in french because I'm actually on french translated system but the windows are the same with the same buttons disposition in english.


Regards
Comment 1 Sébastien Wilmet 2015-10-30 12:10:31 UTC 
Is it a duplicate of bug #756258 ?

Try to rename the file ~/.local/share/recently-used.xbel to see if gedit still needs a long time to launch.
Comment 2 yweb 2015-11-01 19:42:36 UTC 
I renamed ~/.local/share/recently-used.xbel and Gedit is starting normally yet.

It may be bug number #756258 related.

Thanks
Comment 3 Sébastien Wilmet 2015-11-01 20:00:03 UTC 

*** This bug has been marked as a duplicate of bug 756258 ***