Glint on keyboard input under Gnome

[royan]

Hi everybody!

I'm experiencing a problem which occurs in most applications under Gnome.
On every key press the screen glints at a random position (seems to be a
black line, 1 px height, ~50px width).

Any ideas where to look at?

Thank you in advance.

Regards,
Helge


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Using VMWare Player

[royan]

There is a "failed" message here. You should ask VMware why it doesn't
> work, or, if you are longing for some action, open the VMware startup
> script (/etc/init.d/vmware) and see if you can spot the problem.
> 


Hi!
Thanks for your hint.
I found out I had to install ia32-libs to sucessfully install.
Now it's running just fine.

Helge



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Using VMWare Player

[royan]

Hi! 
Here is the output of the vmware-configure process

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Virtual Machine Player is
suitable for your running kernel.  Do you want this program to try to build the
vmmon module for your system (you need to have a C compiler installed on your
system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.12-1-amd64-generic/build/include] /usr/src/linux-headers-2.6.12-1-amd64-generic/include

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Gehe in Verzeichnis »/tmp/vmware-config0/vmmon-only«
make -C /usr/src/linux-headers-2.6.12-1-amd64-generic/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Gehe in Verzeichnis »/usr/src/linux-headers-2.6.12-1-amd64-generic«
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/hostif.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/hash.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/task.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST
  CC  /tmp/vmware-config0/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Verlasse Verzeichnis »/usr/src/linux-headers-2.6.12-1-amd64-generic«
cp -f vmmon.ko ./../vmmon.o
make: Verlasse Verzeichnis »/tmp/vmware-config0/vmmon-only«
The module loads perfectly in the running kernel.

[...]

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Gehe in Verzeichnis »/tmp/vmware-config0/vmnet-only«
make -C /usr/src/linux-headers-2.6.12-1-amd64-generic/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Gehe in Verzeichnis »/usr/src/linux-headers-2.6.12-1-amd64-generic«
  CC [M]  /tmp/vmware-config0/vmnet-only/driver.o
  CC [M]  /tmp/vmware-config0/vmnet-only/hub.o
  CC [M]  /tmp/vmware-config0/vmnet-only/userif.o
  CC [M]  /tmp/vmware-config0/vmnet-only/netif.o
  CC [M]  /tmp/vmware-config0/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-config0/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-config0/vmnet-only/smac_compat.o
  SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x86_64.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST
Warning: could not open /tmp/vmware-config0/vmnet-only/includeCheck.h: Invalid argument
  CC  /tmp/vmware-config0/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Verlasse Verzeichnis »/usr/src/linux-headers-2.6.12-1-amd64-generic«
cp -f vmnet.ko ./../vmnet.o
make: Verlasse Verzeichnis »/tmp/vmware-config0/vmnet-only«
The module loads perfectly in the running kernel.

Starting VMware services:
   Virtual machine monitor done
   Virtual ethernet    done
   Bridged networking on /dev/vmnet0  failed
   Host-only networking on /dev/vmnet1 (background)    done

The configuration of VMware Virtual Machine Player 1.0.0 build-18007 for Linux
for this running kernel completed successfully.

You can now run VMware Virtual Machine Player by invoking the following command:"/usr/bin/vmplayer".


Running vmplayer still brings up the message saying vmware needs to be configured.

Any ideas?

Thank you in advance.

Helge

Re: Using VMWare Player

[royan]

Hi!



> be sure that your kernel sources match perfectly your running kernel...




uname -r returns 2.6.12-1-amd64-generic

The directory I used for kernel headers during the vmware-configure
process was
/usr/src/linux-headers-2.6.12-1-amd64-generic/include

Doesn't seem to be wrong, does it?

Thank you in advance

Helge

Using VMWare Player

[royan]

Hi, 

did anyone sucessfully install the VMWare Player under debian-amd64 and could give me some advice?
After downloading the tar.gz from vmware.com and using the install script I get an error saying that vmware wasn't correctly configured.
After reconfiguring I'm getting that same message again.

Thank you in advance.

Helge