gedit crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
hey guys... context menu show me bug and reporting tool. i don't know what bug is it. the tool should know it, right?
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:05:31 2017
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2016-10-26 (361 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: gedit /home/username/
SegvAnalysis:
Segfault happened at: 0x7f30aa399ee6: mov 0xc8(%rax),%rbp
PC (0x7f30aa399ee6) ok
source "0xc8(%rax)" (0x00000208) 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/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: gedit crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.