Bug 470159
| Summary: | emacs hangs and outputs error info when dragging mouse 1 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dave Blackburn <blackburn> |
| Component: | emacs | Assignee: | Daniel Novotny <dnovotny> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | blackburn, dcantrell |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-07-14 14:07:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dave Blackburn
2008-11-06 02:22:34 UTC
Later I observed several emacs processes running w/o a display window: 11254 root 20 0 131m 24m 9876 R 25.3 1.2 182:08.06 emacs 11469 root 20 0 131m 24m 9856 R 25.0 1.2 180:41.90 emacs 13335 trudy 20 0 131m 24m 9836 R 25.0 1.2 62:09.06 emacs 13392 trudy 20 0 131m 24m 9820 R 25.0 1.2 48:09.37 emacs 13589 trudy 20 0 131m 24m 9820 R 25.0 1.2 45:35.75 emacs 13596 trudy 20 0 127m 20m 9800 R 25.0 1.0 45:11.26 emacs 11578 root 20 0 131m 24m 9864 R 24.6 1.2 174:09.46 emacs 13538 root 20 0 130m 23m 9816 R 24.6 1.2 47:59.00 emacs I killed most of these processes with the default kill signal. While doing so, two processes changed state to: ps -Al | grep emacs 0 S 511 13335 1 28 80 0 - 33599 futex_ pts/0 01:02:53 emacs 0 S 0 13538 1 25 80 0 - 33486 futex_ pts/1 00:48:43 emacs but were only killable using kill -9 Earlier, when the emacs processes were hung so c-x c-c was not usable, I had used the window manager (fvwm) destroy op to kill emacs. That got rid of the emacs windows but apparently left a process still running. It looks like one process was left for each test I ran. I then ran emacs -q & followed by lsof -p <process>. Next, I caused the failure and ran lsof -p <process> again. The second time, after the failure, lsof listed one additional loaded lib: emacs 29820 root mem REG 8,8 93416 293917 /lib64/libgcc_s-4.3.0-20080428.so.1 Otherwise, the lsof output was identical. I ran the following: yum erase emacs yum install emacs-1:22.2-4.fc9.x86_64 yum update emacs I can no longer reproduce this problem. Both emacs-1:22.2-4 and emacs-1:22.2-5 work OK. I reduced the priority to low. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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. |