evince crashed with SIGSEGV in gtk_widget_get_toplevel()

Bug #1195505 reported by siucdude
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Expired
Medium
Unassigned

Bug Description

i get this once in a while, when working with a pdf doc..
TJ

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evince 3.8.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.10.0-0.7-generic 3.10.0-rc7
Uname: Linux 3.10.0-0-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Thu Jun 27 18:34:45 2013
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2011-04-03 (816 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-0-generic root=UUID=02993959-dfdc-418a-91d6-600a20b78305 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb6bcff4fc6 <gtk_widget_get_toplevel+22>: cmp %rax,(%rdx)
 PC (0x7fb6bcff4fc6) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgrip.so.0
 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
Title: evince crashed with SIGSEGV in gtk_widget_get_toplevel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video

Revision history for this message
siucdude (siucdude) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_widget_get_toplevel (widget=0x7fb6bfe860d0) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkwidget.c:10230
 window_destroyed_cb (object=0x7fb6bfbb51d0, user_data=0x7fb6bfe7f100) at gripgesturemanager.c:686
 g_closure_invoke (closure=0x7fb6bff3dbf0, return_value=0x0, n_param_values=1, param_values=0x7fff0dfee430, invocation_hint=0x7fff0dfee3d0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x7fb6bfad7d70, detail=detail@entry=0, instance=instance@entry=0x7fb6bfbb51d0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff0dfee430) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3582
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff0dfee5b8) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3326

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evince (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evince (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

siucdude, thank you for reporting this bug to Ubuntu. Saucy reached EOL on July 17, 2014.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue on a supported release? If so, could you please execute the following at a terminal as it will automatically gather debugging information:
apport-collect 1195505

As well, could you please attach a document that demonstrates this problem?

Changed in evince (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for evince (Ubuntu) because there has been no activity for 60 days.]

Changed in evince (Ubuntu):
status: Incomplete → Expired
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.