1. In "/opt" I see the full "palemoon" folder with all its sub-folders.
Same for "/root/.moonchild productions".
i.e. NOT symlinked.
2. In "/mnt/home" I see both the "palemoon" and ".moonchild productions" folders with their [almost] identical sub-folders content to those in the slackosave filesystem.
The single EXCEPTION?=["/mnt/home/.moonchild productions/pale moon/k2zdffo5.default" has a folder="saved-telemetry-pings" not in "/root/.moonchild productions/pale moon/k2zdffo5.default"]
palemoon browser
The steps are (1) drag the palemoon folder from /opt to /mnt/home and select copy. (2) Delete the palemoon folder from /opt. (3) Then drag the palemoon folder from /mnt/home and select Link(relative).Sylvander wrote:1. In "/opt" I see the full "palemoon" folder with all its sub-folders.
Same for "/root/.moonchild productions".
i.e. NOT symlinked.
2. In "/mnt/home" I see both the "palemoon" and ".moonchild productions" folders with their [almost] identical sub-folders content to those in the slackosave filesystem.
The single EXCEPTION?=["/mnt/home/.moonchild productions/pale moon/k2zdffo5.default" has a folder="saved-telemetry-pings" not in "/root/.moonchild productions/pale moon/k2zdffo5.default"]
But, as long as you have the palemoon folder on /mn/home, you might as well test to see that that one is working before deleting the one at /opt. File-browse into /mnt/home/palemoon and Left-Click the palemoon executable. It looks like a gear. Palemoon should fire right-up. If it does, delete the /opt/palemoon folder and perform Step (3).
The "save-telemetry-pings" is a cached file. The next time (if ever) running from /mnt/home, it will be downloaded again. It's no on my system at all.
Step (4) Don't forget to file-browse to /root, Left-Click Rox's Eye, then drag the .moonchild productions folder into /mnt/home/palemoon, select Move, then drag it back to /root and select Link(relative).
"Palemoon will no longer run from clicking on the "Menu->Internet->Palemoon" entry.
Your operating system expects to find executables "on the path": that is within some /bin or /sbin folder such as /usr/bin, /root/my-applications/bin. NEITHER /opt nor /mnt/home are "on the path". In order to run an application located on either, there must be "on the path" either a symbolic link to the actual binary or an executable bash-script calling the binary.
Open /usr/share/applications/palemoon.desktop in a text-editor. On my system the Exec argument is "Exec = palemoon" with nothing else. So it is looking for something "on the path". pfind "palemoon" shows that there's a palemoon file in /usr/bin; /usr/bin is on the path where you system expects to find executables. Visual examination of that file shows that it is a symbolic link to /opt/palemoon/palemoon. [I haven't moved palemoon to /mnt/home]. But IIRC, on a different system /usr/bin/palemoon was a bash-script which called /opt/palemoon/palemoon. On your system pfind may reveal that it is somewhere else "on the path" -- in a different "bin" or [less likely] "sbin" folder.
The following should work regardless of how your system currently handles palemoon. Open /usr/share/applications/palemoon.desktop in a text editor, and make sure "Exec = palemoon" is how that line is written. If not, edit it so that it will say that without the quotes.
pfind "palemoon" and look for an entry within a /bin or /sbin folder. Browse to that entry and leave that window open. Open a second file-browser window and browse to /mnt/home/palemoon. In the first window delete the bash-script or symbolic link From the second window drag the palemoon executable --just says palemoon and looks like a gear-- into the first window. Select Link(relative). Restart-x. You should now be able to start palemoon from the menu. If so, Save the changes to your SaveFile/Folder.
b. When I enter the "palemoon" command at the terminal command prompt, it returns:
"bash: palemoon: command not found". Repost if this condition exists after you've made the above change.
-
a_salty_dogg
- Posts: 180
- Joined: Sun 15 Dec 2013, 19:08
@Sylvander
Do I understand you've updated to version 28.0.1 since symlinking the Palemoon folders to "home"?
If that's the case, the new Palemoon version will have installed itself to "opt" and it sounds like your config file at ".moonchild productions" has rebuilt itself, and you'll have to go through the whole process again. (Don't worry about the folders you already moved to "home", copying the new version will overwrite them).
The easiest way to update in this situation would have been to download the latest tarball direct from Palemoon.org, then to extract it directly into the Palemoon folder at mnt/home.
However this doesn't explain how your links to menu and to "usr/bin" became broken; if you created identically named symlinks to the identical locations from which you moved the folders, they should not have been affected, so follow mikeslr's directions above to check and fix as necessary.
Do I understand you've updated to version 28.0.1 since symlinking the Palemoon folders to "home"?
If that's the case, the new Palemoon version will have installed itself to "opt" and it sounds like your config file at ".moonchild productions" has rebuilt itself, and you'll have to go through the whole process again. (Don't worry about the folders you already moved to "home", copying the new version will overwrite them).
The easiest way to update in this situation would have been to download the latest tarball direct from Palemoon.org, then to extract it directly into the Palemoon folder at mnt/home.
However this doesn't explain how your links to menu and to "usr/bin" became broken; if you created identically named symlinks to the identical locations from which you moved the folders, they should not have been affected, so follow mikeslr's directions above to check and fix as necessary.
@mikeslr
SUCCESS!
[Looks so prior to saving the changes and reboot]
1. Prior to attempting your instructions, I used another Puppy to restore [and rename correctly] a "HotBackup" of my slackosave.
That took my booted Slacko back to the way things were before making any changes.
Hence "Menu->Internet->Palemoon" succeeded in running the Palemoon browser, and the "/opt/palemoon" folder was there, and also the "/root/.moonchild productions" folder was there.
I deleted the copies "/mnt/home/palemoon" and "/mnt/home/.moonchild productions" [note the incorrect location of this folder (according to your info it aught to be at "/mnt/home/palemoon/.moonchild productions")].
2. I followed your instructions, and all appeared to work at 1st attempt.
3. No need to "FIX" the "Menu->Internet->Palemoon" entry, since it worked once booted to the desktop, and continued to work after completing as instructed.
In the same way, Palemoon also ran using the command prompt in the terminal
4. I'll save the session changes, reboot, and report back regarding the results..
SUCCESS!
[Looks so prior to saving the changes and reboot]
1. Prior to attempting your instructions, I used another Puppy to restore [and rename correctly] a "HotBackup" of my slackosave.
That took my booted Slacko back to the way things were before making any changes.
Hence "Menu->Internet->Palemoon" succeeded in running the Palemoon browser, and the "/opt/palemoon" folder was there, and also the "/root/.moonchild productions" folder was there.
I deleted the copies "/mnt/home/palemoon" and "/mnt/home/.moonchild productions" [note the incorrect location of this folder (according to your info it aught to be at "/mnt/home/palemoon/.moonchild productions")].
2. I followed your instructions, and all appeared to work at 1st attempt.
3. No need to "FIX" the "Menu->Internet->Palemoon" entry, since it worked once booted to the desktop, and continued to work after completing as instructed.
In the same way, Palemoon also ran using the command prompt in the terminal
4. I'll save the session changes, reboot, and report back regarding the results..
Last edited by Sylvander on Sat 15 Sep 2018, 17:38, edited 1 time in total.
@mikeslr
Oh dear!
1. The changes made [during the session] are not being saved back to the slackosave, even though I clicked the "save" icon on the desktop [immediately prior to reboot], then during reboot chose to save a 2nd time.
a. e.g. The "/opt/palemon" and "/root/.moonchild productions" full-folders are still present [no symbolic links].
2. As expected, the "/mnt/home/palemoon" and "/mnt/home/palemoon/.moonchild productions" folders are present.
3. Strange that the changes are not being saved!
How to overcome the problem in 1 above?
Use a 2nd Puppy to make the changes within the slackosave file?
Oh dear!
1. The changes made [during the session] are not being saved back to the slackosave, even though I clicked the "save" icon on the desktop [immediately prior to reboot], then during reboot chose to save a 2nd time.
a. e.g. The "/opt/palemon" and "/root/.moonchild productions" full-folders are still present [no symbolic links].
2. As expected, the "/mnt/home/palemoon" and "/mnt/home/palemoon/.moonchild productions" folders are present.
3. Strange that the changes are not being saved!
How to overcome the problem in 1 above?
Use a 2nd Puppy to make the changes within the slackosave file?
Changing Palemoon’s profile name
I have finally figured out how to change Palemoon's awful profile name, /root/.moonchild productions to something more linux appropriate (no spaces). In the process I figured out how to run multiple versions of Palemoon without them sharing the same profile. See My HowTo for details.
In the process I figured out how to run multiple versions of Palemoon without them sharing the same profile. See My HowTo for details.First #4. With the changes not Saved, the Menu and opening Palemoon via the command may still be using /opt/palemoon/palemoon.Sylvander wrote:@mikeslr
Oh dear!
1. The changes made [during the session] are not being saved back to the slackosave, even though I clicked the "save" icon on the desktop [immediately prior to reboot], then during reboot chose to save a 2nd time.
a. e.g. The "/opt/palemon" and "/root/.moonchild productions" full-folders are still present [no symbolic links].
2. As expected, the "/mnt/home/palemoon" and "/mnt/home/palemoon/.moonchild productions" folders are present.
3. Strange that the changes are not being saved!
How to overcome the problem in 1 above?
Use a 2nd Puppy to make the changes within the slackosave file?
4. From prior post No need to "FIX" the "Menu->Internet->Palemoon" entry, since it worked once booted to the desktop, and continued to work after completing as instructed.
In the same way, Palemoon also ran using the command prompt in the terminal
IS IT POSSIBLE THAT YOU DON'T HAVE ANY AVAILABLE ROOM IN YOUR SAVEFILE TO PRESERVE ANY CHANGES? Let's try creating some. Resize your SaveFile, adding maybe just 32 Mbs.
What frugal Puppies do on FIRST bootup is to copy some files into RAM and create in RAM (inodes) pointers to the location where the rest of an application is located. When you create a SaveFile, the existing pointers are copied from RAM into your SaveFile. If Palemoon was part of your original Puppy, at first the inodes would point to the the /opt/palemoon folder in Puppy_Version_Number.sfs not your SaveFile. Later, as you added bookmarks, addons and configured Palemoon, those changes would be written to your SaveFile and the inodes would point to them in your SaveFile. Similarly, as you upgraded Palemoon, the upgrades would be written to the SaveFile and the inodes would point to those upgrades in your SaveFile.
Deleting a builtin application doesn't remove the application from the Puppy_Version_Number.sfs. It just writes "white-outs" as inodes which essentially tells the operating system "stop". These would be Saved to the SaveFile so that in the future if you try to run the application it won't. But what we want to have happen is that the inodes point to the palemoon folder and its contents at /mnt/home/palemoon.
While inodes are small, perhaps deleting /opt/palemoon requires a lot of them which takes up space in your SaveFile; especially if they are not immediately being replaced by inodes pointing to /mnt/home/palemoon. So, let's leave that for last. If palemoon was a builtin, what you'll recover is the space being used by the upgrades.
What is important is to change the bash-script or symbolic link in /usr/bin [or wherever it happens to be] so that the palemoon in /mnt/home/palemoon rather than the one in /opt/palemoon will be used. That change creates the inodes pointing to the /mnt/home/palemoon folder and its files.
So, after resizing the SaveFile, make that change and reboot. After rebooting, delete the /root/.moonchild productions folder and symlink /mnt/home/palemoon/.moonchild productions to /root. Save and reboot. On reboot, open rox to /root and Left-click its Eye. /root/.moonchild productions should show up as a symbolic link. Hovering your mouse cursor on it should show that it points to /mnt/home/palemoon/.moonchild productions.
Last edited by mikeslr on Sat 15 Sep 2018, 23:09, edited 1 time in total.
Maybe...
I recall that when dragging directories around to be dragged back as symlinks, one must make a save after the first step of cut/pasting the directory elsewhere. I think SFR hinted that to me once while having a similar issue, and (IIRC) it has to do with Linux fundamentally not allowing replacing one identically-named directory with another (or it's symlink) - and Puppy not recognizing one as being removed/deleted until a save is performed - otherwise, Puppy still "sees" it as there, and won't successfully copy the (identically-named) symlink back.
Something like that. And it worked for me! So Sylvander; drag/drop your Palemoon directory to outside/wherever... then make a save - and only after that, continue on with the dragging/pasting back of the symlink(s), and saving again.
Bob
I recall that when dragging directories around to be dragged back as symlinks, one must make a save after the first step of cut/pasting the directory elsewhere. I think SFR hinted that to me once while having a similar issue, and (IIRC) it has to do with Linux fundamentally not allowing replacing one identically-named directory with another (or it's symlink) - and Puppy not recognizing one as being removed/deleted until a save is performed - otherwise, Puppy still "sees" it as there, and won't successfully copy the (identically-named) symlink back.
Something like that. And it worked for me! So Sylvander; drag/drop your Palemoon directory to outside/wherever... then make a save - and only after that, continue on with the dragging/pasting back of the symlink(s), and saving again.
Bob
Hi Moat,
You may be right. But at this point sylvander already has the necessary palemoon folder at /mnt/home. So we're really saying pretty much the same thing. Perhaps, what he should do is delete the bash/script or symbolic link at /usr/bin --or wherever it happens to be-- Save, reboot and then drag /mnt/home/palemoon/palemoon (binary) to that location selecting Link(relative), Save and reboot.
Then delete /root/.moonchild productions, Save and reboot. Then drag /mnt/home/palemoon/.moonchild productions to /root, Select Link(relative), Save and reboot. Note the "."dot before moonchild: Left-click rox's eye to see those hidden folders.
And last, delete the /opt/palemoon folder to recover whatever space is being taken up in the SaveFile by upgrades to Palemoon. Save and reboot.
I haven't had to do that. But I never allow the available space in my SaveFile to fall below 100 Mbs.
mikesLr
You may be right. But at this point sylvander already has the necessary palemoon folder at /mnt/home. So we're really saying pretty much the same thing. Perhaps, what he should do is delete the bash/script or symbolic link at /usr/bin --or wherever it happens to be-- Save, reboot and then drag /mnt/home/palemoon/palemoon (binary) to that location selecting Link(relative), Save and reboot.
Then delete /root/.moonchild productions, Save and reboot. Then drag /mnt/home/palemoon/.moonchild productions to /root, Select Link(relative), Save and reboot. Note the "."dot before moonchild: Left-click rox's eye to see those hidden folders.
And last, delete the /opt/palemoon folder to recover whatever space is being taken up in the SaveFile by upgrades to Palemoon. Save and reboot.
I haven't had to do that. But I never allow the available space in my SaveFile to fall below 100 Mbs.
mikesLr
1.
I'm trying to avoid increasing the size of my slackosave beyond its present 2.0GB.
At the beginning of all of this it had 466M free space and now has 476M free.
Isn't that enough?
2.
3. I believe I understand your last post instructions, and will implement those once 1 above is decided.
4.
Hence, not included in the original Slacko ISO?
b. I save all PET files [either installed, or that I may want to install] in a folder on a particular Flash Drive.
In the folder "/mnt/sdb1/Puppy/pet" I have:
"palemoon-25.5.0.pet"
And in the sub-folder = "/mnt/sdb1/Puppy/pet/Palemoon" there is:
"palemoon-27.6.2-p4-glibc219tweak.pet"
"openssl-1.0.2l-i686.pet"
It's possible I installed these in sequence, and then installed version 28.0.0.
Cannot find the PET file for that.
Is this really necessary?mikeslr wrote:Resize your SaveFile, adding maybe just 32 Mbs.
I'm trying to avoid increasing the size of my slackosave beyond its present 2.0GB.
At the beginning of all of this it had 466M free space and now has 476M free.
Isn't that enough?
2.
See answer 1 above.mikeslr wrote:I never allow the available space in my SaveFile to fall below 100 Mbs.
3. I believe I understand your last post instructions, and will implement those once 1 above is decided.
4.
a. I mounted the optical disk file system, then mounted the slacko SFS file, and searched all mounted filesystems for "palemoon", but found nothing on the SFS.mikeslr wrote:If Palemoon was part of your original Puppy
Hence, not included in the original Slacko ISO?
b. I save all PET files [either installed, or that I may want to install] in a folder on a particular Flash Drive.
In the folder "/mnt/sdb1/Puppy/pet" I have:
"palemoon-25.5.0.pet"
And in the sub-folder = "/mnt/sdb1/Puppy/pet/Palemoon" there is:
"palemoon-27.6.2-p4-glibc219tweak.pet"
"openssl-1.0.2l-i686.pet"
It's possible I installed these in sequence, and then installed version 28.0.0.
Cannot find the PET file for that.
See this thread...
Changing Palemoon’s profile name
Its content may be important/useful.
1. I have warning [broken link] at:
"/opt/palemoon/palemoon"
"/usr/bin/palemoon"
2. Interresting comments:
a. In http://murga-linux.com/puppy/viewtopic.php?p=1004706#1004706
"For some reason it reverted to the awful /root/.moonchild productions if I didn’t cd in first and then execute palemoon."
b. In http://murga-linux.com/puppy/viewtopic.php?p=1004714#1004714
" I am using a slightly unusual .pet (palemoon with "glibctweak"). Not sure where I got it from, but it runs palemoon from user/lib/palemoon so I modded the application.ini profile to specify that."
I may have installed "palemoon-27.6.2-p4-glibc219tweak.pet".
But I have no "user/lib/palemoon" folder or file.
I hope the above is [potentially] helpful rather than confusing matters.
I'm trying to give you info to warn/inform.
Changing Palemoon’s profile name
Its content may be important/useful.
1. I have warning [broken link] at:
"/opt/palemoon/palemoon"
"/usr/bin/palemoon"
2. Interresting comments:
a. In http://murga-linux.com/puppy/viewtopic.php?p=1004706#1004706
"For some reason it reverted to the awful /root/.moonchild productions if I didn’t cd in first and then execute palemoon."
b. In http://murga-linux.com/puppy/viewtopic.php?p=1004714#1004714
" I am using a slightly unusual .pet (palemoon with "glibctweak"). Not sure where I got it from, but it runs palemoon from user/lib/palemoon so I modded the application.ini profile to specify that."
I may have installed "palemoon-27.6.2-p4-glibc219tweak.pet".
But I have no "user/lib/palemoon" folder or file.
I hope the above is [potentially] helpful rather than confusing matters.
I'm trying to give you info to warn/inform.
Hi Sylvander,
From the info you provided there's no need to resize. Lack of space in a SaveFile is sometimes why a change can't be preserved. But that's not your situation.
Try making the changes one step at a time, Saving and rebooting between each step as indicated here, http://www.murga-linux.com/puppy/viewto ... 36#1004736.
Keep us posted, especially if after deleting the current palemoon script or symbolic link at /usr/bin [or wherever it is] and Saving it shows up on reboot.
mikesLr
From the info you provided there's no need to resize. Lack of space in a SaveFile is sometimes why a change can't be preserved. But that's not your situation.
Try making the changes one step at a time, Saving and rebooting between each step as indicated here, http://www.murga-linux.com/puppy/viewto ... 36#1004736.
Keep us posted, especially if after deleting the current palemoon script or symbolic link at /usr/bin [or wherever it is] and Saving it shows up on reboot.
mikesLr
success!
Fingers crossed, all is looking good so far.
All the changes took effect.
Palemoon runs from both the Menu and the terminal command prompt.
I believe I can detect that it is very slightly slower than normal to appear.
The version is 28.0.0 (32-bit).
Aught I to attempt to "Check for Updates" and update [to 28.0.1]?
I first restored a backup of my slackosave and only then completed ALL of your steps, including...
"Perhaps, what he should do is delete the bash/script or symbolic link at /usr/bin..........Save, reboot and then drag /mnt/home/palemoon/palemoon (binary) to that location selecting Link(relative), Save and reboot."
The free space in the slackosave has increased to 645M.
Fingers crossed, all is looking good so far.
All the changes took effect.
Palemoon runs from both the Menu and the terminal command prompt.
I believe I can detect that it is very slightly slower than normal to appear.
The version is 28.0.0 (32-bit).
Aught I to attempt to "Check for Updates" and update [to 28.0.1]?
I first restored a backup of my slackosave and only then completed ALL of your steps, including...
"Perhaps, what he should do is delete the bash/script or symbolic link at /usr/bin..........Save, reboot and then drag /mnt/home/palemoon/palemoon (binary) to that location selecting Link(relative), Save and reboot."
The free space in the slackosave has increased to 645M.
Congratulations.Sylvander wrote:success!
Aught I to attempt to "Check for Updates" and update [to 28.0.1]?...
The free space in the slackosave has increased to 645M.
Might as well try updating. But note, don't use Menu>Internet>Palemoon-updater if it still exists. (a) It probably won't work; but (b) if it tries to run it was designed to update palemoon at /opt so might just make a mess.
Palemoon 28 and above updates from the Help section at the top of the GUI: Help>About Palemoon>Check for Updates.
There may be some more "clean-up" relating to /opt/Palemoon. If Palemoon-Updater shows on your Menu, browse to /usr/share/applications/ and delete the Palemoon-Updater.desktop.
That file calls /usr/bin/pminstaller.sh. You can delete that as well. However, on my system it showed as "locked". So in order to delete it, you may have to first browse to /tmp/pminstaller.lock and delete it.
Don't worry if the latter two deletions don't "stick". They don't take up much space and after deleting the palemoon-updater.desktop they don't do anything.
By the way, I'm kind of embarrassed.
I had forgotten that as of version 28, Palemoon is designed as portable. It wasn't necessary to copy/move Palemoon out of /opt. You could just have downloaded the bzipped tarball from here, https://linux.palemoon.org/ unpacked it and moved the resulting palemoon folder to /mnt/home.You still would have had to edit the file at /usr/bin to point to palemoon's location. And because you used your old profile, moving it out of /root/, you not only freed up space in your SaveFile, but you didn't have to export bookmarks before deleting /opt/palemoon, then importing them into /mnt/home/palemoon. And if you use addons, you didn't have to install them into your new version.
Edit: Oh, yah
You still would have had to delete /opt/palemoon and /root/.moonchild productions and create the symlink there to /mnt/home/palemoon/.moonchild productions. I guess the amount of work either way was about the same.mikesLr
1.
Now version 28.0.1.
I've already saved the changes and rebooted.
Is there any need to make a "Pupsave Hot Backup" of my slackosave?
Any changes caused by the update, that are held within the slackosave?
Or are all the updates made to the files that are now held under the "/mnt/home" folder?
2.
3.
4.
My thanks to ALL for each contribution.
Completed successfully.mikeslr wrote:Might as well try updating.
Now version 28.0.1.
I've already saved the changes and rebooted.
Is there any need to make a "Pupsave Hot Backup" of my slackosave?
Any changes caused by the update, that are held within the slackosave?
Or are all the updates made to the files that are now held under the "/mnt/home" folder?
2.
It doesn't exist.mikeslr wrote:don't use Menu>Internet>Palemoon-updater if it still exists.
3.
This is what I used.mikeslr wrote:Palemoon 28 and above updates from the Help section at the top of the GUI: Help>About Palemoon>Check for Updates.
4.
I'm happy with what has been done, and also the successful outcome, so no regrets.mikeslr wrote:I guess the amount of work either way was about the same.
My thanks to ALL for each contribution.
For anyone using the newest version of Palemoon.
Make sure you are using the latest version.
Make sure you are using the latest version.
v28.0.1 (2018-08-31)
This is a bugfix point release to address serious performance bottlenecks and general run-time issues (UI slowness, crashes, hangs) with the browser. Once again this impacted 32-bit operating systems more severely than 64-bit ones due to its more limited address space that would get flooded with bogus data.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
a_salty_dogg
- Posts: 180
- Joined: Sun 15 Dec 2013, 19:08
Still suffering the same Youtube problem/bug with 28.0.1 as I was with 28.0.0;
Am I alone in getting this? Happens with the first instance of trying to play a Youtube video in every session on every Puppy I've updated to 28.
Easily fixed by clicking twice on the pause/play button, then the video starts, but still xxxxing annoying!If playback doesn't begin shortly, try restarting your device
Am I alone in getting this? Happens with the first instance of trying to play a Youtube video in every session on every Puppy I've updated to 28.
- Attachments
-
- capture4397.png
- (11.18 KiB) Downloaded 1174 times
I had no problem playing videos with 28.0.0.a_salty_dogg wrote:Am I alone in getting this?
Neither am I having any problem with 28.0.1.
Running on Slacko-5.7.0-pae.
I tell a lie...
I think it was when running 28.0.0...
After playing a certain number of videos [in each new session], they would no longer play.
I don't get that in 28.0.1.
When it happened, I would copy and paste the URL into Slimjet, and run it there.
-
Walter Dnes
- Posts: 153
- Joined: Fri 30 Dec 2016, 10:56
Do you have media.autoplay.enabled set to false? This toggle is a tradeoff...a_salty_dogg wrote:Still suffering the same Youtube problem/bug with 28.0.1 as I was with 28.0.0;Easily fixed by clicking twice on the pause/play button, then the video starts, but still xxxxing annoying!If playback doesn't begin shortly, try restarting your device
Am I alone in getting this? Happens with the first instance of trying to play a Youtube video in every session on every Puppy I've updated to 28.
- if set "false", annoying HTML5 ads won't autoplay, but Youtube will need extra clicks
- if set "true", annoying HTML5 ads will autoplay, and Youtube will also autoplay
New release out today:
Pale Moon 28.1.0 has been released. This is a development release focusing on performance, bugfixes and security. More information in the release notes!
http://www.palemoon.org/releasenotes.shtml
Pale Moon 28.1.0 has been released. This is a development release focusing on performance, bugfixes and security. More information in the release notes!
http://www.palemoon.org/releasenotes.shtml