Bug 875440

Created attachment 642665 [details]
File: core_backtrace

Created attachment 642666 [details]
File: environ

Created attachment 642667 [details]
File: event_log

Created attachment 642668 [details]
File: limits

Created attachment 642669 [details]
File: backtrace

Created attachment 642670 [details]
File: cgroup

Created attachment 642671 [details]
File: smolt_data

Created attachment 642672 [details]
File: executable

Created attachment 642673 [details]
File: maps

Created attachment 642674 [details]
File: dso_list

Created attachment 642675 [details]
File: proc_pid_status

Created attachment 642676 [details]
File: var_log_messages

Created attachment 642677 [details]
File: open_fds

Crash on xfce4 session start, after following the directions on the following page to try to fix Bug 860312 ("Back to top level." being dumped at high rate in .xsession-errors):

http://www.emacswiki.org/emacs/EmacsAsDaemon


backtrace_rating: 4
Package: emacs-24.2-5.fc18
OS Release: Fedora release 18 (Spherical Cow)

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

The following is a symptom: when closing a .tex document, emacs complained 'there is an active process'. There were no active processes such as terminal sessions, mysql sessions &c. After I force closed the .tex document, emacs appeared to quit normally. Running a 'ps -A | grep emacs' command showed that there was an emacs process running. I killed that process 'kill <process id number>' (as I do frequently) and all returned to normal.

backtrace_rating: 4
Package: emacs-24.2-6.fc18
Architecture: i686
OS Release: Fedora release 18 (Spherical Cow)

To reproduce (not 100% reproducable)
Kill a buffer (C-x k) Observe a message 'Buffer 'whatever it is' still has clients; kill it? (yes or no)' even though there are no other clients running. If I type 'yes' the entire emacs goes down, even buffers that I do not want to kill. A 'ps -A | grep emacs' command shows that emacs is still running. 'kill <process ID>' dismisses the process.
At this point, emacs is down, and the Automatic Bug Reporting Tool (ABRT) comes up asking if I want to submit a report.

The following may be indirectly related. I offer it in that it may offer a clue.

I am a heavy emacs user, I use it particularly heavily for LaTeX.

I have emacs configured to use texlive-2012 downloaded and installed directly (outside of the Fedora repository) contrasted with the traditional Fedora texlive installation. I do not know if this is germane to the problem or not.

I never saw this problem until upgrading from emacs-23 (Fedora 17) to emacs-24 (Fedora 18).


backtrace_rating: 4
Package: emacs-24.2-6.fc18
Architecture: i686
OS Release: Fedora release 18 (Spherical Cow)

I'm using emacs in the server+clients mode and this happens every time tthe server is killed by the SIGTERM (e.g. on system shutdown).

backtrace_rating: 4
cmdline:        emacs --daemon
crash_function: abort
executable:     /usr/bin/emacs-24.2
kernel:         3.8.1-201.fc18.i686
package:        emacs-24.2-6.fc18
reason:         Process /usr/bin/emacs-24.2 was killed by signal 6 (SIGABRT)
uid:            1000
ureports_counter: 1
xsession_errors:

Do not know. Icon showed up in XFCE information bar. Does not seem to impact system performance.

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        emacs --daemon
core_backtrace: 
crash_function: abort
executable:     /usr/bin/emacs-24.2
kernel:         3.9.4-200.fc18.i686
package:        emacs-24.2-18.fc18
reason:         Process /usr/bin/emacs-24.2 was killed by signal 6 (SIGABRT)
runlevel:       N 5
uid:            1000
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.