Your message dated Thu, 23 Jun 2011 22:41:48 +0200
with message-id <4e03a50c.3040...@gmx.at>
and subject line Re: vim-gtk fails to run
has caused the Debian Bug report #631373,
regarding (no subject)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
631373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim-gtk
Version: 2:7.3.154+hg~74503f6ee649-2+b1
Severity: grave
Justification: renders package unusable


Following an upgrade in Sid today I get this with gvim:

arcadia:~:$ gvim
gvim: symbol lookup error: /usr/lib/libcairo.so.2: undefined symbol: 
FT_GlyphSlot_Embolden


I realise this is probably a bug in libcairo.so.2 but I can't identify
which package is causing it.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.39-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages vim-gtk depends on:
ii  libacl1   2.2.49-5                       Access control list shared library
ii  libc6     2.13-7                         Embedded GNU C Library: Shared lib
ii  libgdk-pi 2.23.3-3                       GDK Pixbuf library
ii  libglib2. 2.28.6-1                       The GLib library of C routines
ii  libgpm2   1.20.4-3.4                     General Purpose Mouse - shared lib
ii  libgtk2.0 2.24.4-3                       The GTK+ graphical user interface 
ii  libice6   2:1.0.7-2                      X11 Inter-Client Exchange library
ii  liblua5.1 5.1.4-5                        Simple, extensible, embeddable pro
ii  libncurse 5.9-1                          shared libraries for terminal hand
ii  libpango1 1.28.3-6                       Layout and rendering of internatio
ii  libperl5. 5.12.3-7+b1                    shared Perl library
ii  libpython 2.6.7-1                        Shared Python runtime library (ver
ii  libruby1. 1.8.7.334-5                    Libraries necessary to run Ruby 1.
ii  libselinu 2.0.98-1.1                     SELinux runtime shared libraries
ii  libsm6    2:1.2.0-2                      X11 Session Management library
ii  libx11-6  2:1.4.3-2                      X11 client-side library
ii  libxt6    1:1.1.1-2                      X11 toolkit intrinsics library
ii  tcl8.5    8.5.9-2                        Tcl (the Tool Command Language) v8
ii  vim-commo 2:7.3.154+hg~74503f6ee649-2+b1 Vi IMproved - Common files
ii  vim-gui-c 2:7.3.154+hg~74503f6ee649-2    Vi IMproved - Common GUI files
ii  vim-runti 2:7.3.154+hg~74503f6ee649-2    Vi IMproved - Runtime files

vim-gtk recommends no packages.

Versions of packages vim-gtk suggests:
pn  cscope       <none>                      (no description available)
ii  gnome-icon-t 3.0.0-3                     GNOME Desktop icon theme
ii  ttf-dejavu   2.33-1                      Metapackage to pull in ttf-dejavu-
ii  vim-doc      2:7.3.154+hg~74503f6ee649-2 Vi IMproved - HTML documentation

-- no debconf information



--- End Message ---
--- Begin Message ---
On 06/23/2011 10:26 PM, Anthony Campbell wrote:
> On 23 Jun 2011, Sebastian Ramacher wrote:
>> Hi Anthony,
>>
>> this looks just like #325526. Could it be that you also have an old 
>> libfreetype
>> in /usr/local/lib? At least I can't reproduce the problem on an up-to-date 
>> sid box.
>>
>> Kind regards,
>> -- 
>> Sebastian Ramacher
>>
> 
> 
> 
> Yes, indeed I did, and removing it (along with all the other old stuff
> there) has made gvim work again. Sincere thanks indeed!

You're welcome. So I'm closing this bug.

> What I find odd is that this has only just now bitten me, although the
> old files must have been there for ages. Anyway, thanks again for the
> quick respose.

I would guess that your $PATH might have changed. But that's just a wild guess.

Kind regards,
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to