ublue-os / cosmic Goto Github PK

View Code? Open in Web Editor NEW

145.0 11.0 12.0 1.87 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 Introduction

Fedora Atomic Cosmic

Fedora Atomic Desktop with the COSMIC Desktop Environment included.

Note

These images are not associated with System76! If you have issues, please understand they might be COSMIC related, OR they might be related to this image. The COSMIC Desktop Environment is still ALPHA. Do not daily drive this image on your main workstation unless you know what you're doing.

Like Fedora? Want to try the latest from the work in progress Cosmic Desktop Environment? Want to help find bugs and/or contribute to COSMIC development, but don't want to work in a VM or install Pop!_OS? None of the above things but something else??!?

Go ahead and try one of the images @ryanabx and the Universal Blue project have created!

About

This project aims to provide a base Fedora Atomic image with the COSMIC Desktop Environment included. This should be treated just like any other base image provided by Universal Blue, and it is expected that you use this image to build your own custom image to meet your specific requirements.

Scope

The base COSMIC image is intended to be a starting point for users to build their own custom images. Therefore, the image is kept as minimal as possible, with only the COSMIC Desktop Environment and a few other essential packages included. This is to ensure that the image is as flexible and unopinionated as possible.

What's Included

Essential tweaks and packages provided by ublue-os/main
COSMIC Desktop Environment
(ISO) Pre-installed Flatpaks

Installation

Download an ISO from the latest GitHub Actions build artifacts

Variants

cosmic: Only the COSMIC Desktop
cosmic-silverblue: Fedora Silverblue (GNOME) with the COSMIC Desktop
cosmic-kinoite: Fedora Kinoite (KDE) with the COSMIC Desktop

We include multiple desktop environments in some of the variants as COSMIC is still early in development, and there may be occasions where you need to switch to a different desktop environment to get work done. These will be removed as COSMIC matures.

Each variant has an nvidia version that includes the proprietary NVIDIA drivers.

Secure Boot

Secure Boot is supported by default on our systems, providing an additional layer of security. After the first installation, you will be prompted to enroll the secure boot key in the BIOS.

Enter the password universalblue when prompted to enroll our key.

If this step is not completed during the initial setup, you can manually enroll the key by running the following command in the terminal:

ujust enroll-secure-boot-key

Secure boot is supported with our custom key. The pub key can be found in the root of the akmods repository here. If you'd like to enroll this key prior to installation or rebase, download the key and run the following:

sudo mokutil --timeout -1
sudo mokutil --import public_key.der

Issues

For issues with the images, feel free to submit an issue on this repo. For COSMIC related issues, please see cosmic-epoch/issues.

cosmic's People

Contributors

Stargazers

Watchers

Forkers

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

cosmic's Issues

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.

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

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

Setup Flathub user remote

Installing applications from the App Store requires a user-scoped Flatpak remote otherwise it tries to use packagekit and fails.
The App Store doesn't appear to support installing system packages at all.

This also resolves #41, since Steam and Lutris (the only two apps where Packagekit is preferred) will fallback to Flatpak seamlessly.

prefer base os no flatpaks,,,,

not sure i agree with the latest change to force flatpaks on people, i dont use them, cant use them not allowed to use them, therefor no i must fork and maintain my own copy... great job... until you added flatpaks :) users should build custom images from your base, not have to rip out a pile of things that are not needed.

Install default Flatpak apps

PopOS!_'s install comes with some applications pre-installed. I think we should try to match the default application lists as much as possible, but obviously manage these apps as Flatpaks.

These default apps would be good as system flatpaks, rather than user flatpaks

These apps include:

COSMIC App Store is built with PackageKit support

COSMIC App Store is built with PackageKit support, but rpm-ostree doesn't support PackageKit, which means a lot of apps will show a "System" option, and when you try to install using it, it will fail.

Maybe there is some way to rebuild the store without the PackageKit feature on from this repo?

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:~$

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?

Can not start cosmic DE in cosmic base and cosmic-silverblue images

I just installed fedora silverblue 40, then ran the first command in the readme here to rebase to the cosmic-silverblue image.
I get this error on boot:

2024-07-26T22:54:08.288042Z ERROR cosmic_comp::config: Failed to read config 'workspaces': NoConfigDirectory
2024-07-26T22:54:08.288136Z ERROR cosmic_settings_config: Failed to read local shortcuts config "system_actions": NoConfigDirectory
2024-07-26T22:54:08.288213Z WARN cosmic_settings_config::shortcuts::ram: Key-binding {"Comma"} only matched case insensitive for "comma"
2024-07-26T22:54:08.288229Z WARN cosmic_settings_config::shortcuts::ram: Key-binding {"Comma"} only matched case insensitive for "comma"
2024-07-26T22:54:08.288245Z WARN cosmic_settings_config::shortcuts::ram: Key-binding {"Period"} only matched case insensitive for "period"
2024-07-26T22:54:08.288260Z WARN cosmic_settings_config::shortcuts::ram: Key-binding {"Comma"} only matched case insensitive for "comma"
2024-07-26T22:54:08.288275Z ERROR cosmic_settings_config::shortcuts: Failed to become owner of name "org.cosmic.ConfigDaemon": Unable to acquire bus name: { "name": "org.cosmic.ConfigDaemon", "error": NotFound, message: "No such file or directory" }}
2024-07-26T22:54:08.380925Z WARN [libgbm|backend/egl/context]: Ignoring requested context priority, EGL_IMG_context_priority not supported priority=High
2024-07-26T22:54:08.380973Z WARN [libgbm|backend/egl/context]: Ignoring requested context priority, EGL_IMG_context_priority not supported priority=High
2024-07-26T22:54:08.384149Z WARN [libgbm|backend/egl/context]: Ignoring requested context priority, EGL_IMG_context_priority not supported priority=High
2024-07-26T22:54:08.397825Z WARN [libgbm|backend/egl/context]: Ignoring requested context priority, EGL_IMG_context_priority not supported priority=High
2024-07-26T22:54:08.415073Z WARN cosmic_comp::wayland::compositor: Preferred format ARGB not available: NoSupportedPixelFormat
2024-07-26T22:54:08.415132Z WARN cosmic_comp::wayland::compositor: Preferred format ARGB not available: NoSupportedPixelFormat
2024-07-26T22:54:08.529562Z ERROR panic: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error::NoDevices(DrNode { dev: 57984, ty: Render })': src/backend/kms/surface/mod.rs:313
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: <unknown>
12: <unknown>
13: <unknown>
14: <unknown>
15: __libc_start_call_main
16: __libc_start_main_impl
17: <unknown>

2024-07-26T22:54:08.529552Z ERROR panic: thread 'surface-Virtual-1' panicked at 'called `Result::unwrap()` on an `Err` value: PoisonError { .. }': /buildir/build/BUILD/cosmic-comp-f44e46fa4493dcacbf656a6cfeb5dbe7dced55c5/vendor/smithay/src/desktop/space/mod.rs:69
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: <unknown>
12: <unknown>
13: <unknown>
14: <unknown>
15: <unknown>
16: start_thread
17: __clone3

Anyone faced this before? Is there a way for me to install it and run?

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

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

Image does not work in a VM

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.

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?

Build and upload ISOs to GHA Job Artifacts

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

Include ublue-os/config

These images are missing out on ujust commands, container policy, etc :)

Remove SELinux disabling instructions

I heard COSMIC works with SELinux enabled now? I would remove the warning then.

Maybe some way for users to enable it back, if they used it before?

Like a yafti page?

A Github security warning could also be used, to "warn" users to re-enable SELinux.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

chore(deps): update hhd-dev/rechunk action to v0.8.6
chore(deps): update sigstore/cosign-installer action to v3.6.0
🔐 Create all pending approval PRs at once 🔐

Detected dependencies

dockerfile

Containerfile

github-actions

.github/workflows/build.yml

ublue-os/remove-unwanted-software v7

actions/checkout v4

docker/metadata-action v5

hhd-dev/rechunk v0.8.1

ASzc/change-string-case-action v6

docker/login-action v3

redhat-actions/push-to-registry v2

sigstore/cosign-installer v3.5.0

ubuntu 24.04

.github/workflows/build_iso.yml

actions/checkout v4

jasonn3/build-container-installer v1.2.2

actions/upload-artifact v4

ubuntu 22.04

Check this box to trigger a request for Renovate to run again on this repository

[Feature Request] Add PPD to COSMIC core image

Now this image does not include either system76-power or power-profile-daemon, once installed with rpm-ostree it just works (tested with ppd). It may be good to include ppd for now and perhaps a system76 image later with system76-power?

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

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.

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 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

All keyboard shortcuts are labled "Disabled".

All shortcuts in the settings are labeled "Disabled". Shortcuts still work as normal and can be rebound. This is not an issue on Pop!_OS 24.04 alpha so just wanted to bring attention to it.

COSMIC Files shows an error when deleting files

Using the latest cosmic-base:40-amd64

Error (had to type it manually since I can't copy it):

Delete {
  paths: [
    "/var/home/user/test",
  ],
}
Error during a `trash` operation: FileSystem { path: "/var/
home/.Trash-1000", source: Os { code: 13, kind: PermissionDenied,
message: "Permission denied" } }

I'm not sure if I should report to the upstream COSMIC Files repo, trash-rs or keep it here.