[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Pkg-xfce-devel] Bug#656281: Multiple Workspace Switchers with multiple Panels ignores number of rows



Package: xfce4
Version: 4.6.2

When using multiple panels, each with their own workspace switcher, the 
number of rows configured on one of the switchers is not honoured after 
logout/login. For example, if you configure two workspace switchers to 
have five rows, one of them will revert to one row only after logout/login.

Steps to reproduce:
- Have or create two panels.
- For each panel:
   - Right click panel
   - Add new items
   - Workspace Switcher
   - Set number of rows to 5
   - Close
- Log out
- Log back in
- One of the switchers will have reverted to one row

Workaround: Remove erroneous switcher, add it back again. Needs to be 
repeated every logout/login.

After the above steps, with one switcher showing one row, the 
configuration will reflect that each switcher is set to use five rows:

$ pwd
~/.config/xfce4/panel

$ ls -1 pager-*
pager-13267552670.rc
pager-2.rc

$ cat pager-13267552670.rc
rows=5
scrolling=true
show-names=false

$ cat pager-2.rc
rows=5
scrolling=false
show-names=false

An interesting observation:
- Right click on switcher
- Properties
- Note that the number of rows displayed is 5, ie. it seems to think it 
is using five rows, when it is not
- Change number of rows to 4
- Close
- Nothing changes visually, although the pager configuration file now 
has "rows=4".

Notes on local environment that may impact the results:
- Xinerama, four screens, four panels (one per screen), with two panels 
having the workplace switcher. Recently migrated from GNOME.

Misc:

$ uname -a
Linux foo 2.6.32-5-686 #1 SMP Wed Jan 11 11:11:11 UTC 2012 i686 GNU/Linux

$ cat /etc/issue.net
Debian GNU/Linux 6.0

Related:

When using GNOME, I experienced the same problem (ie. secondary 
switchers keep reverting back to one row on logout/login). I do not have 
any further diagnostics on the GNOME side, but it would suggest that the 
problem itself might not be in Xfce4 itself, but perhaps in some common 
library that GNOME and Xfce4 use? Either that or it is a remarkable 
coincidence.







Reply to: