[Bug 987707] Re: gvim in Precise can't connect to ibus and takes a long time to load

Jason Conti 987707 at bugs.launchpad.net
Wed Apr 25 21:48:19 UTC 2012


This may be the ibus problem mentioned many times in bug 856779 (so this
is probably a separate issue from that bug). With ibus running I
experience the ~20 second pause before gvim finally starts. However,
after exiting ibus, gvim will start immediately.

The real problem seems to be that without -f, the gvim process cannot
connect to any dbus addresses (so I would say this bug is related to bug
776499 as well, I am seeing ** (gvim:14213): WARNING **: Unable to
create Ubuntu Menu Proxy: Timeout was reached)

We seem to hang in src/ibusbus.c:ibus_bus_connect in the call to
g_dbus_connection_new_for_address_sync. After modifying the code to pass
the GError argument, we get the not so helpful message: Timeout was
reached, the same as Ubuntu Menu Proxy.

My first thought was this was an environment issue, but the IBUS_ADDRESS
seems to be correct as well as DBUS_SESSION_BUS_ADDRESS, so now I'm not
sure what the problem is.

We could work around the hang in ibus by modifying ibus_bus_connect to
use the asynchronous version of g_dbus_connection_new_for_address, but
ibus still won't work in gvim.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/987707

Title:
  gvim in Precise can't connect to ibus and takes a long time to load

Status in “vim” package in Ubuntu:
  Confirmed

Bug description:
  Hi.  I have a system with Ubuntu 12.04 (updated 24 April 2012), with
  the Chinese language packs and the pinyin ibus system installed.  The
  system has vim-gtk 2:7.3.429-2ubuntu2 installed on it.  When I start
  gvim with no arguments, the window appears on the screen, but it is
  not responsive.  After ~30 seconds of frozenness, gvim begins to
  respond again ... however, I can't use Ctrl-Shift to fire up the
  pinyin input system.  If I start gvim with "gvim -f" to prevent it
  from forking to the background, it starts up quickly and pinyin input
  works.

  This sounds like this is the same symptoms as bug #856779... but this
  is on Precise.  I'll attach the strace output from the failing case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/987707/+subscriptions




More information about the foundations-bugs mailing list