gedit crashed with SIGSEGV in gedit_metadata_manager_set()
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
ProcVersionSign
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelMo
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-
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
PATH=(custom, no user)
LANG=it_IT.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f41e7e1367a <gedit_
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_
gedit_
?? () from /usr/lib/
g_object_unref () from /lib/x86_
gtk_text_
Title: gedit crashed with SIGSEGV in gedit_metadata_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
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.