MX-21 fluxbox beta 2 feedback thread

[siamhie]

Did you install mx-fluxbox? And then you need to run MX Flux from the menu to get it set up in your home folder.

Didn't have to do any of that. I got Thunar open via a bash shell. From there I went to /usr/bin and launched the mx-welcome file. From there I opened mx-tweak and selected reset ALL mx-fluxbox settings. After it was finished it prompted me to log out and select fluxbox at the top (already selected) and log back in. Everything is back to normal.

Just weird that it booted me to a stock setup after the installation.

[siamhie]

I did a new install of Fluxbox b2 and can't remember how we were able to stop mxfb-quickshot from creating the hidden comments folder.

[dolphin_oracle]

It doesn’t. That’s gthumb’s comments extension

[rej]

While installing Virtualbox Fluxbox B2, it encountered the following error.

[The normal updates were fine today.]

[siamhie]

It doesn’t. That’s gthumb’s comments extension

That's it. For some reason I thought it was quickshot. Thank you.

[rej]

RE: Virtualbox install error. I have Fluxbox B2 on two different partitions. The first never displayed the usual "user agreement" checkbox, yet kept going and installed it anyway, producing the error dialogue. Confirmed in Synaptic. The 2nd partition with Fluxbox B2 installed it as usual and asked for the agreement and would go no further unless checked.

[mowest]

Just weird that it booted me to a stock setup after the installation.

Actually, I think this makes sense. You had two /root partitions, but only one /home. You installed MX-KDE first. Then you installed MX-Fluxbox second. During the second install, you probably told the installer to use the same /home partition. The installer did what it is supposed to do, not write any thing into /home so that it doesn't overwrite files that you already have in your home directory. Since all of the configuration files and MX customizations for fluxbox are stored in /home the install did not write anything to the /home partition to prevent overwriting files without your permission. So when you started up MX Fluxbox, fluxbox was there, but none of the MX Fluxbox customizations were there. At least that is how I think the installer works currently when it sees that you have one of the versions of MX installed already, I don't think it distinguishes between versions of MX especially when you are asking them to share the same /home.

This brings up an interesting point. I don't know if it is possible, but it would be nice to have all of the MX Fluxbox customizations in /etc or /opt or /usr and that will be the defaults unless fluxbox finds files in /home/.fluxbox then it defaults to using those configuration files. I don't know if that is possible with fluxbox. I know that other DE's and WM's have default configuration files in the /root file system with the user being able to customize their settings through configuration files in their /home, but I imagine that such things need to be programmed into the DE or WM. I would love this if it could be done, because as MX Fluxbox continues to make configuration improvements to the default tint2, docked panel, or menu those defaults would continue to show up, but if I just wanted to change the "keys" file I could have my own custom keybindings but keep everything else default, or I could have my own custom wallpaper but keep everything else as default, since I like to leave most of the defaults in place usually only changing the wallpaper and keys file.

[siamhie]

Just weird that it booted me to a stock setup after the installation.

Actually, I think this makes sense. You had two /root partitions, but only one /home. You installed MX-KDE first. Then you installed MX-Fluxbox second. During the second install, you probably told the installer to use the same /home partition. The installer did what it is supposed to do, not write any thing into /home so that it doesn't overwrite files that you already have in your home directory. Since all of the configuration files and MX customizations for fluxbox are stored in /home the install did not write anything to the /home partition to prevent overwriting files without your permission. So when you started up MX Fluxbox, fluxbox was there, but none of the MX Fluxbox customizations were there. At least that is how I think the installer works currently when it sees that you have one of the versions of MX installed already, I don't think it distinguishes between versions of MX especially when you are asking them to share the same /home.

That's exactly the route I went. Installed KDE first (sdb4), then when I installed Fluxbox (sdb3), the partition screen listed all the partitions I had created during the KDE install, so I just selected the swap and home partitions to use which set the flag to preserve and have it format only sdb3 to use as my Fluxbox root folder. What I'm confused is about is the installer went ahead and created the .fluxbox folder but never setup anything (no dock, tint2 panel, conky). I did look around the stock Fluxbox menu and under Applications>System>Package Management, there was two entries from MX (Synaptic and MXPI). I think I may have also caught an MX entry elsewhere but it looked like a bare bones Fluxbox desktop.

I'm just wondering why the installer didn't setup everything? All the packages were installed but like I mentioned above, I was able to get it corrected without a re-install but I know my way around a stock Fluxbox setup. Not sure if someone new to Fluxbox would know what to do if that were to happen.

Since I am testing, maybe I'll re-install Fluxbox and see if I can replicate the issue (if it is one). (I have all my files I need backed up to a second hard drive)

[dolphin_oracle]

did you not get a popup when installing mx-fluxbox to run the install routine from the menu? there is a lot of stuff in there that lives in the home folder and we don't let packages touch home folders directly.

[siamhie]

did you not get a popup when installing mx-fluxbox to run the install routine from the menu? there is a lot of stuff in there that lives in the home folder and we don't let packages touch home folders directly.

No I didn't. The install of Fluxbox went like it did the first time I installed back on Sep 5th by itself. As soon as it was finished installing the OS, the installer says it will reboot after I click finish (or close-can't remember) at the bottom. When I booted into Fluxbox, that's the desktop I got. The first time I installed beta 2, I had the normal desktop with the dock, tint2 panel and conky.

Has the ISO on the web site been updated since the 5th of Sep? (that's the ISO I'm working with)