AHS KDE -- RESPIN! -- Screen Corruption

[jackdanielsesq]

Greetings all

What we have here is ......

* Buster 5.6 Kernel Full Monty O/S - stunningly quick, fully loaded O/S - up-to-date
* KDE 5.14.5 - the best-looking, most functional, efficient Desktop Experience, ever

This is a first for moi ..... all the more confusing in that all the iso installations are copacetic, and only the 2x Production installations go corrupt after coming out of suspend-mode - both of them !!... even more perplexing
is both Production O/S #16, #20 are built on the original #15 iso file, with #14 untouched, further back....

Even included, redundantly, the inxi code, to stave-off the fishslappers

The problem is within KDE and KDE alone

KDE was tweaked in iso stages only, never in production ...

Hoping to find some kind soul with more in-depth knowledge than mine

Highest Regards .....

Jack

PS - various stages of update included below - most happened in iso #15
Very few in Production in #16 & #20 ... thank you
Anyone with KDE ideas very welcome ...

''Commit Log for Fri Aug 14 11:39:28 2020 on #20''


Upgraded the following packages:
apt-notifier (20.08.06mx19~1) to 20.08.06mx19~2
desktop-defaults-mx-kde (20.08.01) to 20.08.02
mx-goodies (20.08.04) to 20.08.12
mx-installer (20.7) to 20.8
mx-packageinstaller-pkglist (20.07.04) to 20.08.01

''Commit Log for Mon Aug 10 03:42:23 2020 on #20''


Upgraded the following packages:
apt-notifier (20.07.06mx19~12) to 20.08.06mx19~1
desktop-defaults-mx-kde (20.07.07) to 20.08.01
grub-common (2.04-3mx19+3) to 2.04-9~mx19+5
grub-efi-amd64-bin (2.04-3mx19+3) to 2.04-9~mx19+5
grub-efi-ia32-bin (2.04-3mx19+3) to 2.04-9~mx19+5
grub-pc (2.04-3mx19+3) to 2.04-9~mx19+5
grub-pc-bin (2.04-3mx19+3) to 2.04-9~mx19+5
grub2-common (2.04-3mx19+3) to 2.04-9~mx19+5
libjson-c3 (0.12.1+ds-2) to 0.12.1+ds-2+deb10u1
mx-goodies (20.07.08) to 20.08.04

''Commit Log for Sun Aug 2 00:31:15 2020 on #15 [iso]''


Upgraded the following packages:
apt-notifier (20.07.05mx19) to 20.07.06mx19~12
ark (4:18.08.3-1) to 4:18.08.3-1+deb10u1
base-files (10.3+deb10u4) to 10.3+deb10u5
dbus (1.12.16-1) to 1.12.20-0+deb10u1
dbus-x11 (1.12.16-1) to 1.12.20-0+deb10u1
desktop-defaults-mx-kde (20.07.05) to 20.07.06
glib-networking (2.58.0-2) to 2.58.0-2+deb10u2
glib-networking-common (2.58.0-2) to 2.58.0-2+deb10u2
glib-networking-services (2.58.0-2) to 2.58.0-2+deb10u2
intel-microcode (3.20200609.2~deb10u1) to 3.20200616.1~deb10u1
libappstream-glib8 (0.7.14-1) to 0.7.14-1+deb10u1
libdbus-1-3 (1.12.16-1) to 1.12.20-0+deb10u1
libexif12 (0.6.21-5.1+deb10u1) to 0.6.21-5.1+deb10u4
libexiv2-14 (0.25-4) to 0.25-4+deb10u1
libgnutls30 (3.6.7-4+deb10u4) to 3.6.7-4+deb10u5
libinput-bin (1.12.6-2) to 1.12.6-2+deb10u1
libinput10 (1.12.6-2) to 1.12.6-2+deb10u1
liblirc-client0 (0.10.1-5.2) to 0.10.1-6.2~deb10u1
libmariadb3 (1:10.3.22-0+deb10u1) to 1:10.3.23-0+deb10u1
libperl5.28 (5.28.1-6) to 5.28.1-6+deb10u1
libpython3.7 (3.7.3-2+deb10u1) to 3.7.3-2+deb10u2
libpython3.7-minimal (3.7.3-2+deb10u1) to 3.7.3-2+deb10u2
libpython3.7-stdlib (3.7.3-2+deb10u1) to 3.7.3-2+deb10u2
libunwind8 (1.2.1-9) to 1.2.1-10~deb10u1
linux-libc-dev (5.6.14-2~mx19+1) to 5.7.10-1~mx19+1
mariadb-common (1:10.3.22-0+deb10u1) to 1:10.3.23-0+deb10u1
mx-cleanup (20.7.1) to 20.8
mx-network-assistant (19.9.01) to 20.8
nfs-common (1:1.3.4-2.5) to 1:1.3.4-2.5+deb10u1
nfs-kernel-server (1:1.3.4-2.5) to 1:1.3.4-2.5+deb10u1
perl (5.28.1-6) to 5.28.1-6+deb10u1
perl-base (5.28.1-6) to 5.28.1-6+deb10u1
perl-modules-5.28 (5.28.1-6) to 5.28.1-6+deb10u1
python3.7 (3.7.3-2+deb10u1) to 3.7.3-2+deb10u2
python3.7-minimal (3.7.3-2+deb10u1) to 3.7.3-2+deb10u2


''Commit Log for Tue Aug 4 01:08:35 2020 on #15''


Upgraded the following packages:
desktop-defaults-mx-kde (20.07.06) to 20.07.07
mx-packageinstaller-pkglist (20.07.02) to 20.07.04


''Commit Log for Thu Aug 13 01:49:39 2020 on #15''


Upgraded the following packages:
apt-notifier (20.07.06mx19~12) to 20.08.06mx19~1
desktop-defaults-mx-kde (20.07.07) to 20.08.02
grub-common (2.04-3mx19+3) to 2.04-9~mx19+5
grub-efi-amd64-bin (2.04-3mx19+3) to 2.04-9~mx19+5
grub-efi-ia32-bin (2.04-3mx19+3) to 2.04-9~mx19+5
grub-pc (2.04-3mx19+3) to 2.04-9~mx19+5
grub-pc-bin (2.04-3mx19+3) to 2.04-9~mx19+5
grub2-common (2.04-3mx19+3) to 2.04-9~mx19+5
libjson-c3 (0.12.1+ds-2) to 0.12.1+ds-2+deb10u1
mx-goodies (20.07.08) to 20.08.04
mx-installer (20.7) to 20.8

Code: Select all

Snaphot created on: 20200805_0628
System:
  Host: mx 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=d273c400-5928-4865-a632-e23314ea5ac8 ro quiet hush 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX_AHS_KDE_F_M_WIFI_UTD_ReSpin_x64_patito_feo_8_2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: Acer product: Extensa 5635G v: N/A serial: <filter> Chassis: 
  type: 10 serial: <filter> 
  Mobo: Acer model: BA50-MV serial: <filter> BIOS: Phoenix v: 0.3305 
  date: 08/14/2009 
CPU:
  Topology: Dual Core model: Intel Core2 Duo T6570 bits: 64 type: MCP arch: Penryn 
  family: 6 model-id: 17 (23) stepping: A (10) microcode: A0B L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 8378 
  Speed: 1700 MHz min/max: 1200/2101 MHz boost: enabled Core speeds (MHz): 1: 1700 
  2: 1695 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  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: NVIDIA G98M [GeForce G 105M] vendor: Acer Incorporated ALI 
  driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:06ec 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  compositor: kwin_x11 resolution: 1366x768~60Hz 
  OpenGL: renderer: NV98 v: 3.3 Mesa 20.0.7 direct render: Yes 
Audio:
  Device-1: Intel 82801I HD Audio vendor: Acer Incorporated ALI 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Qualcomm Atheros AR8131 Gigabit Ethernet vendor: Acer Incorporated ALI 
  driver: atl1c v: 1.0.1.1-NAPI port: 4000 bus ID: 09:00.0 chip ID: 1969:1063 
  IF: eth0 state: down mac: <filter> 
  Device-2: Huawei E353/E3131 type: USB driver: cdc_ether bus ID: 2-1:4 
  chip ID: 12d1:14db 
  IF: eth1 state: up speed: N/A duplex: N/A mac: <filter> 
Drives:
  Local Storage: total: 1.36 TiB used: 491.89 GiB (35.2%) 
  ID-1: /dev/sda vendor: Seagate model: ST500LT012-9WS142 size: 465.76 GiB 
  block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm 
  serial: <filter> rev: SDM1 scheme: MBR 
  ID-2: /dev/sdb type: USB vendor: Western Digital model: WD Elements 10A2 
  size: 931.48 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 1033 scheme: MBR 
Partition:
  ID-1: / raw size: 10.19 GiB size: 9.96 GiB (97.82%) used: 6.06 GiB (60.8%) 
  fs: ext4 dev: /dev/sda16 
Sensors:
  System Temperatures: cpu: 72.0 C mobo: N/A gpu: nouveau temp: 74 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
  3: deb-src http://deb.debian.org/debian/ buster non-free contrib main
  4: deb http://deb.debian.org/debian/ buster-backports non-free contrib main
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/testrepo/ buster test
  3: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 167 Uptime: 1h 08m Memory: 3.81 GiB used: 1.30 GiB (34.0%) 
  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 

[Jerry3904]

MOD: I changed you subject line to conform to Terms of Use since we just released an AHS KDE.

[m_pav]

What Jerry3904 said.

You're running an 11 year old laptop which is running very hot, and you're running a very modern kernel, that's a recipe for disaster when used in the wrong hands.

Your laptop needs the Debian 4.9 kernel, not the 4.19 and most definitely not any of the 5.x kernels. In fact, it's supremely better off with regular MX19 and a full strip down and dedust.

[tony37]

What Jerry3904 said.

You're running an 11 year old laptop which is running very hot, and you're running a very modern kernel, that's a recipe for disaster when used in the wrong hands.

Your laptop needs the Debian 4.9 kernel, not the 4.19 and most definitely not any of the 5.x kernels. In fact, it's supremely better off with regular MX19 and a full strip down and dedust.

Is there gonna be a 4.19 KDE .iso?
I'm asking because I was reminded of this topic by someone complaining on Distrowatch about screen tearing in MX KDE. Since he doesn't have this problem with Q4OS, which has exactly the same KDE version (so his comments about that are nonsense), it might be the newer kernel.
I don't have any problem with the new kernel, but then I use a 3 year old laptop.

[Eadwine Rose]

I suggest you take a look at the newly released OFFICIAL MX-KDE, to be found here: https://mxlinux.org/blog/mx-19-2-kde-now-available/

[tony37]

I suggest you take a look at the newly released OFFICIAL MX-KDE, to be found here: https://mxlinux.org/blog/mx-19-2-kde-now-available/

I probably should have started a new thread asking this instead of posting in this respin thread. I was very much talking about the official release and wondering if there'd be a release with an older kernel.

[Eadwine Rose]

Definitely ask that question in the official forum for MX-KDE :)

viewforum.php?f=145

[jackdanielsesq]

Friends, Romans, Countrymen ...

First of all ... my sincere apologies for the long delay, especially as the fix was pretty simple - but my day-job is a tyrannical, all-consuming mistress... which is exacerbated by a bunch of other folks who depend on moi also ...

Having been around Nvidia for a very long time, and knowing how that chip, software has wrecked so many of my machines, and many others, all over the world, I guess I had become complacent with the outstandingly, forgiving nature of the MX Linux Operating System, no matter the color or flavor - it simply smokes everything else - whereas when MX did occasionally hiccup, all it took was a simple reflush, fsck, or reboot to fix what ever ailed it - I had never seen a corrupt screen coming out of 'suspend' - before, ever ... the MX nouveaux driver was sufficient, in of itself ..
Which is again, testament to the Developers who are the very glue of this community - so much so that I had forgotten about all the dead machines, und useless software that came before MX Linux

Nvidia has destroyed way too many Mac's, Vaio's, HP's, as well as countless O/S's from MSFT, RPM and even Debian.... MX Linux is the only O/S that has not succumbed ... my bad, I had simply forgotten

The CPU/GPU operating temperature difference between Kernel #4.xx & 5.xx were in the single digits ... have 17-35 O/S on that ol' girl, 12 years-young Acer that I can boot between them, ad hoc, with or without cool-downs - have burned say 300x 'snapshots' to-date, sometimes 15x B2B - so whats not to love - am really expecting the 'spinny-one' to snap first, but not to worry, we have plenty more

BTW - Intel will run 20~25'C hotter than AMD - 24/7
The reason this ol' girl is so old, and works 24/7, is because of relentless maintenance - every machine we own is stripped, cleaned every 6/12 months - even have a special 5gal Wet & Dry attachment that I kludged to 'suck' all the crud out - blowing crud out is worthless - it will be back again in hours/days.

Acquired her almost new, with no HDD, RAM or battery - it has never faltered or shutdown/overheated ... ever ... proving one does not need to purchase every shiny new toy because MSFT & INTEL say so ...

The first fix is cheap & nasty - simply turn off compositing .. go to KDE, Hardware, Display und Monitor, Compositor Setting for Desktop Effects and uncheck the 'enable compositor on startup box' - then hit apply - it worked for moi - one can also explore the other options as they may or not apply to your GPU

The second fix involves simply installing the appropriate Nvidia driver, which I did, und according to the in-situ Nvidia GUI this machine's GPU is running @ 55'C and will start throttling @ 129'C - whew!!

To paraphrase ....

Mx Kernel 4.19.0-6 Snapshot - System Temperatures: cpu: 73.0 C mobo: N/A gpu: nouveau, temp: 81 C

Mx Kernel 5.6.0-2 Snapshot ...System Temperatures: cpu: 75.0 C mobo: N/A gpu: nouveau temp: 77 C

NB - the northern hemisphere is slightly warmer this time of year than NZ right now
We would especially like to thank all the developers at MX, et al, for all their wonderful brainstorming, magnificent support... you folks are the cornerstone, epitome of freedom - 'life is a respin'

In closing, I would like to apologize a second time if anybody took umbrage at the post - it was not intended to be offensive - it was merely to inform - as my good friend from a bygone era would say - "Of what use be there for joy, if not for the sharing thereof?"

index.php

https://sourceforge.net/projects/mx-kde-iso/files/


https://archive.org/details/@mx-kde

Highest Regards

Jack

PS - this tearing only pertained to my own production toys and not, repeat not, to any of my iso's

Peace ...

[Eadwine Rose]

That is one hot running system. Ever thought about installing some better cooling system? On the hottest days here (40+) my system didn't run that hot.