pidgin crashed with SIGSEGV in g_source_attach()

Bug #1530475 reported by Cysioland on 2016-01-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)

Bug Description

Just a random crash

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: pidgin 1:2.10.11-0ubuntu4
Uname: Linux 4.2.5-040205-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Jan 1 22:11:06 2016
ExecutablePath: /usr/bin/pidgin
InstallationDate: Installed on 2014-10-14 (444 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: pidgin
 PATH=(custom, user)
 Segfault happened at: 0x7febbdf0db24 <g_source_attach+4>: cmpq $0x0,0x20(%rdi)
 PC (0x7febbdf0db24) ok
 source "$0x0" ok
 destination "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pidgin
 g_source_attach () from /lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 gst_bus_add_watch_full () from /usr/lib/x86_64-linux-gnu/
 ?? ()
 ?? ()
Title: pidgin crashed with SIGSEGV in g_source_attach()
UpgradeStatus: Upgraded to wily on 2015-10-27 (66 days ago)
UserGroups: adm cdrom dialout dip disk kismet lpadmin mythtv plugdev sambashare sudo vboxusers wireshark

Cysioland (cysioland) wrote :

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1517635, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers