ublue-os / cosmic Goto Github PK

View Code? Open in Web Editor NEW

134.0 9.0 10.0 1.86 MB

A Fedora Atomic based OSTree Image with the COSMIC desktop environment. Thanks to Drakulix for initial image.

Home Page: https://github.com/pop-os/cosmic-epoch

License: Apache License 2.0

Dockerfile 100.00%

cosmic desktop fedora linux ostree cosmic-epoch

cosmic's People

Contributors

Stargazers

Watchers

Forkers

boredsquirrel ryanabx m2giles nerds-run castrojo w3ss pauldgillis qeu-b-458 sungsphinx

cosmic's Issues

Hickups with updates

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?

Build and upload ISOs to GHA Job Artifacts

Could not find group 'akmods' in group file

I'm using cosmic-base. If I try to install nvidia drivers I'm having this problem:

sudo rpm-ostree install kmod-nvidia xorg-x11-drv-nvidia
[sudo] senha para thiago: 
Checking out tree c57504d... done
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:ryanabx:cosmic-epoch copr:copr.fedorainfracloud.org:ublue-os:akmods fedora-cisco-openh264 updates fedora rpmfusion-free-updates-testing rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates-testing rpmfusion-nonfree-updates rpmfusion-nonfree copr:copr.fedorainfracloud.org:phracek:PyCharm rpmfusion-nonfree-nvidia-driver google-chrome rpmfusion-nonfree-steam updates-archive
Importing rpm-md... done
rpm-md repo 'copr:copr.fedorainfracloud.org:ryanabx:cosmic-epoch' (cached); generated: 2024-06-07T09:46:09Z solvables: 882
rpm-md repo 'copr:copr.fedorainfracloud.org:ublue-os:akmods' (cached); generated: 2024-05-29T03:46:46Z solvables: 176
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2024-03-12T11:45:42Z solvables: 3
rpm-md repo 'updates' (cached); generated: 2024-06-08T05:17:25Z solvables: 17099
rpm-md repo 'fedora' (cached); generated: 2024-04-14T18:51:11Z solvables: 74881
rpm-md repo 'rpmfusion-free-updates-testing' (cached); generated: 2024-06-07T11:51:16Z solvables: 56
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2024-06-07T11:49:49Z solvables: 119
rpm-md repo 'rpmfusion-free' (cached); generated: 2024-04-20T12:11:51Z solvables: 422
rpm-md repo 'rpmfusion-nonfree-updates-testing' (cached); generated: 2024-06-07T12:13:08Z solvables: 33
rpm-md repo 'rpmfusion-nonfree-updates' (cached); generated: 2024-06-07T12:11:04Z solvables: 61
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2024-04-20T12:18:23Z solvables: 194
rpm-md repo 'copr:copr.fedorainfracloud.org:phracek:PyCharm' (cached); generated: 2024-03-18T11:54:41Z solvables: 14
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2024-06-07T11:18:32Z solvables: 29
rpm-md repo 'google-chrome' (cached); generated: 2024-06-05T19:42:28Z solvables: 3
rpm-md repo 'rpmfusion-nonfree-steam' (cached); generated: 2024-06-07T11:40:38Z solvables: 2
rpm-md repo 'updates-archive' (cached); generated: 2024-05-22T01:41:39Z solvables: 13161
Resolving dependencies... done
Will download: 1 package (11,4 kB)
Downloading from 'rpmfusion-nonfree-updates'... done
Importing packages... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
error: While applying overrides for pkg akmods: Could not find group 'akmods' in group file

akmods is listed in /etc/group.

cosmic session doesn't start after login

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

thinkpad e450

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.

cosmic-kinoite: greeter and session just flickering, not starting

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.

cosmic-silverblue: GNOME Wayland not launching

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

insecureAcceptAnything

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

Developer Edition

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

Importer: Failed to invoke skopeo proxy

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

Cosmic-screenshot panick

Screenshot tool does not work on cosmic-base (looks like the same issue of cosmic-greeter).

makaba@fedora:~$ sudo setenforce 0 && getenforce
setenforce: SELinux is disabled
makaba@fedora:~$ cosmic-screenshot --interactive=false --modal=false
thread 'main' panicked at src/main.rs:69:10:
failed to send screenshot request: Zbus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.UnknownMethod")))), Some("No such interface “org.freedesktop.portal.Screenshot” on object at path /org/freedesktop/portal/desktop"), Msg { type: Error, sender: UniqueName(Str(Borrowed(":1.26"))), reply-serial: 17, body: Signature("s") }))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
makaba@fedora:~$ cosmic-screenshot
thread 'main' panicked at src/main.rs:69:10:
failed to send screenshot request: Zbus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.UnknownMethod")))), Some("No such interface “org.freedesktop.portal.Screenshot” on object at path /org/freedesktop/portal/desktop"), Msg { type: Error, sender: UniqueName(Str(Borrowed(":1.26"))), reply-serial: 17, body: Signature("s") }))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
makaba@fedora:~$

rpm-ostree low storage space issue

~ ❯❯❯ sudo ostree admin undeploy 1
bootfs is sufficient for calculated new size: 0 Bytes
Transaction complete; bootconfig swap: yes; bootversion: boot.1.1, deployment count change: -1
Freed objects: 228,7 MB
Deleted deployment 60dc43a804aae14fe806a74bc80af143c103fda8c1f4b5dace9e96930d7c286d.0

~ ❯❯❯ rpm-ostree update
note: automatic updates (stage) are enabled
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/cosmic-kinoite:40-amd64
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/cosmic-kinoite:40-amd64 (digest: sha256:8ee04fab87ac4599375d65ccdf8fe587f3361a05f9c41de56df54213dfd45f15)
ostree chunk layers already present: 17
ostree chunk layers needed: 48 (2,4 GB)
custom layers needed: 2 (576,7 MB)
Fetching ostree chunk sha256:58f61b85c3cd (112,4 MB)... done
error: Importing: Unencapsulating base: Layer sha256:58f61b85c3cd569230335106b90cfcc41904024dd540aa0979bd0acccc91a52d: Importing objects: Importing object 08/971f563d00a7e1bea29b7ab987444517b7332b67d137298dde9c0e69875096.file: Processing content object 08971f563d00a7e1bea29b7ab987444517b7332b67d137298dde9c0e69875096: Importing regfile small: Writing content object: min-free-space-percent '3%' would be exceeded, at least 20,5 KB requested

~ ❯❯❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/cosmic-kinoite:40-amd64
                   Digest: sha256:4874fb3e1b8f74b10f162c56a56662ac751c55c7edc1b23bac3aef0a24f5974d
                  Version: 40.20240607.0 (2024-06-08T15:07:17Z)
          LayeredPackages: bat clipboard-manager cosmic-ext-applet-ollama eza fish nu procs ripgrep sd skim tealdeer zoxide

I use cosmic-kinoite:40, didn't update for some time.

I am getting a strange low disk space error preventing me from doing anything (updating or rebasing). Already removed the rollback deployment, must be something else.

cosmic-silverblue: No Pipewire portal appearing

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

Login from cosmic-greeter causes panick

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

Appstore Flatpak install: DBus error

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

Will there now be cosmic-nvidia?

Due to the recent announcement that Nvidia 555 drivers will be in the next image for some you ubue projects, Will we see Nvidia versions of cosmic?