source: xsoft/graphweb/firefox.xml@ c4e7ae2

11.2 11.3 12.0 12.1 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18 xry111/soup3 xry111/xf86-video-removal
Last change on this file since c4e7ae2 was c4e7ae2, checked in by Ken Moffat <ken@…>, 22 months ago

Fix firefox and thunderbird for current cbindgen.

  • Property mode set to 100644
File size: 25.1 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;esr/source/firefox-&firefox-version;esr.source.tar.xz">
8 <!ENTITY firefox-download-ftp " ">
9 <!ENTITY firefox-md5sum "c22765dc34c94035ebd83b998c90de33">
10 <!ENTITY firefox-size "363 MB">
11 <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
12 But the extra cached cargo files, if any, seem to be minimal -->
13 <!ENTITY firefox-buildsize "6.6 GB (193 MB installed) without tests">
14 <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
15 most practical way to get a timing on a machine with more cores, if taking
16 cores offline is not practical. If in doubt, round up -->
17 <!ENTITY firefox-time "25 SBU (on a typical 4-core machine) without tests">
18]>
19
20<sect1 id="firefox" xreflabel="Firefox-&firefox-version;">
21 <?dbhtml filename="firefox.html" ?>
22
23 <sect1info>
24 <date>$Date$</date>
25 </sect1info>
26
27 <title>Firefox-&firefox-version;</title>
28
29 <indexterm zone="firefox">
30 <primary sortas="a-Firefox">Firefox</primary>
31 </indexterm>
32
33 <sect2 role="package">
34 <title>Introduction to Firefox</title>
35
36 <para>
37 <application>Firefox</application> is a stand-alone browser based on the
38 <application>Mozilla</application> codebase.
39 </para>
40
41 &lfs111_checked;
42
43 <bridgehead renderas="sect3">Package Information</bridgehead>
44 <itemizedlist spacing="compact">
45 <listitem>
46 <para>
47 Download (HTTP): <ulink url="&firefox-download-http;"/>
48 </para>
49 </listitem>
50 <listitem>
51 <para>
52 Download (FTP): <ulink url="&firefox-download-ftp;"/>
53 </para>
54 </listitem>
55 <listitem>
56 <para>
57 Download MD5 sum: &firefox-md5sum;
58 </para>
59 </listitem>
60 <listitem>
61 <para>
62 Download size: &firefox-size;
63 </para>
64 </listitem>
65 <listitem>
66 <para>
67 Estimated disk space required: &firefox-buildsize;
68 </para>
69 </listitem>
70 <listitem>
71 <para>
72 Estimated build time: &firefox-time;
73 </para>
74 </listitem>
75 </itemizedlist>
76
77 <bridgehead renderas="sect3">Additional Downloads</bridgehead>
78 <itemizedlist spacing="compact">
79 <listitem>
80 <para>
81 Required patch:
82 <ulink url="&patch-root;/firefox-&firefox-version;esr-gcc12_fix-1.patch"/>
83 </para>
84 </listitem>
85 <listitem>
86 <para>
87 Recommended patch:
88 <ulink url="&patch-root;/firefox-&firefox-version;esr-disable_rust_test-1.patch"/>
89 </para>
90 </listitem>
91 </itemizedlist>
92
93 <note>
94 <para>
95 The directory name is firefox-&firefox-version;
96 </para>
97
98 <para>
99 Extracting the tarball
100 will reset the permissions of the current directory to 0755 if you
101 have permission to do that. If you do this in a directory where
102 the sticky bit is set, such
103 as <filename class="directory">/tmp</filename> it will end with error
104 messages:
105 </para>
106
107<literallayout>tar: .: Cannot utime: Operation not permitted
108tar: .: Cannot change mode to rwxr-xr-t: Operation not permitted
109tar: Exiting with failure status due to previous errors
110</literallayout>
111
112 <para>
113 This does finish with non-zero status, but it does
114 <emphasis>NOT</emphasis> mean there is a real problem.
115 Do not untar as the <systemitem class="username">root</systemitem> user
116 in a directory where the sticky bit is set - that will unset it.
117 </para>
118
119 <para>
120 As with other large packages which use C++ (or rust), the SBU times
121 to build this vary more widely than you might expect. The build times
122 will increase significantly if your machine has to swap.
123 </para>
124
125 <!-- commented, by 78.0 it seems to work reliably
126 <para>
127 The mach build system (Python scripts) can be somewhat unreliable: if
128 the build fails and reports an Error, it can still return a status of
129 success, causing a scripted build to try to install (which does not rerun
130 the build), fail during the preparations for installing, but still exit
131 with a status of success. Also, on occasion it may limit itself to only
132 running one set of jobs - that will make the build take about 3 times as
133 long as running with four sets of jobs.
134 </para>-->
135
136 <para>
137 Although upstream prefer to use <application>PulseAudio</application>,
138 for the moment <application>Alsa</application> can still be used. Both
139 may need runtime configuration to get sound working.
140 </para>
141 </note>
142
143 <bridgehead renderas="sect3">Firefox Dependencies</bridgehead>
144
145 <bridgehead renderas="sect4">Required</bridgehead>
146 <para role="required">
147 <xref linkend="autoconf213"/>,
148 <xref linkend="cbindgen"/>,
149 <xref linkend="dbus-glib"/>,
150 <xref linkend="gtk3"/>,
151 <xref linkend="libnotify"/>,
152 <xref linkend="llvm"/> (clang, used for bindgen even if using gcc),
153 <xref linkend="nodejs"/>,
154 <xref linkend="pulseaudio"/>
155 (or
156 <xref linkend="alsa-lib"/> if you edit the mozconfig;
157 now deprecated by mozilla), in either case please read the
158 Configuration Information,
159 <!-- rustc is required by cbindgen so not needed here
160 <xref linkend="rust"/>,-->
161 <xref linkend="python3"/> (rebuilt after installing <xref linkend="sqlite"/>),
162 <xref linkend="startup-notification"/>,
163 <xref linkend="unzip"/>,
164 <xref linkend="yasm"/>, and
165 <xref linkend="zip"/>
166 </para>
167
168 <bridgehead renderas="sect4">Recommended</bridgehead>
169 <para role="recommended">
170 <xref linkend="icu"/>,
171 <xref linkend="libevent"/>,
172 <xref linkend="libvpx"/>,
173 <xref linkend="libwebp"/>,
174 <xref linkend="nasm"/>,
175 <xref linkend="nss"/>
176 </para>
177
178 <note>
179 <para>
180 If you don't install recommended dependencies, then internal copies of
181 those packages will be used. They might be tested to work, but they can
182 be out of date or contain security holes.
183 </para>
184 </note>
185
186 <bridgehead renderas="sect4">Optional</bridgehead>
187 <para role="optional">
188 <xref linkend="curl"/>,
189 <xref linkend="doxygen"/>,
190 <xref role="runtime" linkend="ffmpeg"/> (runtime, to play mov, mp3 or mp4 files),
191 <!-- <phrase revision="sysv"><ulink url="https://sourceforge.net/projects/liboauth/files/">liboauth</ulink></phrase> -->
192 <xref linkend="liboauth"/>,
193 <!--<xref linkend="openjdk"/>, Not seen in logs -->
194 <xref linkend="valgrind"/>,
195 <xref linkend="wget"/>,
196 <xref linkend="wireless_tools"/>,
197 <ulink url="https://github.com/libproxy/libproxy">libproxy</ulink>
198 </para>
199
200 <para condition="html" role="usernotes">
201 User Notes: <ulink url="&blfs-wiki;/firefox"/>
202 </para>
203 </sect2>
204
205 <sect2 role="installation">
206 <title>Installation of Firefox</title>
207
208 <para>
209 The configuration of <application>Firefox</application> is accomplished
210 by creating a <filename>mozconfig</filename> file containing the desired
211 configuration options. A default <filename>mozconfig</filename> is
212 created below. To see the entire list of available configuration options
213 (and an abbreviated description of some of them), issue <command>./mach
214 configure &amp;&amp; ./configure --help | less</command>. You may also
215 wish to review the entire file and uncomment any other desired options.
216 Create the file by issuing the following command:
217 </para>
218
219<screen><userinput>cat &gt; mozconfig &lt;&lt; "EOF"
220<literal># If you have a multicore machine, all cores will be used by default.
221
222# If you have installed (or will install) wireless-tools, and you wish
223# to use geolocation web services, comment out this line
224ac_add_options --disable-necko-wifi
225
226# API Keys for geolocation APIs - necko-wifi (above) is required for MLS
227# Uncomment the following line if you wish to use Mozilla Location Service
228#ac_add_options --with-mozilla-api-keyfile=$PWD/mozilla-key
229
230# Uncomment the following line if you wish to use Google's geolocaton API
231# (needed for use with saved maps with Google Maps)
232#ac_add_options --with-google-location-service-api-keyfile=$PWD/google-key
233
234# startup-notification is required since firefox-78
235
236# Uncomment the following option if you have not installed PulseAudio
237#ac_add_options --disable-pulseaudio
238# or uncomment this if you installed alsa-lib instead of PulseAudio
239#ac_add_options --enable-alsa
240
241# Comment out following options if you have not installed
242# recommended dependencies:
243ac_add_options --with-system-icu
244ac_add_options --with-system-libevent
245ac_add_options --with-system-libvpx
246ac_add_options --with-system-nspr
247ac_add_options --with-system-nss
248ac_add_options --with-system-webp
249
250# Do not specify the gold linker which is not the default. It will take
251# longer and use more disk space when debug symbols are disabled.
252
253# libdavid (av1 decoder) requires nasm. Uncomment this if nasm
254# has not been installed.
255#ac_add_options --disable-av1
256
257# You cannot distribute the binary if you do this
258ac_add_options --enable-official-branding
259
260# Stripping is now enabled by default.
261# Uncomment these lines if you need to run a debugger:
262#ac_add_options --disable-strip
263#ac_add_options --disable-install-strip
264
265# Disabling debug symbols makes the build much smaller and a little
266# faster. Comment this if you need to run a debugger. Note: This is
267# required for compilation on i686.
268ac_add_options --disable-debug-symbols
269
270# The elf-hack is reported to cause failed installs (after successful builds)
271# on some machines. It is supposed to improve startup time and it shrinks
272# libxul.so by a few MB - comment this if you know your machine is not affected.
273ac_add_options --disable-elf-hack
274
275# The BLFS editors recommend not changing anything below this line:
276ac_add_options --prefix=/usr
277ac_add_options --enable-application=browser
278ac_add_options --disable-crashreporter
279ac_add_options --disable-updater
280# enabling the tests will use a lot more space and significantly
281# increase the build time, for no obvious benefit.
282ac_add_options --disable-tests
283
284# The default level of optimization again produces a working build with gcc.
285ac_add_options --enable-optimize
286
287ac_add_options --enable-system-ffi
288ac_add_options --enable-system-pixman
289
290ac_add_options --with-system-jpeg
291ac_add_options --with-system-png
292ac_add_options --with-system-zlib
293
294# The following option unsets Telemetry Reporting. With the Addons Fiasco,
295# Mozilla was found to be collecting user's data, including saved passwords and
296# web form data, without users consent. Mozilla was also found shipping updates
297# to systems without the user's knowledge or permission.
298# As a result of this, use the following command to permanently disable
299# telemetry reporting in Firefox.
300unset MOZ_TELEMETRY_REPORTING
301
302mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/firefox-build-dir</literal>
303EOF</userinput></screen>
304
305 <para>
306 Compile <application>Firefox</application> by issuing the following
307 commands:
308 </para>
309
310 <para>
311 First apply a patch which works around unexplained failures on some machines
312 (a message that a python check on libgkrust.a identified 1 networking
313 function, getsockname) in the rust static library.
314 </para>
315
316<screen><userinput>patch -Np1 -i ../firefox-&firefox-version;esr-disable_rust_test-1.patch</userinput></screen>
317
318 <para>
319 Now apply a patch which allows the build to complete when using gcc-12 or later.
320 </para>
321
322<screen><userinput>patch -Np1 -i ../firefox-&firefox-version;esr-gcc12_fix-1.patch</userinput></screen>
323
324 <para>
325 A change in cbindgen-0.24.2 causes a symbol to now be output by
326 cbindgen, but it has already been defined in a header. This sed
327 prevents the build eventually failing:
328 </para>
329
330<screen><userinput>sed -i '/ROOT_CLIP_CHAIN/d' gfx/webrender_bindings/webrender_ffi.h</userinput></screen>
331
332<!-- applying this for 11.1: upstream haven't make their mind yet
333 https://bugzilla.mozilla.org/show_bug.cgi?id=1729459 -->
334 <para>
335 If building on a 32 bit machine, the following sed works around
336 an issue with an incompatible <quote>double</quote> type in one
337 header file:
338 </para>
339
340<screen><userinput>case "$(uname -m)" in
341 i?86) sed -e '/typedef[ ]*double/s/double/long double/' \
342 -i modules/fdlibm/src/math_private.h ;;
343esac</userinput></screen>
344
345 <para>
346 If the geolocation APIs are needed:
347 </para>
348
349 <note>
350 <para>
351 <!-- Taken from Arch Linux - an immensely helpful link - Thanks -->
352 The Google and Mozilla API Keys below are specific to LFS. If using
353 these instructions for another distro, or if you intend to distribute
354 binary copies of the software using these instructions, please obtain
355 your own keys following the instructions located at
356 <ulink url="http://www.chromium.org/developers/how-tos/api-keys"/> and
357 <ulink url="https://location.services.mozilla.com/api"/> respectively.
358 <!-- BLFS Devs, register an account at Google with your
359 @linuxfromscratch.org email address, and I'll make you an administrator
360 for the 'Google APIs for LFS' project (where the API and OAuth keys
361 were created for use in the book).-->
362 </para>
363 </note>
364
365<screen><userinput>echo "AIzaSyDxKL42zsPjbke5O8_rPVpVrLrJ8aeE9rQ" > google-key
366echo "613364a7-9418-4c86-bcee-57e32fd70c23" > mozilla-key</userinput></screen>
367
368 <note>
369
370 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
371 href="../../xincludes/mozshm.xml"/>
372
373 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
374 href="../../xincludes/mozmach.xml"/>
375
376 </note>
377 <!--
378 <para>
379 If you are building on i686, apply a fix to prevent Internal Compiler
380 Errors in GCC-7+:
381 </para>
382
383<screen><userinput remap="pre">case $(uname -m) in
384 i?86) sed -i "562 s/mips64/i386/" gfx/skia/skia/third_party/skcms/src/Transform_inl.h ;;
385esac</userinput></screen>
386 -->
387<!--<para>
388 Apply a patch to allow this to be compiled with <xref linkend="rust"/>:
389 </para>
390
391<screen><userinput remap="pre">patch -p1 -i ../firefox-&firefox-version;esr-rustc1470-1.patch</userinput></screen>-->
392
393 <para>
394 Now invoke the Python <command>mach</command> script to compile the package.
395 </para>
396
397<screen><userinput>export CC=gcc CXX=g++ &amp;&amp;
398export MACH_USE_SYSTEM_PYTHON=1 &amp;&amp;
399export MOZBUILD_STATE_PATH=${PWD}/mozbuild &amp;&amp;
400./mach configure &amp;&amp;
401./mach build</userinput></screen>
402
403 <para>
404 The <filename>mozconfig</filename> above disables the tests because
405 they use a lot more time and disk space for no obvious benefit. If
406 you have nevertheless enabled them, you can run the tests by executing
407 <command>./mach gtest</command>. This will require a network connection,
408 and to be run from within an Xorg session - there is a popup dialog
409 when it fails to connect to ALSA (that does not create a failed test).
410 One or two tests will fail. To see the details of the failure(s) you
411 will need to log the output from that command so that you can review it.
412 </para>
413
414 <para>
415 Now, as the <systemitem class="username">root</systemitem> user:
416 </para>
417
418<screen role="root"><userinput>MACH_USE_SYSTEM_PYTHON=1 ./mach install</userinput></screen>
419
420 <para>
421 Empty the environment variables which were set above:
422 </para>
423
424<screen><userinput>unset CC CXX MACH_USE_SYSTEM_PYTHON MOZBUILD_STATE_PATH</userinput></screen>
425
426 </sect2>
427
428 <sect2 role="commands">
429 <title>Command Explanations</title>
430
431<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
432 href="../../xincludes/SIOCGSTAMP.xml"/>-->
433
434 <para>
435 <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer
436 <application>clang</application> so that they can use one compiler
437 everywhere. On the X86 architectures <application>clang</application>
438 now appears to support most of the same security-hardening options as
439 <application>GCC</application>.
440 <!-- supported in llvm-11
441 but the newer
442 <literal>-fstack-clash-protection</literal> is still not supported.-->
443 With the current versions and the default flags,
444 <application>GCC</application> creates a marginally bigger build but
445 takes typically 2 SBU less time on a 4-core machine using the mozconfig
446 above.
447 </para>
448
449 <para>
450 <command>export MOZBUILD_STATE_PATH=${PWD}/mozbuild</command>: The build
451 is now supposed to tell you that it intends to create <filename
452 class="directory">~/.mozbuild</filename>, and offer you an option to
453 press &lt;ENTER&gt; to accept this, or Ctrl-C to cancel and restart the
454 build after specifying the directory. In practice, the message may not
455 appear until after &lt;ENTER&gt; is keyed, i.e. the build stalls.
456 </para>
457
458 <para>
459 That directory is used for a (probably random) telemetry identifier.
460 Creating this in the build directory, and deleting that after the
461 installation, prevents it being used. If you wish to participate in
462 telemetry, export MOZBUILD_STATE_PATH to point to its default directory
463 and remove the entry from the <filename>mozconfig</filename>.
464 </para>
465
466 <para>
467 <command>MACH_USE_SYSTEM_PYTHON=1</command>: Use the system python
468 to create a virtual environment for <command>mach</command> without
469 downloading any python wheels.
470 </para>
471
472 <para>
473 <command>./mach configure</command>: This validates the supplied
474 dependencies and the <filename>mozconfig</filename>.
475 </para>
476
477 <para>
478 <option>./mach build --verbose</option>: Use this alternative if you
479 need details of which files are being compiled, together with any C or
480 C++ flags being used. But do not add '--verbose' to the install command,
481 it is not accepted there.
482 </para>
483
484 <para>
485 <option>./mach build -jN</option>: The build should, by default, use
486 all the online CPU cores. If using all the cores causes the build to swap
487 because you have insufficient memory, using fewer cores can be faster.
488 </para>
489
490<!--
491 <para>
492 <command>mkdir -pv /usr/lib/mozilla/plugins</command>: This ensures
493 that <filename class="directory">/usr/lib/mozilla/plugins/</filename>
494 exists.
495 </para>
496
497 <para>
498 <command>ln -sv ... /usr/lib/firefox/browser</command>:
499 This command creates a symbolic link to <filename
500 class="directory">/usr/lib/mozilla/plugins</filename>. It's not really
501 needed, as <application>Firefox</application> checks <filename
502 class="directory">/usr/lib/mozilla/plugins</filename> by default, but the
503 symbolic link is made to keep all the plugins installed in one folder.
504 </para>
505-->
506
507 </sect2>
508
509 <sect2 role="configuration">
510 <title>Configuring Firefox</title>
511
512 <para>
513 If you use a desktop environment like <application>Gnome</application> or
514 <application>KDE</application> you may want to create a
515 <filename>firefox.desktop</filename> file so that
516 <application>Firefox</application> appears in the panel's menus.
517 As the &root; user:
518 </para>
519
520<screen role="root"><userinput>mkdir -pv /usr/share/applications &amp;&amp;
521mkdir -pv /usr/share/pixmaps &amp;&amp;
522
523MIMETYPE="text/xml;text/mml;text/html;" &amp;&amp;
524MIMETYPE+="application/xhtml+xml;application/vnd.mozilla.xul+xml;" &amp;&amp;
525MIMETYPE+="x-scheme-handler/http;x-scheme-handler/https" &amp;&amp;
526
527cat &gt; /usr/share/applications/firefox.desktop &lt;&lt; EOF &amp;&amp;
528<literal>[Desktop Entry]
529Encoding=UTF-8
530Name=Firefox Web Browser
531Comment=Browse the World Wide Web
532GenericName=Web Browser
533Exec=firefox %u
534Terminal=false
535Type=Application
536Icon=firefox
537Categories=GNOME;GTK;Network;WebBrowser;
538MimeType=$MIMETYPE
539StartupNotify=true</literal>
540EOF
541
542unset MIMETYPE &amp;&amp;
543
544ln -sfv /usr/lib/firefox/browser/chrome/icons/default/default128.png \
545 /usr/share/pixmaps/firefox.png</userinput></screen>
546
547 <sect3><title>Configuration Information</title>
548
549 <para>
550 The application settings for firefox are accessible by keying
551 <command>about:config</command> in the address bar.
552 </para>
553
554 <para>
555 Occasionally, getting working sound in
556 <application>firefox</application> can be a problem. Although upstream
557 prefers pulseaudio,
558 on balance using <application>Alsa</application> may be easier.
559 </para>
560
561 <para>
562 If you enabled <application>Alsa</application> for sound, you may need
563 to alter one variable to get working sound. If you run
564 <command>firefox</command> from a term and try to play something with
565 sound you might encounter error messages like:
566 </para>
567
568 <para>
569 <literal>Sandbox: seccomp sandbox violation: pid 3941, tid 4030,
570 syscall 16, args 48 2147767296 139909894784796 0 0 0.</literal>
571 </para>
572
573 <para>
574 That was on x86_64, on i686 the syscall number is 54. To allow this
575 syscall, in <command>about:config</command> change
576 <command>security.sandbox.content.syscall_whitelist</command> to 16
577 (or 54 if using i686).
578 </para>
579
580 <para>
581 If you use <command>pulseaudio</command> in a Desktop Environment, it
582 might already be started by that DE. But if it is not, although
583 firefox-57 managed to start it, firefox-58 did not. If you run
584 <command>firefox</command> from a term and this problem is present,
585 trying to play sound will
586 encounter error messages warning <literal>Can't get cubeb
587 context!</literal>
588 </para>
589
590 <para>
591 The fix for this is to close firefox, start pulseaudio to check it
592 does start (if not, read the information on Configuring in <xref
593 linkend="pulseaudio"/>) and restart firefox to check it is working.
594 If it now works, add the following to your <filename>~/.xinitrc</filename>:
595<phrase revision="sysv">
596<literal>pulseaudio --verbose --log-target=syslog&amp;</literal></phrase>
597<phrase revision="systemd">
598<literal>pulseaudio --verbose --log-target=journald&amp;</literal></phrase>
599 (unfortunately, on some systems this does not work).
600 </para>
601
602 <para>
603 You may wish to use multiple profiles within firefox. To do that, invoke
604 firefox as <command>firefox --ProfileManager</command>. You can also
605 check which profile is currently in use from
606 <command>about:profiles</command>.
607 </para>
608
609 <para>
610 Although WebRender (using the GPU for compositing) is not used by
611 default, it now appears to work well on supported hardware (ATI, Nvidia
612 and Intel GPUs with Mesa-18 or later. For an explanation, please see
613 <ulink
614 url="https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/">hacks.mozilla.org</ulink>.
615 The only downside seems to be that on a machine with limited RAM it might
616 use more RAM.
617 </para>
618
619 <para>
620 To check if WebRender is being used, look in about:support. In the Graphics
621 section Compositing will either show 'Basic' (i.e. not in use) or
622 'WebRender'. To enable it, go to about:config and change gfx.webrender.all
623 to True. You will need to restart firefox.
624 </para>
625
626 <para>
627 It may be useful to mention the processes from firefox which can appear in
628 <command>top</command> - as well as firefox itself, there may be multiple
629 Web Content processes, and now an RDD Process (Remote Data Decoder) which
630 appears when playing web videos encoded with av1 (libdav1d). If WebRender
631 has been enabled, a GPU Process will also appear when firefox has to
632 repaint (e.g. scrolling, opening a new tab, or playing a video).
633 </para>
634
635 </sect3>
636 </sect2>
637
638 <sect2 role="content">
639 <title>Contents</title>
640
641 <segmentedlist>
642 <segtitle>Installed Programs</segtitle>
643 <segtitle>Installed Libraries</segtitle>
644 <segtitle>Installed Directory</segtitle>
645
646 <seglistitem>
647 <seg>
648 firefox
649 </seg>
650 <seg>
651 Numerous libraries, browser components, plugins, extensions, and
652 helper modules installed in /usr/lib/firefox
653 </seg>
654 <seg>
655 /usr/lib/firefox
656 </seg>
657 </seglistitem>
658 </segmentedlist>
659
660 <variablelist>
661 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
662 <?dbfo list-presentation="list"?>
663 <?dbhtml list-presentation="table"?>
664
665 <varlistentry id="firefox-prog">
666 <term><command>firefox</command></term>
667 <listitem>
668 <para>
669 is a <application>GTK+-3</application> internet browser that uses
670 the Mozilla Gecko rendering engine
671 </para>
672 <indexterm zone="firefox firefox-prog">
673 <primary sortas="b-firefox">firefox</primary>
674 </indexterm>
675 </listitem>
676 </varlistentry>
677
678 </variablelist>
679
680 </sect2>
681
682</sect1>
Note: See TracBrowser for help on using the repository browser.