Version-Release number of selected component: emacs-24.2-5.fc18 Additional info: backtrace_rating: 4 cmdline: emacs class.cpp crash_function: fatal_error_signal executable: /usr/bin/emacs-24.2 kernel: 3.7.2-204.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 fatal_error_signal at /usr/src/debug/emacs-24.2/src/emacs.c:366 #4 getenv at getenv.c:89 #5 g_getenv at genviron.c:256 #6 send_and_allow_reentry at event.c:104 #7 Accessibility_DeviceEventController_NotifyListenersSync at event.c:155 #8 spi_atk_bridge_key_listener at event.c:224 #9 _gail_util_key_snooper at gailutil.c:284 #10 gtk_invoke_key_snoopers at gtkmain.c:2247 #11 gtk_main_do_event at gtkmain.c:1667 #16 g_main_context_iteration at gmain.c:3351
Created attachment 694335 [details] File: backtrace
Created attachment 694336 [details] File: cgroup
Created attachment 694337 [details] File: core_backtrace
Created attachment 694338 [details] File: dso_list
Created attachment 694339 [details] File: environ
Created attachment 694340 [details] File: limits
Created attachment 694341 [details] File: maps
Created attachment 694342 [details] File: open_fds
Created attachment 694343 [details] File: proc_pid_status
Created attachment 694344 [details] File: var_log_messages
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
For analysis I would like to get some overview. How to simulate that error. You have just only logged into KDE and run command emacs --daemon? Did you logged out from session when SIGSEGV occurs? Thank you in advance
I was just saving a text file backtrace_rating: 4 cmdline: emacs crash_function: fatal_error_signal executable: /usr/bin/emacs-24.2 kernel: 3.8.11-200.fc18.x86_64 package: emacs-24.2-18.fc18 reason: Process /usr/bin/emacs-24.2 was killed by signal 7 (SIGBUS) uid: 500 ureports_counter: 1 xsession_errors:
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days