Release announcement with links to KDE release too: https://mxlinux.org/blog/mx-21-beta-2-now-available-for-testing-purposes/
FAQ: Do I need to reinstall if I have Beta1 installed?
Need - no if you just want to use it, if you want to "test" it would help us if you download Beta 2 and test it. Also some stuff doesn't carry over with a simple update: if you want to test the Live system for example.
I don't think it would take too long, we'll need to work out all the major bugs we find, Beta1 looks good so I don't foresee a huge number of betas, maybe another Beta2 after Debian release and then probably a Release Candidate.
We'll probably release KDE and Fluxbox betas alongside with Beta2. If you are user of MX-19 KDE Buster you won't see any upgrade other than the regular fixes that come though Buster. If you need to upgrade to MX-21 you'll need to reinstall, we recommend clean reinstalls every time we change Debian release. That being said, if you are an advanced user and don't mind experimenting you could upgrade to Bullseye in place: https://mxlinux.org/wiki/upgrading-from-mx-19-to-mx-21-without-reinstalling/ back up your data and system, if something breaks the fix is "reinstall from backup".
It looks like you are booting into systemd instead of the default SysV. "The user will end with MX Linux using systemd but with no guarantee about its degree of functionality." https://mxlinux.org/wiki/system/systemd
i use a program called timeshift for situations like this. by default it only keeps track of system files so that rolling back to a previous state won't set your personal files back as well. i tend towards overkill with how many snapshots i keep, but will make one before installing any new program or updates just in case they happen to destabilize my system: https://teejeetech.in/timeshift/
timeshift is available in the stable repo. in a situation like the one you just went through, it can even be used from a live usb or recovery mode to roll the system back.
I updated mx-packageinstaller-pkglist, but when trying to install Mullvad via the MX Package installer, now it says ERROR: Download of Mullvad VPN failed [no file name]. I tried a couple of different repos, Athens, Hamburg and Umeå.
Just a bit more information on all the persistence options:
Credits for the info (here and here). The information is still valid but they are using an older install of MX Linux which is why I didn't link it in my first post.
so you want to not encrypt swap, and you consider that more secure than swap on an encrypted partition? what's not secure about a luks encrypted swap partition?
as for zram, I think this is still valid
https://mxlinux.org/wiki/other/zram/
what you want to do probabley is create the lvm ahead of time on the host system, and use that as the target for the installation. before, not after. probably folks in our forum can help, I know nothing about lvms.
What are you using for a machine and what Linux .. details? You might give Lutris and Wine a shot. One of the commenters (chopdoc) below the article said it worked for him.
"I did this yesterday and it works perfectly right out the box.
Install Wine 4 stable Note, you might have to remove your previous version of WIne. Use synaptic package manager for this.
Install Lutris, then install WOW thru lutris. No glitches at all.
Linux Mint 18.3 Cinnamon 3.6.7
Running 100FPS now"
https://itch.io/t/13882/deb-and-rpm-arent-supported-by-itch-please-ship-portable-linux-builds
" Some games on itch.io ship with a .deb or .rpm package file.
However, itch (the desktop app), does not support DEB or RPM and will never support them."
https://github.com/ValveSoftware/Proton/releases/tag/proton-5.13-4
and
https://boilingsteam.com/cyberpunk-2077-safely-lands-on-linux-on-day-1/
Sorry. To actually answer your question, I haven’t tried running it yet.
from the start the machine is a thinkpad t430s I5 processor 16gb or ram, and a 250gb ssd. second I don't get an error message during install, I installed lutris via apt get, and installed battle.net via lutris.net... when it goes to load a box pops up asking me if I want to send to battle.net.
Are you booting from BIOS or UEFI mode? Also does your system support secure boot and is it enabled? You might also need to confirm that you have the correct version of the iso on your thumb drive. Some disk images aren't bootable by themselves and require a separate boot loader to be installed on the disk. Check out the faq on etcher's sight for more info on that last point. Good luck!
Hi! I would say you should try the mxlinux forum forum.mxlinux.org Their community is very helpful there.. This subreddit is not their prefered channel of communication..
I don't know the full reasons of mxlinux climbing to number on distrowatch, it's a mix of factors. Thing about Linux is that there's a lot of them, and you got to try and check what goes your way.. It's not because mxlinux is first on distrowatch that is the total best at everything.. Strong selling points that made me using it now as daily driver.. Easy to install, lots of pre-configured software (some people don't like this) very fast (due to xfce desktop environment) and the amazing feature of being installed on a USB stick, and can handle persistence easily. This was essential because for a time I was using other people's computers when needed, and with this I always had my own environment available..
Also, arch Linux seems to have a lot more users on reddit, yes.. I think that is explained that it is an advanced distro, very customisable, which means a bit of a learning curve to start using it.. Manjaro is arch, but with predefined stuff.. Easier entry..
Like I said, there's still no perfect distro, before I settled for mx I tried at least 7 or 8.. You can try here https://distrotest.net/.. And know that with patience you can start with one you don't even like and customise it to your liking.. Good luck!
For a quick look at MX Linux, or many others just go to https://distrotest.net/. Two clicks and you can try out any of the popular Linux distributions in a dedicated web page, no installing or downloading necessary. I switched to MX Linux a couple of months ago, and found this resource great when deciding which distro fit my needs. PS...MX Linux was easy to migrate to from Mint/Ubuntu.
Puppy is OK. But try out AntiX, which is a lower end from the same developer from MX.
I think 8GB should be enough to boot into MX. So it's either your graphic card giving it some problems. As the driver isn't install by default. or you actually don't have much RAM to process it all. It's either or and a bigger USB drive isn't going to fix that, if that's the case.
I don't have such hardware so I can't comment on that. But either way, the MX team don't even advertise MX as being lightweight, they say it's mid-weight. antiX on the other hand is targeted for older hardware.
In any case, I'm not pushing Plasma here, I'm just trying to see the dev's opinion on the OS's aesthetics, and whether they're ok with how it looks right now or if they plan to change it. IMO it can be XFCE or KDE or whatever, but IMHO it'd be great for it to look at least a little more modern.
Ya, I just tested and it doesnt work. I've also tried with sudo. Its just not working.
Seems it doesnt save/apply. This xfce4-mouse-settings needs to be fixed or another app needs to be used by default.
Same with touchpad-indicator. touchpad-speed is not saved/applied.
Unless you find another app that works (and please share here if you do) keep an eye on key-mapper Which I've opened a feature request asking for mouse-speed adjustment support.
I too would not actually like to use PayPal at all. I have donated to Linux Lite via a regular "wire transfer" with no problems:
Bank: Westpac New Zealand
Account: JRG Bezencon
Swift Code: WPACNZ2W
IBAN: 0301230321162000
https://www.linuxliteos.com/donate.html
-maybe MX could have similar?
​
There is, if you know what you are doing
(and by the way if you find these instructions complicated, you should see Debian's official instructions for upgrading between releases)
It might just be the repo server listed in sources.list.d is down or your sources.list file has an error.
If you check it again now and it's still down try the mxlinux page on the sources.list.d and sources.list to make sure it's configured correctly.
I think it'll be harder to find 32 bit software.
If you really need something (newer version, etc.), you can search the internet.
According to this page:
https://forum.mxlinux.org/viewtopic.php?t=52970
You should (1) first look at MX repos, then (2) see if a flatpack is available, and (3) as last resort add a ppa if available.
Instructions:
GPU stuff's not really my wheelhouse, but I do recall MX having a scripted command line wizard for dealing with graphics driver stuff ... "inxi"? … "smxi"? … I'll look it up and come back …
Ah, "sgfxi" is actually the one I was thinking of. Here's a page in the MX wiki covering all three:
https://mxlinux.org/wiki/applications/guide-to-smxi-sgfxi-inxi/
Good Luck!
If you're running a recent release of MX 19, a custom MX Fluxbox WM based DE is also preinstalled alongside the default Openbox WM based Xfce DE.
(WM = window manager; DE = desktop environment)
I.e. if you're running a recent (19.2 or later) release of the default 32 bit Xfce version of MX Linux you should be able to select fluxbox from the login screen GUI the same as one would for Xfce or Openbox or your LXDE addition … What version of the MX Linux 32 bit (default Xfce) release are you running?
If you're not running one of the more recent releases, you may be able to add it from the repos, as per …
Can't really speak for KDE version as I haven't used it yet. One downside is the version used in the respin is 5.14.5 (from 8 January 2019!) from the buster repository, while the KDE project is working on the 5.20 beta.
MX linux does have the best debian+XFCE implementation. It's wonderful to just install it and not have to "fix" anything because someone made sane defaults.
Use MX Linux if you prefer Xfce, use antiX if you prefer a more basic Desktop environment (not sure what they use now by default, fluxbox?)
Static persistence should work fine with fast USB 3.0.
From our documentation: https://mxlinux.org/wiki/help-files/help-mx-remaster/
>Dynamic and static root persistence
>Dynamic root persistence saves file system changes in RAM (just like a normal LiveCD/USB). The persist-save program must be run to copy these changes to the rootfs file so the can be remembered across reboots. Use persist-config to have the program run automatically on shutdown/reboot.
>Static root persistence saves file system changes directly in the rootfs file. It does not use any RAM so the only size limit is the size of the rootfs file. This makes it good for doing an “apt-get upgrade” or for installing a bunch of packages. It is usually best to follow up with a Live remaster to consolidate the file system changes into the compressed squashfs file.
>On many systems, static root persistence can be annoyingly slow. You are free to switch between static and dynamic root persistence each time you boot.
You do not have the drivers installed. Grab some Ethernet Connection, now you’ll have to do some manual work to get it done as Realtek uses proprietary components in this driver, making it impossible for the distribution maintainers to pack.
First, try to install the Mxlinux AHS Kernel. https://mxlinux.org/blog/new-advanced-hardware-support-repo-ahs-for-short/
If that doesn’t work, try out the following guide:
Here are the upgrade paths and, though I'm a bit new, it looks like 18 to 19 had no upgrade path because of the switch in Debian versions. I don't know how often they upgrade the Xfce version but the Debian major version only goes up once ever two years.
https://mxlinux.org/migration/
Honestly, it's not a big deal. Even with a distribution like Ubuntu where they provide an upgrade path you're better off just wiping the drive and reinstalling. Just back your files up to an external drive and copy it back after reinstall.
Just looking at it now there is also 'Codecs Installer' under MX tools menu that installs this and more, if anyone wants a GUI option.
https://mxlinux.org/wiki/help-files/help-mx-codecs-installer/
Not an answer to your direct question but I believe the AHS live install comes with 5.6 kernel as default now as of 19.2 https://mxlinux.org/torrent-files/ if that's what you're trying to achieve.
This is what I used to boot when 4.19 didn't like my new GPU.
https://mxlinux.org/migration/ and scroll to the header "From any version of MX-18 to MX-19". Here there are a couple of reasons here why it can't be a full rolling release.
I have personally tried updating the package names in sources from MX18(Stretch) to MX19(Buster) and while it appeared to work initially it started to break sooner than later.
On the other hand I have never had any real issue with backing up my home folder(and some parts of /opt) and just pasting it back into home after a fresh install. This has worked for me always on changing versions and distros even. In fact, I've had less issues doing this than with true rolling release distros.
Edit: messed up the debian codenames by a few generations. :)
Hi.
Some background might help: https://mxlinux.org/wiki/system/systemd/
A SNAP package always needs to have systemd running so if what you want is only available as a SNAP (make sure it is not available as a regular *.deb or an appimage), then you need to boot with that.
I had the same problem, after I update my GPU card. There is another trick if xterm is a default terminal in a application. To make the font's bigger as well. Because sometimes it's small as well.
~/.Xresources
Xft.dpi: 96
Xft.antialias: true
Xft.hinting: true
Xft.rgba: rgb
Xft.autohint: false
Xft.hintstyle: hintslight
Xft.lcdfilter: lcddefault
https://mxlinux.org/wiki/system/font-adjustment/
My are a little different;
! Fonts {{{
Xft.antialias: true
Xft.hinting: true
Xft.rgba: rgb
Xft.hintstyle: hintfull
Xft.dpi: 96
! }}}
​
xterm*faceName: fixed
xterm*faceSize: 18
​
Tweak to your liking.
Anything Qualcomm Atheros 802.11n will work on any distro, for example a AR9271 model. Or just install the non-free Broadcom drivers in MXlinux to use your existing WiFi card. Here is a guide: https://mxlinux.org/wiki/networking/broadcom-wireless/
You don’t need to use WINE to use Ubuntu to install MX on a USB though. WINE allows you to use Windows applications on Linux, it has nothing to do with this.
Use Etcher or try the MX Live USB Appimage on Ubuntu.
https://mxlinux.org/blog/live-usb-maker-tool-now-available-as-an-appimage/
I don’t know about that, you can always ask on the forum. The devs, admins, and moderators are very active there.
But I don’t believe there is an official Mastodon for MX. Edit: looks like it might be official after all.
I think the Facebook group is mostly supported by other users, but the team does get on there, more than here.
I think this list has them in the order of use for Social Media https://mxlinux.org/wiki/other/mx-linux-social-media/
From https://mxlinux.org/wiki/help-files/help-mx-conky/
Drag.
By far the easiest way of making fine adjustments to a basic position selected with Conky Manager is simply to drag it using the Alt key and the left mouse click. You can also resize the conky’s own window by using the Alt key and the right mouse click. You can see that window if you use Comky Manager to change the transparency to “opaque.” These changes are valid only for the session while the conky is running. When the conky is restarted, the script itself will be followed; permanent change requires that the script itself be changed.
From the horse's mouth: https://mxlinux.org/migration/ From MX-19 RC1 to MX-19 Final The upgrade will take place automatically through the standard upgrade process. When the process is completed, the “RC1” in the version name will disappear.
"Our policy is that we discourage installing Ubuntu packages on MX Linux as it can (and has) caused problems. However, MX Packagers can examine the components of the ppa to see if all their dependencies appear to be met, to look for anywhere Ubuntu and Debian have different names or locations for the libraries, and hunt for anything systemd related. So it would be prudent to ask them about particular repositories you are thinking of adding".
Ain't the first link I gave you work? It's a direct torrent link to MX-18.2_x64.torrent.
​
https://mxlinux.org/?smd_process_download=1&download_id=2447
​
Just add to your script. Your asking for a direct link to a .torrent and that's what it is.
here you go: https://mxlinux.org/wiki/help-files/help-mx-codecs-installer
Not sure what do you mean for community ISO, however you can find some spins at MX Forum.
https://forum.mxlinux.org/viewforum.php?f=124&sid=8f605c5a3da9cffe27c8a202f29e8036
I made the MX linux .vhd file following https://www.ventoy.net/en/plugin_vtoyboot.html , and it's working great on my different machines ! (UEFI or legacy BIOS ...)
Use Balena Etcher or Ventoy (Ventoy is my personal favorite).
MX Linix has been tested Ventoy, as you can see here: https://www.ventoy.net/en/isolist.html
It's easy to setup from the terminal. Give it a try and see how it goes.
I have the same issue and it appears that it's tied to the the killswitch command. Not sure if this is a bug, or it's meant to work like that.
Every time I start Linux before I connect to NordVPN I set the killswitch to OFF.
Here is the command: nordvpn set killswitch off
After you connect to a desired server you should turn it ON again. So: nordvpn set killswitch on
If you want to change servers turn it off again: nordvpn set killswitch off
Even if you have the spiny dash in Terminal just close the app after you have turned the killswitch off (when off you can connect to a different server). Open it and it should be OFF. You can use the command to check the status : nordvpn status
If that doesn't work use this command: nordvpn set autoconnect off
It appears that when the killswitch is ON it's blocking the other commands and you get the spinning dash. Turning the killswitch OFF and restarting the app should fix the problem.
Same goes with the autoconnect command. Set it off by default and connect manually every time you launch MXLinux.
Edit: Get in the practice to turn OFF both the killswitch and the autoconnect before you shutdown MXLinux. Next time you launch it, you first connect to a server, and only then you turn the killswitch on. After you're done with your work set the killswitch to off, then disconnect from a server, then shutdown your PC.