Ubuntu
gedit package

gedit -w -s crashes with SIGSEGV

Bug #1832695 reported by PeterPall on 2019-06-13

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gedit (Ubuntu)	New	Medium	Unassigned

Bug Description

After doing a

git config --global core.editor "gedit -w -s"

gedit crashes as soon as I try to commit something using git.

git config --global core.editor "gedit -s"

works fine, though => Something is wrong with gedit's '-w' switch.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gedit 3.32.0-3
ProcVersionSignature: Ubuntu 5.0.0-16.17-lowlatency 5.0.8
Uname: Linux 5.0.0-16-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 13 11:14:26 2019
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2019-05-26 (18 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcCmdline: gedit -w -s /home/username/src/maxima-code/.git/COMMIT_EDITMSG
SegvAnalysis:
Segfault happened at: 0x7fb5d8619518: mov 0x30(%rdi),%eax
PC (0x7fb5d8619518) ok
source "0x30(%rdi)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
() at /lib/x86_64-linux-gnu/libgio-2.0.so.0
() at /lib/x86_64-linux-gnu/libgio-2.0.so.0
g_application_register () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
() at /lib/x86_64-linux-gnu/libgio-2.0.so.0
g_application_run () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gedit crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare scanner sudo wireshark
separator:

Tags:

Revision history for this message

PeterPall (peterpall) wrote on 2019-06-13:

#1

Dependencies.txt Edit (23.8 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (796 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (131.2 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (325 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (49.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1013 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (427 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2019-06-13:

#2

StacktraceTop:
g_dbus_action_group_sync (group=group@entry=0x0, cancellable=cancellable@entry=0x0, error=error@entry=0x7ffc8cb32a80) at ../../../gio/gdbusactiongroup.c:524
g_application_impl_register (application=application@entry=0x555a3abc31e0, appid=<optimized out>, flags=<optimized out>, exported_actions=<optimized out>, remote_actions=remote_actions@entry=0x555a3abc3188, cancellable=cancellable@entry=0x0, error=0x7ffc8cb32a80) at ../../../gio/gapplicationimpl-dbus.c:646
g_application_register (error=0x7ffc8cb32a80, cancellable=0x0, application=0x555a3abc31e0) at ../../../gio/gapplication.c:2166
g_application_register (application=0x555a3abc31e0, cancellable=0x0, error=0x7ffc8cb32a80) at ../../../gio/gapplication.c:2155
g_application_real_local_command_line (application=0x555a3abc31e0, arguments=0x7ffc8cb32ae8, exit_status=0x7ffc8cb32ae4) at ../../../gio/gapplication.c:1105

Revision history for this message

Apport retracing service (apport) wrote on 2019-06-13: Stacktrace.txt

#3

Stacktrace.txt Edit (2.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2019-06-13: StacktraceSource.txt

#4

StacktraceSource.txt Edit (1.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2019-06-13: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (5.4 KiB, text/plain)

Changed in gedit (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2019-06-21:

#6

Thank you for your bug report, those options indeed seem incompatible, that should be reported upstream on https://gitlab.gnome.org/GNOME/gedit/issues/

information type:

Private → Public

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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