libManager Qt Warning -> errors

Not really a supported combination, but it's most likely to be an issue with the X server implementation in Fedora 19 (a bit on the bleeding edge!).

Probably best to contact customer support, and then we can see if it's possible to take a look internally - although strictly speaking we can't support every type of display going - because that ends up being an enormous test matrix.

Regards,

Andrew.

 Thanks for your answer, Andrew.

 I understand that Cadence cannot support any Xserver implementation that people come up with. That said, I actually never saw requirements on the client machine - but maybe I missed it?

 I will contact them, as you suggest. Since only the LIbrary Manager is hit by the error (unfortunately a very vital window) I suspect it is a real bug in the implementation. So, although not being a supported combination, it is probably advantageous to correct it

 Fedora 19 is on the bleeding edge, yes. But I wont be surprised if the same Xserver ends in RHEL7, which I expect Cadence to support in the longer run.

Best regards,

Kenneth

Kenneth,

Very rarely is any issue on a particular X client down to the software itself, since if it was you'd expect it to show up on most (if not all) other clients. Occasionally though there are things we can do with the software to solve the problem - for example, we had an issue with the library manager displaying on an Apple Mac, using XQuartz, caused by the fact that the library manager required a 16 plane visual, and this was no longer supported on XQuartz. There was no particularly good reason for it to use 16 plane visuals, and since the rest of virtuoso uses a 24 plane visual, we switched the default to that, which solved the problem - see solution 11843504 if you're interested.

We don't explicitly list clients that are supported for this reason - and we only test on a small number (mostly native clients, I believe).

Anyway, hopefully we can help you through customer support.

Regards,

Andrew.

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

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.