Bug 211812 - Rpmbuild miscompiles libX11 - deadlocks with XInitThreads
Rpmbuild miscompiles libX11 - deadlocks with XInitThreads
Product: Fedora
Classification: Fedora
Component: libX11 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
Depends On:
  Show dependency treegraph
Reported: 2006-10-23 04:23 EDT by Ivan Gyurdiev
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-09-12 21:45:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ivan Gyurdiev 2006-10-23 04:23:53 EDT
Wine recently enabled XInitThreads, and now all my wine applications deadlock,
including notepad (the wine version). Tracking down the problem brings me to a
call to XFilterEvent, which does not complete. The previous X call is always

Interestingly enough, compiling the same version of libX11 on my computer does
not deadlock. Compiling with the extra patches and configure flags from the spec
file still does not deadlock. Compiling with rpmbuild will deadlock every single
time - I guess CFLAGS are breaking it.. FORTIFY_SOURCE, GNU_HASH and such..?

This is the 32-bit version of libX11 on amd x86_64, in case that makes any
difference... libX11-1.0.3-4.fc6, Fedora Rawhide.
Comment 1 Matěj Cepl 2007-09-11 20:34:29 EDT
Since this bugzilla report was filed, there have been several major updates,
which may have resolved this issue. Users who have experienced this problem are
encouraged to upgrade their system to the latest version of their distribution

Please, if you experience this problem on the up-to-date system, let us now in
the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as
Comment 2 Ivan Gyurdiev 2007-09-12 21:45:53 EDT
I think this is now resolved... closing.

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