Bug 1476225 - XFCE screen flickering after upgrading to F26, use_compositing was set to false
Summary: XFCE screen flickering after upgrading to F26, use_compositing was set to false
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfwm4
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-28 10:44 UTC by Kai Engert (:kaie) (inactive account)
Modified: 2018-05-29 11:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:57:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kai Engert (:kaie) (inactive account) 2017-07-28 10:44:18 UTC
After upgrading from f25 to f26, my display showed flickering, when opening new windows, when opening some popup menus, when playing videos.

Thanks to [Enrico] from #fedora IRC channel who informed me about the need to use a compositor to avoid flickering.

I found a howto page that explained how to control the use of compositing with xfwm4.

On my system the following command returned false:
  xfconf-query -c xfwm4 -p /general/use_compositing

I ran this:
  xfconf-query -c xfwm4 -p /general/use_compositing -s true

And the flickering seems gone.

I suspect that my local configuration files, which were automatically created when I installed a past version of Fedora a while ago, had set this preference to false.

I guess that many people might run into a situation like this when upgrading.

In the past I never knowingly made a configuration to request for compositing to be set to false.

Maybe there should be a smarter way of setting default configurations, when defaults needs to change.

Comment 1 Kevin Fenzi 2017-07-28 23:14:04 UTC
compositing is off by default because some hardware doesnt support it. 

However anything at all new does, so we could look at changing the default. That would likely be a discussion for the fedora-xfce list. 

I'm not sure there's much we could do for defaults. Many of them stay the same and we don't want to remove a users choices.

Comment 2 Fedora End Of Life 2018-05-03 08:32:44 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 '26'.

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 26 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 3 Fedora End Of Life 2018-05-29 11:57:28 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.


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