Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1066749

Summary: [abrt] emacs: terminate_due_to_signal(): emacs-24.3 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Jim Carpenter <jcarpenter>
Component: emacsAssignee: Petr Hracek <phracek>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jchaloup, jonathan.underwood, js, phracek, unixi
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:9df01f0d405e27bef1fed0c27973b971e3facdb4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-23 13:07:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace
File: cgroup
File: core_backtrace
File: dso_list
File: environ
File: limits
File: maps
File: open_fds
File: proc_pid_status
File: var_log_messages none

Description Jim Carpenter 2014-02-19 02:47:44 UTC
Description of problem:
Tried running emacs while tunneling X11 via ssh. It often immediately bombs the first time and then works flawlessly afterwards.

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 3
cmdline:        emacs iouyap.c iouyap.h iouyap.o iouyap.s netmap.h iou_hdr.c iou_hdr.c~ iou_hdr.h iou_hdr.h~
crash_function: terminate_due_to_signal
executable:     /usr/bin/emacs-24.3
kernel:         3.13.3-201.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (7 frames)
 #2 terminate_due_to_signal at /usr/src/debug/emacs-24.3/src/emacs.c:344
 #3 emacs_abort at /usr/src/debug/emacs-24.3/src/sysdep.c:2152
 #4 x_connection_closed at /usr/src/debug/emacs-24.3/src/xterm.c:7814
 #5 x_error_quitter at /usr/src/debug/emacs-24.3/src/xterm.c:7906
 #6 x_error_handler at /usr/src/debug/emacs-24.3/src/xterm.c:7876
 #7 ??
 #8 ??

Potential duplicate: bug 995186

Comment 1 Jim Carpenter 2014-02-19 02:47:49 UTC
Created attachment 864921 [details]
File: backtrace

Comment 2 Jim Carpenter 2014-02-19 02:47:50 UTC
Created attachment 864922 [details]
File: cgroup

Comment 3 Jim Carpenter 2014-02-19 02:47:52 UTC
Created attachment 864923 [details]
File: core_backtrace

Comment 4 Jim Carpenter 2014-02-19 02:48:02 UTC
Created attachment 864924 [details]
File: dso_list

Comment 5 Jim Carpenter 2014-02-19 02:48:04 UTC
Created attachment 864925 [details]
File: environ

Comment 6 Jim Carpenter 2014-02-19 02:48:06 UTC
Created attachment 864926 [details]
File: limits

Comment 7 Jim Carpenter 2014-02-19 02:48:09 UTC
Created attachment 864927 [details]
File: maps

Comment 8 Jim Carpenter 2014-02-19 02:48:11 UTC
Created attachment 864928 [details]
File: open_fds

Comment 9 Jim Carpenter 2014-02-19 02:48:12 UTC
Created attachment 864929 [details]
File: proc_pid_status

Comment 10 Jim Carpenter 2014-02-19 02:48:14 UTC
Created attachment 864930 [details]
File: var_log_messages

Comment 11 Jan Chaloupka 2014-04-23 13:07:49 UTC
Hi, James,

from backtrace I get this error message: "X protocol error: BadAccess (attempt to access private resource denied) on protocol request 143". It is a question of proper setting of ssh.

Here you can get some hints that could solve it:

Recommended use is 'ssh -Y' with ForwardX11Trusted directive in ssh_config(5) instead of 'ssh -X'.

For more information 'man ssh' and -X,-Y options


Comment 12 James Boyle 2014-04-25 14:07:36 UTC
Just to chime in, I had emacs crash on me, but they were local windows (in MATE).