Ubuntu GNOME

yelp crashed with SIGSEGV in g_object_new_valist()

Bug #1436747 reported by thrantir on 2015-03-26

This bug report is a duplicate of: Bug #1338600: yelp crashed with SIGSEGV in location_entry_constructed(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu GNOME	New	Undecided	Unassigned

Bug Description

program crashed

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: yelp 3.12.0-1ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar 26 09:41:40 2015
ExecutablePath: /usr/bin/yelp
InstallationDate: Installed on 2015-01-20 (65 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: yelp help:gnome-help/files
SegvAnalysis:
Segfault happened at: 0x7f8c35e16b87: mov (%rax),%rdi
PC (0x7f8c35e16b87) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: yelp
StacktraceTop:
?? () from /usr/lib/libyelp.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
yelp_location_entry_new () from /usr/lib/libyelp.so.0
Title: yelp crashed with SIGSEGV in g_object_new_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

thrantir (thrantir) wrote on 2015-03-26:

CrashDB.txt Edit (263 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (9.8 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (305 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (5.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu GNOME (ug-bot) wrote on 2015-03-26: This bug is a duplicate

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 #1338600, 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.