Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 224311 - Xephyr segfaults on startup
Summary: Xephyr segfaults on startup
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 6
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-25 07:16 UTC by Jonathan Eskritt
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-01-29 23:02:07 UTC

Attachments (Terms of Use)

Description Jonathan Eskritt 2007-01-25 07:16:03 UTC
Description of problem:
I try to start a Xephyr window using:
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac
as described in the  maemo 3.0 tutorial

but it segfaulst with the error:
Extended Input Devices not yet supported. Impelement it at line 625 in kinput.c
Segmentation fault

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

How reproducible:

Steps to Reproduce:
1. Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac

Actual results:
A window frame beirfly appears before a segfault occurs

Expected results:
a xephyr window should appear

Additional info:

Comment 1 Adam Jackson 2007-01-29 23:02:07 UTC
This appears to be a 64-bitness bug in Xephyr.  hostx.c is being built all
wrong; KeySym is defined as XID is defined as unsigned long, which would be fine
on 32 bit but not here.  As a result, the keymap fill code walks off into other
bits of .data, and smashes the cursor private index, so the next call to
pScreen->RealizeCursor() explodes.  Pretty cool!

hostx.c is special and needs to thunk between X server and Xlib types, which are
not the same sizes even though they're the same type names.  So basically you
can't ever talk about KeySyms, you just have to know that they're unsigned
32-bit ints.  So gross.  But, fixed in 1.2.0-3 and in 1.1.1-47.5.fc6, the latter
of which will be in updates shortly.


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