Bug 552417 - NULL pointer dereference in "IA__gdk_cairo_set_source_pixbuf" running /usr/bin/gnochm
Summary: NULL pointer dereference in "IA__gdk_cairo_set_source_pixbuf" running /usr/bi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e26906fe1c0ac2b66d83380907b...
: 551982 555210 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-04 23:12 UTC by Jens Maucher
Modified: 2010-12-04 00:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 00:51:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (35.02 KB, text/plain)
2010-01-04 23:13 UTC, Jens Maucher
no flags Details

Description Jens Maucher 2010-01-04 23:12:58 UTC
abrt 1.0.2 detected a crash.

Comment: Open a *.chm file with gnochm. In the index clicking on a link from a chapter and gnochm exit with segfault 11
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gnochm /home/jensm/Desktop/rhce5.RHCE.Red.Hat.Certified.Engineer.Linux.Study.Guide.(Exam.RH302),.Fifth.Edition.chm
component: python
executable: /usr/bin/python
kernel: 2.6.31.9-174.fc12.x86_64
package: python-2.6.2-2.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Jens Maucher 2010-01-04 23:13:01 UTC
Created attachment 381674 [details]
File: backtrace

Comment 2 Jens Maucher 2010-01-04 23:40:59 UTC
*** Bug 551982 has been marked as a duplicate of this bug. ***

Comment 3 Dave Malcolm 2010-01-05 18:00:37 UTC
Thanks for the updated backtrace.

Looks like a NULL-pointer deference: p is NULL, but it is dereferenced at gdkcairo.c:242
242		      MULT(q[0], p[2], p[3], t1);

This is happening when rendering a 16x16 image within a GtkTreeView.  Could be an issue in gnochm, in gtk2, or in cairo; reassigning component from "python" to "gtk2"; hopefully the gtk2 maintainer will be able to better assess what's going on.

Comment 4 Dave Malcolm 2010-01-14 22:39:35 UTC
*** Bug 555210 has been marked as a duplicate of this bug. ***

Comment 5 Bug Zapper 2010-11-04 01:50:45 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2010-12-04 00:51:21 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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