Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 4810
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Previously closed windows minimize upon reopening in IC23.10

LMendolia

Hi,

We have recently updated our organization's Virtuoso install from IC6.1.8 320 to IC23.10 020. Since then, we have encountered an unpleasant issue when using our usual remote connection method (X2Go for Windows) to access Virtuoso.
Whenever a window that was previously closed is reopened, it instantly minimizes. This becomes very annoying for frequently closed and reopened windows, such as object properties in schematics/layouts, wire name/pin creation windows, etc.

This bug occurs with any window running from Virtuoso but doesn't happen when running non-Cadence applications. It only happens on IC23.10, not IC6.1.8. We have encountered this bug on a Centos 7 system (previously running IC6.1.8 fine) and a new RHEL 9 system.

I don't know if this is related, but, since the update to IC23.10, the CIW displays the following errors when starting Virtuoso remotely:
libManager Qt Warning: QXcbConnection: Failed to initialize GLX
libManager Qt Warning: QXcbConnection: XCB error: 1 (BadRequest), sequence: 169, resource id: 245, major code: 130 (Unknown), minor code: 47
libManager Qt Warning: QXcbConnection: Failed to initialize GLX
libManager Qt Warning: QXcbConnection: XCB error: 1 (BadRequest), sequence: 169, resource id: 245, major code: 130 (Unknown), minor code: 47
These errors do not appear when starting Virtuoso on a physical display or via XRDP, and we are not encountering the bug in these instances. We have disabled GLX support in X2Go to suppress the first and third errors, but the other two and the minimization bug remain.

Any help would be greatly appreciated.

Loris

Parents

  • Loris,

    This is most likely to be an issue with X2Go (given that it doesn't happen in other display solutions), but the best thing might be to log this with customer support (submit a support case after logging in). I see that R&D have done some analysis of issues with X2Go in the past so may be able to help pinpoint the issue. The Qt version changed between IC6.1.8 and IC23.1 so that may account for the differences in behaviour.

    Regards,

    Andrew

Reply

  • Loris,

    This is most likely to be an issue with X2Go (given that it doesn't happen in other display solutions), but the best thing might be to log this with customer support (submit a support case after logging in). I see that R&D have done some analysis of issues with X2Go in the past so may be able to help pinpoint the issue. The Qt version changed between IC6.1.8 and IC23.1 so that may account for the differences in behaviour.

    Regards,

    Andrew

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.