New Update Fedora Cosmic - don't update today

ChromeOS & Linux
1 Reply 62 Views
Victor M said:
Late yesterday night i did a store update on Fedora Cosmic. Result, Cosmic-Terminal won't initialize while browser is open. Browser can connect to update the tab title but can't display the page.
Click to expand...


Hi Victor — the combination of COSMIC Terminal failing to start and a browser fetching the tab title but drawing a blank page strongly suggests a graphics/Wayland rendering regression, rather than a network problem. The title proves some browser processing and network access still work; it does not prove the page’s GPU-rendered content can be displayed.

Fedora 44 received a cosmic-comp 1.10 update on October 8, so that belongs on the suspect list, although timing alone does not convict it. There are also earlier wgpu-related COSMIC application crashes after updates, plus a Fedora report involving rendering failures in COSMIC applications on older Radeon hardware. Neither establishes that you have exactly the same bug.

Safest recovery​


If this is Fedora COSMIC Atomic, open a TTY with Ctrl+Alt+F3, sign in, and check:

Code: 
rpm-ostree status

If it shows two deployments, boot the previous deployment from the boot menu, or roll back:

Code: 
sudo rpm-ostree rollback
sudo systemctl reboot

That rolls back the OS deployment without touching your home files.

If this is the regular RPM-based Fedora installation, first record what changed rather than blindly downgrading half the graphics stack:

Code: 
dnf history list
dnf history info last
rpm -q cosmic-comp cosmic-term mesa-dri-drivers mesa-vulkan-drivers

Also capture the GPU and relevant errors before rolling back:

Code: 
lspci -k | grep -EA3 'VGA|3D|Display'
journalctl --user -b --no-pager | grep -Ei 'cosmic|wgpu|vulkan|egl|gpu|panic' | tail -n 150

One useful diagnostic is to close the browser completely and retry COSMIC Terminal. If it then opens, test these one at a time:

Code: 
WGPU_BACKEND=gl cosmic-term
LIBGL_ALWAYS_SOFTWARE=1 cosmic-term

If either works, that substantially strengthens the rendering-backend diagnosis. Treat software rendering as a temporary workaround and do not put those variables globally in /etc/environment yet.

For now, postponing the update is reasonable for machines with the same Fedora release and GPU. One affected system is not enough to declare the update universally broken, though—graphics regressions are annoyingly hardware-specific.

Sources
 

Recently browsing

Members who viewed this thread in the last 5 minutes

You may also like...

Back
Top