You are not logged in.
I'm at a complete loss here, did a large pacman -Syu update today, which I tend not to, (mostly to avoid these kind of problems), and vmware now fails to start.
the vmware kernel modules are loaded, its just the vmware gui that won't start, it doesn't give any errors either.
I have no idea of what it could be,
jcosta@jcosta-uportable[~]
[17:35]:vmware
Logging to /tmp/vmware-jcosta/setup-4985.log
filename: /lib/modules/2.6.38-ck/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 2.6.38-ck SMP preempt mod_unload
filename: /lib/modules/2.6.38-ck/misc/vmnet.ko
supported: external
license: GPL v2
description: VMware Virtual Networking Driver.
author: VMware, Inc.
depends:
vermagic: 2.6.38-ck SMP preempt mod_unload
filename: /lib/modules/2.6.38-ck/misc/vmblock.ko
supported: external
version: 1.1.2.0
license: GPL v2
description: VMware Blocking File System
author: VMware, Inc.
srcversion: 400149ED038D22A87322D56
depends:
vermagic: 2.6.38-ck SMP preempt mod_unload
parm: root:The directory the file system redirects to. (charp)
filename: /lib/modules/2.6.38-ck/misc/vmci.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Communication Interface (VMCI).
author: VMware, Inc.
depends:
vermagic: 2.6.38-ck SMP preempt mod_unload
filename: /lib/modules/2.6.38-ck/misc/vsock.ko
supported: external
license: GPL v2
version: 1.0.0.0
description: VMware Virtual Socket Family
author: VMware, Inc.
srcversion: CF8ABF14AFA7E44C2CC4C9C
depends: vmci
vermagic: 2.6.38-ck SMP preempt mod_unload
filename: /lib/modules/2.6.38-ck/misc/vmmon.ko
supported: external
license: GPL v2
description: VMware Virtual Machine Monitor.
author: VMware, Inc.
depends:
vermagic: 2.6.38-ck SMP preempt mod_unload
jcosta@jcosta-uportable[~]
[17:35]:
jcosta@jcosta-uportable[~]
[17:41]:cat /tmp/vmware-jcosta/setup-4985.log
May 13 17:35:19.315: app-140031774119680| Log for VMware Workstation pid=4985 version=7.1.2 build=build-301548 option=Release
May 13 17:35:19.315: app-140031774119680| The process is 64-bit.
May 13 17:35:19.315: app-140031774119680| Host codepage=UTF-8 encoding=UTF-8
May 13 17:35:19.315: app-140031774119680| Logging to /tmp/vmware-jcosta/setup-4985.log
May 13 17:35:19.434: app-140031774119680| modconf query interface initialized
May 13 17:35:19.435: app-140031774119680| modconf library initialized
jcosta@jcosta-uportable[~]
[17:41]:
Last edited by jorge.costa (2011-05-16 09:00:18)
Offline
For me the VMware Workstation 7 GUI does not start with glibmm 2.28. Downgrading glibmm to 2.24 solves my problems.
I have not yet investigated it any further...
Offline
spot on,
jcosta@jcosta-uportable[/tmp]
[9:54]:sudo grep glibmm /var/log/pacman.log
[2010-12-06 13:56] installed glibmm (2.24.2-1)
[2011-05-13 11:04] upgraded glibmm (2.24.2-1 -> 2.28.1-1)
[2011-05-16 09:52] Running 'pacman -U glibmm-2.24.2-1-x86_64.pkg.tar.xz'
[2011-05-16 09:52] upgraded glibmm (2.28.1-1 -> 2.24.2-1)
vmware now runs again!
how did you spot that one ? I ran straces/gdb against the binary but couldn't get anything useful of it.
Offline
how did you spot that one ? I ran straces/gdb against the binary but couldn't get anything useful of it.
There are a few log files in /tmp/vmware-<name>/. One of them included a stacktrace and it ended up in a glib library. I was lucky that the only glib related library that upgraded during that time was glibmm. But, well, downgrading not really *solves* the issue.
VMware Workstation comes bundled with all the libraries it uses (in /usr/lib/vmware/lib/). At startup, it tests if your system has that library and uses it, otherwise, it uses its built-in version. Maybe someone knows a way to force Workstation to use its bundled version?
Offline
Then I tried downgrading both the x86_64 and the i686 versions at the same time.
% yum --skip-broken downgrade glibmm24-2.24.2-1.fc14.1.x86_64.rpm glibmm24-2.24.2-1.fc14.1.i686.rpm
Loaded plugins: auto-update-debuginfo, presto, refresh-packagekit
Setting up Downgrade Process
Examining glibmm24-2.24.2-1.fc14.1.x86_64.rpm: glibmm24-2.24.2-1.fc14.1.x86_64
Examining glibmm24-2.24.2-1.fc14.1.i686.rpm: glibmm24-2.24.2-1.fc14.1.i686
Resolving Dependencies
--> Running transaction check
---> Package glibmm24.i686 0:2.24.2-1.fc14.1 will be a downgrade
---> Package glibmm24.x86_64 0:2.24.2-1.fc14.1 will be a downgrade
---> Package glibmm24.i686 0:2.28.1-1.fc15 will be erased
---> Package glibmm24.x86_64 0:2.28.1-1.fc15 will be erased
--> Finished Dependency Resolution
Packages skipped because of dependency problems:
glibmm24-2.24.2-1.fc14.1.i686 from /glibmm24-2.24.2-1.fc14.1.i686
glibmm24-2.24.2-1.fc14.1.x86_64 from /glibmm24-2.24.2-1.fc14.1.x86_64
Offline