pidgin crashed with SIGSEGV in out_cmd

Bug #183881 reported by ebnf
10
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: pidgin

Pigdin 2.3.1

Got this while idling seems like maybe MSN is messing with their protocol?

ProblemType: Crash
Architecture: i386
Date: Thu Jan 17 10:23:33 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: vmnet vmblock vmmon
Package: pidgin 1:2.3.1-2ubuntu1
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/eric
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/purple-2/libmsn.so
 ?? () from /usr/lib/purple-2/libmsn.so
 ?? () from /usr/lib/purple-2/libmsn.so
 ?? ()
 ?? () from /usr/lib/purple-2/libmsn.so
Title: pidgin crashed with SIGSEGV
Uname: Linux eric-desktop 2.6.24-4-generic #1 SMP Mon Jan 14 17:30:39 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Tags: apport-crash
Revision history for this message
ebnf (eric-zeitler) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:out_cmd (cmdproc=0x85ec850, cmd=0x85b6d38) at ../../../../libpurple/protocols/msnp9/notification.c:339
msn_cmdproc_process_cmd (cmdproc=0x85ec850, cmd=0x85b6d38)
msn_cmdproc_process_cmd_text (cmdproc=0x85ec850, command=0x85f4130 "OUT")
read_cb (data=0x85ede38, source=26, cond=PURPLE_INPUT_READ)
pidgin_io_invoke (source=0x855c078, condition=<value optimized out>, data=0x85790c0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in pidgin:
importance: Undecided → Medium
Revision history for this message
Brian Curtis (bcurtiswx) wrote :

Thank you for your bug report. Do you still experience this issue with an up-to-date system?

Changed in pidgin:
status: New → Incomplete
Revision history for this message
ebnf (eric-zeitler) wrote :

No, I haven't received this crash in a while.

Revision history for this message
Brian Curtis (bcurtiswx) wrote :

As per the users response, this bug is being marked as fixed

Changed in pidgin:
status: Incomplete → Fix Released
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.