Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1586023 [details] Gilouche window borders as rendered by Compiz Description of problem: After update to the latest version of compiz window decorations are no longer correctly rendered. See attached screenshots. Version-Release number of selected component (if applicable): $ rpm -qa | grep compiz libcompizconfig-0.8.16-1.fc30.x86_64 compiz-plugins-main-0.8.16-1.fc30.x86_64 compiz-manager-0.7.0-8.fc30.noarch compiz-plugins-extra-0.8.16-1.fc30.x86_64 compiz-0.8.16.1-3.fc30.x86_64 compizconfig-python-0.8.16-1.fc30.x86_64 How reproducible: Installed two fresh installs (one from MATE-spin, another one from network install) and could reproduce the issue. Steps to Reproduce: 1. Update to latest version 2. Select custom window decoration 3. Enable compiz Actual results: Generic window decoration displayed Expected results: Selected window decoration should be displayed Additional info:
Created attachment 1586024 [details] Gilouche window borders as rendered by Macro
I am also seeing this problem with Fedora 29. F20 Mate + Compiz spin compiz-0.8.16.1-3.fc29.x86_64 5.1.11-200.fc29.x86_64 It occurred immediately after applying all updates on June 30th.
@Jaroslav could this be related to https://bugzilla.redhat.com/show_bug.cgi?id=1708056 a couple of months back? It seems very similar.
(In reply to lists from comment #3) > @Jaroslav could this be related to > https://bugzilla.redhat.com/show_bug.cgi?id=1708056 a couple of months back? > It seems very similar. Is compiz crashing? Does manual rebuild fix the problem? I will try mate spin, but it works for me OK on xfce. compiz-0.8.16.1-3.fc29.x86_64
(In reply to Jaroslav Škarvada from comment #4) > (In reply to lists from comment #3) > > @Jaroslav could this be related to > > https://bugzilla.redhat.com/show_bug.cgi?id=1708056 a couple of months back? > > It seems very similar. > > Is compiz crashing? Does manual rebuild fix the problem? > > I will try mate spin, but it works for me OK on xfce. > compiz-0.8.16.1-3.fc29.x86_64 No, compiz doesn't crash. It runs ok, just uses the default window decoration instead of the selected one (i'm using Arc-Dark). Switching to Marco renders the window decoration ok. F29 Mate 1.22.1 compiz-0.8.16.1-3.fc29.i686
Is this still an issue in Fedora 31? I suspect it is based on the version numbers I see on koji.
Still didn't Upgraded to 31, but I still the problem in F30, something else I can add to this issue which might help, is that when loading the "Compiz Fusion Icon" and from there changing the "Window Decorator" to GTK+ I get a fallback border, and then when I try to switch back to emerald Compiz will crash and launch a fallback windows manager. ``` $ compiz --replace compiz (wallpaper) - Info: Found 4 files compiz (wallpaper) - Info: Found 4 files Cannot register the panel shell: there is already one running. # <- selecting GTK+ from the menu Cannot register the panel shell: there is already one running. # <- selecting emerald compiz (core) - Fatal: No GLXFBConfig for depth 0 Launching fallback window manager ```
(In reply to M. Kristall from comment #6) > Is this still an issue in Fedora 31? I suspect it is based on the version > numbers I see on koji. yes
Having finally upgraded to F31, I can confirm that this is still a bug in Fedora 31 with latest updates. Does the version field need updating to reflect this?
Hi. Looking back over this ticket, I see it's been open since June 2019 across 3 different versions of Fedora. Is the Mate / Compiz spin still supported?
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Based on version numbers, this seems likely to also affect Fedora 32 and it has been confirmed on Fedora 31. I cannot change the version field.
This affects Fedora 32
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I definitely can reproduce this on Fedora 32 but I can't change anything about this bug. Is this how we fix bugs now? Automatically close it after a fixed amount of time because no one bothers to update it?
(In reply to M. Kristall from comment #15) > I definitely can reproduce this on Fedora 32 but I can't change anything > about this bug. Is this how we fix bugs now? Automatically close it after a > fixed amount of time because no one bothers to update it? Yes, you can definitely change it. Debug the problem and send the patch - this is how the open source works. Just crying will not change anything. I am full time worker and I can't fix every reported bug in packages I am maintaining/co-maintaining in my free time, especially bugs which I am unable to reproduce.
I'm hearing this a lot. I wonder how much longer Fedora is going to last under IBM.
(In reply to Jaroslav Škarvada from comment #16) > (In reply to M. Kristall from comment #15) > > I definitely can reproduce this on Fedora 32 but I can't change anything > > about this bug. > > Yes, you can definitely change it. No, I definitely cannot. It would have taken you less time to update the bug than to respond. In other words: (In reply to M. Kristall from comment #15) > Is this how we fix bugs now? Automatically close it after a > fixed amount of time because no one bothers to update it? Confirmed
(In reply to lists from comment #17) > I'm hearing this a lot. I wonder how much longer Fedora is going to last > under IBM. It has nothing to do with IBM. Fedora is community project. A lot of people (including me) are giving a lot of their free time into it.
(In reply to M. Kristall from comment #18) > (In reply to Jaroslav Škarvada from comment #16) > > (In reply to M. Kristall from comment #15) > > > I definitely can reproduce this on Fedora 32 but I can't change anything > > > about this bug. > > > > Yes, you can definitely change it. > > No, I definitely cannot. It would have taken you less time to update the bug > than to respond. In other words: > Now it's clear that you cannot contribute. > (In reply to M. Kristall from comment #15) > > Is this how we fix bugs now? Automatically close it after a > > fixed amount of time because no one bothers to update it? > > Confirmed It seems you are confusing community-supported project with commercial product. It also seems that you are confusing downstream maintainers with upstream developers.
Perhaps I should have been more clear about my terminology, but that is not entirely my fault. On the one hand, there is the bug itself, which has been confirmed to still affect Fedora 32 (and Fedora 31 before it). On the other hand, we have the bug report (this page), which is often referred to simply as a "bug", as is Bugzilla's wont. I thought you could tell that I was referring to the latter when I used terms like "change", "close", and "update", but I can see how it might have been unclear when I used the term "fix", which applies to both (and technically the report was marked "CLOSED EOL", not "fixed"). Hopefully that has been clarified now? The report was made here because the bug affects users of Fedora and as far as I know, it does not affect other distributions' users. For that matter, AFAIK, Compiz is not longer actively developed, so who exactly is upstream? To be clear, I am not bitching at you for not fixing the bug a year ago. I am bitching that the bug was incorrectly closed because no one with permission to do so updated the bug report to indicate the bug affects either Fedora 31 (confirmed six months ago) or Fedora 32 (this month), both of which are still supported. I would have happily updated the bug report it I was able to, but "I can't change anything about this bug [report]", "No, I definitely cannot." Please update the bug report and then continue trying to fit in the time to do your passion-work while also doing your money-work, because even if it doesn't always appear that way, we are very appreciative of the work that you do.
(In reply to M. Kristall from comment #21) > The report was made here because the bug affects users of Fedora and as far > as I know, it does not affect other distributions' users. For that matter, > AFAIK, Compiz is not longer actively developed, so who exactly is upstream? If you have a way to reproduce the bug, You can try to submit it to the upstream project at https://gitlab.com/compiz
(In reply to M. Kristall from comment #21) AFAIK the bugs are autoclosed for years. I think it's enough to be in the packager group to reopen/move it, but maybe I am mistaken. Feel free to raise your concerns to FESCO about it. I have no problem to move bugs myself if people ask for it, but people usually ask different way. I started maintaining compiz because I still use it and there was no other volunteer. No volunteer usually means orphaned package. I do it this way the whole time I am using Fedora and now I am maintaining/co-maintaining over 100 packages :) I became upstream for some of them. I can do lot, but not miracles - co-maintainers are welcome.
I updated to compiz-0.8.16.1-7.fc33.x86_64 (Fedora 33) today and now I have proper window decorations back. Unfortunately, other things broke: 1. Most of a title bar became the resize zone, making it very difficult to drag windows 2. Clicking on the bottom border no longer resizes 3. Resize snapping isn't working if I resize a window from the bottom using alt+rmb Also, "Grab the current window" in mate-screenshot won't capture window decorations. I'm not sure if that's new.
(In reply to M. Kristall from comment #24) > 2. Clicking on the bottom border no longer resizes > 3. Resize snapping isn't working if I resize a window from the bottom using > alt+rmb Doesn't seem to be true. Either it's intermittent or I was delusional. But the window title bar drag thing is definitely true.
compiz-0.8.16.1-5.fc31.x86_64 fixed the problem on F31 for me :-) I agree with point #1 about dragging being slightly finnicky now but I can live with that. Thanks to whoever made this happen!
Issue was fixed by those builds. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c8297fb8f2 https://bodhi.fedoraproject.org/updates/FEDORA-2020-e3099298b2 https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d55413aee https://bodhi.fedoraproject.org/updates/FEDORA-2020-8b5de13ed6 Sorry, didn't know that this report was open, in result i forgot to link bodhi updates. I guess this can be closed now. Heads up, there are new updates to test (compiz-0.8.18) build by Jaroslav. https://bodhi.fedoraproject.org/updates/FEDORA-2020-01bda21ed2 https://bodhi.fedoraproject.org/updates/FEDORA-2020-ac00e88ea6