pidgin crashed when switching between wired and wireless networks

Bug #217346 reported by Copernicvs
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

when switching to wireless for a minute, and then back pidgin (2.4.1) crashed

ProblemType: Crash
Architecture: i386
Date: Tue Apr 15 01:03:13 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.4.1-1ubuntu2
PackageArchitecture: i386
ProcCmdline: pidgin
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 g_free () from /usr/lib/libglib-2.0.so.0
 qq_add_buddy_request_free () from /usr/lib/purple-2/libqq.so
 ?? () from /usr/lib/purple-2/libqq.so
 ?? ()
Title: pidgin crashed with SIGSEGV in free()
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
SegvAnalysis:
 Segfault happened at: 0xb763d4da <free+122>: lock cmpxchg %ecx,(%esi)
 PC (0xb763d4da) ok
 source "%ecx" ok
 destination "(%esi)" (0x636f7473) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA

Tags: apport-crash
Revision history for this message
Copernicvs (kornenator) wrote :
Revision history for this message
Magnus S (magnuss) wrote :

Hi, thanks for the report. Is this bug still reproducible? If so, please attach a fresh backtrace by following the instructions at https://wiki.ubuntu.com/Backtrace.

//magnus

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
Revision history for this message
BlueT - Matthew Lien - 練喆明 (bluet) wrote :

I got similar problem too.
when my laptop was suddently got disconnected from the Fon AP, pidgin crashed.

Revision history for this message
BlueT - Matthew Lien - 練喆明 (bluet) wrote :

matthew@Priapus:~$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
matthew@Priapus:~$ LANG="C" apt-cache policy pidgin
pidgin:
  Installed: 1:2.5.2-0ubuntu1
  Candidate: 1:2.5.2-0ubuntu1
  Version table:
 *** 1:2.5.2-0ubuntu1 0
        500 http://ftp.twaren.net intrepid/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
BlueT - Matthew Lien - 練喆明 (bluet) wrote :

and this is the BackTrace result.

Changed in pidgin:
status: Invalid → New
Revision history for this message
BlueT - Matthew Lien - 練喆明 (bluet) wrote :
Kees Cook (kees)
description: updated
Revision history for this message
bbordwell (benbordwell) wrote :

Is this bug still reproducible in lucid? If so could you please reproduce it and create a new backtrace? Also BlueT, your last backtrace had alot of unresolved symbols in it, if you need help getting a backtrace with all the symbols included I can meet you in IRC sometime.

Changed in pidgin (Ubuntu):
status: New → Incomplete
Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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".

Changed in pidgin (Ubuntu):
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.