Pidgin supposedly crashed on login right after I upgraded from Gusty to Hardy

Bug #277355 reported by emerald000
6
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

I decided today to upgrade from Gutsy to Hardy. Right after I rebooted, there's this message in top-right corner saying there has been a crash in pidgin. Yet, Pidgin was working like a charm. I am still filling this since it is not normal to receive a crash error when something works normally.

ProblemType: Crash
Architecture: i386
Date: Sun Sep 28 15:21:50 2008
Disassembly: 0x0:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.4.1-1ubuntu2.1
PackageArchitecture: i386
ProcCmdline: pidgin
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:

Title: pidgin crashed with SIGSEGV
Uname: Linux 2.6.24-19-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
emerald000 (emerald000) 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.