_FULLSCREEN behaves weird in some Linux OS installations...

[mnrvovrfc]

... and combinations of budget computers. This was on Spiral Linux purposely upgraded to "Bookworm". In other words, this was a Debian clone which had v11 "Bullseye" base, and I upgraded it to v12 "Bookworm" base which has been on since mid-June.

This was tried with bplus' program with the fish. See screenshot below.

This is from a 1-1/2-year-old "ewaste" candidate:

Code: (Select All)

[~]$ inxi -SCMm -x -I
System:
  Host: xxxxxxxx Kernel: 6.1.0-10-amd64 arch: x86_64 bits: 64 compiler: gcc
    v: 12.2.0 Desktop: Xfce v: 4.18.1 Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop E410MAB_E410MA
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: E410MAB v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: E410MAB.300 date: 07/23/2021
Memory:
  RAM: total: 3.65 GiB used: 961.4 MiB (25.7%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
    required.
CPU:
  Info: dual core model: Intel Celeron N4020 bits: 64 type: MCP
    arch: Goldmont Plus rev: 8 cache: L1: 112 KiB L2: 4 MiB
  Speed (MHz): avg: 814 high: 833 min/max: 800/2800 cores: 1: 796 2: 833
    bogomips: 4377
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Info:
  Processes: 166 Uptime: 28m Init: systemd target: graphical (5) Compilers:
  gcc: 12.2.0 Packages: 1834 Shell: Bash v: 5.2.15 inxi: 3.3.26

"ewaste" means do not buy from ASUS, or at least do not buy this particular model because it has a poor battery. This could be the last time I could use this computer, for its possible refusal to deal with the battery if it can't charge it. I had another laptop with SSD crap out on me in this manner but I could still use it without the battery. I cannot use this ASUS computer without the battery because... I have to remove the screws on the bottom of the bulk side of the unit to get to it. :O