MX-21 KDE/plasma beta 2 feedback thread

[davemx]

@davemx well Disk Manager is being worked, so no reason to beat that horse. I was bringing it up because people continue to be vague when it comes to abandoned python2 and gtk2 apps.

Nite Coder is working it, so really just have to wait, these things take time. I'm sure it will be great and most likely improved a lot since he is working on it.

In the meantime, there are replacements, so....

When Disk Manager becomes available I will install it. I still find it easier to use the KDE Partition Manager. That is just a personal choice.

Great minds and all that!

[asqwerth]

Finally installed this in real-metal on my multiboot machine that has a msdos drive where MBR is located, and a GPT drive where most of my distros and installed. The boot-type indicator at the bottom left of the Live iso's bootloader menu indicated it was booted as UEFI, but thankfully I was able still -- as before -- to install grub bootloader in PBR. That's my default since I use custom grub entries for all my distros.

beta2 Seems to run fine.

I note that although the Plasma Style mx-comfort-breeze-dark is installed, the default panel is Breeze Dark. In other words, the MX and MX-Dark Global THeme did not include that as the Plasma Style. As it's late here and I've only just installed it, I'll look into it tomorrow. To be fair though, the only difference between Breeze Dark and the mx-comfort-breeze dark modification is that the Analogue Clock widget's numerals are in a blue that matches the cursor blue of the mx colour scheme instead of the light blue of Breeze.


Meanwhile, like some others, my preference is for:
1. Synaptic and apt-notifier to be preinstalled and apt-notifier/MX-updater to be the default updater.
2. Discover to be kept for optional update checks of stuff installed from KDE Store. That way there is no inadvertent automatic updating of these items which might break compatibility if a particular item from KDE Store is frequently updated to be compatible with the Plasma versions in rolling distros. Also, I prefer to choose when I update my flatpaks and not as part of a wholesale update.

For members who were wondering if they could keep Discover but not have its notifications pop up whenever there are updates, note that you can't stop it using Notifications from System Settings Manager.

Instead, rIght click on the panel under the SHOW HIDDEN ICONS triangle on the right side. The context menu will show the option to Configure System Tray, Open that and change the "Updates" Entry to "Always Hidden". This option has always been there, even in MX19 KDE.

[SpiritOfTux]

Mx Linux 21 Beta 2: mx-packageinstaller Crash


VirtualBox: install Mx Linux 21 Beta 2, OK
VirtualBox: Upgrade Packages for Mx Linux 21 Beta 2:

Fetched 92.7 MB in 4 s (23.2 MB/s).
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'.
QCommandLineParser: already having an option named "h".
QCommandLineParser: already having an option named "help-all
QCommandLineParser: already having an option named "v"
(Read database ... 312390 files and directories are currently installed).
Preparation for unpacking .../00-elementary-xfce-icon-theme_0.15.2-1_all.deb ...
Unpacking elementary-xfce-icon-theme (0.15.2-1) via (0.15.2-1) ...
Preparation for unpacking .../01-ddm-mx_21.09.01mx21_all.deb ...
Unpacking ddm-mx (21.09.01mx21) over (21.08.04mx21) ...
Preparation for unpacking .../02-firefox_92.0~mozillabinaries-1mx21+1_amd64.deb ...
Unpacking firefox (92.0~mozillabinaries-1mx21+1) over (91.0.2~mozillabinaries-1mx21+1) ...
Preparing to unpack .../03-ghostscript-x_9.53.3~dfsg-7+deb11u1_amd64.deb ...
Unpacking ghostscript-x (9.53.3~dfsg-7+deb11u1) over (9.53.3~dfsg-7) ...
Preparation for unpacking .../04-ghostscript_9.53.3~dfsg-7+deb11u1_amd64.deb ...
Unpacking ghostscript (9.53.3~dfsg-7+deb11u1) over (9.53.3~dfsg-7) ...
Preparation for unpacking .../05-libgs9_9.53.3~dfsg-7+deb11u1_amd64.deb ...
Unpacking libgs9:amd64 (9.53.3~dfsg-7+deb11u1) over (9.53.3~dfsg-7) ...
Preparing to unpack .../06-libgs9-common_9.53.3~dfsg-7+deb11u1_all.deb ...
Unpacking libgs9-common (9.53.3~dfsg-7+deb11u1) over (9.53.3~dfsg-7) ...
Preparation for unpacking .../07-kde-servicemenu-checkhash-installdebs_1.3mx21_all.deb ...
Unpacking kde-servicemenu-checkhash-installdebs (1.3mx21) over (1.3mx19+1) ...
Preparing to unpack .../08-kde-servicemenu-extract-and-compress_1.4.4-3mx21_all.deb ...
Unpacking kde-servicemenu-extract-and-compress (1.4.4-3mx21) over (1.4.4-3mx19+1) ...
Preparation for unpacking .../09-kde-servicemenu-kim4_0.9.5-1mx21+1_all.deb ...
Unpacking kde-servicemenu-kim4 (0.9.5-1mx21+1) over (0.9.5-1~mx19+1) ...
Preparing to unpack .../10-kde-servicemenu-rootactions_2.7.3+p8+git20160617.0159-1mx21_all.deb ...
Unpacking kde-servicemenu-rootactions (2.7.3+p8+git20160617.0159-1mx21) over (2.7.3+p8+git20160617.0159-1mx19+3) ...
Preparing to unpack .../11-ntfs-3g_1%3a2017.3.23AR.3-4+deb11u1_amd64.deb ...
Unpacking ntfs-3g (1:2017.3.23AR.3-4+deb11u1) via (1:2017.3.23AR.3-4) ...
Preparing to unpack .../12-libntfs-3g883_1%3a2017.3.23AR.3-4+deb11u1_amd64.deb ...
Unpacking libntfs-3g883 (1:2017.3.23AR.3-4+deb11u1) via (1:2017.3.23AR.3-4) ...
Preparing to unpack .../13-lo-main-helper_21.09.03mx21_all.deb ...
Unpacking lo-main-helper (21.09.03mx21) over (21.08.5mx21) ...
Preparation for unpacking .../14-mx-gpg-keys_21.09.04_all.deb ...
Unpacking mx-gpg-keys (09/21/04) over (09/19/01) ...
Preparation for unpacking .../15-mx-installer_21.9_amd64.deb ...
Unpacking mx-installer (21.9) via (21.8.10) ...
Preparation for unpacking .../16-mx-packageinstaller-pkglist_21.09.03mx21_all.deb ...
Unpacking mx-packageinstaller-pkglist (21.09.03mx21) over (21.08.5mx21) ...
Preparing to unpack .../17-mx-tweak_21.09.01mx21_amd64.deb ...
Unpacking mx-tweak (21.09.01mx21) over (21.08.03mx21) ...
Preparation for unpacking .../18-mx-welcome-data_21.09.02mx21_all.deb ...
Unpacking mx-welcome-data (21.09.02mx21) via (21.04.02mx21) ...
Preparation for unpacking .../19-papirus-icon-theme_20210802-1~mx21+1_all.deb ...
Unpacking papirus-icon-theme (20210802-1~mx21+1) over (20210201-1) ...

Progress: [ 37%] [#################################.........................................................]

DMESG:

[ 21.043396] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
[ 557.192527] mx-packageinsta[3323]: segfault at 38000020 ip 00007f62c1c97140 sp 00007ffd40e084f0 error 4 in lib
Qt5Core.so.5.15.2[7f62c1bd8000+2fe000]

Translated with www.DeepL.com/Translator (free version)

[asqwerth]

@Adrian @dolphin_oracle

This is with regard to my post above about:

I note that although the Plasma Style mx-comfort-breeze-dark is installed, the default panel is Breeze Dark. In other words, the MX and MX-Dark Global THeme did not include that as the Plasma Style. As it's late here and I've only just installed it, I'll look into it tomorrow. To be fair though, the only difference between Breeze Dark and the mx-comfort-breeze dark modification is that the Analogue Clock widget's numerals are in a blue that matches the cursor blue of the mx colour scheme instead of the light blue of Breeze.

Upon checking the defaults file for both the light and dark MX global themes, I note that the lines for the desktoptheme, ie

Code: Select all

[plasmarc][Theme]
name=mx-comfort-breeze-dark

are included. I then applied the global dark theme (fine), and then reapplied the MX light global theme. This time the mx-comfort-breeze-dark desktoptheme was applied. So it appears that when the beta iso was built, the desktoptheme that was running at that time was Breeze Dark so that is what the user gets when they first log into the desktop.

[dolphin_oracle]

@Adrian @dolphin_oracle

So it appears that when the beta iso was built, the desktoptheme that was running at that time was Breeze Dark so that is what the user gets when they first log into the desktop.

the iso is built in a chroot, and nothing is running, so no, that's not it, but maybe something in a defaults file somewhere. we have updated the Global Theme files a couple of times though. including about 7 days ago, so it may be correct now.

[asqwerth]

Could be. I downloaded the iso quite a few days ago but only installed it yesterday. If I only updated the install after I'd already logged in for the first time, the old default file on the iso might still be breeze dark desktoptheme.

[dolphin_oracle]

Could be. I downloaded the iso quite a few days ago but only installed it yesterday. If I only updated the install after I'd already logged in for the first time, the old default file on the iso might still be breeze dark desktoptheme.

@asqwerth
I found it, I think. default theme was being set after the global theme was apply by a preexisitng plasmarc file in desktop-defaults-mx-kde. got it sync'd now.

[TimothySimon]

I think I found some small problems (or bugs?) in MX-21 KDE plasma beta 2:

Problem 1
The virtual keyboard in the login screen is so large that it overlaps and hides the almost everything in that screen, including the field to enter the password.
(My screen resolution is 1366 x 768)

Problem 2
After taking the virtual keyboard in the Login screen, and then closing the virtual keyboard, we can't see the icon (button) to unhide the characters in the password as we type.
But, clicking on the place it was there, we can really unhides the password.
It is just that the icon (of a crossed out eye) is missing.

Problem 3
Doesn't autoconnect to saved WiFi networks, even though we set priority 99 (the maximum) in KDE's System Settings.
Not that we need to type the password again, but that we need to click on "Connect" again (simply switching on WiFi doesn't connect to any network).
I think this is an issue due to my laziness

Steps to reproduce Problem 2 :
-- Go to the Login screen and click the cursor in the password field.
-- Note (in your memory) where the icon (of a crossed out eye) to unhide our typing is.
-- Take the virtual keyboard and type letters.
-- Close the virtual keyboard.
-- That unhide icon (of a crossed out eye) is gone.
-- Clicking on where it was has the desired effect (of unhiding password characters).
So, I suppose only the icon is missing.


Overall, MX-21 KDE plasma beta 2 was a smooth experience for me (I almost forgot that I was using a beta).
I like using (well enough) betas for my daily use , until it gets stable.
I'm doing that with MX-21 beta 2 too.
(I feel that I can catch more problems that way).

Code: Select all

$ cat /etc/fstab
# Pluggable devices are handled by uDev, they are not in fstab
UUID=<filter> / ext4 noatime 1 1
tmpfs                /tmp tmpfs defaults,rw,nosuid,nodev 0 0

Quick System Info:

Code: Select all

$ inxi -Fxxxrza
System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM Distro: MX-21_KDE_beta2_x64 Wildflower September 4  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: Aspire ES1-533 v: V1.12 serial: <filter> 
           Mobo: Acer model: Stego_AP v: V1.12 serial: <filter> UEFI: Insyde v: 1.12 date: 10/18/2017 
CPU:       Topology: Quad Core model: Intel Pentium N4200 bits: 64 type: MCP arch: Goldmont family: 6 model-id: 5C (92) 
           stepping: 9 microcode: 44 L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8755 
           Speed: 1094 MHz min/max: 800/2500 MHz Core speeds (MHz): 1: 1185 2: 1166 3: 1162 4: 1166 
           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 status: Not affected 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics vendor: Acer Incorporated ALI 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5a84 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 505 (APL 3) v: 4.6 Mesa 21.1.5 direct render: Yes 
Audio:     Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus ID: 00:0e.0 chip ID: 8086:5a98 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI driver: r8169 
           v: kernel port: 1000 bus ID: 01:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: 1000 bus ID: 02:00.0 
           chip ID: 8086:24fb 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 945.83 GiB used: 139.71 GiB (14.8%) 
           ID-1: /dev/sda vendor: Western Digital model: WD10SPZX-21Z10T0 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 1A02 scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Blade size: 14.32 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: 32.00 GiB size: 31.20 GiB (97.50%) used: 9.23 GiB (29.6%) fs: ext4 dev: /dev/sda9 
Sensors:   System Temperatures: cpu: 56.0 C mobo: N/A 
           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 bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://la.mxrepo.com/mx/repo/ bullseye ahs
Info:      Processes: 204 Uptime: 1h 56m Memory: 3.67 GiB used: 1.58 GiB (43.0%) Init: SysVinit v: 2.96 runlevel: 5 default: 5 
           Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36 

EDIT: I could reproduce all of these on a live system too (made with Live USB Maker).

[heywoodidaho]

I have the same WiFi issue. Connect automatically and messing with the numbers do nothing.

I'm on bare metal. Damn solid betta [once again] otherwise.

[uncle mark]

Doesn't autoconnect to saved WiFi networks, even though we set priority 99 (the maximum) in KDE's System Settings.
Not that we need to type the password again, but that we need to click on "Connect" again (simply switching on WiFi doesn't connect to any network).
I think this is an issue due to my laziness

In the network properties for your network, in Advanced, check "All users..."

I had the same issue and this corrected it. Don't know if this will be necessary in Final. It's been brought to the dev's attention.