MX-19.2 KDE Beta 2 Feedback Thread

[Gerson]

Is the color scheme set to KvBrown when you open system settings with sudo?

I had put a user theme and with the command he suggested I put another for root, now with the explanation of @fehlix I understood the problem. Thank you.

[dolphin_oracle]

**edit** wrong post

[dolphin_oracle]

The fcitx keyboard shortcuts are probably just a matter of mapping them in Plasma, but I have no idea how as I'm an Xfce kind of guy. Perhaps this will help? https://www.addictivetips.com/ubuntu-li ... -plasma-5/

I solved the fcitx issue, by installing sogoupinyin:
http://cdn2.ime.sogou.com/dl/index/1571 ... _amd64.deb

I think this package installed some neccessary depencies for fcitx and make it work.

quite possibly. looks like there is some Xsession setup too. Thanks!

[chrispop99]

Using MX User Manager to permit a user to automatically logon does not work. Password entry is still required after making the change.

Chris

Just confirmation that today's update to mx-user fixed this.

Chris

[dolphin_oracle]

Using MX User Manager to permit a user to automatically logon does not work. Password entry is still required after making the change.

Chris

Just confirmation that today's update to mx-user fixed this.

Chris

Thanks for the updated report.

[Gerson]

I installed in a VM. I like that Guest Additions is preinstalled and works OOTB. I still see the issue where when the update finishes and the icon changes from green to clear, the updater's right-click menu opens by itself. I was watching it and the menu opened right when the icon changed colors.

I have experienced the same condition on a regular basis with an install to SSD.

I have installed beta 2 in a solid disk and I don't have that problem, right click to see the updates, I run and when I finish the update it closes itself and the icon disappears until when there are new updates.

[SwampRabbit]

It works perfectly well in the XFCE version, I installed the same way and Konsole works as expected. I am guessing it is a PAM problem but I thought I should report it.

It is still hard to know if this is specific for the KDE Beta2.

We need know how you installed this, I looked and didn't find this "fingerprint-gui" for MX or Debian, so you installed this from source?

I am assuming it is this application:
https://aur.archlinux.org/packages/fingerprint-gui

Note its been flagged as out of date, the developer's website has an expired self-signed cert, blah, blah, blah.
Doesn't look like it has been packaged for Debian or any derivative either.

There could potentially already be an alternative application to use that works though, just don't know what it is.
Doesn't our MX Manual, Wiki or FAQ have something on fingerprint readers?

[SwampRabbit]

I solved the fcitx issue, by installing sogoupinyin:
http://cdn2.ime.sogou.com/dl/index/1571 ... _amd64.deb

I think this package installed some neccessary depencies for fcitx and make it work.

quite possibly. looks like there is some Xsession setup too. Thanks!

Arch users have complained about the fcitx-sogoupinyin package, some were recommending https://gitee.com/laomocode/fcitx-sogouimebs

fcitx-sogouimebs uses qt5, and it is indeed MUCH more stable than the current version of fcitx-sogoupinyin

Can't find sources for either, I'm guessing its on "gitee"?

[Gaer Boy]

I installed in a VM. I like that Guest Additions is preinstalled and works OOTB. I still see the issue where when the update finishes and the icon changes from green to clear, the updater's right-click menu opens by itself. I was watching it and the menu opened right when the icon changed colors.

I have experienced the same condition on a regular basis with an install to SSD.

I have installed beta 2 in a solid disk and I don't have that problem, right click to see the updates, I run and when I finish the update it closes itself and the icon disappears until when there are new updates.

I'm fairly sure that this happened to me today on a standard MX-19.2 xfce installation. An upgrade to mxuser which took about 6 secs - when I closed synaptic, the updater right-click menu appeared. I've not seen this before.

[SwampRabbit]

I found something new, I installed steam on my AMD CPU/GPU working machine, and it opens well, after I got home, I plug my MX system(it's installed on a USB drive) into a machine with interl CPU and NVidia GPU, and I installed Nvidia graphics driver first, then start steam, and see crash.
Just now I reached my working place and plugged MX system in AMD CPU/GPU machine, steam can open correctly again.

How are you installing the Nvidia drivers, via MX Package Installer or the Nvidia Driver Installer application?

Just so we are understanding that QSI is the system showing the issue, but you're booting from a Live USB?
The QSI looks good to me at first glance, so I wonder if issue lies in flip flopping between systems and installing the Nvidia drivers.

I only have one system with an Nvidia GPU to test a Steam flatpak install with the KDE Beta2, so it will be a bit before I can test.

If someone with the KDE Beta2 running on a system with an Nvidia GPU can confirm the Steam flatpak will or will not launch that would be great.

The Steam flatpak installed and launched fine in a VM and on an all AMD system.