Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1725196

Summary: xfce4-display-settings not showing buttons
Product: [Fedora] Fedora Reporter: Jeremy Harris <jeharris>
Component: xfce4-settingsAssignee: Kevin Fenzi <kevin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 30CC: kevin, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-28 21:35:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
window with non-displayed gadgets none

Description Jeremy Harris 2019-06-28 16:10:52 UTC
Created attachment 1585694 [details]
window with non-displayed gadgets

Description of problem:

 xfce4-display-settings is not rendering many of its items.  Generally buttons
are missing until they are moused-over; also the secondary screen gadget
disappears when clicked-on to drag to a different placement (and does not
reappear).  The adjustment _does_ take effect, once the Apply button is found.

Version-Release number of selected component (if applicable):
  xfce4-settings-4.13.6-1.fc30.x86_64

How reproducible:
 100%

Steps to Reproduce:
1. run the "Display" option in the menu under Settings
2.
3.

Actual results:
 No visible gadgets, have to operate by memory and guesswork

Expected results:
 Traditional ease of use

Additional info:
  Screeenshot attached

Comment 1 Kevin Fenzi 2019-06-28 21:35:38 UTC

*** This bug has been marked as a duplicate of bug 1722588 ***