Bug 381831 - prefdm seems to fail?
prefdm seems to fail?
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-14 04:01 EST by Jens Petersen
Modified: 2008-02-06 18:33 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-06 18:33:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jens Petersen 2007-11-14 04:01:45 EST
Description of problem:
Not quite sure what the issue is, but in rawhide prefdm seems to be failing
now.  Maybe it is not initscripts fault, since it is unchanged from f8?
So may be related to the new gdm?

This is also causing prefdm to spawn too quickly at runlevel 5.

How reproducible:
every time

Steps to Reproduce:
1. Run prefdm from console
  
Actual results:
nothing

Expected results:
prefdm to start gdm

Additional info:
Funnily enough if I add "set -x" to the prefdm script it seems to work for me??
Comment 1 Bill Nottingham 2007-11-14 12:04:35 EST
Does it work with non-gdm display managers?
Comment 2 Bill Nottingham 2007-11-14 13:49:07 EST
It's gdm. Disabling SELinux lets it get a bit further.
Comment 3 Felix Bellaby 2007-11-22 18:59:01 EST
Part of this problem seems to come from the selinux context on /etc/X11/prefdm

/sbin/init has context init_exec_t
/etc/X11/prefdm has context initrc_exec_t
/usr/sbin/gdm has context xdm_exec_t

selinux allows a transition from init_ext_t -> xdm_exec_t

However it prevents a transition from initrc_exec_t -> xdm_exec_t

If you change the context of prefdm to xdm_exec_t or init_exec_t then you can at
least start gdm using prefdm.
Comment 4 Jens Petersen 2008-02-06 18:33:24 EST
This has been fixed now for quite a while.

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