SEGFAULT in Xephyr

Bug #423188 reported by Alistair Buxton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
X.Org X server
Fix Released
Medium
xorg-server (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xephyr

Xephyr version: 2:1.6.0-0ubuntu14
Ubuntu version: 9.04

Steps to reproduce:
1. Install the Maemo 4.1.2 SDK from maemo.org
2. Launch the Maemo device emulator as instructed, including starting Xephyr:
         Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite
3. Click on the Maemo main menu icon in the emulated device.

Xephyr output:

al@al-desktop:~$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.2872" is not allowed to own the service "org.x.config.display2" due to security policies in the configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)

Backtrace (10 deep):
0: Xephyr(KdBacktrace+0x35) [0x80c1595]
1: /lib/tls/i686/cmov/libc.so.6 [0xb7ad6778]
2: Xephyr(DeliverDeviceEvents+0x20f) [0x808fabf]
3: Xephyr(ProcessOtherEvent+0x36c) [0x81910cc]
4: Xephyr(mieqProcessInputEvents+0x372) [0x80f0da2]
5: Xephyr(ProcessInputEvents+0xd) [0x80c620d]
6: Xephyr(Dispatch+0x6e) [0x80b329e]
7: Xephyr(main+0x3bd) [0x809869d]
8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ac1775]
9: Xephyr [0x8070741]

Fatal server error:
Segmentation fault caught

Aborted

Tags: jaunty
Revision history for this message
In , Peter Hutterer (peter-hutterer) wrote :

Created an attachment (id=25712)
0001-kdrive-set-Activate-Deactivate-grab-for-input-device.patch

Please give this patch a try (compile-tested only).

Revision history for this message
In , Ext-istvan-visegradi (ext-istvan-visegradi) wrote :

(In reply to comment #1)
> Created an attachment (id=25712) [details]
> 0001-kdrive-set-Activate-Deactivate-grab-for-input-device.patch
>
> Please give this patch a try (compile-tested only).
>

I have tested the patch in my environment (xorg-server-1.6.0) and it is fixing my problem. No crashes anymore and the variables, that was zero earlier, now are filled with something.

Do you know how can it be "pushed" to be in between the Ubuntu Jaunty normal fixes? They have the older 1.6.0 server still in use...

Thanks for the quick fix.

Revision history for this message
In , Peter Hutterer (peter-hutterer) wrote :

pushed as 6f9e22049862ee9ac7f604411d005d8bb1b2dd1c and b1b5ec45c1cb650ccb8c659218f9481379c777d9

Revision history for this message
In , Peter Hutterer (peter-hutterer) wrote :

*** Bug 22024 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Hubert Figuiere (hub) wrote :

the patch isn't in the 1.6 branch. Can we get it there too?

(origin/server-1.6-branch)

Revision history for this message
In , Peter Hutterer (peter-hutterer) wrote :

Nominated for 1.6.3. See http://www.x.org/wiki/Server16Branch

Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

Binary package hint: xserver-xephyr

Xephyr version: 2:1.6.0-0ubuntu14
Ubuntu version: 9.04

Steps to reproduce:
1. Install the Maemo 4.1.2 SDK from maemo.org
2. Launch the Maemo device emulator as instructed, including starting Xephyr:
         Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite
3. Click on the Maemo main menu icon in the emulated device.

Xephyr output:

al@al-desktop:~$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.2872" is not allowed to own the service "org.x.config.display2" due to security policies in the configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)

Backtrace (10 deep):
0: Xephyr(KdBacktrace+0x35) [0x80c1595]
1: /lib/tls/i686/cmov/libc.so.6 [0xb7ad6778]
2: Xephyr(DeliverDeviceEvents+0x20f) [0x808fabf]
3: Xephyr(ProcessOtherEvent+0x36c) [0x81910cc]
4: Xephyr(mieqProcessInputEvents+0x372) [0x80f0da2]
5: Xephyr(ProcessInputEvents+0xd) [0x80c620d]
6: Xephyr(Dispatch+0x6e) [0x80b329e]
7: Xephyr(main+0x3bd) [0x809869d]
8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ac1775]
9: Xephyr [0x8070741]

Fatal server error:
Segmentation fault caught

Aborted

Bryce Harrington (bryce)
tags: added: jaunty
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi a-j-buxton,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-xorglog
tags: added: needs-lspci-vvnn
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

Are you sure? Xephyr is a nested X server. It does not touch any hardware, does not write to dmesg and does not create a log file. Attaching requested files anyway, even though they do not show anything useful.

Changed in xorg-server (Ubuntu):
status: Incomplete → New
Revision history for this message
Alistair Buxton (a-j-buxton) wrote :
Revision history for this message
Alistair Buxton (a-j-buxton) wrote :
Changed in xorg-server:
status: Unknown → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Alistair,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 423188

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 423188 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/423188

Changed in xorg-server (Ubuntu):
status: New → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

This bug was fixed upstream in xserver 1.6.1.902 and the fix is in Karmi and later.

Changed in xorg-server (Ubuntu):
status: Incomplete → Fix Released
tags: removed: needs-lspci-vvnn needs-retested-on-lucid-by-june needs-xorglog
Changed in xorg-server:
importance: Unknown → Medium
Changed in xorg-server:
importance: Medium → Unknown
Changed in xorg-server:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.