Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 3744
  • 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

libManager Qt Warning -> errors

kennethbrun

I run IC615 on a RHEL5 server. It used to work fine, but now I updated my client machine to Fedora 19, and this gives some strange errors in the library manager.

Virtuoso version: --

Program: @(#)$CDS: virtuoso version 6.1.5 03/11/2013 22:51 (sjfdl066) $

Sub version: sub-version IC6.1.5.500.16.2 (32-bit addresses)

--

 

 

The Library Manager is completely useless and doesnt respond to any mouse actions (other than giving endless errors as the example below).

 

Any ideas on how to debug it?

From Virtuoso window:

--

Xlib: sequence lost (0x107f2 > 0x19ab) in reply type 0x0!

libManager Qt Warning: X Error: 0 0

Major opcode: 113 (X_KillClient)

Resource id: 0x18b0000

Xlib: sequence lost (0x10000 > 0x19ab) in reply type 0x0!

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0xff7ff87f

Xlib: sequence lost (0x10000 > 0x19ac) in reply type 0x2!

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

Xlib: sequence lost (0x10000 > 0x19b3) in reply type 0x0!

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

libManager Qt Warning: X Error: 0 0

Major opcode: 0 ()

Resource id: 0x0

Xlib: sequence lost (0x1411c > 0x19b3) in reply type 0x1c!

Xlib: sequence lost (0x1230f > 0x19b3) in reply type 0xf!

Xlib: sequence lost (0x10201 > 0x19b3) in reply type 0x1!

libManager Qt Warning: Qt-subapplication: Fatal IO error: client killed

--

 

Parents

  • Kenneth,

    It wasn't a case of not having interest in it, it was just a matter of not prioritizing something on an (as yet) unsupported OS version. Fedora isn't supported anyway, and whilst RHEL7 will be, the roadmap is for new base releases (and that doesn't mean existing releases) to support it from 2H 2014. So that means at least IC617. Usually we do what we can to ensure that legacy releases also will continue to work on newer OS versions too.

    There was interest in looking into this from Product Engineering and R&D - it's just that they couldn't prioritize it right now given that current releases are not supported on Fedora 19 or RHEL7. There's a reasonable likelihood that the bug will have been resolved by the time we get that far or RHEL7 starts being adopted. We do work closely with RedHat and other organizations to feed back and fix bugs - and the relevant people have been involved - they just are busy right now on other priorities - supporting our current releases on currently supported platforms.

    Kind Regards,

    Andrew.

Reply

  • Kenneth,

    It wasn't a case of not having interest in it, it was just a matter of not prioritizing something on an (as yet) unsupported OS version. Fedora isn't supported anyway, and whilst RHEL7 will be, the roadmap is for new base releases (and that doesn't mean existing releases) to support it from 2H 2014. So that means at least IC617. Usually we do what we can to ensure that legacy releases also will continue to work on newer OS versions too.

    There was interest in looking into this from Product Engineering and R&D - it's just that they couldn't prioritize it right now given that current releases are not supported on Fedora 19 or RHEL7. There's a reasonable likelihood that the bug will have been resolved by the time we get that far or RHEL7 starts being adopted. We do work closely with RedHat and other organizations to feed back and fix bugs - and the relevant people have been involved - they just are busy right now on other priorities - supporting our current releases on currently supported platforms.

    Kind 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.