Created attachment 1758260 [details] demonstration of bilateral filter (right on image) Description of problem: Faulty AIGLX symbolic link could be reason why full acceleration isn't available. This manifests itself in strange input lag and weird looking images like bilateral filter is on. How reproducible: Always! :) Steps to Reproduce: 1. Start Fedora and try to use something, like Firefox or Chromium browser. 2. 3. Expected results: No input lag and images don't look as if they have gone through bilateral filter. Additional info: old duplicate of this bug - https://bugzilla.redhat.com/show_bug.cgi?id=1674486
Created attachment 1758262 [details] magic of string "aiglx" could hint at faulty AIGLX symbolic link And here is even stranger find: how do you get when full AIGLX acceleration without input lag and without weird looking images like something is using bilateral filter? 1) you replace any url in browser with string "aiglx" 2) you create folder "aiglx" in home directory ls -1 aiglx Desktop Documents Downloads Pictures 3) you rename all workspace to "aiglx" (it's possible you get even more speed if you increase number of workspaces over 10)
I think it's best if you delete bug 1674486 as I originally thought something tries to enter TAB key secretly ... not that images are behind bilateral filter.
@ https://bugzilla.redhat.com/show_bug.cgi?id=1931068#c3 \ + url For example: \ + https://bugzilla.redhat.com > \https://bugzilla.redhat.com \ + https://www.google.com > \https://www.google.com This entirely removes fake motion blur effect. :)
Created attachment 1758501 [details] \ + url Remove fake motion blur demonstration. (\ + url) :)
@ https://bugzilla.redhat.com/show_bug.cgi?id=1931068#c6 Two scenarios: blank url > \"\blank\" url > \ + url This fixes input lag and removes undesired fake motion blur effect. :)
@ https://bugzilla.redhat.com/show_bug.cgi?id=1931068#c7 \"\blank\" Best possible scenario. :)
@ https://bugzilla.redhat.com/show_bug.cgi?id=1931068#c9 > \"\nouveau\"\_ is even faster! :)
*** This bug has been marked as a duplicate of bug 1931061 ***