Introducing Garuda COSMIC
Hi folks, we now have a new Garuda ISO featuring the COSMIC desktop environment. It is very barebones at the moment–basically just the stock COSMIC packages on a Garuda base–but if there is community interest in this, we can certainly build it up as people chime in with their tweaks and ideas. Feel free to take it for a spin and see what you think!
Please bear in mind that COSMIC is still in an Alpha state, and COSMIC bugs should not be reported to Garuda Linux.
COSMIC is still in an Alpha state
This means that while it’s functional and ready for exploration, you will likely encounter bugs or unfinished features. It is reasonable to expect things to be broken sometimes with an Alpha release.
In general it is not recommended to use this release for a daily driver if you need to use your computer for production or work, or otherwise cannot afford to have downtime.
Please do not report COSMIC bugs to Garuda Linux
We do not develop this software in any way, nor do we anticipate COSMIC devs will be browsing the Garuda Linux forum looking for extra work to do. Please report issues related to COSMIC to the COSMIC devs so they can see what is happening, and work on adding fixes and improvements.
Here is the COSMIC GitHub issue page for reporting issues or adding feature requests:
How to contribute to Garuda COSMIC
The repo for the garuda-cosmic-settings package is here: Garuda Linux 🦅 / Themes and Settings / Settings / Garuda Cosmic Settings · GitLab. There isn’t much in there at the moment, but this is where we can add or change any default configs we want to use in the spin. When the garuda-cosmic-settings package is updated, the corresponding files in /etc/skel will be updated for the users as well.
If you are new to contributing changes to our GitLab, these notes from the repo’s README are a good place to start:
We highly appreciate contributions of any sort!
To do so, please follow these steps:
- Create a fork of this repository.
- Clone your fork locally (short git tutorial).
- Add the desired changes to PKGBUILDs or source code.
- Commit using a conventional commit message and push any changes back to your fork. This is crucial as it allows our CI to generate changelogs easily.
- The commitizen application helps with creating a fitting commit message.
- You can install it via pip as there is currently no package in Arch repos:
pip install --user -U Commitizen.- Then proceed by running
cz commitin the cloned folder.- Create a new merge request at our main repository.
- Check if any of the pipeline runs fail and apply eventual suggestions.
We will then review the changes and eventually merge them.
There is also a directory in the ISO profile repo with some few core configs and the default package list. community/cosmic · master · Garuda Linux 🦅 / Tools / iso-profiles · GitLab
If you you want to contribute your custom tweaks or ideas but creating merge requests in Git is just too far outside your wheelhouse, feel free to chime in here in the forum instead. 
Where can I download the ISO?
Use this link:
Check the dates, and grab the ISO from whichever one is the most recent. Happy tinkering! 
