LinuxStuff

This is a compilation of random Linux tips I've learned. Could be tips relating to fixes for rrandom things, or how to get a game modded and or working on Linux.

[linuxstuff]

What is this blog?

I wanted to put all the random fixes I've learned over my time on desktop Linux into one place. That's basically it! To start off here's one of my own videos:

This first one is probably out of date, but I'll leave it up here anyway. This video explains how to install mods on beat saber on Linux. As a said, it's probably out of date but I'll put it here anyway, just in case.

[linuxstuff]

Preventing Dynasty Warriors 8 Empires from visually freezing when alt tabbing.

This one is a somewhat specific fix, but I think it could apply to other games as well. I was having an issue where for some reason, whenever I would alt tab out of DW8E, the game would stop visually refreshing. I specify visually, because the sound was clearly still playing and I could hear myself pressing buttons in the game.

Before we get into it, I want to link to where I found the command for this which is here. Important to note this is better than the usual way of launching gamescope and connecting it, because this command does it all in one.

If this sounds similar to your issue, we can try fixing it using gamescope. I'm also assuming you are using steam. The fix is pretty simple. First we need to install gamescope. I'm on a Fedora based system, so for me the command for this is:

Sudo dnf install gamescope

If you're debian based, like Linux Mint, Pop OS, or Ubuntu, it'll be:

Sudo apt install gamescope

If you already have it installed, no worries, it just won't do anything besides tell you it's already installed. First of all, we need to figure out which display number gamescope is going to launch on. Press control + alt + t, or open a terminal window however you see fit, and type

gamescope

Scroll down, and eventually you'll see a line that looks like this:

This means my display is 1, but it might be different for you.

Now go back to steam, right click and click properties.

It'll open this window. Click on the launch options box below it, and paste in this:

gamescope --force-grab-cursor --backend sdl -H 1080 & DISPLAY=:1 gamemoderun %command%

A couple things to note here. For one, the number for DISPLAY=:1 needs to match the number we got earlier, which for me was 1. Also, the value to the right of -H is your monitors resolution, so you might need to change that depending on what you have. Otherwise, the game will now launch using gamescope, and you'll notice that tabbing out doesn't even make it minimize in fullscreen! Not only is this way less annoying, but it prevents the bug from happening because there is no minimization.

Hope this helps! Oh and one last thing-- if you're playing DW8E or DW8XL, make sure to use GE-Proton7-55. This version specifically can load up the intro movies with no issue.

[linuxstuff]

Make any application fullscreen on KDE Plasma.

Okay so first things first we're gonna wanna open up our settings.

Then go up to the top left search bar, and type keybinding, above quick settings.

Then click on shortcuts. It should be the only thing that appears.

Then, type fullscreen into the search bar.

From there, click add (or it may say none) and press the key you want to toggle full screen.

And we're done! Hope this helps.

[linuxstuff]

Getting script extender to work on BG3 in Linux

You might have tried getting SE to work by installing it manually, and nothing pops up in the corner saying its installed right? Well, we just need to add a steam launch option to use the dll!

First go to properties...

Then put WINEDLLOVERRIDES="DWrite.dll=n,b" %command% into launch options. This will load the DWrite.dll correctly, allowing for SE to work properly.

Also, for modding on Linux, use Lampray, a Linux mod manager. Otherwise afaik, modding is the same on Linux as on Windows. Now go kill some illithids with some style mods or the 18 million sex mods idk you do you homie

[linuxstuff]

(Potential) Fix for Diablo 4 crashing on Linux under Wayland with Nvidia

If you've noticed Diablo 4 is crashing specifically under Wayland with an Nvidia GPU, it's likely running out of VRAM. When you run out of VRAM on Wayland, it kills the process. (It's more complicated than that, but this explanation is good enough).

Firstly, I want to mention that I'm not 100% on the effectiveness of these fixes. I don't understand DXVK and d3dvk enough to know whether these actually do anything or not. In my anecdotal experience though, they seem to help and others have reported similar results. First lets go to the Diablo IV folder with Steams UI

It'll bring you to the root Diablo IV folder. From here, right click, new, then text file.

Copy paste this into the text file, save it, and name it dxvk.conf.

[Diablo IV.exe] dxgi.maxDeviceMemory = 2048 dxgi.maxSharedMemory = 2048 dxvk.maxChunkSize = 4

By default, this is set to 2 gigabytes, but you'll want to change it to what's right for your system. So if you've got say, 7 gigs of vram, I'd probably set it to 5. Remember that the game isn't the only thing using VRAM, so don't set it to max. The memory chunk setting should be left at 4. To be completely honest, I'm not really sure what this does, but it seemed to help. The memory settings above it get ignored by Diablo IV (on my setup, at least) so I'd try the memory chunk to see if it helps at all.

From what I understand, Diablo IV has a VRAM leak, but it's made even worse by a bug in XWayland, which handles X applications (such as wine/proton running in X11 mode) running on Wayland. So if this still doesn't work for you, I'd look out for Wayland/XWayland updates. Beyond that, I'd try going back to X11. Hope this helps!

[linuxstuff]

PSA: Run KSP1 with Proton if you want to use EVE-Redux (environmental visual enhancements)

The shaders for EVE are specifically made for DX, and they will visually glitch out on native. If you use proton, they seem to work fine. Unfortunately you'll have to mod manually (unless there's a way to run ckan for windows on Linux, but mine kept getting confused)

[linuxstuff]

Warframe stuck in controller mode (and using a controller doesn't work)

This one had me stumped for awhile! First off, ask yourself if you're using a Nintendo controller, and if so, if you've installed joycond. If you have, we'll need to stop it and remove it.

This will stop the joycond daemon. If you don't have the joycond daemon installed, the terminal will tell you this:

In which case, you might just need to restart, or you can jump to the part where we use lutris to run Warframe instead.

But for now, lets remove that daemon from our PC.

First type:

Then:

And then do the same thing again, but replace 72 with 89.

After that, type these two commands in succession.

Then type these two commands:

Then reboot. Essentially what we're doing here is manually removing any joycond daemon files, manually. Technically we only need to remove the service file, but its good to clean it all out.

Now if it still doesn't work, we can run Warframe using Lutris. First, launch lutris, then click the plus on the top right.

Click search Lutris website for installers

Then type warframe and run through the install process. After you launch warframe for the first time, click the gear icon on the top right, and make sure your settings look like this:

This will result in the updater saying "Downloading updates..." with no progress (as seen in the screenshot) but it is downloading the game. It should work as is, but I personally recommend using wineGE instead of the default wine given by Lutris. To do this, download it using this link:

Then, navigate to /home/<your_username>/.local/share/lutris/runners/wine/ with your distributions file browser. After that, extract the downloaded wineGE into this folder. Restart lutris, right click warframe and go into configuration, runner options, then select wineGE from the dropdown.

This should run just about as well as the steam version, and can be handy given Warframes awkward controller implementation. I hope that you're able to get around the issue and enjoy farming!

[linuxstuff]

How to get windows-like screenshot tool in Linux Nobara 39

If you're looking to emulate the feature of pressing win+shift+s and getting to take a rectangular screenshot that you can then copy and paste into say, discord. It's a simple shortcut add to make this feature happen in Nobara 39 (and/or Fedora) with Spectacle.

First press super user key (windows key) , type in shortcuts, and press enter

Either click on spectacle, or search for it with the searchbar

Click the arrow next to "Capture rectangular region"

Left of the trashcan click on the pre-existing shortcut (it will say meta+shift+print)

5. It will then change to input, just press windows key+shift+s to input the shortcut

6. Click apply on the bottom right, and we're done! We now have win+shift+s screenshot functionality on Nobara.

[linuxstuff]

How to fix Guilty Gear Strive can't connect to online on Linux

Most likely if you're unable to connect online, it's due to time sync issues. This an issue on Windows as well as Linux, and I've experienced this annoyance on both. To fix this, we need to sync our clock.

First, open a command prompt.

Type in "timedatectl"

Timedatectl will most likely show this:

In this case we need to enable ntp. To do this, simply type in "sudo timedatectl set-ntp true"

We also may need to install ntp if on arch, in which case type "pacman -S ntp"

And after restarting the game, it should connect just fine. I hope this helps!

Sources:

NTP, also known as Network Time Protocol, is one of the most reliable methods for synchronizing internal clock timings on systems in a netwo

[linuxstuff]

How to install mods for Guilty Gear Strive on Linux

Installing mods for GGST on Linux is actually extremely easy.

First, navigate to the folder where GGST is. You can either do this by going into your library and right clicking and going to browse local files, as seen below, or by going into your .steam folder, most likely located in your home folder. (I recommend just going with the gui option).

This will take you to your GGST folder, which looks like this.

Next, you'll want to go into red, content, and then paks. From there, you'll want to create a folder and name it ~mods. It should look like this.

From here, download any mod you like, (as long as it isn't the fucking I-No mole removal mod, you sick fuck) and put the pak file and sig file in here.

Note, some mods might not have a .sig file, in which case, download a mod that does have one, and copy the sig file and rename it to the name of the pak file of the mod. All mods should have a sig and pak file, for example the suitRam mod looks like this:

So if I downloaded this mod and it didn't have a .sig file, I'd just make one.

And that's it! The process is more or less the same as windows. Have fun modding! (Unless you're downloading that I-No mod I mentioned, in which case fuck you)

[linuxstuff]

Risk of Rain 2 Modding on Linux How-To

While Linux has earned a reputation for being the OS that requires 4 monitors and a lot of tip tap tipping like a madman, modding ROR2 on Linux is actually really easy.

First off we need R2Modman. This is a mod manager that works with many games and fortunately for us, has a native Linux version. So lets get it working. Go to this link

r2modman v3.1.42

A simple and easy to use mod manager for several games using Thunderstore

And click manual download. After the .zip is completed, move it to your desired location then right click, and click extract here. (Or if you're like me, extract it into downloads because we all know downloads is really just documents2)

After that, go into the newly extracted folder, go to the .appimage, right click, go to properties > permissions, and click on allow executing file as program.

If you try to launch it by double clicking it, you'll probably get a pop up that opens, then closes immediately after, that's normal. Now we need to make a launcher that opens r2modman, and also so that we can add it to our panel if we like. To do that, return to the desktop, either by closing every window or (in Linux Mint) clicking on the show desktop button on the panel.

Then right click, and click create a new launcher here.

Name it whatever you want (r2modman makes the most sense) and for the command click on browse. From here go to wherever you put the folder of r2modmans appimage. Once you get to the folder of the appimage, click ok or double click on the appimage to add it to the command.

Then at the end of the command type --no-sandbox, with a space in-between the filepath and the no sandbox value. If you want to get the right icon, the icon for r2modman is in the same folder, so simply click on the rocket icon for the launcher, and then browse to the r2modman icon. No comments are needed, just click ok and you're done!

If you want to add r2modman to your panel as a shortcut, press super key (windows key) then type it in, right click, and then click add to panel. You can also just right click while it's open and click pin to panel.

And thats it! Select risk of rain 2, your platform, and profile. From then on you just download mods exactly as you would on Windows. Have fun playing Paladin!

[linuxstuff]

Fix #2 Shared steam library game with dual-booted Windows gives disk write error when launching on Linux

This one has a few different fixes. First and foremost however, ask yourself if you've dual booted into Windows recently. If you have, it's likely steam is autorun on startup, and automatically starts downloading updates. If this is the case, then what's most likely happened in your case is Windows has locked the folder while downloading updates, and you dual-booted back into Linux while this was happening, so the folder is still locked by Windows.

To fix this, simply boot back into Windows and let the download finish. You can try using chmod username <filepath to shared library> -R but this didn't work for me.

If you didn't do that, then I would advise attempting the common fixes. Try clearing steam downloads cache by going to settings > downloads > clear cache button.

Also try settings > storage > click on the drive the game is installed, then repair folder. I'd also try a reboot of steam, then the PC to see if that helps.

If all else fails, try moving your steam library to another drive if possible. It could be that the drive has had to read one too many hot takes from discord and has decided to give up. Hope this helps!