K
kentauta
Guest
Hello all,
When I remotely use (with a Windows-based X-server software) Virtuoso
Schematic Composer installed on a Linux box, it takes about 8 seconds
to close a fully expanded component property window. Shrunk property
windows close very quickly.
According to a network monitoring software, a lot of packets are
trasfered between the X-server software and the Linux server running
Cadence while the property window is being closed. I do not have
such a problem at all when I run Cadence locally on the Linux server
probably because those packets are internally transferred very
quickly. In addition, I have not had this kind of problem with
SunOS-based Cadence.
I have tried several Linux-based servers with different
distributions such as Debian(2.4 and 2.6) and Gentoo(2.6), two
different X-server sotwares, and many different window managers such
as twm, olvwm, etc. However, the same problem occurs in any case.
Version of Cadence is 5.0.33.500.2 (IC5033USR1 lnx86).
Unfortunatelly, I do not have access to Sourcelink as the licenses
belong to my school.
I am wondering if this is a bug of Cadence, and seeking a way to
solve this problem.
Any help is appreciated.
Thank you,
When I remotely use (with a Windows-based X-server software) Virtuoso
Schematic Composer installed on a Linux box, it takes about 8 seconds
to close a fully expanded component property window. Shrunk property
windows close very quickly.
According to a network monitoring software, a lot of packets are
trasfered between the X-server software and the Linux server running
Cadence while the property window is being closed. I do not have
such a problem at all when I run Cadence locally on the Linux server
probably because those packets are internally transferred very
quickly. In addition, I have not had this kind of problem with
SunOS-based Cadence.
I have tried several Linux-based servers with different
distributions such as Debian(2.4 and 2.6) and Gentoo(2.6), two
different X-server sotwares, and many different window managers such
as twm, olvwm, etc. However, the same problem occurs in any case.
Version of Cadence is 5.0.33.500.2 (IC5033USR1 lnx86).
Unfortunatelly, I do not have access to Sourcelink as the licenses
belong to my school.
I am wondering if this is a bug of Cadence, and seeking a way to
solve this problem.
Any help is appreciated.
Thank you,