MX-23 beta 1 feedback thread

[gurpreetkapoor]

On newly installed MX KDE Plasma, it includes packages installed from ahs repo, every time running update, if there are any updates in ahs repo, its too slow to perform update as i believe it compiles drivers for particular kernel version through dkms, even though i dont need most of those ahs drivers except for few, would anyone please guide me to filter out those drivers, so that i keep only those drivers which are actually needed from ahs repo??

[dolphin_oracle]

On newly installed MX KDE Plasma, it includes packages installed from ahs repo, every time running update, if there are any updates in ahs repo, its too slow to perform update as i believe it compiles drivers for particular kernel version through dkms, even though i dont need most of those ahs drivers except for few, would anyone please guide me to filter out those drivers, so that i keep only those drivers which are actually needed from ahs repo??

just remove the drivers packages you don't need. all the packages end with -dkms.

[gurpreetkapoor]

On newly installed MX KDE Plasma, it includes packages installed from ahs repo, every time running update, if there are any updates in ahs repo, its too slow to perform update as i believe it compiles drivers for particular kernel version through dkms, even though i dont need most of those ahs drivers except for few, would anyone please guide me to filter out those drivers, so that i keep only those drivers which are actually needed from ahs repo??

just remove the drivers packages you don't need. all the packages end with -dkms.

Thanks @dolphin_oracle for reply, I did not notice that. sorry for that.

[gurpreetkapoor]

just a suggestion. Why not mx 23 Kde Plasma move to kio-admin instead of kde-servicemenu-rootactions by default???

[dolphin_oracle]

just a suggestion. Why not mx 23 Kde Plasma move to kio-admin instead of kde-servicemenu-rootactions by default???

what is the reason to do that?

[gurpreetkapoor]

just a suggestion. Why not mx 23 Kde Plasma move to kio-admin instead of kde-servicemenu-rootactions by default???

what is the reason to do that?

kde plasma 5.27.5 has all the functionality by default, which is provided by kde-servicemenu-rootactions, I am not sure whether kde-servicemenu-rootactions package is maintained upstream or not. kio-admin package is available in debian 12, it also enables root menu action in dolphin and other graphical applications on right click.

[siamhie]

@Jerry3904 @Melber @ceeslans

From what I can tell the {fluxbox-remote reloadstyle; fluxbox-remote reconfigure; idesktoggle idesk refresh} command will overwrite ANY manual edits made to the init file.

Case in point. I've moved some entries around so that (to me) they are in some sort of order.

session.screen0.struts: 0,0,0,0 > line 29
session.screen0.struts.1: 0,0,0,0 > line 30
session.screen0.workspacewarpingvertical: false > line 31
session.screen0.workspacewarpinghorizontal: false > line 32

moved-entry2.jpg

After I run the above command the entries get moved back to (I assume) the original placement.

session.screen0.struts: 0,0,0,0 > moved to line 70
session.screen0.struts.1: 0,0,0,0 > moved to line 34
session.screen0.workspacewarpingvertical: false > moved to line 41
session.screen0.workspacewarpinghorizontal: false > moved to line 44

[Jerry3904]

It looks like this bug is actually a feature, judging from this sentence in the Fluxbox Help doc about slitlist:

Similar to the init file it should not be edited while fluxbox is running. Otherwise changes may get overwritten.

That "may" seems to explain why we have been making changes via scripts all along without problem: it may only refer to manual edits to keep the system stable--perhaps especially the remote system.

[siamhie]

It looks like this bug is actually a feature, judging from this sentence in the Fluxbox Help doc about slitlist:

Similar to the init file it should not be edited while fluxbox is running. Otherwise changes may get overwritten.

That "may" seems to explain why we have been making changes via scripts all along without problem: it may only refer to manual edits to keep the system stable--perhaps especially the remote system.

@Jerry3904 @dolphin_oracle @ceeslans I've tracked down which fluxbox-remote command overwrites manual edits of the init file. (fluxbox-remote reloadstyle)

I broke down the command to individual entries and came up with this.

Refresh-orig and Refresh-2 overwrite manual edits of the init file. The other Refresh entries do not.

Code: Select all

[exec] (Refresh) {fluxbox-remote restart; idesktoggle idesk refresh }
[exec] (Refresh-orig) {fluxbox-remote reloadstyle; fluxbox-remote reconfigure; idesktoggle idesk refresh}
[exec] (Refresh-2) {fluxbox-remote reloadstyle; idesktoggle idesk refresh}
[exec] (Refresh-3) {fluxbox-remote reconfigure; idesktoggle idesk refresh}

Even the stock fluxbox root menu doesn't have the reloadstyle command. (copied from /etc/X11/fluxbox//fluxbox-menu)

Code: Select all

[workspaces] (Workspaces)
[reconfig] (Reconfigure)
[restart] (Restart)
[exit] (Exit)

Do we need the reloadstyle command?

Code: Select all

Window Manager Commands

These commands affect the Window Manager, or more than one window.

Restart [path]
Restarts fluxbox. This does not close any running applications. If the optional path is a path to an executable window manager, that manager is started in place of fluxbox.

Quit | Exit
Exits fluxbox. This will normally cause X to stop as well and terminate all existing applications, returning you to the login manager or console.

Reconfig | Reconfigure
Reloads all fluxbox configuration files including the keys file, apps file, and init file, if they have changed.

SetStyle path
Sets the current style to that given in path, which must be the full path to a fluxbox style.

ReloadStyle
Reloads only the current style. Useful after editing a style which is currently in use.

ExecCommand args … | Exec args … | Execute args …
Probably the most-used binding of all. Passes all the arguments to your $SHELL (or /bin/sh if $SHELL is not set). You can use this to launch applications, run shell scripts, etc. Since all arguments are passed verbatim to the shell, you can use environment variables, pipes, or anything else the shell can do. Note that processes only see environment variables that were set before fluxbox started (such as in ~/.fluxbox/startup), or any that are set via the Export or SetEnv commands, below. See fluxbox(1) for more details on the ENVIRONMENT and \~/.fluxbox/startup file.

CommandDialog
Pops up a dialog box that lets you type in any of these commands manually.

SetEnv name value | Export name=value
Sets an environment variable in Fluxbox. It will be passed to any applications spawned by any future ExecCommand commands.
    
SetResourceValue resourcename resourcevalue | SetResourceValueDialog
Sets a fluxbox resource value, which are normally stored in the init file. See fluxbox(1) for more details on available resources and allowed values.

[Jerry3904]

Thanks for tracking it. Not sure ATM bcuz others worked on it; so we'll flag @ceeslans and@dolphin_oracle and see what they think