MX-19.2 KDE Beta 2 Feedback Thread

[leslie1017]

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?
MX Package Installer(MX Tools->Nvidia driver installer)
Just so we are understanding that QSI is the system showing the issue, but you're booting from a Live USB?
No, I installed MX KDE into a USB disk, which means I boot from a Live USB then installed MX KDE to another USB disk, I think I should not mention this to make confusing

[dolphin_oracle]

you'll want to post the log for the /var/log/ddm.log so we can see what happened. there is a variety of things that can happen, not the least of which is installing the wrong driver, etc... those nvidia laptops with intel/nvidia are tricky and I doubt its actually related to the kde setup.

[SwampRabbit]

you'll want to post the log for the /var/log/ddm.log so we can see what happened. there is a variety of things that can happen, not the least of which is installing the wrong driver, etc... those nvidia laptops with intel/nvidia are tricky and I doubt its actually related to the kde setup.

Their QSI makes me think its a desktop though.

But still concur, I think it is a issue with incorrect installation method/expectation that is causing this.

Just so we are understanding that QSI is the system showing the issue, but you're booting from a Live USB?

No, I installed MX KDE into a USB disk, which means I boot from a Live USB then installed MX KDE to another USB disk, I think I should not mention this to make confusing

Actually that is kinda important to know, it is more confusing to not know the specifics.

I would try to create a fresh Live USB with persistence and install the Nvidia drivers then test the Steam flatpak.

[leslie1017]

Lutris+battle.net crashes on start.
I use apt to install the lutris, then use lutris offical site script installed battle.net. When start the battle.net, the log shows:

Code: Select all

Running /home/leslie/.local/share/lutris/runners/wine/lutris-5.7-8-x86_64/bin/wine /home/leslie/Games/battlenet/drive_c/Program Files (x86)/Battle.net/Battle.net.exe
Initial process has started with pid 11433
Game is considered started.
esync: up and running.
Initial process has exited.
wine: Unhandled page fault on execute access to 00000000 at address 00000000 (thread 0033), starting debugger...
Game is considered exited.
All monitored processes have exited.
Exit with returncode 256

I didn't follow lutris website steps to install nvidia drivers, since it is for Ubuntu based system only. Not sure the steps to enable lutris on MX KDE

[SwampRabbit]

Lutris+battle.net crashes on start.
I use apt to install the lutris, then use lutris offical site script installed battle.net. ... Not sure the steps to enable lutris on MX KDE

Again, I do not believe that your issues are related to the KDE Beta. You need to take these issues to separate threads or we have to ask the Moderators to do it for you.

Lutris runs perfectly fine, I am the one that packages it for MX, and there really are no changes from the source provided by Lutris.
I test it extensively on 4 systems (1 using the KDE beta) before it goes to the repos.

I do not test Battle.net because I do not use it, but you should first read the Lutris wiki on configuring you’re system for Battle.net. Do NOT follow the Lutris guide for drivers.

[kangburra]

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?

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.

[SwampRabbit]

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.

[JayM]

I started my MX-KDE B2 VM this morning and let it sit. Two updates were auto-detected by the updater with no intervention on my part. With both checkboxes unchecked (always answer yes, close terminal when finished) and using the MX Updater view and install upgrades window, not Muon, to install the updates I installed them. After hitting a key to close the terminal window there was a pause during which the icon was still green. At the exact time it changed from green to an empty wireframe image the right-click menu opened by itself. Whatever is triggering that menu to open happens when the icon changes from green to the default. It doesn't matter what icon style I use. It's as though something in apt-notifyer.py is triggering a right mouse-click at the time when the icon gets changed from NewUpdatesIcon to NoUpdatesIcon, but only in Plasma, not in Xfce. My mouse cursor wasn't hovering over the updater's icon at the time though. I looked at the python script but can't make heads or tails out of it. I wonder if it's a compatibility issue between the version of Plasma and Python 3.7?

This is really a minor thing but it bothers me, and I know darned well that there will be forum posts and bug reports about it later. It's little niggles like this that give a poor overall impression of a distro IMO (thinking of reviewers.)

[SwampRabbit]

This is really a minor thing but it bothers me, and I know darned well that there will be forum posts and bug reports about it later. It's little niggles like this that give a poor overall impression of a distro IMO (thinking of reviewers.)

Post your darn QSI Jay! :lipsrsealed:

I am extremely impressed by the amount of effort and success that has been done with all of that for the KDE version. I know they will get it fixed one way or another.
If any reviewers don't like it, they can actually help the team, or go use Kubuntu! (partially joking about the Kubuntu part)

[JayM]

This is really a minor thing but it bothers me, and I know darned well that there will be forum posts and bug reports about it later. It's little niggles like this that give a poor overall impression of a distro IMO (thinking of reviewers.)

Post your darn QSI Jay! :lipsrsealed:

I am extremely impressed by the amount of effort and success that has been done with all of that for the KDE version. I know they will get it fixed one way or another.
If any reviewers don't like it, they can actually help the team, or go use Kubuntu! (partially joking about the Kubuntu part)

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

Code: Select all

System:
  Host: mx-kde-b2 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=3de26e4a-56c2-420f-b19b-18102ba13170 ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta2_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
  Chassis: Oracle Corporation type: 1 serial: <filter> 
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
  date: 12/01/2006 
Battery:
  ID-1: BAT0 charge: 50.0 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
  model: innotek 1 type: Unknown serial: N/A status: Full 
CPU:
  Topology: Triple Core model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx 
  bits: 64 type: MCP arch: Zen family: 17 (23) model-id: 11 (17) stepping: N/A 
  microcode: 6000626 L2 cache: 1536 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 11977 
  Speed: 1996 MHz min/max: N/A Core speeds (MHz): 1: 1996 2: 1996 3: 1996 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.17.0.0 bus ID: 00:02.0 
  chip ID: 15ad:0405 
  Display: x11 server: X.Org 1.20.4 driver: vmware unloaded: fbdev,modesetting,vesa 
  compositor: kwin_x11 resolution: 1884x968~60Hz 
  OpenGL: renderer: SVGA3D; build v: 2.1 Mesa 20.0.7 direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio driver: snd_intel8x0 v: kernel bus ID: 00:05.0 
  chip ID: 8086:2415 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI 
  port: d020 bus ID: 00:03.0 chip ID: 8086:100e 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
  v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:
  Local Storage: total: 25.00 GiB used: 6.63 GiB (26.5%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 25.00 GiB block size: 
  physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 1.0 
  scheme: MBR 
Partition:
  ID-1: / raw size: 22.97 GiB size: 22.48 GiB (97.88%) used: 6.63 GiB (29.5%) 
  fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://deb.debian.org/debian buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://deb.debian.org/debian buster main contrib non-free
  2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ buster main non-free
  2: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 180 Uptime: N/A Memory: 3.85 GiB used: 463.5 MiB (11.8%) Init: SysVinit 
  v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
  running in: quick-system-in inxi: 3.0.36 

FYI richb confirmed earlier that he's seeing the same thing happen on his system.

And I agree with you: the MX KDE betas are more polished and run better than some distros' official release versions.