gedit crashed with SIGSEGV in g_closure_invoke()

Bug #1725495 reported by vinid223
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Undecided
Unassigned

Bug Description

I double clicked on a sh file to execute it but gedit opened and crashed. The file was an installation file of 4.5mb

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:50:55 2017
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2017-10-19 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: gedit /home/username/Downloads/anyconnect-linux64-4.4.01054-core-vpn-webdeploy-k9.sh
SegvAnalysis:
 Segfault happened at: 0x7fcb05e29ee6: mov 0xc8(%rax),%rbp
 PC (0x7fcb05e29ee6) ok
 source "0xc8(%rax)" (0x000000c8) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? () 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
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gedit crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
vinid223 (vinid223) 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 #1570938, 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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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