pidgin crashed with SIGSEGV

Bug #278275 reported by Jaakan Shorter
6
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

I just had pidgin siting for a while , hours, and I open the new mail list and hit close but it never closes , pidgin just freezes up.
I had to kill pidgin.

Description: Ubuntu intrepid (development branch)
Release: 8.10

Linux jms1000 2.6.27-4-generic #1 SMP Wed Sep 24 01:29:06 UTC 2008 x86_64 GNU/Linux

pidgin:
  Installed: 1:2.5.1-0ubuntu2
  Candidate: 1:2.5.1-0ubuntu2
  Version table:
 *** 1:2.5.1-0ubuntu2 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Disassembly: 0x7f3ef630cf35:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: wl
Package: pidgin 1:2.5.1-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
Stacktrace: #0 0x00007f3ef630cf35 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: pidgin crashed with SIGSEGV
Uname: Linux 2.6.27-4-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy kvm libvirtd lpadmin netdev plugdev powerdev sambashare scanner video

Revision history for this message
Jaakan Shorter (jaakanshorter) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in pidgin:
importance: Undecided → Medium
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.