MX Linux Forum

Is it possible to install KDE on MX?

joany wrote:Is it possible to install KDE on MX?

Yes. Available through the meta-installer.

Would that be package kde-full?

In Beta 2, yes.

Joany: if you decide to try it, we would be very interested in having a careful report of what you do and how it comes out.

TIA

FWIW, I've tried LXDE on MX-14.

The Meta-installer worked perfectly; logging out, changing session, and logging back in left me with a fully functional fairly standard LXDE desktop. There was no wallpaper. Everything I (briefly) tested worked as expected.

RAM usage idle was 130MB; fetching a page in QupZilla peaked as 200MB

This compared with 180MB idle, and 250MB fetching a web page with Xfce.

Chris

That sounds about right: http://wiki.xfce.org/minimum_requirements

Jerry3904 wrote:Joany: if you decide to try it, we would be very interested in having a careful report of what you do and how it comes out.

TIA

I'm going to install MX-14 in VirtualBox later today (maybe tonight) and I'll try installing KDE using the meta-installer. I'll let you know how it turns out.

In the meantime, I see that chrispop99 already had some success in installing KDE.

In light of the moribund status of SM, I'm aiming at moving to MX-14 as my production distro, but I prefer KDE instead of the lighter XFCE. My present box, albeit old, has fairly robust RAM and CPU capabilities and it should handle KDE pretty well.

@ Joany:

It's the lightweight LXDE that I have tried.

Your enquiry has prompted me to try KDE via the Meta-installer; I'm doing it now, and will report later.

Chris

It should work ok, but it will be a 'vanilla' install. You will need to make your own customisations eg wallpaper, icons etc.

Debian also has a kde-standard metapackage in the repos, for those that don't want every single KDE package installed.

I'd uninstall the kde-full or -standard metapackage afterwards, leaving what they installed. The Debian forums are full of posts from users that removed one minor package, and the metapackage went ahead and removed the whole GNOME or KDE environment.

The metapackage installer in MX-14 comes with 3 kde options.

KDE4-full
kde-full
kdm
virtuoso-minimal

KDE4-standard
kde-standard
kdm
virtuoso-minimal

KDE4-lite
kde-plasma-desktop

KDE-Full will include LOADS!

Success!!

anticapitalista wrote:The metapackage installer in MX-14 comes with 3 kde options.

KDE4-full
kde-full
kdm
virtuoso-minimal

KDE4-standard
kde-standard
kdm
virtuoso-minimal

KDE4-lite
kde-plasma-desktop

KDE-Full will include LOADS!

I installed MX 13.98 in VirtualBox and ran the meta-installer. I could not not locate kde-full. Here were my choices under Metapackages > WindowManager:

1. gnome-ultra
2. icewm
3. kde4_lite
4. kde4_standard
5. lxde
6. mate

I chose kde4_standard and ran it. It took about 15 minutes to download and install everything. After rebooting, the log-in menu showed kdm as an option. I chose that option and voilà, I have a fully-functioning KDE desktop running on MX!!

The desktop is bare-bones KDE standard without any of the usual MEPIS flavor, so it needs quite a bit of customization at this point. But I usually customize a new installation to the hilt anyway, so that's not a problem.

It looks like MX-14 with KDE may be a very viable alternative for me in the future.

Ah yes, I removed kde-full from MX-14.

Have fun customising Joany!

...and keep track of your customizations, please--not necessarily the exact choices you make, but the categories. We could make a helpful document for others out of it.

Thanks--and well done!

Just to add that user should be able to run MX-14 live with persistence, install kde, make all the customisations, reboot and install to hard drive. The customisations*should* carry over to install.

My experience mirrors Joany's.

At the start of the install, I was given the option to select a display manager; I chose light-dm.

There was only one desktop. The forward-back mouse buttons worked in a web browser, but not in Dolphin. (That is always the case with KDE, and not too difficult to fix.)

All the usual things I test worked - viewing various graphics file, playing various video files, opening common document types.

The codecs installer worked as expected. I used the meta-installer to add Firefox. I used the Nvidia installer to get the correct video drivers. (A reboot was needed, although not prompted for.)

Ram used at idle was 386MB
With QupZilla fetching a page was 450MB
With Firefox fetching a page was 500MB
(Note: different hardware from LXDE trial)

I'm very impressed; attempts to install different desktops on other distros have usually met with some sort of failure early on.

Chris

anticapitalista wrote:Just to add that user should be able to run MX-14 live with persistence, install kde, make all the customisations, reboot and install to hard drive. The customisations*should* carry over to install.

Time permitting, I will try that at some point.

Chris

I'm very impressed; attempts to install different desktops on other distros have usually met with some sort of failure early on.

Well done, anti!

anticapitalista wrote:Just to add that user should be able to run MX-14 live with persistence, install kde, make all the customisations, reboot and install to hard drive. The customisations*should* carry over to install.

Unless there has been a tweak somewhere, customizations that would be stored in the user's home directory (wallpapers, custom menus, etc...) would have to be copied over to /etc/skel before running the installation routine. customizations stored elsewhere in the file system (say /etc) will carry over. Installed software will also carry over.

At least, that's been my experience with antix.

What version of KDE gets installed?

chrispop99 wrote:@ Joany:

It's the lightweight LXDE that I have tried.

Your enquiry has prompted me to try KDE via the Meta-installer; I'm doing it now, and will report later.

Chris

that's awesome,

i couldn't get it to work about a week ago (dependencies...) went with 64bit antiX 13.2 upped to jessie . kde-standard 4.11.3 which i think i like a little better than the 4.12... with sol...
thanks guys
great tip Stevo!

cavie here, couldn't get it to suspend to ram correctly until yesterday. what's different you might ask? only thing i did different yesterday was to install compiz 'perfect'.

richb wrote:What version of KDE gets installed?

It's probably the 4.8.4 version.

The version in Debian Wheezy.

Current Stable.

Jerry3904 wrote:...and keep track of your customizations, please--not necessarily the exact choices you make, but the categories. We could make a helpful document for others out of it.

Thanks--and well done!

I'll be sure to document everything I do, but I'd like to wait until the MX-14 final comes out. Then I'll install it on the HDD. Right now, MX/KDE is only running in VBox, so I still consider this to be an experimental installation, although I' was so very pleasantly surprised at how easy it was to switch desktops. Nice work, Anti and the MEPIS team!

I anticipate the first thing I'll do is customize the panel, which was very crude OOTB. Then I'll need to install some KDE-centric applications. Warren's MEPIS installed quite a few of these by default, and the kde-standard metapackage also brought over a few, such as Dolphin. Some of the usual cast of characters, like k3b and Kaffeine, are missing, although Dragon, DeadBeef, and Xfburn are there. I was also very surprised to see that LibreOffice was installed by default with KDE. I'm sure there will be quite a few packages I'll want to add, such as some multimedia players and codecs, Firefox, Thunderbird, etc., etc. Fortunately, most everything seems to be available through Synaptic.

Right now, the Kmenu is kind of a mess, but that will be easy enough to fix. I notice there are a some XFCE-centric applications from the original installation that have the same functions as the KDE apps I commonly use, so I'll probably go in and just uninstall those that I have no use for, and that will clean up the Kmenu somewhat.

This is going to be fun, fun, fun!!

EDIT:

BTW, the KDE version that MX-14 installed was V4.8.4-2. Also, our favorite little apt-notifier icon was transferred to the KDE panel automagically!!

A word of caution: In order to edit Kmenu, you have to install the package kmenuedit and launch it from a konsole. I was used to right-clicking on the Kmenu icon in the panel to edit Kmenu, but that doesn't work.

Nice attitude!

I've done a little customization to my MX/KDE test installation. I have a way to go, but it's looking pretty good. Here's a screen shot of what I've got so far:



It's beginning to look quite a bit like my SM 8.5 desktop.

Too girly.

If you already have a MEPIS or other KDE desktop customized the way you want, you can copy the settings from there. I know most are in ~/.kde, some are in .local, and other non-KDE apps are in .config or their own hidden folders. The KDE ones are the most important, of course.

Stevo wrote:If you already have a MEPIS or other KDE desktop customized the way you want, you can copy the settings from there. I know most are in ~/.kde, some are in .local, and other non-KDE apps are in .config or their own hidden folders. The KDE ones are the most important, of course.

That gives me an idea, why don't we use the skel files from MEPIS and make sure when people install KDE will get the customized MEPIS experience? I doubt the config files are too big to put them on CD...

Stevo wrote:If you already have a MEPIS or other KDE desktop customized the way you want, you can copy the settings from there. I know most are in ~/.kde, some are in .local, and other non-KDE apps are in .config or their own hidden folders. The KDE ones are the most important, of course.

I think Joany's still using Mepis 8.5 which used KDE 4.3.x, some of the settings in ~/.kde might not be compatible with the 4.8.4 KDE version in Wheezy.

I like Adrian's idea a lot, though. Could we just use the current stable settings from M12 B2 and describe that somewhere?

We need someone to test it out. The default MEPIS config could also be a deb that gets downloaded with the kde packages via the metapackage installer.

That works, and follows our general model.

Hello, not been on the forum to often in the past, but recently looking at the news on here that MX 14 has been realeased for testing ,got me interested that a new Mepis version is around.

Anyway, I like some would like KDE, so on a VirtualBox install I loaded up MX 14 and from the meta package instaled KDE. Worked flawlessly, Have a KDE version up and running. Like has been said , needs tweaking to customise etc, but everything working so far with no problems. Got to say I am well pleased with the flexibility, will do a hard install for sure when the final version is released.

Nice work to everyone involved.

Pete

Pete_J wrote:Got to say I am well pleased with the flexibility, will do a hard install for sure when the final version is released.

Me too. I haven't been this excited about MEPIS in a long time. I was disappointed that Warren decided to "move on," so to speak, and will always miss MEPIS. But I'm very encouraged by MX and look forward to installing MX-14/KDE as my production OS as soon as the final is released.

Adrian wrote:That gives me an idea, why don't we use the skel files from MEPIS and make sure when people install KDE will get the customized MEPIS experience? I doubt the config files are too big to put them on CD...

anticapitalista wrote:The default MEPIS config could also be a deb that gets downloaded with the kde packages via the metapackage installer.

Yes! Yes! Brilliant! There is the potential for tremendous value added here. Devil's in the details.

Just a poorly-documented trial. I installed KDE_Lite - 59 packages (having previously installed KMyMoney, which brought in 96 packages). Login to the KDE desktop and most things worked OK. I then copied my plasma-desktoprc and plasma-desktop-appletsrc files from my Mepis 12 install (I have them saved separately for quick & dirty configuration if I reinstall).

This gave me something like my M12 desktop, although a number of widgets were ineffective, and it only remained to switch the wallpaper back to Tutbulence. Voila! And it all seems to work. I won't be using it like this, but I may try a serious job when I install Final.

I had a really ugly synaptic interface, so installed the kde gtk engine, and it works great, synaptic looks nice now.

Agree with what has been said, be great if we had the MEPIS tools, they were very good and what also made the distro so appealing.

I hope maybe a MX-14 KDE version could come to light. But if not this hybrid I am running look very promising.

MX does have MEPIS tools (improved) , just not the MEPIS default KDE desktop.

anticapitalista wrote:MX does have MEPIS tools (improved) , just not the MEPIS default KDE desktop.

That's great! As Pete_J said, those make MEPIS special and they are a great help to Linux novices.

Question: Are all of Warren's tools still available? I'm referring to the MEPIS System Tools and the Repair System Boot. I couldn't find that in my MX-14 test installation.

joany wrote:

anticapitalista wrote:MX does have MEPIS tools (improved) , just not the MEPIS default KDE desktop.

That's great! As Pete_J said, those make MEPIS special and they are a great help to Linux novices.

Question: Are all of Warren's tools still available? I'm referring to the MEPIS System Tools and the Repair System Boot. I couldn't find that in my MX-14 test installation.

I don't think Warren ever updated his Boot Repair Tool for grub2 before he quit.

No, he left it out of M11 and M12 betas. He also never worked on muser after about 2009.

MX-14 has completely reworked muser, and added the very handy MX-Flash and MX-Codecs that Warren never had. msystem we replaced with Grub-Customizer and Disk Manager, since there was no need (and no time) to rework it given that two such well-considered tools already existed.

M11 still has the System Assistant for fixing GRUB.

lucky9 wrote:M11 still has the System Assistant for fixing GRUB.

But it is useless at best and dangerous to use in MEPIS12

I have not missed the System Assistant at all. I experienced some problems with it, so I skipped using it.
It's quite easy to repair grub in the MBR (master boot record on bootdisk) or in the PBR (root partition boot record).
The only things you need to be sure of:

1. what is my bootdrive? Probably /dev/sda, but you should know which drive you boot from. 2. what is my root partition? Suppose it is /dev/sda1, but -again- you should know that. In both cases follow up with running update-grub (as root)

Jerry3904 wrote: MX-14 has completely reworked muser, and added the very handy MX-Flash and MX-Codecs that Warren never had.

Very nice, although I notice MX-Flash and MX-Codecs are not installed by default. Legal reasons, perhaps? Also, when I ran MX-Codecs there were errors. Does something else have to be enabled?

EDIT: Never mind. I ran MX-Codecs again, and the installation was successful. Temporary glitch, I guess.

The other thing I notice is that MX User Assistant and MX User Manger both open the same application. Are there supposed to be two different applications, or is the same application shown twice under two different names?

joany are you using latest RC2 version?

joany wrote:

Jerry3904 wrote: MX-14 has completely reworked muser, and added the very handy MX-Flash and MX-Codecs that Warren never had.

Very nice, although I notice MX-Flash and MX-Codecs are not installed by default. Legal reasons, perhaps? Also, when I ran MX-Codecs there were errors. Does something else have to be enabled?

EDIT: Never mind. I ran MX-Codecs again, and the installation was successful. Temporary glitch, I guess.

The other thing I notice is that MX User Assistant and MX User Manger both open the same application. Are there supposed to be two different applications, or is the same application shown twice under two different names?

MX-Flash and MX-Codecs are installed by default in RC2, have you installed RC2?

A while back I think you did a install of either Beta 1 or Beta 2, but just upgrading wouldn't necessarily bring in those apps.

That might also explain why you have both 'MX User Assistant' and 'MX User Manager'. During development the app name changed to 'MX User manager' (installed by the mx-user package) and that's the only one you should see listed in the Whiskermenu of a RC2 install.

kmathern wrote:

joany wrote:

Jerry3904 wrote: MX-14 has completely reworked muser, and added the very handy MX-Flash and MX-Codecs that Warren never had.

Very nice, although I notice MX-Flash and MX-Codecs are not installed by default. Legal reasons, perhaps? Also, when I ran MX-Codecs there were errors. Does something else have to be enabled?

EDIT: Never mind. I ran MX-Codecs again, and the installation was successful. Temporary glitch, I guess.

The other thing I notice is that MX User Assistant and MX User Manger both open the same application. Are there supposed to be two different applications, or is the same application shown twice under two different names?

MX-Flash and MX-Codecs are installed by default in RC2, have you installed RC2?

A while back I think you did a install of either Beta 1 or Beta 2, but just upgrading wouldn't necessarily bring in those apps.

That might also explain why you have both 'MX User Assistant' and 'MX User Manager'. During development the app name changed to 'MX User manager' (installed by the mx-user package) and that's the only one you should see listed in the Whiskermenu of a RC2 install.

I've been running Beta 2 (MX-14_13.98) have upgraded all the upgradeable packages, but I have not done a complete reinstall of RC1 or RC2.

That's great if that's the way you want to do it, Joany, but recognize that doing it that way brings consequences. The distance between Beta 2 and RC1 was pretty substantial, and a great deal happened behind the scenes at every level.

It's finally totally your call how you want to proceed, but you should understand that we will be necessarily focusing our limited resources on supporting Final. Once it is released, all support for the Betas and RCs will end, so people trying to come up from Beta 2 to Final without a clean install will be pretty much on their own, I'm sorry to say.

anticapitalista wrote:

lucky9 wrote:M11 still has the System Assistant for fixing GRUB.

But it is useless at best and dangerous to use in MEPIS12

I simply pointed out that Mepis 11 has the System Assistant. Pertaining to the point previously made that it was a considerable aid to those new to Linux and GRUB. It was certainly a valuable tool for me when I started using Mepis.

And no mention (by me) was made about using it on Mepis 11.9.xx at all. (As I know it's not there. And that Mepis 11.9.xx uses GRUB 2.)

Jerry3904 wrote:That's great if that's the way you want to do it, Joany, but recognize that doing it that way brings consequences. The distance between Beta 2 and RC1 was pretty substantial, and a great deal happened behind the scenes at every level.

It's finally totally your call how you want to proceed, but you should understand that we will be necessarily focusing our limited resources on supporting Final. Once it is released, all support for the Betas and RCs will end, so people trying to come up from Beta 2 to Final without a clean install will be pretty much on their own, I'm sorry to say.

I understand. The Beta 2 was just a test drive on VirtualBox to find my way around MX-14, learn about installing KDE on top of it, and play around with installing GRUB2 on the PBR. I always wait until the final comes out before doing a permanent installation on the HDD. I must say that from what I've seen from the test, it should be a fairly easy installation.

I was bored this morning, so I reinstalled RC2, added KDE-Lite desktop, installed all my main apps and customised the KDE desktop a bit. Everything I've tested works fine, although there are a few missing items. The whole process from live boot to complete desktop took 55 mins and this is the result: Here's a list of what I did, and I had no problems.

Boot Live & install.
Synaptic - reload and install updates (7 packages)
Meta - Install KDE_Lite (149 packages)
Disk-Manager - mount data partitions
Meta - Install Firefox, Thunderbird
Synaptic - Enable VBox & add suldr repos, Reload, Check-Apt-GPG (for suld), Reload
Synaptic - Install VBox 4.3.8
MX-User - Add phil to vboxusers
Synaptic - Install Samsung printer driver
Menu>Printing - Install printer, test page OK
Synaptic - Install KMyMoney (12), Digikam/kipi (27), Quodlibet (4 packages)
Login to KDE desktop, copy M12 desktop settings files to ~/.kde/share/config
Logout/in to new KDE desktop, change wallpaper to Turbulence.

I think this will be my standard for the desktop when Final is out, and I will use xfde on the netbook.

I can easily see this as a Doc or a video.

Seems to me this is a good place for Adrian's trick of producing a list of apps you have installed as a text file (don't remember the command to do that, but somebody will know), then using a terminal to reinstall them as a batch by pasting the file contents behind an apt-get install command.

Jerry3904 wrote:I can easily see this as a Doc or a video.

Seems to me this is a good place for Adrian's trick of producing a list of apps you have installed as a text file (don't remember the command to do that, but somebody will know), then using a terminal to reinstall them as a batch by pasting the file contents behind an apt-get install command.

Maybe we can use apt-clone for that. It's in the repos, and is described as

Script to create state bundles

This package can be used to clone/restore the packages on a apt based
system. It will save/restore the packages, sources.list, keyring and
automatic-installed states. It can also save/restore no longer
downloadable packages using dpkg-repack.

Though you can do the same thing with Synaptic, with File--Save Markings As..., then load that saved file in Synaptic on the new install to reinstall what you had on the original.

So if you have packages in the apt cache, it looks like you can save those also for reinstallation, rather than redownload them. I'm going to look at the home page of the application...

It would be nice to get a list of just what the user has installed manually, seems to me.

Jerry3904 wrote:Seems to me this is a good place for Adrian's trick of producing a list of apps you have installed as a text file (don't remember the command to do that, but somebody will know), then using a terminal to reinstall them as a batch by pasting the file contents behind an apt-get install command.

It's a simple apt-get command that outputs package names to a text file that you can save. Then you just copy/paste the same names into an apt-get install command. I looked for the command recently but couldn't find it to save my azz.

To get the list and create a text file.
To retore to a new installation

Gaer Boy wrote:I was bored this morning, so I reinstalled RC2, added KDE-Lite desktop, installed all my main apps and customised the KDE desktop a bit. Everything I've tested works fine, although there are a few missing items.
(snip)
I think this will be my standard for the desktop when Final is out, and I will use xfde on the netbook.

I have now changed my view on this and I'm fairly certain that I will settle on MX14 on netbook and desktop. On my latest RC2 install, I've added Dolphin, KMyMoney, Digikam & Quodlibet - a total of 130 packages. With Thunderbird and Firefox this gives me more or less what I'm using in Mepis 12 and I have never been much for additional eye candy so there's little else I want from KDE.

The light dawned when I got to wondering whether I could get the Weather Report widget from xfce to work on the KDE desktop. Why the effort? Weather Report and the System Load Monitor suit me better than the KDE equivalents that I'm currently using.

So, MX for me and I'm no longer interested in a KDE version.

Phil

Is there any prospect of a 64-bit version of MX14? With KDE it would almost directly replace/update my 64B version of M11

No.

CaptainKirk wrote:Is there any prospect of a 64-bit version of MX14? With KDE it would almost directly replace/update my 64B version of M11

Okay, I have installed the MX 14 final on my laptop and read through this whole thread to get to the point I could understand how to install KDE. What is the meta- installer? I find it in the synaptic but, how do I get it to install KDE? Do I need install meta antix? Not liking the xfce desk top.

I have done all the updates and rebooted but do not see a "meta-installer". Is it called something else? Thanks

http://www.mepiscommunity.org/doc_mx/mx ... einstaller
You can get kde directly through synaptic if you know exactly what you want. Yesterday I installed a copy of my M11 kde desktop by getting the same packages (in later versions) and copying my settings.
There's a lot of tweaking to do to make it behave and look exactly like in M11, but it can be done.
Henry

Dieselrider wrote:Okay, I have installed the MX 14 final on my laptop and read through this whole thread to get to the point I could understand how to install KDE. What is the meta- installer? I find it in the synaptic but, how do I get it to install KDE? Do I need install meta antix? Not liking the xfce desk top.

I have done all the updates and rebooted but do not see a "meta-installer". Is it called something else? Thanks

In 14.1.1 it has been replaced by MX Package Installer.

If you have MX14 it's called the meta-packageinstaller. It will be in the Accessories. Accessories/meta-packageinstaller/WindowManager (at the bottom, you need to scroll down). Highlight kde4-standard and then click the Install button. Read what joany did on her installing kde thread.

Not in MX-14, first time in MX-14.1.1

lucky9 wrote:If you have MX14 it's called the meta-packageinstaller. It will be in the Accessories. Accessories/meta-packageinstaller/WindowManager (at the bottom, you need to scroll down). Highlight kde4-standard and then click the Install button. Read what joany did on her installing kde thread.

It's hard telling which MX-14 release Dieselrider installed.

If he installed MX-14 final which was released back in March it's called "meta-packageinstaller", if he installed MX-14.1.1 which was released a couple days ago it's called "MX Package Installer".

They both work the same.

@Dieselrider, if you have a hard time finding it just click on the Whiskermenu and search for "installer". The image below shows both, but you only need one or the other. If you're using the original MX14, it would probably be best to install the 'mx-packageinstaller' package. It's what provides the "MX Package Installer" app, and will be maintained going forward.

The 'install-meta-mx' package is what provided the "meta-packageinstaller" app in the original MX-14, but I doubt that it will be maintained.

Do meta-packageinstaller and MX Package Installer do essentially the same things? In other words, do they both support the same meta packages, such as KDE-standard?

joany wrote:Do meta-packageinstaller and MX Package Installer do essentially the same things? In other words, do they both support the same meta packages, such as KDE-standard?

basically yes. However, the newer mx-packageinstaller will not instll kdm.

I install KDE in MX-14.1 and meet with a problem.
This occurs in MX-14.1.1:

http://forum.mepiscommunity.org/viewtopic.php?t=36436

In addition, I use KDE in Japanese.
Therefore I used the terminal:

anticapitalista wrote: basically yes. However, the newer mx-packageinstaller will not instll kdm.

I see ... so what would someone need to do to install a completely functional KDE desktop and get it up and running after rebooting MX-14.1.1?

It will boot into lightdm, won't it? If yes, then once you are logged in you can install kdm and remove lightdm (in that order). Other than that nothing has changed since you did it, just the name of the GUI that you manage extra packages with--same code base for the install commands.

Probably the original. Had downloaded a few weeks back. I did find it though and have it installed. I had 130 some updates after initial install. I have been playing a bit but, the rain has stopped and I am weeks behind in the gardens. So, maybe after dark.

To see a reply of Jerry, I confirmed MX Package Installer.
As a result, I grasped coping of this problem. (delete of package kdm)
We can install KDE in peace.

What a wonderful Mepis/antiX/MX website you have created.

おめでとうございます

My directions were for the version that I figured Dieselrider had installed. Ergo: meta-packageinstaller.
When he updates he might want to check manually MX Package Installer to get the latest version. Afterwards I'd suggest removing the meta-packageinstaller so there isn't any confusion.

Finally have a wee bit of time to shut down and update the os to Mx 14.2.2 on the desktop. Have it downloaded urned, and installed. Looks like everything went alright but, I do not like the desktop on xfce. I have the kde desktop on my laptop. Much better IMHO. However, I cannot remember how I did it. Was reading back through this thread but, I must have missed something. I will look again but, has something changed that is different from before? I have found and used the mx package installer but still have the xfce desktop. What's next? Thanks.


Okay, I went back and re read and found it. I should not have scanned so light.

Check the Docs also. It's there, and may be easier to follow.