xscreensaver process messes up cadence session ...

Hi,

We just have migrated to Linux and encountered a problem when running
cadence in combination with the xscreensaver daemon:

On some of our desktops (running RH enterprise 3.0) cadence windows get
blacked out (don't know whether this is a valid definition but anyhow:
The contents of the cadence windows are just plain black) whenever the
xscreensaver process is running ("xscreensaver -nosplash" to be
exactly) and the user switches focus from the cadence app to either
another window or a different desktop and then re-enters the desktop
with cadence in it again. Killing this xscreensaver process immediatley
solves the problem.

My question: Has anyone else over here experienced the same behaviour?
If so: What it the more elegant solution (after all killing the
xscreensaver process isn't really a solution but more fightin' the
symptom)?
The graphical card used is a Matrox Millenium G450

Rgds,

Jan.

 

If it doesn't happen on other video cards, this sounds like a potential
xscreensaver + Matrox issue.

The Matrox card is different -- it supports a 24+8 mode which allows
Cadence to run in its preferred 8-bit mode while everything else runs in
its full 24-bit glory. If you have enabled a screen saver which applies
an effect on the current desktop (say, melting your screen, etc.), I
could imagine some peculiar interaction there.

What about screen captures? Does /usr/bin/gnome-panel-screenshot make
correct copies of the screen?

Also, it would help if you could note which tools and versions of
"Cadence" you're running -- there have been a number of changes which
affect redrawing on Linux.

 

David,

Thx for your response.

First to answer your question if it is caused due to (a) specific
type(s) of savers: I don't think so because even running the daemon
without havng selected any saver iself causes this behaviour!

Secondly you ask what specific tool(set) we're using: It is already
apparent in the CIW (without having any other application open). A
typical setup this user works in however is only having the viruoso
composer open (at a digital toplevel) to descend into the verilog text
blocks from that level. Not too complex I would say.

I guess you are right: it's probably caused by the combo
Matrox/Cadence. Our latest Linux desktops have nVidia cards (PCI-E)
which don't show this behaviour at all.

Rgds,

Jan.