gedit crashed with SIGSEGV in gedit_metadata_manager_set()

Bug #1821946 reported by Marco Giannini
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Undecided
Unassigned

Bug Description

No significant information about the bug

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gedit 3.32.0-1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 27 16:46:53 2019
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2019-02-26 (28 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
ProcCmdline: /usr/bin/gedit --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f41e7e1367a <gedit_metadata_manager_set+138>: mov (%rax),%esi
 PC (0x7f41e7e1367a) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gedit_metadata_manager_set () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so
 gedit_document_set_metadata () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so
 ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gtk_text_view_set_buffer () from /lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
Marco Giannini (marco-giannini) 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 this software better. This particular crash has already been reported and is a duplicate of bug #1821404, 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.