I find Qwen3.5 is the best at toolcalling and agent use, otherwise Gemma4 is a very solid all-rounder and it should be the first you try. Tbh gpt-oss is still good to this day, are you running into any problems w it?

That account is less than a day old and you should definitely not do whatever it is they tell you to do

Looks like some combination of defragging & balancing has done the trick! The space that was previously marked UNREACHABLE is now UNUSED, and my disk space is back to normal:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       227G  105G  103G  51% /

Thanks for the wiki link, Btrfs is new to me and I’ve definitely got some learning to do

Just one drive, it was a clean Linux install with no funky stuff going on. I’ll have to look into Btrfs cleanup more, last time I did it the disk just filled up even more

Legend! It found a second filesystem named “UNREACHABLE”:

It looks like an exact duplicate of my main filesystem “/@rootfs”, I’m guessing this is why my disk space filled up. Do you know how I’d go about removing the duplicate? (If it’s safe to do so)

Interesting, this could be it? I haven’t configured any mounts on this device yet, but when I tried one of the other suggestions from this thread and use btdu, I get this error:

$ ./btdu -x /
Fatal error: The mount point you specified, "/", is not the top-level btrfs subvolume ("subvolid=5,subvol=/").
It is the btrfs subvolume "subvolid=256,subvol=/@rootfs".
Please specify the path to a mountpoint mounted with subvol=/ or subvolid=5.
E.g.: mkdir /mnt/sda1 && mount -o subvol=/ /dev/sda1 /mnt/sda1 && ./btdu /mnt/sda1

Note that the top-level btrfs subvolume ("subvolid=5,subvol=/") is not the same as the root of the filesystem ("/").

I’m fairly new to the workings of Btrfs so this is jibberish to me right now, but I’ll look into it more

EDIT: Nevermind! I was just using the tool wrong. I needed to mount my btrfs “sub-volume” then do the scan against that:

sudo mkdir -p /mnt/btdu

sudo mount -o subvolid=5 /dev/sda1 /mnt/btdu

sudo ./btdu /mnt/btdu

ncdu

Oh this one is very cool! Unfortunately it also only shows the same 101GB being used:

ncdu 1.22 ~ Use the arrow keys to navigate, press ? for help                                                                                                                                  
--- / ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   93.1 GiB [###########################] /home                                                                                                                                               
    6.5 GiB [#                          ] /usr
  790.4 MiB [                           ] /var
  173.0 MiB [                           ] /boot
   12.8 MiB [                           ] /etc
    1.7 MiB [                           ] /root
    1.3 MiB [                           ] /run
   44.0 KiB [                           ] /tmp
@   4.0 KiB [                           ]  initrd.img.old
@   4.0 KiB [                           ]  initrd.img
@   4.0 KiB [                           ]  vmlinuz.old
@   4.0 KiB [                           ]  vmlinuz
@   4.0 KiB [                           ]  lib64
@   4.0 KiB [                           ]  sbin
@   4.0 KiB [                           ]  lib
@   4.0 KiB [                           ]  bin
.   0.0   B [                           ] /proc
    0.0   B [                           ] /sys
    0.0   B [                           ] /dev
    0.0   B [                           ] /media
e   0.0   B [                           ] /srv
e   0.0   B [                           ] /opt
e   0.0   B [                           ] /mnt

There is one listed: ID 256 gen 137604 top level 5 path @rootfs Looks like it is just my filesystem though?

For music prod on Linux, have you tried Reaper?

Good solution, cheers! I also followed the other commenter’s idea to add it as a KDE shortcut so I can use it on demand.

I guess I’ll just need to be careful not to paste a bazillion lines of text lol

Works awesome! Thanks for introducing me to xdotool, what a helpful utility. Question: what does the --file flag in your command do? I can’t find it in the manpage

I had a similar problem, it was caused by undervoltage. Are you using the official power supply?

Reporting back!

Reformatted with btrfs, steam now does this when I open the game (didn’t before):

anddd it works! Can’t believe this whole headache was just exfat all along lol!

Thank you for your help :D

Reporting back!

Reformatted with btrfs, steam now does this when I open the game (didn’t before):

anddd it works! Can’t believe this whole headache was just exfat all along lol!

Thank you for your help :D

I think you’ve just pointed me in the direction of a solution…

The comment you’re referring to seems to be this one:

mv Launcher Launcherbak
ln -s bin Launcher
ln -s ./bin/bg3_dx11.exe ./bin/LariLauncher.exe
cp ./Launcherbak/*.dll ./bin

creating a symlink to trick steam into thinking it’s running the launcher when it actually runs the game. BUT … my SSD is formatted as exFAT, which doesn’t support symlinks, so I can’t do this.

So I’m guessing proton is trying to create a symlink at pfx/dosdevices/c when it installs .NET, but fails, which is also probably why everyone else seems to have a breezy time with it. Not sure why my other games haven’t run into this though… maybe they haven’t needed to install anything there?

I will report back after reformatting my entire SSD lol

I think you’ve just pointed me in the direction of a solution…

I tried to create a symlink “c:” pointing to …/drive_c, but I couldn’t. “Operation not permitted” I then got ptsd flashbacks to the last time this happened - turns out it was because my SSD is formatted as exFAT, which doesn’t support symlinks.

I’m guessing proton is trying to create this symlink when it installs .NET, but fails, which is probably why everyone else seems to have a breezy time with it. Not sure why my other games haven’t run into this though… maybe they haven’t needed to install anything there?

I will report back after reformatting my entire SSD lol

Ohh, is the “c” just a symlink to the drive_c folder?

I need STEAM_COMPAT_DATA_PATH because my proton is installed in a different steam library than the game, all of my proton games use this. I tried to remove it anyway and try just ‘–skip-launcher’, but now the game doesn’t launch lol

The command likely won’t work for you because you don’t have proton installed at that location

Still the same error unfortunately.

Interestingly though, when I try to install .NET manually via protontricks-launch -v --appid 1086940 /home/user/Downloads/windowsdesktop-runtime-6.0.35-win-x64.exe I get the following error:

/media/user/T7/Main/Games/SteamInstalled/steamapps/compatdata/1086940/pfx/dosdevices/c:/windows: No such file or directory

Going down that tree I see the entire path is there except for “/c” at the end. I manually added a “c” folder, but then I get stuck at this error:

protontricks (ERROR): Active compatibility tool was found, but it's not a Proton installation supported by Protontricks.
Proton installation could not be found!

I know my proton installation works because all my other games use it fine. Proton is on a different drive than BG3, could that cause issues?

No, installed from debian repository