Can't manage to launch protontricks anymore. Error: 'Protontricks might not have access to the directory.' Edit: relevant error is 'invalid file magic number.'

[Ratconned]

This is what I am assuming is the problem. It was the main error displayed in terminal. Also some stuff about wrong magic number.

I've re-installed protontricks but have the same problem. I'm using the software centre version on debian bookwork stable (which is listed as .deb) and had been able to use it months ago, though I have performed some system updates after that within bookwork itself. The games it cannot access is on a secondary drive. How do I add permission? It is not the flatpak of protontricks, and even steam is not a flatpak The github states it is a package maintained by separate entity and that it is updated (debian unstable only has the newer version), and that older versions could possibly not work properly. But I'm trying to get it to work still, by trying to see what went wrong. There are a few possible causes. Something may have changed with an update to my system, is one of the possible things. Right now I'm just trying to give protontricks access to my steamgames folder, but do not really know how to do it.

protontricks (WARNING): Steam library folder /media/rtc/sdb/SteamLibrary not found. Protontricks might not have access to the directory.
Traceback (most recent call last):
  File "/usr/bin/protontricks", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/usr/lib/python3/dist-packages/protontricks/cli/main.py", line 32, in cli
    main(args)
  File "/usr/lib/python3/dist-packages/protontricks/cli/util.py", line 149, in wrapper
    return cli_func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/protontricks/cli/main.py", line 273, in main
    proton_app = find_proton_app(
                 ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 796, in find_proton_app
    tool_app = find_steam_compat_tool_app(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 584, in find_steam_compat_tool_app
    appinfo_sections = [
                       ^
  File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 584, in <listcomp>
    appinfo_sections = [
                       ^
  File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 514, in iter_appinfo_sections
    raise SyntaxError("Invalid file magic number")
SyntaxError: Invalid file magic number

[Ratconned]

Browsing through the github, it seems protontricks is broken on most debian based systems at the moment. Even the latest versions with flatpak. (Edit: The latter part of this preceding statement was based on an unverified issue raised on github.) sigh I was really hoping to play Arkham Asylum today after feeling like it for some reason. I needed to install a missing component for that, because merely using proton ge wasn't enough as stated in protondb. I'll play something else

Edit: This was not the case, an update in mid-2024 broke protontricks on all distributions. Updating protontricks to version 1.12 or later fixes it.

[NGin]

Have you actually tried the flatpak version that's supposed to contain the fix for this? Busy installing it myself to troubleshoot some things.

Some report it's still a problem yes, but might as well verify that for yourself.

[Ratconned]

Originally posted by NGin:

Have you actually tried the flatpak version that's supposed to contain the fix for this? Busy installing it myself to troubleshoot some things.

Some report it's still a problem yes, but might as well verify that for yourself.

No. Protondb says proton ge contains the fix so I'm looking into that (as in, why it didn't work with version 9.23), and a possible lutris install script, to try to fix the problem.

[grzegorz77]

*** Further entries up to at least #37 turned into a chat about editing fstab,




Old Post:

I don't know much about flatpak, but half a year ago it was described here how to add a disk to flatpak. Maybe that would solve the problem.

edit:
I'm ashamed to admit it, but I don't know what a software center is.
apt search steam
shows you have steam package installed?

debian bookwork = bookworm ??
I'm a bit stupid here too, but I assume you mean the code name of the distribution.

This additional disk is not a usb drive, with some strange file system like ntfs or vfat ??
You have it added in /etc/fstab

edit 2:
/media/rtc/sdb/SteamLibrary
Yes, it is an external drive.
Add the drive as internal in /etc/fstab
You can simply do it with a text editor and reboot.
Or some window program, but I don't use any, so I won't give you the name of the program.
The usb drive must be plugged in before the computer boots up, fstab mounts disks at boot.
uuid:
lsblk -o name,model,size,mountpoint,fstype,label,uuid
or (root)
blkid /dev/sdb

edit 3: ....
Mount the drive here, for example:
/mnt/secound_disk
Don't forget to create a folder.
Then add the disk in steam:
/mnt/secound_disk/steam_secound_disk_folder
Steam loads disks when you start steam, it doesn't refresh.
If you can't add a folder, check if you can save a file there, if not, you don't have access rights somewhere along the way.
The easiest way to add access rights and the owner of the folder is probably in midnight commander.
apt-get install mc
Do I remember the name of the package correctly?
apt search midnight commander

[Ratconned]

Originally posted by grzegorz77:

I don't know much about flatpak, but half a year ago it was described here how to add a disk to flatpak. Maybe that would solve the problem.

edit:
I'm ashamed to admit it, but I don't know what a software center is.
apt search steam
shows you have steam package installed?

debian bookwork = bookworm ??
I'm a bit stupid here too, but I assume you mean the code name of the distribution.

This additional disk is not a usb drive, with some strange file system like ntfs or vfat ??
You have it added in /etc/fstab

edit2:
/media/rtc/sdb/SteamLibrary
Yes, it is an external drive.
Add the drive as internal in /etc/fstab
You can simply do it with a text editor and reboot.
Or some window program, but I don't use any, so I won't give you the name of the program.
The usb drive must be plugged in before the computer boots up, fstab mounts disks at boot.
uuid:
lsblk -o name,model,size,mountpoint,fstype,label,uuid
or (root)
blkid /dev/sda1

I am the stupid one. I do not know exactly how to follow these instructions but I will try.

It is not the flatpak. I have checked /etc/fstab and there is no mention of the drive, yes. It is always connected since it is a laptop and almost all games are there, I use them everyday day nearly.

The game problem might be related to a file the game itself creates which causes problems apparently, but perhaps going along with this will fix protontricks.

I was able to use protontricks with the same configuration around a year ago I think. On the same system. But I do not know how much that matters because it is not working now and as I stated, (and to clarify) I had done a few updates within debian 12 itself. I remember seeing at one point the kernel version was upgraded, though again I do not know the significance of it. Moving that aside for now, I'll try to make the drive 'internal' after seeing how to do it.

[grzegorz77]

I already wrote it to you in edit 3

Experiments like a usb drive, even if you manage to add it as a drive for steam, end this way.
It works today and works tomorrow, but it will break maybe in a week, maybe in five years, but it will stop working, or it will cause a problem.

Added to the system in fstab it should work.

Removable drives are treated differently from fixed drives.
But debian will not dare to deny it if you as the root, tell that the usb drive is an internal drive.

...edit
man fstab

[Ratconned]

Originally posted by grzegorz77:

I already wrote it to you in edit 3 :p2chell:

wow, I'm assuming my filesystem is a mess
for

lsblk -o name,model,size,mountpoint,fstype,label,uuid

, I got

sda    WDC W 931.5G                         
└─sda1       931.5G /mnt/311d7 ext4   sdb   311d743f-5338-4dcb-bf56-0650dd792a8f
nvme0n1
       SAMSU 238.5G                         
├─nvme0n1p1
│              512M /boot/efi  vfat         A11B-108E
├─nvme0n1p2
│              237G /          ext4         13f89656-32aa-48f4-b0b2-36acbbcf2fcd
└─nvme0n1p3
               977M [SWAP]     swap         44a91fcb-6bd2-4561-83f4-f52c6608e715

I previously tried blkid /dev/sdb but got nothing, not even an output. I'd done it as root. Probably de to the above code, which states it is sda. I am clueless now. Any tips?

[Ratconned]

Originally posted by grzegorz77:

:

Experiments like a usb drive, even if you manage to add it as a drive for steam, end this way.
It works today and works tomorrow, but it will break maybe in a week, maybe in five years, but it will stop working, or it will cause a problem.

Added to the system in fstab it should work.

Removable drives are treated differently from fixed drives.
But debian will not dare to deny it if you as the root, tell that the usb drive is an internal drive.

...edit
man fstab

Indeed, that seems to be what happened at least from my not-learned perception

[grzegorz77]

Believe me, this is a very short result of the command.

You have a uuid sdb

...Maybe it's better to edit these uuids and delete some of the numbers. (!!!)

Add this uuid to fstab according to edit 3
and man fstab

Yes, sda1 was the first example I came up with
No result is correct because you don't have sda1

In MC you have a text editor
but maybe it will be easier for you to use the nano (maybe it will be easier for you to paste).
you copy by selecting with the mouse
you paste the mouse with the third key
(root)
nano /etc/fstab
I strongly encourage you to make a backup of fstab

[grzegorz77]

Make the console window bigger, because this fstab output looks strange.
Or maybe something was pasted wrong.

[Ratconned]

Originally posted by grzegorz77:

Make the console window bigger, because this fstab output looks strange.
Or maybe something was pasted wrong.

NAME        MODEL                        SIZE MOUNTPOINT                                FSTYPE LABEL UUID
sda         WDC WD10SPZX-24Z10         931.5G                                                        
└─sda1                                 931.5G /mnt/311d743f-5338-4dcb-bf56-0650dd792a8f ext4   sdb   311d743f-5338-4dcb-bf56-0650dd792a8f
nvme0n1     SAMSUNG MZVLB256HBHQ-000L2 238.5G                                                        
├─nvme0n1p1                              512M /boot/efi                                 vfat         A11B-108E
├─nvme0n1p2                              237G /                                         ext4         13f89656-32aa-48f4-b0b2-36acbbcf2fcd
└─nvme0n1p3                              977M [SWAP]                                    swap         44a91fcb-6bd2-4561-83f4-f52c6608e715

not sure anything is different in formatting. This is the maximised window's output

[Ratconned]

Originally posted by grzegorz77:

man fstab

I'm having trouble finding what this command does

[grzegorz77]

Now it makes sense.
So you have sda1 named with a label as sdb
But it is mounted in /mnt/uuid
Is this your second internal drive ??
Which is this usb drive ??

Maybe change this label, it's very unfortunate
gparted /dev/sda


The whole situation is very unfortunate.
If the drive is mounted, as a /mnt/uuid
Why does the program look for it in /media/rtc/sdb/SteamLibrary
/media/rtc(user)/sdb(label)/SteamLibrary


I suggest you start by changing the label, then adding the sda drive (is it a usb?) to the fstab file.

After reboot, check what the situation is like in /mnt (don't you have any weird symbolic links there?) and check the /media.
If you unplug the usb and plug it back in, the automount will mount it in /media

[grzegorz77]

Originally posted by Ratconned:

Originally posted by grzegorz77:

man fstab

I'm having trouble finding what this command does

man man


man is a user manual

You can type man fstab in the www if it is convenient for you

[Ratconned]

Originally posted by grzegorz77:

Now it makes sense.
So you have sda1 named with a label as sdb
But it is mounted in /mnt/uuid
Is this your second internal drive ??
Which is this usb drive ??

Maybe change this label, it's very unfortunate
gparted /dev/sda


The whole situation is very unfortunate.
If the drive is mounted, as a /mnt/uuid
Why does the program look for it in /media/rtc/sdb/SteamLibrary
/media/rtc(user)/sdb(label)/SteamLibrary


I suggest you start by changing the label, then adding the sda drive (is it a usb?) to the fstab file.

After reboot, check what the situation is like in /mnt (don't you have any weird symbolic links there?) and check the /media.
If you unplug the usb and plug it back in, the automount will mount it in /media

This comment seems like it is key to fixing the problem. I will need to see how to make these changes without messing it up.

As for the hard drive, it is an internal hard drive inside the laptop I'm using. I think I mentioned it before but maybe I removed it during an edit before posting it. What do you think would be the most appropriate label to avoid confusion in the future?

To try to understand... the drive is sda1 but has the label sdb? And it would be best to label it sda1? Sorry if I'm wrong, I've been physically worn out over 2 days