Pale Moon forum

TheRealMaestro wrote: ↑

2023-01-27, 17:01

Which distribution are you using, and how had you installed Pale Moon? The tarball version should be unpacked in /home, where it can modify itself, not under /usr. At any rate, one cannot invoke the tarball version through the terminal as palemoon, as though it were a package. If you would like to manage Pale Moon as an ordinary package, like I do, I suggest installing your distribution’s contributed build if it is not already in your distribution’s official repository. If it is therein, then its overseers might simply be slow to build and offer v32.

Off-topic:
Enabling root privileges for your normal account is rather dangerous, akin to running everything as an administrator on Windows. You should undo this if you can.

TheRealMaestro wrote: ↑

2023-01-28, 04:51

Hm… Pale Moon, if it is being released as a package, ought not check for updates (which it cannot install) on its own. If you click on Preferences, then Advanced in the window that appears, then the Update tab, have you got a single tick box for search engines and nothing else (as in my screenshot), or are there further settings? If there are further settings, then among them should be one to disable checking for updates. Disabling this will not affect your package manager’s function, but it will stop (future) notifications from Pale Moon itself about updates. It also means that the Manjaro repository’s managers have been careless about how they build the package: such packaged versions should not include the updater that features in the tarball, to prevent scenarios like this. Someone should inform them of this.

I confess I am less sure of how to stop the current round of notifications, or what to do if your settings are like mine, but I am researching.

Mæstro wrote: ↑

2023-01-28, 16:22

Does disabling checking for updates stop the browser nagging you? If not, there must be some way to clear the updater’s memory of available updates, but I have not yet found it in my searching.