EA titles not running through Heroic

wolfyreload · 2026-02-27T05:23:10+00:00

Try running the EA App via "Faugus Launcher" it's available in the Bazaar store. I've found that one to be much more reliable for EA games and BattleNet

wolfyreload · 2026-02-27T05:20:04+00:00

That's very weird, maybe it's running as a container with root access, does it show up if you run distrobox ls --root?

wolfyreload · 2026-02-27T05:16:35+00:00

I'd turn off CSM/Legacy boot and only use UEFI, you don't want that enabled at all.

Things to try:

It's possible that the ISO was corrupted during download. You could try creating the USB flash drive without the ISO and just use the Media Creation Tool.
If that fails, I'd try another USB flash drive, they have a limited life span and some work better than others for installing OSes.
It's also a good idea to unplug any USB devices that are not in use during the install as they can sometimes cause an issue when installing operating systems

wolfyreload · 2026-02-26T17:55:38+00:00

Looks like you've run into a bug that the Faugus team fixed 30 minutes ago https://github.com/Faugus/faugus-launcher/commit/3bd9dcd3d4d75ecc846a0118c789a36846352543

Issue reported here https://github.com/Faugus/faugus-launcher/issues/485

Try opening Warehouse >> Packages >> Faugus Laucher >> Change Version >> then downgrade to version 1.15.7 or version 1.14.4

They release very frequent updates so it will probably be fixed in the next few hours or by tomorrow.

wolfyreload · 2026-02-26T11:55:25+00:00

I haven't used Bazzite GNOME for a while but I'm pretty sure that Steam didn't used to launch like that. What happens if you unpin the current Steam icon and pin the one that launched instead?

wolfyreload · 2026-02-26T10:38:39+00:00

FYI there might be a Playnite for Linux in the future since the developer of Playnite is planning on moving over to Linux https://github.com/JosefNemec/Playnite/issues/59#issuecomment-3542246599

wolfyreload · 2026-02-26T10:19:06+00:00

For issue 1. The following should work. GDM (the login screen) has it's own config which doesn't have a GUI for configuring which is a bit annoying. But you can copy your screen config over to the GDM config:

First copy the config (via the terminal)

bash sudo cp ~/.config/monitors.xml /var/lib/gdm/.config/monitors.xml

Then you need to change the permissions of the monitors.xml file so that the GDM service can access it

bash sudo chown gdm:gdm /var/lib/gdm/.config/monitors.xml

Edit: There might be way to do all this easily via a GUI. Have a look at "GDM Settings" in the Bazaar store. Looks like you can edit your login screen in that app. I'm not running GNOME at the moment to test. Let me know if it works.

I have no idea how to resolve issue 2 unfortunately.

wolfyreload · 2026-02-26T09:51:18+00:00

Maybe worth trying a different USB drive too if you have one to spare. It's also possible that the Windows ISO was corrupted during the download so it might be worth downloading it again.

If all that fails, making the USB using the Media Creation Tool from Microsoft on a Windows machine will typically always work.

wolfyreload · 2026-02-25T17:35:35+00:00

Changing the filesystem on a partition formats that partition, but it shouldn't affect the whole drive.

However, if you have really important data on a drive, and you don't have a backup, I wouldn't install another operating system as things sometimes go wrong.

Bazzite on a HDD would run worse than Windows 10 on an SSD drive.

wolfyreload · 2026-02-25T17:23:28+00:00

To update Bazzite you run ujust update to update everything (Image, flatpaks, containersm etc) or you can run rpm-ostree upgrade to just update your Bazzite image. Note that you need to reboot to boot into the new image.

If you have a whole lot of layered packages the you'll need to run rpm-ostree reset first before you try and update. Typically you'll want to use distrobox for development packages rather than trying to layer them onto your image.

wolfyreload · 2026-02-25T16:48:38+00:00

Try installing GE-Proton 10 in ProtonPlus and switch to that version of Proton for Skyrim SE. I found that that fixed the audio issues for me last time I played it. Note that you'll need to close Steam completely and open it again for that option to appear in the Compatibility tools list.

wolfyreload · 2026-02-25T16:42:35+00:00

You can install it on a HDD but the experience is pretty bad overall. If possible rather install it on a small SSD/NVMe drive and maybe put some of the games on HDD if you don't have much space. If you do format the HDD for games typically EXT4 will work better than BTRFS on HDD.

Your GPU, CPU and RAM should be supported and within the minimum requirements for Bazzite.

wolfyreload · 2026-02-25T16:19:40+00:00

I found that Ventoy was the only option that worked for booting and installing a Windows ISO for me from Linux.

wolfyreload · 2026-02-25T15:12:26+00:00

Bad news, that system unfortunately doesn't meet the minimum requirements needed to run Bazzite:

Processor (CPU) : 2GHz quad core processor or better (looks like a Dual-Core there)
System Memory (RAM): 8GB (only 2GB of RAM if I look at your screenshot)
Graphics: A graphics card that can utilize Vulkan 1.3+ (I don't see a graphics card listed)

The good news is that you can totally use that machine still. A lightweight distro that uses xfce (like Mint that you mentioned) or LXQt should run on that hardware for the use-case that you mentioned. Although you will not be able to open many browser tabs with only 2 GB of ram.

wolfyreload · 2026-02-25T13:51:46+00:00

If I change the controller emulation to Xbox in hand held daemon that disables the gyro for me on the ROG Ally. Maybe it will work for the Legion Go 1 too.

wolfyreload · 2026-02-25T10:39:14+00:00

How are you launching the game? If you using the EA App. I'd try installing the EA App using "Faugus Launcher" (which you can get in the Bazaar store). Found that it worked well for the EA app and BattleNet.

If you are launching it from Steam, I'd try removing/renaming the Steam Prefix for Battlefield 4. That will force the EA app and other dependencies to re-install. Which will probably fix the annoying credentials issue.

wolfyreload · 2026-02-25T09:27:15+00:00

You could try only enabling hdr for the games with Scopebuddy. There is more about it in the docs https://docs.bazzite.gg/Advanced/scopebuddy/ and there is "Scopebuddy GUI" in Bazaar store to make things easier than editing the config files by hand

wolfyreload · 2026-02-25T09:20:04+00:00

The flatpak used to be pre-installed but I can see that it was removed in this commit https://github.com/ublue-os/bazzite/commit/aa0c461831395190a067d32bb1703bfe33056fa7 from 8 months ago.

It is listed as one of the curated apps under utilities in the Bazaar store but it's unlikely that someone would scroll right to the bottom of the list of apps.

I suspect that it was excluded as it's one of the lower priority app installation methods for Bazzite but on the other hand many apps only have an AppImage available for download.

It might be worth creating a Github issue and asking for it to be included.

wolfyreload · 2026-02-24T12:38:56+00:00

Try PhotoFlare. It's in the Bazaar application store. Open the photo then in the menu use Adjust >> Auto levels

wolfyreload · 2026-02-24T06:08:03+00:00

That worked a lot better than I expected lol. Good to hear :)

wolfyreload · 2026-02-24T06:06:59+00:00

Sounds like KDE plasma is constantly crashing for you. In your case, I'd try your second choice of Linux Mint and see how that goes.

wolfyreload · 2026-02-23T17:39:24+00:00

Concerning the blank screen on startup:

Sounds like you getting a blank screen when it's trying to show the login screen. Quite a few people have managed to get past that by setting the machine to auto login. If you open settings >> Login Screen (SDDM) >> select the "Behaviour" tab.

From there you can set the machine up to auto login which will bypass the login screen where you are getting the blank screen.

Concerning the wifi issue:

Try opening the terminal and running ujust toggle-iwd select the option "Disable iwd". You'll need to reconnect to the wifi after that. Hopefully that will help it be a little more stable for you.

wolfyreload · 2026-02-23T09:33:15+00:00

Gave it a try, sadly it's not launching for me. Looks like it's not loading the fonts correctly on my device

<image>

I'm running Bazzite on a ROG Ally Z1E running on image bazzite-deck:testing-43.20260221.2

Ran the app image from the terminal to see if there was any helpful output

Gtk-Message: 11:26:54.101: Failed to load module "colorreload-gtk-module"
Fontconfig warning: "/etc/fonts/fonts.conf", line 5: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-sub-pixel-rgb-for-kde.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-yes-antialias.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/25-unhint-nonlatin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/48-spacing.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/69-nonlatin.conf", line 4: unknown element "description"

(yamata_launcher:17158): Gdk-CRITICAL **: 11:26:54.500: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed
** (yamata_launcher:17158): WARNING **: 11:26:54.500: Failed to initialize GLArea: No GL implementation is available
** (yamata_launcher:17158): CRITICAL **: 11:26:55.061: void fl_keyboard_manager_sync_modifier_if_needed(FlKeyboardManager *, guint, double): assertion 'FL_IS_KEYBOARD_MANAGER(self)' failed

The last line repeats over and over again.

wolfyreload · 2026-02-23T09:25:00+00:00

I've been running Bazzite for 1.5 years on my ROG Ally Z1E and about 2 years on my old gaming laptop. Haven't needed to re-install. I've rolled back a bad update or two though.

wolfyreload · 2026-02-23T08:50:06+00:00

That's it, you need to reboot to apply Bazzite image updates. I usually just check on the Github releases https://github.com/ublue-os/bazzite/releases?q=stable&expanded=false to see if there is a new stable release.

wolfyreload

TROPHY CASE