Bug 1009833

note, I have a display attached direct to the Trimslice via HDMI, I am not using serial console.

tflink reports that it works fine if you have a serial console. I'd expect that it ought to work without one, but perhaps it never has and we're kinda expecting that people will have one?

And it works if you try it in qemu (no graphics mode).

Adam I agree, ideally it would detect if a display is connected and do the right thing, however to date the expectation is initial-setup-text is run on serial console.

Discussed this in the F20 Alpha Go/No-Go meeting [1]. While unfortunate, initial-setup appearing only on the serial console is expected behavior and thus, this bug is rejected as a blocker for F20 alpha. However, it should be documented in some combination of release notes and commonbugs

[1] http://meetbot.fedoraproject.org/fedora-meeting-2/2013-09-19/

Initial Setup doesn't tell anybody where it should run. There is just a fallback causing the text version to be run if the graphical version fails to run. Nothing else. systemd decides where the boot process (including initial-setup) runs.

Do you have 'console=ttyS0' or something like that as a boot option?

I'm using the stock ARM image with no modifications. I don't know the boot arguments off the top of my head, and I think I overwrote the USB stick now, so I'd have to write it again to check, I'll try and do that soon.

I'm sorry, but I have no idea what's going on here and I have no way to debug it. Could you please attach the output of 'journactl -u initial-setup-text.service'? Maybe that will tell us something.

Not easily, no. I have no way to access the system when it is in the error condition. I suppose I could try and pre-hack the USB key so the root account is accessible on it, or something.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.