You are not logged in.

#1 2012-06-13 02:07:31

MartinZ
Member
From: Chiloé, Chile
Registered: 2005-06-10
Posts: 379

freemedforms segmentation fault

I'm very interested in the QT application FreeMedForms. However, I have compiled the package from AUR several times (for versions 0.7.0, 0.7.3 and 0.7.4) and always get this error:

"Main" "Command line: freemedforms" 
"Main" "Running release version" 
"Main" "Linux Integrated" 
"Main" "looking for libraries in path: /usr/lib/freemedforms;/usr/lib/qt/plugins;/usr/bin;/usr/lib/kde4/plugins" 
"Settings" "Trying ini file /home/martin/.freemedforms/config.ini" 
"Settings" "Using ini file /home/martin/.freemedforms/config.ini" 
"Settings" "Using network ini file /home/martin/.freemedforms/config-net.ini" 
"** ERROR(databaseconnector.cpp:229)" "DatabaseConnector" "Decrypt error" 
"ThemePrivate" "Setting theme path to: /usr/share/freemedforms" 
Segmentation fault

Some details of my system:

x86_64
KDE 4.8.3
kernel 3.4.0-1-ck
Nvidia 9600M with proprietary drive (nvidia-ck-corex 295.53-2)

I would really appreciate some help with this.

Last edited by MartinZ (2012-06-13 02:10:31)


All your base are belong to us

Offline

#2 2012-06-13 02:21:54

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: freemedforms segmentation fault

This looks like an upstream bug.  Perhaps if someone else here uses this software, they might know some details, but this is not a compilation or arch-based problem.  It's almost certainly a bug in the upstream source.

Have you tried asking on the forum for that software?


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2012-06-14 15:10:31

MartinZ
Member
From: Chiloé, Chile
Registered: 2005-06-10
Posts: 379

Re: freemedforms segmentation fault

Thanks a lot for answering (and sorry for the delay, I didn´t have internet access until now).

That´s exactly what I thought, but I googled a lot and couldn´t find any reference to a segmentation fault like this. And considering that version 0.7.0 is out since 3 months, I thought it should be a problem of PKGBUILD or mine.

I'll ask there and let you know.


All your base are belong to us

Offline

#4 2012-06-14 15:44:45

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: freemedforms segmentation fault

One thing to note is the last line before the segfault: do you have a /usr/share/freemedforms/ directory?  I downloaded the source and ran qmake (following the PKGBUILD) and I can't find anything in the makefiles or installation that would create that directory - yet one of the source files has that path hard-coded in.  This could be the problem.

FYI: grep found this as the only reference to that path anywhere in the package source.  This is referenced from one line of the source code, but never created in the installation.  If this turns.  Unless freemedforms expects to be run as root, there is no way this path could be created at runtime, and this would likely lead to a segfault - though it may not be the only problem.

plugins/coreplugin/settings.cpp:        setPath(BundleResourcesPath, QString("/usr/share/freemedforms"));

If this is a likely cause of the problem (ie, if you don't have a /usr/share/freemedforms directory) then I'd suggest finguring out where the themes really are and either A: modify that line of the source code to point to the proper location, or B: create that directory and move the themes there [or C: (personally unpreferred) create the missing path as a symlink to where the themes actually are.]

If you did not get any themes with the installation, you may have to track them down and download them manually.  Alternately, you could try just creating that missing directory and leave it empty.  You may get oddities from the app not having any theme, but this may at least stop it from seg faulting.

EDIT:
Oops: grep of course only searched for that path verbatim in the installation files.  Perhaps that directory was created as a $prefix/share/freemedforms or some such.
EDIT:
I found MANY references to paths like

freemedforms/freemedforms-src/Makefile:	 -$(DEL_FILE) -r $(INSTALL_ROOT)/usr//share/freemedforms/package_helpers/freetoolbox.iss

Changing the PKGBUILD cmake install root line to

"INSTALL_ROOT_PATH=$pkgdir/usr" \

(ie, remove the trailing slash of the path) fixes that problem.  However, I doubt this would cause the problem.

Copying a file to some/long//path/ should have the same affect as copying to some/long/path/ even though the former is ugly.

Last edited by Trilby (2012-06-14 16:04:24)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

Board footer

Powered by FluxBB