FEDORA-2023-0b23a44f44 — unspecified update for gnome-initial-setup

obsolete

gnome-initial-setup-45.0-2.fc40

FEDORA-2023-0b23a44f44 created by catanzaro a year ago for Fedora 40

Automatic update for gnome-initial-setup-45.0-2.fc40.

Changelog

* Tue Sep 19 2023 Michael Catanzaro <mcatanzaro@redhat.com> - 45.0-2
- Update to 45.0 and refresh live user mode patchset
* Tue Sep 19 2023 Michael Catanzaro <mcatanzaro@redhat.com> - 45.0-1
- Update to 45.0

This update was automatically created

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'failed'.

a year ago

adamwill commented a year ago

Looks like handoff from g-i-s to a logged-in desktop fails - after we enter a password for the user and proceed, the system just gets stuck showing a background and incomplete top bar.

The journal shows this stuff which may be the issue:

Sep 19 13:13:37 fedora accounts-daemon[800]: request by system-bus-name::1.77 [/usr/libexec/gnome-initial-setup pid:1538 uid:981]: create user 'test'
Sep 19 13:13:37 fedora useradd[1791]: new group: name=test, GID=1000
Sep 19 13:13:37 fedora useradd[1791]: new user: name=test, UID=1000, GID=1000, home=/home/test, shell=/bin/bash, from=none
Sep 19 13:13:37 fedora useradd[1791]: add 'test' to group 'wheel'
Sep 19 13:13:37 fedora useradd[1791]: add 'test' to shadow group 'wheel'
Sep 19 13:13:37 fedora accounts-daemon[1794]: [sss_cache] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb]
Sep 19 13:13:37 fedora accounts-daemon[1794]: Could not open available domains
Sep 19 13:13:37 fedora useradd[1791]: useradd: sss_cache exited with status 5
Sep 19 13:13:37 fedora useradd[1791]: useradd: Failed to flush the sssd cache.
Sep 19 13:13:37 fedora accounts-daemon[1797]: [sss_cache] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb]
Sep 19 13:13:37 fedora accounts-daemon[1797]: Could not open available domains
Sep 19 13:13:37 fedora useradd[1791]: useradd: sss_cache exited with status 5
Sep 19 13:13:37 fedora useradd[1791]: useradd: Failed to flush the sssd cache.
Sep 19 13:13:38 fedora accounts-daemon[800]: request by system-bus-name::1.77 [/usr/libexec/gnome-initial-setup pid:1538 uid:981]: set password and hint of user 'test' (1000)
Sep 19 13:13:38 fedora accounts-daemon[1807]: [sss_cache] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb]
Sep 19 13:13:38 fedora accounts-daemon[1807]: Could not open available domains
Sep 19 13:13:38 fedora chpasswd[1803]: chpasswd: sss_cache exited with status 5
Sep 19 13:13:38 fedora chpasswd[1803]: chpasswd: Failed to flush the sssd cache.
Sep 19 13:13:38 fedora accounts-daemon[1809]: [sss_cache] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb]
Sep 19 13:13:38 fedora accounts-daemon[1809]: Could not open available domains
Sep 19 13:13:38 fedora chpasswd[1803]: chpasswd: sss_cache exited with status 5
Sep 19 13:13:38 fedora chpasswd[1803]: chpasswd: Failed to flush the sssd cache.
Sep 19 13:13:38 fedora gnome-initial-s[1538]: act_user_get_uid: assertion 'ACT_IS_USER (user)' failed
Sep 19 13:13:38 fedora gnome-initial-s[1538]: act_user_get_user_name: assertion 'ACT_IS_USER (user)' failed
Sep 19 13:13:38 fedora gnome-initial-s[1538]: g_variant_new_string: assertion 'string != NULL' failed
Sep 19 13:13:38 fedora gdm-password][1810]: accountsservice: ActUserManager: user (null) has no username (uid: -1)

This update has been obsoleted by gnome-initial-setup-45.0-3.fc40.

a year ago

Please log in to add feedback.

Metadata

Type

unspecified

Karma

Signed

Content Type

RPM

Test Gating

failed

Autopush Settings

Unstable by Karma

-3

Stable by Karma

disabled

Stable by Time

0 days

Thresholds

Minimum Karma

Minimum Testing

14 days

Dates

submitted

a year ago

in testing

a year ago

Builds

gnome-initial-setup-45.0-2.fc40

Automated Test Results

For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.

failed