Description of problem: I closed emacs with reboot purposes, but I am newbie, I don't know how to deal with emacs client and server together and I have not found proper guide, so It should be somtehing that related. Being Emacs-server still working at background probably receives the closing order as a kill signal. It's all what I know, by now... If so what should I do? Thanks. Version-Release number of selected component: emacs-24.2-6.fc18 Additional info: backtrace_rating: 4 cmdline: emacs --daemon crash_function: style_changed_cb executable: /usr/bin/emacs-24.2 kernel: 3.8.2-206.fc18.i686 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 style_changed_cb at /usr/src/debug/emacs-24.2/src/gtkutil.c:1053 #1 g_cclosure_marshal_VOID__PARAM at gmarshal.c:1042 #7 g_object_notify_by_spec_internal at gobject.c:1135 #8 g_object_notify at gobject.c:1177 #9 _gtk_settings_handle_event at gtksettings.c:2595 #10 gtk_main_do_event at gtkmain.c:1496 #11 _gdk_event_emit at gdkevents.c:69 #16 g_main_context_iteration at gmain.c:3351 #17 gtk_main_iteration at gtkmain.c:1264 #18 XTread_socket at /usr/src/debug/emacs-24.2/src/xterm.c:7187
Created attachment 711444 [details] File: backtrace
Created attachment 711445 [details] File: cgroup
Created attachment 711446 [details] File: core_backtrace
Created attachment 711447 [details] File: dso_list
Created attachment 711448 [details] File: environ
Created attachment 711449 [details] File: limits
Created attachment 711450 [details] File: maps
Created attachment 711451 [details] File: open_fds
Created attachment 711452 [details] File: proc_pid_status
Created attachment 711453 [details] File: var_log_messages
scm-commit (http://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130325/990284.html) -> modified
emacs-24.2-15.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/emacs-24.2-15.fc18
emacs-24.2-16.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/emacs-24.2-16.fc18
Package emacs-24.2-16.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing emacs-24.2-16.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4933/emacs-24.2-16.fc18 then log in and leave karma (feedback).
emacs-24.2-17.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/emacs-24.2-17.fc18
emacs-24.2-18.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/emacs-24.2-18.fc18
emacs-24.2-18.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.