Qvest
Explore posts from serversUBUniversal Blue
•Created by Qvest on 1/13/2025 in #🛟bazzite-help
custom shortcuts reset in reboot
So I've got a weird problem with a custom image of Bazzite created using BlueBuild, in which the shortcuts I set in KDE settings are reset after a full reboot. The image doesn't have many changes, only package changes (adding and removing packages) and setting some extra options, nothing custom-made by me so I don't think BlueBuild is to blame.
By the way, the only shortcuts I set are to change from ptyxis to konsole and an extra one for a flatpak app. Another thing of note is I also remove ptyxis from the image, but even then the shortcuts reset (even the extra one for the flatpak gets deleted as far as I remember). If anyone has any insight into what could be the cause for this I would appreciate it. In case it's needed, here's the image recipe's link: https://github.com/MrQvest/my-atomic/blob/main/recipes/recipe-bazzite-nvidia.yml
Thanks for your time and any answers!
13 replies
BBlueBuild
•Created by Qvest on 1/13/2025 in #questions
custom shortcuts reset in reboot
Hey, this is not really up-to-date with current BlueBuild, but seeing as no other posts have been made about this I am assuming this is still ongoing, sorry if this has been solved already.
So basically, while trying to use a custom Bazzite built with BlueBuild a couple months back, I was having this weird issue where my Konsole shortcut would be replaced by the upstream (ptyxis) one, even after removing ptyxis from the system at build time in recipe.yml.
Not only that, but other shortcuts from flatpaks I installed would also reset and disappear upon rebooting. Would this be an issue with upstream bazzite or BlueBuild? Or is it an issue with my config (I've only added and removed packages, no custom modules made by me, trying to leave as simple as possible)? As always, thanks for your time and any answers!
12 replies
BBlueBuild
•Created by Qvest on 12/3/2024 in #questions
error: Could not depsolve transaction; 1 problem detected
Hello, I've been getting this message after trying to make a custom image: https://github.com/MrQvest/my-atomic/
Example of a bad Github Action: https://github.com/MrQvest/my-atomic/actions/runs/12144458198
It says there is a problem, but it doesn't specify where or what is wrong:
[17:02:33 g.i/m/my-kinoite-nvidia:latest] => 13.88 error: Could not depsolve transaction; 1 problem detected: [17:02:33 g.i/m/my-kinoite-nvidia:latest] => 13.88 Problem: conflicting requestsThe only things I have changed are recipe.yml and build.yml
8 replies
BBlueBuild
•Created by Qvest on 9/8/2024 in #questions
Run Failed: unable to parse image ghcr.io/MrQvest/my-ublue invalid reference format
Builds were successfull yesterday, but scheduled rebuilds and even manual builds are failing with this error.
Image repo: https://github.com/MrQvest/my-ublue
Relevant (maybe?) log:
[11:52:12 ERROR] => Failed:
× Unable to parse image ghcr.io/MrQvest/my-ublue
╰─▶ invalid reference format
Error: Process completed with exit code 1.
Everything goes well until this step, where it fails8 replies
UBUniversal Blue
•Created by Qvest on 2/6/2024 in #🛟bazzite-help
Trying to build a custom image from startingpoint using bazzite-gnome-nvidia
I've been trying to make a custom image for the last couple days, without much success. I'm trying to build a bazzite-based image using the startingpoint. I've used the automatic web setup in the Tinkerer's guide on the website. The only things I changed were the
recipe.yml
to get base-image: ghcr.io/ublue-os/bazzite-gnome-nvidia
and install
remove
. The error I get is the following (in the build custom image job):
Resolving dependencies...done
error: Could not depsolve transaction; 1 problem detected:
Problem: conflicting requests
error building at STEP "RUN chmod +x /tmp/modules/rpm-ostree/rpm-ostree.sh && source /tmp/exports.sh && /tmp/modules/rpm-ostree/rpm-ostree.sh '{"type":"rpm-ostree","repos":null,"install":["neovim","strawberry","papirus-icon-theme"],"remove":["clapper","vim","waydroid","lutris","winetricks","protontricks","gnome-shell-extension-hanabi","waydroid-selinux"]}'": error while running runtime: exit status 1
time="2024-02-06T18:20:46Z" level=error msg="exit status 1"
[2024-02-06T18:20:46Z ERROR blue_build::commands] Failed to build ghcr.io/mrqvest/my-ublue
Error: Process completed with exit code 1.
Can anyone give me some pointers on how to solve this?7 replies