Bug 1745380 - Display corruption when running compiz
Summary: Display corruption when running compiz
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-26 00:40 UTC by Matt D.
Modified: 2020-09-12 16:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 16:46:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Display corruption (1.77 MB, image/jpeg)
2019-08-26 00:40 UTC, Matt D.
no flags Details
amd_fix.sh (23 bytes, text/plain)
2019-08-26 18:05 UTC, Matt D.
no flags Details

Description Matt D. 2019-08-26 00:40:47 UTC
Created attachment 1607979 [details]
Display corruption

I am experiencing display corruption when trying to run compiz on my Ryzen 7 2700U laptop with integrated graphics.

Everything works fine with macro (MATE's default window manager). Compiz also works fine on the same machine if I boot into the Fedora 30 MATE-Compiz live image.

My current system was installed with the Fedora Server spin and MATE was later installed with groupinstall "MATE Desktop". I don't know how to troubleshoot this further.

I have tried running:
compiz --replace
compiz-manager
fusion-io

All will load up compiz but with display corruption. See attached image.

I can confirm that compiz is running and "works" (such as wobbly windows) but it's unusable due to the artifacts. This appears to be a software issue.

Comment 1 Matt D. 2019-08-26 18:03:36 UTC
After referencing this bug:

https://bugs.freedesktop.org/show_bug.cgi?id=111122

I was able to find a solution by adding "export AMD_DEBUG=nodcc" to the global profile. I've attached a  file "amd_fix.sh" which if placed in /etc/profile.d/ will provide a workaround.

Comment 2 Matt D. 2019-08-26 18:05:58 UTC
Created attachment 1608232 [details]
amd_fix.sh

Comment 3 Ben Cotton 2020-04-30 21:16:03 UTC
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.

Comment 4 Ben Cotton 2020-05-26 16:46:59 UTC
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.

Comment 5 LiuYan 2020-09-12 16:15:59 UTC
(In reply to Matt D. from comment #1)
> After referencing this bug:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=111122
> 
> I was able to find a solution by adding "export AMD_DEBUG=nodcc" to the
> global profile. I've attached a  file "amd_fix.sh" which if placed in
> /etc/profile.d/ will provide a workaround.

Thanks for this workaround. I have same issue on AMD Ryzen 5 2400G.

This bug still exists in Fedora 32. Don't know how to reopen this issue on bugzilla 5.

Also, I don't know if it's related to compiz, because when Fedora 30 released, compiz still works at that time, the version of compiz are same.


Note You need to log in before you can comment on or make changes to this bug.