MX-19.2 KDE Beta 1 feedback thread

[torxxl]

Installation pour la Suisse.
Je retrouve le même problème que sur la version XFCE.
Un bog avait été ouvert.
Si je choisi à l'installation suisse(ch) j'ai une installation en anglais et les paramètres, région, clavier sont anglais anglais.
J'éspère qu'un jour MX arrivera à corriger ce problème.

[Sparky]

Here's another vote for the more whiskerlike menu, too.

You have a choice of menu styles in KDE. Right click on the launcher and choose alternatives.
Making the menu more whisker like would lessen the separation of KDE to XFCE

[i_ri]

Hello dolphin_oracle and everyone
from MX 19.2ahs_KDE-beta1 live on

Code: Select all

System:    Host: mx1 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 
           dm: SDDM Distro: MX-19.2_KDE-beta1_x64 patito feo July 5  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: TOSHIBA product: Satellite L355D v: PSLE8U-00L00X serial: <root required> Chassis: AMD 
           type: 10 serial: <root required> 
           Mobo: ATI model: Ant3 serial: <root required> BIOS: Insyde v: 1.10 date: 05/23/2008 
Battery:   ID-1: BAT0 charge: 18.4 Wh condition: 70.6/49.2 Wh (144%) volts: 12.3/12.3 model: PA3534U-1BRS serial: 0838 
           status: Charging 
CPU:       Topology: Dual Core model: AMD Athlon X2 QL-60 bits: 64 type: MCP arch: Turion X2 Ultra rev: 1 L2 cache: 1024 KiB 
           bogomips: 7580 
           Speed: 950 MHz min/max: 950/1900 MHz Core speeds (MHz): 1: 950 2: 1900 
           Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cmp_legacy constant_tsc cpuid cr8_legacy cx16 cx8 de extapic 
           extd_apicid fpu fxsr fxsr_opt ht hw_pstate lahf_lm lbrv lm mca mce mmx mmxext msr mtrr nonstop_tsc nopl nrip_save 
           nx osvw pae pat pge pni pse pse36 rdtscp rep_good sep skinit sse sse2 svm svm_lock syscall tsc vme vmmcall 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] RS780MC [Mobility Radeon HD 3100] vendor: Toshiba America Info Systems 
           driver: radeon v: kernel bus ID: 01:05.0 chip ID: 1002:9613 
           Display: x11 server: X.Org 1.20.4 driver: radeon FAILED: ati unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1440x900~60Hz 
           OpenGL: renderer: AMD RS780 (DRM 2.50.0 / 5.6.0-2-amd64 LLVM 10.0.0) v: 3.3 Mesa 20.0.7 compat-v: 3.0 
           direct render: Yes 
Network:   Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet vendor: Toshiba America Info Systems RTL810xE 
           driver: r8169 v: kernel port: 3000 bus ID: 04:00.0 chip ID: 10ec:8136 
           Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter vendor: Askey WLL3141 802.11bg driver: ath5k 
           v: kernel port: 3000 bus ID: 05:00.0 chip ID: 168c:001c 
Drives:    Local Storage: total: 247.79 GiB used: 2.00 GiB (0.8%) 
Info:      Processes: 226 Uptime: 6m Memory: 2.68 GiB used: 577.2 MiB (21.0%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: yakuake inxi: 3.0.36 
demo@mx1:~

[torxxl]

Faut-il rendre le menu plus moustache ?
Je ne sais pas le % de personnes qui vont passer de XFCE à KDE dans MX Linux et le % d'utilisateur qui vont passer à MX Linux depuis une autre distribution.
Personellement n'ayant pas trop aimer XFC je suis sur une autre distribution et je vais venir sur XFCE avec un grand bonheur pour KDE, mais j'éspère trouvé un KDe pas trop modifié qui resemble à mon KDe que j'ai dans d'autres distributions.

[JayM]

Try the Application Menu widget rather than Application Launcher. If the column of icons on the left could be made smaller (and I think the can, I just don't remember how) it looks the closest to Whisker Menu of the choices that we have. I installed Excalibur Menu as it looked like it might be good but it doesn't appear to work in this version of Plasma.

[JayM]

Twice today after installing a new widget, which gets added at the far right of the default panel, when I try to move it to where I want it my mouse's buttons have stopped working. The cursor moves, the keyboard still works and the mouse still functions normally in my host OS (MX 19.2 AHS with Xfce.) MX KDE B1 is running as a guest OS in VBox 6.1.6 with 1MB RAM, 128KB VRAM, 2 CPUs, 25GB virtual disk, VBoxSVGA video. The mouse is an A4Tech wireless with a fresh battery.

Code: Select all

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

[Sparky]

Twice today after installing a new widget, which gets added at the far right of the default panel, when I try to move it to where I want it my mouse's buttons have stopped working. The cursor moves, the keyboard still works and the mouse still functions normally in my host OS (MX 19.2 AHS with Xfce.) MX KDE B1 is running as a guest OS in VBox 6.1.6 with 1MB RAM, 128KB VRAM, 2 CPUs, 25GB virtual disk, VBoxSVGA video. The mouse is an A4Tech wireless.

Surely you mean 1 GB not 1 MB RAM?
Try doubling the cores to 2 (in case you havent) and set the ram at 2GB
WIdgets are resource hungry, what do you see when you run top after you open the widgets?

[baldyeti]

Here's another vote for the more whiskerlike menu, too.

FWIW i much prefer it as well.

[asqwerth]

Here's another vote for the more whiskerlike menu, too.

You have a choice of menu styles in KDE. Right click on the launcher and choose alternatives.
Making the menu more whisker like would lessen the separation of KDE to XFCE

I believe the proposal raised was which of the 2 menus to set as default OOTB. That is another issue to discuss.

[JayM]

Twice today after installing a new widget, which gets added at the far right of the default panel, when I try to move it to where I want it my mouse's buttons have stopped working. The cursor moves, the keyboard still works and the mouse still functions normally in my host OS (MX 19.2 AHS with Xfce.) MX KDE B1 is running as a guest OS in VBox 6.1.6 with 1MB RAM, 128KB VRAM, 2 CPUs, 25GB virtual disk, VBoxSVGA video. The mouse is an A4Tech wireless.

Surely you mean 1 GB not 1 MB RAM?

Yes, I meant 1GB, and stop calling me Shirley!

Try doubling the cores to 2 (in case you havent) and set the ram at 2GB
WIdgets are resource hungry, what do you see when you run top after you open the widgets?

I gave it 2 cores when I set up the VM. I'll try bumping up the RAM to 1.5GB and test it some more. I don't want to give it 2 because I only have 4GB in the laptop. Thanks for the suggestions.