Bug 169311 - unresolved Symbol problems
unresolved Symbol problems
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-09-26 17:15 EDT by Andreas Bierfert
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-27 03:31:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
stderr output of startx (15.07 KB, text/plain)
2005-09-26 17:15 EDT, Andreas Bierfert
no flags Details

  None (edit)
Description Andreas Bierfert 2005-09-26 17:15:21 EDT
Description of problem:
Symbol __stack_chk_fail from module ...(see attached file) is unresolved!

Version-Release number of selected component (if applicable):
[11:19 PM][awjb@arcturus ~]$ rpm -q xorg-x11

How reproducible:

Steps to Reproduce:
1. startx
Comment 1 Andreas Bierfert 2005-09-26 17:15:22 EDT
Created attachment 119278 [details]
stderr output of startx
Comment 2 Mike A. Harris 2005-09-26 19:30:15 EDT
This is caused by gcc's stack-protector.  It appears there is no "simple"
solution to work around this problem and keep stack-protector support
in the monolithic builds without more effort than it's worth to spend.

As such, I'm disabling stack-protector for monolithic builds.  Once modular
X hits the tree, everything should build ok with stack protector presumeably
except the X server, unless the problem has been resolved upstream by then.

We'll keep it disabled in the X server at least until we have a proper
solution that is also acceptable to upstream X.Org, as we definitely want
to avoid a Red Hat specific solution that causes inter-distribution binary
incompatibility of X server modules, as that would cause hardware vendors
to build modules for each distribution individually, which would be 'bad'
Comment 3 Mike A. Harris 2005-09-26 20:30:19 EDT
Are you using FC4 with random bits and pieces of Fedora devel?  Curious
because another person using devel says they don't see this error.

I'm thinking the problem might only occur on mixed systems, although
it is a bigger problem than just the failure to solve.  Ultimately we
do want stack-protector to be used.  ;)
Comment 4 Andreas Bierfert 2005-09-27 03:21:53 EDT
Actually its a devel with devel and fc4 repos enabled so if an fc4 version is >
fc5 there probably is some fc4 stuff in there... actually I probably should
track these packages down sometime ^^

Hope that helps. If you want an rpm -qa let me know...
Comment 5 Mike A. Harris 2005-09-27 03:31:03 EDT
Should be fixed in 6.8.2-54, by disabling stack-protector completely.

When we put Xorg modular in rawhide, stack-protector will be automatically
re-enabled for everything except the Xorg X server, unless we come up with
a safe/sane way of doing so by then, as it'd be nice to have the additional
protection.  It'd cut down the seriousness of X server buffer overflows for

Thanks again for the report.

Note You need to log in before you can comment on or make changes to this bug.