gimp won't start, crash in fbFetch_x8r8g8b8()

Bug #123281 reported by Shawn vega
8
Affects Status Importance Assigned to Milestone
libcairo
Fix Released
Medium
libcairo (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gimp

gimp won't start in gusty tribe 2 amd64 here is the output

shawn@gusty64:~$ gimp
This is a development version of GIMP. Debug messages may appear here.

gimp: fatal error: Segmentation fault
gimp (pid:28318): [E]xit, [H]alt, show [S]tack trace or [P]roceed: P
shawn@gusty64:~$

Revision history for this message
polopolo (linux-debaat) wrote :

Does it also happens when you start from the ubuntu application menu?

Changed in gimp:
assignee: nobody → linux-debaat
status: New → Incomplete
Revision history for this message
Shawn vega (svega85-gmail) wrote :

it doesn't start from the terminal or the application menu. i can't get it to start at all

Revision history for this message
polopolo (linux-debaat) wrote :

Open Synaptic from the applications list, and enter you're password.
Then, press settings > Repositories, click new.
Type in the first line this: http://people.ubuntu.com/~pitti/ddebs
In the second line, type: gutsy
In the third line, type: main universe

Then click again new.
Type in the first line this: http://people.ubuntu.com/~pitti/ddebs
In the second line, type: gutsy-updates
In the third line, type: main universe

Then click again new.
Type in the first line this: http://people.ubuntu.com/~pitti/ddebs
In the second line, type: gutsy-proposed
In the third line, type: main universe

Then click again new.
Type in the first line this: http://people.ubuntu.com/~pitti/ddebs
In the second line, type: gutsy-security
In the third line, type: main universe

Then, click ok.
Open a terminal, and type: sudo apt-get update
Press enter Then type: sudo apt-get install yelp-dbgsym gdb
And press enter.
When the install is finished, type: gdb gimp 2>&1 | tee gdb-gimp.txt
and press enter, then type: handle SIG33 pass nostop noprint
and press enter, then type: set pagination 0
and press enter, then type: run gimp
and press enter.

When it goes good, it must crash, when it crashed, do this:
Type: backtrace full
and press enter, type: info registers
and press enter, type: thread apply all backtrace
and press enter, type: quit

Attach the complete output from GDB, contained in gdb-gimp.txt, in your bug report.

Revision history for this message
Shawn vega (svega85-gmail) wrote :

ok i did everything you said and here is the output

Revision history for this message
polopolo (linux-debaat) wrote :

Do you installed the package 'sane' in you're ubuntu system?

Revision history for this message
polopolo (linux-debaat) wrote :

And open Synaptic under applications, and enter you're password.
Click on reload, then click on search and gimp
And press Search.
When you found the package gimp, can you tell what you're current installed version of gimp you installed?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you install libcairo2-dbgsym and get a new backtrace?

Revision history for this message
Shawn vega (svega85-gmail) wrote :

sane is not installed should i install it?

Revision history for this message
Shawn vega (svega85-gmail) wrote :

the installed version of gimp is 2.3.18-1ubuntu1

Revision history for this message
Shawn vega (svega85-gmail) wrote :

ok i installed libcairo2-dbgsym, but i didn't install sane and i did the new backtrace and it's attached

Revision history for this message
In , Sebastien Bacher (seb128) wrote :
Download full text (21.8 KiB)

The bug has been opened on https://bugs.launchpad.net/bugs/123281

"Binary package hint: gimp

gimp won't start in gusty tribe 2 amd64 here is the output

shawn@gusty64:~$ gimp
This is a development version of GIMP. Debug messages may appear here.

gimp: fatal error: Segmentation fault
gimp (pid:28318): [E]xit, [H]alt, show [S]tack trace or [P]roceed: P
shawn@gusty64:~$
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47750748790736 (LWP 15881)]
fbFetch_x8r8g8b8 (bits=0x2aaa2b4dc068, x=<value optimized out>, width=<value optimized out>, buffer=0x7fffda5fd600, indexed=0x0) at /build/buildd/libcairo-1.4.10/pixman/src/fbcompose.c:159
159 /build/buildd/libcairo-1.4.10/pixman/src/fbcompose.c: No such file or directory.
 in /build/buildd/libcairo-1.4.10/pixman/src/fbcompose.c
(gdb) backtrace full
#0 fbFetch_x8r8g8b8 (bits=0x2aaa2b4dc068, x=<value optimized out>, width=<value optimized out>, buffer=0x7fffda5fd600, indexed=0x0) at /build/buildd/libcairo-1.4.10/pixman/src/fbcompose.c:159
 pixel = (const CARD32 *) 0x2aaa2b4dc058
 end = (const CARD32 *) 0x2aaa2b4dc05c
#1 0x00002b6dd4eff654 in pixman_compositeGeneral (op=<value optimized out>, pSrc=0xc0b220, pMask=0x0, pDst=0xc0b540, xSrc=-1, ySrc=-1, xMask=0, yMask=0, xDst=0, yDst=0, width=1, height=1) at /build/buildd/libcairo-1.4.10/pixman/src/fbcompose.c:4196
 region = {extents = {x1 = 0, y1 = 0, x2 = 1, y2 = 1}, data = 0x0}
 n = 1
 pbox = <value optimized out>
 srcRepeat = 1
 maskRepeat = 0
 w = <value optimized out>
 h = <value optimized out>
 _scanline_buffer = {0 <repeats 1142 times>, 3592986288, 11117, 33, 0, 44, 0, 1423468550, 0, 3494557908, 11117, 0, 0, 3663718448, 32767, 1423468550, 0, 3663718816, 32767, 3663718840, 32767, 3574783664, 11117, 0, 0, 0, 0, 3572139192, 11117, 3574827477, 11117, 3574816640, 11117, 3574812200, 11117, 0, 1, 1189, 1, 0, 0, 3572140056, 11117, 3663718896, 32767, 3663718816, 32767, 3663718840, 32767, 1423468550, 0, 0, 0, 3494558451, 11117, 49, 0, 0, 0, 1, 0, 3551770976, 11117, 3551771048, 11117, 3551771048, 11117, 0, 0, 3551771072, 11117, 0, 0, 0, 1, 3572140056, 11117, 3663718944, 32767, 3572139192, 11117, 3551770976, 11117, 8176, 0, 3551771072, 11117, 3551770976, 11117, 1784, 0, 8192, 0, 3548751426, 11117, 0, 0, 64, 0, 3663718832, 32767, 0, 0, 3663718848, 32767, 8224, 0, 21, 0, 64, 0, 3663718880, 32767, 3551770976, 11117, 16, 0, 64, 0, 0, 4, 1, 0, 64, 0, 3548764676, 11117, 48, 4, 3551770976, 11117, 8176, 0, 3551770976, 11117, 21, 0, 11251440, 0, 3663719604, 32767, 3551770976, 11117, 16, 0, 3551770976, 11117, 0, 0, 14, 0, 10, 0, 11249500, 0, 10714403, 0, 3548764044, 11117, 11262640, 0, 3575085529, 11117, 11241316, 0, 1, 0, 29, 0, 0, 0, 0, 0, 3575088189, 11117, 3663719188, 32767, 1, 0, 0, 0, 3663720044, 32767, 3663719184, 32767, 0, 0, 3663728256, 32767, 0, 1...}
 scanline_buffer = (CARD32 *) 0x0
#2 0x00002b6dd4ef1972 in _cairo_pixman_composite (op=PIXMAN_OPERATOR_OVER, pSrc=0xc0b220, pMask=0x1, pDst=0xc0b540, xSrc=-1, ySrc=-1, xMask=0, yMask=0, xDst=0, yDst=0, width=1, height=1) at /build/buildd/libcairo-1.4.10/pixman/src/fbpict.c:1928
 region = {extents = {x1 = 0, y1 = 1, x2 = 0, y2 = 0}, data = 0x0}
 n = <value optimized out>
 pbox = <va...

Revision history for this message
Sebastien Bacher (seb128) wrote :

The crash happens in libcairo, I've sent it upstream to https://bugs.freedesktop.org/show_bug.cgi?id=11449

Changed in gimp:
assignee: linux-debaat → desktop-bugs
importance: Undecided → Medium
status: Incomplete → Confirmed
Changed in libcairo:
status: Unknown → Confirmed
Revision history for this message
Shawn vega (svega85-gmail) wrote :

ok do i need to do anything else?

Revision history for this message
polopolo (linux-debaat) wrote :

No, the bug should maby in the next release of ubuntu.
Or if you have lucky, in feisty.

Revision history for this message
Shawn vega (svega85-gmail) wrote :

ok i think this is related to firefox bug #128762 because it appears that gimp will start fine with other themes just not the default human theme.

Revision history for this message
James Henstridge (jamesh) wrote :

Bug #133124 is another firefox bug that is likely to be a duplicate of this one. The investigation I did seems to match what has been found out here with a few extra details:

 1. The bug is not triggered on x86.
 2. The bug is not triggered when the X server was set to 24 bit depth, but does at 16 bits.
 3. The following patch to ubuntulooks avoids the crash (and Gimp runs with this patch):
    http://launchpadlibrarian.net/9497723/ubuntulooks_0.9.12-6-progressbar-fix.patch

I agree that this is probably a bug in Cairo, so it is probably still possible to trigger the crash with the ubuntulooks patch applied -- this just stops the theme engine from triggering it.

I guess the firefox bugs should be marked as duplicates of this one.

Revision history for this message
Shawn vega (svega85-gmail) wrote :

i think everything works now so i'm going to mark this as fixed

Changed in libcairo:
status: Confirmed → Fix Released
Revision history for this message
In , Sandmann (sandmann) wrote :

There is no reason to think this bug still exists in any recent version of cairo or pixman.

Changed in libcairo:
status: Confirmed → Fix Released
Changed in libcairo:
importance: Unknown → Medium
Changed in libcairo:
importance: Medium → Unknown
Changed in libcairo:
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.