I am trying to bring up draftsight, downloaded from dassault-systemes as an rpm.
Installed without complaints/issues on my 12.3/kde4.10.5 laptop.
from cli, I get
carl@HPDV7T-Linux:/opt/dassault-systemes/draftsight/bin> ./draftsight
./draftsight: line 34: 27500 Segmentation fault "$BINARY"
Is anyone successfully running draftsight on 12.3?
Is that a bash script being run which then calls the binary? It looks like it may be. Try this to obtain some more info:
$head draftsight
then, if it is a bash script:
$bash -x draftsight
That should provide additional debug info for at 34 and before to help determine what may be doing on.
Also, per any draftsight documentation are you supposed to set any environmental variables before running it? (The script itself might say.)
You might want to run ldd on the binary itself (draftsight.bin maybe?) and see if it’s missing any libraries.
Sorry can’t help you with the problem.
Draftsight here is running on 12.3.
Did you checked on that error?
Thanks, gents for the suggestions.
ldd draftsight.bin in the draftsight directory yields no obvious issues.
draftsight is in fact a shell script, the error is reporting a seg fault when the selected binary is executed.
conram - two questions
Do you simply launch “draftsight”, or do you launch with “draftsight - style xxxx”?
Can I assume your 12.3 is up to date?
Reason I ask is that an update I ran on August 9 seems to have rendered another CAD program I have, qcadPro, inoperable with a similar segfault.
In that case, ldd yields no immediately useful errors as well.
I am suspicious that a point release on one of the system libraries is the cause in the qcadPro case, might be similar (or same ) issue here.
Hello,
I can also report no problem using DraftSight V1R3.2 under OpenSUSE 12.3 64bit. I have it installed on two different computers.
I used to have problems with draftsight under fedora year ago, it was segfaulting unless I ran it as root. But this seems like a different problem.
Pol
semhustej - Thanks for your info.
My issue persists.
I originally was asking when my install on intel/intel graphics laptop would not start up.
Today I installed draftsight rpm for V1R32 on my AMD/AMD graphics desktop which had not been updated since early June (I was on holiday).
Draftsight started up as expected.
I then performed an update to today, August 20 and draftsight now SegFaults same as laptop.
I am running 12.3_64 with KDE 4.10.5. Are you machines similar (KDE)?
PS
draftsight does install a .desktop file in /user/share/applications, if you like to have an icon based launch from desktop.
Yes, this 12.3 is up to date.
I can run it from the terminal using the command draftsight or from the launcher. (“/opt/dassault-systemes/draftsight/bin/draftsight”)
I am using nvidia graphic card and running it on xfce 4.10.
conram
Thanks, perhaps this is becoming a KDE MESA issue.
I’ll convert my 12.3 VM to xfce to see what I get.
One of my machines is GNOME 3.6, the other XFCE 4.10. The .desktop file somehow got screwed up when upgrading to V1R3.2, it was working fine before that.
Let us know whether changing the desktop solved the problem.
OK, I am getting more than a bit confused here, but some progress just the same.
This AM I set off to build a new oS 12.3 Virtual Machine in Vbox. I installed three desktops, KDE 4.10.5, Gnome and XFCE.
When install and updates were done, I found that draftsight worked under KDE.
I have not tried Gnome or XFCE yet, both are new to me.
I then switched back to my host 12.3/KDE 4.10.5 interface and draftsight now started up there as well.
I can’t be sure, but believe some updates to kdm that were loaded last evening in an update may be the cause of this change.
Interestingly, issues on the same machine with another CAD program (qcadPro) also have disappeared on this machine, my amd/ati graphics desktop, as well.
I still have issues with my intel/intel graphics laptop.
I continue to believe there is some flaky behavior among KDE, Mesa and the various video drivers.
Another installment and success, of sorts.
My intel/intel graphics Laptop was still exhibiting the Segfault behavior with my qcadPro software, draftsight was OK
I decided to try the XFCE desktop, so installed the XFCE base and Desktop patterns using YAST.
Numerous files downloaded, as expected.
As a final KDE 4.10.5 desktop check before logging out, I once again tested the qcadPro and it worked!
I will sift thru /var/log/zypp/history when I get a chance to see if I can spot a potential items of interest.
Perhaps a different version of a MESA file or ??
So now I have my CADs working and can play with XFCE as well.
I’ve just installed DraftSight on 12.3 and it won’t run with this line in the sys log; “draftsight.bin[13079]: segfault at f17b0eb1 ip 00000000f43544b0 sp 00000000ff9c2cb8 error 7 in libTD_FtFontEngine.so.1[f4309000+84000]” installed both Gnome and XFCE desktops along with KDE but still no joy, anyone have any ideas.
Thanks.
This may not help much; I have not had any recent issues with Draftsight V1R3.2.
I am currently running oS 12.3/KDE 4.11.3.
It appears that libTD_FtFontEngine.so.1 is provided by the Draftsight RPM, so there is not an obvious dependency issue.
I have no other great ideas.
Recent install, or long term install that “suddenly” stopped working?
One thought - I see that Drafsight is a 32 bit APP.
Do you have 32bit environment installed for your oS 12.3?
Start it from the command line that should give you more information. You may need to install some 32 bit versions of some libraries
Thanks for the reply and to answer your questions, it’s a recent install of 12.3 and I do have 32 bit environment installed, most of it installed with draftsight, shame they don’t do a 64 bit for linux.
I assume you downloaded the rpm from the Dassault web site and installed with Yast (or zypper).
Did you try Gogalthorps suggestion?
Here is what I get
~> /opt/dassault-systemes/draftsight/bin/draftsight
Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
When I execute this from a Konsole, I get the above warning, then the GUI window opens.