amel
amel
Explore posts from servers
UBUniversal Blue
Created by amel on 3/12/2025 in #🛟bazzite-help
Steam Virtual Keyboard not displaying at 100% height on dasktop mode
About a day ago Steam Virtual Keyboard stopped showing at full height when launched on the desktop mode, as shown in the video & screenshots below. It's functional of course, but I'm puzzled as to how/why this might have happened and how to fix. It's displaying normally on gaming mode. I haven't really done anything with my Deck, only the usual gaming mode to play <> desktop mode for file management switch. Scaling is at 100%, this is without a second monitor attached, running the latest stable deck image (41.20250301.1).
14 replies
BBlueBuild
Created by amel on 3/10/2025 in #questions
Github branches
Hi! I was wondering if there is a recommended way to fully utilize Github branches, if it's possible at all? In the past I've tried to create a branch and added extra tags in the recipe with something like :testing, and it built just fine, but rebasing to it wasn't possible, so I assumed it's only usable used to test & monitor builds.
13 replies
UBUniversal Blue
Created by amel on 2/24/2025 in #🛟bazzite-help
waydroid-script: cu.axel.smartdock_1100.apk md5 mismatch
Hi! The smartdock installation option is broken on ublue-os' waydroid-scripts fork due to md5 mismatch. Plus, there's an updated version (1.13.0) on F-Droid. I was wondering if the part of the script can be updated to both solve the md5 mismatch + update the version? The new version can be found here: https://f-droid.org/en/packages/cu.axel.smartdock/ (https://f-droid.org/repo/cu.axel.smartdock_1130.apk) Or perhaps opening a GH issue would be better? Thanks! logs
? Select Android version Android 11
? Please select an action Install
? Select apps ['smartdock']
INFO: Downloading smartdock.apk now to /home/reader/.cache/waydroid-script/downloads/smartdock.apk .....
11.9kiB [00:00, 13.4MiB/s]
WARN: md5 mismatches, redownloading now ....
11.9kiB [00:00, 22.5MiB/s]
WARN: md5 mismatches, redownloading now ....
? Select Android version Android 11
? Please select an action Install
? Select apps ['smartdock']
INFO: Downloading smartdock.apk now to /home/reader/.cache/waydroid-script/downloads/smartdock.apk .....
11.9kiB [00:00, 13.4MiB/s]
WARN: md5 mismatches, redownloading now ....
11.9kiB [00:00, 22.5MiB/s]
WARN: md5 mismatches, redownloading now ....
ublue-os' smartdock.py with version 1100:
class Smartdock(General):
id = "smartdock"
dl_link = "https://f-droid.org/repo/cu.axel.smartdock_1100.apk"
partition = "system"
dl_file_name = "smartdock.apk"
act_md5 = "f4087d34218eac902a5cca98ee03d215"
class Smartdock(General):
id = "smartdock"
dl_link = "https://f-droid.org/repo/cu.axel.smartdock_1100.apk"
partition = "system"
dl_file_name = "smartdock.apk"
act_md5 = "f4087d34218eac902a5cca98ee03d215"
2 replies
BBlueBuild
Created by amel on 2/14/2025 in #questions
Changing image base from Ublue images to vanilla Silverblue - what is the best approach?
Hi! I have a question, if I wanted to migrate my custom image's base from ublue's silverblue-main to Fedora's vanilla Silverblue, what would be the best way to do so successfully? I've tried doing so several times in the past w these steps: 1. Create a custom Silverblue image in my repo with quay.io/fedora/fedora-silverblue as base-image. This creates custom-silverblue-base 2. Builds just fine with the signing module 3. Update my existing result image recipe.yml (let's call this result-image) - base-image is replaced from ghcr.io/ublue-os/silverblue-main to gchr.io/username/custom-silverblue-base 4. result-image builds just fine with the signing module 5. result-image is deployed just fine on the target machine, boots & runs as expected 6. When running rpm-ostree update, it fails giving errors as such:
Error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: Error parsing signature storage configuration: "docker" namespace "ghcr.io/username" defined both in "/etc/containers/registries.d/result-image.yaml" and "/etc/containers/registries.d/custom-silverblue-base.yaml"
Error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: Error parsing signature storage configuration: "docker" namespace "ghcr.io/username" defined both in "/etc/containers/registries.d/result-image.yaml" and "/etc/containers/registries.d/custom-silverblue-base.yaml"
Some digging around made me think perhaps it has something to do w/ files under /etc/pki/containers and/or /etc/containers/registries.d/, but sudo ostree admin config-diff doesn't show that the files have been modified locally. Also, my cosign keys are unmodified, so this is not like the case of Bluefin's cosign keys from last year. I wonder if it would be more efficient to just create a new repo altogether? Would appreciate any input on this!
13 replies