Memory leak of 882-877 =5MB after hibernation?? Browser was in text-mode only. AND: they USA are so STUPID, **that** possibility under NOUVEAU the same error aroses!!!

They're so IMPOSSIBLY stupid, certainly... they do bad and good simultaneously, shits of hybrids... [ARURT-US!!!]

 •Test circumstances - [EDIT] I omitted copying certain param into „shadow” module subsystem... &... THE PROPER ONE.

„Clear” initcpio: no nvidia, no nouveau & /etc/modprobe.d/nvidia.conf filled-in.
And  NVreg_PreserveVideoMemoryAllocations=1 as copy from boot cmdline:

 

/etc/modprobe.d/nvidia.conf        :

...

 6 options nvidia  NVreg_PreserveVideoMemoryAllocations=1
 7 options nvidia_drm  NVreg_PreserveVideoMemoryAllocations=1
 8 options nvidia_modeset   NVreg_PreserveVideoMemoryAllocations=1
 9 options nvidia_uvm  NVreg_PreserveVideoMemoryAllocations=1
10 

.... 

# Defined in /root/.config/fish/functions/BASH.fish @ line 50
function hibertest
   s2disk -P "shutdown method"="reboot"
end

Standard GLX info program [EDIT — that is, before the 1-param duplication from cmdline...]:

 root@Knoppix /# glxinfo |grep -i "mem"

Gives
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 886 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# hibertest
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /#

Text-over-text Blogger display ERROR: When I reset the posts amount on main page, the blog NOW is displayed OK, without frustrating error.

Setting post display amount option in Blogger settings into small amount (4) resets (repairs?? NOW OK...) THE ERROR in displaying the blog.

I don't know why they inserted this shitty option. Again for stupid smartphones ?? Blogger „designer” has also some other frustrating features – but this error is the most frustrating, definitely. In starting phase of performing problem diagnostics, I thought it can be lo-res error (and, even Linux OS forces to use lores with some kernel configurations – really strange!!), because screen resolution is problem IMO known to such intensity, as other difficult NVIDIA÷Nouveau affairs.

I am almost sure that malformed blog display is Blogger err, not of the browsers'. Note that WP version of my blog was, & is – OK.

This blog is still a helper version... . Now, lets go step further.

Not to say NVIDIA compiling is so hard – [D]KMS can be, but only at starting learning Linux.

NVIDIA compiling was hard when using sync mode WHILE COMPILING. We should use async „enter” and „exit” Bash script. During compiling another big program, I felt much faster experience. Really, when I remounted fs async, the NVIDIA compiler completed NV driver installation in a moment.

In order to have Linux OK, handy bash async script must have both ENTER and EXIT functions (along CTRL+C interrupt dispatcher).

Kernel recompilation BAD caveat (next!): .config's NOUVEAU is *NOT* marked (y/m) automatically/remains only commended out!!...

• —Despite make defconfig/localmodconfig/THE ETC.!!
• Similar problem is when installing Debian (EVEN both user/kernel-land packages ) inside chrooted container (or usual system as „well”, USTUPID): it is sado-masonism of USA — „deb configuring” have auto-remove even needed packages — we are not robots to discern it as bug!! Deb „configure” IMO does is equivocative — see Arch Linux pacman philosophy (!!!),
• Hibernation patch is in 1/3 OK – is means, HDD spindown turned from amount of 3 (three), to the smaller 2 (two) value.
• Yea, even if restoration failed to reach its end (drivers re-initialization, maybe from lacking of nouveau module - as above) – some crash – see what USA „colonization”, „mega”, „giga”, „super”, „explore”, „discover”, „fun//ky” (etc.) is not that morality that you should have ***to be really happy**** (NOT the «APE»).

NVIDIA/Xorg screen (RE)DRAW BUG as a next case from multievidence of (un)corporate RATS: both business and open source „mans”!!

When using Linux ope*RAT*ing system, remember about it overwhelming downsides!

But the worst is HIBERNATION. And shut up stupids forum maniacs!

People don't write about topic THAT GOING INTO s2disk AND (!!!) RETURNING, THE HDD DRIVE SPINS DOWN [the HDD LIFETIME] in summary THREE TIMES, NOT THE ONE AMOUNT NEEDED — a. before saving image b. when power downs (and, again, NOT ACPI!!!!!) c. while resuming!!!! WHAT YOU NOT UNDERSTAND??

— How this is even possible, crappy people!! Errors, bugs at fundamental kernel-mode levels!!!

They have hope that new approach into NVIDIA drivers will make the Xorg/Wayland experience normalized?

When errors last from nouveau times/usage??!! Discovered at KNOPPIX distribution. The screen not whole crashing, but modern Blender repaints often in black. I remember also the mouse problem to this day. *Your* stupidity, you cannot even maintain Linice debugger – I saw 32-bit version (DWORD—compilation problem) now, 2024.

•Even more! Can't check one Rebecca Black OS Wayland operating (- checked by pgrep to surety! -), because screen completely damages (source of naming convention...!!) at startup!

If *you* would stop bad NLP, then you'd have more mind abilities.

Linux is not such revolution. It lacks in graphics, and power management. Simple sleep operation (to RAM) sometimes crashes whole system. Some fear can arise when VT-switch, still. Some people like standard Linux VT, and you crap do regress Blender (both in BI and memory consumption/loading times by main program file size), VTs (some a'la VT remake layers when you cannot even in.... QUICK simple words explain usage of fbsplash), IF YOU CANNOT MAKE SOMETHING REPAIRED THEN YOU CREATE REGRESSION MAYBE DELIBERATELY!?? Does KWin/Wayfire support ALL compiz options (as ccsm) or NOT?!!

*You* must stand in truth!! Fake mans == apes!

You programmers/testers/bug reporters & forums „staff” are •lazy, •news-oriented, •stupid/ADHD•unlogical – WHY s2disk informs me about page poisoning, when I am sure that my RAM are OK!!! && And why you cannot make comprehenvive manpage about differentating basic concepts: KMS, framebuffer, ...x...dga, DRM!!!

Basic programming layer is making key concepts simple & logical – not jumping with manpage, info, wiki, forum.

Linux OS lacks documentation ability – its structure is very confusing (in comparison with M$' MSDN Library / aka MSDN Collection). Kernel code comments are non-encyclopedical, non-scientific (w/o making big difference in sys-freeze, disk-freeze, suspend and hibernation). Yea, particular KDE program makes help pages user experience a bit better. But it is NOT what we need. But again, very strange that variety of naming conventions and DE amount harden the ability to quickness – productiveness. As Babel thing, once again.

**Unconsequence** of Linux groups (multi BUGS) at Blender, LibreOffice Writer, *AND* LXQt file manager. IRRITATES. Mouse CURSOR not turning to „wait” shape in even BOTH ones.

I can't understand why, if there is such multiple coders of open source system, YOU CAN'T ORGANIZE SIMPLEST THINGS UP and does make Blender regressions bugs.

It can be very frustrating, I start to understand some sense of Gentoo system (and ABS).

The most frustrating is general philosophy of USA „lab”. You test, test, test – and, often still – have not. Even at code of Blender soft, one is bigger and more regressed than previous version (despite „news”).

Don't need animation lie, when basic rendering has still bugs.

In Bfor Artists /Blender 3.3../3.6... (...WHY mutating such versions' nums? Not a simple 1-1 string copy?? Are we computers or humans!!?? Data, data but WISDOM almost... none...), restarting scene demands gdb „r” relaunch.

•NEW Blender packages demands even more memory (for what?? Python language should be more as Visual Basic — when you start it QUICKLY).

And in Blender, there you make several meshes, lights (even without Par. Sys.), and .....

Still nowadays, BUGS ARE ON BASIS, despite Python revolution

 — FROM PEOPLE'S ADHD MINDS, that fail to comprehend that simplicity, practical aspect is more important than new sketch / grease ..cking new dragon scene.

„Ldsym” errors, as I name one category of OFTEN met Linux general bugs (after system usermode [!!!!] upgrade).

When man is almost certain that .so objs would be OK after new actualization (whole system upgrade), NEW, NEW CRASH. Even still, the ICU internationalization library demands its bash script, to the some strange point!

And.. New kernel??! What the f...k about nouveau, not loading (screen tearing) at newer RebbecaBlackOS ISO (GRUB) — a contrario???

Hybrid, hybrid, hybrid!!!! WHAT stupid hybrid society!!

Yea, Linux is really good at overriding M$ monopoly game.

—But what you need really and certainly does is a philosophy to coding opensource. Not such pokemons, snakes or Ukraine horror monsters that you render actually, stupid.

•LXQt is also, generally very good. Problem lies in.... LYING. So stupid strings that you don't have time... why the ....ing bankers does have time to challenge you??? Slaves colony.... .

As errors arise at installation upgrade, as at the programs runtime details. There must be some simple solution... .

•Some very interesting things I discovered. Gtk Window Decorator and Metacity's theme restores text in static application switcher (Compiz). Blender Bfor Artists with LUXCORE works OK if under gdb debugger (because of speciffic buffer overflow founds its redirection??.

•I don't trust even new Wayland „Xorg replacement”. Qt – OK, but what about GTK apps?