[valtam]

* Time & Date post: https://dfgkh547-jsdfv8.iyhkj.tk/forums/showt...p?tid=9689

I've responded to your thread.

[valtam]

Calamares 'Erase disk' option fixed. Timezone sticks after reboot fixed.

Code:

* Fix Erase Disk: add partitionLayout block so Erase creates a root
    partition (previously only a swap partition was created, causing
    rsync code 11 / grub-install failures on install).
  * Add requiredStorageGiB=12.0 to partition.conf so the storage
    requirement is gated correctly.
  * Add welcome.conf with storage/RAM/root requirements; disable the
    Linux Lite Support / Known Issues / Release Notes URL buttons (root
    has no MIME associations under pkexec, xdg-open fails I/O).
  * Increase installer window height (520 -> 640 px).
  * Fix timezone not being written to target on first boot. localecfg
    only writes locale files, so the user's chosen tz from the Location
    step never reached the install. Added the locale viewmodule to the
    exec sequence so its built-in SetTimezoneJob writes /etc/localtime
    and /etc/timezone in the target chroot.

Please - download the new Calamares and install BEFORE you run the installer.

https://repo.linuxliteos.com/linuxlite/p..._amd64.deb

then:

Code:

sudo dpkg -i *.deb

Run the installer.

[valtam]

I'm going to create a Time and Date application to replace gnome-system-tools that uses the new timedatectl commands, wrap it in a easy to use UI.

[valtam]

Code:

sudo apt-get update && sudo apt-get install lite-time-date

[stevef]

I'm going backwards.  Went to try the calamares patch, but now having network problems on live boot.
The odd thing is that I seem to recall my earlier attempts to install had networking without any issues.

Trying to diagnose, but running into issues.
The GUI doesn't show any interfaces when running the 'Network Connections' app.

When running 'ip link', the system reports both the physical ethernet and wifi interfaces are 'DOWN'

If I run 'ip link set xxxxx up
a) the ethernet shows UP (if there is a cable connected) but doesn't run DHCP.
b) the wifi adaptor just shows DOWN.

I tried running nmcli which works on 7.8, but the system reports.

Code:

Error: NetworkManager is not running.

Has anything changed with network management in 8.0 ?
Thanks.


edit - got an interface working by manually editing this file
/etc/netplan/00-installer-config.yaml

Not sure what is happening though.

[stevef]

Completed an install using the calamares patch - thank you.

Minor cosmetic issue.
Lite Core - removed applications remain in the list of applications presented for potential removal.
While the removed apps aren't selectable it just seems odd to see them. Compare with Lite Software behaviour which moves applications between the 'Install' and 'Remove' lists depending on the state.

[valtam]

I'm going backwards.  Went to try the calamares patch, but now having network problems on live boot.
The odd thing is that I seem to recall my earlier attempts to install had networking without any issues.

Trying to diagnose, but running into issues.
The GUI doesn't show any interfaces when running the 'Network Connections' app.

When running 'ip link', the system reports both the physical ethernet and wifi interfaces are 'DOWN'

If I run 'ip link set xxxxx up
a) the ethernet shows UP (if there is a cable connected) but doesn't run DHCP.
b) the wifi adaptor just shows DOWN.

I tried running nmcli which works on 7.8, but the system reports.

Code:

Error: NetworkManager is not running.

Has anything changed with network management in 8.0 ?
Thanks.


edit - got an interface working by manually editing this file
/etc/netplan/00-installer-config.yaml

Not sure what is happening though.

Networking shouldn't need any adjustment.

[valtam]

Completed an install using the calamares patch - thank you.

Minor cosmetic issue.
Lite Core - removed applications remain in the list of applications presented for potential removal.
While the removed apps aren't selectable it just seems odd to see them.  Compare with Lite Software behaviour which moves applications between the 'Install' and 'Remove' lists depending on the state.

Calamares - good to hear.

Lite Core - this is deliberate, once app/s have been removed they are labelled as such giving the user peace of mind that the process they chose was executed properly.

[LL-user]

Completed an install using the calamares patch - thank you.

Minor cosmetic issue.
Lite Core - removed applications remain in the list of applications presented for potential removal.
While the removed apps aren't selectable it just seems odd to see them.  Compare with Lite Software behaviour which moves applications between the 'Install' and 'Remove' lists depending on the state.

Which installation mode did you use after booting live system and installing the batch?
No network issues anymore?

[stevef]

Which installation mode did you use after booting live system and installing the batch?
No network issues anymore?

I booted from the live iso, applied the patch to calamares and then began the install.  At the checking system specification for minimum requirements stage, calamares complained about there being no network and seemed to imply the system did not meet minimum requirement.

This led me down the network debugging route.  I still don't know exactly what was going on, but the netplan hack got the system on line.

Once online, the patched calamares install got past the minimum requirement check and installed as expected.
I used the erase disk option (previously the un-patched version gave us the rsync error 11).

Once installed and rebooted, networking has been fine.  Things like nmcli are working as expected.

Lite Core - this is deliberate, once app/s have been removed they are labelled as such giving the user peace of mind that the process they chose was executed properly.

Ah yes sorry. I had missed the '- not installed' text in the list.  Combination of font size/colour and cataracts.

edit
A fresh look at the problem with live boot networking on my particular set-up shows the networkd-dispatcher.service fails with timeout.  This in turn prevents NetworkManager.service from starting.
Once the live boot has completed, it is possible to add networking by manually starting networkd-dispatcher.service, followed by manually starting NetworkManager.service