from cosmic greeter I can not launch GNOME on Wayland. Last time I checked only GNOME on Xorg worked.

I will try from tty with gnome-session --session gnome-wayland

Loging in with cosmic-greeter causes a panick on my qemu virtual machine based on fedora silverblue with the response:

thread 'main' panicked at greetd/src/session/worker.rs:280:14:
unable to exec: EACCES
note: run with 'RUST_BACKTRACE=1' environment variable to display a backtrace

This is possibly due to my many attempts with rollbacks in between to get cosmic working (it was because I was using the virtio graphics driver instead of QXL). Loging in from GDM seems to work fine though

When trying to run the image getting the error blow.

Operating System: Bazzite 39
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12
Kernel Version: 6.7.5-201.fsync.fc39.x86_64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 980/PCIe/SSE2

sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/ryanabx/fedora-cosmic-atomic-silverblue:latest-amd64
Pulling manifest: ostree-unverified-registry:ghcr.io/ryanabx/fedora-cosmic-atomic-silverblue:latest-amd64
error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: reading manifest latest-amd64 in ghcr.io/ryanabx/fedora-cosmic-atomic-silverblue: manifest unknown

I tried following the Readme on a test machine with Silverblue installed. The rpm-ostree step results in the error message:

error: Preparing import: Fetching manifest: containers-policy.json specifies a default of 'insecureAcceptAnything'; refusing usage

I'd love to see a Developer Edition of this when it's ready. Just like Bluefin and Aurora have.

I am trying cosmic-kinoite:40 in a qemu VM, and it doesnt work at all for some reason.

I wonder why that would be.

cosmic-greeter is flickering black and then disapperaring, flickering black and disappearing, nothing shows. Exiting to TTY I disabled it and enabled SDDM, it showed the COSMIC session but launching that also just flickered.

I am currently rebasing to -base to see if this might be VM related.

using cosmic-silverblue:40 image

when trying to install a flatpak app, this error appears:

Failed to install APPNAME:
org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable

Not sure if this is an issue that can be solved in this image

This may be an issue specific to this image, as it is mixed with GNOME. Does COSMIC have a working portal for pipewire?

pop-os/cosmic-epoch#242

I dont know what is going on but this product has kinda unstable updates.

Used signed cosmic-silverblue:40-amd64 and an update did nearly nothing.

A rebase to the same signed release gave

error: Preparing import: Fetching manifest: containers-policy.json specifies a default of `insecureAcceptAnything` ; refusing usage

The rebase to unsigned (still same image) now worked and I get tons of updates that match the COPR build 11h ago.

Do you know what happened here?

Description

I tried both cosmic base image and cosmic-silverblue images in Virtual Machine Manager and both have a flickering problem when trying to start the cosmic-greeter service. This is a known issue, but I wanted to document it here in case others try to use our images in a VM.