system reverted to Ubuntu after Proton VPN install

[[email protected]]

How does 'system reverted to Ubuntu after Proton VPN install' show itself ?
This may be a significant issue - can you explain what you mean please ?

It looks like the proton vpn installation has added invalid repositories/authentication mechanisms to your system.
The invalid authentication is preventing the update/upgrade process working.
Your system cannot update until the problem has been corrected or some workaround applied.

Simply disabling the proton vpn repositories will allow the rest of the update/upgrade to work but will stop any proton vpn updates which is not good.
To try to recommend a better solution, we need to know a bit more about what was done when installing proton.
Can you provide a link to the instructions you followed to install proton vpn ?

Do you have a System Restore Utility (aka Timeshift) snapshot taken from before the Proton installation ?

---

Thank you ever so much for your time and assistance.


First —

After a seemingly successful install (of Proton VPN, via terminal), I had done a reboot. Walked away for what couldn’t have been but a mere moment, only to find complete reversion to the Ubuntu side of things.

Which, safe to say: I was rather taken aback by. Though I started out there, decades ago, I somehow must have skipped over how Lite was based on it. But then, what isn’t these days, right -?

But yeah — kinda almost like a fresh install, honestly.

Obviously confused, I did another reboot. Only to find the GRUB menu was now stating the Windows partition and “xUbuntu” was in place of where Lite had been, previously.


Jumping Ahead (slightly) —

That I do: protonvpn.com/support/official-linux-vpn-debian

I traced that link through the android app. Via the “help” option.

But, more specifically, I believe it was the “optional” step to place the icon in the Linux system tray that did it {explanation as for why that was deemed important, to follow}.

Kinda wishing I skipped over that one.


As to a bit of the backstory —

Seriously, I was just about done with getting the two halves of my new (donated) PC “up and running” — and this was the last caveat to having completed the task of the initial setup.

For using the system “Network” options [under the VPN drop down menu] kept failing. And the .deb package wasn’t doing the trick. Since pretty much the get-go. After working my way through all the means to install stuff on Lite {kinda exhausting, but kinda dig it — as well}.

Given the credible death threats I (inevitably always manage to) receive(d), I very nearly stopped — mid process — and opted to go back to Mint. My mainstay of the better part of the last decade. Or so. Being that VPN’s are kinda critical — for what I do. And, Proton (overall) was well tested there.


Aside from that —

There isn’t much more to say, honestly.

Just kinda happened. Like some kind of sick cosmic joke.

Best I can figure: it’s some invalid or harmful issue on the Proton VPN side. I’ve already contacted them and they seem just as puzzled.


As to your deductions;

I couldn’t agree more.

Sadly, my Traumatic Brain Injury (2006) has robbed me of much of what would be required for me to suss this out, myself. But, that is not to say that I don’t still know a thing of two as to how to hit the pavement running. But, I fear this one is a tad beyond me.

Granted, it would really suck, but I am not above a fresh re-install // complete wipe of the Linux side. However, it would be preferable to know what the underlying cause was. As to not repeat the same step. Twice.

Arguably, as to Lite Linux; I am VERY much still wet behind the ears — with only having stumbled upon it in the past 6 weeks … after finding a need to resurrect a nearly 20 year old Mac Mini (after my last tower finally “kicked it”), but still.

In nearly 30 some odd years of being predominately a Linux user, I have never — nor have I ever — heard of such a thing as this little pickle.

As much as I do not know about Lite, must admit (especially prior to this snafu); I am falling in love rather quickly. And some assurances of what aspect of this is at fault (aside from the standard “user error,” that is). For I find myself in an unpleasant position. Given how my present life circumstances dictate that I require a workable, reliable computer (disabled).

And I have attempted to do all that I know to expunge the offending code/programming, but I’m still coming up short.


As to your final inquiry —

That I do have TimeShift. Was one of the first steps I’ve tried. However, the results of which are not at all desirable.

Kind of some freakish hybrid of not-quite-Lite, not-quite-Ubuntu.

I was, at the very least, able to revive the system long enough to secure my files. So there’s that.

But due to this, I’ve gone and increased the frequency of how often a back-up is made. Though, that does me little good (now).


In conclusion (for now, at least) —

I’ve followed step-by-step guides on how to punch things into Terminal. For decades. Being how that is unavoidable outcome of the OS … but, I’ve in no way shape or form have even remotely come across such a catastrophic outcome as this.

And being the person I am: it’s not so much about me, but preventing such things for those less capable than myself. Hence, why I am ultimately okay with starting at zero (Linux wise). If I get anything out of this at all, my hopes would be from keeping a less inclined party from the “WTF -?” // panicked side of it all.


Again, I thank you — in advance — for your considerations and expertise.

---

Did you use these exact instructions? https://protonvpn.com/support/official-l...pn-ubuntu/

---

Close, but not quite.

I found protonvpn.com/support/official-linux-vpn-debian through their Android app.

---

===========================
Install Updates Error Log
===========================

Install Updates could not fetch the package cache information lists.
Go to https://www.freecinema2022.gq/forums/ and paste the log below into
a new or existing thread for assistance.

============ Log ===========

Hit:1 http://mirror.clarkson.edu/linux-lite galena InRelease
Get:2 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]
Hit:3 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:4 https://repo.protonvpn.com/debian unstable InRelease
Hit:5 https://packages.mozilla.org/apt mozilla InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu noble InRelease
Get:7 https://repo.protonvpn.com/debian stable InRelease [2,967 B]
Hit:8 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease
Get:9 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
Hit:10 https://ppa.launchpadcontent.net/mozilla...ext/ubuntu noble InRelease
Err:7 https://repo.protonvpn.com/debian stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8DD48989F43719CA
Hit:11 https://dl.google.com/linux/chrome/deb stable InRelease
Get:12 http://security.ubuntu.com/ubuntu noble-security/main amd64 Components [7,224 B]
Get:13 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
Get:14 http://security.ubuntu.com/ubuntu noble-security/restricted amd64 Components [212 B]
Get:15 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Components [52.0 kB]
Get:16 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 Components [212 B]
Get:17 http://us.archive.ubuntu.com/ubuntu noble-updates/main amd64 Components [151 kB]
Get:18 http://us.archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Components [212 B]
Get:19 http://us.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Components [309 kB]
Get:20 http://us.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Components [940 B]
Get:21 http://us.archive.ubuntu.com/ubuntu noble-backports/main amd64 Components [208 B]
Get:22 http://us.archive.ubuntu.com/ubuntu noble-backports/restricted amd64 Components [216 B]
Get:23 http://us.archive.ubuntu.com/ubuntu noble-backports/universe amd64 Components [11.7 kB]
Get:24 http://us.archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 Components [212 B]
Reading package lists...
W: GPG error: https://repo.protonvpn.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8DD48989F43719CA
E: The repository 'https://repo.protonvpn.com/debian stable InRelease' is not signed.
W: https://ppa.launchpadcontent.net/mozilla.../InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024)
W: https://ppa.launchpadcontent.net/mozilla.../InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024)

---

Why do you have two Debian repositories listed for Proton? Did you bork the install? You can only use one at a time i/e stable or unstable.

Oh I see now, It looks like the installation instructions Jerry linked to won't work with Linux Lite updater if you try to install the beta version after the stable one is installed and from your situation it looks like you need to run the beta. Start over and only install the beta.

TC

---

That was actually the recommendations of other guides // suggestions I found (elsewhere).

After the system reversion, to attempt to remove the standard version and go with the beta option. And see if that took the kink out of the hose to get the updater working again.

As to not have to re-install the OS — from scratch.

But that was all prior to effecting the partial walk-back via TimeShift.