Firefox Quantum portable with apulse All-in
Best location for FF portable folder
Hey Fred & Mike -
I was getting the impression that it is not a good idea to keep the FFportable
folder in root if I want to conserve RAM on bootup.
Then today I saw a part of a post by mikesir that seemed to apply:
"Except for portable applications, such as firefox portable, which are built to store their settings and configurations in the folders from which they are run, all applications store such settings and configurations in (usually hidden) files and folders in /root. Files in /root are among those always copied into RAM on bootup and, so, always take up RAM".
This was on a thread started yesterday by Anders3 titled " Installation on USB and harddrive, speed differences." in the Beginners Help forum.
My question is that if I now try to move the FFportable folder and the FFfiles that seem to have something to do with it, which files are also in root, will I thereby mess up something?
And, if it's okay to move them, where would be a good location to locate them?
I hope this is not off topic for your thread, Fred.
Regards,
retry3
I was getting the impression that it is not a good idea to keep the FFportable
folder in root if I want to conserve RAM on bootup.
Then today I saw a part of a post by mikesir that seemed to apply:
"Except for portable applications, such as firefox portable, which are built to store their settings and configurations in the folders from which they are run, all applications store such settings and configurations in (usually hidden) files and folders in /root. Files in /root are among those always copied into RAM on bootup and, so, always take up RAM".
This was on a thread started yesterday by Anders3 titled " Installation on USB and harddrive, speed differences." in the Beginners Help forum.
My question is that if I now try to move the FFportable folder and the FFfiles that seem to have something to do with it, which files are also in root, will I thereby mess up something?
And, if it's okay to move them, where would be a good location to locate them?
I hope this is not off topic for your thread, Fred.
Regards,
retry3
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
@ retry3:-
Ah. You're talking about the Firefox stuff still sitting in /root after putting the portable install on the USB stick, I take it?
Since you now have your main browser set-up as a 'portable', on the USB drive, that's safe. It's not going to go anywhere. All that Firefox-related stuff left behind in /root, all those various bits & pieces, you can delete them. All of them.....every last item. Because all they're now doing is sitting around, taking up 'Puppy'-space in your save-file/folder.
FF68esr will, like regular Firefox 'Quantum', periodically update itself (though these won't be anything like as frequent as 'regular' FF). You'll be safe for quite a while, until the next ESR release comes out. Which, if Mozilla follow their usual routine, will probably be around FF75/76. And that's many months away yet.
Hope that answers that one, anyway.
Mike.
Ah. You're talking about the Firefox stuff still sitting in /root after putting the portable install on the USB stick, I take it?
Since you now have your main browser set-up as a 'portable', on the USB drive, that's safe. It's not going to go anywhere. All that Firefox-related stuff left behind in /root, all those various bits & pieces, you can delete them. All of them.....every last item. Because all they're now doing is sitting around, taking up 'Puppy'-space in your save-file/folder.
FF68esr will, like regular Firefox 'Quantum', periodically update itself (though these won't be anything like as frequent as 'regular' FF). You'll be safe for quite a while, until the next ESR release comes out. Which, if Mozilla follow their usual routine, will probably be around FF75/76. And that's many months away yet.
Hope that answers that one, anyway.
Mike.
-
- Posts: 120
- Joined: Wed 15 Feb 2017, 14:00
Didn't work
Hello, I am having struggles with the demon satanic spawn called PulseAudio and firefox.
I'm using
Linux Kernel: 4.9.71 (i686)
Kernel Version: #1 SMP Thu Dec 21 17:03:45 EST 2017
PAE Enabled: Yes
Kernel Command Line:
psubdir=stretch pmedia=atahd pfix=fsck,copy
Distro: Dpup Stretch 7.5
Window Manager: JWM v2.3.7
I have been using firefox quantum for a while, and out of the blue pulseaudio demands glibc 2.25 and also can't play audio nomatter what I do.
pulseaudio -D tells me basically to go fuck myself (can't start daemon, bohoo.)
Your ESR version of apulse+ff throws me this:
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
[apulse] [error] do_connect_pcm: can't get initial hw parameters for playback device "default". Error code 1 (Operation not permitted)
[apulse] [error] do_connect_pcm: failed to open ALSA device. Apulse does no resampling or format conversion, leaving that task to ALSA plugins. Ensure that selected device is capable of playing a particular sample format at a particular rate. They have to be supported by either hardware directly, or by "plug" and "dmix" ALSA plugins which will perform required conversions on CPU.
[Child 6567, MediaPlayback #1] WARNING: 8b4114c0 OpenCubeb() failed to init cubeb: file /builds/worker/workspace/build/src/dom/media/AudioStream.cpp, line 382
[Child 6567, MediaPlayback #1] WARNING: Decoder=9583dec0 [OnMediaSinkAudioError]: file /builds/worker/workspace/build/src/dom/media/MediaDecoderStateMachine.cpp, line 3639
Can this be solved? The audio works as usual, only firefox keeps screwing my day.
Thanks!
I'm using
Linux Kernel: 4.9.71 (i686)
Kernel Version: #1 SMP Thu Dec 21 17:03:45 EST 2017
PAE Enabled: Yes
Kernel Command Line:
psubdir=stretch pmedia=atahd pfix=fsck,copy
Distro: Dpup Stretch 7.5
Window Manager: JWM v2.3.7
I have been using firefox quantum for a while, and out of the blue pulseaudio demands glibc 2.25 and also can't play audio nomatter what I do.
pulseaudio -D tells me basically to go fuck myself (can't start daemon, bohoo.)
Your ESR version of apulse+ff throws me this:
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
[apulse] [error] do_connect_pcm: can't get initial hw parameters for playback device "default". Error code 1 (Operation not permitted)
[apulse] [error] do_connect_pcm: failed to open ALSA device. Apulse does no resampling or format conversion, leaving that task to ALSA plugins. Ensure that selected device is capable of playing a particular sample format at a particular rate. They have to be supported by either hardware directly, or by "plug" and "dmix" ALSA plugins which will perform required conversions on CPU.
[Child 6567, MediaPlayback #1] WARNING: 8b4114c0 OpenCubeb() failed to init cubeb: file /builds/worker/workspace/build/src/dom/media/AudioStream.cpp, line 382
[Child 6567, MediaPlayback #1] WARNING: Decoder=9583dec0 [OnMediaSinkAudioError]: file /builds/worker/workspace/build/src/dom/media/MediaDecoderStateMachine.cpp, line 3639
Can this be solved? The audio works as usual, only firefox keeps screwing my day.
Thanks!
I haven't used this portable version, but since it includes apulse it shouldn't need pulseaudio, however, I always use pulseaudio with my Firefox installs - and it always works for me. It does complain when you start it as root user using the following, but just ignore the warning messages, it still does actually start up okay:
wiak
Code: Select all
pulseaudio --start
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
In my experiments with pulseaudio and puppy I always succeded to install it: install it in PPM even if declared already installed. Search for default.pa file with pfind and comment in it the lines which are issues for starting the pulseaudio daemon with "pulseaudio --start". Pay attention to change the following lines in default.pa matching your hardware:
Code: Select all
load-module module-alsa-sink device=hw:1,0
load-module module-alsa-source device=hw:0,0
-
- Posts: 120
- Joined: Wed 15 Feb 2017, 14:00
Hello, this is my issue, I downloaded pulseaudio from the ppm and it only bothers to tell me:wiak wrote:I haven't used this portable version, but since it includes apulse it shouldn't need pulseaudio, however, I always use pulseaudio with my Firefox installs - and it always works for me. It does complain when you start it as root user using the following, but just ignore the warning messages, it still does actually start up okay:
wiakCode: Select all
pulseaudio --start
Code: Select all
W: [pulseaudio] main.c: Este programa no tiene por qué ser ejecutado como root (a menos que --system sea especificado).
E: [pulseaudio] main.c: Falló el inicio del demonio.
-
- Posts: 120
- Joined: Wed 15 Feb 2017, 14:00
Hello, that didn't work either, I couldn't start pulseaudio still, I didn't change anything in this computer and still the thing decided to stop working, and this computer is used by an elder who only uses firefox.watchdog wrote:In my experiments with pulseaudio and puppy I always succeded to install it: install it in PPM even if declared already installed. Search for default.pa file with pfind and comment in it the lines which are issues for starting the pulseaudio daemon with "pulseaudio --start". Pay attention to change the following lines in default.pa matching your hardware:
Code: Select all
load-module module-alsa-sink device=hw:1,0 load-module module-alsa-source device=hw:0,0
What can I do?
thanks for the help.
You said
Where do I check if my HW numbers are?Pay attention to change the following lines in default.pa matching your hardware:
It's an old laptop, here's the info:
Code: Select all
!!Loaded ALSA modules
!!-------------------
snd_hda_intel
snd_pcsp
!!Sound Servers on this system
!!----------------------------
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - No
!!Soundcards recognised by ALSA
!!-----------------------------
0 [MID ]: HDA-Intel - HDA Intel MID
HDA Intel MID at 0xfc800000 irq 26
1 [pcsp ]: PC-Speaker - pcsp
Internal PC-Speaker at port 0x61
!!PCI Soundcards installed in the system
!!--------------------------------------
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
It's difficult to help when you have not in hands the machine. I suggest to try buster 64 bit by josejp2424 which has built-in working pulseaudio. Have you a cpu 64 bit capable?
http://www.murga-linux.com/puppy/viewtopic.php?t=116615
LATER: I have tested pulseudio in my stretch-7.5 install. Install pulseaudio by PPM. Install dependencies: libspeexdsp1, libwebrtc-audio-processing1, pulseaudio-utils and its deps. Change /etc/pulse/default.pa as the following:
It works for me with the lines:
http://www.murga-linux.com/puppy/viewtopic.php?t=116615
LATER: I have tested pulseudio in my stretch-7.5 install. Install pulseaudio by PPM. Install dependencies: libspeexdsp1, libwebrtc-audio-processing1, pulseaudio-utils and its deps. Change /etc/pulse/default.pa as the following:
Code: Select all
#!/usr/bin/pulseaudio -nF
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see <http://www.gnu.org/licenses/>.
# This startup script is used only if PulseAudio is started per-user
# (i.e. not in system mode)
.fail
### Automatically restore the volume of streams and devices
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
### Automatically augment property information from .desktop files
### stored in /usr/share/application
load-module module-augment-properties
### Should be after module-*-restore but before module-*-detect
load-module module-switch-on-port-available
### Load audio drivers statically
### (it's probably better to not load these drivers manually, but instead
### use module-udev-detect -- see below -- for doing this automatically)
load-module module-alsa-sink device=hw:0,0
load-module module-alsa-source device=hw:0,0
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input
#load-module module-null-sink
#load-module module-pipe-sink
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev support)
load-module module-detect
.endif
### Automatically connect sink and source if JACK server is present
#.ifexists module-jackdbus-detect.so
#.nofail
#load-module module-jackdbus-detect channels=2
#.fail
#.endif
### Automatically load driver modules for Bluetooth hardware
#.ifexists module-bluetooth-policy.so
#load-module module-bluetooth-policy
#.endif
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif
### Load several protocols
#.ifexists module-esound-protocol-unix.so
#load-module module-esound-protocol-unix
#.endif
#load-module module-native-protocol-unix
### Network access (may be configured with paprefs, so leave this commented
### here if you plan to use paprefs)
#load-module module-esound-protocol-tcp
#load-module module-native-protocol-tcp
#load-module module-zeroconf-publish
### Load the RTP receiver module (also configured via paprefs, see above)
#load-module module-rtp-recv
### Load the RTP sender module (also configured via paprefs, see above)
#load-module module-null-sink sink_name=rtp format=s16be channels=2 rate=44100 sink_properties="device.description='RTP Multicast Sink'"
#load-module module-rtp-send source=rtp.monitor
### Load additional modules from GConf settings. This can be configured with the paprefs tool.
### Please keep in mind that the modules configured by paprefs might conflict with manually
### loaded modules.
#.ifexists module-gconf.so
#.nofail
#load-module module-gconf
#.fail
#.endif
### Automatically restore the default sink/source when changed by the user
### during runtime
### NOTE: This should be loaded as early as possible so that subsequent modules
### that look up the default sink/source get the right value
load-module module-default-device-restore
### Automatically move streams to the default sink if the sink they are
### connected to dies, similar for sources
load-module module-rescue-streams
### Make sure we always have a sink around, even if it is a null sink.
load-module module-always-sink
### Honour intended role device property
load-module module-intended-roles
### Automatically suspend sinks/sources that become idle for too long
load-module module-suspend-on-idle
### If autoexit on idle is enabled we want to make sure we only quit
### when no local session needs us anymore.
#.ifexists module-console-kit.so
#load-module module-console-kit
#.endif
#.ifexists module-systemd-login.so
#load-module module-systemd-login
#.endif
### Enable positioned event sounds
#load-module module-position-event-sounds
### Cork music/video streams when a phone stream is active
#load-module module-role-cork
### Modules to allow autoloading of filters (such as echo cancellation)
### on demand. module-filter-heuristics tries to determine what filters
### make sense, and module-filter-apply does the heavy-lifting of
### loading modules and rerouting streams.
#load-module module-filter-heuristics
#load-module module-filter-apply
### Make some devices default
#set-default-sink output
#set-default-source input
Code: Select all
load-module module-alsa-sink device=hw:0,0
load-module module-alsa-source device=hw:0,0
Code: Select all
# pulseaudio --kill
# pulseaudio --start
W: [pulseaudio] main.c: Questo programma non è pensato per essere eseguito come root (a meno di specificare --system).
#
-
- Posts: 120
- Joined: Wed 15 Feb 2017, 14:00
Thanks watchdog, did as you suggested, and it didn't work, it worked before but still it's an unknown even that fucked everything related with pulseaudio that fucked up.
I will try again later, sadly a 64 bit os doesn't really make sense, for the use of this old laptop. But I will see if it works.
Thanks again, I don't think it's a "pulseaudio" issue because even apulse doesn't work, it's something somewhere that I can't trace that is giving me problems.
Have a nice sunday, don't worry anymore
I will try again later, sadly a 64 bit os doesn't really make sense, for the use of this old laptop. But I will see if it works.
Thanks again, I don't think it's a "pulseaudio" issue because even apulse doesn't work, it's something somewhere that I can't trace that is giving me problems.
Have a nice sunday, don't worry anymore
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
The ff script should be executable already. Version 75.0 now, works for me, what do you see when running from terminal standing in the directory where 'ff' is located:MrAccident wrote:It doesn't work for me; nothing happens when I click on "ff" file. What does it mean to make the file - executable? Maybe that's the problem ― because I didn't do anything about it.
Code: Select all
./ff
And which Puppy you use ?
It's required to have gtk3 installed, see info and link to .pet at first post
Fred
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
@ fredx181 - am using Slacko 5.7.0
Terminal:
I have gtk+3-3.4.4
Should I install the glib-2.0_schemas.pet?
I think I remember that I had the same problem in the past, probably with the first version - with the full file, and then it was solved, then happened again; but I started to use a different version, or just Pale Moon - so left this version with the problem.
Terminal:
Now it's the official FireFox with the 32bit-additions. And tried a few of the other options in this thread; every time ― nothing happens when I click on the "ff" file.find: paths must precede expression: firefox-bin
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression]
# ./ff
./ff: line 6: /initrd/mnt/dev_save/firefox/firefox: cannot execute binary file
I have gtk+3-3.4.4
Should I install the glib-2.0_schemas.pet?
I think I remember that I had the same problem in the past, probably with the first version - with the full file, and then it was solved, then happened again; but I started to use a different version, or just Pale Moon - so left this version with the problem.
That message means often that you use the wrong architecture (e.g. 64-bit firefox on 32-bit OS, or other way around) but I may be wrong...cannot execute binary file
EDIT did you use the installer script from attached here ?:
http://murga-linux.com/puppy/viewtopic. ... 19#1025219
(it should detect correct architecture)
Fred
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
Every time I've chosen 32-bit. How can I find that out?
If you mean where it says:
If you mean where it says:
Yes; and 32bit-additions.++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
EDIT: Another way is to download newest firefox from Here or Here in your language
Unpack it, firefox directory will appear, then download: 32bit-additions or 64bit-additions and extract in the new firefox folder (contains "ff" script and "extralibs" folder)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Find out architecture of your OS, you mean ?MrAccident wrote:Every time I've chosen 32-bit. How can I find that out?
Code: Select all
uname -m
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53