MoonGestures doesn't work after last palemoon update Topic is solved

[purpleleaf]

As in subject, after last palemoon update (version 32.1.0), moongesture stopped working.
Trying some gestures, the status bar shows 'unknown gesture'.
Opening palemoon displays two error consoles, showing the same errors.

Opening the monngestures preferences show this error:

Code: Select all

Errore interpretazione XML: entità non definita
Indirizzo: chrome://firegestures/content/prefs.xul
Riga numero 29, colonna 5:				<checkbox id="mousegesture" label="&mouseGesture;"
--------------------------------^

Translations from italian is:

XML Interprettion error: not defined entity
address: chrome://firegestures/content/prefs.xul
row number 29, column 5: <checkbox id="mousegesture" label="&mouseGesture;"

furthermore opening palemoon shows two error consoles (both with the same content), with a bunch of errors.
The last one, referring to mongestures is:
Data e ora: 28/03/2023 12:07:32

Code: Select all

Errore:  [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: jar:file:///home/max/.moonchild%20productions/pale%20moon/fm8za29d.default/extensions/%7Ba4255263-569a-4ae7-9a5f-978e882cbe76%7D.xpi!/components/xdGestureService.js :: FGS_getLocaleString :: line 197"  data: no]

disabling the extension solves the console errors problem.

[moonbat]

You'll have to contact the extension author to fix it, or hope someone here can troubleshoot the extension; either way it isn't the browser's fault that an old extension stopped working.

[purpleleaf]

You'll have to contact the extension author to fix it, or hope someone here can troubleshoot the extension; either way it isn't the browser's fault that an old extension stopped working.

I should have done so already, but on the extension page only the developer name is reported.
Could you suggest some way to contact him?

Many thanks

ps, anyway, the extension is not old at all, it was updated on january 31

[Moonchild]

By the looks of it this is a problem with the extension's locale (undefined localized string). i.e.: they may have updated the extension but forgot to update all the localized strings.
This would be unrelated to any Pale Moon updates, though, and would have been present for a longer time (unless the extension was updated at the same time?)

[purpleleaf]

By the looks of it this is a problem with the extension's locale (undefined localized string). i.e.: they may have updated the extension but forgot to update all the localized strings.
This would be unrelated to any Pale Moon updates, though, and would have been present for a longer time (unless the extension was updated at the same time?)

I was using the italian language, and i installed the lang pack just after the last palemoon update, so i removed the lang pack and now i'm using the english version of palemoon but the problem persists.
Furthermore this issue appears after the last palemoon update and the last extension update was on january 31, as I reported in my previous post.
I tried also to install some previous versions of palemoon, but the problem is still there.
I will try to start a new profile and will post the result soon.

[purpleleaf]

Solved.
on my arch installation there was a palemoon-i18n-common package referring to palemoon version 29.02
I removed that package and now all works.
I wonder only what caused this problem just now.....