Bug 801871
Summary: | spice-xpi cannot create .spicec and write to folder (SeLinux blocks) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pavel Zhukov <pavel> |
Component: | spice-xpi | Assignee: | Peter Hatina <phatina> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | hdegoede, ipilcher, marcandre.lureau, mgrepl, phatina, tsmetana |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-19 14:55:51 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
Pavel Zhukov
2012-03-09 17:23:58 UTC
spice-xpi 2.8 will no longer use ~/.spicec. I just sent an additional patch to Spice ML making sure we don't touch this anymore. We should release a 2.8 version for f17. Did you setup your own label? It looks so. The mozilla_plugin_t label is for process. Just run $ restorecon -R -v ~/ It should fix your issue. (In reply to comment #1) > spice-xpi 2.8 will no longer use ~/.spicec. > > I just sent an additional patch to Spice ML making sure we don't touch this > anymore. > > We should release a 2.8 version for f17. NOTABUG doesn't seem like the correct status for this. It certainly is a bug (in either spice-xpi or the SELinux policy). And spice-xpi 2.8 doesn't appear to actually exist yet. (I can find no evidence of it in Koji or on spice-space.org.) Please don't close bugs until the fix is available. Aargh! I glossed over comment #2, because I had not set manually set any contexts in my home directory. Nonetheless, the context of ~/.spicec was the problem. (Note to self: 'restorecon -r *' is not the same as 'restorecon -r .') Nothing to see here. Move along. |