ublue-os / bazzite Goto Github PK

Xpadneo does not support the Xbox wireless adapter whose non-BT wireless connection is more reliable than BT. The xone driver exist to remedy that: https://github.com/medusalix/xone/
However there is the catch that the maintainer is currently not active and a few forks exist that are currently hoping for a merge to upstream than collaborate on a fork which would mean some downstream picking of unmerged patches...:

Not sure how fixable it is, but within a Gamescope session, the sleep animation doesn't play, and instead the Deck immediately sleeps. In and of itself, this isn't a big deal, but it causes the following issues:

• Big Picture's power menu cannot be triggered via the power button.
• When attempting a hard shutdown, the Deck immediately sleeps, then immediately turns on again. If continuing to hold down the power button, a hard shutdown will then work five seconds after the Deck wakes up again (as indicated by the haptic chime).

Only affects Steam, in both Game Mode and Desktop Mode.

More info: ValveSoftware/steam-for-linux#9418

Workaround (for some reason it does not work for Korean and also the update screen before entering Game Mode):

$ rpm-ostree override remove google-noto-sans-cjk-vf-fonts
$ rpm-ostree install google-noto-sans-cjk-fonts

sudo ostree fsck is reporting some corrupted file objects, so I deleted them with sudo ostree fsck --all --delete.
I see stock Fedora have the ability to pull the corrupted commits directly from HTTP-based remotes, is it possible to do the same with Bazzite?

The only workaround I found so far is to rebase to stock Fedora then rebase back but that seems too complicated to me.

I put iso with fedora writer on usb thumb the iso boot pass 100% verify correctly the checks pass and cannot pass after this check iso need a fix i try Disable Secure Boot and TPM disable booth at same time and not works i try again only with tpm enabled with UEFI disable not pass help on this iso

"""""""""""""""""""""""""""""""""""""""""""SPECTS""""""""""""""""""""""""""""""""""""""""""

• CASE: MSI ATX MAG Vampiric 100R ARGB
• CPU:AMD RYSEN 5 1600AF 3.2GHZ
• RAM:G.SKILL 16GB DDR4 3200HZ OC
• MOTHERBOARD:ASUS EX-A320M-GAMING
• GRAPHIC CARD: SAPPHIRE RX 570 NITRO+ 4GB GDDR5
• M.2: XPG SPECTRIX S40G - 256GB
• SSD: MSI SPATIUM S270 -480GB
• SSD: TEAM GROUP 120GB SATA III L3 EVO
• HD: 2TB HD TOSHIBA + 1TB HD WD ELEMENTS USB 3.0
• MONITOR: LG-28TL520S-PZ 28 POL
• KEYBOARD: KROM KYRA RGB GAMING PT
• MOUSE: MARS GAMING MMW2 WIRELESS MOUSE
• SPEAKERS 2.1+SUBWOOFER
• SOUNDBAR "ELEGIANT" 2.1
• MICROPHONE: MARS MMICKIT 7-IN-1 MICROPHONE
• GAMEPAD PC: 8BITDO ULTIMATE WIRED CONTROLLER
• BOX TV: MINIX NEO U1(ANDROID 5.1)
• MOBILE PHONE: XIAOMI REDMI 5(ANDROID 8.1) MIUI 11(Black)
• GAMEPAD ANDROID: MOCUTE 050 BLUETHOOT
• GAMEPAD ANDROID/PC MOCUTE 052 VR BLUETHOOT
• OCULOS VR MOBILE QLIVE
• SO: WINDOWS 11 X64 PRO PT-PT
• SO: Linux SteamOS Holo 3.4 iso for Desktop Linux Or ChimeraOS
  i cannot pass on this my record video with my mobile https://www.youtube.com/shorts/h4KtL2m9tIE?feature=share

For the KDE flavor of Bazzite (Steam Deck iteration), sometimes the file picker will default to the GTK one instead of KDE's. I was using Ryujinx installed through Emudeck when I noticed this. How I've resolved this is adding the following to /etc/environment.

GTK_USE_PORTAL=1
XDG_CURRENT_DESKTOP=KDE
GDK_DEBUG=portals

It's probably a bit overboard and I'm unsure of any consequences, but I haven't had the issue since.

Steam controller shortcuts do not work in gamemode.

e.g. With xbox controller "Xbox Button + A" normally brings up quick settings menu, but does nothing on bazzite. Same for Xbox + X to bring up the virtual keyboard.

For context, I have bazzite-deck-gnome installed on PC.

When selecting the "Start Steam in Big Picture Mode", it fails with the following errors:

sed: can't read /home/deck/autostart/bazzite-arch-steam-slient.desktop: No such file or directory
mv: cannot stat '/home/deck/autostart/bazzite-arch-steam-silent.desktop': No such file or directory
error: Recipe enable-big-picture failed with exit code 1
Installation Complete!

I installed the base Bazzite with a user called deck.
My machine is an Intel i7 4790, AMD Radeon RX 580 8GB, 32GB RAM and using a 1TB HDD for test install.

I was trying to see if I could install Bazzite on a VM and try to run World of Warcraft on Lutris out of the box. This would require installig Vulkan drivers on the bazzite-arch distrobox container. Sort of like: https://github.com/lutris/docs/blob/master/InstallingDrivers.md

Here's what currently happens

Does adding this sound like a good idea?

Integrate in a generic-handheld image handygccs

If desktop auto-login is enabled using just enable-desktop-autologin, the Return to Gaming Mode desktop script won't activate Gamescope. It's scripted to kill the KDE or Gnome session, and then it auto boots into a desktop session or gamescope-session.

Is it possible to change the scripting so it detects a KDE or GNOME session, kills it, then launches gamescope-session?

As a bonus - a just script could be made later to switch gamescope-session to use the SteamOS Game Mode UI, or OpenGamepadUI.

Night mode works properly within Plasma, but has no effect in Gamescope Big Picture.

I've migrated to Bazzite from HoloISO on my Home Theater PC and immediatelly noticed very significant performance degradation when running games from steam gameui.

On HoloISO for the same games I've tried I was easily getting 140+ FPS on native 4k, however after switching to Bazzite I'm lucky if I can even get 30FPS on native 4k within the same game. Given that the hardware is literally identical, there must be something amiss withing Bazzite.

Here's my hardware as Bazzite sees it in case it helps.

On SteamOS, the Manual GPU Clock Control option brings up a slider where the GPU clockspeed can be forced to a specific value with a slider. On Bazzite, enabling this option never shows its respective slider.

Trying to install the bazzite deck and have reflashed,redownloaded,used different usbs,for this image,and they all have (during the install) the error “ostree container image deploy —sysroot=/mnt/sysimage —image=ghcr.io
/ublue-os/bazzite-deck:38 —no-signature-verification’ exited with the code 1”. pulling my hair out over this.

Any time I click on the "Return to gaming mode" icon on the desktop the screen goes dark followed by the startup animation. The desktop appears and then steam opens. When opened my account is signed out and by signing back in nothing happens. Big picture mode doesn't achieve the same effect because I can't use multiple features of the regular deck menu.

Upon starting a new game or loading an existing save, the RAM usage increases until it hits 14 gigs, at which point the game either crashes, or more commonly the Deck crashes. This happens within 10 seconds.

I've tried it with the Bazzite and Legacy memory options, I've tried both the GE and regular Proton.

The game worked correctly on SteamOS.

for video wallpaper on GNOME Desktop
gnome-ext-hanabi

SteamOS Default ucm2 settings for the acp5x seem to have it output a bit louder than the defaults we pull from jupiter-hw-support. If we can adjust the following params in Hifi-Upstream.conf and HiFi.conf it should match up properly.

cset "name='Left Digital PCM Volume' 817" -> cset "name='Left Digital PCM Volume' 913"
cset "name='Right Digital PCM Volume' 817" -> cset "name='Right Digital PCM Volume' 913"

I've noticed that OS update from gamemode aren't very clear and doesn't show any changes. Could be useful to show the same list you can see from Software (in gnome desktop mode) or the change from this repo

I would think of sugar candy with some custom backgrounds.

I already made some.

The workaround is to layer "sddm rpms", a really nice project by Lunarequest but it could make the distros stand out more.

The themes have to be tested against bugs, as these sometimes occur.

You can't modify them at all on Kinoite, so the backgrounds have to be fix.

Using GNOME on the Steam Deck feels snappy and intuitive (especially once you figure out you can use backplate buttons for Activities overview and workspace switching), however, there is a major issue with GNOME Search on the Steam Deck. Instead of being drawn over the Activities overview, the Steam Deck keyboard window is created in the active workspace and is only present there.

I keep getting this error message, the installation always stops at this point. Have already tried various things. Installation on microSD, USB stick or external NVMe nothing works.

Using GNOME on the Deck is great, however it could be potentially confusing for a first time user unfamiliar with the default controller layout provided by Steam.
Similar to how GNOME Tour showcases touchpad gestures, there could be a tutorial on the additions and quirks that set the GNOME experience on the Deck apart. For example: hey did you know we've got a helpful menu to the top left that you can click on and do things with? Or that you can press the bottom left L5 back grip button to open Activities, and then switch between workspaces with top and bottom right R4 and R5 back grip buttons? Have something like this communicated but with a pretty UI.

Low Severity: With bazzite version 37.20230221.0 (2023-02-21T16:53:51Z), ChimeraOS desktop crashes after login before anything displays.

Replication Steps:

1. start from KDE login screen after boot.
2. log in with ChimeraOS (gamescope) selected.
3. screen turns to black.
   i. (optional) upon key press, terminal characters show up e.g. ^[, ^D. disappears upon step 5.
4. black screen with mouse cursor visible and movable.
5. desktop session crashes. forced back into KDE login screen.

Workarounds: This issue does not occur with KDE X11 and KDE Wayland. After logging in with the KDE desktop environment, I can also launch Steam and enter Big Picture mode easily.

Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:latest
                   Digest: sha256:97ccd3ce94e88c91f4164fa62c8a5f43ae629c658d6edba56e473a44f8438861
                  Version: 37.20230221.0 (2023-02-21T16:53:51Z)
          LayeredPackages: openssl printer-driver-brlaser virt-manager
            LocalPackages: vktablet-1.2.1-3.x86_64
             InitramfsEtc: /etc/vconsole.conf
[...]

Hardware Info below.

boxkit:~$ neofetch --off
[email protected] 
----------------------------- 
OS: Alpine Linux v3.17 x86_64 
Host: 80X7 Lenovo YOGA 720-15IKB 
Kernel: 6.1.11-200.fc37.x86_64 
Uptime: 29 mins 
Packages: 395 (apk), 149 (flatpak) 
Shell: bash 5.2.15 
Resolution: 3840x2160 
DE: Plasma 
WM: kwin 
Theme: Breeze [GTK2/3] 
Icons: breeze-dark [GTK2/3] 
Terminal: conmon 
CPU: Intel i7-7700HQ (8) @ 2.800GHz 
Memory: 5069MiB / 15723MiB 
GPU: Nvidia GTX 1050M [GP107M]

[tacohut@yoga-fedora ~]$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 05)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 (rev 31)
00:15.1 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #1 (rev 31)
00:15.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #2 (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #6 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13 (rev f1)
00:1e.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO UART #0 (rev 31)
00:1f.0 ISA bridge: Intel Corporation HM175 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
40:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963

Don't know how realistic this will be until Red Hat finishes with the new installer, but the lack of an on-screen keyboard in current Anaconda makes it impossible to install the system without a USB keyboard - something that SteamOS can do. The hitch was on setting up a new user and having to input a username and password for one. SteamOS makes a 'deck' user out of the box with no password. Maybe there's a way to do that with Kickstart?

I guess it would be better for it to be installed by default on the desktop image because it allows for compatibility with programs like EmuDeck / DeckyLoader

In Gamescope Big Picture's display settings, the "Enable Adaptive Brightness" setting is greyed out and cannot be activated.

During gameplay, colour saturation seems lower, when i open steam ui (even qam), colours gains saturation but return the previous state when closed

Had to reinstall bazzite (rebased from regular Kinoite) and the window to configure what you want installed doesn’t pop up

Using the default kernel arguments the Steam Deck fails to properly load amdgpu

Removing Nvidia related arguments as well as nomodeset addresses this allowing amdgpu to load successfully

I've been trying to use the online installer to get Bazzite GNOME working on my steam deck. I got on my network and the installer started, but it freezes on the following screen:

Can someone help me out here? I don't have a lot of experience with Dracut so I don't know how to fix this.

Distrobox with the --nvidia flag is supposed to copy the host's Nvidia drivers into the container. It seems this may be incomplete, as currently this results in a broken installation.

This is a blocker for desktop 1.0

I just rebased from Universal Blue's Kinoite to the latest bazzite on my desktop. After I rebased with rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:latest in the terminal, and rebooted. The Bazzite Portal YAFTI application appeared as usual. It could not find any justfile recipes for any of the exclusive Bazzite ones, like installing the Nix package manager and CoreCtrl.

I rebooted again after finishing the firstboot sequence. Bazzite Portal appeared once again with the same errors if I attempted to install Nix and CoreCtrl

To confirm I am on Bazzite:

I also have the preinstalled Bazzite packages like btop++ and DDC Control which I did not have preinstalled before the rebase.

Decky stuck during and update and after that it doesn't work anymore even trying with reinstall from repo

Edit: reinstalling from first start wizard works but some plugins throws unexpected error

In the Gamescope session, MangoHUD works properly in games, but not within Big Picture itself.

After setting Steam to use the Beta client in the game-mode session, Steam will revert back to Stable on switching between game-mode and desktop.

Not sure how fixable it is, but no options have any effect at all. May be related to #57?

On normal X I can push 3440x1440@100hz with no issues but in Wayland I can only use 60hz. The other options black screen.

My weaker laptop can do 100hz just fine on Wayland with the same resolution on the same dock. I think displaylink is to blame since I dont use that on my laptop and freesync is enabled on the monitor if that helps.

Trying to install the bazzite deck image and keep getting greeted by this error.

I tried to remote play to my Steam Deck running Bazzite Deck version from my i7 4790, RX 580 running Bazzite Deck version. As soon as it tries streaming, the client gets a scrambled frame and then stops receiving data. The host will disappear for a few moments until Gamemode relaunches.

I have had the same issues with Nobara Steam Deck edition and ChimeraOS, Nobara was able to pull in a upstream patch from gamescope to fix it.

In the game mode update menu, the OS Update Channel is shown as "No branch script was found, bra", and the update version shown on checking for software updates is shown as a series of percentages.

Used Rufus to write the install image, tried two types of media (USB flash Disk and USB SSD) Bazzite gnome Nvidia, started install using basic graphics.

After I choose the initial options, I get the error:

Error Image

I'm not sure how to proceed with the install.

Thanks.

There used to be a .desktop file for Clapper in /use/share/applications which has recently disappeared, so it does not appear in the GNOME applications list now.

On the Steam deck, the max volume seems lower after a recent update. There was a time where the boot sound was wildly loud, but how even with volume set to the max, it is still too quiet compared to Steam OS.

why fedora TT

Hi,
tried to connect 2 Xbox Series X Controllers with bluetooth. Controller shows up in settings / bluetooth. But pairing doesn't work.
Tried othe BT devices (mouse, keyboard) which worked.

Any ideas?

bluetoothctl

[Xbox Wireless Controller]# info
Device F4:6A:D7:D2:11:3E (public)
	Name: Xbox Wireless Controller
	Alias: Xbox Wireless Controller
	Appearance: 0x03c4 (964)
	Icon: input-gaming
	Paired: no
	Bonded: no
	Trusted: no
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Vendor specific           (00000001-5f60-4c4f-9c83-a7953298d40d)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
	UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v045Ep0B13d0511
	ManufacturerData Key: 0x0006 (6)
	ManufacturerData Value:
  03 00 80                                         ...             
	Battery Percentage: 0x32 (50)
[DEL] Device 86:A9:3E:35:28:85 86-A9-3E-35-28-85
[Xbox Wireless Controller]# devices
Device F4:6A:D7:D2:11:3E Xbox Wireless Controller
Device 3C:FA:06:05:2A:37 Xbox Wireless Controller
[DEL] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0008
	00001801-0000-1000-8000-00805f9b34fb
	Generic Attribute Profile
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0009/char000a
	00002a29-0000-1000-8000-00805f9b34fb
	Manufacturer Name String
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0009/char000c
	00002a50-0000-1000-8000-00805f9b34fb
	PnP ID
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0009/char000e
	00002a26-0000-1000-8000-00805f9b34fb
	Firmware Revision String
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0009/char0010
	00002a25-0000-1000-8000-00805f9b34fb
	Serial Number String
[DEL] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0009
	0000180a-0000-1000-8000-00805f9b34fb
	Device Information
[DEL] Descriptor (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0012/char0013/desc0015
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0012/char0013
	00002a19-0000-1000-8000-00805f9b34fb
	Battery Level
[DEL] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0012
	0000180f-0000-1000-8000-00805f9b34fb
	Battery Service
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0024/char0025
	00000002-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0024/char0027
	00000003-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0024/char0029
	00000004-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[DEL] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_F4_6A_D7_D2_11_3E/service0024
	00000001-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[DEL] Device F4:6A:D7:D2:11:3E Xbox Wireless Controller
[CHG] Device 3C:FA:06:05:2A:37 Connected: yes
[NEW] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0008
	00001801-0000-1000-8000-00805f9b34fb
	Generic Attribute Profile
[NEW] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009
	0000180a-0000-1000-8000-00805f9b34fb
	Device Information
[NEW] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009/char000a
	00002a29-0000-1000-8000-00805f9b34fb
	Manufacturer Name String
[NEW] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009/char000c
	00002a50-0000-1000-8000-00805f9b34fb
	PnP ID
[NEW] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009/char000e
	00002a26-0000-1000-8000-00805f9b34fb
	Firmware Revision String
[NEW] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009/char0010
	00002a25-0000-1000-8000-00805f9b34fb
	Serial Number String
[NEW] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0012
	0000180f-0000-1000-8000-00805f9b34fb
	Battery Service
[NEW] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0012/char0013
	00002a19-0000-1000-8000-00805f9b34fb
	Battery Level
[NEW] Descriptor (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0012/char0013/desc0015
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0024
	00000001-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[NEW] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0024/char0025
	00000002-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[NEW] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0024/char0027
	00000003-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[NEW] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0024/char0029
	00000004-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[CHG] Device 3C:FA:06:05:2A:37 UUIDs: 00000001-5f60-4c4f-9c83-a7953298d40d
[CHG] Device 3C:FA:06:05:2A:37 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 3C:FA:06:05:2A:37 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 3C:FA:06:05:2A:37 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device 3C:FA:06:05:2A:37 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device 3C:FA:06:05:2A:37 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device 3C:FA:06:05:2A:37 ServicesResolved: yes
[CHG] Device 3C:FA:06:05:2A:37 Modalias: usb:v045Ep0B13d0517
[CHG] Controller A0:80:69:F5:1A:03 Discoverable: yes
[CHG] Controller A0:80:69:F5:1A:03 Discovering: yes
[NEW] Device 86:A9:3E:35:28:85 86-A9-3E-35-28-85
[DEL] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0008
	00001801-0000-1000-8000-00805f9b34fb
	Generic Attribute Profile
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009/char000a
	00002a29-0000-1000-8000-00805f9b34fb
	Manufacturer Name String
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009/char000c
	00002a50-0000-1000-8000-00805f9b34fb
	PnP ID
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009/char000e
	00002a26-0000-1000-8000-00805f9b34fb
	Firmware Revision String
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009/char0010
	00002a25-0000-1000-8000-00805f9b34fb
	Serial Number String
[DEL] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0009
	0000180a-0000-1000-8000-00805f9b34fb
	Device Information
[DEL] Descriptor (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0012/char0013/desc0015
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0012/char0013
	00002a19-0000-1000-8000-00805f9b34fb
	Battery Level
[DEL] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0012
	0000180f-0000-1000-8000-00805f9b34fb
	Battery Service
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0024/char0025
	00000002-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0024/char0027
	00000003-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[DEL] Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0024/char0029
	00000004-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[DEL] Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_3C_FA_06_05_2A_37/service0024
	00000001-5f60-4c4f-9c83-a7953298d40d
	Vendor specific
[DEL] Device 3C:FA:06:05:2A:37 Xbox Wireless Controller
[DEL] Device 86:A9:3E:35:28:85 86-A9-3E-35-28-85
[bluetooth]# 

Thanks,
Helmut

I think something along these lines would work:

I was going to make a pull request, but I didn't exactly do that right last time and this is not a major priority right now. This should try to warn the user in an event where setting up then going straight into Game Mode might cause YAFTI to appear if they return to Desktop Mode without rebooting after initial setup.

Did an install of the Deck version, goes to desktop, won't go to game mode. Also the desktop is rotated the wrong way, it's upside down.

running : sudo env RUST_LOG=debug system76-scheduler daemon

DEBUG 91733 created by 85799 (git)
DEBUG 91739 created by 85799 (htop)
DEBUG 91740 created by 1 (modprobe)
DEBUG 91741 created by 1639 (qdbus)
DEBUG setting 90682 as foreground process

it seem to detect process but does not apply nice value from the config file.