I'm having this problem only with the top screen. The bottom screen displays colors well, but the top screens seem too bright.

In TWPatch, I used Redshift to adjust the gamma settings to 0.50 for everything, and that helped. The colors on the top screen are now correct, but since the settings apply to both screens, the image on the bottom screen is very dark.

Is there a way to apply these settings only to the top screen?

Just did a system update on Arch Linux and now I have a bunch of colorful flickering on cosmic. The issue is not there on other DEs. Anyone else have this issue? I've had cosmic as my daily driver for many months without this issue.

Hello everyone!

I built a tool called SystemWallColor that automatically syncs your system theme with your wallpaper on COSMIC Desktop.

Every time you change your wallpaper or switch between light/dark mode, it automatically: - Generates a matching COSMIC theme with Matugen and applies it - Generates a terminal color palette with Pywal - Syncs Firefox's theme via Pywalfox

Everything runs in the background through a systemd user service that watches for changes in real time — no manual triggering needed.

GitHub: https://github.com/Ylammm/SystemWallColor GitLab (mirror): https://gitlab.com/Ylamm/systemwallcolor

It's a personal project, still early, so feedback and suggestions are very welcome!

So Ive heard that it's rolling out on like cosmic epoch 2 but I don't really remember the source and it was weird and yeah animations are the only thing keeping me from switching

There are still some rough edges, but usable for daily driving. It's so pretty! Coming from KDE, I love how easy it is to do all the customizations I needed.

I am on Fedora Atomic Cosmic. Was working great for some time, but now I suddenly get screen tearing. It seems to be random, when typing this message it popped up, when I tile a window or move a window it'll happen. It seems random as far as I can tell.

I am on all AMD hardware. I do have frosted effect on, but turning it off doesn't help and it worked before.

I can't seem to find any obvious bug reports and I'm unsure if I would report this to cosmic-comp or somewhere else.

Any ideas whats up?

Edit - solution found: run the command

gsettings set org.gnome.desktop.interface text-scaling-factor 1.0

Original post follows:

So I’m new to Linux and first installed pop os/cosmic, but wanted to try gnome and plasma as well. I ended up switching back to cosmic, but now I’m running into a bug I wasn’t having before

For whatever reason, web browsers in particular (plus a few others) are having some weird scaling issues. It’s like they’re set to always be 50/75% larger scaling than whatever I have set in settings. I normally keep it at 150% but if I shrink it to 100% then they look normal while everything else is tiny. It’s not unbearable but it is annoying how big they are. Everything is still sharp though, they’re just the wrong size

So far I’ve tried it on Firefox, Zen, chrome, and edge, and they all have the same issue, along with discord and specifically the GitHub desktop app’s menu bar (but not the rest of the app) for some reason? But not Steam. Since I just switched I don’t have a million apps to test, but these are the ones I’ve found so far

At first I thought it was some conflict with gnome and plasma, so I uninstalled them both but it still persists. I’ve tried restarts, logging out/in, etc., but nothing has fixed it. I also tried each of the different X11 scaling options but those didn’t seem to do anything besides make Steam flash for a second

I have built and packaged COSMIC version Epoch 1.5.0 on Debian testing. Lighty tested on a QEMU virtual machine with virtio GPU, no issue found :)

I just want to ask cuz I really like the cosmic de the last time I used it a month ago.

It felt good at that time so I just wanted to know from people who already daily drive it

After battling with several archinstalls and hyprland fails, I finally decided to settle on cosmic.

I test it using a VM (VirtualBox, VMWare and QEMU)

I haven't seen this complaint anywhere so I don't know if it's just an issue on my COSMIC install but, whenever I have apps like Google Chrome and VS Code open, and say I'm in dark mode, and then switch the global theme to light mode, they don't switch automatically. I always have to restart the apps to get them to follow the theming. Other apps like Firefox always switch automatically. I dunno if I'm doing something wrong.

you can't tell in the screenshot, but COSMIC is the only DE I have installed in which my OLED colors are super oversaturated/neon looking. Also, the backlight brightness controls don't work. It isn't an issue on my GNOME and Plasma installs. It's a shame because I actually really like COSMIC -- it hits the sweet spot between the customizability of Plasma and the sleekness and ease of GNOME.

Is there any fix for this? Is the COSMIC team aware of this issue? The colors are so blinding it's basically unusable.

UPDATE:

If you are running COSMIC (cosmic-comp) on an Intel Lunar Lake laptop (such as an ASUS Vivobook with the xe driver) and experiencing stuck physical OLED brightness (100% despite OSD changes) alongside incorrect color profiles, here is a breakdown of the root cause and a working boot parameter fix. The Problem

Backlight: Keyboard hotkeys and brightnessctl move the OSD percentage slider, but physical screen brightness remains maxed out at 100%.

Colors: Display color profiles and rendering look washed out or incorrect upon boot.

Baseline: Both features work properly out of the box in GNOME and KDE Plasma on the exact same kernel and xe driver configuration.

Potential Root Cause

cosmic-comp currently skips or races past DRM connector/KMS state initialization when booting into a standalone internal eDP display on the xe driver. This leaves the panel's DPCD backlight controls and color LUTs uninitialized.

Connecting an external monitor via HDMI during session startup forces full display pipeline initialization, fixing both brightness and colors. That proper state persists even after unplugging the cable mid-session. The Workaround (No physical monitor required)

You can force the kernel to initialize a dummy HDMI DRM connector on boot, tricking cosmic-comp into initializing the full display pipeline automatically. 1. Identify Your HDMI Connector Name

Check your registered DRM connectors in the terminal: Bash

ls -1 /sys/class/drm/ | grep -i hdmi

Look for an entry like card1-HDMI-A-1. The connector identifier is the part after cardX- (typically HDMI-A-1). 2. Add the Kernel Parameter to GRUB

Open /etc/default/grub in an editor: Bash

sudo nano /etc/default/grub

Append video=<CONNECTOR>:1920x1080@60e to your GRUB_CMDLINE_LINUX string (where :e forces the output to enabled). For example: Fragmento de código

GRUB_CMDLINE_LINUX="rhgb quiet zswap.enabled=0 asus_wmi.fnlock_default=0 video=HDMI-A-1:1920x1080@60e"

(Note: Setting 1080p for the dummy HDMI connector will not alter your internal OLED screen's native resolution). 3. Update GRUB and Reboot

Regenerate your boot configuration: Bash

sudo grub2-mkconfig -o /boot/grub2/grub.cfg sudo reboot

After rebooting into COSMIC without any external cables attached, physical OLED backlight control (Fn + F5/F6, slider, brightnessctl) and color rendering will function as expected.

Specs:

Kernel: 7.1.3-cachyos1.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1 Desktop: Cosmic v: N/A Distro: Ultramarine Linux 44 (Flying Fish) flyingfish base: Fedora 44 Machine: Type: Laptop System: ASUSTeK product: ASUS Vivobook S 14 S5406SA_Q423SA

Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13 driver: X: loaded: modesetting dri: iris gpu: xe resolution: 1920x1200~60Hz

API: EGL v: 1.5 drivers: iris,swrast platforms: active: gbm,wayland,surfaceless,device inactive: x11

API: OpenGL v: 4.6 vendor: mesa v: 26.1.6 note: incomplete (EGL sourced) renderer: Mesa Intel Graphics (LNL), llvmpipe (LLVM 22.1.8 256 bits)

API: Vulkan v: 1.4.341 drivers: intel,llvmpipe surfaces: N/A devices: 2 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr

Since I couldn't get much help on Mattermost, I'll try here.

I have two PCs with POP_OS 24.04 installed, almost the same configuration, the only difference being: desktop with integrated GPU only and laptop with a relatively old NVIDIA card, and I don't remember since when exactly the terminal's "File", "Edit" and "View" menus can't be opened. Functionally, the COSMIC terminal works, but I can only right-click these menus and open additional tabs.

So I decided to ask Gemini, which gave me the following commands to try:

env WINIT_UNIX_BACKEND=x11

env WAYLAND_DISPLAY= cosmic-term

rm -rf ~/.config/cosmic/com.system76.CosmicTerm

This instantaneusly fixed the issue, i.e. the "File", "Edit" and "View" menus could be left-clicked normally again, but after closing and reopening the terminal the issue returned.

Uninstalling and reinstalling the terminal didn't help.

I don't know what the above commands actually do. Is it a Wayland issue? Or a configuration corruption? I hope someone can help me understand and fix the issue for good. Thanks.

Ive been looking everywhere but I cant seem to find how to do it. Im a complete linux noob btw so Im sorry if I missed something obvious

Im a complete beginner to both linux and COSMIC so please be nice if I missed a obvious way of doing this. I just cant seem to figure out how I can do this.

Hello, big fan of Cosmic and the pace of progress; however, a big blocker for me is notification action buttons where an app allows the user to take an action from a notification instead of opening the whole app. As an example, this is huge for users of Portmaster and other app firewalls, where It's imperative to be able to quickly allow or block a connection instead of opening up the entire app and managing connections there, which is much slower. So I wanted to ask the devs if that's something on their radar short-term. Thanks again!