-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Edmonds wrote:
Does installing vmware server console from VMware's tarball work at all?
I haven't tried yet, and I'm a little reluctant to do so.
And, is it possible to use etch in your situation? VMware products tend
to have good
James Healy wrote:
After further testing, I concur that the gtkrc error message is not the
cause of my troubles. Even if I fix that error, vmware-server-console
fails to launch. It just exits silently with a return code of 0.
Could you send the full output of strace -f vmware-server-console
21
James Healy wrote:
Robert Edmonds wrote:
Could you send the full output of strace -f vmware-server-console
21 in this case?
attached.
Thanks. Based on the output, could you also send the log files that
vmware generates (I believe they're written somewhere in /tmp), and try
to collect and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Edmonds wrote:
Thanks. Based on the output, could you also send the log files that
vmware generates (I believe they're written somewhere in /tmp), and try
to collect and send a core file by invoking ulimit -c unlimited before
James Healy wrote:
Package: vmware-package
Version: 0.9
Severity: important
When attempting to run vmware-server-console on my i386 machine, I get
the following error. The machine in question is *not* the one running
vmware-server - vmware-server-console is the only vmware package that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The i386 machine you've submitted the bug on is running unstable; what
are you running on the amd64 host?
Stable, although I was naughty and changed sources.list to sid just long
enough to grab vmware-package (and 2-3 associated upgrades due to
James Healy wrote:
The i386 machine you've submitted the bug on is running unstable; what
are you running on the amd64 host?
Stable, although I was naughty and changed sources.list to sid just long
enough to grab vmware-package (and 2-3 associated upgrades due to
dependencies).
Is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Edmonds wrote:
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc is located in the
gtk2-engines package, whose description says
[...]
The package includes the following engines:
* Clearlooks, the default GNOME theme, based on
James Healy wrote:
Yep, I'm running gnome. With a different theme the same error occurs,
but with the path pointing to the relevant theme's gtkrc. Under KDE it
silently fails to launch.
What happens if you run it under an X environment that is not KDE or
GNOME?
What happens if you create a
9 matches
Mail list logo
