pidgin crashed with SIGSEGV in purple_proxy_connect_data_disconnect()

Bug #929826 reported by Romanos Dodopoulos
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Since the other same bug is closed I submit a new one.

Pidgin crashed and closed. A little before this happens, the router lost its connection to internet for a while.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pidgin 1:2.10.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 9 22:50:09 2012
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: pidgin
SegvAnalysis:
 Segfault happened at: 0x7f9a66dda4fc: mov 0x2c(%rdi),%edi
 PC (0x7f9a66dda4fc) ok
 source "0x2c(%rdi)" (0x00000f80) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/libpurple.so.0
 purple_proxy_connect_cancel () from /usr/lib/libpurple.so.0
 purple_ssl_close () from /usr/lib/libpurple.so.0
 ?? () from /usr/lib/purple-2/libmsn-pecan.so
 ?? () from /usr/lib/purple-2/libmsn-pecan.so
Title: pidgin crashed with SIGSEGV in purple_proxy_connect_cancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Romanos Dodopoulos (rwmanos) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 purple_proxy_connect_data_disconnect (connect_data=0xf54, error_message=0x0) at /build/buildd/pidgin-2.10.1/./libpurple/proxy.c:562
 purple_proxy_connect_cancel (connect_data=0xf54) at /build/buildd/pidgin-2.10.1/./libpurple/proxy.c:2502
 purple_ssl_close (gsc=0x7f9a6c84b7f0) at /build/buildd/pidgin-2.10.1/./libpurple/sslconn.c:249
 close_impl (conn=0x7f9a6c315560) at io/pn_ssl_conn.c:267
 close_impl (conn=0x7f9a6c315560) at io/pn_ssl_conn.c:243

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in pidgin (Ubuntu):
importance: Undecided → Medium
summary: - pidgin crashed with SIGSEGV in purple_proxy_connect_cancel()
+ pidgin crashed with SIGSEGV in purple_proxy_connect_data_disconnect()
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pidgin (Ubuntu):
status: New → Confirmed
Revision history for this message
Romanos Dodopoulos (rwmanos) wrote :

I'm changing the status to incomplete to close this issue since it was affecting an EOL Ubuntu version and nobody has reproduced it since then.

Changed in pidgin (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pidgin (Ubuntu) because there has been no activity for 60 days.]

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