Description of problem: not sure Version-Release number of selected component: emacs-24.1-7.fc17 Additional info: backtrace_rating: 4 cmdline: emacs --daemon crash_function: fatal_error_signal executable: /usr/bin/emacs-24.1 kernel: 3.7.9-104.fc17.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 fatal_error_signal at /usr/src/debug/emacs-24.1/src/emacs.c:366 #4 style_changed_cb at /usr/src/debug/emacs-24.1/src/gtkutil.c:1053 #10 g_object_notify_by_spec_internal at gobject.c:1133 #11 g_object_notify at gobject.c:1175 #12 _gtk_settings_handle_event at gtksettings.c:1988 #13 gtk_main_do_event at gtkmain.c:1500 #18 g_main_context_iteration at gmain.c:3207 #19 gtk_main_iteration at gtkmain.c:1345 #20 XTread_socket at /usr/src/debug/emacs-24.1/src/xterm.c:7187 #21 read_avail_input at /usr/src/debug/emacs-24.1/src/keyboard.c:6859
Created attachment 715074 [details] File: C:\nppdf32Log\debuglog.txt
Created attachment 715075 [details] File: backtrace
Created attachment 715076 [details] File: build_ids
Created attachment 715077 [details] File: cgroup
Created attachment 715078 [details] File: core_backtrace
Created attachment 715079 [details] File: environ
Created attachment 715080 [details] File: limits
Created attachment 715081 [details] File: maps
Created attachment 715082 [details] File: open_fds
Created attachment 715083 [details] File: proc_pid_status
Created attachment 715084 [details] File: smolt_data
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
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.