| Summary: | RFE: use ABRT for handling GUI exceptions | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard Marko <rmarko> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED WONTFIX | QA Contact: | Richard Marko <rmarko> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 16 | CC: | berrange, crobinso, dougsland, dpierce, hbrock, jberan, jforbes, jmoskovc, rmarko, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-27 14:11:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Richard Marko
2011-10-24 11:17:59 UTC
Clarification: error handling of internal errors (python trackebacks) should be integrated with ABRT (not with python-meh) "Integrating with ABRT" means "just call the original exception handler, after you're done with processing the exception" Many caught and reported exceptions aren't unexpected: the complexity of libvirt configuration options means there are many times that an operation has legitimate reason not to work, but virt-manager doesn't want to be in the game of 100% duplicating libvirt validation logic. Some of these reported errors will be libvirt/virt-manager bugs, but it's not feasible to determine the difference I don't want to start getting flooded with abrt false positives. For uncaught exceptions the default exception handler is raised, so those are already covered. Thanks for the report, but closing as WONTFIX |