1. Things are a bit different for MX-Fluxbox users because the core of this Window Manager—the actual package named “mx-fluxbox”–contains files that need to be located inside the /home directory. That means that the upgrade process can not be completed without the user’s active participation—i.e., it’s not enough to just provide the root password at the start.
2. Some applications and files from that core package are installed outside the /home directory. For example: the two “power tools” (mx-idesktool and mx-dockmaker), the artwork package (mxfb-art) and the document package (mxfb-docs). These will be completely installed when the upgrade process is initiated with root’s permission, having no need for the user’s permission.
3. The upgrade of July 1, 2020, provides a clear example. It brings a new app called “exit-options” that generates a graphic index of the various kinds of exit that a user might consider: lock screen, log out, sleep, restart and shut down. Its great advantage is that it relies on self-evident icons so that there is no need for translation. That app is installed into the system without the user being involved. But the upgrade also revises the DefaultDock to include an icon that launches that app. Since that revision would happen inside the user’s home directory (/home/.fluxbox/scripts), it can’t be installed automatically.
4. For this reason, the upgrade to the package mx-fluxbox itself requires a second permission to complete the installation. That second permission is granted when the user launches “MX Flux” from the Xfce menu using one of three methods: navigating Menu > All Apps, pressing F6, or clicking the dock icon with the MX Linux logo. (It is also possible to open a terminal and run as regular user “mxflux_install.sh”). Any of those actions will run the install script, showing a dialog box at the beginning about where the backup is located, and another at the end about the need to log out and back in. NOTE: anytime you click the “MX Flux” menu entry, the latest default setup will be restored, even if there has been no upgrade.
5. Your entire fluxbox config is backed up at the beginning of this process to /home/.restore/fluxbox. This backup gives you a couple of important options:
- You can keep the new config after testing it, but may want to copy and paste some items you want to keep from the old config (stored in /home/.restore/fluxbox) into the new one: for instance, you might want to bring back your own scripts, docks, wallpapers or config files.
- You can do the reverse: rename the new fluxbox directory to something like “fluxbox_NEW” (which will not show up in the Menu) and bring back the entire old fluxbox directory from /home/.restore. You’d have the option of copying over a few of the new items that you liked.
6. You might be saying: “I’m perfectly happy with what I have, why should I upgrade at all?” That’s a good question with a good answer: nothing forces you to carry through the upgrade. Using the July 1 upgrade as an example, not installing would mean 1) you would not know about the new Exit Options app; 2) you would not have the exit icon added to the DefaultDock; 3) you would not get the bug fix for unmuting sound. If you’re OK with that, then just do nothing.
7. Finally, this requirement for a second permission also appears when MX-Fluxbox is installed individually into an earlier version of MX Linux that did not bring it automatically.