Archr

joined 2 years ago
[–] Archr 2 points 6 days ago (1 children)

If you are launching the hoyo launcher through heroic then that will also have to obey Flatpak permissions. Since that is how the containers work.

You could try enabling full filesystem access just to test whether is it Flatpak permissions blocking you.

[–] Archr 1 points 6 days ago* (last edited 6 days ago) (3 children)

Do you have heroic installed through Flatpak? If you do then install flatseal (through Flatpak) and use flatseal to enable permissions for heroic launcher. It should be pretty obvious how to do this once you have flatseal open.

By default Flatpak does not allow applications to write to directories outside of your home fir (and I think it also blocks access to other partitions).

Source: I did this on my system last Friday to install return to moria. Also I got zzz to work on my steamdeck out of the box with heroic game launcher.

[–] Archr 3 points 3 months ago (1 children)

This is true. And it's also why I always recommend downloading steam through their website. They distribute their own Deb directly, and it auto updates.

Flatpak version is also okay but if you want to use a secondary disk then you need to know how to use portals (or the Flatpak configuration tool that I can't remember the name of).

[–] Archr 4 points 4 months ago

I think there is a value you can put into a /sys file to fix this. Had the same issue on my k10 keyboard. (the fix was easily findable on their forums)

[–] Archr 14 points 5 months ago (5 children)

I like the idea that you might actually believe that it really matters WHICH bombs got dropped on civilians rather than THAT bombs get dropped on civilians.

[–] Archr 2 points 5 months ago (1 children)

I'm not sure how that applies here.

I am talking about enterprises being able to leverage their current infrastructure to manage their users in Mastodon from a central location, Like AD. Rather than have to manage local accounts.

I am not talking about activitypub in anyway.

[–] Archr 1 points 5 months ago (4 children)

I'm not sure on the capabilities of Mastodon. But companies will never go for this if Mastodon doesn't support saml or active directory (or other Auth systems). It needs to integrate with their enterprise tools.

[–] Archr 20 points 6 months ago (6 children)

This might help in the future in case you setup a remote mount for backups in the future. Look into using systemd's automount feature. If the mount suddenly fails then it will instead create an unwritable directory in its place. This prevents your rsync from erroneously writing data to your root partition instead.

[–] Archr 1 points 6 months ago

I want to say that that option is going to do that same thing that you tried before. Unsure as I have never used that option.

I was talking about the third or fourth option I think it's called install from windows executable.

[–] Archr 3 points 6 months ago (2 children)

You can download the installer to any folder you like. Use the plus button as the person above said. And you will probably be able to leave most settings as default. Just keep going through the prompts until it asks for the file.

If you run into issues. First go into the configuration and make sure that the executable is correct. (sometimes it points at the crash reporter executable)

If you get errors after that you might check protondb and see if people have other runner/wine suggestions. (you can get other versions with protonupqt).

I haven't run newvegas before. But it hopefully will just work tm.

[–] Archr 2 points 6 months ago

I also like lutris. But it being "for games" doesn't do it justice I think. It is basically just a wine environment manager. It advertises as being for games but it should work with just about any windows executable.

[–] Archr 5 points 8 months ago (1 children)

I did something similar (that my professor still talks about in class as a cautionary tale)

I ran chown -R user .* (intending to target all hidden files in the folder) and for people that don't know .* also matches .. (.. was / in this case) which changed the permissions on all files on the system to that user, including sudo.

We fixed it by mounting the root of the file system in a docker container which effectively gave us root.

view more: next ›