Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1514988 - Cannot open a gnome session with confine users [NEEDINFO]
Summary: Cannot open a gnome session with confine users
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted
Version: 26
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-19 21:41 UTC by olsesi
Modified: 2018-05-29 11:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-29 11:36:58 UTC
lvrabec: needinfo? (olsesi)

Attachments (Terms of Use)
I joined the relevant log messages for xguest user login attempt. (deleted)
2017-11-19 21:41 UTC, olsesi
no flags Details

Description olsesi 2017-11-19 21:41:15 UTC
Created attachment 1355393 [details]
I joined the relevant log messages for xguest user login attempt.

Description of problem:
When I map a user to any confined X SELinux user (xguest_u, user_u, sysadm_u ...), I can not anymore open a gnome session.

Version-Release number of selected component (if applicable):
Every versions availables with fedora 26

How reproducible:

Steps to Reproduce:
1.Install xguest package or map a user to another X SELinux user (and set a password):
dnf install xguest
or useradd -Z user_u username && passwd username
2.Then try to open a gnome session :
open a gnome session for the created user

Actual results:
After trying to open the session, gnome returns to the initial login window.

Expected results:
Open a gnome session in a confined environment.

Additional info:
Same results with fedora 27

Comment 1 Lukas Vrabec 2018-01-04 16:08:01 UTC
What is version of selinux-policy on tested system? 

Could you try it with the latest selinux-policy rpm package? 


Comment 2 Fedora End Of Life 2018-05-03 09:10:30 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 11:36:58 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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

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.