MX 17

Changing border size with Xfce4 Window Manager


In Xfce, the overall look of windows and applications is controlled not just by the GTK theme applied, but also by the Window Manager (WM) theme which “is responsible for the placement of windows on the screen, provides the window decorations and allows you for instance to move, resize or close them“ (Link 1)

Even though most GTK themes will include a subfolder with the accompanying WM theme, you can choose to mix and match your GTK theme with the window decorations and borders from any other WM theme. 

Snap packages and MX Linux

Running snap packages (snaps) is problematic on our default MX setup because of a couple of factors.

1.  snapd (the snaps backend) requires systemd and we use sysVinit by default

2.  snapd confinement doesn't like the symlink we use to link /tmp to /var/tmp.

But you can run snaps on MX if you follow these steps.

1.  Remove the symlink for /tmp and replace with a new directory folder with 1777 permissions

    sudo rm /tmp && sudo mkdir /tmp && sudo chmod 1777 /tmp

How to completely remove Xfce

It's not totally obvious how to get rid of Xfce, so user kmathern came up with this single command:

dpkg -l | grep .*xfce.* | awk '{print $2}' | xargs sudo apt-get purge -V --auto-remove --force-yes -y

When that has finished, then reinstall one package:

sudo apt install desktop-defaults-mx-common



V. 20190105

Create a Live usb w/Persist from a Windows Desktop

This process will allow you to create either 32 or 64 bit live USB thumbdrives with persistence.

* Meaning: It'll behave just like a real system and remember what changes you make and programs you install, etc.


Desktop PC with unetbootin and both 32 & 64 bit MX .iso files on it.

* For MX Linux that would mean MX-17.n_x64.iso MX-17.n_386.iso

* 2ea blank USB thumbdrives >= 8G (recommend 8G for source drive and 32G for target/final product drive)

Watch these videos:

Reset your root and user passwords when you forgot both

So you forgot your root and user passwords?  Or maybe you don't know what they are?   Don't fret, on an installed system you can reset them, but its a little hacky and will require some console command line work.

Don't worry, its easy.

1.  Boot your machine.  At the grub boot menu menu, hit 'e' to edit the grub menu entry.

2.  find the line that reads like this:  

linux /boot/vmlinuz-xxxxx  

at the end of which are boot codes.  on the same line, at the end add


wifi suspend issues

Wifi works great, except resuming from Suspend

Troubleshooting: Does it work if you click on the network widget in the taskbar, then disconnect and reconnect to the access point? Some laptops would exhibit this symptom--it would say it was connected after the resume, but no bits would come over the connection until the above was executed. steveo's fix was to add the wi-fi driver module to a file that unloads it before suspend and reloads it after resume.

From a command line use


Subscribe to RSS - MX 17