evince crashed with SIGSEGV in g_closure_invoke()

Bug #887815 reported by Shock
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was trying to move the "Back" toolbar button to the leftmost position in the toolbar.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Nov 9 00:54:07 2011
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: BOOT_IMAGE=/vmlinuz-3.0.0-13-generic root=UUID=bdd0f7f0-e92e-40fb-989d-7daec91beae7 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fa36c2753b4: mov 0x30(%rax),%rax
 PC (0x7fa36c2753b4) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: evince crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Shock (mmiron) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #863449, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.