I installed a system using LiveCD 2008.0-beta2, and did an 'emerge vmware-modules vmware-workstations' and a number of issues occurred. Reproducible: Always Steps to Reproduce: 1.Install system from LiveCD 2008.0-beta2 2.emerge vmware-modules vmware-workstation 3.configure vmware 4./opt/vmware/workstation/bin/vmware Actual Results: First, during the build of vmware-workstation I complained that I didn't have gtkmm compiled with ACCESSIBILITY! It seems, since this is part of what was built in the emerge step it would have made certain the USE flags were correct! Second, when I finally got everything built and configured, I ran vmware and got the following response: einstein ~ $ /opt/vmware/workstation/bin/vmware /opt/vmware/workstation/bin/vmware: line 85: /etc/vmware/locations: Permission denied /opt/vmware/workstation/bin/vmware: line 177: /lib/wrapper-gtk24.sh: No such file or directory /opt/vmware/workstation/bin/vmware: line 177: exec: /lib/wrapper-gtk24.sh: cannot execute: No such file or directory It seems the ebuild doesn't quite get everything straight. Expected Results: For vmware to run! emerge --info Portage 2.2_rc1 (default/linux/x86/2008.0/desktop, gcc-4.1.2, glibc-2.8_p20080602-r0, 2.6.24-gentoo-r8 i686) ================================================================= System uname: Linux-2.6.24-gentoo-r8-i686-Intel-R-_Core-TM-2_Quad_CPU_Q9450_@_2.66GHz-with-glibc2.0 Timestamp of tree: Sat, 28 Jun 2008 21:00:01 +0000 app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7, 2.1.6 dev-lang/python: 2.4.4-r13, 2.5.2-r5 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.2.5 sys-apps/sandbox: 1.2.18.1-r3 sys-devel/autoconf: 2.13, 2.62 sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1 sys-devel/binutils: 2.18-r2 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 2.2.4 virtual/os-headers: 2.6.25-r4 ACCEPT_KEYWORDS="x86 ~x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-O2 -march=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks parallel-fetch preserve-libs sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_US.UTF-8" LDFLAGS="" LINGUAS="en_US" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X accessibility acl acpi alsa berkdb bluetooth branding bzip2 cairo cdr cli cracklib crypt cups dbus doc dri dvd dvdr dvdread eds emboss encode esd evo fam firefox fortran gdbm gif gnome gpm gstreamer gtk hal iconv ipv6 isdnlog java jpeg jpeg2k kde kerberos ldap libnotify mad midi mikmod mmx mozdevelop mp3 mpeg mudflap ncurses nls nptl nptlonly ntfs ogg opengl openmp pam pcre pdf perl png ppds pppd python qt3 qt3support qt4 quicktime readline reflection sdl session spell spl ssl startup-notification svg tcpd tiff truetype unicode vorbis win32codecs x86 xcomposite xfce xforms xinerama xml xorg xprint xv zlib" ALSA_CARDS="hda_intel loopback intel8x0 intel8x0m" 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" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse vmmouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en_US" USERLAND="GNU" VIDEO_CARDS="vga vesa radeon fbdev fglrx vmware" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Hi Chuck, First off, there's no way for an ebuild to specify what USE flags a dependent package must be built with. It simply isn't possible for one ebuild to affect another that way, and I'm fairly sure it's been designed like that. The best we can do is to give you a warning, so that you actually know how to fix the problem, rather than simply being told "Unknown symbol error" followed by some gibberish when you come to run the program (see bug 185444 and duplicates). Secondly, you have to run vmware as a user in the vmware group. I believe this is mentioned in the notes after vmware has been installed, where it also tells you to configure the system. Again, it would be difficult to allow non-vmware users to run vmware without either introducing vulnerabilities (by reducing the permissions necessary to run vmware) or by writing wrapper scripts simply to tell you something the ebuild notes have already told you. Please could you verify that running vmware as a member of the vmware group works correctly? If not, then you've got a real bug that we can investigate and try and solve. If it does all run correctly, there really isn't much to be gained from trying to protect the user if they don't follow the guidelines we've already provided.
Hi All, In fact, I am having exactly the same problem. Although my system is a gradual update from 2007.0, I had a complete remove of the old workstation 5.5 and also removed all residual files in /etc/ and /opt directories. 1181 After a clean emerge of vmware-workstation 6.5.0.118166 followed by an emerge vmware-modules and emerge --config vmware-workstation, the errors in the original bug appears when the "vmware" script is run. My user account is the member of the "vmware" group. Is this a bug of the ebuild? I do not have know. But based on your last comment, it seems that the issue is still open. Best, Afsar. (In reply to comment #1) > Hi Chuck, > > First off, there's no way for an ebuild to specify what USE flags a dependent > package must be built with. It simply isn't possible for one ebuild to affect > another that way, and I'm fairly sure it's been designed like that. The best > we can do is to give you a warning, so that you actually know how to fix the > problem, rather than simply being told "Unknown symbol error" followed by some > gibberish when you come to run the program (see bug 185444 and duplicates). > > Secondly, you have to run vmware as a user in the vmware group. I believe this > is mentioned in the notes after vmware has been installed, where it also tells > you to configure the system. Again, it would be difficult to allow non-vmware > users to run vmware without either introducing vulnerabilities (by reducing the > permissions necessary to run vmware) or by writing wrapper scripts simply to > tell you something the ebuild notes have already told you. > > Please could you verify that running vmware as a member of the vmware group > works correctly? If not, then you've got a real bug that we can investigate > and try and solve. If it does all run correctly, there really isn't much to be > gained from trying to protect the user if they don't follow the guidelines > we've already provided. >
Afsar, please double check that you've run etc-update or dispatch-conf, and that the file /etc/vmware/config is up-to-date. It should contain text entries that look as follows: libdir = "/opt/vmware/workstation/lib/vmware" bindir = "/opt/vmware/workstation/bin" Please check if those are present. If they're not, please try re-emerging vmware-workstation (in fact, upgrading to vmware-workstation-6.5.1, since 6.5.0 has now been masked), then make sure you do all the steps you mentioned *and* make sure you've run etc-update or dispatch-conf. Then if you're still having trouble, please paste the contents of /etc/vmware/config into this bug...
