Bug 789239 - SELinux is preventing Wine from starting
Summary: SELinux is preventing Wine from starting
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-10 07:03 UTC by Jiri Mensik
Modified: 2012-08-18 17:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-18 17:39:15 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jiri Mensik 2012-02-10 07:03:07 UTC 
Description of problem:
Wine doesn't start.

Version-Release number of selected component (if applicable):
wine-1.3.37

How reproducible:
It happens always, I am still not able to run Wine.

Steps to Reproduce:
1. install and update fedora 16
2. "yum install wine" (I think)
3. try to run Wine
  
Actual results:
Wine doesn't start.

Expected results:
Wine should start.

Additional info:
from /var/log/messages:

Feb 10 07:55:34 Jirka-Fedora setroubleshoot: SELinux is preventing /usr/bin/wine-preloader from mmap_zero access on the None . For complete SELinux messages. run sealert -l f740bb23-75ef-401e-a258-3e94b6f44f02
Comment 1 Jiri Mensik 2012-02-10 07:11:28 UTC 
I run the sealert, but didn't get anything useful.

[root@Jirka-Fedora ~]# sealert -l f7
Error query_alerts error (1003): id (f7) not found
[root@Jirka-Fedora ~]# logout
[Jirka@Jirka-Fedora ~]$ sealert -l f7
Error query_alerts error (1003): id (f7) not found
Comment 2 Michael Cronenworth 2012-08-18 17:39:15 UTC 
Please file bugs against the correct component.

The latest version of wine for Fedora 16 is 1.5.9.

The SELinux message can be ignored as it does not affect normal Wine usage.

To view SELinux messages you must supply the /full/ ID.

Incorrect:
# sealert -l f7

Correct:
# sealert -l f740bb23-75ef-401e-a258-3e94b6f44f02
Note You need to log in before you can comment on or make changes to this bug.