Seedvault key issue

Using /e/OS
, ,
1

I am running /e/OS 4.0 CE on FP3 (the issue described before was observable also on previous 3.x version).

Relating to this solved Seedvault issue, I still cannot select anymore a webdab from my private Nextcloud instance to store backups.

As far as I understand, this could be due to the fact /e/OS is not baselined yet to the fixed LineageOS version (22.2). Please correct any misconceptions I may have.

  • Is there a plan to fix this in /e/OS 4 CE?
  • Do I need to post an issue somewhere (I could not find a proper Issue Tracker).

Thanks!

Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services

phone
phone427×374 173 KB

2

what was the exact issue decribed?

v4.0 on FP3 dev A15 ships 15-5.8, the fix that you link to is in 15-5.9

there wasn’t a sync to upstream past 4th of june before building 12th of june, so you need to wait for the next window. But seedvault proposes to use in-built webdav support vs davx or nextcloud client (via SAF) with 15-5.9 anyway.

/e/OS forked seedvault to foundation.e.backup, but it’s not in the v4.0 FP3 A15 build yet, 4.1 probably. As I read, some things will get hidden in that downstream fork (unrelated to that issue at hand).

3

Hi @tcecyk

I can’t select my webdav folder from /e/OS backup; it is shown with -3 Bytes space availability (unreliabile information / undefined behavior).

I don’t know how to enable or use the built-in support. I also tried to use the Murena backup hosting as an intermidiate solution, with no success.

Thanks, I’ll keep looking if the bump to 15.9 or later will solve the issue.

4

This topic was automatically closed after 60 days. New replies are no longer allowed.