Bug 11620

Summary:	lilypond would not execute, could not find file lily.scm because it's in /usr/share/lilypond which is not in PATH.
Product:	Mageia	Reporter:	Jim Garrett <jimgarrett001>
Component:	RPM Packages	Assignee:	Thomas Spuhler <thomas>
Status:	RESOLVED INVALID	QA Contact:
Severity:	critical
Priority:	Normal	Keywords:	Triaged
Version:	3
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	lilypond	CVE:
Status comment:
Attachments:	An example lilypond file that successfully creates a music PDF with lilypond dobrudjansko-horo.ly

Description Jim Garrett 2013-11-08 04:07:36 CET

Description of problem: lilypond will not execute because key files are not found, even though the package is installed.  Critical files are in /usr/share/lilypond/2.16.1/scm.  Being written in Scheme, these are essentially the executables.  But these files are not in the PATH, so the application fails instantly.

I added the folder to the path in my .bash_profile, but that's not a system-wide fix.

Version-Release number of selected component (if applicable):


How reproducible:  Completely.


Steps to Reproduce:
1. Create a test text file called test-file.ly.  It doesn't matter what's in the file.
2. lilypond test-file.ly.



Reproducible: 

Steps to Reproduce:

Comment 1 Jim Garrett 2013-11-08 04:10:38 CET

Created attachment 4497 [details]
An example lilypond file that successfully creates a music PDF with lilypond dobrudjansko-horo.ly

Manuel Hiebel 2013-11-08 19:53:35 CET

Keywords: (none) => Triaged
Assignee: bugsquad => thomas

Comment 2 Thomas Spuhler 2013-11-08 22:55:42 CET

Jim, I tried your file on three different boxes, all mga3.
Lilypond converts on all of them into a pretty pdf on all three boxes.
Did something go wrong during your installation?
One was upgraded from mga3, the others were virgin installs.

Status: NEW => ASSIGNED

Comment 3 Jim Garrett 2013-11-09 03:00:30 CET

I uninstalled and reinstalled lilypond, reverted my path to its previous state, and lilypond now works fine.  Probably something went wrong during install, as you suggested.  Thanks for your attention!

Status: ASSIGNED => RESOLVED
Resolution: (none) => INVALID