After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619519 - LP-solver doesn't start
LP-solver doesn't start
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
1.10.x
Other Windows
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2010-05-24 14:19 UTC by jochen.wilhelm
Modified: 2010-12-01 16:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jochen.wilhelm 2010-05-24 14:19:59 UTC 
Trying to start the solver by pushing the "solve"-button ands in a error-message related to some "child process" that can't be started ("no such directory or file")
Comment 1 Morten Welinder 2010-05-24 14:58:01 UTC 
Did you install lpsolve?

What is the precise error message?
Comment 2 jochen.wilhelm 2010-05-24 16:32:55 UTC 
lpsolve has been installed.
The error message reads "Kindprozess konnte nicht ausgeführt werden (No
such file or directory)" (German language installation)
Comment 3 Morten Welinder 2010-05-25 00:48:00 UTC 
We were supposed to catch "no such directory or file" and substitute a sane
error message.  Due to a glib bug that did not happen -- now fixed.
See bug 619564 for that part.

But the error message still means that the program isn't being found.
For win32 we might need to search for it somewhere outside $PATH.
Comment 4 jochen.wilhelm 2010-05-27 13:25:50 UTC 
When gnumeric is started from the command window the lpsolver returns the following message "(gnumeric:2512): GLib-WARNING **: passing a child setup function to the g_spawn
functions is pointless on Windows and it is ignored"
Comment 5 Morten Welinder 2010-05-27 13:31:52 UTC 
> GLib-WARNING **: passing a child setup function to the g_spawn

I see that, but it is not the problem.  I'm not sure it will be a problem
at all on win32.
Comment 6 Morten Welinder 2010-07-04 03:14:23 UTC 
This might be fixed in the next release.  (I.e., it needs to be verified
on win32.)
Comment 7 Morten Welinder 2010-12-01 16:40:37 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.