MX-19.2 KDE Beta 2 Feedback Thread

[asqwerth]

Yes, this system is my daily use one, I can't switch my home folder, need lots of configuration for other software in my home directory

It's very likely all your problems are caused by version conflicts in the config files, so you'll have to find a way to keep the config files you want and get rid of the other ones. But you'll have to reinstall MX KDE anyway as the beta apparently won't be upgraded, so what you can do then (there may be other options) is to transform your current /home folder into a separate data partition and have your /home folder (on the new install) on the same partition as /. Then you link the folders you want to use from your old /home to your new /home (you may have to delete some newly created folders first) and that's about it. And also put your data partition in /etc/fstab, so it is mounted at boot, for example at /mnt/data.

I suspect you're seeing a lot of problems because you have downgraded your Plasma from a newer version to 5.14, and the newer version will have put stuff in the config files that the older version isn't programmed to understand.

Is there any plasma/kde log to look for what error occured?

Does this really belong in this Feedback thread for Beta 2, if you're testing it with a /home from a newer Plasma version? It won't be an accurate picture of how the Beta 2 runs.

Perhaps you should take this side conversation to another thread under MX-Modified subforum.

[leslie1017]

This issue may not caused by reuse /home folder, I have installed MX KDE for about 1 month, and this issue appears today.

[SwampRabbit]

This issue may not caused by reuse /home folder, I have installed MX KDE for about 1 month, and this issue appears today.

You installed the MX KDE “BETA” and are using it as a daily driver though.

Since no one else has reported this issue, it has to be assumed it is localized to your system for some reason.

Unless there is an actual issue with apt-notifier and or an issue with upgrading and keeping the home folder, this probably won’t get determined until RC1 comes out or after.

[tony37]

Is there any plasma/kde log to look for what error occured?

the only plasma log I know of is in /home/user/.xsession-errors
but there are almost no timestamps, except for something like "Xsession: X session started for user at wo aug 5 17:19:10 CEST 2020"

[tony37]

One remark about apt-notifier: when I put it on 'Auto' in the system area settings, it always reverts to 'Shown' after reboot.

[fehlix]

One remark about apt-notifier: when I put it on 'Auto' in the system area settings, it always reverts to 'Shown' after reboot.

I am not sure what is meant by "system area settings"? Which "auto" part of apt-notifier's settings/preferences you are referring to?

[Adrian]

It's in KDE Tray settings:


It's a KDE issue not an app one. However that option works fine for me.

You might want to remove that "shownItems=apt-notifier.py" from ~/.config/plasma-org.kde.plasma.desktop-appletsrc

[fehlix]

It's in KDE Tray settings:
It's a KDE issue not an app one. However that option works fine for me.

You might want to remove that "shownItems=apt-notifier.py" from ~/.config/plasma-org.kde.plasma.desktop-appletsrc

We fixed this KDE/Plasma issue this way:
It's a bit more complex. If set to auto it would not be shown in the system tray, but only sit in the "hidden" area. So when apt-notifer, starts it changes intentionally "auto" to "shown", regardless of the setting in appletrc.
Otherwise the apt-notifier icon would never be shown in the systray, and would stay in the hidden area (that the one you see with the arrow-up. And user would only notice the popups auf availabel updates but not the green icon in the systray.
EDIT: So when apt-notifier starts with the login, any previous setting for shown/auto are forgotten by plasma, it always registers itself as "auto". The fix (within apt-notifier) made the opposite, it always registers itself as shown, when it starts.

[tony37]

You might want to remove that "shownItems=apt-notifier.py" from ~/.config/plasma-org.kde.plasma.desktop-appletsrc

when I looked there, there was a gigantic mass of \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ signs there, never seen such thing before
my file is 8 MB big because of this, I'm adding it in attachment as zip file

[tony37]

It's two times now (today and yesterday) that I couldn't select any file on my desktop (I could when I opened my desktop folder in Dolphin). It was solved when I logged in again. I thought it was maybe because I pasted a file to my desktop from within Dolphin but I can't reproduce it.