MX-21 KDE/plasma RC1 feedback
Re: MX-21 KDE/plasma RC1 feedback
It happens to me that if I have files in the /home partition and I cut to paste them in my backup partition, I get a message saying: "Access denied to /media/Files/..." (see image) However the action is fulfilled, but they are still grayed out in /home (second image). If I change directory, when I come back; they have already been deleted from the sending folder and are still in the destination folder. The annoying thing is the message that appears and the gray color of the files, otherwise the files are changed and are not damaged. (third image)
Translated with www.DeepL.com/Translator (free version)
Translated with www.DeepL.com/Translator (free version)
You do not have the required permissions to view the files attached to this post.
No todos ignoramos las mismas cosas. 

Re: MX-21 KDE/plasma RC1 feedback
The Print key works fine on T430 but I was left staring at the Ksnip?
Tried New and it became a Screen capture app.
Obviously, been a long time since I used KDE.
Tried New and it became a Screen capture app.
Obviously, been a long time since I used KDE.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
__kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
__Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
HP Ryzen 5 17-cp3xxx with MX23.4 AHS & Liquorix 6.10-12~mx23ahs amd64
__kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
__Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
HP Ryzen 5 17-cp3xxx with MX23.4 AHS & Liquorix 6.10-12~mx23ahs amd64
Re: MX-21 KDE/plasma RC1 feedback
Yeah I have been getting that auto reconnect bug, how odd.
Its too bad it can't get fixed without manual intervention, it's not a terrible issue nor a dealbreaker, but still very strange it can't get fixed by the MX team at this point (shrugs)
I am not complaining mind you, but I never had this issue with other KDE distros that use sudo.
It even works with sparkylinux's recent release, maybe the MX devs could see what they did to circumnavigate this?
Not saying sparky is better mind you, but when i gave it a spin with its recent Sparky 6.0 “Po Tolo” release it auto reconnected.
Since I am no developer or coder I have no idea how they fixed it but it is worth investigating since sparkylinux 6.0 and MX21 share the same debian bullseye base.
Its too bad it can't get fixed without manual intervention, it's not a terrible issue nor a dealbreaker, but still very strange it can't get fixed by the MX team at this point (shrugs)
I am not complaining mind you, but I never had this issue with other KDE distros that use sudo.
It even works with sparkylinux's recent release, maybe the MX devs could see what they did to circumnavigate this?
Not saying sparky is better mind you, but when i gave it a spin with its recent Sparky 6.0 “Po Tolo” release it auto reconnected.
Since I am no developer or coder I have no idea how they fixed it but it is worth investigating since sparkylinux 6.0 and MX21 share the same debian bullseye base.
Re: MX-21 KDE/plasma RC1 feedback
Hello i am new in this Forum!
I am not sure if it is there by default but although i created a root user during the installation process i have only one administrator user the user i created as normal user!
In KDE settings i ve tried to create a new root user but is impossible! No error at all!
Thanks in advance
I am not sure if it is there by default but although i created a root user during the installation process i have only one administrator user the user i created as normal user!
In KDE settings i ve tried to create a new root user but is impossible! No error at all!
Thanks in advance
Re: MX-21 KDE/plasma RC1 feedback
I think you posted in the wrong sub forum there matey.sthras wrote: Fri Oct 08, 2021 1:11 pm Hello i am new in this Forum!
I am not sure if it is there by default but although i created a root user during the installation process i have only one administrator user the user i created as normal user!
In KDE settings i ve tried to create a new root user but is impossible! No error at all!
Thanks in advance
Are you using MX 19?
Re: MX-21 KDE/plasma RC1 feedback
No MX-21 KDE/plasma RC1
Re: MX-21 KDE/plasma RC1 feedback
In /etc/passwd there is a root user but kde use only as administrator the normal user i have already created!
Re: MX-21 KDE/plasma RC1 feedback
Re missing shutdown icon in menu
Neither do I.Needless to say I don't see this behavior either in Live or Installed...
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: MX-21 KDE/plasma RC1 feedback
Assuming that is the issue, how can I remove that 32 bit filter? (By the way, I did get Steam installed already with the Popular Applications tab.) Also, VeraCrypt is not listed in the Flatpaks tab either.dolphin_oracle wrote: Fri Oct 08, 2021 7:07 amSteam in Debian is a 32 bit package and sometimes gets filtered out by default. Try installing steam:i386Arnox wrote: Fri Oct 08, 2021 6:34 amOn that note, it seems some packages are missing from the MX Package Installer. Notably Steam (can be installed via the Popular Applications tab though) and VeraCrypt. Synaptic's not installed either, though I'm not sure if that's intended or not. Doing an apt-get install for VeraCrypt also results in it finding nothing.davemx wrote: Thu Oct 07, 2021 6:31 pm Flatpaks not working in the KDE RC1. I installed Freetube from there in the Beta version so I know it used to work on my computer.
By the way, no, I didn't touch the default respositories.
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 splash init=/lib/systemd/systemd Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM Distro: MX-21_KDE_RC1_x64 Wildflower October 5 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 2802 date: 10/22/2020 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 serial: <filter> charge: 55% (should be ignored) rechargeable: yes status: Discharging CPU: Topology: 6-Core model: AMD Ryzen 5 3600XT bits: 64 type: MT MCP arch: Zen family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 91034 Speed: 2106 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2106 2: 2508 3: 2259 4: 2067 5: 2146 6: 2140 7: 2281 8: 2133 9: 2053 10: 2303 11: 2119 12: 2232 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, IBPB: conditional, STIBP: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA TU104GL [Quadro RTX 4000] driver: nvidia v: 470.63.01 bus ID: 09:00.0 chip ID: 10de:1eb1 Display: x11 server: X.Org 1.20.13 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: kwin_x11 resolution: 1920x1080~60Hz OpenGL: renderer: Quadro RTX 4000/PCIe/SSE2 v: 4.6.0 NVIDIA 470.63.01 direct render: Yes Audio: Device-1: NVIDIA TU104 HD Audio driver: snd_hda_intel v: kernel bus ID: 09:00.1 chip ID: 10de:10f8 Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 0b:00.4 chip ID: 1022:1487 Device-3: Cubeternet Live Streaming USB Device type: USB driver: snd-usb-audio,uvcvideo bus ID: 2-1:2 chip ID: 1e4e:7102 serial: <filter> Sound Server: ALSA v: k5.10.0-8-amd64 Network: Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: f000 bus ID: 05:00.0 chip ID: 8086:1539 IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 1.93 TiB used: 11.72 GiB (0.6%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXM7 scheme: GPT ID-2: /dev/sda vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 1A01 temp: 41 C scheme: MBR ID-3: /dev/sdb vendor: Kingston model: SUV400S37120G size: 111.79 GiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 96R9 temp: 37 C scheme: GPT Partition: ID-1: / raw size: 105.91 GiB size: 103.69 GiB (97.90%) used: 11.72 GiB (11.3%) fs: ext4 dev: /dev/sdb2 ID-2: swap-1 size: 5.62 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sdb3 Sensors: System Temperatures: cpu: 63.8 C mobo: N/A gpu: nvidia temp: 50 C Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 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: 275 Uptime: 1h 13m Memory: 15.60 GiB used: 2.15 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
In any case, the really good news though is that MX21 is working super beautifully for me. the missing packages seem to be the only problem. 21 even fixed a minor issue of KDE desktop screen tearing I was experiencing before with 19.4.