With the kde live iso images, drakx-finish-install does not
ask about configuring the network, so the hostname is localhost.
journalctl -a|grep finish|grep network
May 12 16:16:19 localhost finish-install: ignoring ask_network
May 12 16:31:20 localhost finish-install: calling ask_network
May 12 16:32:23 localhost finish-install: running: /bin/systemctl disable network-auth.service
May 12 16:32:23 localhost finish-install: modified file /etc/sysconfig/network
It's working with the gnome live iso images.
The wired ethernet connection is working though.
Steps to Reproduce:
RPM Packages =>
Release (media or process)Version:
*** Bug 11005 has been marked as a duplicate of this bug. ***
Release (media or process) =>
(In reply to Dave Hodgins from comment #1)
> it's working with the gnome live iso images
It is an intermittent problem. I did a gnome VirtualBox install and no network screen, Did a kde VB install and it did have it. Installed KDE on two different systems and it did not have it.
Valid 5beta2 Live ISOs. Noticed on all live isos tried so far not just kde ones.
Wired network, which might explain why it skips it but in doing so it allows nowhere to set the hostname.
Same journal extract as comment 0
kde live installs do not ask for network configuration. =>
live installs do not ask for network configurationSource RPM:
Thierry, Thomas, any idea about this one?
It's by design.
The live medias have been designed to ask as little questions as possible, so if the system detects working network during bootup, it will skip the question.
The real fix would be to move the changing of hostname maybe to the same pages as setting user names or so... but thats a mga6 thing
Thanks, adding to the mga6 tracker.
That would be a good resolution for this yes.
live installs do not ask for network configuration =>
Live Installed system should ask for hostname at the same time it asks for usernameWhiteboard:
Moving to the Mga7 tracker, because afaik there is no action with regard to this issue.
Of course, that doesn't mean it is forbidden to fix it before Mga6 is released ;-)
(In reply to Marja van Waes from comment #8)
> Moving to the Mga7 tracker, because afaik there is no action with regard to
> this issue.
Setting target milestone field to Mageia 7 then.
Mageia 6 =>