MX Linux Forum

dolphin_oracle wrote: Sat Aug 21, 2021 8:05 pm @Melber can you try your system live just removing the splasht parameter?

@dolphin_oracle
Live USB, boot with quiet nosplash. Correct 1920x1200 screen resolution. CPU correctly identified. Shutdown and restart work without hanging.

Out of curiosity, I tried quiet splasht nosplash again afterwards. Strangely this time the laptop booted with correct screen resolution. Previous attempts always resulted in 1280x1024. Perhaps the successful boots with ro no quiet and/or quiet nosplash set some variable or configuration file? Shutdown still hung and didn't complete.

hello dolphin_oracle
Tint2 default on using two display screens
tint2 taskbar on each, only one has systray,
show taskbar icons separate [several] each screen.
Is Amazing.
Good first impression on two monitors.

systray can only be on one tint2rc

proves directly that it is pretty smart.

ceeslans wrote: Sun Aug 22, 2021 3:24 pm The problem with Conky reporting oversized-memory values only started occurring with conky version 1.11.6 ( --> which is exactly the version that ships with Debian bullseye and MX-Linux).
Meanwhile this has been corrected in conky version 1.12.2. However, this build has only reached Arch, Gentoo and Fedora repositories - but not Debian or any of its derivatives (afaik).
There are some workarounds (see Bunsenlabs forum post https://forums.bunsenlabs.org/viewtopic ... 88#p111888 back in March this year), or you could downgrade to the buster version 1.10.8, which also works perfectly in bullseye. But surely it is better to wait for the corrected version 1.12.2 to hit the MX (test?)repo.

Just tried conky 1.12.2 AppImage release, which comes with a ${legacymem} to show the "old" $mem, as mentioned by Mr. brndnmtthws here https://github.com/brndnmtthws/conky/is ... -826114532

Some of the Fluxbox tiling keys conflict with Thunar view keys.
For example Ctrl+3 in Thunar is supposed to change to compact view but Fluxbox tiles the window to the top of the screen.

Users should be made aware of the importance of the key file and what they can do with it.
Motivate a little :-)

My key file, for example, has hardly any similarities with the original file.
I don't think you can cover every single case. In PCManFM ctrl1 to ctrl4 are used to switch the folder view. The function keys are almost all commented out in my case, because otherwise some function keys won't work in applications and so on.

In Fluxbox the keyboard codes can be chained, so I put another ctrl C in front of ctrl[number] of the tiling function (I can remember ctrl C as "control command").
just a few more examples, I use it to call submenus from the root menu, or some stuff that was on the function keys before
ctrl c ctrl s :CustomMenu ~/.fluxbox/submenus/sidebar1
ctrl c ctrl f :CustomMenu ~/.fluxbox/submenus/favorites
ctrl c ctrl o :CustomMenu ~/.fluxbox/submenus/locations
ctrl c ctrl h : CustomMenu ~/.fluxbox/submenus/helpfiles
up to
Control c Control x :exec sudo poweroff

Doesn't have to make sense to others, but makes my daily work a lot easier. Others may have other ideas and solutions.
-------
A good documentation in the key file what is behind what would not be bad. A small start has been made, but for the beginner there are still some things missing:
############
#Mod1=Alt key
#Mod4=Left logo key
#Menu=Right logo key
#Mouse1=Left click
#Mouse3=Right click
##########
what about Mouse2, Mouse4 and Mouse5. Used that yes, why not explained. (rhetorical question, I read it all together in the original documentation when I switched to Fluxbox).
Either everything or nothing, otherwise a beginner is only confused ;-}

BV206 wrote: Sun Aug 22, 2021 9:06 pm Some of the Fluxbox tiling keys conflict with Thunar view keys.
For example Ctrl+3 in Thunar is supposed to change to compact view but Fluxbox tiles the window to the top of the screen.

Thanks. It is inevitable that any set of commands we create may conflict with one app or another's special keys. For that reason, there are actually 3 different tiling methods spelled out in the keys file:
-- Control + number keys
--Alt/Alt-LogoKey + arrow keys
--Alt and numpad keys (NumLock off or on)

A good documentation in the key file what is behind what would not be bad. A small start has been made, but for the beginner there are still some things missing:
############
#Mod1=Alt key
#Mod4=Left logo key
#Menu=Right logo key
#Mouse1=Left click
#Mouse3=Right click
##########
what about Mouse2, Mouse4 and Mouse5. Used that yes, why not explained. (rhetorical question, I read it all together in the original documentation when I switched to Fluxbox).
Either everything or nothing, otherwise a beginner is only confused ;-}

The intent was to list out the most common, but it could easily be expanded. We now have a revision of the keys file on our beta to-do list, thanks.

Just noticed that MX21 is running fluxbox-1.3.5, whereas in MX19 we were (or at least I was...) running fluxbox-1.3.7.
Is there any reason why MXFluxbox is sticking to fluxbox-1.3.5 , instead of upgrading to the 1.3.7-1-antix1 version