Bug 15794 - Broken libX11 with xtrans-1.1
Summary: Broken libX11 with xtrans-1.1
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/xtrans (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: xorg-7.4
  Show dependency treegraph
 
Reported: 2008-05-01 19:50 UTC by ugenn
Modified: 2008-05-03 11:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description ugenn 2008-05-01 19:50:54 UTC
Apps that link to libX11 built with xtrans-1.1
are unable to make a local X server connection
when the server is started with -nolisten tcp.
Everything works fine when I downgraded to
xtrans-1.0.4 and rebuilt libX11.

Packages built and running on:
linux-2.6.24.4
glibc-2.7
xorg-server-1.4.0.90
libX11-1.1.4
libXau-1.0.3
libXdmcp-1.0.2
xproto-7.0.12
xextproto-7.0.2
xf86bigfontproto-1.1.2
kbproto-1.0.3
inputproto-1.4.3
Comment 1 Alan Coopersmith 2008-05-02 07:23:56 UTC
Does it work if you build xtrans from git master which has the fix for 
https://bugs.freedesktop.org/show_bug.cgi?id=15677  ?
Comment 2 ugenn 2008-05-03 00:49:53 UTC
Same problem.
Comment 3 ugenn 2008-05-03 01:21:21 UTC
Did straces on both the working and broken versions and noticed the following:

On the working libX11, i got
connect(3, {sa_family=AF_FILE, path="/tmp/.X11-unix/X0"}, 19) = 0

On the broken,
connect(3, {sa_family=AF_FILE, path=@/tmp/.X11-unix/X0}, 20) = -1 ECONNREFUSED (Connection refused)
Comment 4 Alan Coopersmith 2008-05-03 08:14:15 UTC
Did you rebuild both Xorg & libX11 with the new xtrans or just libX11?
Comment 5 ugenn 2008-05-03 10:09:31 UTC
Both xlib and server were built against the
broken xtrans (1.1). I've only tried rebuilding
xlib with git-head, not the xserver. I'll try the
server and post an update later.
Comment 6 ugenn 2008-05-03 11:30:02 UTC
Works after rebuilding the server.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.