MX-19.2 KDE Beta 2 Feedback Thread

[SwampRabbit]

That's what happens when thunderstorms at night plus frightened dogs crying means you're sleep-deprived.

I was messing with you about the QSI Jay.

That doesn't sound like a good time with the pups though.

I was in the KDE beta earlier to test those flatpak and other issues, but I didn't update though. But if you and Rich identified it... then I am sure they are tracking it.

[JayM]

I wish I could figure out what's triggering the darn menu so I could suggest a fix instead of making Dolphin or someone have to track it down. I should have pursued that "How to learn Python the hard way" online tutorial/course that I started to do once, but I never seem to get enough time to sit down and concentrate on things like that without interruptions derailing my train of thought.

[richb]

Yes the exact same opening of the MX Updater window happens with me when the updater icon changes from green to wireframe. It is not only JayM. This is not a VB install but a hardware install.

I would post my QSI but at the moment I am running Kubuntu 20.04.1 LTS, KDE Plasma 5.18.5 to check out that KDE version and see what is different from the 5.8 release.

[SwampRabbit]

Yes the exact same opening of the MX Updater window happens with me when the updater icon changes from green to wireframe. It is not only JayM. This is not a VB install but a hardware install.

I would post my QSI but at the moment I am running Kubuntu 20.04.1 LTS, KDE Plasma 5.18.5 to check out that KDE version and see what is different from the 5.8 release.

You get a pass this time on the QSI Rich! I was just kidding with Jay anyway.

From the dev thread, apt-notifier is getting a lot of attention.

[richb]

Yes the exact same opening of the MX Updater window happens with me when the updater icon changes from green to wireframe. It is not only JayM. This is not a VB install but a hardware install.

I would post my QSI but at the moment I am running Kubuntu 20.04.1 LTS, KDE Plasma 5.18.5 to check out that KDE version and see what is different from the 5.8 release.

You get a pass this time on the QSI Rich! I was just kidding with Jay anyway.

From the dev thread, apt-notifier is getting a lot of attention.

It certainly is not being ignored.

[kangburra]

Since coming to MX Linux from whatever I was using before I have used this PPA https://launchpad.net/~fingerprint/+arc ... rprint-gui or at least added the apt file and imported the key. As I say it works properly in XFCE and works for Konsole commands but the lock screen requires multiple entries to get back in.

I will have a look for an MX fingerprint reader, I must admit when I find a way that works I use it until it stops working.

Thanks for the link.

By chance can you provide which version of Ubuntu you install from?

I don't see why we can't package it for our repos from the sources on Launchpad, it may help identify if something on the KDE beta2 is actually causing it.
Although it may be mute since this application is no longer maintained as well and that means fixes to this application won't come.

Several interesting things I noticed:

GNOME users: The package policykit-1-fingerprint-gui replaces GNOME's standard PolicyKit daemon (contained in package policykit-1-gnome) ... KDE SC users: The above instructions for GNOME users apply to you as well

Please note that Fingerprint GUI doesn't work with kdm and kscreensaver because of a bug in these applications

Check /var/log/auth.log for any clues. Fingerprint GUI is set up to run in debugging mode by default.

Does that log seem like it provides anything useful?

I hate to push you off to find another application, but its hard to recommend an application that isn't maintained, and has some known issues already. I'm sure fingerprint readers and applications have been talked about on the forums already.

Maybe dolphin_oracle, fehlix, or Adrian can look at this and potentially figure out why it works for Xfce and not KDE. That doesn't mean there's a fix, but its worth a shot.

I have, as a test, installed KDE Neon, and this also has the same behaviour. So it is a KDE problem and not just an MX Linux problem.
When the RC comes out I will try again and have a look as I am very tempted to give KDE a proper go if MX is behind it. If it is just sddm maybe a workround with the PAM files will solve it, or I could just not lock after resume.
Thanks for looking into it.

[asqwerth]

The login molecule splash (Quark) has reverted back to the standard kde plasma logo splash.

I think it is due to the MX Look and Feel global theme's internal default configs for the things that aren't specifically set. I applied the global theme to test it, and that's where the change happened.

[JayM]

The login molecule splash (Quark) has reverted back to the standard kde plasma logo splash.

I think it is due to the MX Look and Feel global theme's internal default configs for the things that aren't specifically set. I applied the global theme to test it, and that's where the change happened.

I noticed that in Beta 1 too after installing a different Look and Feel. Instead of the nice splash screen I had the boring KDE gears. Apparently, in Plasma the boot splash screein is part of an overall theme rather than being separate like with LightDM.

[tony37]

One thing I noticed now that I installed the beta to hard drive is that /boot/efi is not 'locked', like in any other distro I've seen. Is this intentional? And funnily the 'changed' and 'opened' dates are set to 1/1/1970

[dolphin_oracle]

The login molecule splash (Quark) has reverted back to the standard kde plasma logo splash.

I think it is due to the MX Look and Feel global theme's internal default configs for the things that aren't specifically set. I applied the global theme to test it, and that's where the change happened.

I've messed around with a lot of themes, and haven't seen this.

but it very possible. if a look-and-feel theme doesn't have something defined, then that thing doesn't change. asqwerth educated us on that with the icons.