MX-19.2 KDE Beta 2 Feedback Thread

[asqwerth]

Please @asqwerth, could you put it in the right place? I went to do it, but I got lost in so many threads... HAHAHA

Done. Go here:
viewtopic.php?f=116&t=59393#p587902

[asqwerth]

Do you already have a name for MX-KDE? Just as MX 19 is called "ugly duckling" I suggest that MX-KDE is called "caterpillar"; if the ugly duckling turns into a beautiful swan, the caterpillar turns into a beautiful butterfly!

Think of MX19-KDE as part of the MX19 series.

It is not MX20.

[tony37]

FYI I do have the two checkboxes checked to answer yes to all prompts and to close the updater when complete. It seems that the next testing step is to change those back to unselected, then select one at a time to see which one if any is making the right-click menu appear. I hope there are a few more updates coming over the next few days.

For me the menu always shows up after updating, except when both checkboxes are checked. Strange...

edit: Oops, spoke too soon. I retried it with both checkboxes checked, and now the menu popped up while it was downloading some stuff (while installing). Don't understand anything here.

[Gerson]

Please @asqwerth, could you put it in the right place? I went to do it, but I got lost in so many threads... HAHAHA

Done. Go here:
viewtopic.php?f=116&t=59393#p587902

Thank you very much.

[leslie1017]

MX KDE beta2, systemd enabled
Flatpak cmdline installed steam can't start(it was started correctly right after installed, after reboot, it wont run), here's the error log:

Can you verify that it is only an issue on MX KDE beta2 and not also an issue on MX-19.2 Xfce?

You don't really need to use systemd as your init to use flatpaks and I honestly don't think it is part of the reason the install or starting has issues.
You also don't need install Steam via a flatpak either, it is in the repository and can be installed via MX Package Installer, fcitx can be installed the same way.

If there is a flatpak issue only with the KDE beta2, then it needs looked at, if not then this discussion can continue in the other thread you started.

I just tried boot without systemd enabled and got same issue for steam and fcitx.
I enable systemd for snap applications, now I can see shutter(a screen capture app I use daily, provided only by snappy) not started.
My software install order is flatpak>snap>apt, doing this is expecting consistent app experience. BTW fcitx is installed by apt neither flatpak nor snap.
I don't have another machine for MX-19.2 Xfce, very sorroy that I can't do such kind comparision.

[leslie1017]

MX KDE beta2, systemd enabled
Flatpak cmdline installed steam can't start(it was started correctly right after installed, after reboot, it wont run), here's the error log:

Can you verify that it is only an issue on MX KDE beta2 and not also an issue on MX-19.2 Xfce?

You don't really need to use systemd as your init to use flatpaks and I honestly don't think it is part of the reason the install or starting has issues.
You also don't need install Steam via a flatpak either, it is in the repository and can be installed via MX Package Installer, fcitx can be installed the same way.

If there is a flatpak issue only with the KDE beta2, then it needs looked at, if not then this discussion can continue in the other thread you started.

might need xdg-desktop-portal-kde installed. on Xfce we have xdg-desktop-portal-gtk . flatpaks use the xdg-desktop-portal system for accessing things like home folders, which steam would.

Just installed xdg-desktop-portal-kde, still same issue for steam:

Code: Select all

leslie@leslie-desktop ~/Downloads $ sudo apt install xdg-desktop-portal-kde 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  xdg-desktop-portal-kde
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 94.0 kB of archives.
After this operation, 473 kB of additional disk space will be used.
Get:1 http://mirrors.ustc.edu.cn/debian buster/main amd64 xdg-desktop-portal-kde amd64 5.14.5-1 [94.0 kB]
Fetched 94.0 kB in 0s (312 kB/s)            
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Selecting previously unselected package xdg-desktop-portal-kde.
(Reading database ... 211947 files and directories currently installed.)
Preparing to unpack .../xdg-desktop-portal-kde_5.14.5-1_amd64.deb ...
Unpacking xdg-desktop-portal-kde (5.14.5-1) ...
Setting up xdg-desktop-portal-kde (5.14.5-1) ...
leslie@leslie-desktop ~/Downloads $ 

[SwampRabbit]

I just tried boot without systemd enabled and got same issue for steam and fcitx.
I enable systemd for snap applications, now I can see shutter(a screen capture app I use daily, provided only by snappy) not started.
My software install order is flatpak>snap>apt, doing this is expecting consistent app experience. BTW fcitx is installed by apt neither flatpak nor snap.
I don't have another machine for MX-19.2 Xfce, very sorroy that I can't do such kind comparision.

So your only machine you are running a BETA on?
There is no upgrade path that I am aware of from the beta to final, you're probably going to have to reinstall anyway.

So you are having more issues than just with flatpaks on the KDE Beta2?

You didn't mention needing snap support, but yes you need systemd for snaps.

You're having the following issues?
- Steam flatpak
- fcitx via apt

I just installed Steam flatpak using MX Package Installer on MX-KDE beta2, it installed fine, and opens fine.

fcitx 4.x series with Qt5 front end installed via the MX Package Installer no issues and at least the Input Method - System Settings Module opens... I can't test past this right now.

Now the only difference is I didn't boot with systemd, but I don't think booting with systemd is the issue... it may be. But having just tested both of those, I think the issue may be isolated to your system and not a issue with the Beta or those applications.

[i_ri]

hello everyone
Missing the panel eyes that follow cursor.
treasure the do-nothing app..

mx triangles1 image is so kde!
well ,, with xeyes staring up the side of the triangle, it is.

mxkde5-beta2 has the kde fluidity that i associate with kde.
This is the best kde5 i have trialed since a kubuntu k5 five(?) years ago.

[kangburra]

I have setup fingerprint-gui and it works well except now when I resume the machine the password does not unlock the machine, neither does the fingerprint. I have to enter the password and see it say failed to unlock, then swipe my finger with that password still in the box. It seems excessively secure to require both.

[SwampRabbit]

I have setup fingerprint-gui and it works well except now when I resume the machine the password does not unlock the machine, neither does the fingerprint. I have to enter the password and see it say failed to unlock, then swipe my finger with that password still in the box. It seems excessively secure to require both.

Pretty sure fingerprint-gui is not created by the MX team, so how “excessive“ it’s functionality is is not up to MX really.

You may want to research the application more and see if it is a setting or known issue.

If it’s a bug in the particular version package, and it just needs updated or is missing a dependency to make it work as expected, then that is another topic unrelated to the KDE beta.