Page 1 of 1
Automatic Update not working for Linux
Posted: 2022-05-10, 12:11
by Lothar Weber
Xubuntu 18.04:
29.4.6:
64bit:
Problem URL:
Browser theme (if not default):
Installed add-ons:
Installed plugins: (about:plugins):
If possible, please include the output of help->troubleshooting information (as text):
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 12:20
by Moonchild
open about:config
find app.update.log
set to "true"
Open Developer tools -> browser console
Click trash can
Go to Help->Check for updates
Copy and paste the browser console output in your reply.
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 12:30
by smithy
Not sure if its the same problem, but I get this message.
Screenshot_2022-05-10_13-26-28.png
On Linux mint xfce
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 13:07
by Lothar Weber
Exactly what I get looking for update. In the meanwhile I did it manually.
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 13:07
by Night Wing
@ smithy
I'm running 64 bit linux Mint 20.3 (Una) Xfce and I manually updated to 64 bit linux Pale Moon 31.0 by using the link below. Pick your choice of either GTK3 or GTK2.
http://linux.palemoon.org/download/mainline/
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 13:20
by JSladek
Using PCLinusOS:
Browser console output:
Code: Select all
TypeError: popup is null[Learn More]
toolbar_button.js:301:5
AUS:UI gUpdates:onLoad - setting current page to startpage checking
AUS:SVC Checker: checkForUpdates, force: true
AUS:SVC Checker:getUpdateURL - update URL: https://aus.palemoon.org/?application=palemoon&version=29.4.6&arch=Linux_x86_64-gcc3&flavor=gtk3&toolkit=gtk3&buildid=20220410194651&channel=release&force=1
AUS:SVC Checker:checkForUpdates - sending request to: https://aus.palemoon.org/?application=palemoon&version=29.4.6&arch=Linux_x86_64-gcc3&flavor=gtk3&toolkit=gtk3&buildid=20220410194651&channel=release&force=1
AUS:SVC Checker:onLoad - request completed downloading document
AUS:SVC Checker:_updates get - unexpected node name!
AUS:SVC Checker:onLoad - there was a problem checking for updates. Exception: Error: Unexpected node name, expected: updates, got: error
AUS:SVC Checker:onLoad - request.status: 200
AUS:SVC getStatusTextFromCode - transfer error: Update XML file malformed (200), code: 200
AUS:UI gCheckingPage:onError - proceeding to error page
AUS:UI gErrorsPage:onPageShow - update.statusText: Update XML file malformed (200)
ALso downloaded gtk3 version of 31.0.0 from site and it is was still 29.4.6
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 13:40
by JSladek
ALso downloaded gtk3 version of 31.0.0 from site and it is was still 29.4.6
My bad. downloaded version is the 31.0 version.
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 14:16
by Moonchild
Yeah I think this was a small mistake by Travis. He uploaded the wrong update archives.
For the moment just manually updating is the only option.
Also note: Automatic updating with the internal updater from v30.* to v31 on Linux is not supported and manual installation (or using a package manager or similar distribution) is the only way forward there.
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 15:42
by BenFenner
If I give it a week or so, would I expect PM to auto-update from 29 to 31 on Linux (Mint)?
Or can I expect to have to manually update, regardless of how long I wait (no fix expected)?
Just trying to plan my near future and if I'll need to do anything or if I can ride it out.
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 17:46
by smithy
Thanks, that worked
The "Fox to the moon" theme is incompatible, but otherwise all good. )
Re: Automatic Update not working for Linux
Posted: 2022-05-10, 22:03
by trava90
Sorry guys this was my mistake. Everything should be fixed now and automatic updates should work again.
Re: Automatic Update not working for Linux
Posted: 2022-05-12, 16:08
by BenFenner
I'm still waiting for this update on Linux Mint. The Update Manager doesn't have anything for Pale Moon right now. I'm currently on PM v29.4.6.
Patiently sitting by awaiting instructions.
Re: Automatic Update not working for Linux
Posted: 2022-05-12, 16:38
by Moonraker
BenFenner wrote: ↑2022-05-12, 16:08
I'm still waiting for this update on Linux Mint. The Update Manager doesn't have anything for Pale Moon right now. I'm currently on PM v29.4.6.
Patiently sitting by awaiting instructions.
The browser will update internally.check for updates.
Re: Automatic Update not working for Linux
Posted: 2022-05-13, 13:12
by BenFenner
Moonraker wrote: ↑2022-05-12, 16:38
The browser will update internally.check for updates.
I don't know exactly what updating "internally" means, but it sounds like you expect the browser to update outside of the normal OS update manager.
That is not the case in my configuration.
However, this morning I do see the update in my OS Update Manager, so all is well.
Re: Automatic Update not working for Linux
Posted: 2022-05-13, 14:04
by Moonchild
It depends entirely on how you installed the browser in the first place.
If you installed the "mainline" (i.e. official binary) version from linux.palemoon.org, then updating is handled internally, i.e. in the browser itself (help -> check for updates, or on a bi-daily timer).
if you installed it through an OS package manager, then updates will be handled by that manager but will depend on when the package maintainer updates the package with the new version (which can have a delay of hours to days, normally).
Re: Automatic Update not working for Linux
Posted: 2022-05-13, 20:21
by stevenpusser
For Debian derived distros, just "apt policy palemoon" in a terminal will tell us what version of Pale Moon the apt system knows about, and what repository it's coming from. I uploaded the 31.0.0 sources early yesterday afternoon California time, and they take a few hours to build for x86 architectures, and about 10X longer for 32-bit ARM (armhf in Debian, i.e. Raspberry Pi).
Right now on the OBS, since I'm also building armhf packages, and the OBS seems to be slower in providing armhf virtual build machines with lots of RAM, I'm limiting the maximum number of threads to four. If someone wants to rebuild my sources, which can be downloaded from the OBS without
being logged in there, and you have some 128 GB 32-core fire-breathing monster, you can read the last lines of debian/mozconfig and increase the number of threads, and probably build it in a few minutes.