Created attachment 1757023 [details]
Description of problem:
Looks like GNOME 40 tour is launching on Live boot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot Fedora-Workstation-Live-x86_64-34-20210213.n.0.iso
Welcome to GNOME 40 covers the Welcome to Fedora window, see screenshot
Shouldn't run on Live bot
Bastien, did you do the "Welcome to GNOME 40" dialogue? Can you look into how to disable this on live media, please?
Moving to gnome-shell as this is where the dialog lives.
Can you please file an upstream bug about this?
Feel free to pick up the patch in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1677 if you want to have this fixed ASAP.
Actually, this needs to happen in the kickstart file. This should work:
diff --git a/fedora-live-base.ks b/fedora-live-base.ks
index 3e4ce78..47641bc 100644
@@ -184,6 +184,9 @@ systemctl stop mdmonitor-takeover.service 2> /dev/null || :
# don't enable the gnome-settings-daemon packagekit plugin
gsettings set org.gnome.software download-updates 'false' || :
+# disable welcome tour by passing a huge version number
+gsettings set org.gnome.shell welcome-dialog-last-shown-version '4294967295' || :
# don't start cron/at as they tend to spawn things which are
# disk intensive that are painful on a live image
systemctl --no-reload disable crond.service 2> /dev/null || :
I didn't see this error on the 210211 iso image, but it is on the 210213 and on today's 210215 too.
Hope the fix pointed by @bnocera come in the next iso.
(In reply to Bastien Nocera from comment #5)
> Actually, this needs to happen in the kickstart file. This should work:
> diff --git a/fedora-live-base.ks b/fedora-live-base.ks
> index 3e4ce78..47641bc 100644
> --- a/fedora-live-base.ks
> +++ b/fedora-live-base.ks
> @@ -184,6 +184,9 @@ systemctl stop mdmonitor-takeover.service 2> /dev/null
> || :
> # don't enable the gnome-settings-daemon packagekit plugin
> gsettings set org.gnome.software download-updates 'false' || :
> +# disable welcome tour by passing a huge version number
> +gsettings set org.gnome.shell welcome-dialog-last-shown-version
> '4294967295' || :
> # don't start cron/at as they tend to spawn things which are
> # disk intensive that are painful on a live image
> systemctl --no-reload disable crond.service 2> /dev/null || :
Nice, that sounds like it should work. Can you turn this into a PR against https://pagure.io/fedora-kickstarts.git please?
Sorry, I'm afraid that I don't have the bandwidth for turning it into a PR.
(To be clear, I have the bandwidth for making a PR, I don't have the bandwidth to actually test said change before submitting it)
I think it would be perfectly fine to submit a PR for a simple change like this without testing it in a local compose first.
(In reply to Kalev Lember from comment #10)
> I think it would be perfectly fine to submit a PR for a simple change like
> this without testing it in a local compose first.
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 34 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.
Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
Thank you for reporting this bug and we are sorry it could not be fixed.