VLC player not loading

#34

The system won’t let me post the diagnostics file you requested. I have had several “Post hidden by community flags,” already. I can only guess it because the system is doing this because I started the post as @Linux1 but was not allowed to post replies as that user, so I am using @newbie
Anyways, thanks for all your help so far. :smile:

"Your post was flagged as spam : the community feels it is an advertisement, something that is overly promotional in nature instead of being useful or relevant to the topic as expected.

Multiple community members flagged this post before it was hidden,…"

How can a diagnostic file be spam? Please check everything on both accounts and you will find that I haven’t done anything wrong.

#35

Post it to https://pastebin.com/ in the meantime (and provide the link here), so that we can continue to investigate in your issue :slight_smile:

#36

eos-diagnostic-190516_120637_UTC 0800.txt (262.8 KB)

#37

I can reply again on @Linux1

#38

@wjt
Could this have something to do with the Signing Key used for the OSTree Updates?

=================
= OSTree status =
=================
* eos 7083275ee04acaf9f19fc070df8132861acb8171d18e2587efbfc06bca7f5ef7.0
    origin refspec: eos:os/eos/amd64/eos3
    GPG: Signature made Wed 13 Jun 2018 08:35:52 AM +08 using RSA key ID 9E08D8DABA02FC46
    GPG: BAD signature from "EOS OSTree Signing Key 1 <maintainers@endlessm.com>"
  eos 9c37aaeaf98a3777a05c522d3a6470796fafe04221b2f1b37a1ae224395057c2.0 (rollback)
    origin refspec: eos:os/eos/amd64/eos3
    GPG: Signature made Sat 05 Aug 2017 05:25:58 AM +08 using RSA key ID 9E08D8DABA02FC46
    GPG: BAD signature from "EOS OSTree Signing Key 1 <maintainers@endlessm.com>"

According to the GPG Information for the used Key, it’s expired:

egon@endless:~/tmp/eos-keyring/keys/signing$ gpg --import EOSK1.pub 
gpg: /sysroot/home/egon/.gnupg/trustdb.gpg: trustdb created
gpg: key 9E08D8DABA02FC46: public key "EOS OSTree Signing Key 1 (EOSK1) <maintainers@endlessm.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: no ultimately trusted keys found

egon@endless:~/tmp/eos-keyring/keys/signing$ gpg --list-keys  --verbose
gpg: using pgp trust model
gpg: Note: signature key 9E08D8DABA02FC46 expired Mon 13 May 2019 08:51:20 PM CEST
/sysroot/home/egon/.gnupg/pubring.kbx
-------------------------------------
pub   rsa4096 2014-05-14 [SC] [expired: 2019-05-13]
      63C3FCD3C48FBF116A2F4ACC9E08D8DABA02FC46
uid           [ expired] EOS OSTree Signing Key 1 (EOSK1) <maintainers@endlessm.com>
sub   rsa4096 2014-05-14 [E] [expired: 2019-05-13]

The Key expired on 13th of May this Year.

I installed the earliest EOS Version if have in a virtual machine (3.5.6) and tried updating it to 3.5.8. Whenever i instruct the updater to check for new updates with eos-updater-ctl poll, in the Log for the eos-updater the following line appears:

May 16 13:12:07 endless eos-updater[1629]: Failed to poll metadata from source main: Commit 5c046e257c68118a231396f56d5d1e23c47c7201072a72b280b798345c974e9c: GPG signatures found, but none are in trusted keyring

The above error also is a strong indication that there is some problem with the certificate, as the update could not be verified.

#39

@mwleeds Could it help?

#40

As of a couple days ago, the commits (both for OS updates and flatpak updates) being served are signed with the flatpak keyring which has not expired. I also just was able to update a VM of 3.5.6 to 3.5.8. @egrath can you reboot and try again to update?

#41

I’m just downloading a few of the older EOS releases, to see if they update to the latest version without any problems now. Will post the results here.

#42

Just finished testing 3.5.6

  • Downloaded 3.5.6 via Torrent (eos-eos3.5-amd64-amd64.190212-145424.base.iso)
  • Installed in GNOME Boxes

After the installation finished and rebootet, i saw the Update once:

Screenshot%20from%202019-05-17%2009-54-52
Screenshot from 2019-05-17 09-54-52.png801×413 28.6 KB

After installation and a reboot, the system is still at 3.5.6 and the update no longer show up as available. When doing a manual flatpak update --appstream -y i get the following output, which indicates some problem:

Updating appstream data for remote eos-apps
Updating appstream data for remote eos-runtimes
Error updating: Error updating appstream2: Commit 152606ed8975d1cb3009fe15ac4d125fa2d80e03b906f4c3d4319679c70c9995: GPG signatures found, but none are in trusted keyring; Error updating appstream: Commit 4444ec74ff3aa481b96866bfebac123b708bb7f893253466985dc9ada77f24e4: GPG signatures found, but none are in trusted keyring
Updating appstream data for remote eos-sdk
Updating appstream data for remote flathub

How did you update your 3.5.6? gnome-software or commandline (if commandline, which commands)

Result for 3.3.16

Downloaded 3.3.16 via Torrent, fresh install on VM. Updated all available Updates from App Center, no more updates available. Still at 3.3.16.

Tried also:

root@endless:~# flatpak update --appstream -y
Updating appstream for remote eos-apps
[####################] 3 metadata, 0 content objects fetched; 569 B transferred in 0 seconds
Updating appstream for remote eos-runtimes
Error updating: Commit 4444ec74ff3aa481b96866bfebac123b708bb7f893253466985dc9ada77f24e4: GPG signatures found, but none are in trusted keyring
Updating appstream for remote eos-sdk
[####################] 3 metadata, 0 content objects fetched; 569 B transferred in 0 seconds
Updating appstream for remote flathub
[####################] 1 delta parts, 1 loose fetched

and

root@endless:~# eos-updater-ctl update
Changed state to Polling
Changed state to Ready
======= Properties =======
State: Polling
 CurrentID: '9f280efd9133212df279653067875881ace96dde7e76fa75c94f1cff7a1316b3'
 DownloadSize: int64 0
 DownloadedBytes: int64 0
 ErrorCode: uint32 0
 ErrorMessage: ''
 ErrorName: ''
 FullDownloadSize: int64 0
 FullUnpackedSize: int64 0
 OriginalRefspec: ''
 UnpackedSize: int64 0
 UpdateID: ''
 UpdateLabel: ''
 UpdateMessage: ''
 UpdateRefspec: ''

Traceback (most recent call last):
  File "/usr/bin/eos-updater-ctl", line 355, in <module>
    main()
  File "/usr/bin/eos-updater-ctl", line 351, in main
    sys.exit(args.function(**args_dict))
  File "/usr/bin/eos-updater-ctl", line 186, in command_update
    fetch_result = command_fetch(block=True, quiet=quiet)
  File "/usr/bin/eos-updater-ctl", line 173, in command_fetch
    return command_dbus('fetch', block, quiet)
  File "/usr/bin/eos-updater-ctl", line 145, in command_dbus
    proxy.call_sync('com.endlessm.Updater.' + function_name, None, 0, -1, None)
GLib.Error: g-io-error-quark: GDBus.Error:com.endlessm.Updater.Error.WrongState: Can't call Fetch() while in state Ready (36)

This also generates the following log entry:

May 17 12:47:39 endless eos-updater[1573]: Changing to state Polling
May 17 12:47:39 endless eos-updater[1573]: Using product branch os/eos/amd64/eos3
May 17 12:47:40 endless eos-updater[1573]: libostree HTTP error from remote eos for <https://ostree.endlessm.com/ostree/eos-amd64/objects/70/83275ee04acaf9f19fc070df8132861acb8171d18e2587efbfc06bca7f5ef7.sizes2>: Server returned status 404: Not Found
May 17 12:47:41 endless eos-updater[1573]: Failed to poll metadata from source main: Commit 7083275ee04acaf9f19fc070df8132861acb8171d18e2587efbfc06bca7f5ef7: GPG signatures found, but none are in trusted keyring
May 17 12:47:41 endless eos-updater[1573]: Changing to state Ready
Update fail. Use Endless OS 3.3.19
#43

@egrath Thanks for all of your help. I appreciate it.
You will figure it out why I can’t update and it will probably help lots of others also.

#44

Thanks for taking a look at this. Looks like there are still some commits that need to be re-signed.

#45

Just wanted to inform in this thread, that updating works again, just updated a fresh 3.5.6 and 3.3.16 to the latest one (with eos-updater-ctl poll; eos-updater-ctl update).

1 Like
#46

My OS is 3.3.19
I entered this to terminal
eos-updater-ctl poll; eos-updater-ctl update
It came back with error messages

#47

Endless OS 3.3.19 (180611-160226)
Did I do something wrong?

#48

Can you do:

  1. Open a Terminal and write:
journalctl -f -u eos-updater
  1. Open another Terminal and write:
eos-updater-ctl update

Then copy the output from the first window here. This will show us, whats going on with your updater and which errors are produced.

#49

mr@endless:~$ journalctl -f -u eos-updater
– Logs begin at Thu 2019-05-23 05:56:04 +08. –
May 23 05:56:56 endless systemd[1]: Starting Endless OS Updater…
May 23 05:56:56 endless eos-updater[1275]: Acquired a message bus connection
May 23 05:56:57 endless eos-updater[1275]: Changing to state Ready
May 23 05:56:57 endless eos-updater[1275]: Exporting objects
May 23 05:56:57 endless systemd[1]: Started Endless OS Updater.
May 23 05:56:57 endless eos-updater[1275]: Acquired the name com.endlessm.Updater

#50

No error there :slight_smile: Second terminal says

Changed state to UpdateApplied

#51

Thanks so much !!!

Screenshot%20from%202019-05-23%2006-20-11
Screenshot from 2019-05-23 06-20-11.png772×545 42.5 KB

#52

Thanks for the update. We looked into it after you reported still seeing these signature errors, and found that the old signatures had been cached by our CDN. This should be fixed now, and it sounds like that’s the case for everyone in this thread!

#53

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.