System fails to sleep, can't wake from suspend, with KDE, when Onedriver is mounted.

[averagejoey2000]

System Information

averagejoey2000@Mjolnir-Endeavour 
--------------------------------- 
OS: EndeavourOS Linux x86_64 
Host: 82FG IdeaPad 5 15ITL05 
Kernel: 6.9.9-arch1-1 
Uptime: 1 hour, 2 mins 
Packages: 7 (npm), 2592 (pacman), 8 (steam) 
Shell: zsh 5.9 
Editor: VIM - Vi IMproved 9.1 
Resolution: 1920x1080 
DE: Plasma 6.1.3 [KF5 ] [Qt ] (wayland) 
WM: kwin_wayland_wr 
Theme: Breeze-Dark [GTK2/3] 
Icons: breeze [GTK2], Colorful-Dark-Icons [GTK3] 
Cursor: whiteglass [GTK2], breeze_cursors [GTK3] 
Terminal: tmux 
CPU: 11th Gen Intel i7-1165G7 (8) @ 4.7GHz 
GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] 
Memory: 6.69 GiB / 11.47 GiB (58%) 
Network: Wifi6 
Bluetooth: Intel Corp. AX201 
BIOS: LENOVO 1.63 (10/12/2021) 

It took me a couple weeks of narrowing down possible culprits. I determined that systemctl suspend works with other DEs, I do not get this bug on LXQT or Hyperland.
I thought it was a problem with KDE itself, but reviewing sudo journalctl -b -1 gist shows that while all the other processes are trying to stop, OneDriver is filling the journal with errors.
Stopping Onedriver and unmounting my drives allows my system to sleep and recover in the normal way.

When I suspend the system, either with the sleep button, allowing the computer to sleep from inactivity, closing the laptop lid, or with systemctl suspend (with or without sudo), the screen goes black but my cursor is still visible and the blacklight is on, the fans are still active meaning the laptop has not physically entered sleep, and I cannot meaningfully interact with the system. Moving the mouse or touching the keyboard does not wake the system, I cannot to get other TTYs, and even pressing the Caps Lock and Num Lock buttons didn't change the indicators.
The only way to wake my system is to hold power button and reboot.

I think this might be related this issue.
When I tested with KDE/X11 or KDE/Openbox, I hit suspend and I got a strangely degraded system. I can move the cursor but not click or type. I can get other TTYs but they freeze after some inputs. I get the "failed to freeze user-1000.slice" like this person and I sometimes got "freezing of tasks failed after 20.006 seconds", the 20.006 is both notable and common.
I believe that onedriver's behavior when systemd is trying to reach stop or suspend targets is causing whatever timer is responsible for controlling sleep and wake functions to give up. Don't know how, don't know why, don't know what you can do about it.

(Including this next part so my bug report shows up in search terms)
If you are running KDE, Intel Graphics and CPU, with onedriver, and your system hangs or freezes or crashes or dies when you try to sleep or hybernate, onedriver might be the issue.