Stats

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

  • Thanks for the explanation, Andrew.

    I contacted supported (back in August), but they didn't show much interest in the case - which surprises me.

    Do you have some contacts, that have insight in the Cadence source and want to throw a couple of hours into fixing either Fedora (i.e. Xorg, I guess) or Cadence depending on the source of the error ? Just a couple of words on how to debug this, or which exact feature to direct the debugging will be a huge help.

    People are completely stuck with this issue. E.g.

    https://bugzilla.redhat.com/show_bug.cgi?id=1010181

    https://bugzilla.redhat.com/show_bug.cgi?id=1004979

    As RHEL7 will be based on Fedora 19, I'm disappointed that Cadence does not prioritize this higher. Either the bug should be fixed in RHEL, or it should be changed in Cadence. The sooner, the better in order to provide legacy support for "old" (in future terms) versions of Cadence..

    Best regards,

    Kenneth

Reply

  • Thanks for the explanation, Andrew.

    I contacted supported (back in August), but they didn't show much interest in the case - which surprises me.

    Do you have some contacts, that have insight in the Cadence source and want to throw a couple of hours into fixing either Fedora (i.e. Xorg, I guess) or Cadence depending on the source of the error ? Just a couple of words on how to debug this, or which exact feature to direct the debugging will be a huge help.

    People are completely stuck with this issue. E.g.

    https://bugzilla.redhat.com/show_bug.cgi?id=1010181

    https://bugzilla.redhat.com/show_bug.cgi?id=1004979

    As RHEL7 will be based on Fedora 19, I'm disappointed that Cadence does not prioritize this higher. Either the bug should be fixed in RHEL, or it should be changed in Cadence. The sooner, the better in order to provide legacy support for "old" (in future terms) versions of Cadence..

    Best regards,

    Kenneth

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.