pidgin crashed with SIGSEGV

[Jeff Anderson]

Binary package hint: pidgin

Gutsy Gibbon, Pidgin 2.0.2. Crash occured after closing an IM tab.

ProblemType: Crash
Architecture: i386
CoreDump:

Date: Thu Jun 21 16:21:46 2007
Disassembly:

DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.0.2-0ubuntu1
PackageArchitecture: i386
ProcCmdline: pidgin --session 10e595a8a6000118239488400000070890022
ProcCwd: /home/jeff
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Registers:

Signal: 11
SourcePackage: pidgin
Stacktrace:

StacktraceTop:

ThreadStacktrace:

Title: pidgin crashed with SIGSEGV
Uname: Linux lappy486 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for the bug report. Also, please answer these questions:

* Is this crash reproducible?
* If so, which are the steps that lead to it?

This will greatly aid us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[mthakur200x (mthakur2006)]

it is reproducible (i mean it happens every now and then just randomly)

[Arturo Vez (spacemonkey87)]

when i drag a pic to the little box on bottom of the window it chrashes, most of times...

[Craig Snr (internet-junk)]

Happened in 9.04 Netbook Remix

[Blake Munro (blake-munro)]

Happened to me in Ubuntu 9.04 Jaunty Beta AMD64 after closing a chat window. It seems this bug is still lurking...

[Sebastien Bacher (seb128)]

could somebody get the requested detail?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!