Version-Release number of selected component: emacs-24.3-14.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 3 cmdline: emacs crash_function: __flockfile executable: /usr/bin/emacs-24.3 kernel: 3.14.0-0.rc2.git0.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 __flockfile at ../nptl/sysdeps/pthread/flockfile.c:29 #1 terminate_due_to_signal at /usr/src/debug/emacs-24.3/src/emacs.c:344 #2 emacs_abort at /usr/src/debug/emacs-24.3/src/sysdep.c:2152 #3 x_connection_closed at /usr/src/debug/emacs-24.3/src/xterm.c:7814 #4 x_error_quitter at /usr/src/debug/emacs-24.3/src/xterm.c:7906 #5 x_error_handler at /usr/src/debug/emacs-24.3/src/xterm.c:7876 #6 ?? #7 ??
Created attachment 865626 [details] File: backtrace
Created attachment 865627 [details] File: cgroup
Created attachment 865628 [details] File: core_backtrace
Created attachment 865629 [details] File: dso_list
Created attachment 865630 [details] File: environ
Created attachment 865631 [details] File: limits
Created attachment 865633 [details] File: maps
Created attachment 865634 [details] File: open_fds
Created attachment 865635 [details] File: proc_pid_status
Created attachment 865636 [details] File: var_log_messages
cause by x_connection_closed
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Hi reporter, I am closing this bug as backtrace does not contain complete information about this issue. This bug comes under those bugs that are hard to reproduce, backtrace does not contain all necessary data due to optimization or are caused by a known glitch in emacs. If you manage to reproduce this issue more than once don't hesitate to reopen this bug. Kind regards Jan