Bug 445303 - No rhgb the first boot after install
Summary: No rhgb the first boot after install
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-xtrans-devel   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: F9Blocker
TreeView+ depends on / blocked
 
Reported: 2008-05-06 02:06 UTC by Jesse Keating
Modified: 2013-01-10 03:20 UTC (History)
3 users (show)

Fixed In Version: xorg-x11-server-Xorg-1.4.99.901-29.20080415.fc9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-05-07 20:40:26 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jesse Keating 2008-05-06 02:06:38 UTC
For some inexplicable reason I don't get rhgb the first time I do an install,
regardless of install type or source.  There are no files left in /etc/gdm/temp
that might explain what happens.  Subsequent reboots has rhgb launching without
a hitch.

I don't yet know what is the source, so I'm filing this bug to get it tracked at
least.

Comment 1 Jeremy Katz 2008-05-06 14:30:35 UTC
Any avcs?  Try before rebooting chrooting and loading the policy which shows all
the dontaudit'd messages (which I don't remember off hand).  Could be that rhgb
is trying to create something, being denied by selinux and then on subsequent
boots, it's already been created.

Although I have seen rhgb on live boots (not in kvm but that's a known bug --
but it means I can't verify right now) which makes this a little odd.

Comment 2 Jeremy Katz 2008-05-06 18:22:40 UTC
Bill found it and is building fixed xorg-x11-xtrans-devel (and rebuilding the
xserver against that)

Comment 3 Will Woods 2008-05-07 20:40:26 UTC
Verified fixed.


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