[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: VMware interaction with screensaver



On Fri, 12 Jul 2002, Simeon Walker wrote:

> Does anyone here use VMware? I'm using the 3.0.2 debs and find that
> I can no longer start the screensaver after I have run VMware, even
> if it is no longer running.  I can run the screensaver test from the
> control panel but it will never start after the timeout and pressing
> the 'lock' button has no effect. I have seen the same problem on
> a different PC with the same VMware and KDE.
>
> Any suggestions?

unfortunatelly I can just confirm your experiences (in the most cases,
when vmware is running for longer time). it's the same for me.

normally when I click on "lock screen" it executes the
/usr/bin/kdesktop_lock --forcelock command. after I stop using vmware if I
click on "lock screen", nothing happens, the command doesn't get executed.
(the command really doesn't get executed, because I log exec*() calls with
grsecurity)

libc6 2.2.5-7, xserver-xfree86 4.1.0-17, xlibs 4.1.0-16
kdebase 3.0.2-0, kscreensaver 3.0.2-0, kernel 2.4.18, vmware 3.1

-- 
 Gabor Gludovatz <ggabor@sopron.hu>
  http://www.sopron.hu/~ggabor/ * http://gludo.sopron.hu/gpg.txt
GPG fingerprint: 8D0C 6AE8 5875 751E 5122-1DAE 4990 1A4E BC2E C8B9


-- 
To UNSUBSCRIBE, email to debian-kde-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: