Bug 1750237 - g-i-s window overlapped with gdm login screen
Summary: g-i-s window overlapped with gdm login screen
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-initial-setup
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rui Matos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F31BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2019-09-09 06:36 UTC by Parag Nemade
Modified: 2019-09-11 01:30 UTC (History)
8 users (show)

Fixed In Version: gnome-initial-setup-3.34.0-2.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-11 01:30:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
gdm screen appearing with g-i-s window (256.43 KB, image/png)
2019-09-09 06:36 UTC, Parag Nemade
no flags Details

Description Parag Nemade 2019-09-09 06:36:32 UTC
Created attachment 1612988 [details]
gdm screen appearing with g-i-s window

Description of problem:
Since updated to gnome-initial-setup-3.33.92-2 build, when I boot machine and gets gdm login screen, there appears also gnome-initial-setup screen in minimal size. See attached screenshot.

Version-Release number of selected component (if applicable):
gnome-initial-setup-3.33.92-2.fc31 

How reproducible:
always

Steps to Reproduce:
1. just update F31 WS/SB to latest updates including Gnome Megaupdate as well and reboot or logout and login
2. at the gdm screen, you will see g-i-s window
3.

Actual results:
showing g-i-s window

Expected results:
should not show g-i-s window

Additional info:

Comment 1 Fedora Blocker Bugs Application 2019-09-09 06:42:46 UTC
Proposed as a Freeze Exception for 31-beta by Fedora user pnemade using the blocker tracking app because:

 Not tried with fresh installation but with the existing installation carried with upgrades occasionally, today I found at the gdm login screen, gnome-initial-setup window is appearing which may confuse end users like whether to click on next button or continue with gdm login. I reproduced this bug with F32 rawhide and F31 Silverblue systems.

Comment 2 Kalev Lember 2019-09-09 15:05:26 UTC
Benjamin, any ideas what's going wrong here?

Comment 3 Benjamin Berg 2019-09-09 15:24:29 UTC
Oh, uhm, right …

could you try adding:

Conflicts=gnome-session

into gnome-initial-setup-first-login.service?

Comment 4 Geoffrey Marr 2019-09-09 19:49:45 UTC
Discussed during the 2019-09-09 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedFreezeException" was made as while the contexts in which this might happen are a bit unclear, we think it can happen on upgrade and on first boot after install, so on that basis a freeze exception is justified as those cannot be fully addressed with a 0-day update.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-09-09/f31-blocker-review.2019-09-09-16.00.txt

Comment 5 Fedora Update System 2019-09-09 22:19:42 UTC
FEDORA-2019-c11489c6b5 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c11489c6b5

Comment 6 Fedora Update System 2019-09-09 23:16:15 UTC
gnome-initial-setup-3.34.0-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c11489c6b5

Comment 7 Fedora Update System 2019-09-11 01:30:29 UTC
gnome-initial-setup-3.34.0-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.


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