Gedit is very slow when starting in Intrepid

[junior]

Binary package hint: gedit

After installing Intrepid beta Gedit has become veery slow when starting (ex opening a regular text-file)
It didn't use to be that way! It takes about ten seconds to open it's interface, and another 5 seconds to show the content (for a small file)

[Mackenzie Morgan (maco.m)]

Using 2.24.0-0ubuntu1
I cannot reproduce this on Intrepid. It opens nearly instantly, and this is in a virtual machine.

What version are you using?

[Sebastien Bacher (seb128)]

do you have any non local server listed or some extra option enabled?

[junior (olav-ekkje)]

I've tested this a little more, and it seems it's not slow opening a blanc document, like just running gedit command, eighter as root or regular user. Also opening a file from terminal, like sudo gedit /etc/X11/xorg.conf goes quick. BUT double clicking a file in home folder, like just containing some simple text file, is slow.

I don't have any special plugins or anything, just as it is from fresh install

[Sebastien Bacher (seb128)]

do you have lot of files in the directory where you open the example?

[junior (olav-ekkje)]

No, the dir is empty

[fenix0 (fenix0)]

I too had the same problem, but I managed to solve it, it is a gedit's plugin that causes the slowness, all you have to do is disable the plugins, and gedit will get as fast as on Hardy

[showcaser (showcaser)]

I can confirm this problem on fresh install (intel x86) of intrepid beta with all updates . Opening gedit from the menu or by double clicking a file would take between 20-30 seconds to start. Once opened new files would load instantaneously in a new tab. However, closing gedit and reopening it immediately would take the 20-30 seconds to start.

Disabling all the plugins fixed the slow startup (now starts in < 2 seconds). I'll see if I can find which plugin is the culprit.

I've never touched the gedit plugins, didn't even know there were any, so this happened with the default settings off of a fresh install.

I've also installed Intrepid beta AMD64 on another computer where it is taking 10+ seconds to start gedit (haven't disabled plugins yet).

[daspooky (daspooky)]

I pinpointed the plugin causing this. It is the "File Browser pane" plugin.

[Sebastien Bacher (seb128)]

the bug is similar to bug #276094, could you try to use gdb to figure on what it's hanging in your case though?

[junior (olav-ekkje)]

I can confirm that I disabled all but the spelling plugin, and now it's working great! It may very well be the "File Browser Pane" plugin that daspooky pointed out!

[Kevin (kevinshlee)]

I'm using Intrepid (8.10) beta upgraded from Hardy (8.04) and have the same problem.

Regardless of opening it from terminal or the menu in the X-Window, it is always slow when starting.

It happens even when I ran it without any text file.

[xianthax (xianthax)]

confirmed on x86 8.04 to 8.10 beta upgrade

gedit takes very long (30 seconds +) to open directly or by double clicking an icon in nautilus. During this time gedit spikes one CPU to 100% usage.

disabling the "File Browser" plugin removes the problem, startup is near instant.

no helpful output from starting gedit in a terminal

-x

[Andrei Ghimus (ghimus)]

I've attached a trace and a summary running gedit with only the File Browser pane plugin enabled.

[Andrei Ghimus (ghimus)]

I filed a bug upstream as well: http://bugzilla.gnome.org/show_bug.cgi?id=556901