why not just use a separate user for gaming?
why not just use a separate user for gaming?
Bsteam puts everything in your $HOME/.steam by default, even flatpak'd
II considered it, but It wouldn't be convinient for me
Ialso flatpaks will still be an issue
Bnot if you only install the flatpaks for that user
Bflatpak install --user project.nameISee the example I linked. Bazzite installs flatpaks systemwide
IAm I misunderstanding your suggestion?
Bno, i misunderstood you, i thought you just wanted to separate your gaming, but you want to seperate your entire os
Bbut you can install flatpak's for that user, even in bazzite
BIIRC you just need to add the remote for the
--user option, and then you can install it either via discover/gnome software or via cliIthey will also be installed system wide and Im proposing a "flag" to make this easier for everyone to "image hop" (is this a phrase or can I say that I coined it?)
ICreating a separate user and installing all the flatpaks again means tens of gigabytes of wasted space and I wouldnt be able to start a quick Rocketleague game while I'm waiting for something to finish
Ianyway, lets wait for kyle to get his opinion. I can just create the files needed to skip any installs in my user/system. I'm just trying to solve once and for everyone like me.
PIn my spare time I’ve been chipping away at getting multi-Unix-user Steam working properly so your flatpaks are isolated (don’t want others opening your discord/chrome!!) and got as far as making a shared game directory, but I need to revisit ensuring permissions stay consistent.
Not sure if it would be better to play with file system attrs or write a service
Not sure if it would be better to play with file system attrs or write a service
Bnot sure what you've tried already, but you could try a service that on boot that basically sets
GAMES_DIR=/var/opt/games chown -R nobody:nobody "$GAMES_DIR" && chmod -r 777 "$GAMES_DIR" and a user service that when logged in, takes owner ship of that directory and/or symlinks it to your steam dirBi'm really priviledged that no one else uses my computer for anything, so i havent ran into these kind of issues
KCan you send me that patch again? I'll double check
AUnfortunately no patch
AIt got upstream 2 months ago
KOh, then all we need is that service?
KThat's easy, I'm happy to add that
AProbably better to pull the patch from the upstream kernel
AIt's part of Linux as of two months ago, see the Asus WMI history for it
KIf it's upstream and simply not in a released kernel then we should be getting 6.7 here within a week or two
AYep
A6.7 should also include the driver for the 323 IMU in the ally. But you still need patch 3 of the series to load it in the allu
APatches 4 and 5 might not be required for hhd but I have not checked
LHow do I update AMD drivers on Bazzite? If I get no signal from the previous driver should I not even update it? Im so confused. After bios screen and selecting which OS version of Bazzite to use, I kept getting no signal on my monitor and a black screen, so I added the nomodeset to the boot options and now I can enter the desktop.
KAMD drivers are built into the Linux kernel, there's nothing to update
KWhat GPU do you have?
LAMD RADEON RX 6800 XT
LIm not sure how to fix whatever is causing the issue so i can put the display mode back to normal
Lthe screen resolution while doing this is terrible
KSomething silly going on, I'm daily driving a 6900 XT without issue
LCould it be a desktop effect in system settings? If so I dont even know how to turn it off if I cant enter the desktop with normal boot options
Lis there a way to put stuff at default for screen resolution etc, for when i boot normally
Lwithout nomodeset
LI tried entering recovery mode with init=/bin/bash/ in grub boot settings, but it had the same issue as starting the desktop normally getting no signal again
LBasically I need to revert the KMS(for display) to default settings somehow, but I have no idea how to do so.
LMade a little summary here; Problem:
Was using desktop normally and had to reboot after desktop froze.
The monitor now gets no signal when attempting to boot into the OS.
I attempted to boot into a recovery mode and that also gets no signal.
Adding nomodeset in grub, allows me to boot into and access and use the desktop.
I'm using an AMD RX 6800 XT GPU.
Possible Solution Question:
How do you revert KMS Display Settings to default if you can only access the desktop with nomodeset? While in nomodeset I don't even see everything I had installed like desktop effects for instance, so I don't know how to remove them if I can't see them. I assume that if I were able to revert KMS display settings to default and save them, that next time I try to boot normally, I will be able to see the desktop again without getting no signal.
Was using desktop normally and had to reboot after desktop froze.
The monitor now gets no signal when attempting to boot into the OS.
I attempted to boot into a recovery mode and that also gets no signal.
Adding nomodeset in grub, allows me to boot into and access and use the desktop.
I'm using an AMD RX 6800 XT GPU.
Possible Solution Question:
How do you revert KMS Display Settings to default if you can only access the desktop with nomodeset? While in nomodeset I don't even see everything I had installed like desktop effects for instance, so I don't know how to remove them if I can't see them. I assume that if I were able to revert KMS display settings to default and save them, that next time I try to boot normally, I will be able to see the desktop again without getting no signal.
Twhen i get on the desktop ill link the draft. It's a public hackmd link. Need to improve it but you can have the link saved somewhere and do it whenever
PIs this something I need to worry about? Unsure if it meant run that now, or after the update has been applied.
Hehh you on a bios install? not uefi install?
PYeah I'm on bios install so that would make sense. Odd that it would notify me about that then...
Hit notifies you about it since bios install is really not expected as far as i know, it is not an expected install due to it being deprecated many years ago so there is no check in place if you are on a bios install or not.
Hbut yes @pure you can ignore the message since its only needed for secure boot
KOut of an abundance of caution it's notifying everyone
KWhen the next update launches next weekend that message will disappear for you and everyone else
KIt was the best way to make sure everyone was aware of it
KI suppose in your case it's also useful because you should not be using the bios mode regardless
