When using latest stable fbpager (0.1.4) with latest unstable fluxbox (1.0.0): fbpager always starts in the wrong layer (Dock) and is hence visible above other apps when it should be underneath in the Desktop layer. For example, when maximising firefox, fbpager is still visible on top. Adding an fbpager [Layer] {12} entry to .fluxbox/apps does not solve this problem. Reproducible: Always Steps to Reproduce: 1. start fluxbox-1.0.0 with fbpager in the startup script. 2. start a desktop app, e.g. firefox, and maximise it. 3. fbpager still drawn on top. Actual Results: fbpager statrs in Dock layer Expected Results: fbpager starts in Desktop layer Henrik doesn't seem too keen to do further work on fbpager: thus might be considered for removal from portage. Should recommmend x11-misc/netwmpager as a slot-in replacement for all users: it's light, active, and works fine. Comes with glowing reviews from Sylvain Fourmanoit, adesklets author, as the reason for never writing a pager desklet.
Fbpager not working with fluxbox 1.0.0 here either. Another substitute for fbpager is ipager, which is looking for a maintainer at Bug #173562. I had trouble getting all windows to show up on netwmpager, but ipager works beautifully.
Henrik has fixed this in the fluxbox SVN. A satisfactory workaround for now is to start fbpager in the fluxbox slit, by using the -w (withdrawn) option. It's behaviour is then controlled by the slit, which works fine. I also had the same problem with netwmpager, which is a shame because this pager is very well spoken of on other platforms.
