Mouse not working: upgrading from Ubuntu 20.04 to 22.04

Hello,

Is your Ubuntu session a Wayland session or an X11 session?

If it's a Wayland session (usually the default on Ubuntu 24.04), reconnect to an X11 (or Xorg) session and see if it works.

Hello,

Does your mouse work with another PC/operating system? Do you have the same problem with another mouse? Normally, USB mice work without issues, so it suggests a hardware problem.

Regarding the errors:

• In the logs:
  • The errors you're reporting mean that someone tried to unload modules without having administrative rights (without being root). If you remember doing this, it's just a trace of that incorrect action. In any case, the mentioned modules are not related to your mouse.
• Error in the repositories: this error means that a repository currently configured in the APT manager is incorrect. It can be easily fixed
  • You should change the URL listed in this entry. This is written in /etc/apt/sources.list or in one of the files in /etc/apt/sources.list.d and correct it (or remove it).

    sudo gedit /etc/apt/sources.list &

    I think in your case it's more like (see the tutorial here)

    deb [arch=amd64 signed-by=/etc/apt/keyrings/rocm.gpg] https://repo.radeon.com/amdgpu/latest/ubuntu jammy main

    . Once the correction is made:

    sudo apt update

Good luck

Hello,

Thank you for your help and the very useful link. I noticed that the mouse was working fine when using a live version with Ventoy but intermittently with the installed version:

• Ubuntu mate 22.04
• Linux bernard 6.10.11-zabbly+ #ubuntu22.04 SMP PREEMPT_DYNAMIC Fri Sep 20 10:05:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Since yesterday, it is no longer functional.

I checked the mounting of the file /lib/modules/6.10.11-zabbly+/kernel/drivers/usb/storage/usb-storage.ko which I reloaded, with no result.

• sudo dmesg | grep -i usb gives me:

[ 2.142377] usb 3-2: Product: USB2.0 Hub
[ 2.157181] usb 1-4: New USB device found, idVendor=1c4f, idProduct=0034, bcdDevice= 1.10
[ 2.157193] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.157197] usb 1-4: Product: Usb Mouse
[ 2.157201] usb 1-4: Manufacturer: SIGMACHIP
[ 2.186303] hub 3-2:1.0: USB hub found
[ 2.191510] input: SIGMACHIP Usb Mouse as /devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb1/1-4/1-4:1.0/0003:1C4F:0034.0002/input/input7
[ 2.191719] hid-generic 0003:1C4F:0034.0002: input,hidraw1: USB HID v1.10 Mouse [SIGMACHIP Usb Mouse] on usb-0000:03:00.3-4/input0
[ 2.191775] usbcore: registered new interface driver usbhid
[ 2.191779] usbhid: USB HID core driver
[ 2.193467] usbcore: registered new interface driver usbmouse
[ 2.476617] usb 3-2.1: new high-speed USB device number 3 using xhci_hcd
[ 2.600827] usb 3-2.1: New USB device found, idVendor=13d3, idProduct=56dd, bcdDevice=18.52
[ 2.600840] usb 3-2.1: New USB device strings: Mfr=3, Product=1, SerialNumber=2

but also this message at the end of the message:

[ 7.865681] usb 3-2.1: Found UVC 1.50 device USB2.0 HD UVC WebCam (13d3:56dd)
[ 7.889857] usbcore: registered new interface driver uvcvideo
[ 9.985632] usb 3-2.1: Failed to suspend device, error -19
[ 11.662948] usb 3-2.2: Failed to suspend device, error -19
[ 13.348480] usb 1-4: USB disconnect, device number 2
[ 16.776484] usb 3-2.1: Failed to suspend device, error -19
[ 19.052505] usb 3-2.2: Failed to suspend device, error -19
[ 20.920400] usb 3-2.1: Failed to suspend device, error -19

I could send you the entire message, but I don’t know how to do that!

If that helps you since I don’t know how to interpret the end of the file.

Best regards.

ps: the problem affects the functioning of both mice.

A clarification: the observation remains the same regardless of the core used.

Hello,

Sorry, I didn't see the message #3, which is why I didn't reply. I see in the logs that the USB device associated with your mouse seems to be created correctly. However, the error:

 Failed to suspend device, error -19

... seems to be the cause of the problem, and we need to find out what it means.

This seems to resemble this problem or that one or even this one, which mention a USB power issue, and there's talk of a USB hub, so can you let us know if you're in that scenario?

Good luck

Hello,

I did a large number of tests and discovered something that intrigued me. As mentioned, I'm using Ubuntu Mate with Lightdm as the display manager. I tested gdm3 and the mouse came back to life! Not being comfortable with that environment, I returned to Lightdm and the mouse stopped working again.

In live mode, the mouse works with Linux Mint, Zorinos, Emmabuntus, etc.

An essential point: USB keys are not recognized by Ubuntu Mate (Lightdm), which might explain the lack of recognition of the mice.

I don't see how to solve this problem. I'll keep looking!

Have a nice day and thank you.

Hello,

Something intrigues me in your response #6. I think you are confusing display manager (like lightdm, gdm, sddm, ...) and desktop environment (like gnome, mate, KDE, ...). The display manager allows you to choose which desktop environment (among those installed) to launch and with which user profile.

The confusion is legitimate in the sense that usually only one display manager and one desktop environment are installed. Generally, we choose them so that they rely on the same technologies (for example, KDE often goes with sddm, Gnome with gdm or lightdm, etc.). However, it is perfectly possible to install multiple display managers and/or multiple desktop environments simultaneously; it just takes up more disk space.

So, if I return to your message #6, what did you mean?

• Is it "with mate, I have problems, with gnome, it works but I'm not used to this graphical environment (regardless of the display manager)"?
• Or did you mean that with mate, depending on whether it is launched via lightdm or gdm, the behavior is not the same?

Here are a few points I would like to bring to your attention:

• Whatever the distribution / display manager / graphical environment you have installed: nothing prevents you from installing other desktop environments / display managers.
  • There is therefore no difference between Ubuntu Mate, Ubuntu (gnome), Xubuntu (xfce) or Kubuntu (KDE): it is actually just one and the same distribution; the only thing that changes are the packages deployed during installation.
• If you install multiple display managers, your package manager will ask you to choose which one to launch at startup.

Depending on the incriminating element (either mate or lightdm), you can totally install an alternative (for example gdm if the problem comes from lightdm, and the graphical environment of your choice if the problem comes from mate).

If the problem seems to come from the graphical environment, you should check if the problem persists by creating a new user. If so, it’s probably a bug that should be reported. Otherwise, something is likely wrong with your user profile.

Finally, you haven't replied to my message #5: are you using a USB hub?

Good luck

Hello,

I understand better now because I was simply thinking of modifying the login manager... In fact, the desktop environment was installed instead of Lightdm.

When I mentioned that the problem had disappeared, it was with GNOME. I did notice that a significant number of programs were installed. And as often, it was dependencies... I wasn't attentive enough.

Otherwise, I don't use a USB hub unless I'm connecting to the box with an RJ45/USB adapter that offers USB slots or when I launch live programs with Ventoy for Linux presentations.

Could you tell me how to install only the login manager because the installation via the command line or Synaptic forces the installation of GNOME... At least, that's what I understood.

sudo apt-get install gdm3

Have a good afternoon.

Hello,

Response to #8

Installing a display manager is done like any other package. You can indeed run:

sudo apt update sudo apt install gdm3

As shown by:

 apt show gdm3

You can see that the gdm3 package depends on GTK and libgnome. This is actually why lightdm was designed.

Indeed, each display manager relies on a technology, for example:

• Glib for lightdm
• GTK/libgnome for gdm
• X11 for xdm
• Qt for ssdm, etc.

... just like the desktop environment:

• GTK/libgnome for gnome,
• Qt for KDE,
• X11 for icewm
• ....

To install fewer packages, it is therefore preferable to use a display manager whose dependencies coincide with the (or one of the) installed desktop environment(s).

Back to your initial problem

I have the impression that the problem comes more from the desktop environment than from the display manager. Do you confirm?

For example, if you tell me that "it works with gnome but not with mate" when starting them with the same display manager, it is indeed evidence that the culprit is the desktop environment (or its configuration), and not the display manager or the operating system (e.g., udev). And if it doesn’t come from the display manager, installing and using gdm3 instead of lightdm won’t help you.

If the problem indeed comes from the desktop environment (so mate), it is necessary to determine whether it is due to:

• user configuration
• global configuration
• the software itself

If by creating a new user and launching a graphical session with that user, the problem persists, then it’s your current user profile that is at fault (i.e., one of the files stored in your home directory).

If you have tinkered with global configuration files (i.e., in /etc) related to mate, that could be the source. If you haven't done anything there, you can probably rule that out.

If you observe your mouse problem still with mate, but in different contexts (for example different distributions, your installation, a live USB/CD...) but not with other desktop environments, it is likely a bug in mate (or in the default configuration of mate).

Good luck

Good evening,

Your explanations are always so clear.

To answer your first question, the problem seems to stem from the environment. I created another user and the mouse worked for a good while before freezing.

I did quite a bit of "testing" by upgrading to version 22.4.5 and other trials that led me to reinstall Ubuntu Mate version 22.04.01. (I have a /home partition). It's a distribution I enjoy because I find it very user-friendly.

There's one point that intrigues me. During the installation, the mouse didn't cause any issues. It's true that it was not used much.

After the installation, it worked for a while and then stopped without any explanation from my side. Since everything was recent, I copied the logs. The solution may be in those lines.

I then installed the amdgpu-dkms packages.

The processors of the PC:

AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx00:02300,00 MHz

 deb https://repo.radeon.com/amdgpu/6.2.1/ubuntu jammy main deb https://repo.radeon.com/rocm/apt/6.2.1 jammy main 

This conflicted with existing files (amdgpu) so I disabled the above repositories.

I also just noticed that USB sticks are no longer recognized either.

Here is the end of dmesg |grep usb:

..............

[2.233639] input: Logitech Wireless Receiver Mouse as /devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb1/1-1/1-1:1.0/0003:046D:C542.0002/input/input7
[ 2.233837] hid-generic 0003:046D:C542.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech Wireless Receiver] on usb-0000:03:00.3-1/input0
[ 2.233892] usbcore: registered new interface driver usbhid
[ 2.233895] usbhid: USB HID core driver
[ 2.533349] usb 3-2.1: new high-speed USB device number 3 using xhci_hcd
[ 2.636420] usb 3-2.1: New USB device found, idVendor=13d3, idProduct=56dd, bcdDevice=18.52
[ 2.636439] usb 3-2.1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 2.636447] usb 3-2.1: Product: USB2.0 HD UVC WebCam
[ 2.636455] usb 3-2.1: Manufacturer: Azurewave
[ 2.636462] usb 3-2.1: SerialNumber: 0x0001
[ 2.764446] usb 3-2.2: new full-speed USB device number 4 using xhci_hcd
[ 2.860195] usb 3-2.2: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.10
[ 2.860211] usb 3-2.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.990366] usb 3-2.3: new full-speed USB device number 5 using xhci_hcd
[ 3.099140] usb 3-2.3: New USB device found, idVendor=04f3, idProduct=0903, bcdDevice= 1.67
[ 3.099151] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.099156] usb 3-2.3: Product: ELAN:Fingerprint
[ 3.099161] usb 3-2.3: Manufacturer: ELAN
[ 4.368461] usbcore: registered new interface driver btusb
[ 4.483623] usb 3-2.1: Found UVC 1.50 device USB2.0 HD UVC WebCam (13d3:56dd)
[ 4.499478] usbcore: registered new interface driver uvcvideo
[ 6.998387] usb 3-2.1: Failed to suspend device, error -19
[ 8.328473] usb 3-2.2: Failed to suspend device, error -19
[ 14.888477] usb 1-1: USB disconnect, device number 2
[ 15.984378] usb 3-2.2: Failed to suspend device, error -19
[ 17.946383] usb 3-2.1: Failed to suspend device, error -19
[ 29.519411] usb 3-2.1: Failed to suspend device, error -19

The mouse is indeed recognized...

The logs are numerous. In which file could we find a clue?

-rw-r--r-- 1 root root 50449 Sept. 26 10:38 alternatives.log
-rw-r----- 1 syslog adm 23432 Sept. 26 11:31 auth.log
-rw------- 1 root root 53189 Sept. 26 11:20 boot.log
-rw-r----- 1 root adm 91773 Sept. 26 11:20 dmesg
-rw-r----- 1 root adm 92684 Sept. 26 11:14 dmesg.0
-rw-r--r-- 1 root root 1392205 Sept. 26 10:38 dpkg.log
-rw-r--r-- 1 root root 32032 Sept. 26 10:25 faillog
-rw-r--r-- 1 root root 12395 Sept. 26 10:38 fontconfig.log
-rw-r--r-- 1 root root 1383 Sept. 26 11:20 gpu-manager.log
-rw-r--r-- 1 root root 1390 Sept. 26 11:19 gpu-manager-switch.log
-rw-r----- 1 syslog adm 832263 Sept. 26 11:22 kern.log
-rw-rw-r-- 1 root utmp 292292 Sept. 26 10:25 lastlog
-rw-r--r-- 1 root root 55 Sept. 26 11:20 prime-offload.log
-rw-r--r-- 1 root root 30 Sept. 26 11:20 prime-supported.log
-rw-r----- 1 syslog adm 2182518 Sept. 26 11:31 syslog
-rw-r--r-- 1 root root 2177750 Sept. 26 11:24 syslog.txt
-rw-r--r-- 1 root root 28921 Sept. 26 11:20 Xorg.0.log
-rw-r--r-- 1 root root 30061 Sept. 26 11:19 Xorg.0.log.old

Have a good evening

Hello,

Once again, the mouse is not working. I recorded the logs right after it became inactive. I selected the following logs by extracting the part that relates to the last few minutes:

• syslog
• kern.log
• auth.log

I have them available in PDF format. The number of pages is very limited.

If that helps!

A recurring question I have. Why does the mouse work normally for an hour until the PC is shut down, but fails to wake up when the computer is turned back on? It's not systematic; it can also freeze while in full activity.

Hello,

I'm wondering if your problem is more related to sleep mode, or at least the sleep mode of your mouse.

Roles of the most "famous" logs

Regarding the logs, to know where to look, you need to see in the documentation what they refer to:

• /var/log/Xorg.0.log : graphic server, if the problem is specific to graphical mode, we can find things there
• /var/log/auth.log : relates to authentication, we probably won’t find anything here
• /var/log/kern.log : kernel log, since the problem seems related to hardware support, we might find something there. But if you've concluded that it's a problem specific to a graphical environment (for example, specific to MATE), the problem comes from "higher up"
• /var/log/syslog : system log, same.

Software layers and logs

I will now explain this notion of "higher up". Basically, Linux (and generally any operating system) is broken down into layers. From the closest to the hardware to the closest to the user, these layers are in this case:

• The hardware itself
• The kernel (or the kernel module that supports the mouse), that is, the software layer that takes care of (among other things) the hardware. In Windows terminology, you can think of this as a big "driver," even though it's a bit more complicated.
• The operating system (more particularly udev, hibernation...), which allows you to use your computer.
• The graphic server (Xorg=X11 or Wayland…). Depending on where we are in the boot process:
  • Either the login manager (lightdm, gdm, sddm, ...)
  • Or the graphical environment (mate, gnome, KDE...)
• The application in use
• The user

In this list, as long as we are not yet at the graphical session, there is no identified user, so everything is executed as root (once the kernel is loaded). Any logs will be located in /var/log.

Beyond that, from the system's perspective, these are processes launched by a user, and any logs will be hidden somewhere in their home directory.

Note that services (for example, the ssh server, a potential web server or database) are launched by root or a dedicated user and their logs are also generated somewhere in /var/log.

Examining logs

Strategy 1: in real time: When you don't know which log to look into, one technique is to monitor log files in real time with tail -f. Suppose you want to check system/kernel-specific logs:

tail -f /var/log/*log tail -f /var/log/kern.log /var/log/syslog

... then, when the problem occurs, see the last messages that appeared. Of course, the more you narrow down the files to monitor, the less unrelated information you'll display. You can stop the monitoring with ctrl c. You can also open multiple terminals, each responsible for monitoring a particular file.

Strategy 2: afterwards: you look at the times when the problem occurs with your favorite text editor or a command such as cat, more or less the log of your choice.

Back to your problem

What’s strange about your problem is the "it works for a while, then it doesn’t work anymore" aspect. Here are the possible causes I see:

• Damaged RAM: but you would probably have other symptoms
• Damaged hardware: testing with another mouse of this model would help determine that
• Bug in the kernel or in a module: testing another distribution using a different kernel would help confirm or rule out this lead
• If it follows a hibernation, an implementation issue related to hibernation.
• A buggy power-saving mechanism (which seems consistent with the logs). In which case, we could see if disabling USB power saving resolves the issue (see here).

But you seem to say that the problem appears to be related to a particular graphical environment (and not the others) so another cause. It would be necessary to test longer to see if this is true, by using another graphical environment (let's say gnome) for a longer period.

• If no problem occurs, you should also check if error messages continue to appear in the logs (in which case, these log messages are not important and do not help to find the cause of the problem).
• You could then solve your problem by deciding to abandon mate.

Regarding the logs you kept

If they are short, you could just attach them to your next message and share them as you would for a code snippet.

Good luck

Hello,

After running some tests, I found that the mouse works ... when changing distributions.

Tests and Observations (summary)

When I access the BIOS to modify the boot order (tests with a live USB using Ventoy), the mouse is active. The same goes for live distributions.

One last detail. When I start Ubuntu Mate, the mouse pointer remains frozen. However, upon user login after entering the password, the cursor reacts by changing into a spinning circle while waiting for the selected profile to log in. Then it returns to its original shape, an arrow, without having moved an inch. I don't know how to explain that.

The "solution"

I then replaced Ubuntu Mate 22.04 with Zorin OS 17 (a nice distribution, by the way). The mouse worked normally. Since I am attached to the Mate environment and Caja, I have permanently migrated to Linux Mint 22 Mate based on Ubuntu 22. Everything is working wonderfully.

This does not resolve the issues encountered. I have log excerpts available, but given their length, I don't want to "asphyxiate" the forum!

Thank you again for your relevant advice and your always very informative responses.

Have a great weekend.

Good evening,

Indeed, I was mistaken in stating that Linux Mint was based on Ubuntu 22.04!

Thanks again for your help and for the knowledge you constantly share with us.