MX-21 KDE/plasma beta 2 feedback thread

[davemx]

I don't know how relevant this is, but, adding a few programs, I found that Krita is broken in the MX Package Installer but installs just fine via Synaptic, though MXPI still insists that it's not installed.

[dolphin_oracle]

I don't know how relevant this is, but, adding a few programs, I found that Krita is broken in the MX Package Installer but installs just fine via Synaptic, though MXPI still insists that it's not installed.

probably a missing auxillary package. will investigate thanks.

[uncle mark]

No issues with KDEß1 and even fewer with KDEß2! Mind you, I did strip out plasma-discover and install synaptic and apt-notifier, which I am far happier with! It might be the KDE version of MX, but it's still MX, and I want MX to be MX!!

So if I do this will I get the good old green box in the tray, tied to synaptic? With all the same functionality?

Yes. It runs the text-based updater if there are updates, else it runs synaptic.

Excellent. Works a treat. Thanks. Like you, I like the little things that make MX MX.

[uncle mark]

And another note of satisfaction, although I doubt anyone else would find this useful...

I have an old v31 deb file for Thunderbird I've been dragging along with me since Mepis 11. I have a highly customized TB profile that's invaluable to me, mostly for the newsgroup functionality it provides that doesn't work with later TB versions. I'm always concerned it won't work with new OS versions, but it works just fine on this KDE B2.

[dnkwins]

Hi, do not want to create a new topic. Could please help me with installation of MX-21_KDE_beta2_x64.iso

GPT

sda1 EFI
sda2 BOOT
sda3 lvm on luks
home
root
swap
sda4 ntfs partition

After reboot


How to correct?

[gsm]

Edit: Tried also MX21 XFCE Beta2, booting sysv without problems, at the same hardware configuration and same partition.
Should i retry the KDE version?

SOLVED!
So i gave it a retry and reinstalled the KDE version again. Now it boots (sysv and systemd kernels)! The only difference is that i did not remove the boot device of the live system, before i rebooted into the installed KDE system. So problem is solved by just a retry of the installation from the same iso.

[/quote]

Now Plasma, after a fresh boot, starts up twice when using the sysv kernel en starts up normally using systemd.
Something is broken and Plasma 5.20 to me does not feel as stable as 5.14, as used with MX 19.
First time the desktop is complete and fully operational but without any message the screen goes black again after about 10 seconds and Plasma is restarted with its splash screen.
After the second startup of Plasma the desktop is stable.

[dolphin_oracle]

Edit: Tried also MX21 XFCE Beta2, booting sysv without problems, at the same hardware configuration and same partition.
Should i retry the KDE version?

SOLVED!
So i gave it a retry and reinstalled the KDE version again. Now it boots (sysv and systemd kernels)! The only difference is that i did not remove the boot device of the live system, before i rebooted into the installed KDE system. So problem is solved by just a retry of the installation from the same iso.

Now Plasma, after a fresh boot, starts up twice when using the sysv kernel en starts up normally using systemd.
Something is broken and Plasma 5.20 to me does not feel as stable as 5.14, as used with MX 19.
First time the desktop is complete and fully operational but without any message the screen goes black again after about 10 seconds and Plasma is restarted with its splash screen.
After the second startup of Plasma the desktop is stable.
[/quote]

We do some trickery under sysv to get the logout reboot and shutdown buttons working in sddm. It involves restarting X. Apparently that happens slow enough on your system that you can see it. Usually it’s very fast maybe a second or so.

[ibm450]

hi all
installed mx21 kde B2 onto SSD on the following spec but i get constant blank screens on boot to login screen. it has become a hit and miss to get on to the desktop. i installed the latest nvidia drivers from the mx nvidia installer and no matter what i do, either the system locks up or i get a blank screen upon reboot. so i reverted back to my default ssd with mx 19xx kde and no issues.

i have tried the nomodeset, removed the splasht etc via grub but nothing seems to work?

below is the sys info via mx19xx

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-17.1-liquorix-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: audit=0 intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-5.10.0-17.1-liquorix-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.14.5 tk: Qt 5.11.3 wm: kwin_x11 dm: SDDM Distro: MX-19.4_KDE_x64 patito feo November 11 2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: Hewlett-Packard product: HP Compaq 8000 Elite SFF PC v: N/A serial: <filter> Chassis: type: 4 
           serial: <filter> 
           Mobo: Hewlett-Packard model: 3646h serial: <filter> BIOS: Hewlett-Packard v: 786G7 v01.14 date: 10/14/2015 
CPU:       Topology: Dual Core model: Intel Core2 Duo E8500 bits: 64 type: MCP arch: Penryn family: 6 model-id: 17 (23) 
           stepping: A (10) microcode: A0E L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 bogomips: 12634 
           Speed: 1995 MHz min/max: 1998/3166 MHz Core speeds (MHz): 1: 1995 2: 1995 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ASUSTeK driver: nvidia v: 455.45.01 bus ID: 01:00.0 
           chip ID: 10de:128b 
           Display: x11 server: X.Org 1.20.9 driver: nvidia compositor: kwin_x11 tty: N/A 
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01 direct render: Yes 
Audio:     Device-1: Intel 82801JD/DO HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:3a6e 
           Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 10de:0e0f 
           Sound Server: ALSA v: k5.10.0-17.1-liquorix-amd64 
Network:   Device-1: Intel 82567LM-3 Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel port: 2100 
           bus ID: 00:19.0 chip ID: 8086:10de 
           IF: eth0 state: down mac: <filter> 
           Device-2: ASUSTek USB-N53 802.11abgn Network Adapter [Ralink RT3572] type: USB driver: rt2800usb bus ID: 7-4:3 
           chip ID: 0b05:179d serial: <filter> 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 313.19 GiB (67.2%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB block size: physical: 512 B logical: 512 B 
           speed: 3.0 Gb/s serial: <filter> rev: 2B6Q scheme: MBR 
Partition: ID-1: / raw size: 32.60 GiB size: 31.83 GiB (97.66%) used: 27.62 GiB (86.8%) fs: ext4 dev: /dev/sda5 
           ID-2: swap-1 size: 4.66 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default) 
           dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 42.0 C mobo: N/A gpu: nvidia temp: 48 C 
           Fan Speeds (RPM): N/A 
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/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/microsoft-edge-dev.list 
           1: deb [arch=amd64] http://packages.microsoft.com/repos/edge/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/openshot_developers-ubuntu-ppa-impish.list 
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb http://linux.teamviewer.com/deb/ stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 213 Uptime: 20m Memory: 5.74 GiB used: 1.86 GiB (32.3%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36 

[davemx]

I don't know how relevant this is, but, adding a few programs, I found that Krita is broken in the MX Package Installer but installs just fine via Synaptic, though MXPI still insists that it's not installed.

probably a missing auxillary package. will investigate thanks.

I noticed that MXPI was updated so I checked again. Krita still showed as uninstalled, so I "installed" it. This time, it installed over itself if you know what I mean, and now all's well with it.

[gsm]

Edit: Tried also MX21 XFCE Beta2, booting sysv without problems, at the same hardware configuration and same partition.
Should i retry the KDE version?

SOLVED!
So i gave it a retry and reinstalled the KDE version again. Now it boots (sysv and systemd kernels)! The only difference is that i did not remove the boot device of the live system, before i rebooted into the installed KDE system. So problem is solved by just a retry of the installation from the same iso.

Now Plasma, after a fresh boot, starts up twice when using the sysv kernel en starts up normally using systemd.
Something is broken and Plasma 5.20 to me does not feel as stable as 5.14, as used with MX 19.
First time the desktop is complete and fully operational but without any message the screen goes black again after about 10 seconds and Plasma is restarted with its splash screen.
After the second startup of Plasma the desktop is stable.

We do some trickery under sysv to get the logout reboot and shutdown buttons working in sddm. It involves restarting X. Apparently that happens slow enough on your system that you can see it. Usually it’s very fast maybe a second or so.

It takes about 7 seconds starting the plasma desktop for the second time. Does not feel as a very solid solution, but more as a temporary bypass.