the chrome-argument addresses the problem completely: you have a window completely covering all of the available space. any event on any poin there is handled by the app covering that area. let it be chrome, nautilus or wine (which creates a "virtual desktop" and thus spanning the whole area): the app covering that area receives the events. if you as the user spawn apps which spawn the whole area: what can fluxbox do about it? maximize a regular xterm, put it onto the bottom-layer and the same effect you have with nautilus happens: your clicks are handled by xterm, not fluxbox. if you want to fluxbox' root-menu to popup anywhere you click: bind the RootMenu action to whatever key-mouse-combo you like the most which is not handled by any app that might run at the position you trigger the event.
if you "quit nautilus" and still have nautilus running and covering that area you have not quitted it correctly or completely, it's just that easy. and thus your counter-argument against the chrome-argument is just that: incomplete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/69938 Title: Fluxbox background disappears on certain events To manage notifications about this bug go to: https://bugs.launchpad.net/fluxbox/+bug/69938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
