WARNING Palemoon 30.0.0 lost autofill logins High CPU

[peppyy]

After several replies I updated the subject.

Just a warning, I updated Palemoon today and now I have no login credentials unless I look each one up in Tools, Preferences, Passwords. Anyone else having this issue? If not, how do I roll back Palemoon? Thanks in advance.

palemoon-30-0-0-usage.jpg (32.38 KiB) Viewed 1341 times

PS, I heard my fans kick on high so I went to htop. This is the only app I am using at the moment and only on this site, other than Take a shot.

palemoon-30-0-0-usage2.jpg (58.36 KiB) Viewed 1341 times

It appears to be swapping cores, as in one goes full and drops then another goes full and drops and this is just posting on this forum without anything else open.

[FeodorF]

Oh boy!

They are saying that v30.0.0 "Is a new milestone release!"
With other words, they have thrown every thing over board.

http://www.palemoon.org/releasenotes.shtml

O.K., I'll jump into the pond too and give it a try.

[mikeslr]

Thanks, peppyy, for the warning, and FeodorF for the details.

For others, may I recommend the following:
Install the portable from here, viewtopic.php?t=709 if you are using some other version. Don't update until you transferred your credentials and customizatons.
Right-Click that folder and select Duplicate from the Pop-up menu.
Only duplicate one of the two versions you now have.
Then kindly post what problems you have and steps you've taken to get the updated version as useful as the old version.

[JASpup]

Obtuse acknowledgement...

I do not use login credentials so can't help there.

Reverting is highly dependent on how both previous and new versions are ran.

On my system if PM were builtin and I were running frugal, new PM would be standalone.

Normally I remove it in a remaster, so any version can be installed or removed.

If you're frugal, a new version by package in the PPM should be "Uninstall"able.

If you installed PM over an existing builtin version, snafus are normal. Standalone then is really the way to go. Same for PM .sfs.

[Feek]

my fans kick on high
It appears to be swapping cores, as in one goes full and drops then another goes full and drops.

EDIT: in this case, the real cause is probably the new version of Palemoon (you can ignore my post).

Exactly what you describe happens to me (very rarely) with Firefox.
I haven't found out the cause yet, something just goes wrong (maybe some bad downloads).

Anyway, rebooting always helped me.

[peppyy]

I was hoping that the problems would magically resolve after I shut down for the night and rebooted this morning, No such luck. Guess I will head over to Firefox to keep the cpu happy till I figure it out.

[FeodorF]

Yes @peppyy , you are right saying the cpu gets hot. My BIOS box with quad core gets very hot. That never ever happened with the older versions of Pale Moon.

[peppyy]

Safe Mode is no better so I am guessing it has nothing to do with extensions. Still looking for a way to revert. Might see what happens in console. Getting hot gotta go.

[rockedge]

something is really wrong with palemoon 30.

If this is progress..........

[Keef]

Rather than risk an update, I downloaded the tarball from the Palemoon site. On FatDog there is no CPU hogging, but there is no text in menus or dialogs, which is a little awkward. It does work perfectly well on EasyOS though (haven't tested the autofill login, as I rarely use that).
Tried it with my exisitng profile and that was ok too (has ublock and noscript extensions).

[xenial]

I too was experiencing very high cpu usage with palemoon with just the homepage open which has never occurred before.
No complete themes available at the moment with v30.I did give it a fair chance and tried several times but the cpu usage was 49% in some cases.

I will refrain from using it..Librewolf seems a good alternative.

[bigpup]

Is this happening with a clean version of Pale Moon 30?

No add-ons.

[mikewalsh]

Is this happening with a clean version of Pale Moon 30?

No add-ons.

Yup. Add-ons have got nowt to do wi' it.

I've just fired up a brand-new copy of the portable PaleMoon, then allowed it to update. Even on this 'big rig' of mine, although CPU usage seems kinda constant at around 23-28% (effectively one core), temps are getting up near the 60°C mark.....high enough for the fans to step up a gear.

Nothing else running. No addons. Just this forum.

Moonchild Productions have re-coded the browser so that it now identifies internally as Firefox.....because users have been moaning about not being able to use the older FF extensions & add-ons, and their user downloads have been nosediving this last year.

I can only presume Moonchild & Tobin haven't got the bugs out of it yet.....even on the Pale Moon forums, folks have definitely noticed, and there's a slew of complaints already. We'll have to wait and see what the first point release brings.

Mike.

[peppyy]

I downloaded Mike's portable 64 version and put it in My Applications.
I am guessing that I should backup my profile in .moonchild-Productions to use with the portable, but where should I put it so the portable finds it?

Sorry, I have a lot of irons in the fire today so my memory is a bit foggy.

[mikewalsh]

@peppyy :-

You want to put the 'portable' directory outside the save. /mnt/home's a good place.....or even stick it on a Linux-formatted flash drive.

I'd do this:-

• Click to enter the portable, so the 'LAUNCH' script is showing. Leave this window open.

• Go into /root/.moonchild productions/palemoon, and locate the "xxxxxxxxxx.default" directory. Copy this across to the open PaleMoon-portable window, so it's alongside the 'LAUNCH' script.

• Once you've done this, rename it to just "profile" (no .default or anything). PaleMoon's launcher will now find it, and use it.

Easy when you know how. Let us know how ya get on, please.

Mike.

EDIT:- It won't "fix" the behaviour, but it will give you an external, self-contained copy that you can use to experiment with until this all gets sorted out.

[peppyy]

Put it in mnt/home, copied and renamed my profile, Ran the menu script, restarted x and launched from the menu. It was still the installed version.
Launched from the launch script in the portable directory and it was the portable one. When launched it brought up the 30.0.0 release page which was interesting. It immediately wanted to update to which I said ask later. Help reports version 29.4.1 and it appears to be working correctly.

Should I uninstall the built in and run the menu script again.

pm-portable.jpg (242.99 KiB) Viewed 1138 times

[mikeslr]

Menu>Setup>Remove builtin packages doesn't actually remove anything until you remaster. It just writes a .wh (white-out) file so that it will not be used.

I'd just change the Exec= argument used in /usr/share/applications/palemoon.desktop. Currently it probably reads something like:
Exec=/opt/palemoon/palemoon.
Open the file in geany/text-editor and change that line to point to the LAUNCH script. General argument is Exec=/PATH-TO-LAUNCH-SCRIPT/LAUNCH
Probably something like:
Exec=/mnt/home/palemoon/LAUNCH

Tips: Linux is case sensitive. And after you've extracted a portable folder you can rename it anything such as by removing identifying endings, e.g. ...xxx.extracted.

Then run fixmenus or Restart-x so that your system picks up the new location. If you have a panel/taskbar launcher for Palemoon you also may have to remove it, then add it back so that the 'new version' is called by the launcher.

You may also want to open Palemoon's settings and put a check mark in "Never Update" or "Check for updates but let me choose": Menu>Tools>Preferences>Advanced>Update. The former isn't recommended, but will eliminate the nag at startup. Mike Walsh and other Puppy Fans will likely keep us posted as to when it's safe to go back in the water, hopefully soon.

I use other Web-browsers for special purposes. But Palemoon has been my default browser for accessing this Forum and general browsing. Except for seamonkey, up 'til now, it ran the lightest of browsers that can provide the full range of graphics found on the web. And unfortunately seamonkey has been mozilla's bastard-child deprived of a decent set of addons. [Classic Add-on Archive can be used. But most of the old addons are either non-functional or just old and likely security hazards].

[xenial]

@bigpup
It was a straight update through the internal updater and with just the home screen and doing absolutely nothing the cpu usage was creeping up to the 50% mark which i regard as rather high.

not certain if it was a clash between the profile of the previous version.I have cleaned my system entirely of pale moon and will attempt another clean install to see if the issue persists..odd as i have never experienced this with the browser before and i have used it for a few years.

[mikewalsh]

@xenial :-

@bigpup
It was a straight update through the internal updater and with just the home screen and doing absolutely nothing the cpu usage was creeping up to the 50% mark which i regard as rather high.

not certain if it was a clash between the profile of the previous version.I have cleaned my system entirely of pale moon and will attempt another clean install to see if the issue persists..odd as i have never experienced this with the browser before and i have used it for a few years.

My guess is that there will be at least a couple of point releases out over the next several days. You're aware yourself that Pale Moon forum regulars are already bitching about v30.....

Something's bound to happen before too much longer. I don't see it remaining like it is for long, y'know? (And who cares if Tobin IS getting his knickers in a twist over it all?)

(*shrug*)

Mike.

[xenial]

@mikewalsh
Thanks mike.
I made a passing comment on one of the threads on their forum in regard to the cpu usage and like you say if i create a specific thread on the subject then the wrath of tobin will fall upon me....

Just to point out that any potential new users of the browser may be put off by the fact that the full complete themes are non existent which incidentally was one of pale moon's selling points.

Not certain if this is a sign of intent in regard to the full themes and it could be months before any appear indeed if they do at all.

[peppyy]

I just dragged a shortcut from launch to the desktop for now. Sure is nice not having to look every login up now. Seems to run great, currently under 1% usage while I am typing this. Not even a line on gatotray.

Thanks everyone. Now on to change the motor on my 71 Wheel Horse.

[mikewalsh]

@peppyy :-

Yeah, this is one of those scenarios where the Menu Add/Remove stuff doesn't always work.

All the script does is to create an 'absolute' sym-link from the 'LAUNCH' script into /usr/bin, renaming it to the name of the app as it does so. Of course, if there's a regular, existing file with the same name, the sym-link fails.....because a sym-link will never overwrite a 'real' file. It can't, by its very nature.

Perhaps I should start naming these sym-links slightly differently. Like, in this case - for instance - make the symlink read

Code: Select all

palemoon.app

.....instead of just

Code: Select all

palemoon

.....in order to prevent a naming 'clash'. Something I really ought to have considered at an earlier stage of the game. Hmm.....

Mike.

[xenial]

It should be noted that tobin one of the pale moon developers has in fact left the project and has also been banned from the forum so a point release might be a bit longer than anticipated.

[Wiz57]

Reading the release notes and other information about PM 30, it looks like Moonchild has ditched UXP in favor of Goanna engine.
This of course means that some themes may not work as they did on prior UXP versions, but it also appeases the group that
wants to use who-know-how-many older Firefox extensions as many are more compatible with Goanna than UXP.

I know it's "anathema" to suggest users actually READ documentation before using a new version...if most of them had,
they would realize that PM 30 is way different than PM29...given time, perhaps some of the little bugs will get worked out.
Just as is normally advised with Puppy Linux update versions...using a savefile from prior version may have unexpected
results. Be prepared to "roll back"...backup your savefile, or in the case of Palemoon, your profile...and with such a big
milestone release, perhaps time to start fresh with a new profile.
Wiz

[Keef]

Further to my previous post, there are gtk3 and gtk2 versions available. The latter works correctly on Fatdog (the gtk3 version does not display text in menus etc).

[mikewalsh]

@xenial :-

It should be noted that tobin one of the pale moon developers has in fact left the project and has also been banned from the forum so a point release might be a bit longer than anticipated.

From what I understood, reading through the particular thread the other night - I still "visit", occasionally - the decision to quit participation in the forum was in fact by mutual 'agreement' between Moonchild and Tobin. It didn't exactly look like a 'ban', as such, though I admit Tobin was NOT exactly happy about it!

Mike.

[mikewalsh]

@Keef :-

Further to my previous post, there are gtk3 and gtk2 versions available. The latter works correctly on Fatdog (the gtk3 version does not display text in menus etc).

Well, the version I based the portable package on WAS in fact the GTK2 build.....so that probably explains why I hadn't noticed some of the things others here have mentioned.

(*shrug*)

Mike.

[xenial]

This is a link to the pale moon forum thread which seems to indicate tobin has in fact left the project and also the add on site for which he is/was the maintainer is down at the moment for an undetermined period of time.

https://forum.palemoon.org/viewtopic.ph ... 01#p225101

[JASpup]

I'm typing this in 30 by spot .sfs that I just made in Fossa.

I'm in Xenial JWM because it doesn't work in Fossa.

What is it that blocks a .sfs app from appearing in the spot directory? Is this related to the use of the home directory?

It works in Xenial without a hitch.

The only caveat is my Xenial has the default browser removed, but it shouldn't matter because 30 is in the spot directory with a different launcher. They should co-exist with the exception of using the same .config folder (you wouldn't want to run builtin & 30 at the same time).

I'd be happy to share my .sfs if I can make it spot-compatible for Fossa.

[mikewalsh]

@JASpup :-

RI-i-ight. So; you built it in Fossa.....but it doesn't, in fact, work in Fossa. O-kay.

Did you not think to try it out first before you packaged it..? Would make more sense..!

Mike.