Bug 520616
Summary: | sectool --info NotAtest --use-dbus throws traceback | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miroslav Vadkerti <mvadkert> |
Component: | sectool | Assignee: | Peter Vrabec <pvrabec> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 11 | CC: | dkopecek, jhrozek, mbarabas, pvrabec |
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: | 2009-09-01 13:55:11 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
Miroslav Vadkerti
2009-09-01 13:14:30 UTC
When exception occures in backend side of app. dbus will return exception as well, but except tuierrors.SecToolActionError, dbus will raise DBusException: org.freedesktop.DBus.Python.tuierrors.SecToolActionError. Traceback is not a bug, unknown messages are written to stderr with traceback. It could be done by catching all possible exceptions we know about, but it's much more (almost useless) code. If somebody want a fix for this issue, please reopen this bug (fix for all exceptions not only this one). |