Skip to content

Linux and Steam Deck FAQ

This page lists issues specific to Linux or Steam Deck

Known Working/Broken Linux Configurations

Click here to view the Higurashi Linux Configuration Spreadsheet

We informally keep a Linux configuration record, stating which configurations work, and which are known to have problems. This includes information like:

  • which Higurashi chapter was tested
  • whether the game was run natively, or was run under proton
  • The operating system and operating system version
  • a list of problems if the game did not run correctly

However please take it with a grain of salt, as some reports may be in error or unrelated to the configuration.

Steam Deck

Steam Deck - No Audio at all

Steam Deck has a way to mute specific apps, as discussed in this reddit post "No Sound Fix"

tldr: Games can be accidentally muted. Starting the game again in desktop mode then going to the applications tab in audio settings allows you to unmute it.

...fixed it by opening the game in desktop mode, going to audio settings (click the speaker icon in the taskbar), opening the applications tab and unmuting it there.

If you're still having problems, check the "There is no sound/audio/BGM/voices" in the General FAQ, as you may have some other issue.

General Linux Issues

Game crashes on startup with "fatal stalled cross-thread pipe" error at start of game log

  • If you get a src/common/pipes.cpp (852) : fatal stalled cross-thread pipe error at the top of your game log, it appears to be an issue with the game communicating with Steam
  • To fix this:
    • Try restarting Steam and launching the game again
    • Try playing the game without Steam (close steam, then click on the executable directly)

Whole game / system freezes when you move the mouse cursor with awesomewm desktop manager (and possibly others)

  • This issue was reported with the awesomewm desktop manager
  • This issue affected other games than just Higurashi
  • To fix this issue:
  • Disable your compositor
  • Run your desktop manager with the --no-argb flag (More info here, but not quite the same issue).

Game used to work in windowed mode, but fullscreen crashes immediately, and I can't reset to windowed mode

To forcibly reset to windowed mode, see Uninstalling Unity PlayerPrefs to forcibly clear your PlayerPrefs.

GNOME/MATE Desktop - whole desktop crashes when game launched

NOTE 2022-11-13: We have added a workaround in our mod to fix this issue. Let us know if you still have this problem on the latest version of the mod.

Expand the below red box for more information.

[FIXED 2022-11-13] Linux Users: Windowed Mode causes Game/Desktop Crash with GNOME/MATE

NOTE 2022-11-13: We have added a workaround in our mod to fix this issue. Let us know if you still have this problem on the latest version of the mod.

Triggering the bug

This bug is triggered when:

  • you transition from fullscreen to windowed mode
  • the game launches in windowed mode
  • you drag the window around

If the game is always in fullscreen mode, the bug will never be triggered.

The bug only seems to affect chapters 3-6, although theoretically it could trigger on chapters 1 and 2. It occurs even on the unmodded game.

The bug does not affect all desktop environments, however GNOME desktop is known to be affected.

Symptoms of the bug

When the bug is triggered, the game window will become extremely large or small, and the screen will be colored a black or blue color.

After this happens, the game may freeze, crash, or sometimes your whole desktop environment will crash.

Cause of the bug

This bug is due to Unity versions ≤ 5.5.3p3 having a broken window resize function that sends uninitialized stack data to XSetWMNormalHints.

See the following links for more details: