gedit crashed with SIGSEGV in g_closure_invoke()

Bug #1734966 reported by Scott Cohen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Undecided
Unassigned

Bug Description

I accidentally opened a 7.8 MB text file with gedit and closed it. From what I could tell, it looked like it exited fine but evidently it didn't.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 28 10:01:37 2017
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2017-11-27 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gedit /media/username/VBox_GAs_5.2.0/VBoxLinuxAdditions.run
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f9bace1aea2: mov 0x18(%rax),%rdi
 PC (0x7f9bace1aea2) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so
 ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so
 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: gedit crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to bionic on 2017-11-27 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Scott Cohen (yetoo) wrote :
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.