[Vmware-package-maintainers] Bug#468057: 2.8 gtkmm breaks vmware-player

[Tom Parker]

Package: vmware-package
Version: 0.21

Using a vmplayer generated from a version 2.0.2.59824 tarball, I get
the following error when I click on the "open an existing virtual
machine" button

/usr/lib/vmware/bin/vmplayer: symbol lookup error:
/usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so: undefined symbol:
g_get_user_special_dir

Also, attempting to use "VMWARE_USE_SHIPPED_GTK=no vmplayer" instead
gets me the following,

/usr/lib/vmware/bin/vmplayer: symbol lookup error:
/usr/lib/vmware/lib/libvmwareui.so.0/libvmwareui.so.0: undefined
symbol: _ZN3Gtk13RecentManager11get_defaultEv

Upgrading libgtkmm-2.4-1c2a from 1:2.8.8-1 to 1:2.12.3-2 appears to
fix this, and appears to have made vmware use the shipped libgtkmm by
default. Some detective work
(http://library.gnome.org/devel/gtk/stable/GtkRecentManager.html#gtk-recent-manager-get-default)
indicates that the relevant symbol has been around since 2.10, and
1:2.12.3-2 WFM.

Therefore, can the vmware-package upgrade its libgtkmm-2.4-1c2a
recommendation to specify at least version 1:2.12.3-2, and preferably
do the same thing for the generated vmware-player packages as well.

Thanks!

Tom Parker