gvim complains about "gtk_form_set_static_gravity: assertion `static_gravity_supported' failed" in the shell it's started from

Bug #402188 reported by Martijn vdS on 2009-07-21
608
This bug affects 121 people
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
High
NULL Project
Undecided
Unassigned
PIDA
Confirmed
Undecided
Unassigned
vim
Fix Released
Unknown
vim (Debian)
Fix Released
Unknown
vim (Gentoo Linux)
New
Undecided
Unassigned
vim (Ubuntu)
Low
Unassigned
Nominated for Karmic by Alain Baeckeroot
Nominated for Lucid by Rusty Burchfield

Bug Description

Binary package hint: vim

When running gvim (from vim-gnome) from a gnome-terminal, the terminal will get spammed with the following message:

** (gvim:5944): CRITICAL **: gtk_form_set_static_gravity: assertion `static_gravity_supported' failed

A few times on startup, and then every time a new window is opened inside vim (for example, when using :split)

gvim works fine otherwise, it's just annoying to get these warnings.

Bug fixed in upstream patch #257
http://ftp.vim.org/pub/vim/patches/7.2/7.2.257
applied in debian/unstable and should be synced for lucid.

Related branches

Martijn vdS (martijn) wrote :

I'm using karmic btw:

ii vim-addon-manager 0.4 manager of addons for the Vim editor
ii vim-common 2:7.2.148-2ubuntu2 Vi IMproved - Common files
ii vim-gnome 2:7.2.148-2ubuntu2 Vi IMproved - enhanced vi editor - with GNOM
ii vim-gui-common 2:7.2.148-2ubuntu2 Vi IMproved - Common GUI files
ii vim-runtime 2:7.2.148-2ubuntu2 Vi IMproved - Runtime files
ii vim-scripts 20081206-1 plugins for vim, adding bells and whistles
ii vim-tiny 2:7.2.148-2ubuntu2 Vi IMproved - enhanced vi editor - compact v

vim doesn't like csw gtk

another effect is that x11 embedding of gvim now breaks its main window rendering

Changed in gtk:
status: Unknown → Fix Committed
Changed in pida:
status: New → Invalid
Changed in gtk:
status: Fix Committed → Fix Released
Facundo Batista (facundo) wrote :

It happens to me in a fully updated karmic.

Changed in vim (Ubuntu):
status: New → Confirmed
RLHawk (rayhawk2008) wrote :

Same here -- happens to me on a fully updated karmic.

Alex Converse (ajc30) wrote :

Upstream patch 7.2.257 supposedly fixes this. http://ftp.vim.org/pub/vim/patches/7.2/7.2.257

This problem still occurs in karmic beta and makes using the command line and gvim really messy. Please update with the upstream patch for the real release. Thanks.

Alex Converse (ajc30) wrote :

Patch 257 does in fact fix this for me. A proof of concept available in my PPA.

Leandro (leandromartinez98) wrote :

This is still present in karmic beta, up to date on Oct 13th.

Changed in vim:
status: Unknown → Fix Committed
Changed in vim (Debian):
status: Unknown → Fix Committed
Leandro (leandromartinez98) wrote :

Will the patches arrive to karmic?

Fix not in karmic 2 days after being "Fix committed"

Leandro (leandromartinez98) wrote :

Actually nobody understands what "fix committed" means. The mix may arrive in lucid.

affects: pida → bzr-pida
affects: bzr-pida → pida
Changed in pida:
status: Invalid → Confirmed
sam (sdoyle-2) wrote :

Still visible for me as well as of full update on Oct. 20th.

Julius (caesar-bs) wrote :

Still visible for me as well as of full update on Oct. 24th.

George Ryan (george-ryan) wrote :

I am fully updated with the release candidate and all updates to 28 October '09 and I am still getting this error message.

Luis Díaz (piponazo) wrote :

I have the same problem in both Ubuntu 9.10 and Gentoo with gnome 2.28.

Vik (vik-catalyst) wrote :

I'm on vim-full 2:7.2.079-1ubuntu5

Yup, bug still here in the current Karmic files.

Vik :v)

paradoxheart (paradoxheart) wrote :

This bug is present in the release version of Karmic. Hopefully this warrants a "recommended updates" fix.

As a temporary workaround until it is fixed, you can declare an alias for gvim in your .bashrc pointed to 'gvim 2>/dev/null'. This will suppress all stderr messages, including this one, but bear in mind that if gvim encounters any other errors that would normally be reported via stderr, these will not be shown either.

ergodic (dawangee) wrote :

I just upgraded to Karmic and this bug shows up..

Same behaviour here, fresh Karmic install.

Ramon Tayag (ramon-tayag) wrote :

Same error fresh karmic install

Jeremy Kerr (jk-ozlabs) wrote :

I've done a test build with the patch listed above. PPA details are at:

 https://launchpad.net/~jk-ozlabs/+archive/vim

Fixes the bug for me.

oversky (mailcwc) wrote :

The fixes from Jeremy works.

MrMagne (mr.magne) wrote :

the PPA from Jeremy works for me too

zorblek (zorblek) wrote :

I am experiencing this bug in Karmic, and the PPA works for me as well.

Michael George (mdgeorge) wrote :

PPA works for me too.

Changed in vim:
status: Fix Committed → Fix Released
Changed in vim (Debian):
status: Fix Committed → Fix Released

Hi, please help a Karmic newbie: will this bug be fixed or not? Using an untrusted PPA does not seem to be a good solution to me. Even if I decide to trust Jeremy, what if there are other updates to gvim - will they appear in the PPA, too? I'd rather go with the official package. This is a bug, so why can't it be fixed?

Fastrack20 (aedmunds) wrote :

PPA worked here as well.

X Y (throwaway-xy+ubuntu) wrote :

Experiencing this here. This is egregious and should be fixed immediately.

Comment #9 suggests this atrocious bug has been present since Karmic.

Why has it not been fixed? Who is accountable?

Philip Muškovac (yofel) wrote :

Folks, before even more post a request here for this bug to be fixed please first read
https://wiki.ubuntu.com/StableReleaseUpdates

The page explains how and when bug fixes are applied in stable releases like karmic.
For now the bug the bug is fixed in debian and will be fixed in Lucd Lynx once the package is pulled from debian.

As to why this bug wasn't fixed in time: Maybe there were more urgent issues to fix than this and the maintainers never had the time for it?

Regards Yofel

PS: why not use vim if you're already on the command line?

Kai Blin (kai.blin) wrote :

Philip, that PS is kind of pointless.
You can safely assume that people who do experience the bug do want to run gvim not vim, or they wouldn't care about this bug. Last but not least, even if you're running gvim from the K menu or any other setup that doesn't display stderr, output from stderr ends up in ~/.xsession-errors. That file just keeps growing and growing, and because it's a . file, you tend to forget about it when trying to figure out where all your disk space on /home went.

Launchpad lacks a setting that will tell people that this bug will be fixed for 10.04 but not for 9.10, so the folks using 9.10 will stop posting "affects me too" reports. ( By the way, should the "this bug affects me too" link on the top of the page be made more obvious? )

Philip Muškovac (yofel) wrote :

Ok, sry for that ps, good point. There was some discussion about how to improve the 'affects me too' link. I would like to see it be a bit more obvious too.

Also, doesn't

"Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel)."

apply? (From the web site about stable releases).

WORKAROUND, as i don't expect ubuntu to fix it (maybe i should go back to Debian as suggested by Philip M in #30)

i added 2 lines in my /home/alain/.bash_aliases
alias gvim="gvim -reverse 2>/dev/null"
alias tvim="gvim --servername localhost --remote-silent-tab 2>/dev/null"

regards.

Philip Muškovac (yofel) wrote :

Well, I had some free time today and so here's a debdiff for karmic-proposed containing the upstream patch if the SRU Team thinks it qualifies for an SRU.

description: updated
description: updated
C de-Avillez (hggdh2) wrote :

marking triaged

Changed in vim (Ubuntu):
status: Confirmed → Triaged
traxxas (traxxas) wrote :

The patch has been added and someone made a PPA for it here: https://launchpad.net/~jk-ozlabs/+archive/vim . Short-link: ppa:jk-ozlabs/vim

Roger Erens (rogererens) wrote :

The description of this bug states:
"gvim works fine otherwise, it's just annoying to get these warnings."

But this is not true when issueing a bzr commit command without the -m or -F option:
if gvim is chosen as the editor in ~/.bazaar/bazaar.conf,
then gvim will not show the horizontal line that separates the commit message from the list of files that are changed in the commit.

I'll try Jeremy's patch now and report back if that behaviour is fixed.

Roger Erens (rogererens) wrote :

Sorry, I meant to refer to the Bazaar project, not Bazaar Explorer

Changed in bzr-explorer:
status: New → Invalid
Roger Erens (rogererens) wrote :

Despite applying Jeremy's patch, 'bzr commit' with an empty commit message AND having gvim as the editor to be used, the separator line and lines following it are not shown in gvim.
Setting vim as the editor works as expected, though (just as before applying the patch).

Loïc Minier (lool) wrote :

I'm not sure this is SRU material, but the patch looks trivial; I'm unsub-ing sponsors for now, but please re-sub when ubuntu-sru team approves the SRU.

Martin Pitt (pitti) wrote :

Seems simple and obvious enough, and I agree that it's pretty annoying. So please sponsor (also to lucid).

bayo opadeyi (bayokrapht) wrote :

I am trying to apply the patch http://ftp.vim.org/pub/vim/patches/7.2/7.2.257, and got stuck on the "top Vim directory, where the "src" and "runtime' directories are located". I don't know where the top Vim directory is. can someone help me out?

On Tue, Jan 5, 2010 at 02:30, bayo opadeyi <email address hidden> wrote:
> I am trying to apply the patch
> http://ftp.vim.org/pub/vim/patches/7.2/7.2.257, and got stuck on the
> "top Vim directory, where the "src" and "runtime' directories are
> located". I don't know where the top Vim directory is. can someone help
> me out?

enter the commands

:!echo $VIM

and

:!echo $VIMRUNTIME

Jeroen Pulles (jeroen-pulles) wrote :

My workaround for 9.10 is a iittle shell function:
gvim () { command gvim $@ 2> /dev/null }

When using the PPA, I now get this new error : "GLib-WARNING **: g_set_prgname() called multiple times". Anybody else with the same problem ?

jlmalet (jeanluc-malet) on 2010-01-14
Changed in vim (Ubuntu):
status: Triaged → Confirmed
Roy Jamison (xteejx) on 2010-01-14
Changed in vim (Ubuntu):
status: Confirmed → Triaged
dj3 (dim-jakobi) wrote :

The version from the PPA still does produce a "GLib-WARNING **. The problem is with vim 7.2 release and it is already fixed, there is a patch on www.vim.org.

I report having successfully build vim from source including all the latest official patches using aap

(http://www.a-a-p.org/ports.html,
the package "aap" should be installd beforehand lkewise all the build dependencies "apt-get build-dep vim-gnome")

and do not observe any warnings or erros in the console when I start gvim. I hope this will help to somebody.

Han (kdhan) wrote :

Thank you.

Philip Muškovac (yofel) on 2010-02-23
Changed in vim (Ubuntu):
importance: Undecided → Low
Launchpad Janitor (janitor) wrote :
Download full text (3.3 KiB)

This bug was fixed in the package vim - 2:7.2.330-1ubuntu1

---------------
vim (2:7.2.330-1ubuntu1) lucid; urgency=low

  [ Michael Bienia ]
  * Merge with Debian unstable (LP: #509900):
    - Highlight Breaks in debian/control (LP: #498303).
    - [7.2.257] GTK 2.17: lots of assertion error messages (LP: #402188).
  * Remaining changes:
    - debian/runtime/vimrc: "syntax on" is a sane default for non-tiny vim.
    - runtime/syntax/debcontrol.vim:
      + Add "metapackages" to the list of valid sections.
    - runtime/syntax/grub.vim:
      + Add Ubuntu-specific 'quiet' keyword.
    - Drop vim-lesstif package and lesstif2-dev build-dependency.
    - Enable Python interpreter on basic builds.
    - Rename Vcs-* to XS-Debian-Vcs-*.
  * runtime/ftplugin/debchangelog.vim: Use python-launchpadlib (and LP API)
    instead of python-launchpad-bugs for bug completion for Ubuntu
    (forwarded to Debian as bug #566841).
  * src/configure.in, src/auto/configure:
    As MODLIBS from python's config/Makefile includes LOCALMODLIBS which
    shouldn't be used and breaks the build with newer python versions, use
    BASEMODLIBS instead of MODLIBS (forwarded to Debian as bug #566842;
    LP: #534251).

  [ Colin Watson ]
  * Add Launchpad integration to the Help menu if launchpad-integration is
    installed (LP: #453103).

vim (2:7.2.330-1) unstable; urgency=low

  * [34a85b6] Update README for patches 285 - 330
    - [1aee41b] [7.2.294] when using TEMPDIRS dir name could get too long
      (Closes: #544682)
    - [f3ea2c2] [7.2.300] file descriptors not closed when executing external
      command (Closes: #290507)
    - [f3ce928] [7.2.324] a negative column argument in setpos() may cause a
      crash (Closes: #563071)
  * [fd76420] Sync runtime files
    - NetRW updated to handle 'equalalways' being set, but window sizes not
      being equal. (Closes: #346089)
  * debian/control:
    - [49f131e] Add Depends: ${misc:Depends} to all binary stanzas.
    - [8973628] Bump Standards-Version, no changes required
    - [12ac9a3] Remove Pierre Habouzit from Uploaders.

vim (2:7.2.284-1) unstable; urgency=low

  * syntax/debcontrol.vim:
    - [b997413] Add highlighting of Breaks field (Closes: #541989)
    - [05a38bf] Recognize lpia and kopensolaris-i386. (Closes: #543207)
  * [a85b832] Update README for patches 246 - 259
    - [669e098] [7.2.256] GTK font dialog doesn't have a default when
      'guifont' not set (Closes: #307158)
    - [f4ed8fc] [7.2.257] GTK 2.17: lots of assertion error messages (Closes:
      #545168)
  * [83583c3] Add Ubuntu's next release, lucid, to the Debian-related runtime
    files.
  * [87f3b00] update-runtime: Use -A option for git-add so deleted files
    are committed.
  * [60cbb45] Sync runtime files
    - Updated remind.vim syntax file. (Closes: #536770)
    - Fix typos in Japanese vimtutor. (Closes: #539577)
  * [96dca67] Move html docs from /u/s/d/vim-common/html to /u/s/d/vim-
    doc/html.
  * [9fec1cd] Use usr_toc.html for the usermanual Index page.
  * [fbacb18] Update README for patches 268 - 284
    - [76d3dad] [7.2.283] GTK: changing font doesn't keep the window maximized
      (Closes: #466088)
  * [6e51684] debsour...

Read more...

Changed in vim (Ubuntu):
status: Triaged → Fix Released
Philip Muškovac (yofel) wrote :

Now that this bug is fixed in lucid, can a sponsor please upload the fix for karmic?

Changed in vim (Ubuntu):
status: Fix Released → Confirmed
Philip Muškovac (yofel) wrote :

Please don't change the Status without explaining why you're doing so.

Changed in vim (Ubuntu):
status: Confirmed → Fix Released
Eric Angell (some-other-guy) wrote :

Here we are, almost a full year after this was "fixed" and it's still broken in Karmic. That's pretty egregious.

affects: bzr-explorer → null
David Tombs (dgtombs) wrote :

@Eric: Sorry, but these kinds of fixes are not usually backported; it's not worth the effort. Feel free to upgrade to Lucid, it's an LTS.

Dan Scott (denials) wrote :

"Feel free to upgrade to Lucid" is a dismissive and offensive statement. It would be better not to reply than to make comments like this, which might just as well read:

:%s/to Lucid.\+$/to a different distribution/

Dan,

Well why don't you fix it then?

Andrew

On 6 September 2010 23:45, Dan Scott <email address hidden> wrote:

> "Feel free to upgrade to Lucid" is a dismissive and offensive statement.
> It would be better not to reply than to make comments like this, which
> might just as well read:
>
> :%s/to Lucid.\+$/to a different distribution/
>
> --
> gvim complains about "gtk_form_set_static_gravity: assertion
> `static_gravity_supported' failed" in the shell it's started from
> https://bugs.launchpad.net/bugs/402188
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GTK+ GUI Toolkit: Fix Released
> Status in NULL Project: Invalid
> Status in Python Integrated Development Application: Confirmed
> Status in Vi IMproved: Fix Released
> Status in “vim” package in Ubuntu: Fix Released
> Status in “vim” package in Debian: Fix Released
> Status in “vim” package in Gentoo Linux: New
>
> Bug description:
> Binary package hint: vim
>
> When running gvim (from vim-gnome) from a gnome-terminal, the terminal will
> get spammed with the following message:
>
> ** (gvim:5944): CRITICAL **: gtk_form_set_static_gravity: assertion
> `static_gravity_supported' failed
>
> A few times on startup, and then every time a new window is opened inside
> vim (for example, when using :split)
>
> gvim works fine otherwise, it's just annoying to get these warnings.
>
> Bug fixed in upstream patch #257
> http://ftp.vim.org/pub/vim/patches/7.2/7.2.257
> applied in debian/unstable and should be synced for lucid.
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gtk/+bug/402188/+subscribe
>

Changed in gtk:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.