MX Linux Forum

That menu is generated by a script so as long as the applications themselves still are installed they will reappear wherever the menu is refreshed. Same for Appfinder.

Jerry3904 wrote: Tue Aug 31, 2021 12:42 pm That menu is generated by a script so as long as the applications themselves still are installed they will reappear wherever the menu is refreshed. Same for Appfinder.

True, if you select Update Menu. If you select Update Menu, your customized menu (any changes you've made to menu-mx and/or any of the files in the submenus folder) gets reset back to the default menu by the command /usr/bin/mxfb-menu-generator.

I still have the apps installed but they no longer appear in my menu. (any changes you make to the files mentioned above are updated right away-no need for refreshing/restarting)

Kernel 5.10.0-8-amd64 is used in the live system and in the installed system. However Debian 64 bit (4.19) is greyed, as if it was installed, according to the popular packages list of the MX package installer.
I have trouble on my HP mini 110 netbook with kernel version 5.10 (no internet), disconnecting or no wifi connections and would like to use 4.19 or 4.9. Version 4.19 however can't be downloaded and reinstalled.
The horizontal task bar is hiding part of the windows used for installation of the system on the small screen of the HP mini 110, but one can use the Alt key to shift the windows a little when required.

Because of abandoning legacy drivers by nVidia, I was forced to use compton to get rid off screen tearing. The effect is acceptable, although still a little bit worse than in MX19. No screen-tearing, rather smooth movement of windows, but there's a little strange behavior of Thunar and terminals (both Rox and XFCE). Their borders became about 50% transparent and there is a "flashlight effect" while launching and closing, like there was a white background beneath that launches a couple of milliseconds before the content of the window is painted. All the rest of apps, no matter if gtk or qt launch and close smoothly.

Because compton adds a real transparency, and there is only a pseudo-transparency in Fluxbox by default, after login the behavior of some windows and apps change. A problem appears with compton and idesk icons, because of the order of launching apps in the default startup: compton > idesk > nitrogen wallpaper (as far as I remember). So if you change the wallpaper you've got a glitch after login, idesk icons are painted on the lightdm wallpaper that still appears on the transparent part of the icons. I had to change the standard setup to get rid off this. First off all I've moved all the commands rather to the end of the startup, and changed the order to: nitrogen restore > idesk > compton and added a sleep command before those two last.

I had a problem to start the fluxbox session today. After a quick research I noticed, there was a "#" before every "$HOME" variable in the startup file. So the startup was broken. I didn't have put this sign manually. The only thing I could have done is removing dock using "Disable default dock" from menu... So check out if this command work properly to you.

Will check, thanks for the report.

First off all I've moved all the commands rather to the end of the startup, and changed the order to: nitrogen restore > idesk > compton and added a sleep command before those two last.

I've never used compton in my entire MX life, so hope someone who knows something about this can comment.

I have confirmed my suspicions. After clicking the menu entry "Disable default dock" every entry turns to in ~/.fluxbox/startup .

So you've got not only but also: or: that breaks the startup file and the Fluxbox session does not load at all.

kobaian wrote: Wed Sep 01, 2021 6:11 am I have confirmed my suspicions. After clicking the menu entry "Disable default dock" every

Code: Select all

$HOME

entry turns to

Code: Select all

#$HOME

in ~/.fluxbox/startup .

So you've got not only

Code: Select all

#$HOME/.fluxbox/scripts/DefaultDock.mxdk

but also:

Code: Select all

#$HOME/.fluxbox/scripts/conkystart

or:

Code: Select all

# mx-welcome if configured to autostart
if [ -e #$HOME/.config/autostart/mx-welcome.desktop ]; then
# launch mx-welcome
(sleep 5; /usr/bin/mx-welcome) &
fi

that breaks the startup file and the Fluxbox session does not load at all.

confirmed, good catch.

Thanks for checking again.

changed code for $HOME/.fluxbox/scripts/dfltdck_kill here: