OK . . . just “noise” in the “signal to noise” ratio?? This install is running on nvme drive. The new install, likely now unnecessary, is on a SATA SSD . . . . Guess I could check out the same commands over on that install . . . but, for now, the glitchy behaviors are not replicating.
“Awareness IS Action”???
Good. You only need to report if/when it does.
Alrighty. Back atcha if and when there is a recurrence. Just checking to see if any of the previous comments might show some hint on the issue . . . which may or may not be gone, with no params on the “why” of it thus far . . . .
So, the “not typing in Google Voice test message box” . . . just briefly occurred in my Manjaro install. Realizing that Manjaro is not in the purview of this forum, but previously I had narrowed it down to just Leap . . . now, it could be the shared DE of XFCE that might be involved??
I clicked in the box and the blinking cursor appeared, but typing on the keyboard did not type letters. I was able to click somewhere else and then back in the box and was able to type out the message. It didn’t “progress” as it did in the Leap install to the wonky mouse behaviors . . . etc. Unfortunately since I wasn’t expecting the problem I didn’t have the sudo journalctl -f command up and running . . . now that the cows are out of the barn I did . . . .
Point being it could be more “universal” too the machine or to the mobo (usb params) or to the DE than to just the Leap install?? It could be that it is afflicting the Leap install more overtly than in Manjaro . . . but has now seemingly escaped the confines of Leap . . . “jumping” over to other systems in an ad hoc manner???
It could very well be something upstream.
Hmm . . . now we are over to TW . . . this morning after logging in with password the mouse cursor “froze” . . . first no “light” from the bottom of the mouse, then unplugged it and back again, light came on but no movement of the mouse cursor. Unplugged the keyboard at the usb 3.2 port on the machine, plugged in . . . no change. Moved the mouse around a few times . . . nothing.
Then shut down with power button logged back in to observe the log in procedure . . . the log in window shows blinking cursor, so no need to mouse over to it . . . typing password gets to GUI and this time mouse is working.
Exploring the possibility of some “mobo” handling of usb ports I moved the usb cable from one of the usb 2.0 ports to the 3.2 yesterday and ran that on Leap 16 . . . everything worked well and fast. Then this morning TW’s mouse “froze” . . . adding to the number of “systems” that have had some aspect of this problem happen . . . .
You are jumping between different OS, boxes and topics. But the TW issue is known and fixes are provided.
I briefly saw the post on the Factory list-serve, but that appears to be a “wayland” based system, so far to my knowledge I am running X on all of my installs . . . . There is no “VT” aspect to this episode. The GUI loaded from log in password, then mouse froze, . . . ???
If you read down the thread, you will notice that also some X11 systems are affected.
Ah . . . OK, I will have to scroll through it . . . . Perhaps I have several issues that are overlapping across OSs and manifesting spontaneously in variation depending on how the stars are aligning??
Happy Lunar New Year!!!
If you don’t have the issue please hold back. Please.
What am I to “hold back” on?? If you read the subject line of this thread it says “mouse action glitchy” in Leap 16 . . . now I posted a “mouse frozen” problem, which I assumed was “the same problem,” but perhaps is yet another problem???
Sorry, was in the wrong thread.
OK, gave that thread a fast read . . . ran libddcutil through a YaSt search . . . shows “not installed” . . . so I don’t think that is the issue or solution in my case, although the reported log in behavior is similar.
I was noticing in the linked thread the words “Ryzen 7” seemed to be repeated . . . I am also running a Ryzen 7 cpu w/ integrated graphics . . . “coincidence” or “known issue”??
Your issue is from way before the bugs the other thread is about were instroduced, and not in Tumbleweed.
Alrighty, way before . . . and now seems to be “bleeding” over into others of my installs . . . this morning a very brief “freezing” of mouse cursor movement in my Sid install . . . . So it’s looking to be more “universal” in terms of “the machine” OR could be something that has found its way into “the kernel” that is growing or intermittent, making it harder to track down. Fortunately so far in Sid it was just a quick hiccup and then back to the biz.
@non_space checked your memory with memtest86?
Hmm . . . well Mr Sid “doesn’t recognize” that command . . . back to Leap 16 tomorrow. But, this is a “new” machine from May/June of last year . . . ???
memtest86+ is a separate boot https://www.memtest.org/
I think openSUSE provides memtest86+ it should add a grub stanza to boot from <== @mrmazda should be able to confirm.
