Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1815787 - I get a new setup for every login
Summary: I get a new setup for every login
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-initial-setup
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Rui Matos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F32FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2020-03-21 18:05 UTC by Andreas Tunek
Modified: 2020-03-23 10:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-23 10:56:58 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Andreas Tunek 2020-03-21 18:05:45 UTC 
Description of problem:
Every time I log in I get a new popup of gnome-initial-setup. It doesn't seem to remember what I entered. Happened in Beta and latest compose.

Version-Release number of selected component (if applicable):
Beta and Fedora-Workstation-Live-x86_64-32-20200321.n.0 compose.

How reproducible:
Always.

Steps to Reproduce:
1. Log in.
2. gnome-initial-setup pops up. I enter info.
3. Log out and log in again. gnome-initial-setup pops up again.

Additional info:
I did fresh installs of both Beta and 20200321.
Comment 1 Fedora Blocker Bugs Application 2020-03-21 18:11:08 UTC 
Proposed as a Blocker for 32-final by Fedora user tuna using the blocker tracking app because:

 Really bad user experience.

(Wrong bug in previous entry, sorry.)
Comment 2 Andreas Tunek 2020-03-23 09:51:26 UTC 
This seems to be hardware dependent, I tested on another computer and there it works as it should. I will try to reinstall again.
Comment 3 Andreas Tunek 2020-03-23 10:56:11 UTC 
I made a new install on the same hardware without LVM, and then everything seems to work. So it is not a problem with this component.
Note You need to log in before you can comment on or make changes to this bug.