Bug 1367452 - anaconda uses zenity to report failure to write pid file
Summary: anaconda uses zenity to report failure to write pid file
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-16 12:41 UTC by Ray Strode [halfline]
Modified: 2017-12-12 10:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:26:07 UTC
Type: Bug


Attachments (Terms of Use)

Description Ray Strode [halfline] 2016-08-16 12:41:26 UTC
In a fresh fedora 25 nightly, anaconda fails to write it's PID file at start (probably selinux, since there's an selinux denial notification, too).

This wouldn't be a big deal, I guess, except anaconda notifies the user about this failure, using zenity, in a dialog that pops behind the anaconda window.  This causes a notification to show up saying '"Unable to create PID file" is now ready'

It's not fatal, there's nothing the user can do, the user doesn't need to know. I mean it can go in a log file somewhere, sure, but it's not the kind of error that merits user interaction.

Comment 1 Fedora End Of Life 2017-12-12 10:26:07 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.


Note You need to log in before you can comment on or make changes to this bug.