Dualsense plugged in prevents PC from going to sleep

I have bazzite installed on my PC (deck version but switched it to start in desktop mode using "ujust _toggle-autologin".) In any case, I noticed if I have my dualsense controller plugged in, the computer will not respect my power options that I have set in KDE ie: when I have the screen set to turn off or when I have the PC set to go to sleep. If I unplug the controller, every thing works fine. Is there a way to figure out what is causing this issue and maybe get the system to still go to sleep when the controller is plugged in?
Solution:
ok so there is 2 things here 1. pc not sleeping while a controller is connected is by design to get around the issue of the pc going to sleep while playing a game for long periods of time with a controller, this is handled by joystickwake 2. _toggle-autologin is hidden in ujust because it is not meant to be used on the deck image as it breaks the session management and you can soft lock your system into a black screen on boot, it is only there for us to debug stuff in VMs and a super few other niche usecases, you are better off making your own custom image with the login screen enabled (this will also give you the lock screen back)...
Jump to solution
13 Replies
Solution
HikariKnight
HikariKnight3mo ago
ok so there is 2 things here 1. pc not sleeping while a controller is connected is by design to get around the issue of the pc going to sleep while playing a game for long periods of time with a controller, this is handled by joystickwake 2. _toggle-autologin is hidden in ujust because it is not meant to be used on the deck image as it breaks the session management and you can soft lock your system into a black screen on boot, it is only there for us to debug stuff in VMs and a super few other niche usecases, you are better off making your own custom image with the login screen enabled (this will also give you the lock screen back)
djwyman
djwymanOP3mo ago
How would I make my own custom image?
HikariKnight
HikariKnight3mo ago
https://github.com/ublue-os/image-template or https://blue-build.org if you want something that uses mostly yaml configs and script files with 0 docker knowledge (if you need support with it use their discord not ours)
GitHub
GitHub - ublue-os/image-template: Build your own custom Universal B...
Build your own custom Universal Blue Image! Contribute to ublue-os/image-template development by creating an account on GitHub.
BlueBuild
The easiest way to build your own desktop Linux images.
The BlueBuild project creates accessible tools for you to create, configure & build custom images of atomic Fedora distributions.
djwyman
djwymanOP3mo ago
lol ok that maybe a bit over my head. I unfortunately did run into this soft lock/black screen issue though. I did end up rebasing my system just now to the "desktop" version but that took away game mode...now I am back to regular big picture mode on steam without the cool extras...which was half of the reason to have bazzite in the first place... but atleast I was able to fix that black screen issue without wiping everything with my apps, settings, files and such.
HikariKnight
HikariKnight3mo ago
yeah if you want both without potentially breaking your system you will need a custom image. its literally just "base on bazzite-deck" and remove 1-2 files and disable 1 service
# Remove the autologin to gamescope-session
rm /etc/sddm.conf.d/steamos.conf

# Remove virtual keyboard on SDDM
# as this image is for workstations and permanently docked steamdecks
rm /etc/sddm.conf.d/virtualkbd.conf

# Disable the steam session management service
systemctl disable bazzite-autologin.service
# Remove the autologin to gamescope-session
rm /etc/sddm.conf.d/steamos.conf

# Remove virtual keyboard on SDDM
# as this image is for workstations and permanently docked steamdecks
rm /etc/sddm.conf.d/virtualkbd.conf

# Disable the steam session management service
systemctl disable bazzite-autologin.service
this will not work on the normal deck image as the files you remove from /etc/ will be restored when removed due to them being part of the defaults on the image you might be able to edit them but that might conflict with future updates so you will be on your own (since your edits will be prioritized)
djwyman
djwymanOP3mo ago
so in container file change "silverblue" to "bazzite-deck" and change "main" to "stable" correct? then where do I add those commands? also then lastly how do I then install it?
HikariKnight
HikariKnight3mo ago
which one you using, image-template or blue-build? oh wait change silverblue to bazzite suffix to -deck then add the above to the build.sh i believe
djwyman
djwymanOP3mo ago
the image-template
HikariKnight
HikariKnight3mo ago
yeah then its what i said above
djwyman
djwymanOP3mo ago
Ok I have the whole custom image built...however I am guessing I put the above commands in the wrong place as they didn't do anything. I ran them manually and I now have sddm but I am guessing I will lose those settings after an update on a side note my black screen issue was because I tried to use fish so for now I have scraped that idea
HikariKnight
HikariKnight3mo ago
you need to enable workflows for your github repository and build the image with the github action
djwyman
djwymanOP3mo ago
ok yeah I think I have it now. I had ran the ones that kept failing until I added the keys but never ran the main one again. to test if I got it working I added kpat(kde solitaire) using the build.sh and it worked so I think I have it now. Thanks I learned a whole new thing today lol. I have installed arch before but never really dealt with github outside of backing up my dot files or downloading something so this was neat. now knowing how to use this I may have to play with it more to see what else I can do. like fixing those ugly sddm themes it won't let me edit like I would on a normal distro.
HikariKnight
HikariKnight3mo ago
yep and once you have the image built you can rebase to it and you will have your own custom version of bazzite-deck
Want results from more Discord servers?
Add your server