http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c2 --- Comment #2 from Jan Nieuwenhuizen 2010-01-05 09:59:19 UTC --- I cannot run a backtrace, as it seems that ghostscript-library-debuginfo and ghostscript-library are out of sync in factory. peder:/usr/src/packages/BUILD/lilypond-2.12.3> gdb /usr/bin/gsGNU gdb (GDB) SUSE (7.0-1.9) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/gs... warning: the debug information found in "/usr/lib/debug//usr/bin/gs.debug" does not match "/usr/bin/gs" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/bin/gs.debug" does not match "/usr/bin/gs" (CRC mismatch). Missing separate debuginfo for /usr/bin/gs Try: zypper install -C "debuginfo(build-id)=d3354ad4c6df1696ae951fb9ba2d5266d6131d64" (no debugging symbols found)...done. (gdb) quit peder:/usr/src/packages/BUILD/lilypond-2.12.3> zypper install -C "debuginfo(build-id)=d3354ad4c6df1696ae951fb9ba2d5266d6131d64" Loading repository data... Reading installed packages... 'debuginfo(build-id)=d3354ad4c6df1696ae951fb9ba2d5266d6131d64' not found. Resolving package dependencies... Nothing to do. peder:/usr/src/packages/BUILD/lilypond-2.12.3> rpm -qa ghostscript-library ghostscript-library-debuginfo ghostscript-library-8.64-9.3.x86_64 ghostscript-library-debuginfo-8.64-9.2.x86_64 peder:/usr/src/packages/BUILD/lilypond-2.12.3> rpm -qa ghostscript-library-debuginfo ghostscript-library-debuginfo-8.64-9.2.x86_64 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c3 Dave Plater changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|werner@novell.com |jsmeix@novell.com --- Comment #3 from Dave Plater 2010-01-07 10:16:50 UTC --- I'm the new maintainer of lilypond and can maybe help with the resolution of this bug as I have also hit an almost brick wall with this problem. The difference is, I can successfully build lilypond with documentation using rpmbuild and the gs command in question succeeds. I've tried (my patience as well) build service build, os build locally and are now using the build command to try and narrow down why gs fails on a chrooted build system. My last attempt with build used # needsrootforbuild in the spec file in attempt to duplicate my successful rpmbuild build but I'm not really sure if it works yet and that build failed in exactly the same place as well. I've added a gs -h before make in the spec file and am now performing yet another rpmbuild build in the hope that I can pick something up there. A successful build takes one and a half hours on my box so any help with the failed gs command is very much appreciated and it will also help to get to the bottom of this bug. My hardware :- uname -a Linux Arbuthnot 2.6.31.8-0.1-desktop #1 SMP PREEMPT 2009-12-15 23:55:40 +0100 x86_64 x86_64 x86_64 GNU/Linux Up to date openSUSE_11.2 which I use for all my local builds but home:plater:branches:openSUSE:Factory:Contrib lilypond builds fail on 11.1 through to factory standard. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c4 --- Comment #4 from Dave Plater 2010-01-10 10:19:30 UTC --- I found the difference between plain local rpmbuild and chrooted build, I added the line "export GS_LIB="/home/$USER/.fonts"" to the beginning of the spec file and 98% of the time I don't get the segfault. I emphasize 98% of the time because sometimes the failure still appears and a rebuild is necessary to achieve a success. This bug can be fixed by updating ghostscript-library to 8.70 which is what upstream would reply if contacted. Meanwhile I'm pushing lilypond-2.12.3 to contrib. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c6 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |janneke@gnu.org --- Comment #6 from Dr. Werner Fink 2010-01-14 09:58:43 UTC --- As I'm not able to reproduce; see here: /suse/werner> gs -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="lily-65a7b1b1-1.pdf" -c setpdfwrite -f lily-65a7b1b1-1.eps GPL Ghostscript 8.64 (2009-02-03) Copyright (C) 2009 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. /suse/werner> ll lily-65a7b1b1-1.pdf -rw-r--r-- 1 werner suse 24330 Jan 14 10:54 lily-65a7b1b1-1.pdf I'd like to ask if this crash happens also with the latest build from http://download.opensuse.org/repositories/Printing/ -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c8 --- Comment #8 from Dave Plater 2010-01-14 13:57:31 UTC --- (In reply to comment #5)

Do you know that 8.70 is under GPL3 which will cause troubles e.g. with TeXLive sub packages Does this mean that there is a legal problem with gs and if so how can it be overcome. I'm busy with building gs 8.70, I've already built a converted fc10 8.70 in my home project for lilypond to build against and haven't experienced any failures due to this bug. The best way to test is for me to have a lilypond to build against the above mentioned gs but it's not in Printing, you must mean Printing:ghostscript. I've setup home:plater:branches:openSUSE:Factory:Contrib lilypond to build against the Printing:ghostscript gs without the workaround that 90% solves the segfault problem.

-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c10 --- Comment #10 from Dave Plater 2010-01-15 09:37:22 UTC --- So a package that has the license statement "GPL2 or later" cannot be dependent on a package licensed under GPL3. This is their statement : The licensing of the Free version of the core Ghostscript code has been changed to GPLv3 or later. Previously, the core code was GPLv2 only. Ghostscript can now be used with GPLv3 applications, and can no longer be used with applications that are GPLv2-only. This means that lilypond cannot depend on gs-8.70? I wonder how Fedora solved this problem? Getting back to fixing this bug, I removed the workaround from lilypond.spec and the build now fails, even with ghostscript-library-8.64-27.1 linked from Printing:ghostscript ghostscript. This traces back to a gs "failed (11)" which Jan states is the segfault. Factory standard builds of lilypond are blocked ATM but both x86_64 and i586 fails on 11.2. The gs segfault sometimes doesn't happen, you will see that home:plater:branches:openSUSE:Factory:Contrib lilypond 11.1 i586 succeeded. If I insert the line "export GS_LIB="/home/$USER/.fonts" at the beginning of the %build section, lilypond will succeed 90% of the time. Jan has investigated this problem more than I have and I don't have the knowledge nor the time to debug this problem. The clue to reproducing this problem locally is the GS_LIB= variable. Lilypond builds without problem on my own system but fails both with local chrooted build and local osc build. Chrooted builds don't insert the GS_LIB variable by themselves. This is the worst problem to reproduce because it doesn't happen all the time but it does exist. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c12 --- Comment #12 from Dave Plater 2010-01-16 14:50:09 UTC --- I have three lilypond packages :- 1) openSUSE:Factory:Contrib which builds against factory etc. ghostscript-library 2) home:plater:branches:openSUSE:Factory:Contrib which I've setup to build against Printing:ghostscript ghostscript-library 3) home:plater which builds against home:plater ghostscript-library-8.70 and without the variable "GS_LIB="/home/$USER/.fonts" they all fail. Gs-8.70 is built with the same unmodified %install section as 8.64 and I've checked and modified all the existing patches, which took quite a while. I've uncommented "export GS_LIB="/home/$USER/.fonts" in the Contrib lilypond.

From this we can conclude that whatever is causing the seg fault is present in version 8.70.

-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c14 --- Comment #14 from Dave Plater 2010-01-17 07:53:05 UTC --- With ~/.fonts same result as C#13. With gs --version 8.70 also same result as C#13. Therefore the conclusion in C#12 is correct. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c16 --- Comment #16 from Dave Plater 2010-01-17 09:52:54 UTC --- Next we downgrade back to gs-8.64 from 11.2 and unset GS_LIB then rpmbuild -bc lilypond and we reproduce the failure that cause this bug in the first place. I will attach the build log > lilylog and all the files involved in the process to ensure reproduction. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c18 --- Comment #18 from Dave Plater 2010-01-17 10:16:28 UTC --- Executing the command :- gs -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="./4e/lily-7d242e8d-1.pdf" -c .setpdfwrite -f "./4e/lily-7d242e8d-1.eps" With GS_LIB still unset gives :- GPL Ghostscript 8.64 (2009-02-03) Copyright (C) 2009 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Can't handle format 12 Segmentation fault Executing the command after "export GS_LIB=/home/davepl/.fonts" gives the same result as above, I will repeat rpmbuild with the variable set and post the log called lilylog2 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c21 --- Comment #21 from Dave Plater 2010-01-17 12:22:43 UTC --- Created an attachment (id=337014) --> (http://bugzilla.novell.com/attachment.cgi?id=337014) Logs and files from a successful build of lilypond docs This is from a successful build of lilypond docs, I've done all I can to get to the bottom of this, hope these sets of files contribute to the resolution of this bug. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c29 --- Comment #29 from Dr. Werner Fink 2010-01-19 11:53:55 UTC --- The patch for Omni was broken as it seems that quilt can not handle file names including blanks. I've restored this patch. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c31 --- Comment #31 from Dave Plater 2010-01-19 16:08:13 UTC --- Quilt makes updating patches easy but I've decided it's good to check them but not good to make or update them. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=568280 https://bugzilla.novell.com/show_bug.cgi?id=568280#c33 --- Comment #33 from Swamp Workflow Management 2014-01-16 10:04:58 UTC --- openSUSE-RU-2014:0079-1: An update that has 5 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 466437,568280,646093,733730,851999 CVE References: Sources used: openSUSE 13.1 (src): lilypond-2.18.0-2.4.1, lilypond-doc-2.18.0-2.4.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.