Intermittently I cannot select / click on items with pointer. not solved

[prairie_dog]

I had a drive failure and had reload on another drive using mx 23.6 64bit iso off a ventoy disk.
Btrfs locked the failed drive ... great work and glad I used btrfs all these years.

Usually (always?) system correctly works on boot.
Then after some use I can point at an item but cannot click and get a response.
I can use the keyboard to point at items (such as on the switch-user / poweroff / suspend screen
which I can get to by toggling to a black workspace and hitting alt-F4 to access switch user
(great script and programming work that bit of software is!)

Note the Dell m6800 has two pointers and sets of buttons.

If I use 'switch user' (to F8 screen) and login to a user that
has only been used for one browser. Very simple setup.
I do not recall ever having an issue on the second user. PLUS:

Then if I toggle back back to F7 first user ... the first user functions correctly again.

Often I toggle over to F8 without logging in and back to F7 ... this also (usually/always?) corrects the issue.

Things I do .. some short notes:
0) I use btrfs on encryped drives. Non encrypted boot and swap. / and /home separate partitions
On boot I receive invalid partion notice ... I believed it is because the GPT partition did no have
a protective MBR encasing. Noticed that gdisk now reports there is a protective MBR. I hand enter
the encryption passwords. btrfs reports no issues.

1) All updates done through synaptic.
2) I have tested the computer and identifed no errors.
3) I have used an external keyboard with tracpad built in ... same issue.
but I did not deactivate the internal keyboard.
4) Software:
gvim ... gtk3 GUI for vim. This software is heavily used and may be part of the issue.
Occasionally error messages appear on the terminal orginating a gvim editor.
As I recall they all relate to gtk3.

Guake termial. Extensively. May be related.
Browsers
palemoon, librewolf, vivaldi, firefox-esr, firefox, falkon, ... and others.

gnome calculator now locks instantly on load BUT FUNCTIONS CORRECTLY ON THE SIMPLE USER.
other software seems to function okay until the problem shows up.

Initially I believe it was some corruption in my home directory. However I have migrated across three users
with totally new setups and each experiences the issue.

Ah. I have not experienced the issue on 23.6 live disk.

.xsesstion errors?

(xfsettingsd:3422): GLib-CRITICAL **: 09:35:46.869: g_strv_contains: assertion 'str != NULL' failed
discover_other_daemon: 1No keyboard layout specified on the command line
Trailing -layout option ignored
only one keyboard


=======================
I downloaded older versions of MX Linux. (23.4, 23.5) as my experience in the past
is that the last release before a new release has a great many issues.
I want to go back in time and see if that helps ... they just stay there.

But I do not think I can manage getting the encrypted drives loaded again. I have lived up to now
with a drive I created in 2019(?) that was an early encryption ... and I had just managed to upgrade
through to 23.6.

Took me a day plus to get through the installer with two encrypted partitions in a custom setup.
I still am not positive they will function through a timeshift restore.

Tried debian trixie ... woof. Don't think I am going there.

Note: Some error message concerning systemd i found in .xsessions-errors
dbus-update-activation-environment systemd:--user not found, ignoring --systemd argument

The problem with all I listed above ... red herrings.

A quick knock to my head would be appreciated.

Thank you.

Please forgive my typo's ... stressful day and limited time.

Quicksystem

Code: Select all

System:
  Kernel: 6.1.0-38-amd64 [6.1.147-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/vmlinuz-6.1.0-38-amd64 root=UUID=<filter> ro quiet
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.6_x64 Libretto April 13  2025 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: Dell product: Precision M6800 v: 00 serial: <superuser required> Chassis:
    type: 9 serial: <superuser required>
  Mobo: Dell model: N/A serial: <superuser required> BIOS: Dell v: A26 date: 06/13/2019
Battery:
  ID-1: BAT0 charge: 31.4 Wh (100.0%) condition: 31.4/98.2 Wh (31.9%) volts: 12.2 min: 11.1
    model: Samsung SDI DELL 1C75X35 type: Li-ion serial: <filter> status: full
CPU:
  Info: model: Intel Core i7-4900MQ bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 751 high: 800 min/max: 800/2800 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 800 2: 800 3: 409 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 44699
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel
    arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: eDP-1 empty: DP-1,HDMI-A-1,VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0416 class-ID: 0300
  Device-2: NVIDIA GK104GLM [Quadro K3100M] vendor: Dell driver: N/A alternate: nouveau non-free:
    series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx process: TSMC 28nm
    built: 2012-18 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:11b6
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
  Monitor-1: eDP-1 model: LG Display 0x02da built: 2010 res: 1920x1080 hz: 60 dpi: 128 gamma: 1.2
    size: 382x215mm (15.04x8.46") diag: 438mm (17.3") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 25.0.7-2~mx23ahs renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Dell 8 driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
  Device-3: NVIDIA GK104 HDMI Audio vendor: Dell driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e0a class-ID: 0403
  API: ALSA v: k6.1.0-38-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I217-LM vendor: Dell driver: e1000e v: kernel port: f080 bus-ID: 00:19.0
    chip-ID: 8086:153a class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: Dell driver: ath9k v: kernel
    modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 168c:0034
    class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  IF-ID-1: usb0 state: unknown speed: -1 duplex: half mac: <filter>
Bluetooth:
  Device-1: Motorola PCS moto e6 type: USB driver: rndis_host v: kernel bus-ID: 2-1.3:3
    chip-ID: 22b8:2e25 class-ID: 0a00 serial: <filter>
  Device-2: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 2-1.5:4 chip-ID: 0cf3:817b
    class-ID: e001
  Report: ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 sub-v: 1 hci-v: 4.1
    rev: 1102
  Info: acl-mtu: 1022:8 sco-mtu: 183:5 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 1.71 TiB used: 1.01 TiB (58.9%)
  ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: SanDisk model: SD64G size: 57.94 GiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABF050 size: 465.76 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: 1D
    scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST320LT009-9WC142 size: 298.09 GiB
    block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: DEMA scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD10EZEX-75WN4A1 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 7113 scheme: GPT
Partition:
  ID-1: / raw-size: 117.17 GiB size: 117.17 GiB (100.00%) used: 16.14 GiB (13.8%) fs: btrfs
    dev: /dev/dm-0 maj-min: 253:0 mapped: luks-<filter>
  ID-2: /boot raw-size: 33.87 GiB size: 33.86 GiB (99.98%) used: 296.9 MiB (0.9%) fs: vfat
    dev: /dev/sda5 maj-min: 8:5
  ID-3: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 1 KiB (0.0%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-4: /home raw-size: 292.95 GiB size: 292.95 GiB (100.00%) used: 146.47 GiB (50.0%) fs: btrfs
    dev: /dev/dm-1 maj-min: 253:1 mapped: luks-<filter>
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 21.48 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4
    maj-min: 8:4
Sensors:
  System Temperatures: cpu: 55.0 C mobo: 49.0 C sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 2294
Repos:
  Packages: pm: dpkg pkgs: 2619 libs: 1372 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  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/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ bookworm-backports non-free-firmware non-free contrib main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb https://mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
Info:
  Processes: 333 Uptime: 21m wakeups: 2 Memory: 15.52 GiB used: 2.18 GiB (14.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

[CharlesV]

Does this happen after a screen saver kicking in, or suspend / wake etc ?

Do you still have the xfce4 screensaver loaded / running?
- If so, then uninstall it. If you want a screensaver, then install xscreensaver instead. But for testing, I would remove xfce4 screensaver first.

[prairie_dog]

Not that I have noticed.
I am using the screensaver and suspend.
I will immediately change that.

But.. I am working on something and suddenly I cannot click.

But.. This I cannot answer ... is there a 2nd screensaver in the alternate user tab.

I thank you for the tip and reply if it corrects ... or not.

[prairie_dog]

Well, I removed the screensaver.

Whole system went a bit nuts flashing screens when I removed the xfce screensaver.
(Edited this section. My humble apologies for leaving out the screensaver and typing just xfce.
I removed just the xfce4 screensaver.)

Plus my sloppy incorrect spelling of Intermittently. My day as the idiot.

System operates very differently ... very quick responses.

>>>>>>>>>>>>>>>>>>
Tried gnome-calculator. Still locks on that user.
(Tried from command prompt
gnome-calculator -m advanced
Error messages
(gnome-calculator:6871): Gtk-WARNING **: 13:35:30.370: Trying to snapshot MathConverter 0x55d63a2c2760 without a current allocation

(gnome-calculator:6871): WARNING **: 13:35:30.940: currency-provider.vala:161: Couldn't download IMF currency rate file: HTTP/2 Error: NTERNAL_ERROR

(gnome-calculator:6871): libsoup-WARNING **: 13:35:30.940: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0)

(gnome-calculator:6871): libsoup-WARNING **: 13:35:30.940: (../libsoup/soup-connection-manager.c:78):soup_host_free: runtime check failed: (host->conns == NULL)

Only the first error showed up in the alternate user. So this is a configuration problem with the gnome-calculator files for some users using currency exchange.
And not related to any other issue. All I have to do is find the configuration files and wipe them, and stop using the currency exchange update.
A red herring.
<<<<<<<<<<<<<<<<

Triggered suspend ... and received the message 'failed to lock screen',
and the system does not suspend.

But it will be some time before I know if the pointer click is corrected.

I will hold off installing xscreensaver or any other changes until I know current status.
Which means I must power off manually.

Currently running:
lightdm
xfce4-power-manager

Considering as options (but have not investigated at all)?
cryptsetup-suspend?
autosuspend?
qshutdown?
nvidia-suspend-common
not consiering: exit-options for MX Fluxbox
and the x window screen saver.

I do need the system to lock whan I am away from it.

Note: I neglected to point out that the nvidia card in the Dell M6800 is a bit notorious.
I have not loaded a propriatary nvidia driver.
Started to explore it ... to see if they could correct the issue.
Dell's nvidia is too quirky for use.

Still dreaming about hibernate.
Really miss that feature.

[Nokkaelaein]

In the possible case that you really removed xfce itself, know that Charles meant remove xfce4 screensaver, not the whole xfce desktop environment.

[CharlesV]

Lets see if that stops the initial problem and then we can add things back in, get things working smoothly and hopefully nto break anything along the way.

Just an fyi here I use xscreensaver on ALL machines I build (60+ and counting) and it works! I dont have many people that hibernate, but a few that do and we dont have issues with that. And my HP laptop I have set to never suspend etc, unless it goes too far down on battery and then it hibernates and wakes up pretty much without issue. (a few times I have seen its WiFi be slow, but still working.)

[CharlesV]

In the possible case that you really removed xfce itself, know that Charles meant remove xfce4 screensaver, not the whole xfce desktop environment.

Eeek.. I didnt see that.. you could be right!

[prairie_dog]

Thanks to Charles V, I realized that xfce4-screensaver was the trigger, but not necessarly the cause. That left suspend as a possible cause. I am sorry but at this point I am unsure if suspend trying to activate on a 2nd logged in user was part of my issue. It may have been because switching to a second user with suspen actvie and pending often triggers a suspension.

I turned OFF the requirement to lock screen on suspend. This allowed suspension.

When I suspend and resume the point and click no longer functions.

Switching user via the dual user script system corrects the issue until the next suspend.
But not every time. As I tried the suspend with a second user active, suspend resumed to a working system.
Without the second (ctrl-alt-F8) user logged in, but the screen on the login prompt, the 2nd x-window did not
correct the issue. That is just a trial of one or two times.

I will have to reboot, suspend without a second active user x-login to see if the problem shows up again
and perhaps explore the conistency of behavior.
I will have to post this first.

Somewhere between possibly and probably this has something to do with the nvidia card.

The package nvidia-suspend-common ... which I had previously investigated ... provides nvidia power management integration with systemd.
Installing nvidia-suspend-common triggers an update to nvidia-detect. I did not install the package nvidia-suspend-common.

Nvidia-detect searches for proprietary drivers for nvidia cards. I did install nvidia-detect about a week ago but I did not install any drivers from its search, as it provided a very long list and I could not find a compatible driver. If I were to find a compatible driver, nvidia-detect may be a solution. The proprietary nvidia drivers contain a risk of a requirement for use of timeshift. And I do not know if that will work yet, and hesitate to experiment that much.

For solutions:

I think I have a Dell Radeon card that can be used in this machine.
That may solve the issue and thus be a possible solution via hardware change.
Some risk in the trial.

I believe I could install xsecurelock to lock the screen without suspension ... or go back to xfce4-screensaver as a screen lock. That could possibly allow suspension with screen lock and I could suspend and then on resume use the switch-user button to correct the issue caused by suspend. My impression is that is not a reliable fix while using xcef4-screensaver.

Perhaps I could just leave the alternate 2nd user x windows session open on ctrl-alt-F8 with no power management for that user. In a trial just now, with the 2nd x-windows session active but not logged in on ctrl-alt-F8, the pointer malfunctions and switching to ctrl-alt-F8 does not correct the issue. Switching to a logged in 2nd x-session user and back to ctrl-alt-F7 does correct the issue.

So the question has become is there any other suggestion to correct or identify the resume from suspension glitch which is possibly related to the nvidia card?

My opinion, this is not a common issue .. and probably related to hardware. It does appear somewhat common with nvidia cards, but is correctable with other drivers.

nvidia-suspend-common which are scripts that rely on systemd does not seem a viable option.

Someone else with more knowledge may know better.

At least there appears a way to function without using a system where the pointer will not click.
Just use one user, no power management, no suspend, and power off when I leave the machine.

Makes my choice of entering the encryption key manually and not using LUKS look pretty idiotic.
I wish there was an option on the install to automatically and easily separate the /home into an encrypted btrfs partition, (and / also separate and encrypted) with a separate swap partition.

Thank you all very much. Sorry this reply is not shorter.

[CharlesV]

I install xscreensaver (not to be confused with xfce4-screensaver, they are totally different!)

xscreensaver is in the repos and is part of my standard installation (ie all machines I build get it!) This has stable saver functions, as well as stable lock functions.

There are a few additional things that you can check out, but start with xscreensaver.

a) I run only Liquorix kernels (also in the mx repos ) and I have found them to be highly stable (more stable than the 6.1 regular for some machines), they are 'faster / smoother imo ) and also they help resolve various issues on some machines - some like this.

b) Locking the machine *before the suspend" may help. Timing can be critical, so screen saver engaging and locking, THEN suspending 5 min later... could resolve this possibly. Also look the other way around - dont lock on screensaver, but engage it, then suspend. And finally even with xscreensaver installed.. just dont have it engage.

c) There are numerous reports here in the forum of suspend causing issues with certain usb devices - keyboards or mice not working after a suspend. Sometimes this can just be the device, sometime it is the base machine or driver. And if this is the case, changing the say the usb works at suspend time, or not allowing the usb to 'turn off' at suspend can help here.

d) Your bios! Some bios's are not good about how they sleep / suspend. Some have trouble or settings which help them 'recover' devices. I have seen some Dell's require "legacy" being set in the bios to help machines recover. Also, if your machine has Windows Fast start - turn it off, or an OS setting - make sure that is set to 'other' .

[prairie_dog]

I promise you CharlesV, I will follow your advice to the letter.

Nothing else. Just your advice on all points.

I will report back. It is the only way I have of saying thank you.

Will take me a while. xscreensaver was easy. And somehow I think I got it to suspend.

But I am sorting out the suggested scripts on forums intended to trigger suspend "properly".

Most are related to systemd.

I will understand the screensaver operation better when I have time to study command options.
=====
I did manage (I think) to lock screen prior to suspend, following your advice (b).

On resume I still had to use the keyboard to switch to an empty workspace (ctrl-f2) and Alt-F4 to
bring up the logout/restart/shutdown/suspend/switchuser selection; switchuser ... on the first time
after reboot and to login to another basic user account; and then Alt-F7 back to my main account.
Where the pointer will then function.

Otherwise I now leave the 2nd user running. Bit of a security loophole.
I will add a lock screen with no suspend.

I can then work without trouble until I let the system suspend again.
Which is only about 30 times a day.
========
Concering advice (a)
I found a prior post of yours suggesting liquorix 6.12.
That is the latest in the time range I am looking for.
This post: (What liquorix should I use.)
viewtopic.php?t=84844

That kernel is in my plan. Sooner rather than later.
=======
Your advice (c) concerning usb has made me wonder.

I use internet via a tethered phone via usb and have done so for years.
I will investigate if the tethered usb phone might be part of the issue in the current system.

Thank you for another item to check on.
It never occurred to me that I could keep the usb from suspending.
I see how that could even be a triggering issue. Since after resuming
from suspend I usually but not always have to toggle tethering on the phone
to tell the computer it exists.

I never setup an automatic toggle on the phone to toggle on when detecting the active computer coming online
or toggling off when detecting the computer going offline. The phone has no problem with that.
The computer does.

That is a possible trigger. Perhaps low possiblity. But worth my time to learn.

Your advice (d) on checking bios. I think I am okay with the settings there. But will verify on next boot.
That is not to say there are not bios issues.

Dang. You list item after item that each could be the root issue.

Fantastic acuity. I bet that is genetic ... Now I will have to investigate if acuity is possibly genetically linked.

They claim to have found a genetic link to excessive generosity.

Hope you have a nice day.
Thank you.