I am using MATE/Compiz as my desktop environment. I ran `dnf update && shutdown -h now` last night. This morning compiz does not decorate my windows. When I try to restart the compositor I get an error message saying that something has been terminated, although compiz (or its main process, at least) is still running: $ compiz ccp --replace compiz (core) - Warn: No XI2 extension (gtk-window-decorator:5351): Wnck-CRITICAL **: 10:13:55.470: wnck_set_client_type: changing the client type is not supported. *** stack smashing detected ***: terminated I assume this must have been triggered by the dnf update, but I can't figure out which package is to blame. I already tried rebooting to the previous kernel, and downgrading libstdc++, because those seemed to me like the most likely suspects. No soap. I'll attach the dnf transaction log. Reproducible: Always Steps to Reproduce: Login to desktop, or try to restart compiz Actual Results: No window decorations Expected Results: Compiz should decorate windows
Created attachment 2128524 [details] dnf transaction log
Downgrading mesa-libGL didn't help either.
abrt did its thing
Aha, downgrading marco fixes the problem. It appears that marco's MetaFrameBorders struct has new members in version 1.28.2 that were not present in 1.28.0. <https://github.com/mate-desktop/marco/compare/v1.28.0...v1.28.2#diff-2b446cb0067d010f86af3114c480af171cff5fdad35e88ed7cde3d30651bb11a> Compiz should be rebuilt to pick up the increased struct size.
*** Bug 2437515 has been marked as a duplicate of this bug. ***
The Fedora 44 build of compiz, <https://koji.fedoraproject.org/koji/buildinfo?buildID=2896736>, was built against marco-libs 1.28.0, and will also crash if Fedora 44 includes marco 1.28.2. I suggest fixing this by rebuilding compiz before the beta.
compiz isn't the renderer for any blocker desktop, so I don't think this can be a blocker.
Rejected as an F44 beta blocker in https://pagure.io/fedora-qa/blocker-review/issue/2033 (In reply to Ben Slusky from comment #6) > The Fedora 44 build of compiz, > <https://koji.fedoraproject.org/koji/buildinfo?buildID=2896736>, was built > against marco-libs 1.28.0, and will also crash if Fedora 44 includes marco > 1.28.2. I suggest fixing this by rebuilding compiz before the beta. Ben, I think you misunderstood what the tracker bug is used for. You can read more about the blocker process here: https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process If you have questions or remarks, feel free to raise them ideally in the linked ticket, thanks.
Trying one more time, since one voter said they would make this bug a beta freeze exception. Just to reiterate: this issue can be fixed with a RPM release bump and rebuild of compiz, to pick up the increased struct size in marco-libs 1.28.2. If this is not done, compiz will be totally non-functional in Fedora 44.
blockerbot pls
You don't need to do that, you just need to wait. It runs every 30 minutes.
+4 in https://pagure.io/fedora-qa/blocker-review/issue/2033 , marking accepted FE.
I guess it isn't problem in f43, because I am running compiz on f43 without problem, changing release to f44.
FEDORA-2026-b9fa86bae1 (compiz-0.8.18-20.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-b9fa86bae1
FEDORA-2026-b9fa86bae1 (compiz-0.8.18-20.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-afba611afa (compiz-0.8.18-20.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-afba611afa
(In reply to Jaroslav Škarvada from comment #13) > I guess it isn't problem in f43, because I am running compiz on f43 without > problem, changing release to f44. Maybe it's because I am not running marco, that's why I am probably not affected, but there is bug 2441728. So rebuilding it also for f43.
FEDORA-2026-4dd0f84cd0 (compiz-0.8.18-20.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-4dd0f84cd0
FEDORA-2026-4dd0f84cd0 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-4dd0f84cd0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-4dd0f84cd0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-afba611afa has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-afba611afa` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-afba611afa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
On fresh installation of RC1.2, Compiz decorates just fine. Then I issued the above reproducing command `sudo dnf -y update && shutdown -h now` and started the machine again. Compiz still decorated fine, see attachment. I consider this verified.
Created attachment 2132161 [details] Compiz decorations
I can also verify the fix. With marco-libs-1.28.2-1.fc43 and compiz-0.8.18-20.fc43, gtk-window-decorator does not crash on startup.
Lukas: I don't think you reproduced this right, because the fix isn't in Beta-1.2. Beta-1.2 was built on Feb 27, long before the F44 fix was submitted. (Or else possibly you did a network install and got the fixed package from updates-testing?)
FEDORA-2026-afba611afa (compiz-0.8.18-20.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-4dd0f84cd0 (compiz-0.8.18-20.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.