Mouse not recognized Suddenly

[Munguasafiwe]

Is there a fix for this problem of unresponsive mouse and keyboard coming out soon? I would like to switch my graphics display back to Wayland from X11. I had this problem before that was cured by switching to Wayland:

Computer locks up with LibreOffice

If I’m working on a project with LibreOffice Writer or Impress, after some time LibreOffice will lock up. Sometimes it locks up just those two programs, other times it locks up the computer. In the first instance, I can shut the computer down using the normal shutdown with the mouse clicking on icons in Tumbleweed. In the second instance, I have to shut the computer down using the power supply power switch as nothing on the desktop responds to mouse clicks. The computer is running Tumbleweed…

[qwert.zuiop]

Pull out mouse and plug in again

This is my current fix for 2.5G wireless devices.

mouse, keyboard, keypad.
I unplug the hub or the dongle and plug-in again.
Works but recent updates make the usb hiccups more frequently.

[knurpht]

From KDE, logout. At the SDDM login screen there’s a selector at the bottom left. You can choose “Plasma X11” and “Plasma Wayland”. Pick the latter and see if the issue disappears.

[Munguasafiwe]

Thanks everyone for their suggestions.
Pulling out the mouse usb plug and reinserting it doesn’t work, I mentioned that in my first post to this thread in my explanations of what I’ve tried for troubleshooting.

Regarding selecting Plasma Wayland, when operating in Plasma Wayland, the mouse is not recognized. I mentioned that that distinction in my post regarding alternately selecting Plasma X11 or Plasma Wayland.

Sorry, the modification to the .config/environment.d/kwin-cursor.conf didn’t have any effect.

[deano_ferrari]

Try adding the nvidia_drm.modeset=1 parameter to your GRUB boot configuration. Do this on a temporary basis initially:

• Reboot, and at the GRUB menu, highlight the openSUSE entry, and press ‘e’ to edit.

• Find the entry starting with linux and add the parameter at the end of it. CTRL +X or F10 to boot.

See if that makes a difference with the Wayland session mouse behaviour. You can make it permanent if it helps.

[Munguasafiwe]

I tried modifiying GRUB as you instructed, and on each of two tries it made no difference. In Plasma Wayland the mouse isn’t recognized.

[deano_ferrari]

Thanks for the update. I assume that the impacted system is fully updated?

I have no further ideas…this looks like a Wayland/KWin + NVIDIA environment-specific problem. You may want to create a bug report with the details above.

Include inxi -GSaz, and the steps (as per above) that you tried so far.

[deano_ferrari]

Hmmm…related to this topic?

[Munguasafiwe]

Yes, the system is fully updated (zypper -vvv dup). It seems from other posters to this thread that the problem is related to the udev latest revision. I wasn’t able to reinstall the earlier version due to a dependency issue that I can’t satisfy. This is detailed in an earlier post I made to the thread.
It does seem that the topic posted asking if the problem in this thread is similar, is probably the same issue. I’ll file a bug report when I figure out how to do it.
Thanks for everyone’s assistance.

[malcolmlewis]

@Munguasafiwe It’s a pure Plasma/Wayland issue. Else it would not be working on other Desktop environments with Wayland…

I’ve seen no issues here with MicroOS/Hyprland, Aeon and GNOME DE’s…

[Munguasafiwe]

I’ve tried to file a bug report, but had to make a new account to do so. The bugzilla requires a token sent to my email address to let me post after I submitted my info to establish an account. It doesn’t seem to be working, as I haven’t received an email with a token necessary to access the newly created account. I’ll give it a while to think and maybe send me the token requested, but if not I will try to establish an account with a different username sometime later today.