pidgin crashed changing icon with SIGSEGV in memcpy()

Bug #383986 reported by Alejandro R. Mosteo
36
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Pidgin
Confirmed
Unknown
pidgin (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

This is a duplicate of bug 139081, but I was asked to open it with apport to get the collected information.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.5-1ubuntu8.1
ProcCmdline: pidgin
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 memcpy () from /lib/libc.so.6
 gdk_pixbuf_loader_write ()
 pidgin_status_box_redisplay_buddy_icon (
 buddy_icon_set_cb (
 do_callbacks (name=0x80fc0d4 "/pidgin/accounts/buddyicon",
Title: pidgin crashed with SIGSEGV in memcpy()
Uname: Linux 2.6.28-11-server i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mail plugdev vboxusers video www-data

Revision history for this message
Alejandro R. Mosteo (mosteo) wrote :
visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
Saivann Carignan (oxmosys) wrote :

I'm adding some useful information about the bug :

Screencast : http://upload.leservicetechnique.com/bugs/pidgin_mystatusbox.ogv

Steps to reproduce :
1. Start pidgin.
2. Go to Tools / Plugins and check the mystatusbox plugin.
3. Click on the bottom-right picture to change it.
4. Choose any png in your computer pictures.
5. If pidgin does not crash, repeat 3 and 4 until it does.

I also attach a backtrace, a strace and a valgrind

Revision history for this message
Saivann Carignan (oxmosys) wrote :
Revision history for this message
Saivann Carignan (oxmosys) wrote :
Changed in pidgin:
status: Unknown → New
Revision history for this message
Saivann Carignan (oxmosys) wrote :

According to upstream pidgin developers, this issue has been fixed in pidgin 1.5.6 which is already in karmic. I installed 1.5.6 and was not able to reproduce the problem anymore. According to this, I set the status to fix released.

Changed in pidgin (Ubuntu):
status: New → Fix Released
Changed in pidgin:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.