AYou have the right to unlock your own session I'm pretty sure
Aloginctl --unlock anyone?
HI'm having some unreasonably bad performance on my Steam Deck right now
Hand I'm using custom drivers no less
AI meant the gnome bug
AIt's dynamic in both
AThe os allocates as if needs
Kis it not recommended to show your UUID's of your drives?
ANobody cares
Pre-enabled proton is genius
Hit changes each time you reformat the partition, its just meant to be unique to avoid conflicts with other partitions
Kthanks. yea I just asked because of the prior messages, I thought that might be too sensitive data ... xDD
HEven on Windows?
HYeah the games are giving me a low VRAM error and I'm getting mega hitches
KGitLab
Known affected versions: OS: Fedora Silverblue 39, Fedora Workstation 39, Bazzite-GNOME 39 GNOME Shell Version: 45.4 Appears in: XORG & Wayland
K
HKAThink so
AAmind the fact that some games hate it
Aboth on win and linux
HThis performance is not consistent
HKDE gang represent, the superior DE
KFirst update!!!
(I triggered it myself
)
(I triggered it myself
)
Ksudo show progress bar --pls
Aofc its written in rust
Ayes lets not fill in the printer callback lmao
KI wish, I could follow you 
JUhm.
FIssue closed, wontfix.
Aguys it cant be fixed, your user has the right to unlock its sessions
Arun these commands, they unlock kde too
Athe problem is that the joy lib calls the unlock command of the screensaver
Kif that's the case, the bigger issue is gnome has no way to prevent a screen lock that doesn't also unlock the device
Ayes the gnome lockscreen is meh
Ayou also cant programmatically make it lock on login
Aand you need an extension for it to not blank in 5s
Aat least it supports fingerprints, <looks at sddm>
FHaving fingerprint on gamepad to unlock remotely through Bluetooth would be great
For just install joycon & enjoy
Almao
JThe user having the right to unlock their session isn't the issue, rather there are a number of supported mechanisms for unlocking, namely A) password B) fingerprint. AFAIK pressing a game controller button isn't one of them. Either this should be fixed/mitigated in gnome-shell, or somewhere lower in the stack like PAM or systemd
JAlso, like, "just run it in flatpak" isn't a solution because what malicious script author would want to make their job more difficult?
JThe ublue project serves to integrate a whole bunch of software in their images outside of flatpak which means a lot of software is being run in the same security context
KIf I want to ship joystickwake as-is
KI'm gonna have to modify it to check if you're on gnome, then check if you're locked, then do nothing
JIt's pretty ridiculous you would have to do that in the first place because people will know about this development and use it as ammunition to show that Gnome developers are out of touch
AYou should open an issue since it uses the wrong command
