Quantcast
Channel: Phoenix Firestorm Project - Wiki
Viewing all articles
Browse latest Browse all 5258

firestorm_in_manjaro - ↷ Page moved from support:mister_acacia:firestorm_in_manjaro to ...

$
0
0

Using Firestorm in Manjaro/Arch

NOTE: The steps here have not been rigorously tested, and therefore might not work for you.
NOTE: This process makes use of AUR, the build is not an official or supported product. You must make sure the build script is fetching Firestorm from our site and not from any other site.
The steps here apply to a typical installation of Manjaro 20 and may also apply to native Arch or other Arch-based systems.

Enable AUR

By far the simplest method requiring the fewest steps is to use the software manager, called Add/Remove Programs. Refer to this page for detailed steps if AUR is not already enabled.

Install Firestorm

Still in Add/Remove Programs, start typing firestorm. You will see at least one possible version. You want to install official release version, it generally shows the complete version number. Others may show a revision numberl; you don't want those. To be sure which version to select, refer to the version shown on the Linux Download page and make sure the version numbers match.

Click the desired entry – not the build button – and then on the left click the Build Files tab.

If you see a line that looks like

source=("https://downloads.firestormviewer.org/linux/Phoenix_Firestorm-Releasex64_x86_64_$pkgver.tar.xz"

Then you have the correct package selected. Click Build at the right, then the left arrow at the top left.

If you plan on using the Win32 voice files, you'll need to make sure WINE is installed. Search for WINE and click Install.

Now click the Apply button to install Firestorm (and optionally WINE).

Try It Out

Firestorm is installed for all users, so the binaries are in /opt/firestorm. A desktop launcher was created, and would be in your menu under Games.

Beta/Preview builds

No one has added or is maintaining any beta or preview builds on AUR. Fortunately, once you install from AUR, you can visit our site and download a beta or preview version, extract it where desired and run it, and it should work.

Troubleshooting

Crashing

If you crash continually, it will be helpful to get a backtrace, like so:

cd ~/Firestorm
sed -i "/^#export .*gdb/ s/^#//" ./firestorm # This enables gnu debug
./firestorm

At the (gdb) prompt, type r to launch Firestorm. When Firestorm crashes, you should be back at a (gdb) prompt.
Type bt to get a backtrace (there may be several pages, press Enter until you get the gdb prompt again). Copy everything from the terminal screen to a text file.
Type q to exit gdb.
Create a Support Request on our Jira and attach the backtrace as well as crash logs. JIRA can guide you through the process.

NOTE: You can turn off debugging with:

sed -i "/^export .*gdb/ s/^export/#export/" ./firestorm

Voice

Default Linux voice files function, but may not on your particular system. As a workaround, install wine and use the Windows 32-bit voice files:

sudo apt install wine-stable
winecfg #Set the Windows version to Windows 10, test audio output

Once WINE is configured to your satisfaction, launch Firestorm and log in, disable voice if necessary, then press Ctrl+Alt+Shift+S to open Debug Settings. Search for FSLinuxEnableWin32VoiceProxy, set that to TRUE, then close Debug Settings. For good measure, relog, then enable and test voice.

Note that using WINE means there is a slight delay connecting to voice as the WINE system starts up. As well, WINE needs a little time to shut down when you disconnect voice. This may cause a race condition if you toggle voice, where a new connection tries to start before the previous one shuts down. This can affect both instances of WINE, and a relog may be required to restore voice functions.


Viewing all articles
Browse latest Browse all 5258

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>