MX Linux Forum

exo-preferred-applications

I used an automated tool to generate the obmenu, and it works for everything except the MX Linux links (they seem to follow some non-standard approach for .desktop files/ layout) see: https://sysdfree.wordpress.com/2018/02/15/165/

## Openbox autostart
## ====================
## When you login to your Openbox session, this autostart script
## will be executed to set-up your environment and launch any applications
## you want to run at startup.
##
## Note: some programs, such as 'nm-applet' are run via XDG autostart.
## Run
## /usr/lib/x86_64-linux-gnu/openbox-xdg-autostart --list
## or
## /usr/lib/i386-linux-gnu/openbox-xdg-autostart --list
## to list any XDG autostarted programs.
##
## More information about this can be found at:
## http://openbox.org/wiki/Help:Autostart
##
## This script is modified from the original available at
## http://forums.bunsenlabs.org
##

### SETTINGS START

## Turn on/off system beep.
xset b off

## Set keyboard settings - 250 ms delay and 25 cps (characters per second) repeat rate.
## Adjust the values according to your preferances.
xset r rate 250 25

## Set Desktop Manager
sleep 1; pcmanfm --desktop &

## Add keyboard mapping.
#xmodmap -e "keysym Insert = Multi_key"

## Disable CapsLock
#setxkbmap -option ctrl:nocaps
# alternative: use as compose key
#setxkbmap -option compose:caps

# Alias Super key to Super+Space for single-key menu.
# See 'man xcape' for other possibilities.
xcape -e 'Super_L=Super_L|space'

### TOUCHPAD: comment out the next two entries if you don't have one

## Configure touchpad. See 'man synaptics' for more info.
## (Now might be using libinput instead of synaptics.)
synclient VertEdgeScroll=1 HorizEdgeScroll=1 TapButton1=1 2>/dev/null

## Disable touchpad while typing
syndaemon -i .5 -K -t -R -d &

### TOUCHPAD END

### SETTINGS END

## GNOME PolicyKit authentication
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &

## Set a wallpaper
#nitrogen --restore
#variety &
#fehbg &
feh --randomize --bg-fill /usr/share/backgrounds/openbox/*

## Compton
## NOTE: composition must be started before tint2
compton &

## Start the tint2 session (the default tint2 will run if no sessions have been set)
tint2 &

## Volume control for systray
pnmixer &

## Start the Conky session (the default conkyrc will run if no sessions have been set)
# bl-conky-session --autostart &

## Start Clipboard manager
 clipit &

manyroads wrote: Tue Apr 23, 2019 8:21 am-- I elected to use Compton as the Compositor rather than xcompmgr (Compton comes with a nice Configurator and is much more user friendly, but heavier than xcompmgr.) It is, also, reasonably tear-free.

compton -b --backend glx --vsync opengl-mswc

manyroads wrote: Tue Apr 23, 2019 8:21 am ===== AutoStart (located in ~/.config/openbox of your install) ==================

Code: Select all

[...]
## Set Desktop Manager
sleep 1; pcmanfm --desktop &

Head_on_a_Stick wrote: Tue Apr 23, 2019 12:48 pm Nice work!

A few comments:

manyroads wrote: Tue Apr 23, 2019 8:21 am-- I elected to use Compton as the Compositor rather than xcompmgr (Compton comes with a nice Configurator and is much more user friendly, but heavier than xcompmgr.) It is, also, reasonably tear-free.

For optimal tear-reduction launch compton like this:

Code: Select all

compton -b --backend glx --vsync opengl-mswc

But the glx backend only works if hardware accelerated graphics are available (which is why BL & MX use the stock xrender backend with no vsync).

More here: https://github.com/chjj/compton/wiki/perf-guide

manyroads wrote: Tue Apr 23, 2019 8:21 am ===== AutoStart (located in ~/.config/openbox of your install) ==================

Code: Select all

[...]
## Set Desktop Manager
sleep 1; pcmanfm --desktop &

Don't put sleep commands in the autostart file, we found that the ones in the #! autostart file could cause race conditions and result in the panel not being transparent because the compositor was started after tint2 as well as a few other things — that's why the BL version doesn't include any (and also why the compositor is controlled from a script).

I will play around with your ISO and offer some more feedback later.

manyroads wrote: Tue Apr 23, 2019 8:21 am Catfish file search does not function.

exo-preferred-applications

I used an automated tool to generate the obmenu, and it works for everything except the MX Linux links (they seem to follow some non-standard approach for .desktop files/ layout) see: sysdfree.wordpress...

   desktop_files_paths   : Absolute paths which contain .desktop files.
                              Example: [  '/usr/share/applications',
                                "\$ENV{HOME}/.local/share/applications",
                                glob("\$ENV{HOME}/.local/share/applications/wine/Programs/*"),   ]

chrispop99 wrote: Tue Apr 23, 2019 1:54 pm Thanks manyroads.

Is this 64-bit? I wondered if a 32-bit would be of interest to users with older hardware.

Chris

Head_on_a_Stick wrote: Tue Apr 23, 2019 2:06 pm Quick update:

manyroads wrote: Tue Apr 23, 2019 8:21 am Catfish file search does not function.

It works with the Adwaita icon theme selected, running it with the Sardi icon theme returns an error about not being able to load the pixbuf from the icon theme.

skidoo wrote: Tue Apr 23, 2019 2:09 pm PCManFM, does it (its exo backend) ignore elections specified via galternatives ?

manyroads wrote: Tue Apr 23, 2019 2:28 pm I was looking for a pixabuf fix. But it looks like both apps require gtk3.

skidoo wrote: Tue Apr 23, 2019 2:09 pm if no joy with catfish, consider replacing it with "searchmonkey"

Code: Select all

exo-preferred-applications

PCManFM, does it (its exo backend) ignore elections specified via galternatives ?

chrispop99 wrote: Tue Apr 23, 2019 4:37 pm Clicking the network icon on the panel shows the list of available wireless networks, but clicking the preferred network makes the panel icon disappear. Network manager doesn't launch.

Chris

manyroads wrote: Tue Apr 23, 2019 2:27 pm

chrispop99 wrote: Tue Apr 23, 2019 1:54 pm Thanks manyroads.

Is this 64-bit? I wondered if a 32-bit would be of interest to users with older hardware.

Chris

Hi Chris... yes it is 64bit.

JayM wrote: Wed May 01, 2019 1:44 am [...]
I'm very interested in running this on my old netbook if either a 32-bit version is in the offing or if there's a script that I can run on the stock 32-bit MX installation that's on it to turn it into this Openbox spin. Thanks.

#!/bin/bash
sudo apt update
sudo apt-get remove --purge aisleriot asunder chromium-bsu chromium-bsu-data clementine clipit dconf-editor dict fbreader featherpad feh firefox galculator geany geany-common gimp gimp-data gmtp gnome-hearts gnome-mahjongg gnome-ppp gnome-schedule gscan2pdf gsmartcontrol gtkhash gtkhash-common guvcview* hexchat htop lbreakout2 lbreakout2-data libreoffice* lightning luckybackup luckybackup-data mc mc-data nomacs nomacs-l10n onboard onboard-common onboard-data orage pdfshuffler peg-e pppoeconf qpdfview* samba samba-common samba-common-bin samba-libs simple-scan smtube swell-foop thunar-gtkhash thunderbird vlc xfce4-notes xfce4-notes-plugin xfce4-sensors-plugin xfce4-taskmanager  xfce4-dict
#
sudo apt autoremove --purge

OpenBox dependencies:
build-essential
pkg-config
libpango1.0-dev
libglib2.0-dev
libxml2-dev
libxcursor-dev
libimlib2-dev
libstartup-notification0-dev
xlibs-dev
libxext-dev
x11proto-randr-dev

For Debian menu use:
menu
menu-xdg

Building and installing the program
Once you have the above dependancies installed, you are ready to build Openbox. You can obtain the source code from github.com (or as through tar archives (eg. linux from scratch)):

$ git clone https://github.com/Mikachu/openbox.git
Run bootstrap script to obtain configuration scripts

$ ./bootstrap
Then run:

  $ ./configure --prefix=/usr --sysconfdir=/etc
	...configure detects the build evironment...
 $ make
	...openbox builds...
  $ sudo make install
	...openbox installs...
If you do not want to install to /usr, then you should use ./configure --prefix=<whatever you want> --sysconfdir=/etc --datarootdir=/usr/share. If you don't do this, the Openbox log in options will not be available, because they need to be installed to /usr/share/xsessions.

If the configure command fails and the reason is not obvious, you should look in the generated config.log file to discover the cause of the problem.

For 64-bit distributions
When building Openbox on the 64-bit versions of Debian or Fedora, use:

$ ./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib64
$ make
$ sudo make install

Head_on_a_Stick wrote: Wed May 01, 2019 1:03 pm @manyroads, why are you building openbox from source?

manyroads wrote: Wed May 01, 2019 4:11 pmI have had better success with a source build of Openbox

manyroads wrote: Wed May 01, 2019 4:11 pmI'm having even BETTER success with antiX

manyroads wrote: Wed May 01, 2019 4:28 pm Actually antiX in general seems not to like VirtualBox very much. I can make it work but getting privs to work so that Guest Additions installs and allows 'seamless' shared file access is much harder than it ought to be.

I have not tried installing OB on antiX yet...

manyroads wrote: Wed May 01, 2019 4:28 pm Pieces like communication (network) seems sporadic and unpredictable with the repo versions of OB.

As an aside, I m becoming something of a fan of iceWm... after I add a few tweaks and a decent set of themes and icons. Fluxbox themes is a bit too 'retro', for me (clunky looking). jwm is not bad but seems a bit unstable, especially with networking from Virtualbox. Actually antiX in general seems not to like VirtualBox very much. I can make it work but getting privs to work so that Guest Additions installs and allows 'seamless' shared file access is much harder than it ought to be.

I have not tried installing OB on antiX yet...

anticapitalista wrote: Wed May 01, 2019 4:51 pm [...]
You must use VB 6 version.
Also, do remember that this antiX version is an alpha release and will have lots of issues.

dolphin_oracle wrote: Wed May 01, 2019 5:50 pm add your user to the "vboxsf" user group (login/logout) to use shared file access

manyroads wrote: Wed May 01, 2019 7:48 pm

dolphin_oracle wrote: Wed May 01, 2019 5:50 pm add your user to the "vboxsf" user group (login/logout) to use shared file access

Did that. I get a different problem when I miss on that error/setting. The version I have works (sort of), I simply need to do everything using the root verison of SpaceFM. Access from non-root to the shared drive is not happy unless its from root. I do think it may have something to do with the version 5 vs. 6 of VB issue mentioned by @anticapitalista. I'll test that specifically in the next iteration.

dolphin_oracle wrote: Wed May 01, 2019 8:04 pm FWIW I'm using VB 5.2.24 with the latest antiX alpha 19a1 as a guest (VB 6 guest additions preinstalled) and not having any problems with shared folder access, either reading or writing.

manyroads wrote: Wed May 01, 2019 4:28 pm Pieces like communication (network) seems sporadic and unpredictable with the repo versions of OB.

manyroads wrote: Fri May 03, 2019 7:02 am
As for OB being abandoned or 'functionally stabilized', I was not aware. That actually seems reason enough to move on to another wm (like iceWM which is still alive, so far as I can tell.).

PPC wrote: Fri May 03, 2019 7:28 am

manyroads wrote: Fri May 03, 2019 7:02 am
As for OB being abandoned or 'functionally stabilized', I was not aware. That actually seems reason enough to move on to another wm (like iceWM which is still alive, so far as I can tell.).

Hi Manyroads!
iceWM (or my favorite Fluxbox) is a good wm to go, and also has a "plus" - it can make MX and antiX be more similar (both in: 1- the way antiX looks, making it more visually appealing to both new and currents users and 2- in the way Mx may use less resources, just like antiX).
My antiX with a Fluxbox that looks like MX (windows decorations and horizontal bar with quick launchers and quick buttons to eject usb devices, volume control and exit) uses about 120 meg of RAM on idle, less than 110 meg if no desktop icons/conky - sorry, not the exact numbers, I'm not on that pc right now...
Fluxbox as some "problems" like no notifications out of the box (you can work around that and install a system notifier).

P.

Fluxbox as some "problems" like no notifications out of the box

you can work around that and install a system notifier

manyroads wrote: Fri May 03, 2019 7:02 am As for OB being abandoned or 'functionally stabilized', I was not aware. That actually seems reason enough to move on to another wm

Head_on_a_Stick wrote: Sun May 05, 2019 1:47 pm
The openbox project is still maintained but it is considered feature-complete and so will not be developed any further, I would consider this to be a major advantage.

EDIT: although Lubuntu are going to fork openbox and develop a Wayland-based version under the Mir display server, apparently.

Reference: https://lubuntu.me/lubuntu-development-newsletter-9/

manyroads wrote: Sun May 05, 2019 6:23 pm If you believe that the antiX/MX family of OSes ought to have an OB respin

manyroads wrote: Sun May 05, 2019 7:04 pm I'll have to try the Devuan OpenBox variant Star

manyroads wrote: Wed May 01, 2019 6:47 am

JayM wrote: Wed May 01, 2019 1:44 am [...]
I'm very interested in running this on my old netbook if either a 32-bit version is in the offing or if there's a script that I can run on the stock 32-bit MX installation that's on it to turn it into this Openbox spin. Thanks.

Hi @JayM, I am using my minimal script to strip down MXLinux and then adding OpenBox.

Here's the stripping commnds:

Code: Select all

#!/bin/bash
sudo apt update
sudo apt-get remove --purge aisleriot asunder chromium-bsu chromium-bsu-data clementine clipit dconf-editor dict fbreader featherpad feh firefox galculator geany geany-common gimp gimp-data gmtp gnome-hearts gnome-mahjongg gnome-ppp gnome-schedule gscan2pdf gsmartcontrol gtkhash gtkhash-common guvcview* hexchat htop lbreakout2 lbreakout2-data libreoffice* lightning luckybackup luckybackup-data mc mc-data nomacs nomacs-l10n onboard onboard-common onboard-data orage pdfshuffler peg-e pppoeconf qpdfview* samba samba-common samba-common-bin samba-libs simple-scan smtube swell-foop thunar-gtkhash thunderbird vlc xfce4-notes xfce4-notes-plugin xfce4-sensors-plugin xfce4-taskmanager  xfce4-dict
#
sudo apt autoremove --purge

Here's the rest of what I'm using... notes & all.

Code: Select all

OpenBox dependencies:
build-essential
pkg-config
libpango1.0-dev
libglib2.0-dev
libxml2-dev
libxcursor-dev
libimlib2-dev
libstartup-notification0-dev
xlibs-dev
libxext-dev
x11proto-randr-dev

For Debian menu use:
menu
menu-xdg

Building and installing the program
Once you have the above dependancies installed, you are ready to build Openbox. You can obtain the source code from github.com (or as through tar archives (eg. linux from scratch)):

$ git clone https://github.com/Mikachu/openbox.git
Run bootstrap script to obtain configuration scripts

$ ./bootstrap
Then run:

  $ ./configure --prefix=/usr --sysconfdir=/etc
	...configure detects the build evironment...
 $ make
	...openbox builds...
  $ sudo make install
	...openbox installs...
If you do not want to install to /usr, then you should use ./configure --prefix=<whatever you want> --sysconfdir=/etc --datarootdir=/usr/share. If you don't do this, the Openbox log in options will not be available, because they need to be installed to /usr/share/xsessions.

If the configure command fails and the reason is not obvious, you should look in the generated config.log file to discover the cause of the problem.

For 64-bit distributions
When building Openbox on the 64-bit versions of Debian or Fedora, use:

$ ./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib64
$ make
$ sudo make install

I hope this helps you out.

anticapitalista wrote: Mon May 06, 2019 7:36 am Someone has offered antiX with openbox - and is looking for feedback.

https://www.antixforum.com/forums/topic/antixlabs/

old_guy wrote: Mon May 06, 2019 9:30 am manyroads
Same here.
I ran "locate install" in a term and found "/usr/sbin/minstall". Ran that and it installed.
Earl

anticapitalista wrote: Mon May 06, 2019 7:36 am Someone has offered antiX with openbox - and is looking for feedback.

PPC wrote: Thu May 09, 2019 6:08 am [...]
Side question: did you get to tinker with antiX fluxbox, Mark?

P.

manyroads wrote: Thu May 09, 2019 11:05 am Plus I'll share my setup scripts etc so anyone (not afraid of cli) can do it themselves where ever they like (on a debian platform).

PPC wrote: Thu May 09, 2019 11:50 am

manyroads wrote: Thu May 09, 2019 11:05 am Plus I'll share my setup scripts etc so anyone (not afraid of cli) can do it themselves where ever they like (on a debian platform).

Nice, Mark! I only asked this because I'm the guy that sent you my antiX Fluxbox "transformation pack" and was curious if you would be doing anything with that :-), but it's outside of the scope of what you are now doing...
Also if I may be so bold as to suggest a "GUI" script for you to add to the stuff you are using and making available to other people- viewtopic.php?f=40&t=48644
I start this script with a icon that mimics "MX updater". This basicly allows a antiX user to update the OS's packages without using the CLI or Synaptic - just click the icon, enter the password and click a button... It didn't get a very warm welcome when I made it available in the forum, maybe you can do something positive with it :-) [I belive the script was included in all the files I sent up, I'm too lazy to check now :-) ]
Also I noticed one thing- antiX fluxbox's config is missing an option to eject usb devices (I had to dig deep to find where it was and create a quick launcher for it- I wonder why FB does not have this program easily available...

Take care!

P.

#!/bin/bash

# ======  Cleanup  ======
# Clean packages and install scripts in /var/cache/apt/archives/
sudo apt-get clean
# Removes orphaned packages which are no longer needed and purges
sudo apt autoremove --purge
#
# ======  Update-Upgrade  ======
#
# update the stable software
sudo apt update
# perform full stable update/ upgrade
sudo apt full-upgrade
# perform testrepo full update
sudo apttestrep update
sudo apttestrepo upgrade
{/code]

manyroads wrote: Thu May 09, 2019 5:33 pm As for fluxbox, I have to say it is a bit peculiar. The worst thing I've found are the panel and how it handles icons (you can use anything you want so long as it's square.).

dolphin_oracle wrote: Mon May 13, 2019 12:21 pm I would look at your polickit authentication agent and make sure its running. its sounds to me like a lot of issues point towards a wonky policykit setup.

dolphin_oracle wrote: Mon May 13, 2019 12:21 pm I would look at your polickit authentication agent and make sure its running. its sounds to me like a lot of issues point towards a wonky policykit setup.

manyroads wrote: Mon May 13, 2019 1:18 pm

dolphin_oracle wrote: Mon May 13, 2019 12:21 pm I would look at your polickit authentication agent and make sure its running. its sounds to me like a lot of issues point towards a wonky policykit setup.

Well I tried:
-- reinstalling policykit (that did nothing)...
-- copying a working set of policykit files from my home xfce machine (no joy)

I read debian instructions on policykit installations with sysVinit & shim and they didn't offer any obvious clues.
Mother google did not turn up much that looked helpful except for some things on stackexchange that mirrored the above actions.

Head_on_a_Stick wrote: Mon May 13, 2019 3:27 pm The OP indicates that /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 is listed in the openbox autostart file and so should be running.

dolphin_oracle wrote: Mon May 13, 2019 3:31 pm I have not had success starting policykit-1-gnome that way.

Head_on_a_Stick wrote: Mon May 13, 2019 3:44 pm

dolphin_oracle wrote: Mon May 13, 2019 3:31 pm I have not had success starting policykit-1-gnome that way.

It works for BunsenLabs

The OP lifted the autostart file from that distribution and it was in turn inherited from CrunchBang (with some changes).

dolphin_oracle wrote: Mon May 13, 2019 3:31 pm

Head_on_a_Stick wrote: Mon May 13, 2019 3:27 pm The OP indicates that /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 is listed in the openbox autostart file and so should be running.

I have not had success starting policykit-1-gnome that way. lxpolkit yes, but not policykit-1-gnome.

manyroads wrote: Mon May 13, 2019 4:00 pm I tried both:
policykit-1-gnome
lxpolkit

/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &

Head_on_a_Stick wrote: Mon May 13, 2019 4:20 pm

manyroads wrote: Mon May 13, 2019 4:00 pm I tried both:
policykit-1-gnome
lxpolkit

There is no policykit-1-gnome command, you need to use

Code: Select all

/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &

I've just tried your ISO and that line is missing from ~/.config/openbox/autostart and if I put it back at the end of that file, log out and log back in again then synaptic works.

The only problem is that the dialogue box asks for the root password rather than the user password.

Also, empty your trash before making an ISO image

manyroads wrote: Mon May 13, 2019 4:38 pm I ran autoclean and autoremove --purge

rm -rf ~/.local/share/Trash/*

Head_on_a_Stick wrote: Mon May 13, 2019 4:40 pm

Code: Select all

rm -rf ~/.local/share/Trash/*

Be careful typing that though.

manyroads wrote: Mon May 13, 2019 4:38 pm I like the way pcmanfm does the desktop management, am not happy with using either xfdesktop or spacefm. Might you have any suggestion(s)?

manyroads wrote: Mon May 13, 2019 5:33 pm I am unable to find the terminal command that displays the obmenu. Do you happen to know what it is?

Head_on_a_Stick wrote: Tue May 14, 2019 2:25 pm
I am ideologically opposed to icons on the desktop, it is a sin against nature. [...]

But you should probably try to figure out that permission issue rather than just work around it. [...]

If you're using obmenu then it just creates ~/.config/openbox/menu.xml for you, there is no command that can be used to display the openbox menu (AFAIK).

The menu should display if you right-click tint2, that option is set in the configuration for the linked ISO image.

manyroads wrote: Tue May 14, 2019 2:56 pm Rather than using autostart heavily, I have tint2 managing the start functions.

manyroads wrote: Tue May 14, 2019 2:56 pm Right now the memory footprint seems to be hovering around 310MB.

Head_on_a_Stick wrote: Tue May 14, 2019 3:28 pm

manyroads wrote: Tue May 14, 2019 2:56 pm Rather than using autostart heavily, I have tint2 managing the start functions.

Really? How?

FWIW I think the autostart file is a more intuitive location for such things.

manyroads wrote: Tue May 14, 2019 2:56 pm Right now the memory footprint seems to be hovering around 310MB.

I managed to get the XFCE desktop in MX down to just over 200MiB:

http://forum.mxlinux.org/viewtopic.php? ... 21#p497583

The stock system has about half a million superfluous services and applications running, XFCE itself is very lightweight.

manyroads wrote: Wed May 15, 2019 9:52 pm Once I get a good openbox install I'll build the same thing on antiX... along with iceWM. I really am not a fan of fluxbox and jwm is ok but I leave that to others. The same with 32-bit. Not my cup of tea.

• Conky doesn't start automatically, is that what you want?
• Menu "Accessories" -> "MX Updater" is available twice and doesn't work (/usr/bin/apt-notifier-unhide-icon doesn't exist)
• Menu "Other": all items report only the Openbox error "Text was empty (or contained only space)".

gosia wrote: Fri May 17, 2019 4:33 pm Hello manyroads,
First of all, my English isn't that good, I hope you understand me anyway.
[...]

• Conky doesn't start automatically, is that what you want?
• Menu "Accessories" -> "MX Updater" is available twice and doesn't work (/usr/bin/apt-notifier-unhide-icon doesn't exist)
• Menu "Other": all items report only the Openbox error "Text was empty (or contained only space)".

[...]

gosia wrote: Fri May 17, 2019 4:33 pm [*]Menu "Accessories" -> "MX Updater" is available twice and doesn't work (/usr/bin/apt-notifier-unhide-icon doesn't exist) ...

old_guy wrote: Sun May 19, 2019 4:49 pm manyroads
Just downloaded rc2 and installed to Virtualbox.
You fixed the conky startup, but the info it shows???

System Information
User:mark@xxxxxx

Disk USE
System SSD

NETWORK
WAN IP XXXXXXXXXX

Info needs to be deleted from somewhere.

Also for Thunar to Browse Network I had to install gvfs-backends

Will continue to look through it - keep up the good work.

Earl

${image img/hard-disk.png -p 0,585 -s 30x30}
${offset 35}${font Good Times:size=12}${color2}DISK USE ${color}${hr 2}${font}
${voffset 15}${color}System SSD:
${color}Used: ${color}${fs_used /} of${color1}${fs_size /} ${color}~ Free: ${color0}${fs_free /} ${color}or${color0} ${fs_free_perc /}% ${color}
${color lightgrey}Read: $color${diskio_read}${alignr}${color lightgrey}Write: ${color}${diskio_write}
${diskiograph_read /dev/sda 10,160 FFFF14 FFFF14 -l}${diskiograph_write /dev/sda 10,160 48FF1C 48FF1C -l}

manyroads wrote: Wed Oct 09, 2019 4:39 pm Details for the BunsenLabs Lithium (Experimental) installs (tutorial) on MX19b3 & antiX19b3 are available here.

http://eirenicon.org/getting-bunsenlabs ... a-journey/

manyroads wrote: Sun May 19, 2019 2:53 pm Hello all.

I have fixed all reported bugs (by my testing) and changed the wallpapers to be more screen-size independent. Unless I hear otherwise, I think this release is very close to being 'ready for prime-time'.

You may download the current RC from here (it should be uploaded/available about 1930 UTC today 19 May 2019) :

http://treemagic.org/MX%20Desktops/MX-Openbox-rc

S.t.e.P. wrote: Mon Nov 15, 2021 11:59 am I'd like to install MX with Openbox on a old PIII PC. The thing is: The MX installer in the live session stops after 15% every time. What I can do is install MX via cli (adding 3 in the live boot screen). But afterwards neither the Fluxbox version nor XFCE are loading properly.
That's why I would like to install MX with Openbox. What I'm wondering now is how can I make Openbox the default DE during installation via cli so that Openbox is loaded as DE. Do you have an idea or suggestion [sorry in advance if the solution is actually obvious but I don't see it]?

lxpanel &
pcmanfm --desktop &

S.t.e.P. wrote: Sun Nov 21, 2021 10:16 am It worked! Thanks to your advice figueroa!
Now this machine from 1999 (was "powerful" at the time and cost me 2.600,00 DM) has an up to date OS.
Also thanks to the whole MX team. You, providing 32bit, saved resources - this PC can now still run.

the following inxi has been made under AntiX, which was running on that PC before: