Gschem: gschem wont start and gives unrelated error message when when guile can't open script

Bug #1492599 reported by Jason
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gEDA
Triaged
Medium
Unassigned

Bug Description

You can recreate this issue on a clean system (free of previous installs) by making gschem but not installing. When you try to run it one of the guile startup scripts will not exist at its hard coded path in gschem. When guile tries to open the non-existent file gschem crashes with no helpful error message.

Backtrace:
In ice-9/boot-9.scm:
157: 1 [catch #t #<catch-closure 8277be0> ...]
In unknown file:
  ?: 0 [apply-smob/1 #<catch-closure 8277be0>]

ERROR: In procedure apply-smob/1:
ERROR: In procedure scm_to_utf8_stringn: Wrong type argument in position 1 (expecting string): #f

How to fix:
In general, have gschem check if a scheme script exists before having guile run it. Guile seems to be incapable of handling this gracefully and does not produce comprehensible error messages in this case.

Changed in geda:
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.