pidgin crashed with SIGSEGV in g_source_attach()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Ubuntu) |
New
|
Undecided
|
Unassigned |
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-
NonfreeKernelMo
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
ProcEnviron:
LANGUAGE=pl_PL
PATH=(custom, user)
XDG_RUNTIME_
LANG=pl_PL.UTF-8
SHELL=
SegvAnalysis:
Segfault happened at: 0x7febbdf0db24 <g_source_
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
StacktraceTop:
g_source_attach () from /lib/x86_
?? () from /usr/lib/
gst_bus_
?? ()
?? ()
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
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.