Bug 509703 - Using GIMP to pixel-edit causes X server to abnormally exit
Summary: Using GIMP to pixel-edit causes X server to abnormally exit
Keywords:
Status: CLOSED DUPLICATE of bug 504300
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 11
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-05 10:02 UTC by Alex Butcher
Modified: 2009-07-05 21:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-05 21:40:54 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Alex Butcher 2009-07-05 10:02:05 UTC 
Description of problem:

Using GIMP to pixel-edit an image causes the X server to catch a signal 11 and exit back to gdm.

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

xorg-x11-server-Xorg-1.fc11
gimp-2.6.6-3.fc11

How reproducible:


Steps to Reproduce:
1. Open an image in GIMP
2. Magnify to 1600%, select the 1x1 pixel brush
3. Click somewhere in the image to set that pixel
  
Actual results:

Get kicked out of X session back to gdm login prompt

Expected results:

Able to use any X application without it crashing the X server.

Additional info:

Using xorg-x11-drv-nvidia-185.18.14-2.fc11 driver with a Geforce 7600GT card.
Comment 1 Alex Butcher 2009-07-05 10:31:59 UTC 
Actually, just using GIMP to edit an image at all causes the X server to crash; no magnification nor 1x1 pixel brush necessary; e.g. using the 'Fill' tool has the same effect.
Comment 2 Alex Butcher 2009-07-05 10:36:25 UTC 
Regression of Bug 489776 ?
Comment 3 Alex Butcher 2009-07-05 10:37:46 UTC 
Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6]
1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f]
2: /lib64/libc.so.6 [0x3f5bc33370]

Fatal server error:
Caught signal 11.  Server aborting
Comment 4 Alex Butcher 2009-07-05 21:37:14 UTC 
Disabling the vnc Module in xorg.conf appears to have fixed it, as per bug 504300
Comment 5 Alex Butcher 2009-07-05 21:40:54 UTC 

*** This bug has been marked as a duplicate of bug 504300 ***
Note You need to log in before you can comment on or make changes to this bug.