MX Linux Forum

When I open LBRY it says, "LBRY Leveled Up
An updated version of LBRY is now available. Your version is out of date and may be unreliable or insecure." I click upgrade and it downloads something but doesn't upgrade. I even tried the command line sudo dpkg -i /tmp/PQ4qmp/LBRY_0.39.0.deb and I get this error. "dpkg: error: cannot access archive '/tmp/PQ4qmp/LBRY_0.39.0.deb': No such file or directory" I even tried upgrading through the MX Package Installer when I found no upgraded version. How do I upgrade it?

Please explain what LBRY is, and how you installed it in the first place.

This is LBRY https://lbry.com/ I installed it from the MX Packer Installer in the Flatpaks tab from the flathub repo.

Updating flatpaks has already been discussed here: viewtopic.php?f=97&t=53749&p=537518
HTH.

JayM wrote: Thu Jan 23, 2020 10:11 pm Updating flatpaks has already been discussed here: viewtopic.php?f=97&t=53749&p=537518
HTH.

That doesn't apply to my issue. The LBRY app won't upgraded even when it offers me an upgrade in the app. There is no new version in the flathub repo.

Found the answer but I can't explain it in a civil manner.

So, if I understand correctly, the Appimage is updated by downloading the new version in another Appimage and overwriting the old version?

Seaken64

I have calmed down so I can explain it in a civil manner. I had to download the updated version from LBRY web site. https://lbry.com/ I downloaded the .deb file since I never had any luck with getting any AppImage to ever work. I installed the new version but lost everything on LBRY that I had saved except for what I have downloaded. Then I find that this so called upgrade was actually an Alpha version even through I was told that an upgrade is required because it was claimed the version I was originally using was no longer secure anymore and had vulnerabilities. I uninstalled the older version that I got from flathub using the MX Package Installer. I was originally going to file for support until I viewed the log that they require you to send for support. It would involve giving up all my privacy because the log in LBRY has every little detail in there eliminating all privacy making LBRY a farce when it comes to privacy. That's why I tried all kinds of ways to figure it out. So in other words, in order to upgrade LBRY you have to install a newer version and loose all the channels and subject matter that you follow, settings all because the updater doesn't work in LBRY.

I also use LBRY. At MX 18.3 I had previous version, so I've started update (with button in application).

After that there was a message: Error. The deamon has exited and so on.

So I've downloaded new .deb file (Joule, 0.39.0 version) and installed it. The same result.

Next, I've tried AppImage - the same result.

When I type/run AppImage in terminal, the output is:
Starting SDK
Sandbox listening on port 5278.
Daemon: [11976] Error loading Python lib '/tmp/_MEIwr1cNA/libpython3.7m.so.1.0': dlopen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/_MEIwr1cNA/libpython3.7m.so.1.0)

Gtk-Message: 21:47:11.286: GtkDialog mapped without a transient parent. This is discouraged.

In MX 18.3 there is only libc6 in version 2.24 available (in MX Package Installer).

So I've installed LBRY from flatpak, but it's 0.38.2 (previous version).

New LBRY AppImage Joule 0.39.0 works fine on MX 19 64 bit Live USB. I suppose it will be ok with new .deb file too (I'll try it).

So, maybe for MX 18.3 the problem is with GLIBC.2.25 library.

Edit:

I've found solution on LBRY Discord help channel.

https://lbry.com/faq/startup-troubleshooting

IMPORTANT: We are aware of issues starting up LBRY on Xenial based systems with the latest update. You can continue to use the old version or try the build below which keeps the original SDK that supports it

Download special Linux build for Xenial systems
https://build.lbry.io/app/build-9203_co ... /electron/

AppImage LBRY 0.39.0 from that build works fine on MX 18.3.

Many Electron apps, and LBRY is one, now require sandboxing, and that's not available in the standard Debian kernel that we use. You can either pass a flag to the program like "--no-sandbox", or use a kernel that does support sandboxings, such as Liquorix.

The .deb file from https://lbry.com/linux works when you install it which seems some of you might of missed what I posted earlier. But what it means when ever there is an update, you have to install the newer version and loose all your settings and favorite channels. Between the LBRY developers not checking their work and loosing all my settings and favorite channels is what got me mad and is why I had to wait to cool down so I could post without very colorful language. I was taught to check my work. I know the MX Linux developers check their work. Why can't the LBRY developers check their work?

Mauser wrote: Fri Jan 24, 2020 8:04 pm The .deb file from https://lbry.com/linux works when you install it which seems some of you might of missed what I posted earlier. But what it means when ever there is an update, you have to install the newer version and loose all your settings and favorite channels. Between the LBRY developers not checking their work and loosing all my settings and favorite channels is what got me mad and is why I had to wait to cool down so I could post without very colorful language. I was taught to check my work. I know the MX Linux developers check their work. Why can't the LBRY developers check their work?

It works ok (channels and so on). What you need is check an option in Settings: Sync your balance and preferences across devices.

And if you don't check an option when you log in (as you can see on my video 4 min 34 sec here: https://lbry.tv/@Dude:7/lbry-joule-desk ... lication:6) there is no channels and other private settings.

If you check it (6 min of video) - there will be private settings.

So, as usual, it is good to read manual

Stevo wrote: Fri Jan 24, 2020 7:07 pm Many Electron apps, and LBRY is one, now require sandboxing, and that's not available in the standard Debian kernel that we use. You can either pass a flag to the program like "--no-sandbox", or use a kernel that does support sandboxings, such as Liquorix.

LBRY works fine on MX 18.3 .deb (0.38.2) and standard AppImage (0.39.0, now there is already update 0.39.1) on MX 19 - without additional flags.

There was/is an issue with new version on MX 18.3 (and some other distributions), but they prepared quickly workaround for this (special versions of files) (as I wrote above a few posts earlier).

LBRY people work and react fast, it's really impressive.

Fibogacci wrote: Fri Jan 24, 2020 9:11 pm

Mauser wrote: Fri Jan 24, 2020 8:04 pm The .deb file from https://lbry.com/linux works when you install it which seems some of you might of missed what I posted earlier. But what it means when ever there is an update, you have to install the newer version and loose all your settings and favorite channels. Between the LBRY developers not checking their work and loosing all my settings and favorite channels is what got me mad and is why I had to wait to cool down so I could post without very colorful language. I was taught to check my work. I know the MX Linux developers check their work. Why can't the LBRY developers check their work?

It works ok (channels and so on). What you need is check an option in Settings: Sync your balance and preferences across devices.

And if you don't check an option when you log in (as you can see on my video 4 min 34 sec here: https://lbry.tv/@Dude:7/lbry-joule-desk ... lication:6) there is no channels and other private settings.

If you check it (6 min of video) - there will be private settings.

So, as usual, it is good to read manual

The LBRY app didn't work O.K. in my case. I had to re-install the newer version because the older version wouldn't upgrade. When I installed the .deb file installing the newer version that works fine but I lost all settings and channels I had followed. I had to adjust all my settings. What I really don't like about LBRY is after viewing the logs was very disturbing privacy wise and that the app needs to be re-installed in order to update it.