Release | Endless OS 3.8.4

Endless OS 3.8.4 was released for existing users today, July 6th, 2020.
Downloadable images for new users will be available in the next few days.

Live + Installer USB now working again

On Endless 3.8.0 a problem was introduced on installer USB devices created with our Endless Installer for Windows. These devices can be used to try Endless on a live boot, but the actual installation process would fail. This is now fixed with Endless OS 3.8.4 images (you should not need to download a new Endless Installer for Windows, as the problem was in the actual OS image, not in the installer tool), where these USB devices can be used both for trying Endless OS live and for installing it.

We know our images are large, take a long time to download and may have consumed some of the data allowance from your internet plan. If you have already downloaded a version of Endless OS between 3.8.0 and 3.8.3, you can install it using the alternative method described on this FAQ entry.

Other Improvements and Changes

  • We’ve updated to Chromium 83.0.4103.116 bringing new improvements and security fixes to Endless’ built-in web browser.
  • Sometimes unlocking the screen would show a “No apps are open” dialog or restore the last minimized application. This is now fixed.
  • Dragging icons outside application folders in the desktop should now work as expected.
  • The desktop was updated to fix an issue with some translations not getting applied correctly.
  • The App Center was updated to fix a potential crash when the local flatpak storage is corrupted.
  • Non-administrator users should now be able to modify metrics settings on Settings > Privacy > Metrics by authenticating with an administrator account when requested.
  • The scanner driver libraries were updated to add support for a number of scanner models.
  • Users who have installed Firefox from Endless’ app repository will be migrated to the official Mozilla version on Flathub.
  • The Kolibri application is now pre-installed on new OS installations.
3 Likes

Hi, there is a bug with new update, Hot Corner now move all windows to right down, they are not centered anymore.

1 Like

3 posts were split to a new topic: Missing tray icons

Thanks for the report – we believe this will be fixed in GNOME 3.38 / Endless OS 3.9 in November, but unfortunately the relevant change cannot easily be applied to the Endless OS 3.8 series.

Hi!
I am stuck with 3.8.0. No update shows for months in App Center and
eos-updater-ctl update returns
FullDownloadSize: int64 0
FullUnpackedSize: int64 0
OriginalRefspec: ‘’
UnpackedSize: int64 0
UpdateID: ‘’
UpdateLabel: ‘’
UpdateMessage: ‘’
UpdateRefspec: ‘’
Version: ‘’

Traceback (most recent call last):
File “/usr/bin/eos-updater-ctl”, line 409, in
main()
File “/usr/bin/eos-updater-ctl”, line 405, in main
sys.exit(args.function(**args_dict))
File “/usr/bin/eos-updater-ctl”, line 209, in command_update
force=force, timeout=timeout)
File “/usr/bin/eos-updater-ctl”, line 191, in command_fetch
return command_dbus(‘fetch’, block, quiet, parameters)
File “/usr/bin/eos-updater-ctl”, line 159, in command_dbus
proxy.call_sync(qualified_method_name, parameters, 0, -1, None)
gi.repository.GLib.Error: g-io-error-quark: GDBus.Error:com.endlessm.Updater.Error.WrongState: Can’t call Fetch() while in state Ready (36)

Seems like this release might have a solution to my Mozilla Firefox problem, but how do I get it?

try:

  1. Open a Terminal
  2. Type:
sudo ostree admin upgrade
  1. Reboot

**
OSTree:ERROR:src/libostree/ostree-repo-pull.c:1854:scan_commit_object: assertion failed: (ref)
Bail out! OSTree:ERROR:src/libostree/ostree-repo-pull.c:1854:scan_commit_object: assertion failed: (ref)
Aborted

Please run:

rm -f eos-fix-ostree-repo
wget https://raw.githubusercontent.com/endlessm/eos-meta/master/eos-tech-support/eos-fix-ostree-repo
chmod +x eos-fix-ostree-repo
sudo ./eos-fix-ostree-repo

After that, reboot your system and run eos-updater-ctl update again.

after doing it, returns the same as in my first post.

can you please provide us with a diagnostic for further analysis

eos-diagnostics

… and then upload the generated file here.

eos-diagnostic-200806_190251_UTC.txt (897.2 KB)

Ok, two things to try:

  1. Boot into 3.7.8 using the Boot Menu (hold Shift during boot), then try to update using the command line as you did before.

If this does not work too, please:

  1. Open a Terminal and run:
journalctl -f -u eos-updater | tee ~/updater.log
  1. Open another Terminal and run:
eos-updater update --force

After it fails as previously, upload the updater.log file here.

updater.log (807 Bytes)

Interesting. Are there more messages in the window where journalctl is running. There should be log messages like:

-- Logs begin at Tue 2020-08-04 21:06:53 CEST. --
Aug 06 18:11:06 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 18:11:06 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 18:11:07 endless eos-updater[4959]: libostree pull from 'eos' for os/eos/amd64/eos3a complete
                                           security: GPG: commit http: TLS
                                           non-delta: meta: 1 content: 0
                                           transfer: secs: 0 size: 1.1 kB
Aug 06 18:11:07 endless eos-updater[4959]: Poll: Couldn’t find any updates
Aug 06 18:11:07 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 18:11:08 endless eos-updater[4959]: libostree pull from 'eos' for os/eos/amd64/eos3a complete
                                           security: GPG: commit http: TLS
                                           non-delta: meta: 1 content: 0
                                           transfer: secs: 0 size: 1.1 kB
Aug 06 18:11:08 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 18:11:08 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 18:11:08 endless eos-updater[4959]: libostree pull from 'eos' for os/eos/amd64/eos3a complete
                                           security: GPG: commit http: TLS
                                           non-delta: meta: 1 content: 0
                                           transfer: secs: 0 size: 1.1 kB
Aug 06 18:11:08 endless eos-updater[4959]: Changing to state Ready

Now when i executed eos-updater in another window, the following log messags were appended:

Aug 06 20:35:42 endless eos-updater[4959]: Changing to state Polling
Aug 06 20:35:42 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:42 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:42 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:42 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:44 endless eos-updater[4959]: libostree pull from 'eos' for os/eos/amd64/eos3a complete
                                           security: GPG: commit http: TLS
                                           non-delta: meta: 1 content: 0
                                           transfer: secs: 0 size: 1.1 kB
Aug 06 20:35:44 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:44 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:45 endless eos-updater[4959]: libostree pull from 'eos' for os/eos/amd64/eos3a complete
                                           security: GPG: commit http: TLS
                                           non-delta: meta: 1 content: 0
                                           transfer: secs: 0 size: 1.1 kB
Aug 06 20:35:45 endless eos-updater[4959]: Poll: Couldn’t find any updates
Aug 06 20:35:45 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:46 endless eos-updater[4959]: libostree pull from 'eos' for os/eos/amd64/eos3a complete
                                           security: GPG: commit http: TLS
                                           non-delta: meta: 1 content: 0
                                           transfer: secs: 0 size: 1.1 kB
Aug 06 20:35:46 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:46 endless eos-updater[4959]: Using product branch os/eos/amd64/eos3a
Aug 06 20:35:46 endless eos-updater[4959]: libostree pull from 'eos' for os/eos/amd64/eos3a complete
                                           security: GPG: commit http: TLS
                                           non-delta: meta: 1 content: 0
                                           transfer: secs: 0 size: 1.1 kB
Aug 06 20:35:46 endless eos-updater[4959]: Changing to state Ready

bash: eos-updater: command not found

I figured it out. Wrong command. Here is the new
updater.log (2.7 KB)

Open a Terminal, then run:

sudo ostree admin deploy eos:os/eos/amd64/eos3a

Now reboot, then try to update again

error: Refspec ‘eos:os/eos/amd64/eos3a’ not found

There’s something seriously broken here on your system. Can you please run:

cat /ostree/deploy/eos/deploy/$(ostree admin status | grep \* | awk '{print $3}').origin

and verify that it contains:

[origin]
refspec=eos:os/eos/amd64/eos3a

[origin]
refspec=eos:dd7c0a54a0c6303e7eea425dd4e11cf37ebb99ed55d84881ce8308a950fc28ee

OK this seems to be the root cause. The updater looks for a refspec of eos:os/eos/amd64/eos3a for the update. Fix it with:

sudo ostree admin set-origin eos https://ostree.endlessm.com/ostree/eos-amd64 os/eos/amd64/eos3a --index=0

Then, reboot and try to update again.

3 Likes