| Summary: | [abrt] gkrellm-2.3.4-3.fc14: gkrellm_exit: Process /usr/bin/gkrellm was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dale Snell <dbuggzie> | ||||
| Component: | atk | Assignee: | Matthias Clasen <mclasen> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | hdegoede, mclasen, ville.skytta | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:35871db1f3a8ae72bf0e78593635586cb009947a | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-03-21 16:14:21 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Dale Snell
2011-03-21 03:38:21 UTC
Created attachment 486539 [details]
File: backtrace
The backtrace points to a failure in atk-spi when it tries to clean up some things on exit from a registered exit handler, changing component. Dale, looking at the backtrace it suggests this crash happened while you exited from gkrellm, did you quit gkrellm? (In reply to comment #2) > The backtrace points to a failure in atk-spi when it tries to clean up some > things on exit from a registered exit handler, changing component. Would that be related to bug 657967? That one seems responsible for quite a number of seemingly-random failures. > Dale, looking at the backtrace it suggests this crash happened while you exited > from gkrellm, did you quit gkrellm? No, I hadn't. It's by far my favorite tool for displaying system status. I have it set to start when I log in, and it stays running until I log out. To tell the truth, GKrellM did not seem to have died at all, since the graphs were uninterrupted. BTW, you may be interested in bug 689314. It's the same sort of thing (at least from my point of view). This bug may be a duplicate of that one, I don't know. I'm afraid I'd forgotten about it when I submitted this bug report. (In reply to comment #3) > (In reply to comment #2) > > The backtrace points to a failure in atk-spi when it tries to clean up some > > things on exit from a registered exit handler, changing component. > > Would that be related to bug 657967? That one seems responsible for quite a > number of seemingly-random failures. > At a first glance that one seems unrelated. > > Dale, looking at the backtrace it suggests this crash happened while you exited > > from gkrellm, did you quit gkrellm? > > No, I hadn't. It's by far my favorite tool for displaying system status. I > have it set to start when I log in, and it stays running until I log out. To > tell the truth, GKrellM did not seem to have died at all, since the graphs were > uninterrupted. > Weird, this makes me wonder if the backtrace is correct at all. Maybe abrt detected some older core file of a previous crash and used that ?? > BTW, you may be interested in bug 689314. It's the same sort of thing (at > least from my point of view). This bug may be a duplicate of that one, I don't > know. I'm afraid I'd forgotten about it when I submitted this bug report. Erm, this is bug 689314, so you probably meant another bug ? (In reply to comment #4) > (In reply to comment #3) > > > > BTW, you may be interested in bug 689314. It's the same sort of thing (at > > least from my point of view). This bug may be a duplicate of that one, I don't > > know. I'm afraid I'd forgotten about it when I submitted this bug report. > > Erm, this is bug 689314, so you probably meant another bug ? Ack! That's... interesting. I seem to have encountered a bug in Bugzilla. On my "My Bugs" page, _this_ bug is listed as being assigned to mclasen, while the older bug report -- bug 678896, which is the one I'd meant to reference in my previous comment -- is shown assigned to you. And since I'd gone by the assignee field when doing my cut-and-paste, I got the wrong number. As for abrt getting confused and using an old backtrace, I suppose it's possible. /var/spool/abrt does contain several old reports, including the older gkrellm report. However, I looked at the backtraces and they aren't the same. The one referenced in this bug report is the one from the most recent gkrellm crash. So I don't think abrt is getting confused. Backtrace analysis found this bug to be similar to bug #678896, closing as duplicate. This comment is automatically generated. *** This bug has been marked as a duplicate of bug 678896 *** |