Jaunty Gimp running inside Xephyr causes a Segmentation fault

Bug #351251 reported by Obrouni
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I am using Jaunty with Xephyr to create a multiseat configuration. If you create a new image in the Gimp, as soon as you click in the image area, Xephyr crashes.

xserver-xephyr:
  Installed: 2:1.6.0-0ubuntu6

I have attached the backtrace from Xephyr.

Revision history for this message
Obrouni (nick-fisk) wrote :
Revision history for this message
Wollschaf (wollschaf) wrote :

Exactly the same here with gimp and inkscape:

Backtrace (8 deep):
0: Xephyr(KdBacktrace+0x35) [0x80c1595]
1: [0xb8041400]
2: Xephyr(ProcXGrabDevice+0x12a) [0x8195a0a]
3: Xephyr [0x81924e3]
4: Xephyr(Dispatch+0x33f) [0x80b356f]
5: Xephyr(main+0x3bd) [0x809869d]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7a56775]
7: Xephyr [0x8070741]

Fatal server error:
Segmentation fault caught

Segmentation fault

A Xephyr launched nested in another Xephyr crashes, the parent Xephyr (multiseat) survives.

DISPLAY=:5 inkscape
inkscape: Fatal IO error 0 (Success) on X server :5.0.

DISPLAY=:5 gimp
gimp: Fatal IO error 11 (Resource temporarily unavailable) on X server :5.0.

Bryce Harrington (bryce)
tags: added: jaunty
Bryce Harrington (bryce)
tags: added: crash
Revision history for this message
Arie Skliarouk (skliarie) wrote :

Same story here, with using "Eraser Tool" of the gimp:
During the crash I see following message in the /var/log/syslog:

Sep 12 21:15:16 mainframe kernel: [ 5029.552822] Xephyr[3838]: segfault at d0 ip
 000000000044b055 sp 00007fff08427110 error 4 in Xephyr[400000+1e7000]

Revision history for this message
Arie Skliarouk (skliarie) wrote :

The bug does not happen on karmic.
For some reason the first time I run gimp, it takes about a minute to start (the logo appears and gets stuck).

Revision history for this message
Fábio Figueiredo (fabiosoaresf) wrote :

What I have tested for solving this problem in Jaunty (9.04) was temporarily include karmic entry in /etc/apt/sources.list and update just a few packages related to "xserver-xephyr" (in my case, 4 packages). For example, we updated "xserver-xephyr" from 2:1.6.0-0ubuntu14 to 2:1.6.3-1ubuntu7, along with 3 other packages. Gimp is finally working with Xephyr now. Do not forget to remove the karmic entry from sources.list to avoid mixing other packages besides Xephyr.

Revision history for this message
rinovan (rinovan) wrote :

how about xserver-xephyr in lucid, do you ever tried?

Revision history for this message
Arie Skliarouk (skliarie) wrote :

As I wrote on 2009-10-04, the bug does not happen on karmic. Gimp works perfectly, without crashes.
Consider to close the bug and reopen it should the problem reappear.

Revision history for this message
blackmatrix (blackmatrix-box) wrote :

I have the same bug with 9.10 but I'm not using xephyr.

I use X for each seat with 3D and compiz enabled.

is there a patch for xserver-xorg ?

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

[This is an automatic notification.]

Hi Obrouni,

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 351251

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 351251 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/351251

Changed in xorg-server (Ubuntu):
status: New → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Arie Skliarouk (skliarie) wrote :

The bug does not appear in lucid.

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

[Resetting to incomplete since we need a response from the original reporter on this].

Changed in xorg-server (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Obrouni (nick-fisk) wrote :

I can confirm this now works fine in Lucid

Changed in xorg-server (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
sly (liste-letuffe) wrote :

Hi,

I am using Lucid and I am still affected by that bug (or one that looks
really like the one of the original poster)

Using gimp and trying any action with my mouse on the drawing surface cause
Xorg to segfault. (The only other apps I'm aware of that do crash xorg the same way is inkscape)

I'm also using a multi-seat configuration, but it does happen in the Xephyr
session as well as in the main xorg session.

What I found is that this bug is related to gimp + the evdev input driver of
xorg

My relevent section in xorg.conf is :
Section "InputDevice"
  Identifier "Right Mouse"
  Option "CorePointer"
  Driver "evdev"
  Option "Device" "/dev/input/event4"
EndSection

The bug does not occure if I'm using the default xorg input driver

My guess would be that gimp requests something related to a graphic tablet
and that is badly supported by the evedev input driver, but that just a
guess.

I haven't upgraded yet to Maverik so I cannot confirm if that occurs on it as well

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.