MX-19.2 KDE Beta 2 Feedback Thread

[uncle mark]

Will there be another beta after this or a release candidate? or already the final version?

No more betas, the next one will be a RC.

You guys obviously worked your butts off in the alpha stage. Very few significant bugs or gotchyas or omissions in these betas. Well done. Very well done.

[JuhaT]

I use the "Nvidia driver installer" in MX-tools and it installs fine but doesnt work when booting into systemd. I just get a scrambled prompt after the three dots and before the login page loads. I have to restart the computer to get out of it. I can boot into sysVinit just fine with the Nvidia driver..

I had this problem in beta 1 too and the suggestion to disable plymoth in boot options (add: disable splash) didnt help.I have now made a clean install to see if the problem was that I used the same home-folder from XFCE, but that wasnt the problem it seems.

I have no problem contiuning using Noveau driver since it is fast enough and works in systemd (I need to use systemd since my VPN software from OVPN doesnt work in sysVinit), I just wanted to report this for info. Maybe I am the only one having this problem with my hardware?

Code: Select all

System:
  Host: muka 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=b0f96b86-7912-40a0-93e1-be72166b325c ro quiet splash 
  init=/lib/systemd/systemd 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta2_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: Gigabyte product: Z390 GAMING X v: N/A serial: <filter> 
  Mobo: Gigabyte model: Z390 GAMING X-CF v: x.x serial: <filter> 
  UEFI [Legacy]: American Megatrends v: F9 date: 10/15/2019 
CPU:
  Topology: 8-Core model: Intel Core i7-9700K bits: 64 type: MCP arch: Kaby Lake 
  family: 6 model-id: 9E (158) stepping: D (13) microcode: D6 L2 cache: 12.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57600 
  Speed: 4061 MHz min/max: 800/4900 MHz Core speeds (MHz): 1: 4061 2: 3070 3: 3445 
  4: 4414 5: 3612 6: 3381 7: 4239 8: 3261 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  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 mitigation: TSX disabled 
  Type: tsx_async_abort mitigation: TSX disabled 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Gigabyte driver: nouveau 
  v: kernel bus ID: 01:00.0 chip ID: 10de:1b81 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  compositor: kwin_x11 resolution: 3440x1440~60Hz 
  OpenGL: renderer: NV134 v: 4.3 Mesa 20.0.7 direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a348 
  Device-2: NVIDIA GP104 High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10f0 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k 
  port: efa0 bus ID: 00:1f.6 chip ID: 8086:15bc 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:
  Local Storage: total: 3.29 TiB used: 7.49 GiB (0.2%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: 
  physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q 
  scheme: MBR 
  ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 2B6Q scheme: GPT 
  ID-3: /dev/sdc type: USB vendor: Western Digital model: WDS1 20G2G0A-00JH30 
  size: 111.80 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 0107 
  ID-4: /dev/sdd vendor: Seagate model: ST2000DX001-1CM164 size: 1.82 TiB 
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm 
  serial: <filter> rev: CC43 scheme: MBR 
  ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO M.2 250GB size: 232.89 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 3B6Q scheme: MBR 
Partition:
  ID-1: / raw size: 29.34 GiB size: 28.76 GiB (98.00%) used: 7.16 GiB (24.9%) 
  fs: ext4 dev: /dev/sdb1 
  ID-2: /home raw size: 203.54 GiB size: 199.35 GiB (97.94%) used: 334.2 MiB (0.2%) 
  fs: ext4 dev: /dev/sdb2 
Sensors:
  System Temperatures: cpu: 38.0 C mobo: 27.8 C gpu: nouveau temp: 32 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 1363 
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 http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster main non-free
  2: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 244 Uptime: 11m Memory: 23.49 GiB used: 1.80 GiB (7.7%) Init: systemd 
  v: 241 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 

[dolphin_oracle]

I use the "Nvidia driver installer" in MX-tools and it installs fine but doesnt work when booting into systemd. I just get a scrambled prompt after the three dots and before the login page loads. I have to restart the computer to get out of it. I can boot into sysVinit just fine with the Nvidia driver..

I had this problem in beta 1 too and the suggestion to disable plymoth in boot options (add: disable splash) didnt help.I have now made a clean install to see if the problem was that I used the same home-folder from XFCE, but that wasnt the problem it seems.

I have no problem contiuning using Noveau driver since it is fast enough and works in systemd (I need to use systemd since my VPN software from OVPN doesnt work in sysVinit), I just wanted to report this for info. Maybe I am the only one having this problem with my hardware?

Code: Select all

System:
  Host: muka 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=b0f96b86-7912-40a0-93e1-be72166b325c ro quiet splash 
  init=/lib/systemd/systemd 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta2_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: Gigabyte product: Z390 GAMING X v: N/A serial: <filter> 
  Mobo: Gigabyte model: Z390 GAMING X-CF v: x.x serial: <filter> 
  UEFI [Legacy]: American Megatrends v: F9 date: 10/15/2019 
CPU:
  Topology: 8-Core model: Intel Core i7-9700K bits: 64 type: MCP arch: Kaby Lake 
  family: 6 model-id: 9E (158) stepping: D (13) microcode: D6 L2 cache: 12.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57600 
  Speed: 4061 MHz min/max: 800/4900 MHz Core speeds (MHz): 1: 4061 2: 3070 3: 3445 
  4: 4414 5: 3612 6: 3381 7: 4239 8: 3261 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  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 mitigation: TSX disabled 
  Type: tsx_async_abort mitigation: TSX disabled 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Gigabyte driver: nouveau 
  v: kernel bus ID: 01:00.0 chip ID: 10de:1b81 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  compositor: kwin_x11 resolution: 3440x1440~60Hz 
  OpenGL: renderer: NV134 v: 4.3 Mesa 20.0.7 direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a348 
  Device-2: NVIDIA GP104 High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10f0 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k 
  port: efa0 bus ID: 00:1f.6 chip ID: 8086:15bc 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:
  Local Storage: total: 3.29 TiB used: 7.49 GiB (0.2%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: 
  physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q 
  scheme: MBR 
  ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 2B6Q scheme: GPT 
  ID-3: /dev/sdc type: USB vendor: Western Digital model: WDS1 20G2G0A-00JH30 
  size: 111.80 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 0107 
  ID-4: /dev/sdd vendor: Seagate model: ST2000DX001-1CM164 size: 1.82 TiB 
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm 
  serial: <filter> rev: CC43 scheme: MBR 
  ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO M.2 250GB size: 232.89 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 3B6Q scheme: MBR 
Partition:
  ID-1: / raw size: 29.34 GiB size: 28.76 GiB (98.00%) used: 7.16 GiB (24.9%) 
  fs: ext4 dev: /dev/sdb1 
  ID-2: /home raw size: 203.54 GiB size: 199.35 GiB (97.94%) used: 334.2 MiB (0.2%) 
  fs: ext4 dev: /dev/sdb2 
Sensors:
  System Temperatures: cpu: 38.0 C mobo: 27.8 C gpu: nouveau temp: 32 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 1363 
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 http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster main non-free
  2: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 244 Uptime: 11m Memory: 23.49 GiB used: 1.80 GiB (7.7%) Init: systemd 
  v: 241 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 

my suggestion is to boot into systemd mode first, install the nvidia drivers, and see if that improves the situation.

[JuhaT]

my suggestion is to boot into systemd mode first, install the nvidia drivers, and see if that improves the situation.

I have tried it both ways. I had no problems in the XFCE version so I guess it is something with KDE that is not working right with my machine. I have in the past tried Kubuntu and some other distro with KDE and there were problems with plasma also. Most prominent was that computer always hanged when waking up from suspend. A problem I only have had with plasma, but not with MX-KDE, for which I am grateful :)

But as I said, I am satisfied with Noveau driver and if no one else has reported this problem or can reproduce it, then it is not a problem with MX that you have to fix.

[CaputAlista]

i create a direct access sudo kcmshell5 clock shows << kf5.kcoreaddons.kaboutdata: QGuiApplication::desktopFileName "/usr/share/kservices5/clock.desktop" is out-of-sync with KAboutData::applicationData().desktopFileName "org.kde.kcmshell5"
Failed to enable NTP "org.freedesktop.DBus.Error.InvalidArgs" "Invalid argument"
Failed to set current time "org.freedesktop.DBus.Error.InvalidArgs" "Failed to update context: Invalid argument"
Failed to enable NTP "org.freedesktop.DBus.Error.InvalidArgs" "Invalid argument"
Failed to set current time "org.freedesktop.DBus.Error.InvalidArgs" "Failed to update context: Invalid argument" >>

It is curious, the date cannot be changed
But if I press the reset button (kde date dialog box) it works and changes to any time zone (country)

[heywoodidaho]

This mornings update changed my background pic? Anyone else? no big deal,but odd.

[srq2625]

This mornings update changed my background pic? Anyone else? no big deal,but odd.

Yep - me too.

And, the MX Update notifier is missing from my "task bar". I don't know when it went missing, but the quoted post made me look and I noticed it was not showing after having been logged in for about 20 minutes. For me, not a big deal as I do the updates from the command line but ... if I'm not the only person for whom it is missing, well this might be an issue.

[fehlix]

This mornings update changed my background pic? Anyone else? no big deal,but odd.

Yep - me too.

And, the MX Update notifier is missing from my "task bar". I don't know when it went missing, but the quoted post made me look and I noticed it was not showing after having been logged in for about 20 minutes. For me, not a big deal as I do the updates from the command line but ... if I'm not the only person for whom it is missing, well this might be an issue.

Will it show up when you either login/logout or run MX Updater (unhide icon) from the menu.

[dolphin_oracle]

the thing with the wallpaper I will look at..I assume it changed on login...

if so, it won't change again, even on update.

[heywoodidaho]

Yep,updater is gone as well.