xchat-gnome crashed with SIGSEGV in gdk_pixbuf_composite()

Bug #284635 reported by Uphaar Agrawalla
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
XChat-GNOME
Fix Released
Critical
gtk+2.0 (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: xchat-gnome

Steps to reproduce:
Connect to a network
Receive a file from someone
Open IRC > File Transfers window
xchat-gnome crashes!

It is always reproducible. Would really be great if someone could take a look at it before release, Hardy did not have this crasher.
Running an up-to-date Intrepid (upgraded from Hardy).

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/xchat-gnome
NonfreeKernelModules: nvidia
Package: xchat-gnome 1:0.24.0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: xchat-gnome
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
 SHELL=/bin/bash
Signal: 11
SourcePackage: xchat-gnome
StacktraceTop:
 ?? () from /usr/lib/libgdk_pixbuf-2.0.so.0
 ?? () from /usr/lib/libgdk_pixbuf-2.0.so.0
 ?? () from /usr/lib/libgdk_pixbuf-2.0.so.0
 gdk_pixbuf_composite ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: xchat-gnome crashed with SIGSEGV in gdk_pixbuf_composite()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mldonkey netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Uphaar Agrawalla (uphaar) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:pixops_process (dest_buf=0x7fff7dcab1d8 <Address 0x7fff7dcab1d8 out of bounds>, render_x0=0,
_pixops_composite (dest_buf=<value optimized out>, dest_width=<value optimized out>,
IA__gdk_pixbuf_composite (src=0x7fff740115e0, dest=0x7b3e80, dest_x=4, dest_y=4, dest_width=12,
apply_emblems (info=<value optimized out>) at /build/buildd/gtk+2.0-2.14.3/gtk/gtkicontheme.c:2829
icon_info_ensure_scale_and_pixbuf (icon_info=0x17e6d80, scale_only=<value optimized out>)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in xchat-gnome:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

is this still reproducible with xchat-gnome 0.24.1? i cannot reproduce it

Changed in xchat-gnome:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Uphaar Agrawalla (uphaar) wrote :

Yes.

Changed in xchat-gnome:
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: https://bugs.edge.launchpad.net/ubuntu/+source/xchat-gnome/+bug/284635

Changed in xchat-gnome:
status: New → Triaged
importance: Undecided → Unknown
status: New → Unknown
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue was a gtk one and is fixed in jaunty

Changed in xchat-gnome:
status: Triaged → Fix Released
Changed in xchat-gnome:
status: Unknown → Fix Released
Revision history for this message
Uphaar Agrawalla (uphaar) wrote :

seb, since it is a crasher, any chance you can provide the fix to intrepid-updates as well?

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

intrepid is not a lts and xchat-gnome is a side application and the crasher is easy to workaround I prefer to focus on get jaunty working correctly now but other people are welcome to work on that is they want

Changed in xchat-gnome:
importance: Unknown → Critical
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.