nedit crashed with SIGSEGV in initialize()

Bug #1667773 reported by dlefevre
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nedit (Ubuntu)
New
Medium
Unassigned

Bug Description

nedit crashes when opened from either the command line or the applications menu in Ubuntu-MATE 16.04.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: nedit 1:5.6a-3
ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
Uname: Linux 4.4.0-63-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Feb 24 13:56:58 2017
ExecutablePath: /usr/bin/nedit
InstallationDate: Installed on 2017-02-15 (9 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcCmdline: nedit -server
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/tcsh
SegvAnalysis:
 Segfault happened at: 0x565162788b99: movzwl 0x48(%rdx),%r13d
 PC (0x565162788b99) ok
 source "0x48(%rdx)" (0x00000048) not located in a known VMA region (needed readable region)!
 destination "%r13d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nedit
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 _XtCreateWidget () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
Title: nedit crashed with SIGSEGV in _XtCreateWidget()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
dlefevre (dlefevre) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1415309. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nedit (Ubuntu):
importance: Undecided → Medium
summary: - nedit crashed with SIGSEGV in _XtCreateWidget()
+ nedit crashed with SIGSEGV in initialize()
tags: removed: need-amd64-retrace
Revision history for this message
Paul Gevers (paul-climbing) wrote :

Please install one of the following packages and verify if the bug still appears:
xfonts-100dpi or xfonts-75dpi or xfonts-100dpi-transcoded or xfonts-75dpi-transcoded

Paul

Revision history for this message
dlefevre (dlefevre) wrote :

Sorry, I installed those font packages and I still get the Segfault.

dlefevre (dlefevre)
information type: Private → Public
Revision history for this message
Bill (whiskey9cjo) wrote :

Debian provides a patch for this in their nedit 5.6a-5 package called "improve_no_X_font_handling.patch".

It worked well for me. I've uploaded it.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "Patch from Debian nedit 5.6a-5 package" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
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.