pidgin crashed with SIGSEGV in SmcCloseConnection()

Bug #1106198 reported by Coya DeBrojara
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
New
Undecided
Unassigned

Bug Description

The "pidgin" has failed along with the program "xfce4-session" (Bug # 1104435). In the meantime no operations were performed. This error is similar to the previously reported earlier Bug # 1103165.

Program "pidgin" uległ awarii wraz z programem "xfce4-session" (Bug #1104435 ). W międzyczasie nie byly wykonywane żadne czynności. Ten błąd, jest podobny do zgłoszonego wcześniej wcześniej Bug #1103165.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: pidgin 1:2.10.6-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sat Jan 26 17:53:34 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/pidgin
InstallationDate: Installed on 2013-01-13 (13 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130113)
MarkForUpload: True
ProcCmdline: pidgin --session 2fdc57b36-02f0-4670-9b2c-3561bab6c610 --display :0.0
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8fe114d3a6 <SmcCloseConnection+150>: mov %ebx,0x4(%rax)
 PC (0x7f8fe114d3a6) ok
 source "%ebx" ok
 destination "0x4(%rax)" (0x00000085) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 SmcCloseConnection () from /usr/lib/x86_64-linux-gnu/libSM.so.6
 pidgin_session_end ()
 ?? ()
 purple_core_quit () from /usr/lib/libpurple.so.0
 ?? ()
Title: pidgin crashed with SIGSEGV in SmcCloseConnection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Coya DeBrojara (coyadebrojara) wrote :
information type: Private → Public
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.