Bug 795858
| Summary: | X server crashes with segfault at startup when using X font server | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Michael <mikeus> | ||||
| Component: | xorg-x11-server | Assignee: | Adam Jackson <ajax> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.2 | CC: | mikeus, tpelka | ||||
| Target Milestone: | rc | Keywords: | OtherQA | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | xorg-x11-server-1.13.0-17.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-11-21 11:28:26 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 842499, 960058 | ||||||
| Attachments: |
|
||||||
|
Description
Michael
2012-02-21 16:41:03 UTC
Created attachment 564747 [details]
Xorg.0.log
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. I'm quite confused here. How do we can reproduce without xfs in rhel6. Michael are you using some kind of third-party rpm on your systems? Or Adam any other thoughts regarding xfs in rhel6 and reproducer for this. I would be open to push this fix as OtherQA if we can get commitment from Michael to test the fix when available. Thanks Tom Hello. For the sake of integrity I've used an RHEL5 box on the LAN. But the xfs rpm from RHEL5 (plus one dependency package) installed on RHEL6 and worked good at least as of the time of release 6.2. (In reply to Michael from comment #5) > Hello. > For the sake of integrity I've used an RHEL5 box on the LAN. > But the xfs rpm from RHEL5 (plus one dependency package) installed on RHEL6 > and worked good at least as of the time of release 6.2. I'm sorry Michael I'm not able to reproduce. It is just working fine with external XFS server from rhel5.x. Would you be able to check the fix once packages are ready? Thanks Tom Hello, Tomas. Now I've installed a test VM and release 6.4 X server starts OK with external XFS server. But it crashes when I'm trying to run xfontsel utility: [ 2831.501] (EE) [ 2831.501] (EE) Backtrace: [ 2831.502] (EE) 0: /usr/bin/X (xorg_backtrace+0x50) [0x80b19b0] [ 2831.502] (EE) 1: /usr/bin/X (0x8047000+0x70406) [0x80b7406] [ 2831.502] (EE) 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xcc940c] [ 2831.502] (EE) 3: /usr/bin/X (doListFontsWithInfo+0x14b) [0x807a11b] [ 2831.503] (EE) 4: /usr/bin/X (ProcessWorkQueue+0x31) [0x807d171] [ 2831.503] (EE) 5: /usr/bin/X (WaitForSomething+0x6f) [0x80aecff] [ 2831.503] (EE) 6: /usr/bin/X (0x8047000+0x3192e) [0x807892e] [ 2831.503] (EE) 7: /usr/bin/X (0x8047000+0x7b9fc) [0x80c29fc] [ 2831.503] (EE) 8: /lib/libc.so.6 (__libc_start_main+0xe6) [0x6ddce6] [ 2831.503] (EE) 9: /usr/bin/X (0x8047000+0x1f0e1) [0x80660e1] [ 2831.504] (EE) [ 2831.504] (EE) Segmentation fault at address 0x0 [ 2831.504] Fatal server error: [ 2831.504] Caught signal 11 (Segmentation fault). Server aborting [ 2831.504] [ 2831.504] (EE) Can you reproduce the issue with this additional step? Before then, it is essential to make sure (with xfsinfo or fslsfonts utility) that the tested box with X server actually sees the external XFS server, since otherwise X server and xfontsel utility silently works well. Anyway I'm ready to test the fix you are about of. Hi Michael,
still no crash.
I have
[ 47.307] (**) FontPath set to:
tcp/192.168.122.40:7100,
catalogue:/etc/X11/fontpath.d,
built-ins
in my Xorg.0.log on rhel6, checked with tcpdum that there is some communication on port 7100 and I can get fonts listed via 'fslsfonts -server 192.168.122.40:7100' (also compared with the list on rhel5 which is serving fonts)
xfsinfo -server 192.168.122.40:7100
name of server: 192.168.122.40:7100
version number: 2
vendor string: X.Org Foundation
vendor release number: 6700
maximum request size: 8192 longwords (65536 bytes)
number of catalogues: 1
all
Number of alternate servers: 0
number of extensions: 0
My setup:
1) rhel5 (192.168.122.40) which serves fonts, so have no-listen commented
2) rhel6 (ip is not important here) with configuration in /etc/X11/xorg.conf.d
$ cat /etc/X11/xorg.conf.d/test.conf
Section "Files"
FontPath "tcp/192.168.122.40:7100"
EndSection
xfs version:
xorg-x11-xfs-utils-1.0.2-5.el5_6.1
xorg-x11-xfs-1.0.2-5.el5_6.1
libFS-1.0.0-3.1
OK I can do the same using rhel6 only (with rhel5 packages) on both sites. Michael, since I'm still not able to reproduce proposing again the possibility to pushing this through OtherQA which means that you can test fixed packages once is ready. Unfortunately the time is limited, if you can commit that I can ack and move forward. Thanks Tom Tomas, I cat do a test of the fixed packages. (In reply to Michael from comment #11) > Tomas, I cat do a test of the fixed packages. Thank you, will let you know on time. Tom Please try the following test packages, which should be compatible with RHEL 6.4: http://people.redhat.com/~ajackson/795858/ I've updated to xorg-x11-server-Xorg-1.13.0-14.el6.font1.i686.rpm / xorg-x11-server-common-1.13.0-14.el6.font1.i686.rpm packages. It seems to work well: X server when configured to use xfs doesn't crash on xfontsel launching. xfontsel shows 4314 font names matched with connection to xfs and 1579 without it, and characters in a font from the remote font server can be displayed with xfd utility on the client. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1620.html |