Bug 454409 - Xephyr ends with Segmentation fault
Xephyr ends with Segmentation fault
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xorg-x11-server (Show other bugs)
x86_64 Linux
medium Severity urgent
: rc
: ---
Assigned To: Adam Jackson
Desktop QE
: Patch, Triaged
Depends On:
Blocks: 726826
  Show dependency treegraph
Reported: 2008-07-08 07:27 EDT by Laurent Desnogues
Modified: 2012-02-20 22:12 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-02-20 22:12:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
strace -ff -o Xephyr.strace Xephyr :2 (36.83 KB, text/plain)
2008-07-10 05:40 EDT, Ralph Angenendt
no flags Details
strace -ff -o Xephyr.strace Xephyr :2 (second file) (28.91 KB, text/plain)
2008-07-10 05:41 EDT, Ralph Angenendt
no flags Details
Xorg.conf file (566 bytes, text/plain)
2008-07-10 06:29 EDT, Laurent Desnogues
no flags Details
X server log file (64.57 KB, text/plain)
2008-07-10 06:29 EDT, Laurent Desnogues
no flags Details
Proposed fix (2.46 KB, patch)
2011-07-05 10:05 EDT, Olivier Fourdan
ofourdan: review?
Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
FreeDesktop.org 8417 None None None Never

  None (edit)
Description Laurent Desnogues 2008-07-08 07:27:19 EDT
Description of problem:

Running Xephyr on my CentOS 5.2 x86_64 (e6600, i965 integrated graphics) results
in a quasi-immediate Segmentation fault:

bash-3.2$ Xephyr :2 -screen 800x480x16
Extended Input Devices not yet supported. Impelement it at line 625 in kinput.c
Segmentation fault (core dumped)

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

This is with xorg-x11-server-Xephyr-1.1.1-48.41.el5_2.1.

How reproducible:

Steps to Reproduce:
1.Xephyr :2 -screen 800x480x16

Actual results:

Extended Input Devices not yet supported. Impelement it at line 625 in kinput.c
Segmentation fault (core dumped)

Expected results:

Additional info:

selinux is disabled.

strace does not give any useful information (at least not close to the end).

gdb bt is as follows:

0 0x0000000000000000 in ?? ()
0000001 0x00000000006acdec in PictureDestroyWindow ()
0000002 0x0000000000448a39 in FreeColormap ()
3 0x0000000000448d53 in FreeColormap ()
4 0x0000000000438c79 in NotImplemented ()
5 0x0000003b84a1d8b4 in __libc_start_main () from /lib64/libc.so.6
6 0x000000000041fb19 in ?? ()
0000007 0x00007fff42823148 in ?? ()
0000008 0x0000000000000000 in ?? ()



PS - x-ref http://bugs.centos.org/bug_view_advanced_page.php?bug_id=2948
Comment 1 Matěj Cepl 2008-07-08 20:08:59 EDT
Thanks for the bug report.  We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.
Comment 2 Ralph Angenendt 2008-07-10 05:09:22 EDT
It doesn't even get that far, so it doesn't write any logs:

[angenenr@shutdown ~]$strace -ff -eopen Xephyr :2 2>&1 | grep log
[angenenr@shutdown ~]$

This is without xorg.conf in place.
Comment 3 Ralph Angenendt 2008-07-10 05:14:44 EDT
Backtrace (I seem to be missing some debug symbols, but do not really know which):

(gdb) run :2
Starting program: /usr/bin/Xephyr :2
Extended Input Devices not yet supported. Impelement it at line 625 in kinput.c
[Detaching after fork from child process 20563. (Try `set detach-on-fork off'.)]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00000000006acdec in AnimCurRealizeCursor (pScreen=0x18981280, 
    pCursor=0x1899b150) at animcur.c:269
#2  0x0000000000448a39 in AllocGlyphCursor (source=<value optimized out>, 
    sourceChar=0, mask=<value optimized out>, maskChar=1, 
    foreRed=<value optimized out>, foreGreen=<value optimized out>, foreBlue=0, 
    backRed=4294967295, backGreen=4294967295, backBlue=4294967295, 
    ppCurs=0x7fff6b3f48e0, client=0x1897ed80) at cursor.c:409
#3  0x0000000000448d53 in CreateRootCursor (pfilename=0x70901e "cursor", glyph=0)
    at cursor.c:451
#4  0x0000000000438c79 in main (argc=2, argv=0x7fff6b3f4a48, 
    envp=<value optimized out>) at main.c:413
#5  0x00000035d3e1d8b4 in __libc_start_main () from /lib64/libc.so.6
#6  0x000000000041fb19 in _start ()
Comment 4 Ralph Angenendt 2008-07-10 05:39:44 EDT
Attaching complete strace files:

strace -ff -o Xephyr.strace Xephyr :2

Still without xorg.conf in place.
Comment 5 Ralph Angenendt 2008-07-10 05:40:59 EDT
Created attachment 311461 [details]
strace -ff -o Xephyr.strace Xephyr :2
Comment 6 Ralph Angenendt 2008-07-10 05:41:40 EDT
Created attachment 311462 [details]
strace -ff -o Xephyr.strace Xephyr :2 (second file)
Comment 7 Laurent Desnogues 2008-07-10 06:28:00 EDT
Attaching my xorg.conf and Xorg.0.log (there's no Xorg.[12].log which confirms
what Ralph wrote).

I can't restart my Xserver now (it's my work machine), so I can't post what
happens with an empty xorg.conf file.
Comment 8 Laurent Desnogues 2008-07-10 06:29:00 EDT
Created attachment 311464 [details]
Xorg.conf file
Comment 9 Laurent Desnogues 2008-07-10 06:29:46 EDT
Created attachment 311465 [details]
X server log file
Comment 16 Adam Jackson 2011-08-17 15:37:00 EDT
3564263 build (dist-5E-qu-candidate, /cvs/dist:rpms/xorg-x11-server/RHEL-5:xorg-x11-server-1_1_1-48_83_el5) completed successfully

Comment 20 errata-xmlrpc 2012-02-20 22:12:43 EST
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.


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