• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Cadence 6 Key Lock

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13014
  • 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

Cadence 6 Key Lock

GTStan
GTStan over 13 years ago

Hello Gentlemen, My research team and I are encountering an issue in Cadence 6 (IC6.1.4.500.13 (32-bit)) where dialogue boxes will suddenly be unresponsive to key stroke entries.  This seems to happen at random intervals and the only means of fixing this issue has been to do a cold re-boot of Cadence 6.  We have attempted closing and re-opening all dialogue boxes, but the boxes still remain unresponsive to key strokes.  The CIW will however respond to keyboard entries.  Any insight would be appreciated!

  • Cancel
Parents
  • skillUser
    skillUser over 13 years ago

    Hi,

    I've seen this under various circumstances, for me it only seemed to happen with a certain window manager setup (Gnome or KDE, I can't remember which, but I don't think that I suffered this issue with IC61x on FVWM) but I think that the culprit was an environment variable setting "XMODIFIERS" - try removing this setting (or changing it?) and see if the problem still occurs. If I remember correctly, removing this setting fixed the issue for me.  Not sure if it is important whether VNC was involved or not, I think that the problem occurred if I was sat directly at the terminal too.

    Hope this helps!

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 13 years ago

    Hi,

    I've seen this under various circumstances, for me it only seemed to happen with a certain window manager setup (Gnome or KDE, I can't remember which, but I don't think that I suffered this issue with IC61x on FVWM) but I think that the culprit was an environment variable setting "XMODIFIERS" - try removing this setting (or changing it?) and see if the problem still occurs. If I remember correctly, removing this setting fixed the issue for me.  Not sure if it is important whether VNC was involved or not, I think that the problem occurred if I was sat directly at the terminal too.

    Hope this helps!

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information