last update for me was on the 28th but i am also 1 day behind on updates due to custom image
last update for me was on the 28th but i am also 1 day behind on updates due to custom image
ZLast update was yesterday
ZAlright so the game boots normally in desktop mode
ZBut gets the mono error in gamemode
Hthats weird
ZCould it have something to do with the
ujust clean-system command perhaps?ZNah, couldn't be
Jthe trick is to set your build.yml cron to fire off 1h after the image you derive from, that way you're only ever 1h behind
Hi like to be behind by 24 hours though 
and manually fire off a build if i want to update earlier
and manually fire off a build if i want to update earlierJheh
Hespecially since its my production pc that has the custom build
ZUh.. clicking cancel apparently took me straight to the game anyways somehow
ZAlso, another strange issue, might be steam tho but I can't set the resolution in the game properties. It's like the game can see the monitor directly anyways and can pick those resolutions
KYou don't need refind for windows
KBazzite has grub, just install windows and it'll find it and add it to the boot menu
VIs there any good streaming option for my PC that can also change the resolution of my PC when streaming from Deck?
VIf my monitor was 16:9 I'd honestly deal with the letterboxing but 21:9 is a bit extreme
VOh, for wayland*
VAll fonts fixed. But now I have questions. Is there any particular reason why you layered steam, lutris, etc as rpm and not installed as flatpaks?
VAlso, cuda driver not included with nvidia driver. I want to install it so KDE system monitor could get nvidia GPU usage information and display it. Should I simply install it through rpm-ostree install? I'm not sure due to specific way of installing nvidia driver in ublue images.
Kno HDR support on the flatpak, no way to use Steam Input in Wayland on the desktop, and a performance penalty
Kwould also make deck & desktop builds function differently since you can't use the flatpak in gamescope as a compositor
Kxorg-x11-drv-${NVIDIA_PACKAGE_NAME}-{,cuda-,devel-,kmodsrc-,power-}${NVIDIA_FULL_VERSION} \Kshould be based on this, what package are you missing?
Vnvidia-smi
Kthat is defintiely there, it's part of our test to make sure nvidia is working
Kcan you run
rpm-ostree status for me?VState: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus-nvidia:latest
Digest: sha256:221a67232517b911612198097ed5b33a7354e1483d2982b0881851e9b3ac445d
Version: 39.20231229.0 (2023-12-29T17:32:53Z)
LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
virt-manager waydroid
ostree-image-signed:docker://ghcr.io/ublue-os/kinoite-asus-nvidia:latest
Digest: sha256:21149572e4d33f70e62e878311fe93c44bd8e786d0697ae8d060964241d275b6
Version: 39.20231230.0 (2023-12-30T16:21:36Z)
RemovedBasePackages: firefox firefox-langpacks 121.0-2.fc39
LayeredPackages: cloudflare-warp cockpit-networkmanager cockpit-ostree cockpit-packagekit cockpit-podman cockpit-selinux cockpit-storaged cockpit-system gnome-disk-utility uld
virt-manager waydroid
Pinned: yesVChecked system monitor right now. No nvidia dGPU information.
VAnd back when I used openSUSE TW, there were nvidia basic driver + cuda. Basic driver showed nothing for system monitor too, but when I searched for nvidia-smi, it said it was in CUDA package. So I installed it and system monitor started showing nvidia dGPU info.
Kcan you share the name of the package you installed?
KI'll take a look at ublue/nvidia and see what's up
Vnvidia-compute-utils-G06-545.29.06-18.1.x86_64And repo if matters: https://download.nvidia.com/opensuse/tumbleweed/x86_64/
VProbably, not even CUDA but some compute thing...
Klatest update should fix that
H@KyleGospo not sure if you can help me with this, but yet again today I can't use discord on my laptop it refuses to load up no matter what client I try
Krun it from the terminal, get any logs out of it?
Kflatpak run com.discordapp.DiscordHSeems like SSL failures prevent it from updating or starting or running
H-202 ERR_CERT_AUTHORITY_INVALID
HKis your timezone correct?
K5:38 don't look right to me
HLet me check
HYeah it's correct
HIt's 4:15 for me
HNot sure where it's getting 5:38 from Because my timezone is correct in settings
Hdouble check if its right in the bios
HI don't know what you mean by that
Hcheck if the clock in bios/uefi is correct
HNot sure how it helps the situation, but yes the time is correct
