Bug 1038556 - Changing Settings/Desktop/Saturation control changes background color in XFCE
Summary: Changing Settings/Desktop/Saturation control changes background color in XFCE
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-settings
Version: 22
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: 2013-12-05 10:41 UTC by Peter H. Jones
Modified: 2016-07-19 10:46 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 10:46:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Xfce 10531 0 None None None Never

Description Peter H. Jones 2013-12-05 10:41:22 UTC
Description of problem:
In XFCE, changing Settings/Desktop/Brightness results in changing
the background hue displayed. 

Version-Release number of selected component (if applicable):
Can't find version in Help button.

How reproducible:
Always

Steps to Reproduce:
1. Open Settings/Desktop menu
2. Change Brightness

Actual results:
Background color changes from red to cyan, passing through grey

Expected results:
Background should change brightness

Additional info:
If this problem is hardware-specific, I can provide it.

Comment 1 Peter H. Jones 2013-12-05 13:22:08 UTC
Sorry, its the Saturation slider that is producing the problem. So my title is correct.

Comment 2 Kevin Fenzi 2013-12-05 20:53:58 UTC
I can confirm this here too. ;) 

Would you like to report this upstream to bugzilla.xfce.org? Or would you like me to do so?

Comment 3 Peter H. Jones 2013-12-06 05:12:57 UTC
Glad you could confirm the bug.
I'd rather you reported it upstream, so I can avoid having to become a member of bugzilla.xfce.org and having to learn its procedure for submitting reports. I'd appreaciate a link to be able to check on progress upstream, if that's possible.

Comment 4 Kevin Fenzi 2013-12-08 17:28:07 UTC
https://bugzilla.xfce.org/show_bug.cgi?id=10531

Comment 5 Fedora End Of Life 2013-12-21 15:38:12 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 6 Kevin Fenzi 2013-12-21 15:52:27 UTC
I see this on rawhide as well...

Comment 7 Jaroslav Reznik 2015-03-03 16:57:27 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 8 Fedora End Of Life 2016-07-19 10:46:20 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.