Bug 1242861
| Summary: | enterprise user is not logged in after creation in g-i-s | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vladimir Benes <vbenes> |
| Component: | gnome-initial-setup | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | rstrode |
| Target Milestone: | rc | ||
| Target Release: | 7.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gnome-initial-setup-3.14.4-5.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 08:28:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vladimir Benes
2015-07-14 09:39:07 UTC
so the issue is not the directory creation as if directory exists g-i-s doesn't log the user anyway. after logging in yelp with getting started should be started not gnome-initial-setup as it's now. the reason that gnome-initial-setup gets started again after login is that the copying of saved data from gnome-initial-setup to the account failed - that would have put in place ~/.config/gnome-initial-setup-done, which is the marker to tell us we don't need to run it in the session. i have a patch for this, but it still needs a little more work before it's ready (In reply to Ray Strode [halfline] from comment #5) > i have a patch for this, but it still needs a little more work before it's > ready Very well, Ray! It's fixed! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2157.html |