MX-19.2 KDE Beta 2 Feedback Thread
Re: MX-19.2 KDE Beta 2 Feedback Thread
That's probably due to sharing the same home directory with other KDE-based distros then. Doing that is never a good idea and leads to strange problems because of configuration files being shared. I've seen it before in regular Xfce MX, when people use a common /home among distros. I just tested it by removing LO from my favorites then logging out and in, and it was still gone.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
-
- Posts: 50
- Joined: Thu Jul 23, 2020 9:16 am
Re: MX-19.2 KDE Beta 2 Feedback Thread
how to fix this? I have to use same home folder, any configuration folder to look at for kde settings?
Re: MX-19.2 KDE Beta 2 Feedback Thread
With you using a pre-used /home with settings and configs from other distros, it's very hard to know if your issues are due to the Beta2 or your pre-existing settings.
I would suggest you make a separate clean install of the Beta2 and see if the issue still arises. Any other feedback should also be based on this new install. This is a Testing thread, for a release that is still in Beta phase.
I would suggest you make a separate clean install of the Beta2 and see if the issue still arises. Any other feedback should also be based on this new install. This is a Testing thread, for a release that is still in Beta phase.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
-
- Posts: 50
- Joined: Thu Jul 23, 2020 9:16 am
Re: MX-19.2 KDE Beta 2 Feedback Thread
My understanding that all these KDE distro (similar plasma version) uses same kde/plasma settings, unless MX KDE has some customization on kde/plasma. A fresh clean installation of MX will have no issue, as some one already tried. I'd like to do more investigation on why MX can read the favourite but cannot delete one, or a method to reset all KDE settings to default, just like a fresh install.
Re: MX-19.2 KDE Beta 2 Feedback Thread
Did you see the problem with using the installer to backup existing home?asqwerth wrote: Tue Jul 28, 2020 1:40 am With you using a pre-used /home with settings and configs from other distros, it's very hard to know if your issues are due to the Beta2 or your pre-existing settings.
I would suggest you make a separate clean install of the Beta2 and see if the issue still arises. Any other feedback should also be based on this new install. This is a Testing thread, for a release that is still in Beta phase.
Re: MX-19.2 KDE Beta 2 Feedback Thread
The installer installs MX Linux. It's not a backup utility.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: MX-19.2 KDE Beta 2 Feedback Thread
what version of plasma is used by your kubuntu and opensuse? KDE/Plasma has pretty active development. It may have changed certain file paths etc for their various settings and configs. I note that the layout of Plasma SYstem Settings is different when you compare Plasma 5.18 to Buster's 5.14.leslie1017 wrote: Tue Jul 28, 2020 2:22 am My understanding that all these KDE distro (similar plasma version) uses same kde/plasma settings, unless MX KDE has some customization on kde/plasma. A fresh clean installation of MX will have no issue, as some one already tried. I'd like to do more investigation on why MX can read the favourite but cannot delete one, or a method to reset all KDE settings to default, just like a fresh install.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX-19.2 KDE Beta 2 Feedback Thread
@ asqwerth: When trying to lower the font size used in 'Application Dashboard' (like it is in newer versions), I remarked they slightly changed the syntax of these things. (I didn't succeed in making the changes I wanted) So imo a totally thankless task of trying to find out what exactly is causing leslie's problem (I'm pretty sure it's a version conflict).
@ leslie1017: Consider using your home from previous distros as a separate data partition (but maybe only useful when you have a multiboot system). So your /home in your new install is on the root partition, but you link to the folders you want to use on the data partition (very easy to do this in Dolphin with split view). Best to add an entry in /etc/fstab to mount the data partition on startup.
Using the same config files for different versions is very likely to lead to problems. I only share the config files for VirtualBox across different distros, but having version 6.0 on one partition vs version 6.1 on another already causes issues.
@ leslie1017: Consider using your home from previous distros as a separate data partition (but maybe only useful when you have a multiboot system). So your /home in your new install is on the root partition, but you link to the folders you want to use on the data partition (very easy to do this in Dolphin with split view). Best to add an entry in /etc/fstab to mount the data partition on startup.
Using the same config files for different versions is very likely to lead to problems. I only share the config files for VirtualBox across different distros, but having version 6.0 on one partition vs version 6.1 on another already causes issues.
Last edited by tony37 on Tue Jul 28, 2020 6:36 am, edited 2 times in total.
Re: MX-19.2 KDE Beta 2 Feedback Thread
So the idea of renaming your home directory is just a suggestion and should not be used? Then why not remove it, it is going to stop people from using MX if features in the installer do not work.
Re: MX-19.2 KDE Beta 2 Feedback Thread
This is just semantics, JayM and kangburra.
When you rename the home directory, it is just to tell the installer not to wipe it but to set it aside under a different name. Meanwhile, the installer will then create a fresh /home for the current installation being done.
Is renaming the old /home "backup"? Yes and no. Yes because you are setting it aside/preserving it for future use. No because often when people think of backup, they are thinking of a new copy being created. Here no new copy of the old partition is made.
When you rename the home directory, it is just to tell the installer not to wipe it but to set it aside under a different name. Meanwhile, the installer will then create a fresh /home for the current installation being done.
Is renaming the old /home "backup"? Yes and no. Yes because you are setting it aside/preserving it for future use. No because often when people think of backup, they are thinking of a new copy being created. Here no new copy of the old partition is made.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400