I was run the 15.1 version 1.8 of this and updated to a newer experimental package v1.9 but it has the same problem when I get to simulating a circuit. Both installed 1 click style via yast.
This error message is generated as soon as I select simulate, That should just pop up another tabbed window.
:'(Help. No other problems with the package. So far.
Out of interest I also tried compiling the latest verion - 2.0 but config complained about the version of Qt. Must be greater than 4.6, thought i was running 5,x
Only when I click simulate and the official 0.18 version does exactly the same thing as the 0.19 version. Undefined symbol error. This is often mentioned as a linkage error on the web so assume this should be in a dev file some where.
Perhaps the best way for some one else to check it is to load one of the sample designs and then select simulation. I’d suggest
My depository list includes a number of disabled ones - left over from previous problems and nothing is now installed from them. The “odd” ones are for photo applications, multimedia. I do have pulse utilities installed as well. That initially gave rise to my previous problem.
In some ways I would rather install odd applications like this from source as I then know exactly what needs to be added rather than risking getting some odd mix from a repo. This leaves the question why ./config fails with this message if I compile qucs 2.0
configure: error: Qt >= 4.6.0 is required
I had a similar problem on another application that used a version of automake. System was up to it’s needs but somehow it detected older versions. This one also had ./config and I had no problems that way just needed to load a couple of lib files from the 15.1 repo.
This is a bit of a bleat really but worrying as I suspect all would be ok on Ubuntu as that generally seems to be all that is checked and often all that is supported now. I’m a long term OpenSuse man and Suse before that.
It looks like the image I linked to hasn’t loaded. All that it indicated is that qucs has no problems at all producing schematic diagrams.
That sounds like it might relate as while I shouldn’t I tried running it as root and got that style of error message. Run as user doesn’t do that. Another ap I installed cleanly wouldn’t run. Turned out that I needed to be a member of the dial out group. I have wondered if it might be a permissions problem but have no idea which one it could be.
The Qt aspect suggests that 5 is not greater than 4.x that it requires.
My repo’s. Afraid I can’t see that it having anything to do with the problem as the official one does the same thing. I don’t think YAST pulled anything in when I installed both versions. The applications i have added are well supported for opensuse. Just photo related ones that are very popular. Used some for years on different releases without any problems at all. quantas94heavy is wine only. When needed I find play with linux far more reliable than straight wine. That leaves packman. The 2 versions came from qt5 repo’s so I am inclined to wonder if ok the built without problems but where not completely tested.
I’ll see what’s on github. This is frustrating. For what it is not a bad app that could do with a little tidying in places - pretty small changes really.
Hi
Yes, but if a library has been ported to qt5 and introduced to the Leap series, then your going to bang your head against the wall, it’s not like qt4 got deprecated overnight. I would suggest an upstream bug report asking them to port their code to something that is supported.
You could raise a qucs openSUSE bug but I suspect it may get closed, suffice to say I can duplicate with only the default repos, so it may have already been broken before the Leap release… Also realize it’s been dropped in Tumbleweed already since it’s qt4…
I’m not sure how upstream bugs are reported. Maybe some one can tell me how. A git search bought up signs of qt version fixes. There may also be a spin off from it that uses a different simulator.
The spin off is called Qucs-S and uses ngspice for simulation. That is available in the repo. Qucs-S is only shown for tumbleweed. Suppose I could try it but … doesn’t sound like a good idea. If I try and compile this one it states must be version Qt4.
I may have found a solution to qucs-s compiles anyway.
The solution to compiling turned out to be searching for qt4 in YAST and adding the dev file. That allowed both qucs and qucs-s to compile but it took rather a long time on one during configure so I went out. There seem to be a lot of depreciated errors. Just installing the dev file didn’t help the one click opensuse versions.
Both now produce this error when I select simulation
line 70: syntax error, unexpected Identifier, expecting '"'
However an example appears to work so that may be down to me moving things around in the schematic and the netlist changes not always working cleanly. :’( Or ???
I’ve now tried all versions of qucs. Qucs 0.02 seems to be ok but have only simulated an example. Qucs-S probably means hours searching for parts definitions to suite spice but it looks like the latest versions of that can also be made to work.
I’ve been getting on reasonably well with qucs “normal”. Just installed the dev file I mentioned and compiled qucs 0.02. All problems so far but for one 10mins ago are down to me and spice syntax. Latest one may be down to me or might be asking it to analyse too much. For a beta and I think all versions are it’s not bad. Some polish needed on the graphics really but they do work as is and offer some interesting features. It does appear to simulate correctly. It’s saved me building several microphone amps based loosely around one on the web which I found isn’t as good as it appears. Flawed in fact.
Qucs-S comes with warnings especially in the simulation area - favourite seems to be a very recent spice implementation. Reminds me of a video on youtube - why Linux stinks. Several different groups of people working on the same functionality and imagine what they would achieve if they all worked together on the same thing. Qucs went it’s own way on spice as they reckon the existing ones are impossible to work on. Reminds me of KDE3 and probably the demise of 4etc. Seems to happen quickly these days.
The main thing that seems to be lacking in this whole area is some easy method of importing spice files. They are apt to differ according to where they are coming from. Even analogue devices seem to have that problem in their free windows one. It can be done but using an appropriate symbol seems to be another matter. I’d have thought that the IEEE would have produces some standards but … no sign of them.
Latest Qucs-S also compiles with the dev file added. I’ve posted that Qt5 should come with a 4 library and also a 3 to 4 as several comments on the web say Qt is a no no with both of them.
This is frustrating. For what it is not a bad app that could do with a little tidying in places - pretty small changes really.
It’s saved me building several microphone amps based loosely around one on the web which I found isn’t as good as it appears. Flawed in fact.
Reminds me of a video on youtube - why Linux stinks. Several different groups of people working on the same functionality and imagine what they would achieve if they all worked together on the same thing. Qucs went it’s own way on spice as they reckon the existing ones are impossible to work on. 
Reminds me of KDE3 and probably the demise of 4etc. Seems to happen quickly these days.