Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

When I start gvim:

$ date; /usr/bin/gvim; date
Tue May 29 10:45:45 CST 2012

** (gvim:6030): WARNING **: Unable to create Ubuntu Menu Proxy: Timeout was reached
Tue May 29 10:46:11 CST 2012

To stop ubuntu menu proxy:

export UBUNTU_MENUPROXY=0

And test it again:

$ date; /usr/bin/gvim; date
Tue May 29 10:46:47 CST 2012
Tue May 29 10:47:13 CST 2012

No warning. But it still takes 26 seconds to start gvim.

Why it's so slow? Is there any season to make it happen (both 26 sec)?


Currently, I use:

alias gvim='gvim -f'

But I cannot detach from shell anymore.
Hope Ubuntu developer fix this problem as soon as possible.


$ dpkg --list | grep vim
ii  vim-common                             2:7.3.429-2ubuntu2.1                 Vi IMproved - Common files
ii  vim-gnome                              2:7.3.429-2ubuntu2.1                 Vi IMproved - enhanced vi editor - with GNOME2 GUI
ii  vim-gui-common                         2:7.3.429-2ubuntu2.1                 Vi IMproved - Common GUI files
ii  vim-runtime                            2:7.3.429-2ubuntu2.1                 Vi IMproved - Runtime files
ii  vim-tiny                               2:7.3.429-2ubuntu2.1                 Vi IMproved - enhanced vi editor - compact version
share|improve this question
    
I have the same issue.. –  Paul Praet Jun 29 '12 at 21:23
    
@PaulPraet Probably not too localized then. –  Eliah Kagan Jul 20 '12 at 22:23

2 Answers 2

I'm also seeing this delay with gvim and rox-filer on 12.04. I added scim recently so that I could use chinese input. I have a little keyboard icon in my tray whose about box tells me is IBus 1.4.1. Selecting 'quit' off that same menu (so that the keyboard icon disappears) gives me instant gvim startup again. Starting ibus-daemon again (by "ibus-daemon -d"), I get the 26 second behaviour back.

share|improve this answer

See How to get global application menu for gvim?

It seems that the upstream version has already fixed this problem.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.