Bug 179274

Summary: guile causes gnucash to crash on start
Product: [Fedora] Fedora Reporter: John Courie II <jcourie>
Component: guileAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: bojan, drepper, dwalsh, gajownik
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-06 14:53:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Courie II 2006-01-29 16:21:06 UTC
Description of problem: gnucash fails on startup with an error message that: 


[john@rallypointgamma ~]$ gnucash
/usr/bin/guile: error while loading shared libraries: libqthreads.so.12: cannot
enable executable stack as shared object requires: Permission denied

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

guile-1.6.7-4.1
kernel-2.6.15-1.1872_FC5
kernel-2.6.15-1.1878_FC5
gnucash-1.8.12-2



How reproducible: always 


Steps to Reproduce:
1.  run gnucash from the terminal.
2.  read the error message regarding /usr/bin/guile
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Miroslav Lichvar 2006-02-03 15:00:29 UTC
Unfortunately it is impossible for guile to link against the qthreads library
due to a selinux policy issue. The library is marked correctly as requiring
executable stack.

Comment 2 Daniel Walsh 2006-02-03 15:11:48 UTC
The library needs executable stack or is built with executable stack?

Does execstack -c LIBRARY fix the problem?

Comment 3 Miroslav Lichvar 2006-02-06 14:53:19 UTC
Yes, execstack -c fixes it, thanks for the hint. There is an assembly source
without the GNU-stack section, so I passed --noexecstack option to the assembler.

Comment 4 Miroslav Lichvar 2006-02-07 16:41:52 UTC
*** Bug 180313 has been marked as a duplicate of this bug. ***