gjs-console crashed with SIGSEGV in gd_main_view_generic_set_model()

Bug #1581599 reported by paulle
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

gnome documents crashed

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gjs 1.45.3-1~xenial0.1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri May 13 18:27:26 2016
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2016-04-22 (21 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
ProcCmdline: /usr/bin/gjs /usr/bin/gnome-documents --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe7d417ea4c <gd_main_view_generic_set_model+28>: mov 0x10(%rax),%rax
 PC (0x7fe7d417ea4c) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
 gd_main_view_generic_set_model () from /usr/lib/x86_64-linux-gnu/gnome-documents/libgd.so
 gd_main_view_set_model () from /usr/lib/x86_64-linux-gnu/gnome-documents/libgd.so
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ?? () from /usr/lib/libgjs.so.0
Title: gjs-console crashed with SIGSEGV in gd_main_view_generic_set_model()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
paulle (ya-paulle) wrote :
Revision history for this message
paulle (ya-paulle) wrote :

gnome documents crashed after start

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : 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 #1573987, 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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.