Hi, vmware-workstation does not start anymore on one of my boxes after the latest 'emerge -vauDN world'. I suspect (but only suspect) the xorg-server update to be responsible. All that happens is: #################################################################### colding@athero ~ $ vmware /opt/vmware/workstation/lib/bin/vmware: /opt/vmware/workstation/lib/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib32/libcairo.so.2) Gdk: error while retrieving Xinerama information VMware Workstation Error: VMware Workstation unrecoverable error: (vmui) Gdk: error while retrieving Xinerama information A log file is available in "/tmp/vmware-colding/ui-29655.log". Please request support and include the contents of the log file. To collect files to submit to VMware support, run vm-support. We will respond on the basis of your support entitlement. #################################################################### My emerge --info is: #################################################################### colding@athero ~ $ emerge --info Portage 2.1.2.12 (default-linux/amd64/2007.0, gcc-4.1.2, glibc-2.5-r4, 2.6.22-gentoo-r5 x86_64) ================================================================= System uname: 2.6.22-gentoo-r5 x86_64 Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz Gentoo Base System release 1.12.9 Timestamp of tree: Mon, 10 Sep 2007 14:50:01 +0000 app-shells/bash: 3.2_p17 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.9-r2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=nocona -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.uni-c.dk/pub/gentoo/ http://gentoo.tiscali.nl/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X acl alsa amd64 avahi berkdb bitmap-fonts bzip2 cdr cli colordiff cracklib crypt cscope cups dbus dri dvd dvdr emacs gdbm gnome gphoto2 gpm gtk hal iconv ipv6 jpeg lm-sensors madwifi midi mmx mudflap ncurses nls nptl nptlonly nvidia openmp pam pcre perl png pppd python readline reflection session spl sse sse2 ssl tao tcpd tetex toolkit-scroll-bars truetype-fonts type1-fonts unicode wifi xorg xvmc zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nv vesa vga" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS #################################################################### Thanks, jules
*** This bug has been marked as a duplicate of bug 185444 ***
I tried the solution as outlined in #185444 but it didn't work. I think that this bug should be reopened. The output from my vmware command is attached asap.
Created attachment 130658 [details] Output from "VMWARE_USE_SHIPPED_GTK=force vmware"
Uh, don't prelink such stuff. Anyway, there's no solution to bug 185444, that's whole point why's it still *open*. No need to have multiple bugs for the same thing. *** This bug has been marked as a duplicate of bug 185444 ***
(In reply to comment #4) > Uh, don't prelink such stuff. > > Anyway, there's no solution to bug 185444, that's whole point why's it still > *open*. OK, it didn't came out right. What I meant to say was that the workaround from #185444 comment 3 (setting VMWARE_USE_SHIPPED_GTK=[force,yes]) does work with vmware for me. I'm now realizing that comment 3 was about vmplayer, so maybe it doesn't work for vmware. I'll try the trick with the wrapper-gtk24.sh script that the OP from 185444 proposes.
(In reply to comment #5) > OK, it didn't came out right. What I meant to say was that the workaround from > #185444 comment 3 (setting VMWARE_USE_SHIPPED_GTK=[force,yes]) does work with > vmware for me. Doh! - s/"does work"/"does not work" Sorry, jules
These complaints would really be better directed to VMWare folks - because there's not much we would do with closed source stuff.
(In reply to comment #7) > These complaints would really be better directed to VMWare folks - because > there's not much we would do with closed source stuff. I know. I've reported the problem to VMware.
Just as additional info. I've tried the patch to wrapper-gtk24.sh as outlined in #185444 but it doesn't work for me. May this issue is another one after all? All I got after applying the patch is: colding@athero ~ $ vmware Gdk: error while retrieving Xinerama information VMware Workstation Error: VMware Workstation unrecoverable error: (vmui) Gdk: error while retrieving Xinerama information A log file is available in "/tmp/vmware-colding/ui-6204.log". Please request support and include the contents of the log file. To collect files to submit to VMware support, run vm-support. We will respond on the basis of your support entitlement. colding@athero ~ $ cat /tmp/vmware-colding/ui-6204.log Sep 12 21:32:11: vmui| Log for VMware Workstation pid=6204 version=5.5.4 build=build-44386 option=Release Sep 12 21:32:11: vmui| Gdk: error while retrieving Xinerama information Sep 12 21:32:11: vmui| Backtrace: Sep 12 21:32:11: vmui| Backtrace[0] 0xffd6fa68 eip 0x821da80 Sep 12 21:32:11: vmui| Backtrace[1] 0xffd6fe88 eip 0x821eb75 Sep 12 21:32:11: vmui| Backtrace[2] 0xffd6fea8 eip 0x8077028 Sep 12 21:32:11: vmui| Backtrace[3] 0xffd6fec8 eip 0x846e46b Sep 12 21:32:11: vmui| Backtrace[4] 0xffd70328 eip 0xf7d3635d Sep 12 21:32:11: vmui| Backtrace[5] 0xffd70358 eip 0xf7d36569 Sep 12 21:32:11: vmui| Backtrace[6] 0xffd70398 eip 0xf7bfbea8 Sep 12 21:32:11: vmui| Backtrace[7] 0xffd703c8 eip 0xf7bfc224 Sep 12 21:32:11: vmui| Backtrace[8] 0xffd70488 eip 0xf7be347a Sep 12 21:32:11: vmui| Backtrace[9] 0xffd704a8 eip 0xf7bc0bed Sep 12 21:32:11: vmui| Backtrace[10] 0xffd704c8 eip 0xf7987f3f Sep 12 21:32:11: vmui| Backtrace[11] 0xffd704e8 eip 0xf7987f74 Sep 12 21:32:11: vmui| Backtrace[12] 0xffd70508 eip 0xf7585fed Sep 12 21:32:11: vmui| Backtrace[13] 0xffd70538 eip 0xf7585b48 Sep 12 21:32:11: vmui| Backtrace[14] 0xffd705b8 eip 0x8078113 Sep 12 21:32:11: vmui| Backtrace[15] 0xffd70938 eip 0x8076f99 Sep 12 21:32:11: vmui| Backtrace[16] 0xffd70998 eip 0xf7096824 Sep 12 21:32:11: vmui| Backtrace[17] 00000000 eip 0x8076c71 Sep 12 21:32:11: vmui| Msg_Post: Error Sep 12 21:32:11: vmui| [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vmui) Sep 12 21:32:11: vmui| Gdk: error while retrieving Xinerama information Sep 12 21:32:11: vmui| [msg.panic.haveLog] A log file is available in "/tmp/vmware-colding/ui-6204.log". [msg.panic.requestSupport.withLog] Please request support and include the contents of the log file. [msg.panic.requestSupport.linux] Sep 12 21:32:11: vmui| To collect files to submit to VMware support, run vm-support. Sep 12 21:32:11: vmui| [msg.panic.response] We will respond on the basis of your support entitlement. Sep 12 21:32:11: vmui| ---------------------------------------- Sep 12 21:32:40: vmui| Caught signal 2 -- pid 6204 (eip 0xffffe40e) colding@athero ~ $
OK, I can now confirm that it is indeed another issue than #185444. At least if I am to consider the proposed workaround in comment 1 in #185444. This fix did not make VMware work for me. Downgrading xorg-server from 1.3.0.0 to 1.2.0-r3 did, on the other hand, fix the issue and made VMware happy on my box. VMware is now starting and the wrapper-gtk24.sh script is unmodified. I'm risking my right arm and is reopening the bug. I hope that it is the right thing to do under these circumstances.
It is the right thing to do, but there's not anything that we can really do about it. As Jakub said, the main VMware products are all closed-source. As such, we're unable to do anything about this. You had said that you had reported it to VMware. At this point, we have exactly one option: wait for Vmware to release a new 5.5 build... Because of this, I'm marking this as UPSTREAM since we have to wait on them before we can do anything about this. The ball is solely in their court now.
