Hi folks! So I just spent an hour or two debugging an unexpected change in behaviour in the openQA base images. I've figured out what's going on, but I'm unsure if it's intended.
There was a change to anaconda between Fedora 25 and Fedora 26 which causes it to write a line:
post_install_tools_disabled=1
to /etc/sysconfig/anaconda for all kickstarted installs where there is no explicit 'firstboot' directive in the kickstart. (Prior to Fedora 26, anaconda would disable 'initial-setup.service' by default for kickstarted installs, but it didn't write that line, or disable gnome- initial-setup - either mode - in any way.)
It seems that gnome-initial-setup reads that file on startup, and if it sees that post_install_tools_disabled is set, it will kinda short- circuit - it won't display its UI at all, it'll just do its shutdown tasks (create ~/.config/gnome-initial-setup-done and so on) and then quit. It doesn't only do this in its system-wide, 'run before gdm if no user accounts exist' mode - it also does it when running in its 'first login to GNOME as any user' mode.
So an effect of this change - which may not have been intended - is that on most kickstarted installs of Fedora 26+, gnome-initial-setup does not run *even in 'first login to a user account' mode*. (This is the change that affected openQA). I can't immediately see that it makes logical sense to disable this g-i-s mode on kickstarted installs by default, but maybe someone disagrees.
Anyway, just wanted to raise this issue for discussion between desktop and anaconda folks (who are CCed on this), before filing bugs anywhere. Thanks!
Hi,
On Sat, Oct 21, 2017 at 2:30 AM, Adam Williamson adamwill@fedoraproject.org wrote:
There was a change to anaconda between Fedora 25 and Fedora 26 which causes it to write a line:
post_install_tools_disabled=1
Right, the gdm/gnome-initial-setup behavior of not doing anything if anaconda writes this out is very much on purpose, including in existing user mode as you noticed. The rational AFAICT is that sysadmins want an automated, sure-fire way to disable *any* kind of initial setup.
to /etc/sysconfig/anaconda for all kickstarted installs where there is no explicit 'firstboot' directive in the kickstart.
Now this I'm not so sure of but I'll defer to the anaconda folks. I'll say that when I was doing the above changes to gdm/g-i-s I was under the assumption that firstboot was enabled by default. You're asserting that firstboot is now disabled by default which is a substantial behavior change indeed.
Rui
A related issue: when installing *without* kickstart (just plain anaconda) F27 beta I was first asked about the keyboard layout in anaconda, and made my choices there, and then g-i-s insisted on asking the same questions again starting from scratch. This is especially annoying because g-i-s ignored previous setup, and doesn't have a quit button or a skip button, so unless I picked the keyboard layouts again, it would just undo my changes.
Not sure how much of this is intended, but it feels like a regression from F26.
Zbyszek
On Sat, Oct 21, 2017 at 07:26:02PM +0200, Rui Tiago Cação Matos wrote:
Hi,
On Sat, Oct 21, 2017 at 2:30 AM, Adam Williamson adamwill@fedoraproject.org wrote:
There was a change to anaconda between Fedora 25 and Fedora 26 which causes it to write a line:
post_install_tools_disabled=1
Right, the gdm/gnome-initial-setup behavior of not doing anything if anaconda writes this out is very much on purpose, including in existing user mode as you noticed. The rational AFAICT is that sysadmins want an automated, sure-fire way to disable *any* kind of initial setup.
to /etc/sysconfig/anaconda for all kickstarted installs where there is no explicit 'firstboot' directive in the kickstart.
Now this I'm not so sure of but I'll defer to the anaconda folks. I'll say that when I was doing the above changes to gdm/g-i-s I was under the assumption that firstboot was enabled by default. You're asserting that firstboot is now disabled by default which is a substantial behavior change indeed.
Rui _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
On Mon, Oct 23, 2017 at 3:04 AM, Zbigniew Jędrzejewski-Szmek zbyszek@in.waw.pl wrote:
Not sure how much of this is intended, but it feels like a regression from F26.
It's always done that, see https://fedoraproject.org/wiki/Changes/ReduceInitialSetupRedundancy
I don't know if I'll have time to return to this project soon... hopefully.
Michael
On Sat, 2017-10-21 at 19:26 +0200, Rui Tiago Cação Matos wrote:
to /etc/sysconfig/anaconda for all kickstarted installs where there is no explicit 'firstboot' directive in the kickstart.
Now this I'm not so sure of but I'll defer to the anaconda folks. I'll say that when I was doing the above changes to gdm/g-i-s I was under the assumption that firstboot was enabled by default. You're asserting that firstboot is now disabled by default which is a substantial behavior change indeed.
Note we're talking *only about kickstarted installs* here. But yes, the change in F26 is that the /etc/sysconfig/anaconda setting gets set to 0 by default for kickstart installs, whereas it did not before.
On Mon, Oct 23, 2017 at 09:09:02AM -0700, Adam Williamson wrote:
Note we're talking *only about kickstarted installs* here. But yes, the change in F26 is that the /etc/sysconfig/anaconda setting gets set to 0 by default for kickstart installs, whereas it did not before.
At the very least, this should go in the release notes.
On Mon, 2017-10-23 at 12:26 -0400, Matthew Miller wrote:
On Mon, Oct 23, 2017 at 09:09:02AM -0700, Adam Williamson wrote:
Note we're talking *only about kickstarted installs* here. But yes, the change in F26 is that the /etc/sysconfig/anaconda setting gets set to 0 by default for kickstart installs, whereas it did not before.
At the very least, this should go in the release notes.
It changed in *F26*. Those release notes are sort of done now. :P
desktop@lists.stg.fedoraproject.org