Description of problem: Laptop plus external screen, both active. External with the main panel. Four workspaces configured. On login, four spaces shown on the panel, then changes to eight (?on first window create?). Every other one is actually used; only four can be navigated among. Version-Release number of selected component (if applicable): F20, kernel 3.11.9-300.fc20.x86_64, xfwm4-4.10.1-2.fc20.x86_64 Thinkpad T530 How reproducible: 100% Steps to Reproduce: 1. Log in. 2. 3. Actual results: Eight workspaces shown Expected results: Configured number of workspaces shown Additional info: Mouseclick on one of the bogus displayed workspaces selects the one to its left. Keybinding moves between workspaces jumps over the bogus ones.
There's sadly a number of outstanding issues around multi monitor support still. ;( Would you care to file this upstream at bugzilla.xfce.org? Or would you like me to do so?
Please do (I'm too lazy to create yet another account, so if you have one...). Additional info: possibly the flip from 4 to 8 displayed is on the 1st workspace switch.
One final thing to try: does doing a: 'xfce4-panel -r' change anything?
No apparent change on doing 'xfce4-panel -r'.
Filed upstream as https://bugzilla.xfce.org/show_bug.cgi?id=10544
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Still present in f21; updating version field.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.