After the last two times (one per week) I have updated my laptop running fedora cosmic atomic, only to enter my login password and be shown a black screen. I searched for this issue and couldnt find the solution. I’ve been learning more about atomic desktops but haven’t had as much time as I hope. What is the best way to debug this? Thanks!
Fedora Linux 44.20260806.0 (COSMIC Atomic)
Start by posting the output from inxi -ezxx so we can see exactly what system you have and what version of what is installed.
Will do, I’m on a slow wireless connection and rollbacked to 44.20260731.0 which ran into the same issue. I installed 44.20260806.0 and the command couldn’t be found.
The laptop is a HP DevOne (AMD Ryzen Pro 5850u - APU)
I am unsure of what service is ran after the user authenticates with the cosmic service to handle that. I don’t know which service to check logs for.
44.20260726.0 works, in place of knowing what service logs to check, I’m taking a bisect approach to see what version the issue originate from.
I’m also facing this issue on a brand new install of Cosmic Atomic. After some testing it appears that this is a regression introduced in 44.20260731.0, 44.20260730.0 is the last version that successfully launches COSMIC desktop.
Machine is a Framework Laptop 13 (AMD 7040 Series), Ryzen 7 7840U.
I am not experiencing the issue, setting this in your environment (like .bash_profile) may fix the issue:
export COSMIC_DISABLE_DIRECT_SCANOUT=y
I was using it to fix some serious artifacting issues on COSMIC (unrelated to the current AMD artifact issues with 7.1.6).
I was about to send a message mentioning that, lol. I can confirm that it fixed the login issue but ended up rolling back as the 7.1.6 kernel has issues with the display driver.
Thanks for feedback. If possible could you, when reporting the images which work, also deliver a uname -a so that users which not use the cosmic atomic desktop, have a hint, which kernel they can use as a workaround.
If possible could you, when reporting the images which work, also deliver a
uname -aso that users which not use the cosmic atomic desktop, have a hint, which kernel they can use as a workaround.
That would not have helped at all in this situation given that both of those images have the exact same kernel (7.1.5-201.fc44.x86_64) and there doesn’t seem to be any reports outside of COSMIC Atomic of this bug.
Nonetheless 40.20260804.0 is now demonstrating the bug with cosmic-greeter not launching COSMIC again despite COSMIC_DISABLE_DIRECT_SCANOUT being on after a few reboots, so I’m really not sure what’s going on anymore. Maybe it’s a bug upstream with COSMIC 1.5.0?
I confirmed this morning that 44.20260730.0 is the last release that doesn’t exhibit the bug, just as @padgriffin mentioned above. I’ll search the cosmic issue list to try to find out more information.
Ok, I agree on that.
Comming back to @anothermindbomb 's request of inxi. This is the best way to inform us your versions … I guess also for the atomic desktop? Then users as me which not use the atomic desktop yet, can help checking with the normal spin, as I do have an installation in a virtual environment.
When we do talk here about a regression, I would say it has something todo with the kernel and the default video drivers.
As mentioned inxi is the correct tooling to debug such a bug with a lot of possibilities.
Wen you want to report upstream, then they ask also for information and mostly they like something to reproduce.
Have you tried to enter into the rescue mode, in case the atomic desktop allows you to do so? Inxi is a command-line tool and can be used without a Desktop Environment. When having an inxi from working and not working state, it makes it much easier to give you clues and as mentioned above we can help to reproduce.
Inxi (as far as I can tell) is not included on the Atomic images and asking people to install it by overlaying it onto their image (and breaking the entire atomic desktop model) is not ideal. You can also just reproduce the entire system by deploying the version which makes reproduction extremely trivial.
I have the same problem, also on a Framework 13 Ryzen 7040
I installed Fedora Cosmic Atomic from the ISO today, and after rpm-ostree upgrade I got black screen on login. Moving into a TTY and sudo systemctl restart cosmic-greeter temporarily fixes it (but there are still artifacts). In the end I rolled back to previous release.
My inxi output:
mike@fedora:/var/home/mike$ inxi
CPU: 6-core AMD Ryzen 5 7640U w/ Radeon 760M Graphics (-MT MCP-)
speed/min/max: 1116/406/4972 MHz Kernel: 6.19.10-300.fc44.x86_64 x86_64 Up: 0m
Mem: 1.75/27.2 GiB (6.4%) Storage: 931.51 GiB (2.0% used) Procs: 395
Shell: Bash inxi: 3.3.41
(although I’m not sure how useful this is, this output is from the rolled-back setup).
I asked in the S76 chat but haven’t received a response from the devs yet, I will post back when/if I do.
I’ve made an issue on the cosmic-greeter repo.
You’d be better off posting inxi -ezxx - that output gives basically no insight into your configuration, software version, drivers, hardware, etc.
I want to flag that the same thing happened to me when i installed Fedora Cosmic yesterday (Not on Atomic). The same thing happened after 3 reinstalls, with the error happening after i ran my first system update with sudo dnf upgrade
I also, like other people in this thread, use an AMD system. Heres an image of my journalctl when it happened (if its helpful at all).
I’ve sinced switched to Fedora Cosmic (not Atomic, for unrelated reasons) and kept it on the previously known working version. Today I did the updates and all seems to be working fine (I can log in and get a GUI).
Output from inxi -ezxx if it still helps:
System:
Kernel: 7.1.8-200.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
Desktop: Cosmic v: N/A tk: Iced wm: Smithay X WM lm: greetd Distro: Fedora
Linux 44 (COSMIC)
Machine:
Type: Laptop System: Framework product: Laptop 13 (AMD Ryzen 7040Series)
v: A5 serial: <superuser required>
Mobo: Framework model: FRANMDCP05 v: A5 serial: <superuser required>
part-nu: FRANDRCP05 Firmware: UEFI vendor: INSYDE v: 03.20 date: 06/23/2026
Battery:
ID-1: BAT1 charge: 35.4 Wh (62.3%) condition: 56.8/60.6 Wh (93.7%)
volts: 15.52 min: 15.48 model: NVT FRANGWA serial: <filter> charging:
status: discharging cycles: 40
CPU:
Info: 6-core model: AMD Ryzen 5 7640U w/ Radeon 760M Graphics bits: 64
type: MT MCP arch: Zen 4 rev: 1 cache: L1: 384 KiB L2: 6 MiB L3: 16 MiB
Speed (MHz): avg: 1116 min/max: 406/3501 boost: enabled cores: 1: 1116
2: 1116 3: 1116 4: 1116 5: 1116 6: 1116 7: 1116 8: 1116 9: 1116 10: 1116
11: 1116 12: 1116 bogomips: 83848
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: Framework
driver: amdgpu v: kernel arch: RDNA-3 pcie: speed: 16 GT/s lanes: 16 ports:
active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7, DP-8,
Writeback-1 bus-ID: c1:00.0 chip-ID: 1002:15bf temp: 41.0 C
Device-2: Framework Laptop Webcam Module (2nd Gen) driver: uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 32ac:001c
Display: wayland server: Xwayland v: 24.1.13 compositor: cosmic-comp
driver: gpu: amdgpu display-ID: 1
Monitor-1: eDP-1 model: BOE Display NE135A1M-NY1 res: 2880x1920 dpi: 257
diag: 343mm (13.5")
API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.6 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: AMD Radeon 760M Graphics (radeonsi phoenix ACO
DRM 3.64 7.1.8-200.fc44.x86_64) device-ID: 1002:15bf
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
vendor: Framework driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: c1:00.1 chip-ID: 1002:1640
Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Framework
driver: snd_pci_ps v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: c1:00.5
chip-ID: 1022:15e2
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Framework
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: c1:00.6 chip-ID: 1022:15e3
API: ALSA v: k7.1.8-200.fc44.x86_64 status: kernel-api
Server-1: PipeWire v: 1.6.8 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 01:00.0
chip-ID: 14c3:0616
IF: wlp1s0 state: up mac: <filter>
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 bus-ID: 1-5:3 chip-ID: 0e8d:e616
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 931.51 GiB used: 74.49 GiB (8.0%)
ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P5PSSD8 size: 931.51 GiB
speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 34.9 C
Partition:
ID-1: / size: 928.91 GiB used: 73.98 GiB (8.0%) fs: btrfs dev: /dev/dm-0
mapped: luks-bc6e6087-e92b-4c3a-b35f-1179c62140e1
ID-2: /boot size: 1.9 GiB used: 497.7 MiB (25.6%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 928.91 GiB used: 73.98 GiB (8.0%) fs: btrfs
dev: /dev/dm-0 mapped: luks-bc6e6087-e92b-4c3a-b35f-1179c62140e1
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.9 C mobo: N/A gpu: amdgpu temp: 42.0 C
Fan Speeds (rpm): fan-1: 0
Info:
Memory: total: 28 GiB available: 27.2 GiB used: 3.39 GiB (12.5%)
Processes: 459 Power: uptime: 5m wakeups: 0 Init: systemd v: 259
default: graphical
Packages: 669 pm: nix-usr pkgs: 633 pm: rpm pkgs: N/A note: see --rpm
pm: flatpak pkgs: 36 Compilers: gcc: 16.1.1 Shell: fish v: 4.6.0
running-in: cosmic-term inxi: 3.3.41
I updated (atomic) and the issue remains.
Hello, I got the same problem with a brand new laptop with AMD processor and integrated graphics. Roll back to 44.20260730.0 fixed the issue.
Btw, no issue on my desktop with AMD processor (no integrated graphics) and 10y old graphics card.
I am new to the community here. Is it fair to assume this will be fixed ? I want to make it my daily driver (I enjoy cosmic very much), but this will not work if we can’t upgrade the system.
Thank you.