MX Linux Forum

Posted: **Sat Sep 04, 2021 11:23 pm**

https://mxlinux.org/blog/mx-21-beta-2-n ... -purposes/

don't forget the Quick-system-info output and the appropriate log files per the blog post when reporting bugs.

Posted: **Sun Sep 05, 2021 6:48 am**

No boot. Immediately after installation and rebooting MX KDE Beta2, boot with default sysv kernel, using Manjaro grub2. Only boot splash screen.

boot.log:

Code: Select all

------------ Sun Sep 05 10:22:45 CEST 2021 ------------
rootMX21: recovering journal
rootMX21: clean, 319311/8445952 files, 2572664/33773744 blocks
INIT: version 2.96 booting
Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.

The above sequence is repeated all the time (recovering journal)
Systemd kernel is ok and boots very fast.

Code: Select all

root@mx:/var/log# /usr/local/bin/inxi -F
System:
  Host: mx Kernel: 5.10.0-8-amd64 x86_64 bits: 64 Console: tty 1 
  Distro: MX-21_KDE_beta2_x64 Wildflower September 4  2021 
Machine:
  Type: Desktop Mobo: ASUSTeK model: Berkeley v: 1.xx serial: X312345678 
  BIOS: American Megatrends v: 5.04 date: 06/23/2007 
CPU:
  Topology: Quad Core model: Intel Core2 Quad bits: 64 type: MCP L2 cache: 4096 KiB 
  Speed: 1813 MHz min/max: 1596/2394 MHz Core speeds (MHz): 1: 1813 2: 1902 3: 1596 
  4: 1596 
Graphics:
  Device-1: AMD Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] driver: radeon 
  v: kernel 
  Display: server: X.Org 1.20.11 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1) 
  v: 3.3 Mesa 21.1.5 
Audio:
  Device-1: Intel 82801I HD Audio driver: snd_hda_intel 
  Sound Server: ALSA v: k5.10.0-8-amd64 
Network:
  Device-1: Intel 82566DC-2 Gigabit Network driver: e1000e 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:1b:fc:c4:c8:32 
Drives:
  Local Storage: total: 3.17 TiB used: 6.99 GiB (0.2%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB 
  ID-2: /dev/sdb vendor: Kingston model: SA400S37240G size: 223.57 GiB 
  ID-3: /dev/sdc vendor: Hitachi model: HDS721010DLE630 size: 931.51 GiB 
  ID-4: /dev/sdd vendor: Western Digital model: WD15EARS-00MVWB0 size: 1.36 TiB 
  ID-5: /dev/sde vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB 
Partition:
  ID-1: / size: 125.76 GiB used: 6.99 GiB (5.6%) fs: ext4 dev: /dev/sde4 
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A gpu: radeon temp: 51 C 
  Fan Speeds (RPM): N/A

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.

Posted: **Sun Sep 05, 2021 6:55 am**

Please read the forum rules which state

System information, terminal commands and their results, log file contents, scripts and similar must be formatted as code by using the </> button in the forum's editor. Do not post these items as plain text or quotations. Doing so disrupts the flow of the thread and is difficult to read.

Then edit your post and change the quote tags to code tags.

Posted: **Sun Sep 05, 2021 6:57 am**

If you already have the beta1 ISO, it is possible to convert it to the beta2 ISO using the zsync protocol, whilst only downloading about 11% of the full size image. You need to use the helper script provided by fehlix here (slightly adapted below)

Code: Select all

#!/bin/bash

# zsync helper script
# for MX-19-beta Testing

# filename MX21kde-zsync-helper.sh


usage()
{
	echo "Usage $0 script"
	echo "$0 download_filename.iso inputfile.iso"
	echo "	Where inputfile.iso is the file you already have that's similar to the one you download"
	echo
	echo "$0 download_filename.iso"
	echo "	This command format will search automatically for the most recent MX*x64.iso file in the current folder"
	exit
}

[[ "$1" == "--help" || "$1" == "-h" ]] && usage


TARGET="$1"
[[ -z "$1" ]] && {
	echo "You need to specify a file name to download. exiting..."
	echo
	usage
}
echo "Downloading \"$1\" file"

grep "x64" <<< "$1" && ARCH="x64" || ARCH="386"

# add available local ISO-sources here - newest first
# check latest ISO-sources are available
SOURCE="$2"

[[ -f "$SOURCE" ]] && echo "Using input file:" "$SOURCE" || {
	[[ "$SOURCE" == "" ]] && echo "Input source not specified, trying to find a useful ISO in current path"
	[[ "$SOURCE" != "" ]] && echo "Input file \"$SOURCE\" not found, trying to find a useful ISO in current path"
	SOURCE=$(find . -iname "MX*$ARCH*.iso" -printf "%T+\t%p\n" | sort -r | head -1 | cut -f2)
	[[ "$SOURCE" != "" ]] && echo "Using "$SOURCE" source file" || {
		echo "Could not found an appropriate input file, exiting..."
		echo
		usage
	}
}

# do we have zsync
command -v zsync >&- || {
	# opps we need to and install zsync
	sudo apt-get update
	sudo apt-get install zsync
}

ZSYNC="${TARGET}".zsync

# get closest sourceforge server for zsync

#DOWNLD=https://sourceforge.net/projects/mx-linux/files/Testing/MX-19/"${ZSYNC}"/download
DOWNLD=https://sourceforge.net/projects/mx-linux/files/Testing/beta2/kde/"${ZSYNC}"/download
SPIDER=$(wget -nv --spider "${DOWNLD}" 2>&1 | grep -Eo https.*iso.zsync | sed 's/https/http/')

[[ -z "$SPIDER" ]] && {
	 echo; echo "Could not find \"$1\" file on SourceForge server, please check the name. Exiting..."
	 echo
	 usage
}

# let's do zsync
[[ -f "${TARGET}" ]] || echo; echo "Executing zsync command"; zsync -i "$SOURCE" "${SPIDER}" || {
	echo
	usage
}

save this as MX21-zsync-helper.sh in the same folder where you have the beta1 iso, then invoke it as follows:

Code: Select all

bash ./MX21-zsync-helper.sh  MX-21_KDE_beta2_x64.iso MX-21_KDE_beta1_x64.iso

the procedure should work for the xfce or fluxbox betas, too, by replacing "kde" in the script above in the "DOWNLD=xyz" line

Posted: **Sun Sep 05, 2021 6:58 am**

Quick info systemd:

Code: Select all

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 7 
           splash init=/lib/systemd/systemd 
           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: Desktop Mobo: ASUSTeK model: Berkeley v: 1.xx serial: <filter> BIOS: American Megatrends v: 5.04 
           date: 06/23/2007 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M185 serial: <filter> charge: 55% (should be ignored) 
           rechargeable: yes status: Discharging 
CPU:       Topology: Quad Core model: Intel Core2 Quad bits: 64 type: MCP arch: Core Merom family: 6 model-id: F (15) 
           stepping: 7 microcode: 6A L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 19151 
           Speed: 1645 MHz min/max: 1596/2394 MHz Core speeds (MHz): 1: 1645 2: 1700 3: 1756 4: 1683 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled 
           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: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] vendor: ASUSTeK 
           driver: radeon v: kernel bus ID: 02:00.0 chip ID: 1002:6779 
           Display: x11 server: X.Org 1.20.11 driver: ati,radeon unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1) v: 3.3 Mesa 21.1.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           chip ID: 8086:293e 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82566DC-2 Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel port: c080 
           bus ID: 00:19.0 chip ID: 8086:294c 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.17 TiB used: 7.01 GiB (0.2%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: physical: 512 B logical: 512 B 
           speed: 3.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
           ID-2: /dev/sdb vendor: Kingston model: SA400S37240G size: 223.57 GiB block size: physical: 512 B logical: 512 B 
           speed: 3.0 Gb/s serial: <filter> rev: 0102 scheme: MBR 
           ID-3: /dev/sdc vendor: Hitachi model: HDS721010DLE630 size: 931.51 GiB block size: physical: 4096 B logical: 512 B 
           speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: A600 scheme: MBR 
           ID-4: /dev/sdd vendor: Western Digital model: WD15EARS-00MVWB0 size: 1.36 TiB block size: physical: 512 B 
           logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: AB51 scheme: MBR 
           ID-5: /dev/sde 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: 3B6Q scheme: MBR 
Partition: ID-1: / raw size: 128.84 GiB size: 125.76 GiB (97.61%) used: 7.01 GiB (5.6%) fs: ext4 dev: /dev/sde4 
Sensors:   System Temperatures: cpu: 52.0 C mobo: N/A gpu: radeon temp: 49 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 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://nl.mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://nl.mxrepo.com/mx/repo/ bullseye ahs
Info:      Processes: 215 Uptime: 27m Memory: 7.77 GiB used: 1.07 GiB (13.8%) Init: systemd v: 247 runlevel: 5 default: 5 
           Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36

Posted: **Sun Sep 05, 2021 7:23 am**

Good morning and congratulations for beta 2.
I have MX KDE, do I need to install beta 2 from scratch or with the updates that have arrived I already have beta 2?

Posted: **Sun Sep 05, 2021 7:55 am**

@Gerson

The problem with not installing from scratch is that your feedback may not reflect what is in beta 2, but in your updated beta1 [installer, other changes in configs and preinstalled packages, etc - see the blog post].

I know beta1 is working well for a lot of people, but without proper feedback on the changes in beta2 that might not be reflected in your current usage of beta 1 e.g. the updated installer and installation process, the devs can't improve the same in MX21.

Since this is a feedback thread, if you are continuing to use beta1, any feedback and issues you report should make clear whether you are using beta 1 (as updated) or 2. And you can try to follow the blog post to make your beta1 more like beta 2, eg remove gtk-nocsd package, install mx-comfort gtk themes, etc.

Posted: **Sun Sep 05, 2021 12:01 pm**

Installed beta2 in VirtualBox, everything went smooth except I only have logout icon in Applications menu. No shutdown or restart.
Icons were present in the previous beta.

Code: Select all

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: 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: Single Core model: Intel Core i7-4720HQ bits: 64 type: MCP arch: Haswell family: 6 model-id: 3C (60) 
           stepping: 3 microcode: N/A L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 5187 
           Speed: 2594 MHz min/max: N/A Core speed (MHz): 1: 2594 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT Host state unknown 
           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: Unknown: Dependent on hypervisor status 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1346x758~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 21.1.5 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel 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: 15.09 GiB used: 6.94 GiB (46.0%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 15.09 GiB block size: physical: 512 B logical: 512 B 
           speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 14.18 GiB size: 13.85 GiB (97.71%) used: 6.94 GiB (50.1%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 896.0 MiB 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 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 https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye main non-free
           2: deb https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye ahs
Info:      Processes: 179 Uptime: 10m Memory: 5.71 GiB used: 708.8 MiB (12.1%) 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

And thumbs up for changing the default Conky appearance! Nice touch

Posted: **Sun Sep 05, 2021 1:18 pm**

Installed successfully to same MBR logical partition which previously held beta1

Code: Select all

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 
  init=/lib/systemd/systemd 
  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: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> 
  Chassis: type: 3 serial: <filter> 
  Mobo: Gigabyte model: B75M-D3H serial: <filter> 
  BIOS: American Megatrends v: F15 date: 10/23/2013 
CPU:
  Topology: Quad Core model: Intel Core i5-3470 bits: 64 type: MCP 
  arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 21 
  L2 cache: 6144 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 25542 
  Speed: 1914 MHz min/max: 1600/3600 MHz Core speeds (MHz): 1: 1914 
  2: 1848 3: 1829 4: 1903 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
  Type: mds mitigation: Clear CPU buffers; SMT disabled 
  Type: meltdown mitigation: PTI 
  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 generic retpoline, IBPB: 
  conditional, IBRS_FW, STIBP: disabled, RSB filling 
  Type: srbds status: Vulnerable: No microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics 
  vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:0152 
  Display: x11 server: X.Org 1.20.11 driver: modesetting 
  unloaded: fbdev,vesa compositor: kwin_x11 resolution: 1680x1050~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 2500 (IVB GT1) 
  v: 4.2 Mesa 21.1.5 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:1e20 
  Sound Server: ALSA v: k5.10.0-8-amd64 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: e000 bus ID: 02:00.0 
  chip ID: 10ec:8168 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.82 TiB used: 8.75 GiB (0.5%) 
  ID-1: /dev/sda vendor: Toshiba model: DT01ABA200 size: 1.82 TiB 
  block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s 
  rotation: 5700 rpm serial: <filter> rev: ABB0 scheme: MBR 
Partition:
  ID-1: / raw size: 17.43 GiB size: 16.99 GiB (97.47%) 
  used: 8.75 GiB (51.5%) fs: ext4 dev: /dev/sda18 
  ID-2: swap-1 size: 4.05 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) 
  dev: /dev/sda9 
Sensors:
  System Temperatures: cpu: 37.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://mirror.tiguinet.net/mx/packages/mx/repo/ bullseye main non-free
  2: deb http://mirror.tiguinet.net/mx/packages/mx/repo/ bullseye ahs
Info:
  Processes: 212 Uptime: 2m Memory: 7.65 GiB used: 969.4 MiB (12.4%) 
  Init: systemd v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 
  alt: 10 Shell: quick-system-in running in: quick-system-in 
  inxi: 3.0.36

Unfortunately still exhibits the same two small glitches i mentioned before:
- installing grub to pbr does not default to the correct partition
- booting in systemd mode complains about missing /etc/machine-id (another user suggested a work-around in the beta1 thread)

There also seems to be something odd with "mx date & time/network time": at first it did not work but then it did after i adjusted the time manually

Posted: **Sun Sep 05, 2021 1:46 pm**

MX 21 KDE beta 2 is already installed, in 11 minutes it did it, everything from zero including the /home, then came 3 updates and then to customize it. I have no crashes and everything installs beautifully.

Posted: **Sun Sep 05, 2021 2:19 pm**

markol wrote: Sun Sep 05, 2021 12:01 pm Installed beta2 in VirtualBox, everything went smooth except I only have logout icon in Applications menu. No shutdown or restart.
Icons were present in the previous beta.

Switching from Applications menu to alternative (I tried Launcher and Dashboard) and then back fixes this issue

Posted: **Sun Sep 05, 2021 2:32 pm**

markol wrote: Sun Sep 05, 2021 12:01 pm Installed beta2 in VirtualBox, everything went smooth except I only have logout icon in Applications menu. No shutdown or restart.
Icons were present in the previous beta.

I had the same anomaly in B1. Am installing B2 as we speak to see if that (and a couple other niggles) had changed.

Posted: **Sun Sep 05, 2021 3:16 pm**

My B1 had three issues:

-- Dolphin crashing -- that's fixed
-- Only had logout button in menu -- that's fixed
-- Wifi did not connect automagically on bootup -- that's half fixed, but I have found the full fix

After first installing and setting up the network connection, on subsequent boots I still had to manually connect to my wifi network, but just had to bring it up and click Connect. I did not have to re-enter the password. In B1, I had to re-enter the password as well.

However, once I went into the configuration for that network and ticked "All users..." it fully connects automagically. This is with a single user account and with the one user having permission to use that network.

Posted: **Sun Sep 05, 2021 3:37 pm**

guvcview is still installed.

Chris

Posted: **Sun Sep 05, 2021 4:09 pm**

chrispop99 wrote: Sun Sep 05, 2021 3:37 pm guvcview is still installed.

Chris

Should I remove it?

We have Webcamoid instead and guvcview has been removed from Xfce version.

Chris

Posted: **Sun Sep 05, 2021 4:49 pm**

baldyeti wrote: Sun Sep 05, 2021 1:18 pm - booting in systemd mode complains about missing /etc/machine-id (another user suggested a work-around in the beta1 thread)

It should be fixed in the new installer version that will come at some point through the repo (so new Beta or RC should have this fixed)

Posted: **Sun Sep 05, 2021 5:32 pm**

Adrian wrote: Sun Sep 05, 2021 4:49 pm It should be fixed in the new installer version that will come at some point through the repo (so new Beta or RC should have this fixed)

So another Beta or RC is in the offing? Good to know. I don't want to get too heavily invested in an install that I'll end up discarding.

Posted: **Sun Sep 05, 2021 5:38 pm**

There were few fixes between B1 and B2, I think they will be even less for the next build so I'm pretty sure it's going to be a Release Candidate. Technically, if there are no major problems with the RC that should be renamed "Final" or "MX-21" Release, so probably not even needed to re-release, it maybe only to change the version strings -- personally I think a RC1 should not even have "RC" listed anywhere so once is considered "OK" we can just say "This is the release"

Posted: **Sun Sep 05, 2021 6:47 pm**

Adrian wrote: Sun Sep 05, 2021 5:38 pm There were few fixes between B1 and B2, I think they will be even less for the next build so I'm pretty sure it's going to be a Release Candidate. Technically, if there are no major problems with the RC that should be renamed "Final" or "MX-21" Release, so probably not even needed to re-release, it maybe only to change the version strings -- personally I think a RC1 should not even have "RC" listed anywhere so once is considered "OK" we can just say "This is the release"

Fair enough. This is an install on a test bed laptop that only gets used on occasion, so I'm not concerned one way or the other.

On a separate note, is the consensus to stick with Discover as the updater? Since I'm old and cranky and set in my ways my preference is using the MX notifier tied to synaptic, but it's not a deal breaker by any means.

Posted: **Sun Sep 05, 2021 7:35 pm**

Minimize, maximize and close icons on Firefox still an issue.
They appear as expected with Breeze Dark.

Fail to appear (or slightly) with MX global themes.

Posted: **Sun Sep 05, 2021 7:50 pm**

danielson wrote: Sun Sep 05, 2021 7:35 pm Minimize, maximize and close icons on Firefox still an issue.
They appear as expected with Breeze Dark.

Fail to appear (or slightly) with MX global themes.

Thanks I think I found the issue

Posted: **Sun Sep 05, 2021 9:01 pm**

Just another comment... I normally don't like bright or colorful or flashy or busy wallpapers and rarely like photographs... but the default wallpaper for KDE B2 is gorgeous. I might even keep it. :-)

Obligatory:

Code: Select all

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 5250 v: V1.01 
  serial: <filter> 
  Mobo: Acer model: Aspire 5250 v: V1.01 serial: <filter> BIOS: Acer 
  v: 1.01 date: 04/21/2011 
Battery:
  ID-1: BAT1 charge: 48.1 Wh condition: 48.1/47.5 Wh (101%) 
  volts: 12.5/10.8 model: Panasonic AS10D51 type: Li-ion 
  serial: <filter> status: Full 
  Device-1: hidpp_battery_0 model: Logitech M215 serial: <filter> 
  charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:
  Topology: Dual Core model: AMD C-50 bits: 64 type: MCP arch: Bobcat 
  family: 14 (20) model-id: 1 stepping: N/A microcode: 5000029 
  L2 cache: 512 KiB 
  flags: lm nx pae sse sse2 sse3 sse4a ssse3 svm bogomips: 3989 
  Speed: 820 MHz min/max: 800/1000 MHz Core speeds (MHz): 1: 887 2: 814 
  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: Vulnerable 
  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: AMD Wrestler [Radeon HD 6250] vendor: Acer Incorporated ALI 
  driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:9804 
  Display: x11 server: X.Org 1.20.11 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD PALM (DRM 2.50.0 / 5.10.0-8-amd64 LLVM 11.0.1) 
  v: 3.3 Mesa 21.1.5 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Acer Incorporated ALI 
  driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Sound Server: ALSA v: k5.10.0-8-amd64 
Network:
  Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet 
  vendor: Acer Incorporated ALI driver: atl1c v: kernel port: 2000 
  bus ID: 06:00.0 chip ID: 1969:2062 
  IF: eth0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter 
  vendor: Lite-On driver: ath9k v: kernel port: 2000 bus ID: 07:00.0 
  chip ID: 168c:002b 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 111.79 GiB used: 8.32 GiB (7.4%) 
  ID-1: /dev/sda vendor: Kingston model: SV300S37A120G size: 111.79 GiB 
  block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
  serial: <filter> rev: BBF0 scheme: MBR 
Partition:
  ID-1: / raw size: 105.93 GiB size: 103.70 GiB (97.90%) 
  used: 8.32 GiB (8.0%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 5.86 GiB used: 1.8 MiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) 
  dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 66.6 C mobo: N/A gpu: radeon temp: 66 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 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/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/mx.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Info:
  Processes: 173 Uptime: 5h 51m Memory: 3.57 GiB used: 1.37 GiB (38.3%) 
  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

Posted: **Sun Sep 05, 2021 9:19 pm**

@dolphin_oracle - and thank you for this new beta release!
Previous one was too hard for me.
Hopefully, this beta will be less of a challenge.

@uncle mark - wallpaper is a definite keeper.
Trying to find a conky that blends in well with it can be a challenge though.

Posted: **Sun Sep 05, 2021 10:24 pm**

danielson wrote: Sun Sep 05, 2021 9:19 pm @uncle mark - wallpaper is a definite keeper.
Trying to find a conky that blends in well with it can be a challenge though.

Isn't that what Conky Toggle [off] is for?

Posted: **Mon Sep 06, 2021 4:55 am**

Two problems:
1) Downloaded new global themes take a long time to be installed and don't display icons correctly after apply.
After a complete re installation of MX-21 KDE Beta 2, it seemed to be ok.
Maybe things got corrupted, when i closed the global theme installation windows to early, before all themes had been installed, or i changed to a new theme, while other themes still being installed.
2) At the taskbar the widget for the virtual desktops is initially not displaying the desktop numbers correctly, after clicking with the right mouse button and then adding a desktop. The desktop numbers are shifted downwards or not aligned correctly. This can be avoided by increasing the taskbar height to 40 or more. After a reboot the numbers are placed at the correct position again.

Posted: **Mon Sep 06, 2021 8:58 am**

Took at least 2 minutes to install a new global theme here.

Firefox minimize, maximize and close icons were just fine this a.m. until after playing around with a new global theme.
Maybe a reboot will fix the looks?

Workspace icon no.1 gives me the impression of being of 2:
https://imgur.com/YREfx6U

- - - - -

@uncle mark trying to match a conky like a tie with a shirt is sometimes a bit of a challenge.

Posted: **Mon Sep 06, 2021 9:04 am**

danielson wrote: Mon Sep 06, 2021 8:58 am Took at least 2 minutes to install a new global theme here.

Firefox minimize, maximize and close icons were just fine this a.m. until after playing around with a new global theme.
Maybe a reboot will fix the looks?

Workspace icon no.1 gives me the impression of being of 2:
https://imgur.com/YREfx6U

- - - - -

@uncle mark trying to match a conky like a tie with a shirt is sometimes a bit of a challenge.

Global theme changes most everything theme wise. To get minimize, maximize and close icons back use Application Style>Window decorations.

Posted: **Mon Sep 06, 2021 9:17 am**

if the global theme does not define a kwin theme, or if the theme it defines is missing, you'll get missing icons in gtk3 apps like firefox. I think Qt apps will default back to breeze.

Posted: **Mon Sep 06, 2021 9:24 am**

dolphin_oracle wrote: Mon Sep 06, 2021 9:17 am if the global theme does not define a kwin theme, or if the theme it defines is missing, you'll get missing icons in gtk3 apps like firefox. I think Qt apps will default back to breeze.

Is this what got Dominic Hayes frustrated?

"I’m writing this to announce a change that’ll be hitting Feren OS next year, a significant change at that. I’m writing this also because I, Dominic, am frustrated — frustrated with the situation with GTK+ being janky and thus having broken theming functionality (of whom they blame themes themselves for) despite Qt doing all of that, even with custom/complex controls, just fine, and frustrated about users not getting to know it’s not all sunshine and rainbows when it comes to theming in GTK+, much as many will try to make everyone else think it is.
I could also mention how some GTK+ developers even go out calling stylesheets out for issues, that could just be bug reported, to further incriminate ‘themes’ in GTK+ instead of adding a proper theme API to fix all that, but… that’d be a discussion for elsewhere.
I hope you’re happy, said GTK+ developers, with what’s being announced below, and with no further ado:
There is no future for the Feren OS GTK+ theme beyond GTK+ 3
I’ve been tossing this idea around for a while now, and honestly with the GTK+ theme situation just getting worse and worse now I can confidently make this decision: Feren OS’s GTK theme will NOT be developed for GTK+ 4 and beyond.
There, honestly, just is no future for it, nor is there future for any theme really outside of Adwaita if GTK+ keeps going the direction it is going nowadays..."

https://medium.com/feren-os/the-future- ... 051a64e6de

Posted: **Mon Sep 06, 2021 9:30 am**

Nah, I think we is upset over gtk4 supposedly more limited theming avenues.

Posted: **Mon Sep 06, 2021 9:47 am**

@richb - tried, but only reboot fixed it.

Odd thing, switching from Breeze to MX-Dark made the no.1 workspace icon split up again.
It was just fine (single box) at reboot.

Posted: **Mon Sep 06, 2021 10:18 am**

Not sure if this feedback thread is only for pointing out issues but I wanted to say that I am having none at all..

I installed the KDE Beta 2 on a small partition on a laptop that i swapped with my daughter ... apparently it is not good enough for her and gets too hot to play all her windows games...

it is a dell inspiron 7000 that i hadn't previously used with MX linux and i am delighted with it .... the touch screen works (not that i especially need it) , i have installed all of my usual apps and themed it as usual with latte dock and other tweaks .... it is lightning quick on this machine and boots in no time at all

https://postimg.cc/JtXBh4Ys

here is the QSI inc case it is of any use

Code: Select all

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 info: latte-dock 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: Dell product: Inspiron 7348 v: A08 
  serial: <filter> Chassis: type: 10 v: A08 serial: <filter> 
  Mobo: Dell model: 067RT2 v: A00 serial: <filter> UEFI: Dell v: A08 
  date: 11/13/2015 
Battery:
  ID-1: BAT0 charge: 32.0 Wh condition: 32.0/43.8 Wh (73%) 
  volts: 12.5/11.1 model: LGC-LGC3.95 DELL 0WF284CR type: Li-ion 
  serial: <filter> status: Full 
CPU:
  Topology: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP 
  arch: Broadwell family: 6 model-id: 3D (61) stepping: 4 microcode: 2F 
  L2 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 19153 
  Speed: 1964 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 1964 
  2: 2044 3: 2001 4: 2007 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, 
  SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  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 generic retpoline, IBPB: 
  conditional, IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:1616 
  Display: x11 server: X.Org 1.20.11 driver: modesetting 
  unloaded: fbdev,vesa compositor: kwin_x11 resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) 
  v: 4.6 Mesa 21.1.5 direct render: Yes 
Audio:
  Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel 
  v: kernel bus ID: 00:03.0 chip ID: 8086:160c 
  Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:9ca0 
  Sound Server: ALSA v: k5.10.0-8-amd64 
Network:
  Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel port: 3040 
  bus ID: 01:00.0 chip ID: 8086:095a 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 238.47 GiB used: 8.15 GiB (3.4%) 
  ID-1: /dev/sda vendor: SanDisk model: SD9TB8W256G1001 size: 238.47 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 6101 scheme: GPT 
Partition:
  ID-1: / raw size: 59.57 GiB size: 58.33 GiB (97.92%) 
  used: 8.15 GiB (14.0%) fs: ext4 dev: /dev/sda4 
Sensors:
  System Temperatures: cpu: 61.0 C mobo: 48.0 C sodimm: 37.0 C 
  Fan Speeds (RPM): cpu: 0 
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 https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye main non-free
  2: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye ahs
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
  1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 212 Uptime: 17m Memory: 7.69 GiB used: 1.47 GiB (19.1%) 
  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

Posted: **Mon Sep 06, 2021 10:45 am**

@junoluna
Positive feedback is as welcome as problem feedback. Except for odd theming issues, my experience is the same as yours with a desktop computer that I built using an AMD A8-7600 Radeon R7 processor. My impression is that it is more responsive than MX 19.4 which is quite fast as well.

I am considering replacing MX 19.4 installed on old my Acer Inspiron laptop, i5 processor, when MX 21 goes final. Although MX 19.4 runs very well on it.

Posted: **Mon Sep 06, 2021 10:48 am**

danielson wrote: Mon Sep 06, 2021 8:58 am Took at least 2 minutes to install a new global theme here.

Firefox minimize, maximize and close icons were just fine this a.m. until after playing around with a new global theme.
Maybe a reboot will fix the looks?

Workspace icon no.1 gives me the impression of being of 2:
https://imgur.com/YREfx6U

- - - - -

Issue 1: which global theme did you install and was it from KDE Store?

Also, if you install a global theme, you need also to install all the items it requires and specifies in its config file, eg the relevant plasma style/desktop theme, colour scheme, kvantum theme (if the global theme uses kvantum theme instead of a "true" qt widget style like Breeze or Breeze Dark), icon set, aurorae theme (window decoration). The relevant web page in KDE store for the global theme will usually list all the individual items specified in the global theme.

Issue 2: your screenshot is not showing a split workspace 1. The smaller rectangle within workspace 1 icon is the indicator of the opened window on your workspace 1 desktop. It will show no rectangle at bootup because no window is opened on your desktop at that point. Once you open your settings manager to change themes and appearance, you will have a window on the desktop.

Posted: **Mon Sep 06, 2021 1:11 pm**

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!!

One thing regarding the MX Package Installer. I wonder whether more packages suitable to KDE (example, KMyMoney, DigiKam and Knights) could be added to its list, or even if there could be two versions, one for KDE.

A couple of years back, I didn't think I'd ever go back to KDE, and I was never going to try the KDE version of MX, but now the KDE team have improved it a lot, while XFCE doesn't seem to know whether it's Arthur or Martha with its mixture of GTK3/CSD and old-style apps, though I appreciate the MX team's brave attempt to try to make the two look broadly similar.

Posted: **Mon Sep 06, 2021 3:51 pm**

If I install beta2 on my computer and start using it - will I have to completely reinstall it later when the official release is out?

Posted: **Mon Sep 06, 2021 3:55 pm**

markol wrote: Mon Sep 06, 2021 3:51 pm If I install beta2 on my computer and start using it - will I have to completely reinstall it later when the official release is out?

Yes.

The only test version that you would normally be able to update to Final is the Release Candidate.

Chris

Posted: **Mon Sep 06, 2021 4:10 pm**

chrispop99 wrote: Mon Sep 06, 2021 3:55 pm
markol wrote: Mon Sep 06, 2021 3:51 pm If I install beta2 on my computer and start using it - will I have to completely reinstall it later when the official release is out?
Yes.

The only test version that you would normally be able to update to Final is the Release Candidate.

Chris

Thank you

Posted: **Mon Sep 06, 2021 4:28 pm**

davemx wrote: Mon Sep 06, 2021 1:11 pm 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 happer 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?

Posted: **Mon Sep 06, 2021 7:12 pm**

uncle mark wrote: Mon Sep 06, 2021 4:28 pm
davemx wrote: Mon Sep 06, 2021 1:11 pm 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.

Posted: **Mon Sep 06, 2021 7:17 pm**

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.

Posted: **Mon Sep 06, 2021 7:57 pm**

davemx wrote: Mon Sep 06, 2021 7:17 pm 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.

Posted: **Mon Sep 06, 2021 8:04 pm**

davemx wrote: Mon Sep 06, 2021 7:12 pm
uncle mark wrote: Mon Sep 06, 2021 4:28 pm
davemx wrote: Mon Sep 06, 2021 1:11 pm 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.

Posted: **Mon Sep 06, 2021 9:22 pm**

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.

Posted: **Mon Sep 06, 2021 11:27 pm**

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?

Posted: **Tue Sep 07, 2021 7:01 am**

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.

Posted: **Tue Sep 07, 2021 7:12 am**

gsm wrote: Tue Sep 07, 2021 7:01 am
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.

Posted: **Tue Sep 07, 2021 8:07 am**

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

Posted: **Tue Sep 07, 2021 10:24 am**

dolphin_oracle wrote: Mon Sep 06, 2021 7:57 pm
davemx wrote: Mon Sep 06, 2021 7:17 pm 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.

Posted: **Tue Sep 07, 2021 10:36 am**

dolphin_oracle wrote: Tue Sep 07, 2021 7:12 am
gsm wrote: Tue Sep 07, 2021 7:01 am
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.

Posted: **Tue Sep 07, 2021 1:13 pm**

richb wrote: Mon Sep 06, 2021 10:45 am I am considering replacing MX 19.4 installed on old my Acer Inspiron laptop, i5 processor, when MX 21 goes final. Although MX 19.4 runs very well on it.

The problem I have with MX 21 is not with the O.S. but with some programs made in Python that work fine in MX 19.4, but can no longer be installed in MX 21. I will have to consider whether or not to switch.

Posted: **Tue Sep 07, 2021 1:21 pm**

Gerson wrote: Tue Sep 07, 2021 1:13 pm
richb wrote: Mon Sep 06, 2021 10:45 am I am considering replacing MX 19.4 installed on old my Acer Inspiron laptop, i5 processor, when MX 21 goes final. Although MX 19.4 runs very well on it.
The problem I have with MX 21 is not with the O.S. but with some programs made in Python that work fine in MX 19.4, but can no longer be installed in MX 21. I will have to consider whether or not to switch.

python2 is going the way of the dodo.

Posted: **Tue Sep 07, 2021 1:34 pm**

Gerson wrote: Tue Sep 07, 2021 1:13 pm The problem I have with MX 21 is not with the O.S. but with some programs made in Python that work fine in MX 19.4, but can no longer be installed in MX 21. I will have to consider whether or not to switch.

dolphin_oracle is absolutely right, this shouldn't be a surprise at this point as its a long time coming.

And we need to know which specific applications you're referring to in order to even attempt to address the issue.

Many python2 applications that their developers have migrated to python3 are already in the MX Repos, the ones that aren't have been abandoned by their developers, and will remain that way until someone forks and updates them.

The real solution is to know which applications are an issue and fix that problem, because sooner or later MX-19 won't be supported, and python2 isn't coming back.

Posted: **Wed Sep 08, 2021 6:09 pm**

dnkwins wrote: Mon Sep 06, 2021 11:27 pm 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?

After some research I found that to run system in my case I need forcibly decrypt luks as follows
cryptsetup open /dev/sda3 any
exit
After that it starts, but it is fanny that it not gives splash to type pswd while boot.

I was need to update following files to boot normally

/etc/crypt-initramfs/conf-hook
CRYPTSETUP=y

/etc/crypttab
any /dev/sda3 none luks,initramfs

Then update initramfs
update-initramfs -c -k all

That's all folks.

Posted: **Thu Sep 09, 2021 8:43 am**

Hi,
I wasn't able to manually modify Date & Time, nor select automatic date and time. For a reason, the "Apply" button was 'locked', despite the fact that the logged user is Administrator.
Never happened before with another Linux Distro.
BTW, MX KDE was a pleasant surprise.

Posted: **Thu Sep 09, 2021 10:24 am**

hotchilli wrote: Thu Sep 09, 2021 8:43 am Hi,
I wasn't able to manually modify Date & Time, nor select automatic date and time. For a reason, the "Apply" button was 'locked', despite the fact that the logged user is Administrator.
Never happened before with another Linux Distro.
BTW, MX KDE was a pleasant surprise.

Did you use the date and time tool in MX Tools?

Posted: **Thu Sep 09, 2021 12:09 pm**

SwampRabbit wrote: Tue Sep 07, 2021 1:34 pm
Gerson wrote: Tue Sep 07, 2021 1:13 pm The problem I have with MX 21 is not with the O.S. but with some programs made in Python that work fine in MX 19.4, but can no longer be installed in MX 21. I will have to consider whether or not to switch.
dolphin_oracle is absolutely right, this shouldn't be a surprise at this point as its a long time coming.

And we need to know which specific applications you're referring to in order to even attempt to address the issue.

Many python2 applications that their developers have migrated to python3 are already in the MX Repos, the ones that aren't have been abandoned by their developers, and will remain that way until someone forks and updates them.

The real solution is to know which applications are an issue and fix that problem, because sooner or later MX-19 won't be supported, and python2 isn't coming back.

For me, Disk Manager is the biggest loss, it probably won't matter for people who don't have multiple systems on their computer, but I do! The gnome replacement is extremely fiddly, and its ability to set mount points and update /etc/fstab was not obvious to me when I tried it, in fact when I ran it I wasn't sure of what it was meant to do! And... I ended up making /etc/fstab by hand, and creating the mount point folders by hand, too!

KDE Partition Manager is much better, but still a bit fiddly, and it did update /etc/fstab correctly for me, but I still had to create the mount point folders by hand.

Posted: **Thu Sep 09, 2021 12:16 pm**

@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....

Posted: **Thu Sep 09, 2021 12:20 pm**

I'm not sure I would install Disk Manager on Plasma since we have KDE Partition Manager that pretty much does that, but for Xfce it would be great to have it.

Posted: **Thu Sep 09, 2021 12:25 pm**

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.

Posted: **Thu Sep 09, 2021 7:16 pm**

hello dolphin_oracle
installed; change kernel.
As you can see, I did realize, that the WallE machine cannot have software sound problem, if in my own, the answer, the heap machine has the same audio hardware with sounding. then both have sound.

System Setings, Startup and Shutdown, Splash Screen
The breeze selection shows an mx animation.
Breeze does not show breeze.
The setting None shows none okay.

Code: Select all

System:
  Host: <filter> Kernel: 5.13.0-exp-mx2-amd64 x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.13.0-exp-mx2-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: Hewlett-Packard product: HP EliteBook 8440p 
  v: N/A serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: Hewlett-Packard model: 172A v: KBC Version 30.35 
  serial: <filter> BIOS: Hewlett-Packard v: 68CCU Ver. F.60 
  date: 11/11/2015 
Battery:
  ID-1: BAT0 charge: 45.8 Wh condition: 47.0/47.0 Wh (100%) 
  volts: 12.3/11.1 model: Hewlett-Packard Primary type: Li-ion 
  serial: <filter> status: Unknown 
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360 
  serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
  status: Discharging 
CPU:
  Topology: Dual Core model: Intel Core i5 M 560 bits: 64 type: MT MCP 
  arch: Nehalem family: 6 model-id: 25 (37) stepping: 5 microcode: 7 
  L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 21284 
  Speed: 1917 MHz min/max: 1199/2667 MHz boost: enabled 
  Core speeds (MHz): 1: 1917 2: 2416 3: 1870 4: 2230 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
  Type: l1tf mitigation: PTE Inversion 
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no 
  microcode; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  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 generic retpoline, IBPB: 
  conditional, IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel Core Processor Integrated Graphics 
  vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:0046 
  Display: x11 server: X.Org 1.20.11 driver: intel compositor: kwin_x11 
  resolution: 1600x900~60Hz, 1280x1024~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 21.1.5 
  direct render: Yes 
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
  bus ID: 00:1b.0 chip ID: 8086:3b56 
  Sound Server: ALSA v: k5.13.0-exp-mx2-amd64 
Network:
  Device-1: Intel 82577LM Gigabit Network vendor: Hewlett-Packard 
  driver: e1000e v: kernel port: 5020 bus ID: 00:19.0 chip ID: 8086:10ea 
  IF: eth0 state: down mac: <filter> 
  Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel 
  port: 5000 bus ID: 43:00.0 chip ID: 8086:4239 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 29.11 GiB used: 7.93 GiB (27.2%) 
  ID-1: /dev/sda type: USB vendor: SanDisk model: Cruzer Glide 
  size: 29.11 GiB block size: physical: 512 B logical: 512 B 
  speed: <unknown> serial: <filter> rev: 1.27 scheme: MBR 
Partition:
  ID-1: / raw size: 27.58 GiB size: 26.98 GiB (97.82%) 
  used: 7.93 GiB (29.4%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 1.50 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) 
  dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 42.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: 195 Uptime: 35m Memory: 3.64 GiB used: 816.2 MiB (21.9%) 
  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

Posted: **Thu Sep 09, 2021 7:40 pm**

hello dolphin_oracle
Standard Menu
right-click in Desktop
Desktop and Folder View with keyboard shortcuts that differ;
the Standard Menu listed, displayed, written keyboard shortcuts are mixed-up. for each, both.
Can I edit my own Standard Menus?
to list applied keyboard shortcuts and to remove the Lock Screen entry?
Desktop Settings and Folder View Settings.
the mouse action settings need input from mouse when changing;
it is more like Add New than like edit existing.
In the mouse action it is better to delete/ remove and add new.

Posted: **Thu Sep 09, 2021 8:34 pm**

Hello dolphin_oracle,

First, I want to thank you and all the MX devs for the good work you do. I'm very excited for the release of MX-21!

Unfortunately, when I went to download the KDE beta 2 ISO, I found that there is no signature file for it on SourceForge. Please fix this ASAP so users can properly verify the authenticity of the ISO.

Thank you, and have a good day/night.

Posted: **Thu Sep 09, 2021 8:37 pm**

computerworm01001 wrote: Thu Sep 09, 2021 8:34 pm Hello dolphin_oracle,

First, I want to thank you and all the MX devs for the good work you do. I'm very excited for the release of MX-21!

Unfortunately, when I went to download the KDE beta 2 ISO, I found that there is no signature file for it on SourceForge. Please fix this ASAP so users can properly verify the authenticity of the ISO.

Thank you, and have a good day/night.

@Adrian can you upload the signature file?

Posted: **Thu Sep 09, 2021 9:34 pm**

dolphin_oracle wrote: Thu Sep 09, 2021 8:37 pm
computerworm01001 wrote: Thu Sep 09, 2021 8:34 pm Hello dolphin_oracle,

First, I want to thank you and all the MX devs for the good work you do. I'm very excited for the release of MX-21!

Unfortunately, when I went to download the KDE beta 2 ISO, I found that there is no signature file for it on SourceForge. Please fix this ASAP so users can properly verify the authenticity of the ISO.

Thank you, and have a good day/night.
@Adrian can you upload the signature file?

Done.

Posted: **Fri Sep 10, 2021 2:52 am**

No, in System Settings. I didn't know the Time & Date setting is disabled there by MX Tools.
OK, so I'll try in MX Tools and be back with a conclusion.

Posted: **Fri Sep 10, 2021 3:55 am**

Setting Date & Time works in MX Tools. The corresponding setting (not working) from System Settings cannot be removed, then ?

Posted: **Fri Sep 10, 2021 6:52 am**

SwampRabbit wrote: Tue Sep 07, 2021 1:34 pm
Gerson wrote: Tue Sep 07, 2021 1:13 pm The problem I have with MX 21 is not with the O.S. but with some programs made in Python that work fine in MX 19.4, but can no longer be installed in MX 21. I will have to consider whether or not to switch.
And we need to know which specific applications you're referring to in order to even attempt to address the issue.
Many python2 applications that their developers have migrated to python3 are already in the MX Repos, the ones that aren't have been abandoned by their developers, and will remain that way until someone forks and updates them.
The real solution is to know which applications are an issue and fix that problem, because sooner or later MX-19 won't be supported, and python2 isn't coming back.

In my case I am referring to Openastro, and it seems that the developer is not going to release a new version. I found Skylendar that already @timkb4cq very kindly compiled and uploaded to MX repositories, but this program has a time calculation error that already the developer is informed. Otherwise I am very happy with Plasma beta 2, I have had no bugs so far.

Posted: **Fri Sep 10, 2021 7:22 am**

hotchilli wrote: Fri Sep 10, 2021 3:55 am Setting Date & Time works in MX Tools. The corresponding setting (not working) from System Settings cannot be removed, then ?

nope, it cannot be removed. It might work under systemd mode, I don't know, but its one we have fought with in the past and haven't found a way to 1. make work or 2. remove.

Posted: **Fri Sep 10, 2021 9:45 am**

OK, thank you.

Posted: **Fri Sep 10, 2021 12:43 pm**

SwampRabbit wrote: Thu Sep 09, 2021 12:16 pm @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....

richb wrote: Thu Sep 09, 2021 12:25 pm 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!

Posted: **Sat Sep 11, 2021 12:48 pm**

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.

Posted: **Sun Sep 12, 2021 7:49 am**

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)

Posted: **Sun Sep 12, 2021 9:53 am**

@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.

Posted: **Sun Sep 12, 2021 10:19 am**

asqwerth wrote: Sun Sep 12, 2021 9:53 am @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.

Posted: **Sun Sep 12, 2021 10:25 am**

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.

Posted: **Sun Sep 12, 2021 11:50 am**

asqwerth wrote: Sun Sep 12, 2021 10:25 am 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.

Posted: **Sun Sep 12, 2021 2:51 pm**

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).

Posted: **Sun Sep 12, 2021 4:12 pm**

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.

Posted: **Sun Sep 12, 2021 4:27 pm**

TimothySimon wrote: Sun Sep 12, 2021 2:51 pm 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.

Posted: **Sun Sep 12, 2021 5:24 pm**

That got it. Thanks. Don't know how I missed it.

Posted: **Sun Sep 12, 2021 8:24 pm**

Hi all,

I don't think this has been mentioned in this thread previously, but when running live from my thumb drive, the pinned icons in the taskbar get overwritten by the icons for the open apps, as per my attachment. The notification that Firefox is open covers the icons for Firefox and also Dolphin. Closing the open applications sees the pinned applications still present. I got a bit of a fright initially, thinking I'd accidentally deleted them.

I've embedded the quick system info results, as it might just be a display glitch due to my hardware.

If I'm missing any information, or if there's things I can try (on the live install), please let me know. Happy to help if I can.

All other things that irked me in MX-19 KDE like my Epson scanner not working, and getting Dolphin to connect to my Google Drive have been fixed.

Thanks to everyone for their dedication to this particularly fine OS - I'm very grateful.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-5mx-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM Distro: MX-19.4_kde_x64 patito feo March 31  2021 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: LG product: 17Z90N-R.AAC8U1 v: 0.1 serial: <filter> Chassis: type: 10 v: 0.1 serial: <filter> 
           Mobo: LG model: 17Z90N v: FAB1 serial: <filter> UEFI: Phoenix v: C2ZE0160 X64 date: 04/07/2020 
Battery:   ID-1: CMB0 charge: 72.2 Wh condition: 72.2/80.0 Wh (90%) volts: 8.7/7.7 model: LG LGC-LGC type: Li-ion 
           serial: <filter> status: Full cycles: 149 
CPU:       Topology: Quad Core model: Intel Core i7-1065G7 bits: 64 type: MT MCP arch: Ice Lake family: 6 model-id: 7E (126) 
           stepping: 5 microcode: A6 L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23961 
           Speed: 2153 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 2153 2: 2566 3: 2292 4: 2357 5: 2302 6: 2298 7: 2202 
           8: 2173 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           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: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Iris Plus Graphics G7 vendor: LG driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:8a52 
           Display: x11 server: X.Org 1.20.10 driver: intel compositor: kwin_x11 resolution: 3840x2160~60Hz 
           OpenGL: renderer: Mesa DRI Intel Iris Plus Graphics (ICL GT2) v: 4.6 Mesa 20.3.4 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: LG driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:34c8 
           Sound Server: ALSA v: k5.10.0-5mx-amd64 
Network:   Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi v: kernel port: 2000 
           bus ID: 00:14.3 chip ID: 8086:34f0 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus ID: 2-1.1:3 chip ID: 0bda:8153 
           serial: <filter> 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.36 TiB used: 456.33 GiB (32.7%) 
           ID-1: /dev/nvme0n1 vendor: Kingston model: SA2000M81000G size: 931.51 GiB block size: physical: 512 B 
           logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: S5Z42105 scheme: GPT 
           ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M81000G size: 931.51 GiB block size: physical: 512 B 
           logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: S5Z42105 scheme: GPT 
           ID-3: /dev/sda type: USB model: SMI USB DISK size: 462.80 GiB block size: physical: 512 B logical: 512 B 
           serial: <filter> rev: 1100 scheme: MBR 
Partition: ID-1: / raw size: 929.23 GiB size: 913.65 GiB (98.32%) used: 98.89 GiB (10.8%) fs: ext4 dev: /dev/nvme1n1p2 
           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/nvme1n1p3 
Sensors:   System Temperatures: cpu: 68.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 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/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ buster main non-free
           2: deb http://la.mxrepo.com/mx/repo/ buster ahs
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 265 Uptime: 23m Memory: 15.27 GiB used: 1.81 GiB (11.9%) 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

Posted: **Sun Sep 12, 2021 8:29 pm**

It’s not a glitch that’s how the task list plasma widget works.

Posted: **Sun Sep 12, 2021 9:50 pm**

Okay.

That's surprising, and makes no sense for it to have been changed. (It's not evident in MX-19 KDE.) That's a deal-breaker as far as I'm concerned as it forces more mouse movements to open the applications via the menu.

Posted: **Sun Sep 12, 2021 10:49 pm**

Metal Mick wrote: Sun Sep 12, 2021 9:50 pm Okay.

That's surprising, and makes no sense for it to have been changed. (It's not evident in MX-19 KDE.) That's a deal-breaker as far as I'm concerned as it forces more mouse movements to open the applications via the menu.

The option was always there in MX19KDE but IIRC Adrian used the "add to panel (widget)" option for the launchers there, instead of the "Pin to Task Manager" option for launchers in MX21, which gives a more "Windows 7" type feel. The latter saves space on the panel because when a pinned app is opened, you don't have double icons on the panel: ie for the launcher + opened window.

What you can do if you don't like that style, is to unpin (right click and choose) all the launchers and add them back using the add to panel option (search for app in menu, right click the item and choose the right type of launcher)

Posted: **Sun Sep 12, 2021 10:58 pm**

there is some additional features this way as well, like a sort of "jumplist" capability to dolphin.

Posted: **Mon Sep 13, 2021 12:41 am**

TimothySimon wrote: Sun Sep 12, 2021 2:51 pm 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

..............................
..............................

Problem 4
sudo kwrite or sudo kate is insecure, so, it exits with an error message (this is a KDE bug).

I think it may be good to keep some alias (in .bashrc) for the method that works safely:
alias sudokwrite='SUDO_EDITOR="/bin/kwrite" sudo --edit '

Example usage: sudokwrite /etc/fstab

(Ref: $ man sudo)

EDIT:

asqwerth wrote: Mon Sep 13, 2021 1:55 am It's not a bug. It's been close to 2 years, I believe, that KDE prohibited that. However, what they provide instead is for you to just open (at least for KATE) any root text file as user, amend the same, and then when you press "SAVE", you are asked for your root/user password. To me, that's perfectly acceptable ans still allows me to edit root files.

Sorry for wasting your valuable time, I now understand that problem 4 is not a problem at all.
I think that "problem 4" was a side effect of me getting used to "sudo gedit" .
(I've been on GNOME/Mate/Cinnamon/XFCE for years. MX-21 Beta 2 was my first experience with KDE plasma.)

Posted: **Mon Sep 13, 2021 12:49 am**

asqwerth wrote: Sat Sep 11, 2021 12:48 pm 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.

I second asqwerth.

asqwerth wrote: Sat Sep 11, 2021 12:48 pm 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.

Thank you for that.

Posted: **Mon Sep 13, 2021 1:32 am**

Problem 4
sudo kwrite or sudo kate is insecure, so, it exits with an error message (this is a KDE bug).

I don't understand, have you noticed we use sudo kwrite/sudo kate anywhere? We shouldn't.
Nobody should use sudo for those programs, just edit the file and when saving it will prompt you for root privileges if needed (sounds to me like a user problem not a program problem)

Posted: **Mon Sep 13, 2021 1:55 am**

TimothySimon wrote: Mon Sep 13, 2021 12:41 am
Problem 4
sudo kwrite or sudo kate is insecure, so, it exits with an error message (this is a KDE bug).

I think it may be good to keep some alias (in .bashrc) for the method that works safely:
Code: Select all
alias sudokwrite='SUDO_EDITOR="/bin/kwrite" sudo --edit '
Example usage: sudokwrite /etc/fstab

(Ref: $ man sudo)

It's not a bug. It's been close to 2 years, I believe, that KDE prohibited that. However, what they provide instead is for you to just open (at least for KATE) any root text file as user, amend the same, and then when you press "SAVE", you are asked for your root/user password. To me, that's perfectly acceptable ans still allows me to edit root files.

Posted: **Mon Sep 13, 2021 2:14 am**

asqwerth wrote: Sun Sep 12, 2021 10:49 pm
The option was always there in MX19KDE but ...f you don't like that style, is to unpin (right click and choose) all the launchers and add them back using the add to panel option (search for app in menu, right click the item and choose the right type of launcher)

Indeed, that is what I tried and all is working well. Often, I will elect to have several Firefox instances running at once so I can keep my surfing-topics separate. Sometimes too, I'll have a couple of Dolphins open at once.

I noted that when I deleted then added to the panel again, the additional application icons were to the left of where they were orignally, so I guess there is some form of spacer in there.

My apologies. The panel was working as designed.

Cheers,

Michael P.

Posted: **Mon Sep 13, 2021 12:16 pm**

One more minor bug with MX 21 KDE plasma Beta 2:

The three-finger right click (with a laptop touchpad) works fine for some time after a fresh boot.
But, after a long time, it doesn't work as expected.
(after 5-6 hours of almost continuous usage -- just two breaks for snacks and lunch, with the lid closed and screen locked)
Still, right clicking with the physical right click button works as expected.

This bug is also present in MX 19.4 XFCE (stable) release.

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: 937 MHz min/max: 800/2500 MHz Core speeds (MHz): 1: 937 2: 978 3: 1179 4: 918 
           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.76 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.28 GiB (29.7%) fs: ext4 dev: /dev/sda9 
Sensors:   System Temperatures: cpu: 46.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: 203 Uptime: 10h 13m Memory: 3.67 GiB used: 1.20 GiB (32.7%) 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

Code: Select all

$ sudo lshw
................................
     *-pnp00:00
          product: PnP device PNP0c02
          physical id: 1
          capabilities: pnp
          configuration: driver=system
     *-pnp00:01
          product: PnP device MSF0001
          vendor: M-Systems Flash Disk Pioneers
          physical id: 2
          capabilities: pnp
          configuration: driver=i8042 kbd
     *-pnp00:02
          product: PnP device SYN1b7b
          vendor: Synaptics Inc
          physical id: 3
          capabilities: pnp
          configuration: driver=i8042 aux
     *-pnp00:03
          product: PnP device PNP0c02
          physical id: 6
          capabilities: pnp
          configuration: driver=system
     *-pnp00:04
          product: PnP device PNP0b00
          physical id: 7
          capabilities: pnp
          configuration: driver=rtc_cmos
..............................................

Code: Select all

$ xinput --list --long
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
        Reporting 8 classes:
                Class originated from: 12. Type: XIButtonClass
                Buttons supported: 12
                Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None None None
                Button state:
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 0:
                  Label: Rel X
                  Range: 1344.000000 - 5658.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 1:
                  Label: Rel Y
                  Range: 1246.000000 - 4652.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 2:
                  Label: Rel Horiz Scroll
                  Range: 0.000000 - -1.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 3:
                  Label: Rel Vert Scroll
                  Range: 0.000000 - -1.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 4:
                  Label: Abs MT Pressure
                  Range: -1.000000 - -1.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIScrollClass
                Scroll info for Valuator 2
                  type: 2 (horizontal)
                  increment: 111.000000
                  flags: 0x0
                Class originated from: 12. Type: XIScrollClass
                Scroll info for Valuator 3
                  type: 1 (vertical)
                  increment: 110.000000
                  flags: 0x0

⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
        Reporting 3 classes:
                Class originated from: 4. Type: XIButtonClass
                Buttons supported: 10
                Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None
                Button state:
                Class originated from: 4. Type: XIValuatorClass
                Detail for Valuator 0:
                  Label: Rel X
                  Range: -1.000000 - -1.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 4. Type: XIValuatorClass
                Detail for Valuator 1:
                  Label: Rel Y
                  Range: -1.000000 - -1.000000
                  Resolution: 0 units/m
                  Mode: relative

⎜   ↳ SynPS/2 Synaptics TouchPad                id=12   [slave  pointer  (2)]
        Reporting 8 classes:
                Class originated from: 12. Type: XIButtonClass
                Buttons supported: 12
                Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None None None
                Button state:
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 0:
                  Label: Rel X
                  Range: 1344.000000 - 5658.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 1:
                  Label: Rel Y
                  Range: 1246.000000 - 4652.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 2:
                  Label: Rel Horiz Scroll
                  Range: 0.000000 - -1.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 3:
                  Label: Rel Vert Scroll
                  Range: 0.000000 - -1.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIValuatorClass
                Detail for Valuator 4:
                  Label: Abs MT Pressure
                  Range: -1.000000 - -1.000000
                  Resolution: 0 units/m
                  Mode: relative
                Class originated from: 12. Type: XIScrollClass
                Scroll info for Valuator 2
                  type: 2 (horizontal)
                  increment: 111.000000
                  flags: 0x0
                Class originated from: 12. Type: XIScrollClass
                Scroll info for Valuator 3
                  type: 1 (vertical)
                  increment: 110.000000
                  flags: 0x0

⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
        Reporting 1 classes:
                Class originated from: 11. Type: XIKeyClass
                Keycodes supported: 248

    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 5. Type: XIKeyClass
                Keycodes supported: 248

    ↳ Power Button                              id=6    [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 6. Type: XIKeyClass
                Keycodes supported: 248

    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 7. Type: XIKeyClass
                Keycodes supported: 248

    ↳ Power Button                              id=8    [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 8. Type: XIKeyClass
                Keycodes supported: 248

    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 9. Type: XIKeyClass
                Keycodes supported: 248

    ↳ VGA Webcam: VGA Webcam                    id=10   [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 10. Type: XIKeyClass
                Keycodes supported: 248

    ↳ AT Translated Set 2 keyboard              id=11   [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 11. Type: XIKeyClass
                Keycodes supported: 248

    ↳ ACPI Virtual Keyboard Device              id=13   [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 13. Type: XIKeyClass
                Keycodes supported: 248

    ↳ Acer WMI hotkeys                          id=14   [slave  keyboard (3)]
        Reporting 1 classes:
                Class originated from: 14. Type: XIKeyClass
                Keycodes supported: 248

Code: Select all

$ synclient -l
Parameter settings:
    LeftEdge                = 1645
    RightEdge               = 5357
    TopEdge                 = 1484
    BottomEdge              = 4414
    FingerLow               = 25
    FingerHigh              = 30
    MaxTapTime              = 180
    MaxTapMove              = 241
    MaxDoubleTapTime        = 180
    SingleTapTimeout        = 180
    ClickTime               = 100
    EmulateMidButtonTime    = 0
    EmulateTwoFingerMinZ    = 282
    EmulateTwoFingerMinW    = 7
    VertScrollDelta         = 110
    HorizScrollDelta        = 111
    VertEdgeScroll          = 1
    HorizEdgeScroll         = 1
    CornerCoasting          = 1
    VertTwoFingerScroll     = 1
    HorizTwoFingerScroll    = 1
    MinSpeed                = 1
    MaxSpeed                = 2
    AccelFactor             = 0.075
    TouchpadOff             = 2
    LockedDrags             = 0
    LockedDragTimeout       = 5000
    RTCornerButton          = 0
    RBCornerButton          = -1
    LTCornerButton          = 0
    LBCornerButton          = -1
    TapButton1              = 1
    TapButton2              = 2
    TapButton3              = 3
    ClickFinger1            = 1
    ClickFinger2            = 3
    ClickFinger3            = 2
    CircularScrolling       = 1
    CircScrollDelta         = 0.100007
    CircScrollTrigger       = 7
    CircularPad             = 0
    PalmDetect              = 0
    PalmMinWidth            = 10
    PalmMinZ                = 200
    CoastingSpeed           = 8
    CoastingFriction        = 50
    PressureMotionMinZ      = 30
    PressureMotionMaxZ      = 160
    PressureMotionMinFactor = 1
    PressureMotionMaxFactor = 1
    GrabEventDevice         = 0
    TapAndDragGesture       = 1
    AreaLeftEdge            = 0
    AreaRightEdge           = 0
    AreaTopEdge             = 0
    AreaBottomEdge          = 0
    HorizHysteresis         = 27
    VertHysteresis          = 27
    ClickPad                = 1
    RightButtonAreaLeft     = 3501
    RightButtonAreaRight    = 0
    RightButtonAreaTop      = 4038
    RightButtonAreaBottom   = 0
    MiddleButtonAreaLeft    = 0
    MiddleButtonAreaRight   = 0
    MiddleButtonAreaTop     = 0
    MiddleButtonAreaBottom  = 0

Code: Select all

$ ls -lh /dev/input/by-path/*
lrwxrwxrwx 1 root root 10 Sep 13 11:13 /dev/input/by-path/pci-0000:00:15.0-usb-0:7:1.0-event -> ../event15
lrwxrwxrwx 1 root root  9 Sep 13 11:13 /dev/input/by-path/platform-i8042-serio-0-event-kbd -> ../event0
lrwxrwxrwx 1 root root  9 Sep 13 11:13 /dev/input/by-path/platform-i8042-serio-1-event-mouse -> ../event6
lrwxrwxrwx 1 root root  9 Sep 13 11:13 /dev/input/by-path/platform-i8042-serio-1-mouse -> ../mouse0

EDIT: This was (temporarily) fixed by assigning Two fingers to Right button in the Touchpad section of KDE Settings.

Posted: **Mon Sep 13, 2021 2:36 pm**

Opened poll about Discover vs Synaptic+apt-notifier:
viewtopic.php?f=145&t=66359

Posted: **Tue Sep 14, 2021 11:09 am**

Please do not post outside the beta topics when dealing with betas, or it will become very messy with them all about. Beta topics were created for a reason, please use them.

I am going to close this one so you can repost there.

MX-Xfce: viewtopic.php?f=94&t=66249

MX-KDE: viewtopic.php?f=94&t=66250

MX-Fluxbox: viewtopic.php?f=94&t=66251

---- Eadwine Rose

Following this instruction by Eadwine Rose, I am reposting it here.

I had some trouble installing qtcreator and its Desktop kits on MX 21 KDE plasma Beta 2.
As I now understand, it was caused by changes in package names in Debian 11 Bullseye.

Following the instructions given by dolphin_oracle , I could install it successfully using the "Qt Dev tools" option from mx-packageinstaller .

Link to the topic: viewtopic.php?f=108&t=66370

Posted: **Tue Sep 14, 2021 12:08 pm**

After installing "Qt Dev Tools" from mx-packageinstaller , I get these error messages on installing any package.

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"

Code: Select all

timothy@mx21B1:~
$ sudo apt install tree
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  tree
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 49.6 kB of archives.
After this operation, 118 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 tree amd64 1.8.0-1+b1 [49.6 kB]
Fetched 49.6 kB in 0s (104 kB/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"
Icon theme "elementary" not found.
Selecting previously unselected package tree.
(Reading database ... 310936 files and directories currently installed.)
Preparing to unpack .../tree_1.8.0-1+b1_amd64.deb ...
Unpacking tree (1.8.0-1+b1) ...
Setting up tree (1.8.0-1+b1) ...
Processing triggers for man-db (2.9.4-2) ...

Posted: **Tue Sep 14, 2021 12:10 pm**

These ones?

Code: Select all

QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"

Those are showing for everybody not sure how to fix that. It also doesn't look like they actually create any problems.

Posted: **Tue Sep 14, 2021 2:37 pm**

gedit has no window decorations on MX 21 KDE plasma Beta 2.
(I suspect this may be applicable for some other GTK apps too)

The only ways to close it in the GUI are through the panel or killing it with KSysGuard.

Sorry, my mistake.

Posted: **Wed Sep 15, 2021 12:50 am**

Hypnotix is in the stable repo on MX 21 but the same issue applies to the version in test on MX-19

The app will not open without installing python3-requests first

think this one belongs to @SwampRabbit who probably has not much better to do these days :)

BTW...........MX-21 is brilliant ... would be happy enough if this were the final ... i keep forgetting that it isn't and that i will have to configure it all over again

Posted: **Wed Sep 15, 2021 1:44 am**

junoluna wrote: Wed Sep 15, 2021 12:50 am Hypnotix is in the stable repo on MX 21 but the same issue applies to the version in test on MX-19

The app will not open without installing python3-requests first

think this one belongs to @SwampRabbit who probably has not much better to do these days :)

Thanks for bringing this up, don't see how that happened because I actually test it... must have had python3-requests pulled in by another package during testing.

I see the issue though and can fix it two different ways, not sure how this got past the Linux Mint folks or why its not reported as a dependency upstream.

Also it would have been proper to report that in the MX-19 Hypnotix thread rather than here, its not a problem with the Beta.

I'll work on fixing it sometime tomorrow.

Posted: **Wed Sep 15, 2021 3:08 am**

sorry ... i could only find the hypnotix lite thread

Posted: **Wed Sep 15, 2021 10:33 am**

This is what I get when I click on the "Wastebin" (UK English) plasmoid from the panel. I don't know whether it works correctly in US English where it's called Trash.

The right click option to empty the bin works, and it can be accessed via Dolphin. I wonder whether this is because it's faulty or due to a problem with the translation. I suspect it may be a KDE error rather than an MX error though.

ksnip_20210915-152844.png

Posted: **Wed Sep 15, 2021 11:51 am**

davemx wrote: Wed Sep 15, 2021 10:33 am This is what I get when I click on the "Wastebin" (UK English) plasmoid from the panel. I don't know whether it works correctly in US English where it's called Trash.

The right click option to empty the bin works, and it can be accessed via Dolphin. I wonder whether this is because it's faulty or due to a problem with the translation. I suspect it may be a KDE error rather than an MX error though.

ksnip_20210915-152844.png

Rubbish!

I don't think it's translation. However, I cannot replicate it, I don't see that in Live environment did a fresh install and still don't see it. trash:/ is what it shows for me and it works.
Do you see a ~/.local/share/Trash folder? If not can you create and try again?

Posted: **Wed Sep 15, 2021 1:24 pm**

KDE settings consistently crashes
This happens when trying do to a certain action in the "Touchpad" section:
Trying to drag the "Drag me" icon in the Testing area and drop it in a specific corner (the one just above the "Apply" button).
(a short screen recording is attached)

It also produces a consistent crash report:

Code: Select all

Application: System Settings (systemsettings5), signal: Aborted

[KCrash Handler]
#4  0x00007fc5b595fce1 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x00007fc5b5949537 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x00007fc5b5b837ec in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x00007fc5b5b8e966 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x00007fc5b5b8e9d1 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fc5b5b8ec65 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fc5b5d46fe1 in qBadAlloc() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007fc5b5d58bc3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007fc5b5f0908a in QAbstractListModel::dropMimeData(QMimeData const*, Qt::DropAction, int, int, QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fc5b6dc79df in QListWidget::dropMimeData(int, QMimeData const*, Qt::DropAction) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fc5b6d78b73 in QAbstractItemView::dropEvent(QDropEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007fc5b6b62fae in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007fc5b6c0b42e in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007fc5b5f63d33 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fc5b6b2314e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007fc5b6b2bf31 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007fc5b5f63fca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fc5b6b7d752 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x00007fc5b6b7e583 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007fc5b6b2315f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x00007fc5b5f63fca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007fc5b643d54f in QGuiApplicationPrivate::processDrop(QWindow*, QMimeData const*, QPoint const&, QFlags<Qt::DropAction>, QFlags<Qt::MouseButton>, QFlags<Qt::KeyboardModifier>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#26 0x00007fc5b6410ec8 in QWindowSystemInterface::handleDrop(QWindow*, QMimeData const*, QPoint const&, QFlags<Qt::DropAction>, QFlags<Qt::MouseButton>, QFlags<Qt::KeyboardModifier>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#27 0x00007fc5aca081a8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#28 0x00007fc5aca0c15e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#29 0x00007fc5b647b65d in QBasicDrag::eventFilter(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#30 0x00007fc5b5f63c06 in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x00007fc5b6b23198 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#32 0x00007fc5b5f63fca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x00007fc5b643b583 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#34 0x00007fc5b641164c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#35 0x00007fc5ac9f87da in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#36 0x00007fc5b3a95e6b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007fc5b3a96118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#38 0x00007fc5b3a961cf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#39 0x00007fc5b5fbb51f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#40 0x00007fc5b5f6298b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#41 0x00007fc5b647a7a3 in QBasicDrag::drag(QDrag*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#42 0x00007fc5b6477aa5 in QDragManager::drag(QDrag*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#43 0x00007fc5b6477dcb in QDrag::exec(QFlags<Qt::DropAction>, Qt::DropAction) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#44 0x00007fc5b6dc0453 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#45 0x00007fc5b6dbfdd1 in QListView::startDrag(QFlags<Qt::DropAction>) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#46 0x00007fc5b6d84edd in QAbstractItemView::mouseMoveEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#47 0x00007fc5b6dbf0f7 in QListView::mouseMoveEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#48 0x00007fc5b6b62fae in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#49 0x00007fc5b6c0b42e in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#50 0x00007fc5b5f63d33 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#51 0x00007fc5b6b2314e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#52 0x00007fc5b6b2a04b in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#53 0x00007fc5b5f63fca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#54 0x00007fc5b6b29076 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#55 0x00007fc5b6b7b011 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#56 0x00007fc5b6b7e33e in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#57 0x00007fc5b6b2315f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#58 0x00007fc5b5f63fca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#59 0x00007fc5b643b583 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#60 0x00007fc5b641164c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#61 0x00007fc5ac9f87da in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#62 0x00007fc5b3a95e6b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#63 0x00007fc5b3a96118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#64 0x00007fc5b3a961cf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#65 0x00007fc5b5fbb51f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#66 0x00007fc5b5f6298b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#67 0x00007fc5b5f6ac00 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#68 0x000055a505b19d2c in ?? ()
#69 0x00007fc5b594ad0a in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#70 0x000055a505b1a6ea in _start ()
[Inferior 1 (process 15231) detached]

Posted: **Wed Sep 15, 2021 1:27 pm**

davemx wrote: Wed Sep 15, 2021 10:33 am This is what I get when I click on the "Wastebin" (UK English) plasmoid from the panel. I don't know whether it works correctly in US English where it's called Trash.

The right click option to empty the bin works, and it can be accessed via Dolphin. I wonder whether this is because it's faulty or due to a problem with the translation. I suspect it may be a KDE error rather than an MX error though.

ksnip_20210915-152844.png

It's working as expected here (also UK). Clicking displays the contents of the waste-bin in Dolphin; if the waste-bin is empty it opens Dolphin correctly also.

Chris

Posted: **Wed Sep 15, 2021 6:17 pm**

Just a heads up to the KDE Beta users.... you're probably gonna see a lot of updates now that the AHS repos are populating.

Posted: **Wed Sep 15, 2021 6:41 pm**

SwampRabbit wrote: Wed Sep 15, 2021 6:17 pm Just a heads up to the KDE Beta users.... you're probably gonna see a lot of updates now that the AHS repos are populating.

Thanks for the heads up. Everything updated fine.

Posted: **Wed Sep 15, 2021 7:01 pm**

Adrian wrote: Wed Sep 15, 2021 6:41 pm
SwampRabbit wrote: Wed Sep 15, 2021 6:17 pm Just a heads up to the KDE Beta users.... you're probably gonna see a lot of updates now that the AHS repos are populating.
Thanks for the heads up. Everything updated fine.

Same here. As I recall there were 46, mostly libraries.

Posted: **Thu Sep 16, 2021 9:56 am**

Jerry asked me for a screenshot of Task Scheduler for KDE for the manual. It is not installed in the current ISO. I installed it and provided the screenshot. I think it should be installed by default.

Posted: **Thu Sep 16, 2021 9:59 am**

richb wrote: Thu Sep 16, 2021 9:56 am Jerry asked me for a screenshot of Task Scheduler for KDE for the manual. It is not installed in the current ISO. I installed it and provided the screenshot. I think it should be installed by default.

Thanks, added to the list.

Posted: **Thu Sep 16, 2021 9:58 pm**

So I'm not one to care much about appearances and theming and the like, but this is something that kinda bugs me and should be an easy "fix" for someone who knows what he's doing.

With MX21b2KDE, on startup, the background for the grub screen is the dark blue and black pyramid image; then you get the circular throbber with a turquoise background with some stylistic swirls; then the "twirling DNA"; then the login screen which appears to be laid over the wallpaper image but is fuzzed out dramatically; and then finally the gorgeous red & pink flowers wallpaper. None of that follows. It's disjointed. It just looks cobbled together.

I think it was MX 17 (don't hold me to that) that had the startup visual that transitioned from a black and white image to the full color wallpaper. First time I saw that I literally, actually, said "Wow" out loud. It reminded me of the Wizard of Oz when Dorothy's house landed. That's how you make a first impression.

Just an offhand idle comment. I know you guys have bigger fish to fry, but if impressions matter, I'd like to see you somehow tie all the different startup screens together in one coherent whole.

Posted: **Fri Sep 17, 2021 2:53 am**

uncle mark wrote: Thu Sep 16, 2021 9:58 pm I think it was MX 17 (don't hold me to that) that had the startup visual that transitioned from a black and white image to the full color wallpaper. First time I saw that I literally, actually, said "Wow" out loud. It reminded me of the Wizard of Oz when Dorothy's house landed. That's how you make a first impression.

Just an offhand idle comment. I know you guys have bigger fish to fry, but if impressions matter, I'd like to see you somehow tie all the different startup screens together in one coherent whole.

I remember that, indeed. I liked that too.

Wow, I am agreeing with Uncle Mark on something.

Might be a thought to reimplement that cool thing we had then.

Posted: **Fri Sep 17, 2021 3:40 am**

@uncle mark

Your observation is something the dev team have actually been discussing already, but no decision has been made yet.

However, some points for your information:

That B/W login to coloured desktop transition was used all the way to mx19 but it was for XFCE. I don't mind having something similar be done in MX21 xfce.

KDE's default display manager, sddm, allows sddm login themes to show a highly blurred version (ie like it's behind frosted glass) of a background. In beta2, the background used in the sddm theme is the default WP. So the transition is from blurred default WP in the login window, to the default WP in its full coloured glory on the desktop. That would in my opinion be a fair parallel of the previous transition in xfce.

Splash screen between login window to desktop - that is a plasma thing. XFCE has a splash screen option with is very rarely enabled by any distro, as far as I am aware, and MX has never used it. A neutral grey (plus dna/molecue structure graphic) splash theme was chosen to match the greyish shade of the sddm theme.

grub theme background and the plymouth splash background, yes, I agree with you that right now they don't really blend that well.

Posted: **Fri Sep 17, 2021 5:57 am**

Adrian wrote: Wed Sep 15, 2021 11:51 am
davemx wrote: Wed Sep 15, 2021 10:33 am This is what I get when I click on the "Wastebin" (UK English) plasmoid from the panel. I don't know whether it works correctly in US English where it's called Trash.

The right click option to empty the bin works, and it can be accessed via Dolphin. I wonder whether this is because it's faulty or due to a problem with the translation. I suspect it may be a KDE error rather than an MX error though.

ksnip_20210915-152844.png
Rubbish!
I don't think it's translation. However, I cannot replicate it, I don't see that in Live environment did a fresh install and still don't see it. trash:/ is what it shows for me and it works.
Do you see a ~/.local/share/Trash folder? If not can you create and try again?

OK it may have something to do with how I've partitioned my hard drive to cope with having multiple linux systems sharing a big data partition incorporating all the homes and shared data. It looks as if anything I send to trash ends up in a folder /mnt/Data/.Trash-1000, which functions correctly, including via Dolphin, with the exception of this widget. But if I delete or rename ~/.local/share/Trash it instantly reappears. There must be contradictory settings somewhere. I set up a second desktop for my wife and she has a trash folder at /mnt/Data/.Trash-1002, and the widget doesn't work on her desktop either. I noticed also /mnt/Data/.Trash-0, presumably root, even though root's home directory is in the standard place. Anyhow, this doesn't appear to be a problem with the beta but with my weird setup.

But if anyone could point me in the direction of the relevant settings files, I would be grateful!

Posted: **Fri Sep 17, 2021 8:47 am**

Thanks for the comments @asqwerth . Not surprised you guys are on top of this.

Just throwing this out...

Perhaps the amount of blurring or otherwise distorting the final wallpaper could be changed between screen backgrounds, from the grub screen being totally smeared/blurred/distorted and then gradually becoming less so until the default wallpaper finally is displayed.

Posted: **Fri Sep 17, 2021 8:50 am**

Eadwine Rose wrote: Fri Sep 17, 2021 2:53 am
Wow, I am agreeing with Uncle Mark on something.

That's a bad omen.

Posted: **Mon Sep 20, 2021 1:40 am**

Is there an option to pin trash to the desktop on MX 21 KDE Plasma Beta 2 ?
(I know that we can make a desktop file with Exec=dolphin trash:/ , but is there an easier GUI way ?)

I know this may be a foolish question, but I'm very new to KDE.
(I've been using GNOME/Mate/Cinnamon/XFCE for years. MX-21 Beta 2 was my first experience with KDE plasma.)

Posted: **Mon Sep 20, 2021 1:54 am**

@TimothySimon

you can just drag it from 'places' in dolphin onto the desktop .... or add a trashcan from widgets

Posted: **Mon Sep 20, 2021 4:02 am**

junoluna wrote: Mon Sep 20, 2021 1:54 am @TimothySimon

you can just drag it from 'places' in dolphin onto the desktop .... or add a trashcan from widgets

Thanks. It works.

Posted: **Mon Sep 20, 2021 5:25 am**

TimothySimon wrote: Mon Sep 20, 2021 4:02 am
junoluna wrote: Mon Sep 20, 2021 1:54 am @TimothySimon

you can just drag it from 'places' in dolphin onto the desktop .... or add a trashcan from widgets
Thanks. It works.

I might try this (dragging from places in Dolphin), see my previous posts on a problem with the Wastebin plasmoid. I tried reorganising the stuff on my Data partition and remounting it as /home, and started with a new partition for myself. I reinstalled MX21ß2KDE, and the plasmoid worked just fine, but as soon as I symlinked folders to my Pictures, Downloads etc., I got the same Malformed URL error. This didn't happen with MX19KDE, and it doesn't happen with another distro I have installed with KDE5.22 (though that iteration brings back the ghost window problem!).

I found that making a .desktop with Exec=dolphin --new-window trash:/ works properly, so there must be some sort of error in the Wastebin plasmoid.

EDIT: It doesn't work. I get the same "Malformed URL" with the link dragged from dolphin as I did from the plasmoid. No idea why!

FIXED IT!: OK — it had nothing to do with the symlinks. It was simply because I had dragged a copy of the Dolphin desktop file into my ~/.local/share/applications folder in order to add some right-click actions, and to change the exec line to add --new-window, to be dragged onto a panel. So now the system sees two dolphin desktop files and gets confused! So I changed the Name= entry in my local copy to File Manager and also changed the name of the desktop file to file-manager.desktop, and now everything works as it should.

By the way, in my other distro running KDE5.22, the Wastebin plasmoid works despite me having two dolphin desktop files. No idea why this is but problem is solved now.

Posted: **Mon Sep 20, 2021 3:00 pm**

Under MX Dark theme (on MX KDE beta 2, from KDE setings -> Global Theme) , LibreOffice and nomacs (and probably many more apps) have poorly visibile icons (Black icons on a Grey background).

In nomacs, I could fix this by nomacs' Dark Theme (from nomacs Settings).

But, I couldn't fix it in LibreOffice.

I think the icons should be more visible by default.

Posted: **Mon Sep 20, 2021 3:35 pm**

you can change libreoffice's theme in the libreoffice settings. it should default to breeze on KDE. LO tries to do something automatic with its theme selection but I've noticed it doesn't always make the right decision.

Posted: **Mon Sep 20, 2021 3:39 pm**

In LibreOffice I use the Hicontrast icon theme and for dark themes I use BeatyLine, Oxy R3 Classic, Oieicons or Sweet-Rainbow, the problem is not in MX 21 KDE.

Posted: **Mon Sep 20, 2021 10:00 pm**

TimothySimon wrote: Mon Sep 20, 2021 3:00 pm Under MX Dark theme (on MX KDE beta 2, from KDE setings -> Global Theme) , LibreOffice and nomacs (and probably many more apps) have poorly visibile icons (Black icons on a Grey background).

In nomacs, I could fix this by nomacs' Dark Theme (from nomacs Settings).

But, I couldn't fix it in LibreOffice.

I think the icons should be more visible by default.

The problem with some apps is that they have their own internal theme. Like nomacs. So if you change your system theme from light to dark, you'll need to manually change nomacs' as well.

For LO, they have their own icon choices that are not governed by system settings: go to Options, View, and choose your icon set. Try Tango or Sifr dark. To be honest, I always change the icons in LO from default.

It's not possible to always cover all appearance changes. If the default system look is a light theme, the user may have to make some manual changes in some apps if he or she then switches to a dark system theme.

Posted: **Tue Sep 21, 2021 12:06 am**

asqwerth wrote: Mon Sep 20, 2021 10:00 pm ............

Thank you.

I am now using the Options -> View -> Breeze dark theme in LibreOffice (no SVG).

I wish such apps' internal themes were changed when I change the Global Theme.

Posted: **Wed Sep 22, 2021 7:26 am**

markol wrote: Sun Sep 05, 2021 2:19 pm
markol wrote: Sun Sep 05, 2021 12:01 pm Installed beta2 in VirtualBox, everything went smooth except I only have logout icon in Applications menu. No shutdown or restart.
Icons were present in the previous beta.
Switching from Applications menu to alternative (I tried Launcher and Dashboard) and then back fixes this issue

Fix was only temporary, shutdown and reboot icons missing from the Applications menu again.

I don't know what triggered this, but there were only two things I did in the last couple of days - applying updates and replacing existing LibreOffice for 7.2

Posted: **Wed Sep 22, 2021 8:21 am**

markol wrote: Wed Sep 22, 2021 7:26 am … and replacing existing LibreOffice for 7.2

Care to share the method you used to do this so someone can try to replicate it and see if that’s the issue?

Posted: **Wed Sep 22, 2021 11:25 am**

Now this is really weird. I have the MX21ß2-KDE testing version installed, and another Linux using KDE5.22. On both installs, I have the same version of Vivaldi (4.2.2406.44). I have exactly the same extensions on both. Following my recent re-install of MX21ß2-KDE (see previous posts why I did it), there's something not quite right about Vivaldi. Not only does it not use the KDE Load/Save dialogs (and the native Vivaldi ones are painful to use), but there is a massive keyboard delay when I type something into Facebook and on no other site, but only on the MX install, not on the other one which works perfectly. I am at a real loss to understand why this is. I wonder if this and the KDE Load/Save issue are connected. I am having trouble finding the setting to force Vivaldi to use the desktop settings for Load/Save rather than its own. Just really strange. I might have to re-install yet again from scratch to see if that makes a difference!

Posted: **Wed Sep 22, 2021 11:45 am**

Not sure what you mean by Load/Save dialog. I use Vivaldi in MX 21 B2 as well, and would like to check your issue. I have Vivaldi version 4.2.2406.48. I think that is the latest stable version.

Posted: **Wed Sep 22, 2021 12:01 pm**

SwampRabbit wrote: Wed Sep 22, 2021 8:21 am
markol wrote: Wed Sep 22, 2021 7:26 am … and replacing existing LibreOffice for 7.2
Care to share the method you used to do this so someone can try to replicate it and see if that’s the issue?

Sure :)

I downloaded debs from https://www.libreoffice.org/download/download/ and extracted archive to a folder

Removed existing with

Code: Select all

sudo apt remove libreoffice*

Then opened terminal in a mentioned folder and ran

Code: Select all

sudo dpkg -i *.deb

Posted: **Wed Sep 22, 2021 12:37 pm**

@markol I noticed this issue goes back awhile for you, is that right?

You did a fresh install of MX-21 Beta 2 not an upgrade from Beta 1 right?

In a stock but updated MX-21 KDE Beta 2 VM, I have always had all the icons in the Applications menu.

To try and replicate that manually updating Libreoffice does or does not cause this problem, I...

- downloaded 7.2.1 from the site
- installed all the .debs, BUT did not remove anything prior

Libreoffice 7.2.1 starts fine and still have all the icons in the Applications menu.

I don't think regular updates or manually updating Libreoffice caused this, I think something is wrong with your initial installation. Going back through the thread I see it was mentioned this should not be an issue anymore. So hopefully when you install again (another Beta, RC, or Final) you won't have this issue.

Posted: **Wed Sep 22, 2021 1:36 pm**

SwampRabbit wrote: Wed Sep 22, 2021 12:37 pm @markol I noticed this issue goes back awhile for you, is that right?

You did a fresh install of MX-21 Beta 2 not an upgrade from Beta 1 right?

In a stock but updated MX-21 KDE Beta 2 VM, I have always had all the icons in the Applications menu.

To try and replicate that manually updating Libreoffice does or does not cause this problem, I...

- downloaded 7.2.1 from the site
- installed all the .debs, BUT did not remove anything prior

Libreoffice 7.2.1 starts fine and still have all the icons in the Applications menu.

I don't think regular updates or manually updating Libreoffice caused this, I think something is wrong with your initial installation. Going back through the thread I see it was mentioned this should not be an issue anymore. So hopefully when you install again (another Beta, RC, or Final) you won't have this issue.

Yes, this was a clean install. I believe @uncle mark had this problem in beta1.
I don't believe LibreOffice had anything to do with it either.

I will try to reinstall (clean) tonight and retrace the steps.

Posted: **Wed Sep 22, 2021 1:44 pm**

richb wrote: Wed Sep 22, 2021 11:45 am Not sure what you mean by Load/Save dialog. I use Vivaldi in MX 21 B2 as well, and would like to check your issue. I have Vivaldi version 4.2.2406.48. I think that is the latest stable version.

I just did the general upgrade which took vivaldi to 4.2.2406.58. I did that in both distros. At present, I don't seem to be getting the keyboard delay, but for whatever reason, I can still hear the fan, which I cannot on the other distro. I have a modified MX-asq/GeekyTower which shows the top 10 CPU users instead of 3 and vivaldi-bin was taking too much, over three instances shown. But now it is hardly taking anything after I did a "killall vivaldi-bin" and restarted it without facebook and now it's running silently. Yet in my other distro Facebook doesn't cause a problem.

Load/Save dialogs. Like "Open File" when you want to upload an attachment.

This is the KDE dialog box as used by the other distro:

Screenshot_20210922_180927.png

This is the Vivaldi dialog box as used by MX

ksnip_20210922-181358.png

I'm sure that before I reinstalled MX21ß2-KDE a couple of days ago, that MX was using the first of these, and I had no problems on Facebook.

Posted: **Wed Sep 22, 2021 2:26 pm**

I am afraid you lost me. Those dialog boxes appear to be from Dolphin not the Vivaldi browser. If that is the case the appearance of the window is controlled by the theme chosen in System Settings and how Dolphin is configured.

Posted: **Wed Sep 22, 2021 3:16 pm**

richb wrote: Wed Sep 22, 2021 2:26 pm I am afraid you lost me. Those dialog boxes appear to be from Dolphin not the Vivaldi browser. If that is the case the appearance of the window is controlled by the theme chosen in System Settings and how Dolphin is configured.

OK, I'll have a look at that when I'm next on the computer. Cheers!

Posted: **Wed Sep 22, 2021 4:12 pm**

No, I am pretty sure I was right. The first dialog box is a KDE File selector, it even says KDialog at the top. The second one is different. It works differently, and has different options, not just a stylistic difference. I went through the options in both Systemsettings and Dolphin, and if you can tell me how to set the style of the dialog box, I'll give it a try.

Posted: **Wed Sep 22, 2021 5:19 pm**

markol wrote: Wed Sep 22, 2021 1:36 pm I will try to reinstall (clean) tonight and retrace the steps.

@SwampRabbit a fresh install did the trick, everything went well without problems and/or hickups. I installed it from the same image as before.

Posted: **Wed Sep 22, 2021 5:24 pm**

davemx wrote: Wed Sep 22, 2021 4:12 pm No, I am pretty sure I was right. The first dialog box is a KDE File selector, it even says KDialog at the top. The second one is different. It works differently, and has different options, not just a stylistic difference. I went through the options in both Systemsettings and Dolphin, and if you can tell me how to set the style of the dialog box, I'll give it a try.

The second dialog looks more gtk than kdialog. Do you have any gtk settings set up or maybe installed mx-fluxbox?

Posted: **Wed Sep 22, 2021 7:28 pm**

dolphin_oracle wrote: Wed Sep 22, 2021 5:24 pm The second dialog looks more gtk than kdialog. Do you have any gtk settings set up or maybe installed mx-fluxbox?

That's what I thought. Obviously I have some gtk programs installed, for example GIMP and Inkscape. I haven't installed fluxbox, I really don't like it. Maybe I should look at the Open dialog in a gtk program for comparison. I'm just at a loss as to why I can't get Vivaldi to use kdialog, and also why Vivaldi is misbehaving. I've been looking on the net and so far found nothing that helps.

Posted: **Wed Sep 22, 2021 11:45 pm**

I just got a new work notebook, MSI GE75 Raider, i7 w/ GeForce video, so I decided to give the beta2 a try on it. It's dual boot with Windows.
2 issues
1. no sound

ksnip_20210922-224104.png

The top controller only has Off as an option.
None of the options on the second controller produce sound.
2. no video output to the external HDMI
The TV I'm connecting to detects that something is plugged in, but in the system settings it never shows the second screen. I've tried setting the refresh rate down to 60Hz and changing the resolution with no change.

I tried installing nvidia drivers with the MX installer which did not help with either.
Everything works fine in Windows.

I am currently at an IT conference and don't have access to a spare flash drive to install MX-19.4 from to see if the issues are there as well, so this may not be just MX-21 related.
Al

Code: Select all

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: Micro-Star product: GE75 Raider 10SE v: REV:1.0 serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: Micro-Star model: MS-17E9 v: REV:1.0 serial: <filter> UEFI: American Megatrends v: E17E9IMS.10D 
           date: 11/17/2020 
Battery:   ID-1: BAT1 charge: 47.0 Wh condition: 48.3/51.6 Wh (94%) volts: 12.2/10.9 model: MSI BIF0_9 type: Li-ion 
           serial: N/A status: Unknown 
           Device-1: hid-00:02:76:06:c7:82-battery model: Si670m Bluetooth Wireless Notebook Mouse serial: N/A charge: N/A 
           status: Discharging 
CPU:       Topology: 6-Core model: Intel Core i7-10750H bits: 64 type: MT MCP arch: N/A family: 6 model-id: A5 (165) 
           stepping: 2 microcode: EA L2 cache: 12.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62399 
           Speed: 800 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
           9: 800 10: 800 11: 800 12: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           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: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Micro-Star MSI driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:9bc4 
           Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Micro-Star MSI driver: nvidia v: 460.91.03 
           bus ID: 01:00.0 chip ID: 10de:1f15 
           Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa alternate: nv 
           compositor: kwin_x11 tty: N/A 
           OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 21.2.1 direct render: Yes 
Audio:     Device-1: Intel Comet Lake PCH cAVS vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:06c8 
           Device-2: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 10de:10f9 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel port: 5000 bus ID: 00:14.3 chip ID: 8086:06f0 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros Killer E2500 Gigabit Ethernet vendor: Micro-Star MSI driver: alx v: kernel port: 3000 
           bus ID: 03:00.0 chip ID: 1969:e0b1 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.40 TiB used: 356.25 GiB (24.8%) 
           ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN730 SDBPNTY-512G-1032 size: 476.94 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 11111000 scheme: GPT 
           ID-2: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 0001 scheme: GPT 
           ID-3: /dev/sdb type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.90 GiB block size: physical: 512 B 
           logical: 512 B serial: <filter> rev: PMAP scheme: MBR 
Partition: ID-1: / raw size: 25.00 GiB size: 24.44 GiB (97.76%) used: 8.65 GiB (35.4%) fs: ext4 dev: /dev/nvme0n1p5 
           ID-2: /home raw size: 178.00 GiB size: 174.15 GiB (97.84%) used: 467.9 MiB (0.3%) fs: ext4 dev: /dev/nvme0n1p9 
           ID-3: swap-1 size: 17.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default) 
           dev: /dev/nvme0n1p8 
Sensors:   System Temperatures: cpu: 54.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/anydesk-stable.list 
           1: deb http://deb.anydesk.com/ all main
           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/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/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/syncthing.list 
           1: deb [signed-by=/usr/share/keyrings/syncthing-archive-keyring.gpg] https://apt.syncthing.net/ syncthing stable
Info:      Processes: 307 Uptime: 24m Memory: 15.46 GiB used: 2.39 GiB (15.5%) 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

Posted: **Thu Sep 23, 2021 2:54 am**

I tried installing nvidia drivers with the MX installer which did not help with either.

What happened? Did you get error messages? Your QSI shows that the Nvidia driver 460 was installed, so the driver installation probably succeeded.

If you search the forum you'll find posts about how some laptop manufacturers hard-wire the HDMI port to the Nvidia GPU's bus, and as yours is a bumblebee/optimus system that GPU won't be in use by default. These posts also tell how to work around that so the HDMI port can also be used by the default Intel integrated GPU. That's also explained here: https://wiki.archlinux.org/title/Bumble ... VIDIA_chip.

As a troubleshooting measure open a terminal and run

Code: Select all

optirun kcmshell5 kcm_kscreen

with the TV connected and see if it's detected. If it is, then that's what the situation is: HDMI wired to Nvidia's bus. It wouldn't be an MX issue but a hardware design "feature."

Posted: **Thu Sep 23, 2021 5:32 am**

Hello all,

I've tried the XFCE and KDE beta2 isos. I liked the KDE one so much, that I've been using it as my primary system for the past week or so. I will list here all of the improvements and bugs I have encountered in KDE beta2. I don't know which bugs are caused by KDE devs, which by Debian, and which by MX, so I'll just lay out everything I've observed and let you all figure it out.

Improvements:

1. Better external monitor detection. In MX-19.4, when I booted from Live USB, the first thing I had to do was open System Settings and turn off my laptop panel to make my external monitor the main display. In MX-21, my external monitor is already detected as being primary on first boot.

2. Picture of the Day actually works (sort of) in MX-21. In MX-19.4 PIcture of the Day was present but nonfunctional. In MX-21, half of the picture providers work. The ones that don't are Flickr, National Geographic, NOAA, and Wikimedia Commons.

Bugs:

1. Plasma randomly freezes - it's an easy fix; just enable the compositor, but still, it seemed like something you should be made aware of.

2. Changing default directories under System Settings > Locations doesn't do anything and I have to manually edit the sidebar shortcuts in Dolphin by right-clicking them and selecting "Edit". And yes, I did try logging out and logging back in, with no effect.

3. Network always disconnects after suspending from Plasma power buttons and doesn't automatically reconnect - have to reconnect manually. This glitch does not happen when I suspend using rtcwake or pm-suspend. Sometimes it also fails to automatically connect directly after boot, with no apparent rationale behind it.

4. I don't like sudo, I prefer doas, but plasma-desktop depends on kde-cli-tools, which depends on libkf5su5, which depends on sudo, therefore I have both doas and sudo installed - but it shouldn't have to be that way - doas should just be a drop-in replacement for the sudo dependency.

5. When I click the close button, Kaffeine asks multiple times whether I want to quit, because there are pending recordings, and I have to click yes 2 or sometimes 3 times - isn't 1 confirmation enough?

6. When creating system snapshot, MX Snapshot creates "minstall.desktop" shortcut on Desktop of currently running system.

7. When using autologin, it logs in once, then after a few seconds logs out and logs in again. I found another post on this thread where an MX dev explained that X restarts because of a special MX fix for making the SDDM power buttons work in SysVinit, and that most people should barely see a flash. And when I login manually, I don't notice X restarting at all. I only see it when I use autologin.

8. Autologin doesn't work when laptop is not plugged in - computer goes to sleep before having a chance to login, I have to plug it in and wake it in order for autologin to work. I'm not sure whether or not this has anything to do with the fact that my laptop's lid is always closed because I use an external monitor. It might work differently if the lid were open/if there were no external monitor, but I haven't had the motivation to test that hypothesis, and anyway I think it needs to just work regardless of what monitor setup the end user has . . .

9. Removable devices will mount with Device Notifier only under first user account created. Subsequently created accounts do not have permission to mount with Device Notifier. I also tried mounting the USB drive from the Dolphin interface, and got a more verbose error message:

"An error occurred while accessing 'USB_DRIVE', the system responded: An unspecified error has occurred: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

10. This is not specifically a KDE bug, but it is an MX beta2 bug; I tried the new Job Scheduler app, and I got these strange errors when I attempted to save my crontab edits, and for the record, I double checked my crontab syntax, and there was nothing wrong with it, so I don't know why the errors are raised:

Code: Select all

CronTime::CronTime Invalid Minute Format: "*/"
File Saved : "/tmp/job-scheduler-root/root.HOGeqD"
File Saved : "/tmp/job-scheduler-root/root.QBOcfa"
CronTime::CronTime Invalid Item count: 1
CronTime::CronTime Invalid Item count: 2
CronTime::CronTime Invalid Item count: 2
CronTime::CronTime Invalid Item count: 3
CronTime::CronTime Invalid Item count: 3
CronTime::CronTime Invalid Item count: 4
CronTime::CronTime Invalid Item count: 4
CronTime::CronTime Invalid Week Format: ""
File Saved : "/tmp/job-scheduler-root/root.oWJviK"

11. This may or may not tie in with the previous error, but the root crontab doesn't work. I know my syntax is correct because I entered the same commands in my personal user crontab (appending doas to the beginning, of course) and it works perfectly. So there's something wrong with the root crontab, and I don't know what it is.

So those are all the foibles of note that I've found so far. If I find anymore, I will update this post. The bugs are more numerous as opposed to XFCE, and when I used MX-19 I was a diehard XFCE fan. But in MX-21 the single factor that throws the game in Plasma's favor for me is XFCE 4.16's horrendous implementation of CSD, and MX's suboptimal implementation of turning off CSD, but I'll write more about all that in the XFCE beta2 thread.

I will close out my laundry list of complaints by saying that although it's a long list, it is that way not because I disdain MX Linux and am looking to nitpick. Rather it's because I love MX Linux very much, and although I don't know how to code, I want to help make the distro better in any way I can. I have a lot of respect for the MX devs and the work they do, without payment, just because they love FOSS software and want to help people make better use of their computers. I send all my love to dolphin_oracle, Adrian, SwampRabbit, and all the rest of the MX developers.

:yourock:

Posted: **Thu Sep 23, 2021 8:19 am**

I send all my love to dolphin_oracle, Adrian, SwampRabbit, and all the rest of the MX developers.

A good bug report is showing love :)

Posted: **Thu Sep 23, 2021 9:13 am**

7. When using autologin, it logs in once, then after a few seconds logs out and logs in again. I found another post on this thread where an MX dev explained that X restarts because of a special MX fix for making the SDDM power buttons work in SysVinit, and that most people should barely see a flash. And when I login manually, I don't notice X restarting at all. I only see it when I use autologin.

I tried that multiple times, I can't replicate the issue. I think we removed the SDDM fix so that should not play a role. Do you have Beta2 or updated Beta1 to Beta2?

8. Autologin doesn't work when laptop is not plugged in - computer goes to sleep before having a chance to login

That's another thing I don't see. Also seems like a bug in itself if the computer goes to sleep before the log in. Do you have a timezone issue on that computer? Is it set up on the wrong timezone or localtime?

Posted: **Thu Sep 23, 2021 9:20 am**

10. This is not specifically a KDE bug, but it is an MX beta2 bug; I tried the new Job Scheduler app, and I got these strange errors when I attempted to save my crontab edits, and for the record, I double checked my crontab syntax, and there was nothing wrong with it, so I don't know why the errors are raised:

Might be a Job Scheduler issue, but I could not replicate this either, I successfully created a user task. Do you have errors only when you do root tasks? Also what's the string exactly?

Posted: **Thu Sep 23, 2021 9:23 am**

11. This may or may not tie in with the previous error, but the root crontab doesn't work. I know my syntax is correct because I entered the same commands in my personal user crontab (appending doas to the beginning, of course) and it works perfectly. So there's something wrong with the root crontab, and I don't know what it is.

Just tried, switched to root in Job Scheduler added the command to execute every other minute (a test command) saved, and the command executed without issue, again, what is the command?

Posted: **Thu Sep 23, 2021 12:24 pm**

Hello everyone, I've been testing MX 21 KDE Beta 2 for a couple days now and everything is going preety smoothly.

Code: Select all

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: SAMSUNG product: 340XAA/350XAA/550XAA v: P03REP serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: SAMSUNG model: NP350XAA-XF3BR v: SGL9362A08-C01-G006-S0001+10.0.16299 serial: <filter> 
           UEFI: American Megatrends v: P03REP.034.181016.ZW date: 10/16/2018 
Battery:   ID-1: BAT1 charge: 37.6 Wh condition: 37.6/43.1 Wh (87%) volts: 12.6/11.4 
           model: SAMSUNG Electronics SR Real Battery type: Li-ion serial: <filter> status: Full cycles: 163 
           Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter> charge: 55% (should be ignored) 
           rechargeable: yes status: Discharging 
CPU:       Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Kaby Lake family: 6 model-id: 8E (142) 
           stepping: A (10) microcode: EA L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999 
           Speed: 803 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 834 2: 826 3: 838 4: 816 5: 849 6: 842 7: 829 8: 862 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           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 generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Samsung Co driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5917 
           Device-2: NVIDIA GM108M [GeForce MX110] vendor: Samsung Co driver: N/A bus ID: 01:00.0 chip ID: 10de:174e 
           Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.2.1 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Samsung Co driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:9d71 
           Device-2: MacroSilicon USB Video type: USB driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus ID: 1-2:3 
           chip ID: 534d:2109 
           Device-3: BEHRINGER UMC404HD 192k type: USB driver: snd-usb-audio bus ID: 1-3:5 chip ID: 1397:0509 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Samsung Co driver: r8169 v: kernel port: d000 
           bus ID: 02:00.0 chip ID: 10ec:8136 
           IF: eth0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Samsung Co driver: ath10k_pci 
           v: kernel port: d000 bus ID: 03:00.0 chip ID: 168c:0042 
           IF: wlan0 state: up mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-5:7 chip ID: 0cf3:e500 
Drives:    Local Storage: total: 1.16 TiB used: 381.90 GiB (32.2%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: SDM2 scheme: MBR 
           ID-2: /dev/sdb vendor: Western Digital model: WDS240G2G0B-00EPW0 size: 223.58 GiB block size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0000 scheme: GPT 
           ID-3: /dev/sdc type: USB vendor: Generic model: SD MMC size: 29.72 GiB block size: physical: 512 B logical: 512 B 
           serial: <filter> rev: 1.00 scheme: MBR 
Partition: ID-1: / raw size: 74.97 GiB size: 73.24 GiB (97.70%) used: 9.01 GiB (12.3%) fs: ext4 dev: /dev/sdb5 
           ID-2: /home raw size: 93.13 GiB size: 91.17 GiB (97.89%) used: 18.82 GiB (20.6%) fs: ext4 dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 57.0 C mobo: 57.0 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/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
           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/insync.list 
           1: deb http://apt.insync.io/debian bullseye non-free contrib
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.ufam.edu.br/mx/mx/repo/ bullseye main non-free
           2: deb http://mirror.ufam.edu.br/mx/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/teams.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
Info:      Processes: 266 Uptime: 29m Memory: 7.68 GiB used: 2.57 GiB (33.4%) 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

I'm having some very small issues with MX-Comfort-Dark global theme.

When I first changed to the dark theme, some GTK were buggy on the title bar (close, minimize and maximize buttons were not shown). I solved it by going to Settings > Appearance > Application Style > Window Decoration and manually reapplying Breeze Window Decoration.

I'm also having issues with LibreOffice and dark theming, because the icons remain dark.

=

Posted: **Thu Sep 23, 2021 1:42 pm**

Re: previous posts about Vivialdi and Facebook. For whatever reason, the problem with keyboard delays when running Facebook under Vivaldi in MX21ß2KDE has vanished as mysteriously as it appeared! No fan noise either. Strange that it didn't happen in the other distro also running KDE but other little differences could have played a part. As the only difference when I did an update today was MX Package Installer, it must have been the online software running Facebook.

Posted: **Thu Sep 23, 2021 2:28 pm**

pablogvieira wrote: Thu Sep 23, 2021 12:24 pm I'm also having issues with LibreOffice and dark theming, because the icons remain dark.

viewtopic.php?p=653599#p653599
viewtopic.php?p=653609#p653609

Posted: **Thu Sep 23, 2021 6:18 pm**

Installed b2 today but haven't played around with it too much. (wow does it ever boot fast compared to 19.4)

One thing I was delighted to see was Quickshot but it's not installed.

"Could not find the program '/usr/bin/mxfb-quickshot'"

I copied over the one from my Fluxbox install.

Posted: **Thu Sep 23, 2021 6:29 pm**

siamhie wrote: Thu Sep 23, 2021 6:18 pm Installed b2 today but haven't played around with it too much. (wow does it ever boot fast compared to 19.4)

One thing I was delighted to see was Quickshot but it's not installed.

"Could not find the program '/usr/bin/mxfb-quickshot'"

I copied over the one from my Fluxbox install.

you'll want to install mxfb-accessories. (note to self, update mx-fluxbox metapackage).

Posted: **Thu Sep 23, 2021 7:32 pm**

dolphin_oracle wrote: Thu Sep 23, 2021 6:29 pm
siamhie wrote: Thu Sep 23, 2021 6:18 pm Installed b2 today but haven't played around with it too much. (wow does it ever boot fast compared to 19.4)

One thing I was delighted to see was Quickshot but it's not installed.

"Could not find the program '/usr/bin/mxfb-quickshot'"

I copied over the one from my Fluxbox install.
you'll want to install mxfb-accessories. (note to self, update mx-fluxbox metapackage).

Done. Now I can run my custom tint2 panel I created in Fluxbox that has shortcuts to various tools I use including the quickshot button.

Posted: **Thu Sep 23, 2021 10:09 pm**

Adrian wrote: Thu Sep 23, 2021 8:19 am
computerworm01001 wrote: Thu Sep 23, 2021 5:32 am Hello all,I send all my love to dolphin_oracle, Adrian, SwampRabbit, and all the rest of the MX developers.
A good bug report is showing love :)

Hello, Adrian. I'm glad you see it that way, and thank you for reading and responding to my findings.

Adrian wrote: Thu Sep 23, 2021 9:13 am
computerworm01001 wrote: Thu Sep 23, 2021 5:32 am 7. When using autologin, it logs in once, then after a few seconds logs out and logs in again. I found another post on this thread where an MX dev explained that X restarts because of a special MX fix for making the SDDM power buttons work in SysVinit, and that most people should barely see a flash. And when I login manually, I don't notice X restarting at all. I only see it when I use autologin.
I tried that multiple times, I can't replicate the issue. I think we removed the SDDM fix so that should not play a role. Do you have Beta2 or updated Beta1 to Beta2?

I installed directly from the beta2 iso, no upgrade.

Adrian wrote: Thu Sep 23, 2021 8:19 am
computerworm01001 wrote: Thu Sep 23, 2021 5:32 am8. Autologin doesn't work when laptop is not plugged in - computer goes to sleep before having a chance to login
That's another thing I don't see. Also seems like a bug in itself if the computer goes to sleep before the log in. Do you have a timezone issue on that computer? Is it set up on the wrong timezone or localtime?

I have my home time zone set in MX Date & Time, and my hardware clock is set in UTC mode. But I don't think it's a time issue, because when I say autologin isn't working, I'm referring to SDDM autologin, where SDDM logs you in on boot without you having to enter your password. I'm not referring to timed booting with rtcwake, although I do use that concurrently with SDDM autologin to record TV shows while I'm asleep. But rtcwake is working perfectly regardless of my laptop being attached to/detached from wall power, because every night I put my computer in S5, and when I wake up I find it in S3. So rtcwake did its job. It's SDDM that's dropping the ball. Or perhaps some kernel or other low-level power management that's goofing. Because as soon as I wake the computer from sleep by moving the mouse or the lid, SDDM immediately does autologin. And I have my Plasma power settings properly configured to make the machine stay awake, ignore lid closed, etc. So once I'm logged into Plasma, those settings should take over. The problem is making sure my computer gets all the way there without my intervention. For now, my solution is to keep the computer plugged in always. But I don't want to always do that because it wastes electricity to have it plugged in drawing power when I'm asleep.

Adrian wrote: Thu Sep 23, 2021 9:20 am
computerworm01001 wrote: Thu Sep 23, 2021 5:32 am 10. This is not specifically a KDE bug, but it is an MX beta2 bug; I tried the new Job Scheduler app, and I got these strange errors when I attempted to save my crontab edits, and for the record, I double checked my crontab syntax, and there was nothing wrong with it, so I don't know why the errors are raised:
Might be a Job Scheduler issue, but I could not replicate this either, I successfully created a user task. Do you have errors only when you do root tasks? Also what's the string exactly?

I think I figured this out, and I don't think it's a bug after all. You see, when I wanted to use job scheduler to edit the root crontab, I had to use "mx-pkexec job-scheduler" in the terminal because there's no app menu entry for launching Job Scheduler as root. So I had a terminal open on the other side of my screen outputting messages from Job Scheduler in real time. I did it again today, observing more closely, and the message

Code: Select all

CronTime::CronTime Invalid Week Format: ""

outputs whenever I leave a field empty in the Time box, so that's just a normal behavior. Likewise , the message

Code: Select all

CronTime::CronTime Invalid Item count: #

(# is a placeholder for any number) merely denotes how many fields are currently empty in the Time box. And I think that

Code: Select all

CronTime::CronTime Invalid Minute Format: "*/"

just means that I haven't added a number after the slash yet. So I think that there is nothing wrong with the Job Scheduler

Adrian wrote: Thu Sep 23, 2021 9:23 am
11. This may or may not tie in with the previous error, but the root crontab doesn't work. I know my syntax is correct because I entered the same commands in my personal user crontab (appending doas to the beginning, of course) and it works perfectly. So there's something wrong with the root crontab, and I don't know what it is.
Just tried, switched to root in Job Scheduler added the command to execute every other minute (a test command) saved, and the command executed without issue, again, what is the command?

However, the root crontab is definitely malfunctioning, and it doesn't matter what commands I enter. Ones I've tried include rtcwake, pm-suspend, fstrim, and they don't function under root crontab. They function perfectly under my user crontab (with doas tacked on front). Something else changed about it today that I find odd. Just yesterday when I was editing the root crontab in the terminal, the crontab file looked like this:

Code: Select all

# Edit this file to introduce tasks to be run by cron.
# 
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
# 
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
# 
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
# 
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
# 
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
# 
# For more information see the manual pages of crontab(5) and cron(8)
# 
# m h dom mon dow command

Today when I opened it, it looked like this:

Code: Select all

# Home
HOME=/root
# Path
PATH=/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/bin
# Shell
SHELL=/bin/bash

What is that and how did it happen? I'm truly at a loss for what to do now, except to go to doas.conf and just set passwordless for my user any root commands I want to automate and enter them in my user crontab with doas at the beginning of each line. But it would probably be better and more secure to just be able to use the root crontab for root stuff. Or should I maybe just reinstall the cron daemon and use the --purge option?

Again, I thank you very kindly for your helping me, and for the good work you and your colleagues do with MX Linux!

Posted: **Thu Sep 23, 2021 10:19 pm**

I'm not sure PATH really helps in crontab, you probably have to use the full address, I would use "/bin/tar" not "tar"

Posted: **Thu Sep 23, 2021 10:38 pm**

JayM wrote: Thu Sep 23, 2021 2:54 am
I tried installing nvidia drivers with the MX installer which did not help with either.
What happened? Did you get error messages? Your QSI shows that the Nvidia driver 460 was installed, so the driver installation probably succeeded.

Yes, the driver install succeeded. The only error was needing to blacklist the nouvou driver, as is normal with this setup.

If you search the forum you'll find posts about how some laptop manufacturers hard-wire the HDMI port to the Nvidia GPU's bus, and as yours is a bumblebee/optimus system that GPU won't be in use by default. These posts also tell how to work around that so the HDMI port can also be used by the default Intel integrated GPU. That's also explained here: https://wiki.archlinux.org/title/Bumble ... VIDIA_chip.

Bumblebee did not get installed. At the end of the install it showed:

Code: Select all

You can use the new PRIMUS driver built in to the nvidia drivers.
Use "nvidia-run-mx" followed by your application command to use the nvidia graphics

I installed all the Primus stuff, which did install Bumblebee. Followed some of the instructions on the link. Now I can't even open the Nvidia settings, it just flickers in the task manager for a few seconds and dies.

As a troubleshooting measure open a terminal and run
Code: Select all
optirun kcmshell5 kcm_kscreen
with the TV connected and see if it's detected. If it is, then that's what the situation is: HDMI wired to Nvidia's bus. It wouldn't be an MX issue but a hardware design "feature."

Before installing Bumblebee this failed. Tried it using "nvidia-run-mx" instead of "optirun", and the settings window came up, but did not show a second monitor. The TV did show in the Nvidia settings window, but would not let me do anything with it, and now Nvidia settings won't open.
When I plug in the TV, the window

ksnip_20210923-213713.png

pops up asking what to do with the external monitor, but nothing happens when choosing any of the options.

Al

Posted: **Thu Sep 23, 2021 11:44 pm**

Al,

I think there is a disconnect, its not Jay's fault, I think with MX-21 bumblebee usage is being depreciated for the new setup which its to use nvidia-run-mx rather than the whole old way most people are used to.

bigboppercole wrote: Thu Sep 23, 2021 10:38 pm Bumblebee did not get installed. At the end of the install it showed:
Code: Select all
You can use the new PRIMUS driver built in to the nvidia drivers.
Use "nvidia-run-mx" followed by your application command to use the nvidia graphics
I installed all the Primus stuff, which did install Bumblebee. Followed some of the instructions on the link. Now I can't even open the Nvidia settings, it just flickers in the task manager for a few seconds and dies.

Notice it says

"You can use the new PRIMUS driver built in to the nvidia drivers."
AND
"Use "nvidia-run-mx" followed by your application command to use the nvidia graphics"

I think once you got that output you were good to go, obviously using the above then at that point.
Doing all the that other stuff probably broke the setup.

@dolphin_oracle is that correct?

I think we need to get a grasp on this new way of doing things and probably figure out how to handle the common optimus issues like external displays.

Posted: **Fri Sep 24, 2021 12:04 am**

SwampRabbit wrote: Thu Sep 23, 2021 11:44 pm Al,

I think there is a disconnect, its not Jay's fault, I think with MX-21 bumblebee usage is being depreciated for the new setup which its to use nvidia-run-mx rather than the whole old way most people are used to.
bigboppercole wrote: Thu Sep 23, 2021 10:38 pm Bumblebee did not get installed. At the end of the install it showed:
Code: Select all
You can use the new PRIMUS driver built in to the nvidia drivers.
Use "nvidia-run-mx" followed by your application command to use the nvidia graphics
I installed all the Primus stuff, which did install Bumblebee. Followed some of the instructions on the link. Now I can't even open the Nvidia settings, it just flickers in the task manager for a few seconds and dies.
Notice it says
"You can use the new PRIMUS driver built in to the nvidia drivers."
AND
"Use "nvidia-run-mx" followed by your application command to use the nvidia graphics"
I think once you got that output you were good to go, obviously using the above then at that point.
Doing all the that other stuff probably broke the setup.

@dolphin_oracle is that correct?

I think we need to get a grasp on this new way of doing things and probably figure out how to handle the common optimus issues like external displays.

I would agree that following the instructions on the link previously provided broke things.
The external display was still not working after the initial install of the Nvidia drivers though, before doing any of the further instructions.
I would also agree that this is not necessarily a MX-21 beta issue, but an issue none the less.
And audio has been non-existent since the initial install.
Once I get home again, I will try installing MX-19.4 just to see how it goes.

Al

Posted: **Fri Sep 24, 2021 12:13 am**

That's because I haven't installed MX-21 KDE as I don't intend to ever use Plasma, so I was going by the display manager in MX-19 KDE which now that I think of it using an older version of Plasma. You can add a shortcut to whatever the new Plasma's display manager is to your desktop then open it in a text editor to see what the command is and run it in a terminal with "optirun" in front of it (or whatever the new command is to invoke bumblebee/optimus and use the Nvidia GPU. I also don't have any Nvidia optimus laptops, only one hybrid-graphics laptop with two AMD GPUs in it and my desktop PC.)

Posted: **Fri Sep 24, 2021 12:50 am**

bigboppercole wrote: Fri Sep 24, 2021 12:04 am I would agree that following the instructions on the link previously provided broke things.
The external display was still not working after the initial install of the Nvidia drivers though, before doing any of the further instructions.
I would also agree that this is not necessarily a MX-21 beta issue, but an issue none the less.
And audio has been non-existent since the initial install.
Once I get home again, I will try installing MX-19.4 just to see how it goes.

Al

Really appreciate the testing and all! but...

Please remember to bear with us as much as you can.... this is a Beta, people and hours are limited, and not everyone has Nvidia hardware let alone the close same kind of system (like Jay said)

I remember seeing Stevo say he was going to work on updated Nvidia drivers, so it just may be a semi-short waiting game.

I can't recall off the top of my head if the GeForce RTX 2060 Mobile was working under MX-19 AHS or not.
But I can tell you that I have no intent (was pretty much told we weren't either) on updating MX-19 AHS outside of maybe some already staged items going final.... for what that is worth.

The external display like this could be a lot of things, this is a typically an issue with all Optimus laptops, the whole messy breakdowns (buses and junk) of it all are in the forums a few places.
The interwebs is littered with junk about this Nvidia junk doing junk. Its probably just a matter of figuring out what that junk needs configured to post Nvidia driver install.

So first things first, I'd do some hunting for GE75 Raider 10SE + linux or whatever... there is lots of info out there on issues with this Nvidia junk on a per laptop basis out there.

- figure out if anything specific must be done for this laptop and its specific Optimus setup
- verify the Nvidia drivers install fine, this new thingamajig nvidia-run-mx works as it should, then...
- identify the audio issue, which may go away when the first thing is done
- figure out the external display junk

Does it show that it is 12:43AM and I don't want to mess with this junk anymore tonight?

Good night all

Posted: **Fri Sep 24, 2021 2:59 am**

Adrian wrote: Thu Sep 23, 2021 10:19 pm I'm not sure PATH really helps in crontab, you probably have to use the full address, I would use "/bin/tar" not "tar"

Still doesn't work, but that's OK. The only root commands I really need to automate are rtcwake, pm-suspend, and fstrim. So I'll just modify my doas.conf and run them under my user crontab. It's weird though, because I'm creating the exact same crontab entries in the exact same way that I did in Artix, and my root crontab worked perfectly there . . .

But I've bigger fish to fry right now, like what is with the USB mounting error I cited in my original post? I share my computer with another person, and it is very inconvenient for them to not be able to mount USB flash drives under their user account.

Posted: **Fri Sep 24, 2021 7:41 am**

computerworm01001 wrote: Fri Sep 24, 2021 2:59 am
But I've bigger fish to fry right now, like what is with the USB mounting error I cited in my original post? I share my computer with another person, and it is very inconvenient for them to not be able to mount USB flash drives under their user account.

is the drive in question still mounted by the first user?

Posted: **Fri Sep 24, 2021 11:53 am**

MX 21 Beta 2 has many keys in /etc/apt/trusted.gpg and /etc/apt/trusted.gpg.d/*.gpg that are (AFAIK) trusted by apt, even for signing packages in the official repo.

There are also many historic keys (like that or Warren Woodford from MEPIS), medibuntu, many individuals' keys (like Christian Marillat, Adam Blackburn, Hendrik Rittich), many companies' keys (Oracle Corporation, innotek GmbH, Opera Software) etc., in these places where (AFAIK) apt trusts them.

These keys are present in /etc/apt/trusted.gpg and /etc/apt/trusted.gpg.d/*.gpg and these are (AFAIK) trusted by apt, even for signing packages in the official repo:

Code: Select all

$ sudo apt-key list | grep '^uid'
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
uid           [ expired] Warren Woodford (MEPIS Maintainers) <dev@mepis.org>
uid           [ unknown] Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
uid           [ unknown] The Medibuntu Team <medibuntu@sos-sts.com>
uid           [ unknown] Ubuntu CD Image Automatic Signing Key <cdimage@ubuntu.com>
uid           [ unknown] Christian Marillat <marillat@debian.org>
uid           [ unknown] Christian Marillat <marillat@free.fr>
uid           [ unknown] Stefan Lippers-Hollmann (sidux.com) <s.l-h@gmx.de>
uid           [ expired] Opera Software Archive Automatic Signing Key <hostmaster@opera.com>
uid           [ unknown] innotek GmbH (archive signing key) <info@innotek.de>
uid           [ unknown] Adam Blackburn <compwiz18@gmail.com>
uid           [ unknown] Sun Microsystems, Inc. (xVM VirtualBox archive signing key) <info@virtualbox.org>
uid           [ expired] Hendrik Rittich <hendrik.rittich@gmx.de>
uid           [ unknown] Steven Barrett <damentz@gmail.com>
uid           [ unknown] Oracle Corporation (VirtualBox archive signing key) <info@virtualbox.org>
uid           [ expired] Opera Software Archive Automatic Signing Key 2010 <packager@opera.com>
uid           [ unknown] Warren Woodford (MEPIS Maintainers) <dev@mepis.org>
uid           [ unknown] aurelien (Be Free!) <ice.cube@gmx.com>
uid           [ expired] Hendrik Rittich <hendrik.rittich@gmx.de>
uid           [ unknown] Dedinčanov archív balíkov (Debian APT repositary) <dedincan@slavino.sk>
# ^^^^ this is NOT *.debian.org and note that the "repository" is spelt incorrectly
uid           [ expired] David deJong (Dave) <david@daveserver.info>
uid           [ unknown] antiX (this is for the antix repo) <antix@daveserver.info>
uid           [ expired] Opera Software Archive Automatic Signing Key 2012 <packager@opera.com>
uid           [ unknown] aurele (Free your Gnu !) <ice.cube@gmx.com>
uid           [ unknown] MEPIS Community Repository (CR Signing key) <repo@teharris.net>
uid           [ expired] home:gottcode OBS Project <home:gottcode@build.opensuse.org>
uid           [ expired] MX Community Repository <repo@teharris.net>
uid           [ unknown] antiX Linux repo <repo@antixlinux.com>
uid           [ unknown] Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>
uid           [ unknown] Debian Security Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>
uid           [ unknown] Debian Stable Release Key (11/bullseye) <debian-release@lists.debian.org>
uid           [ unknown] Debian Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>
uid           [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>
uid           [ unknown] Debian Stable Release Key (10/buster) <debian-release@lists.debian.org>
uid           [ unknown] Debian Archive Automatic Signing Key (9/stretch) <ftpmaster@debian.org>
uid           [ unknown] Debian Security Archive Automatic Signing Key (9/stretch) <ftpmaster@debian.org>
uid           [ unknown] Debian Stable Release Key (9/stretch) <debian-release@lists.debian.org>
uid           [ unknown] MX-21 Repository <maintainer@mxrepo.com>

apt-key(8) is deprecated, but keys present in /etc/apt/trusted.gpg and /etc/apt/trusted.gpg.d/*.gpg are (AFAIK) trusted by apt, even for signing packages in the official repo.

I think a lot of these keys should be removed in MX 21 Final, because they may pose a security threat (at least in theory) because these keys can be used to successfully sign packages delivered through the official repo.

Posted: **Fri Sep 24, 2021 12:33 pm**

@TimothySimon i think this has already been discussed here on the forums, and a response to that thread was provided, but for sure we should look to see if there is an issue.

If I remember right these keys were being provided externally and by packages themselves

Posted: **Fri Sep 24, 2021 12:35 pm**

I wonder whether Vivaldi using gtk dialog boxes instead of kdialog (which is, in fact, installed in MX-KDE by default) can only be changed by vivaldi having to be rebuilt to use it? If that's the case, then I think that I'll put up with it how it is. It would be wrong to put it onto the devs. It's inconsistent but hardly a huge issue. I'm not having any problems at all with this beta at the moment.

Posted: **Fri Sep 24, 2021 2:19 pm**

SwampRabbit wrote: Fri Sep 24, 2021 12:33 pm @TimothySimon i think this has already been discussed here on the forums, and a response to that thread was provided, but for sure we should look to see if there is an issue.

If I remember right these keys were being provided externally and by packages themselves

I think those keys are of no use, but I would wait for the MX team to confirm that.

I'm especially worried that a lot of them use DSA1024 and one even uses RSA1024 -- both of which are NO LONGER CONSIDERED SAFE .

NIST SP 800-57 Part 1 Rev. 5 ( https://doi.org/10.6028/NIST.SP.800-57pt1r5 ) says that RSA1024 and DSA1024 have <=80 bits of security (Ref: Table 2 of NIST SP 800-57 Part 1 Rev. 5)

Also, note that algorithm/key-size combinations that have been estimated at a maximum security
strength of less than 112 bits (i.e., at ≤ 80, as shown in orange above) are no longer approved for
applying cryptographic protection on federal government information (e.g., encrypting data or
generating a digital signature).

- NIST SP 800-57 Part 1 Rev. 5 Section 5.6.1.1

If it were to be broken (which can be anytime in now - it has just 80 bits of security) , just intercepting HTTP would be enough for anyone (not just the real private key holders) to deliver fake packages in the guise of http://deb.debian.org/debian (which uses HTTP).

BTW I think MX 21 should start using RSA4096 , not RSA2048.
Debian has been using RSA4096 from STRETCH (Debian 9) onward.

Even if it is not broken (no, it will be broken soon) , it greatly increases attack surface , by trusting 37 keys which can validly sign packages and may deliver it in the guise of the official repo.

Consider this situation :
1) Any one of the private key holders whose public key is listed (there are 37 of them) makes and validly signs a malicious package.
2) They deliver it by intercepting the insecure HTTP (over which http://deb.debian.org/debian works).

I trust only 13 of these 37 -- the official Debian, MX, antiX and Ubuntu signing keys.
The rest 24 are not trusted at all (at least in my case).

BTW I got the old discussion (after a lot of searching) at viewtopic.php?f=104&t=64322
and I'm really getting worried.

Posted: **Fri Sep 24, 2021 3:03 pm**

TimothySimon wrote: Fri Sep 24, 2021 2:19 pm Consider this situation :
1) Any one of the private key holders whose public key is listed (there are 37 of them) makes and validly signs a malicious package.
2) They deliver it by intercepting the insecure HTTP (over which http://deb.debian.org/debian works).

package signatures are ignored by apt on Debian. One would need take over the whole repository and deliver a malicious signed release file. The verification of those faked release file would fail as the local public-signing keys are expired. To tidy up expired keys is a kind of houskeeping exercise, which IIRC was already initiated. The described scenario, seems to me not a realistic security thread, as far as I can see.

Posted: **Fri Sep 24, 2021 4:01 pm**

@TimothySimon First why in the world are we pointing to NIST RMF stuff in this Beta thread. I’m not knocking any NIST SP (I mean someone was part of writing quite a few of them), but any standard or framework should not be blindly blanketed on anything just because.

It’s not like we have known compromised keys … like ummm… any Buntu based Distro, Manjaro, and a few others did (might still) awhile ago.

But I’m not worried and I’ll leave that for what it’s worth.

This discussion and any other should be moved out of this Beta thread and into something else like Chat.

Posted: **Fri Sep 24, 2021 7:43 pm**

dolphin_oracle wrote: Fri Sep 24, 2021 7:41 am
computerworm01001 wrote: Fri Sep 24, 2021 2:59 am
But I've bigger fish to fry right now, like what is with the USB mounting error I cited in my original post? I share my computer with another person, and it is very inconvenient for them to not be able to mount USB flash drives under their user account.
is the drive in question still mounted by the first user?

No, it is not. And the problem is not limited to just one flash drive. I've tried several flash drives, and they all raise the same error. I also created a dummy account to further test the phenomenon, and the results were the same. Only my user can mount removable media. I checked group memberships, and they are identical for all users. I also checked the permissions in the /media folder, and got an identical string for both user folders, so that can't be the issue:

Code: Select all

drwxr-x---+ 2 root root 4096

The only other possibility I can think of is that it's a polkit issue, maybe?

Posted: **Sat Sep 25, 2021 1:03 am**

SwampRabbit wrote: Fri Sep 24, 2021 4:01 pm @TimothySimon First why in the world are we pointing to NIST RMF stuff in this Beta thread. I’m not knocking any NIST SP (I mean someone was part of writing quite a few of them), but any standard or framework should not be blindly blanketed on anything just because.

It’s not like we have known compromised keys … like ummm… any Buntu based Distro, Manjaro, and a few others did (might still) awhile ago.

But I’m not worried and I’ll leave that for what it’s worth.

This discussion and any other should be moved out of this Beta thread and into something else like Chat.

I've forked it off to viewtopic.php?f=6&t=66528

BTW I now noticed that DSA1024 generally uses SHA1 , which is ALREADY BROKEN in 2017.
https://en.wikipedia.org/wiki/SHA-1
https://security.googleblog.com/2017/02 ... ision.html
https://shattered.io/

And one DSA1024 key present even now in MX Linux (key id 630239CC130E1A7FD81A27B140976EAF437D05B5) was the matter of a HIGH Importance issue on Ubuntu, fixed back in 2016
( Ref: https://bugs.launchpad.net/ubuntu/+sour ... ug/1363482 )

Posted: **Sat Sep 25, 2021 2:39 am**

Moderator: Everyone, please continue THIS part of the discussion over here: viewtopic.php?p=654259#p654259 so we can continue on topic (which is the KDE beta) in here, thanks.

Posted: **Sat Sep 25, 2021 12:16 pm**

Installation went smooth with no issues. Installed my rtl8814 drivers and emby-server from HDD. Added xscreensaver's extra goodies from MXPI. Added mxfb-quickshot from my Fluxbox installation. (ksnip is nice but I like the simplicity of quickshot)

Boots lightning fast and runs rock solid. Well done.

Code: Select all

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 
  init=/lib/systemd/systemd 
  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: Desktop System: ASUSTeK product: K30BF_M32BF_A_F_K31BF_6 v: N/A 
  serial: <filter> 
  Mobo: ASUSTeK model: K30BF_M32BF_A_F_K31BF_6 v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 0401 date: 04/29/2015 
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse 
  serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
  status: Discharging 
  Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360 
  serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
  status: Discharging 
CPU:
  Topology: Quad Core 
  model: AMD A10-7800 Radeon R7 12 Compute Cores 4C+8G bits: 64 
  type: MCP arch: Steamroller family: 15 (21) model-id: 30 (48) 
  stepping: 1 microcode: 6003106 L2 cache: 2048 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 27928 
  Speed: 1640 MHz min/max: 1400/3500 MHz boost: enabled 
  Core speeds (MHz): 1: 1640 2: 1654 3: 1870 4: 1571 
  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: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK 
  driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:130f 
  Device-2: AMD Oland PRO [Radeon R7 240/340] vendor: ASUSTeK 
  driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6613 
  Display: x11 server: X.Org 1.20.13 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: AMD OLAND (DRM 2.50.0 5.10.0-8-amd64 LLVM 12.0.1) 
  v: 4.5 Mesa 21.2.1 direct render: Yes 
Audio:
  Device-1: AMD Kaveri HDMI/DP Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:01.1 chip ID: 1002:1308 
  Device-2: AMD FCH Azalia vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1022:780d 
  Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 
  7000 Series] 
  vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  chip ID: 1002:aab0 
  Sound Server: ALSA v: k5.10.0-8-amd64 
Network:
  Device-1: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter 
  vendor: AzureWave driver: rtl8821ae v: kernel port: d000 
  bus ID: 04:00.0 chip ID: 10ec:8821 
  IF: wlan0 state: down mac: <filter> 
  Device-2: NetGear Nighthawk A7000 802.11ac Wireless Adapter AC1900 
  [Realtek 8814AU] 
  type: USB driver: 8814au bus ID: 3-2:2 chip ID: 0846:9054 
  serial: <filter> 
  IF: wlan1 state: up mac: <filter> 
Drives:
  Local Storage: total: 1.36 TiB used: 549.35 GiB (39.3%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 500GB 
  size: 465.76 GiB block size: physical: 512 B logical: 512 B 
  speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1ER162 
  size: 931.51 GiB block size: physical: 4096 B logical: 512 B 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC43 
  scheme: MBR 
Partition:
  ID-1: / raw size: 130.00 GiB size: 126.90 GiB (97.62%) 
  used: 7.96 GiB (6.3%) fs: ext4 dev: /dev/sda5 
  ID-2: /home raw size: 100.00 GiB size: 97.87 GiB (97.87%) 
  used: 1.24 GiB (1.3%) fs: ext4 dev: /dev/sda6 
  ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) 
  dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 4.1 C mobo: N/A 
  Fan Speeds (RPM): N/A 
  GPU: device: radeon temp: N/A device: radeon temp: 35 C 
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: 208 Uptime: 56m Memory: 14.60 GiB used: 1.77 GiB (12.1%) 
  Init: systemd v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 
  alt: 10 Shell: quick-system-in running in: quick-system-in 
  inxi: 3.0.36

Posted: **Sat Sep 25, 2021 12:28 pm**

siamhie wrote: Sat Sep 25, 2021 12:16 pm Installation went smooth with no issues. Installed my rtl8814 drivers and emby-server from HDD.

Out of curiosity, which rtl8814 exactly, what adapter do you have?

I want to tighten up our rtl packages a bit in the coming weeks.

Edit: duh NetGear Nighthawk A7000

Posted: **Sat Sep 25, 2021 12:53 pm**

SwampRabbit wrote: Sat Sep 25, 2021 12:28 pm
siamhie wrote: Sat Sep 25, 2021 12:16 pm Installation went smooth with no issues. Installed my rtl8814 drivers and emby-server from HDD.
Out of curiosity, which rtl8814 exactly, what adapter do you have?

I want to tighten up our rtl packages a bit in the coming weeks.

Edit: duh NetGear Nighthawk A7000

I came across three developers on GitHub releasing the Nighthawk drivers and chose Aircrack-ng's driver because it seems his/hers is the most recent release.

https://github.com/aircrack-ng

Posted: **Sat Sep 25, 2021 12:57 pm**

@siamhie thanks, I try to avoid the aircrack ones if possible, but good to know that one works.

Posted: **Sat Sep 25, 2021 1:00 pm**

SwampRabbit wrote: Sat Sep 25, 2021 12:57 pm @siamhie thanks, I try to avoid the aircrack ones if possible, but good to know that one works.

Which one/ones would you recommend? Will you have the rtl8814 available by final release time?

Posted: **Sat Sep 25, 2021 7:36 pm**

siamhie wrote: Sat Sep 25, 2021 1:00 pm Which one/ones would you recommend? Will you have the rtl8814 available by final release time?

Usually anything without frame injection, promiscuous mode, that kind of stuff. Also ones that support as many kernels as possible and are known to be very stable with as many adapters as possible. I don't want to update something like this constantly when new kernels come out and it should work on normal MX and AHS OOTB.

I looked quick the aircrack one has patches waiting to be pulled in order to build on kernels >=5.12, so I'll grab that and get to it as soon as I can, but its gonna be awhile... but more than enough time for final release.

Posted: **Sat Sep 25, 2021 8:41 pm**

SwampRabbit wrote: Sat Sep 25, 2021 7:36 pm
siamhie wrote: Sat Sep 25, 2021 1:00 pm Which one/ones would you recommend? Will you have the rtl8814 available by final release time?
Usually anything without frame injection, promiscuous mode, that kind of stuff. Also ones that support as many kernels as possible and are known to be very stable with as many adapters as possible. I don't want to update something like this constantly when new kernels come out and it should work on normal MX and AHS OOTB.

I looked quick the aircrack one has patches waiting to be pulled in order to build on kernels >=5.12, so I'll grab that and get to it as soon as I can, but its gonna be awhile... but more than enough time for final release.

Take your time. I have my copy that will work (rtl8814au-5.8.5.1) and I'm not sure if there are other members that run this dongle or require this particular driver, so it's perfectly fine if it doesn't make it to Final.

Posted: **Sat Sep 25, 2021 9:30 pm**

@siamhie based on the potential timeline for maybe another Beta, RC, and Final... we have more than enough time to get it into Final.
I'm just busy away from home all next week and I'd like to verify the package with you (at least) cause you can test it. Its really not KDE specific... so lets follow up later outside of this thread once I get it packaged.

Posted: **Sat Sep 25, 2021 11:03 pm**

SwampRabbit wrote: Sat Sep 25, 2021 9:30 pm @siamhie based on the potential timeline for maybe another Beta, RC, and Final... we have more than enough time to get it into Final.
I'm just busy away from home all next week and I'd like to verify the package with you (at least) cause you can test it. Its really not KDE specific... so lets follow up later outside of this thread once I get it packaged.

OK, I can do that. I'm dual booting Fluxbox/KDE, so when I install the driver on a new install, I copy that folder (sits on a spare HDD) to each OS and run make then make dkms_install. I can just run make dkms_remove and try the new one.

Posted: **Mon Sep 27, 2021 3:36 am**

SwampRabbit wrote: Sat Sep 25, 2021 9:30 pm @siamhie based on the potential timeline for maybe another Beta, RC, and Final... we have more than enough time to get it into Final.

Approximately when do you guys expect to have an RC ready or a final release? I'm so impatient for MX 21. This is the real Windows 11 for me pretty much.

Posted: **Mon Sep 27, 2021 4:08 am**

It'll be ready when it is ready. We don't even know exactly. There is a lot going on behind the scenes, so.. patience

Posted: **Mon Sep 27, 2021 4:23 am**

Arnox wrote: Mon Sep 27, 2021 3:36 am
SwampRabbit wrote: Sat Sep 25, 2021 9:30 pm @siamhie based on the potential timeline for maybe another Beta, RC, and Final... we have more than enough time to get it into Final.
Approximately when do you guys expect to have an RC ready or a final release? I'm so impatient for MX 21. This is the real Windows 11 for me pretty much.

Impatience -> Doing in a hurry -> Less stability, less polish and more problems.

Patience -> Take your own time -> More stability, more polish and less problems.

Posted: **Mon Sep 27, 2021 3:58 pm**

Yeah it's easy to get impatient when the betas are smoother than most distros releases,but like the sign in my shop says "Do you want it right or do you want it right now? : ]

Posted: **Mon Sep 27, 2021 10:49 pm**

heywoodidaho wrote: Mon Sep 27, 2021 3:58 pm Yeah it's easy to get impatient when the betas are smoother than most distros releases

To be a little fair, MX is "cheating" by utilizing Debian Stable. lol

Posted: **Tue Sep 28, 2021 12:56 pm**

I have installed and used Debian Stable; while stable, it is missing a lot of what I desire in a distro.
And I never got it anywhere near to what the MX team does.
I was fortunate to be distro hopping in March 2014 when the first release was almost ready.
It did nearly all I wanted plus some great bonuses out of the box; still missing in Debian.

Also, the real push is getting all the MX magic to work with all the changes in the new Stable.
So, in the end, I get a Debian Stable on steroids with the bells and whistles I prefer.
And, all the updated MX magic works right out of the box.

Posted: **Tue Sep 28, 2021 2:03 pm**

heywoodidaho wrote: Mon Sep 27, 2021 3:58 pm Yeah it's easy to get impatient when the betas are smoother than most distros releases,but like the sign in my shop says "Do you want it right or do you want it right now? : ]

+1 Definitely!

Posted: **Tue Sep 28, 2021 2:07 pm**

For what is worth, we keep upgrading out packages and improving stuff even after the release. But of course we'd like to get most of the annoying bugs out of the way before the release.

Posted: **Tue Sep 28, 2021 4:19 pm**

My "L" key does't work on my Logitech keyboard.
MX sucks !
Nah. It's slick as it has been forever Someone once said.. when it's ready ? Clem? Ben? Coop ? Me ? I'm 68
It damn sure was NOT CannonBall ! Next update Aug 2022 3 am. fer sure dude.

Um I probably shouldn't say this.
I asked Clem about an LMDE/XFCE
Ummm. He said MX....Seriously

Posted: **Tue Sep 28, 2021 4:20 pm**

Adrian wrote: Thu Sep 23, 2021 9:13 am
7. When using autologin, it logs in once, then after a few seconds logs out and logs in again. I found another post on this thread where an MX dev explained that X restarts because of a special MX fix for making the SDDM power buttons work in SysVinit, and that most people should barely see a flash. And when I login manually, I don't notice X restarting at all. I only see it when I use autologin.
I tried that multiple times, I can't replicate the issue. I think we removed the SDDM fix so that should not play a role. Do you have Beta2 or updated Beta1 to Beta2?

I experienced that yesterday when I was working on one of manyroads new conky. When I was enabling and disabling the conky from the conky manager to see the changes, I would sometimes get logged out and logged back in but I would have to reconnect to the internet (password saved-so just select connect). I was booting back and forth between SysV and systemd so I'm not sure which init it was happening in. That seems to be the only time I've experienced this.

Code: Select all

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 init=/lib/systemd/systemd 
           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: Desktop System: ASUSTeK product: K30BF_M32BF_A_F_K31BF_6 v: N/A serial: <filter> 
           Mobo: ASUSTeK model: K30BF_M32BF_A_F_K31BF_6 v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 0401 
           date: 04/29/2015 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter> charge: 55% (should be ignored) 
           rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360 serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Quad Core model: AMD A10-7800 Radeon R7 12 Compute Cores 4C+8G bits: 64 type: MCP 
           arch: Steamroller family: 15 (21) model-id: 30 (48) stepping: 1 microcode: 6003106 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27929 
           Speed: 2668 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 2668 2: 2693 3: 3109 4: 2980 
           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: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: radeon 
           v: kernel bus ID: 00:01.0 chip ID: 1002:130f 
           Device-2: Advanced Micro Devices [AMD/ATI] Oland PRO [Radeon R7 240/340] vendor: ASUSTeK driver: radeon 
           v: kernel bus ID: 01:00.0 chip ID: 1002:6613 
           Display: x11 server: X.Org 1.20.13 driver: ati,radeon unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD OLAND (DRM 2.50.0 5.10.0-8-amd64 LLVM 12.0.1) v: 4.5 Mesa 21.2.1 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 00:01.1 chip ID: 1002:1308 
           Device-2: Advanced Micro Devices [AMD] FCH Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1022:780d 
           Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aab0 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter vendor: AzureWave driver: rtl8821ae 
           v: kernel port: d000 bus ID: 04:00.0 chip ID: 10ec:8821 
           IF: wlan0 state: down mac: <filter> 
           Device-2: NetGear Nighthawk A7000 802.11ac Wireless Adapter AC1900 [Realtek 8814AU] type: USB driver: 8814au 
           bus ID: 4-2:2 chip ID: 0846:9054 serial: <filter> 
           IF: wlan1 state: up mac: <filter> 
Drives:    Local Storage: total: 1.36 TiB used: 549.33 GiB (39.3%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB block size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC43 temp: 29 C scheme: MBR 
Partition: ID-1: / raw size: 130.00 GiB size: 126.90 GiB (97.62%) used: 8.09 GiB (6.4%) fs: ext4 dev: /dev/sda5 
           ID-2: /home raw size: 100.00 GiB size: 97.87 GiB (97.87%) used: 1.45 GiB (1.5%) fs: ext4 dev: /dev/sda6 
           ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 4.1 C mobo: N/A 
           Fan Speeds (RPM): N/A 
           GPU: device: radeon temp: N/A device: radeon temp: 35 C 
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: 198 Uptime: 6m Memory: 14.60 GiB used: 1.35 GiB (9.2%) Init: systemd v: 247 runlevel: 5 
           default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36

Posted: **Tue Sep 28, 2021 4:23 pm**

When I was enabling and disabling the conky from the conky manager to see the changes, I would sometimes get logged out

Weird, sounds to me like a conky issue, but why would conky-manager log the computer off? Beats me...

Posted: **Tue Sep 28, 2021 4:28 pm**

Does this happen with a particular conky, or is it just random?

Is there anything in the syslog maybe?

Posted: **Tue Sep 28, 2021 10:39 pm**

Adrian wrote: Tue Sep 28, 2021 4:23 pm
When I was enabling and disabling the conky from the conky manager to see the changes, I would sometimes get logged out
Weird, sounds to me like a conky issue, but why would conky-manager log the computer off? Beats me...

I'm only guessing at this point but when I was loading and unloading the new conky to see if the new changes take effect, conky manager has to reload the conky and KDE threw up a fit. The conky's shipped with MX doesn't display this behaviour (I tested about 6 different ones- load then unload, then load again).

Eadwine Rose wrote: Tue Sep 28, 2021 4:28 pm Does this happen with a particular conky, or is it just random?

Is there anything in the syslog maybe?

Yes, it was one conky. manyroads wrote a new conky and when I finished setting it up in Fluxbox, I copied the conky over to KDE but there were some variables missing that KDE needed for it to display properly. So in the process of adding and removing variables, KDE logged me out and right back in. All the other conky's that ship with MX have no problem and now that the conky is finished for KDE, I'm no longer experiencing the issue. Just odd.

This is the new conky he wrote.
viewtopic.php?p=654460#p654460

Posted: **Wed Sep 29, 2021 3:04 pm**

Eadwine Rose wrote: Tue Sep 28, 2021 4:28 pm Does this happen with a particular conky, or is it just random?

Is there anything in the syslog maybe?

@Eadwine Rose Even tho the system is running fine, I'm curious as to why it happened in the first place. What should I look for in the syslog? It goes back to the 23rd but this happened on the 26th or 27th. (if it helps, when I was logged out of my session, then logged back in, I had to reconnect to the router--my USB wifi nic is on wlan1)

Posted: **Thu Sep 30, 2021 2:21 pm**

All works fine on my Thinkpad T420 except the wifi connection. The initial wifi connection is attempted and fails multiple times before being abandoned. Likewise when resuming from sleep the connection rarely re-establishes. Manually disconnecting then manually reconnecting gets an immediate connection. Attached is a redacted syslog showing both failed and successful connections.

I've used this as a daily driver for the last 3 weeks and this is the only issue encountered. Tasks include the usual browsing, email and text editing up to compiling code from source. All done without missing a beat!

Thanks to all concerned in developing this. MXLinux continues to be way better than anything else! :)

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM Distro: MX-21_x64 Wildflower August 22  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 4180CV1 v: ThinkPad T420 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 4180CV1 serial: <filter> UEFI: LENOVO v: 83ET69WW (1.39 ) date: 03/26/2012 
Battery:   ID-1: BAT0 charge: 18.5 Wh condition: 45.2/47.5 Wh (95%) volts: 10.7/10.8 model: LGC 42T4911 type: Li-ion 
           serial: <filter> status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i7-2620M bits: 64 type: MT MCP arch: Sandy Bridge family: 6 model-id: 2A (42) 
           stepping: 7 microcode: 2F L2 cache: 4096 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21530 
           Speed: 1638 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 1638 2: 1473 3: 2028 4: 1993 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           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 generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Lenovo ThinkPad T420 driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:0126 
           Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 
           resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 21.2.1 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:1c20 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo ThinkPad T520 driver: e1000e v: kernel port: 5080 
           bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 chip ID: 8086:4238 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 223.57 GiB used: 25.48 GiB (11.4%) 
           ID-1: /dev/sda vendor: Crucial model: CT240BX200SSD1 size: 223.57 GiB block size: physical: 4096 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: .4 temp: 26 C scheme: GPT 
Partition: ID-1: / raw size: 217.15 GiB size: 212.68 GiB (97.94%) used: 25.38 GiB (11.9%) fs: ext4 dev: /dev/dm-0 
           ID-2: /boot raw size: 512.0 MiB size: 487.2 MiB (95.16%) used: 104.3 MiB (21.4%) fs: ext4 dev: /dev/sda2 
           ID-3: swap-1 size: 5.61 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default) 
           dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 40.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 1993 
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
           Active apt repos in: /etc/apt/sources.list.d/mt-ansible.ppa.list 
           1: deb http://ppa.launchpad.net/ansible/ansible/ubuntu trusty main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/nordvpn.list 
           1: deb https://repo.nordvpn.com//deb/nordvpn/debian stable main
Info:      Processes: 257 Uptime: 1h 11m Memory: 3.72 GiB used: 1.69 GiB (45.4%) Init: systemd v: 247 runlevel: 5 default: 5 
           Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36

Posted: **Thu Sep 30, 2021 2:45 pm**

@ladle-hill

i am sure the devs will put that right for the next beta but for now

to automatically connect, go to : configure network connections > check 'all users may connect to this network'

Posted: **Thu Sep 30, 2021 3:00 pm**

Thank you! I really thought I had tried that but when I looked it was unchecked. Checking it seems to have done the trick :)

Posted: **Sun Oct 03, 2021 8:33 am**

I noticed some weird things after last update:
- restart and shutdown icons missing again from the Application Menu (logout icon remains)
- date on login screen is in unknown language (RTL?)

Could this be related to any of the desktop-defaults-mx* packages?

Here's my info:

Code: Select all

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 
           init=/lib/systemd/systemd 
           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: 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: Single Core model: Intel Core i7-4720HQ bits: 64 type: MCP arch: Haswell family: 6 model-id: 3C (60) 
           stepping: 3 microcode: N/A L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 5187 
           Speed: 2594 MHz min/max: N/A Core speed (MHz): 1: 2594 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT Host state unknown 
           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: Unknown: Dependent on hypervisor status 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.13 driver: vmware unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1648x860~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 12.0.1 256 bits) v: 4.5 Mesa 21.2.1 compat-v: 3.1 direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel 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: 15.09 GiB used: 254.78 GiB (1688.9%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 15.09 GiB block size: physical: 512 B logical: 512 B 
           speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 14.18 GiB size: 13.85 GiB (97.71%) used: 7.76 GiB (56.0%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 896.0 MiB 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 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 https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye main non-free
           2: deb https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye ahs
Info:      Processes: 183 Uptime: 7m Memory: 5.71 GiB used: 968.8 MiB (16.6%) Init: systemd v: 247 runlevel: 5 default: 5 
           Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in running in: quick-system-in inxi: 3.0.36

I only have two locales enabled (en_US and sl_SI), this is my /etc/default/locale:

Code: Select all

#  File generated by update-locale
LANG=en_US.UTF-8
LC_TIME=si_SL.UTF-8

Posted: **Mon Oct 04, 2021 3:14 pm**

Here's the follow up...
I re-added the missing icons (right click, add to favourites) and they are still there after a few reboots.
That weird language thingie on the login screen was a result of a typo in the locale file (si_SL != sl_SI).

Posted: **Tue Oct 05, 2021 1:27 am**

@siamhie there is a 8814 dkms in the repo (obviously will work on any MX-21 version) waiting for your generous testing and feedback

Posted: **Tue Oct 05, 2021 9:09 am**

SwampRabbit wrote: Tue Oct 05, 2021 1:27 am @siamhie there is a 8814 dkms in the repo (obviously will work on any MX-21 version) waiting for your generous testing and feedback

@SwampRabbit Removed my copy and installed rtl8814 from testing. Installation went without a hitch

rtl8814.jpg

Only thing I see is there's no description, other than that, works just fine.

Code: Select all

$ sudo lshw -class network -short
H/W path                 Device      Class          Description
===============================================================
/0/100/15.3/0            wlan0       network        RTL8821AE 802.11ac PCIe Wireless Network Adapter
/1                       wlan1       network        Wireless interface

My 200MB symmetrical connection

Speedtest.png

Posted: **Tue Oct 05, 2021 11:15 am**

@siamhie I have no clue why it isn't showing up with a description, I used the one you referenced but included a pending PR to allow this to work with kernels >=5.12
https://github.com/aircrack-ng/rtl8814au/pull/73
I don't see anything in that commit that would change the adapter from being displayed. This driver doesn't seem to be getting updated, not sure if an issue on the GitHub would get addressed or not.

Do you mind testing with kernel 5.14?
Just to verify it works at least.

MX Linux Forum

MX-21 KDE/plasma beta 2 feedback thread

MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread

Re: MX-21 KDE/plasma beta 2 feedback thread