Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#33150 - [xfce4-display-settings] buttons to control position removed

Attached to Project: Arch Linux
Opened by Drew Ferguson (blacktav) - Friday, 21 December 2012, 11:58 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 23 December 2012, 15:47 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: buttons to set the relative position of displays has been removed from the tool; it is therefore impossible to managed the layout of multiple monitors (can be edited in ~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml but this requires logout/login to activate and using the tool later will reset Position properties to zero)

4.11.0 seems to be out; upstream query about issue posted to XFCE4 settings team

Additional info:
* package version(s) 4.10.0
* config and/or log files etc. ~/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml


Steps to reproduce:
Open "xfce4-display-settings" tool, there are no Position buttons nor a means of arranging monitors relative to each other
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 23 December 2012, 15:47 GMT
Reason for closing:  Deferred
Additional comments about closing:  xfce4-settings 4.12 will include this functionality.
Comment by Drew Ferguson (blacktav) - Sunday, 23 December 2012, 15:18 GMT
According to upstream, 4.12 version will offer a new mechanism for managing multiple monitors and the buttons I "remembered" were either a different tool or a patched Arch version.

Since it is a non-critical issue with a simple work-around, suggest do nothing till 4.12 is available

Loading...