Zoey The Trans Witch 🏳⚧✨💖 Posts

Zoey The Trans Witch 🏳⚧✨💖

Explore posts from servers

•Created by Zoey The Trans Witch 🏳⚧✨💖 on 11/12/2024 in #questions

I keep getting an ISO based on Fedora 39 and not 41 when building an ISO on silverblue image.

The Repo : https://github.com/ZoeTheTransHoe/zoeys-first-image Im trying to make my own silverblue spin. I want to base it off of Fedora 41, but despite adding

base-image: ghcr.io/ublue-os/silverblue-main
image-version: 41

base-image: ghcr.io/ublue-os/silverblue-main
image-version: 41

, going to then build an ISO from that repo makes it use Fedora SB 39 as the base, and not 41 as specified. Using latest instead of 41 doesnt fix my issue either. Im using podman but I can replicate the same issue with docker. The command Im using to build the ISO is:

mkdir ./iso-output

sudo podman run --rm --privileged --volume ./iso-output:/build-container-installer/build --security-opt label=disable --pull=newer ghcr.io/jasonn3/build-container-installer:latest \ 
IMAGE_REPO=ghcr.io/zoethetranshoe/zoeys-first-image \
IMAGE_NAME=weird-os \ 
IMAGE_TAG=latest \
VARIANT=Silverblue

mkdir ./iso-output

sudo podman run --rm --privileged --volume ./iso-output:/build-container-installer/build --security-opt label=disable --pull=newer ghcr.io/jasonn3/build-container-installer:latest \ 
IMAGE_REPO=ghcr.io/zoethetranshoe/zoeys-first-image \
IMAGE_NAME=weird-os \ 
IMAGE_TAG=latest \
VARIANT=Silverblue

Im using Fedora Silverblue 41 to build the ISO on. Im not sure why even after specifing multiple times for it to build the latest Fedora it picks one 2 releases old 😭. Im going to bed now so I wont respond for a while. This is acc gonna be the death of me and I know Ive just missed some obvious parameter I need to add or change and im too tired to spot it,

10 replies

UBUniversal Blue

•Created by Zoey The Trans Witch 🏳⚧✨💖 on 10/25/2024 in #🛟bazzite-help

Whole PC is incredibly choppy after wake from being put to sleep in Steam Big Picture

Posting to see if someone has a fix. System Info: Kernel : Linux 6.9.12-210.fsync.fc40.x86_64 Uptime: 15 hours, 33 mins Bazzite Version: bazzite-deck:stable - Bazzite 40 (FROM Fedora Kinoite) Hardware Info PC Name: OptiPlex 3080 CPU: Intel(R) Core(TM) i5-10505 (12) @ 4.60 GHz GPUs: AMD Radeon RX 6400 [Discrete] + Intel UHD Graphics 630 @ 1.20 GHz [Integrated] RAM: 8.83 GiB / 31.09 GiB (28%) HDD1: 632.76 GiB / 915.82 GiB (69%) - ext4 SSD1: 252.65 GiB / 476.94 GiB (53%) - btrfs SSD2 (Boot NVME SSD): 273.07 GiB / 475.35 GiB (57%) - btrfs [Read-only] Screen: 1920x1080 @ 60 Hz in 24" [External] When I boot a game within Big Picture, it plays perfectly fine, performance is as expected (e.g. 60 FPS locked in Hades, or around 120 FPS in Payday 2) and the steam UI is snappy at 60FPS. However, after putting the system to sleep using the power menu in steam big picture, upon rewaking the system not only do the games slow to a crawl at around 4-10 FPS, so does the steam UI. If I then close the game, steams UI returns to a locked 60FPS. When I reboot the game, it returns to its expected performance. Please Help! This is my only issue with bazzite so far, and so far I love it a lot aside from this issue. Im not a Linux newbie and willing to get dirty in the command line if need be. Games Tested: Hades (Steam) + Payday 2 (Heroic)

3 replies

Gaming

Programming