pidgin crashed with SIGSEGV in atoi()

Bug #268698 reported by Miles Lane
6
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

I was logged into MSN, GoogleTalk and IRC at the time of the crash. I was not using the program. As far as I know, it was idle.

I am running the latest packages for Intrepid.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.0-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: pidgin
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 /lib/libc.so.6
 atoi () from /lib/libc.so.6
 ?? () from /usr/lib/purple-2/libmsn.so
 msn_cmdproc_process_cmd ()
 msn_cmdproc_process_cmd_text ()
Title: pidgin crashed with SIGSEGV in atoi()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
Miles Lane (miles-lane) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:____strtoll_l_internal () from /lib/libc.so.6
atoi () from /lib/libc.so.6
ubm_cmd (cmdproc=0x14ae0d0, cmd=0x1d2b3b0)
msn_cmdproc_process_cmd (cmdproc=0x14ae0d0, cmd=0x1d2b3b0)
msn_cmdproc_process_cmd_text (cmdproc=0x14ae0d0,

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

Changed in pidgin:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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

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