Pidgin Crashed with Segfault Reported

[Stephen L]

Binary package hint: pidgin

How I Produce the Crash:

1. Launch Pidgin.
2. Double-click a buddy to open a new chat window.
3. Enter some text.
4. Hit Enter.
5. Crash. All windows close. Inspecting /var/log/syslog reveals a segfault has occurred.

Here are the log entries produced by five such crashes:

Oct 7 15:28:06 CACC-DTOP-34 kernel: [93927.072057] pidgin[32718]: segfault at 00000004 eip b780bef6 esp b4bc59b8 error 6
Oct 7 15:28:51 CACC-DTOP-34 kernel: [93972.333004] pidgin[306]: segfault at 00000004 eip b77f6ef6 esp b4c10ac8 error 6
Oct 7 15:35:01 CACC-DTOP-34 kernel: [94341.792356] pidgin[762]: segfault at 00000004 eip b7876ef6 esp b41ddaa8 error 6
Oct 7 15:54:19 CACC-DTOP-34 kernel: [ 120.424349] pidgin[7221]: segfault at 00000004 eip b7889ef6 esp b4c7a9c8 error 6
Oct 7 15:56:30 CACC-DTOP-34 kernel: [ 250.683593] pidgin[7421]: segfault at 00000004 eip b7889ef6 esp b4cd2ac8 error 6

BTW: At least one of the five crashes occurred while I was typing the message (didn't even have to hit Enter).

My Environment:
Ubuntu: 8.04 (actually Ubuntu 8.04.1 according to /cat/issue)
Package: 1:2.5.0-0ubuntu2~hardy1
Kernel: 2.6.24-19-generic (#1 SMP Wed Aug 20 22:56:21 UTC 2008)

Assuming "Report a Problem" will include any other needed info.

Thank you!

ProblemType: Bug
Architecture: i386
Date: Tue Oct 7 15:33:55 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.0-0ubuntu2~hardy1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
SourcePackage: pidgin
Uname: Linux 2.6.24-19-generic i686

[arno_b (arno.b)]

Please, try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/DebuggingProgramCrash.
(install packages 'pidgin-dbg' and 'gdb' and see here for backtrace https://wiki.ubuntu.com/Backtrace)

Set to incomplete until we have a backtrace.

[Pedro Villavicencio (pedro)]

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!.