Discord updater won't run in Fossapup

[Zarius]

Hexcore AMD|
Radeon RX 570
using a usb WLAN adapter
FossaPup install on 500gb drive; 300mb for boot drive, the rest for Frugal install; folder, not file.

Okay. so I've got Discord installed on my install and, when I booted up today, Discord has an update waiting. I downloaded it, but it won't actually run. It downloaded in to the Spot folder, and I had to set up a password for it, and now when I put in the password, the window just closes and doesn't run the .dev. I'm *sure* I'm just missing something stupid and simple, but it's been years since I ran Linux to any great degree.

[mikeslr]

How did you install discord? Exactly what steps did you take.

AFAIK, neither chromium [google-chrome's test bed] nor any of the clones created from chromium can be updated. discord is one of those clones. You'll have to wait for someone to take the new version the originator publishes, and rebuilt it to work under Puppys --especially to run as spot.

But shortly, MikeWalsh, ozsouth, peebee or someone else who actually prepares clones for Puppys will explain.

[mikewalsh]

@Zarius :-

As t'other Mike has explained, none of the Chromium browser 'clones' (of which even Chrome is but one), OR anything that is Electron-based (the Electron 'framework' runs on top of a stripped-down Chromium browser) will, unfortunately, auto-update in Linux. Most mainstream distros perform regular releases via their own package manager/repo, but this leads to the reason why.....which, quite simply, is because there are so many alternate ways of doing things, and so many alternate layouts in the Linux world.

An auto-updater can be set to function under Windoze for the simple reason that every single copy of Windows is constructed in precisely the same way. Hence, one package is guaranteed to run for everyone.....

Several of us build, and regularly update, various browser and Electron-based packages for the community. I produce & maintain a whole slew of 'portable' packages, amongst which is a 'portable' version of Discord.....which I updated to the current v0.0.16 just the other day. If you'd like to take it for a spin, the thread is here:-

viewtopic.php?t=2717

The download link can be found in the first post, along with instructions on how to use it.

Hope that perhaps helps.

Mike.

[Zarius]

I downloaded it from the website and installed it. And I'm fine if it doesn't update on it's own (though I didn't realize that Discord was a Chromium clone), but I *downloaded* the update file, and the update file won't run. Do I just need to download the newest version and/or start using the in-browser program for Discord?

[mikewalsh]

@Zarius :-

Technically, it's NOT a Chromium 'clone.....except in the loosest possible application of the term, being based on top of a stripped-back version of that browser.

Generally speaking, any updaters that ARE designed for Linux give us problems here in Puppy-land, due to Puppy's unusual mode of operation. They're invariably designed for a full, "standard" install, along with multiple users, separate home directories, 'sudo' root elevation of privileges, and all the rest of it.

Top and bottom of the matter boils down to this; your Discord updater is NOT finding files where it expects to find them, nor will those files have the expected, restricted privileges that exist for a "normal" user. It will also be having issues with Puppy's native package management system. Nothing is quite how it expects to find it.....so it digs its heels in & refuses to run.

Mike.

[Zarius]

As annoying as that is, your explanation at least makes sense. Thanks for the info.