Logitech M325 wireless mouse Unifying Receiver stops working after logging into various sessions.

NuxIT · 04-24-2022, 03:00 PM

Hello, I recently was messing around and trying to disable the touch screen on my Ubuntu 20.04 load for the "Wayland" Session GUI. My screen is cracked so it causes it to freak out.

I currently have GNONE on Xorg, Ubuntu, Xfce, GNOME (wayland) and Ubuntu on Wayland (Wayland) sessions.
I probably should of left it alone since I was able to disable the touch screen without issues on Ubuntu & Xfce without issues. The Wayland is much more difficult and cumbersome to disable the touchscreen on.

Anyway, after I was doing various things to try and disable the touchscreen on Wayland session it seems to have broken the Logitech USB receiver for my mouse. Upon booting up and before logging into any of the above sessions the mouse works without issues. However, right after I login to any of the sessions it immediately stops working and I have to remove the mouse receiver and plug it back in. Then it works fine. I even tried a different USB port and a different mouse and have the same issues.

I noticed this in blacklist.conf but I believe this is default. I tried commenting out these two lines and rebooting but that did not help.

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

Any ideas why I have to disconnect the receiver and plug it back in AFTER logging in to any of my various sessions? Seems pretty strange but some command I ran when trying to disable my touchscreen appears to have cause this problem. I was also wondering if I could simulate removing and plugging in the USB receiver through a rc.local file or some automated way?

If the computer goes to sleep the mouse still works fine. It's only if I log out of the session or restart. The mouse works on the logon screen but as soon as I logon any session it stops working until I remove and re-insert the USB receiver. Appreciate any input or ideas.

Sorry if it's too much info but figured better to have to much than too little.

Code:

asus:~$ xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                	id=18	[slave  pointer  (2)]
⎜   ↳ Logitech M325                           	id=11	[slave  pointer  (2)]


asus:/etc/udev/rules.d$ sudo lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 03eb:8417 Atmel Corp. 
Bus 001 Device 004: ID 13d3:5188 IMC Networks 
Bus 001 Device 003: ID 8087:07da Intel Corp. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 004: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


asus:~$ dmesg |grep Receiver
[ 1347.539451] usb 3-3: Product: USB Receiver
[ 1347.547796] logitech-djreceiver 0003:046D:C52B.001D: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
[ 1381.770535] usb 3-3: Product: USB Receiver
[ 1381.779788] logitech-djreceiver 0003:046D:C52B.0021: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
[ 1416.050282] usb 3-3: Product: USB Receiver
[ 1416.059624] logitech-djreceiver 0003:046D:C52B.0025: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
[15692.122111] usb 3-3: Product: USB Receiver
[15692.130523] logitech-djreceiver 0003:046D:C52B.0029: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2

asus:~$ grep . /sys/bus/usb/devices/*/product
/sys/bus/usb/devices/1-1.2/product:USB2.0 UVC HD Webcam
/sys/bus/usb/devices/1-1.3/product:Atmel maXTouch Digitizer
/sys/bus/usb/devices/3-3/product:USB Receiver
/sys/bus/usb/devices/4-2/product:AX88179
/sys/bus/usb/devices/usb1/product:EHCI Host Controller
/sys/bus/usb/devices/usb2/product:EHCI Host Controller
/sys/bus/usb/devices/usb3/product:xHCI Host Controller
/sys/bus/usb/devices/usb4/product:xHCI Host Controller

asus:~$ usb-devices


asus:/var/log$ grep -i logitech syslog
Apr 24 10:57:44 asus kernel: [15692.122115] usb 3-3: Manufacturer: Logitech
Apr 24 10:57:44 asus kernel: [15692.130523] logitech-djreceiver 0003:046D:C52B.0029: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
Apr 24 10:57:44 asus kernel: [15692.256362] input: Logitech M325 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0029/0003:046D:400A.002A/input/input46
Apr 24 10:57:44 asus kernel: [15692.257566] logitech-hidpp-device 0003:046D:400A.002A: input,hidraw1: USB HID v1.11 Mouse [Logitech M325] on usb-0000:00:14.0-3/input2:1
Apr 24 10:57:46 asus kernel: [15693.504160] logitech-hidpp-device 0003:046D:400A.002A: HID++ 2.0 device connected.
Apr 24 13:43:39 asus kernel: [25646.408327] logitech-djreceiver 0003:046D:C52B.002D: hiddev2,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
Apr 24 13:43:39 asus kernel: [25647.239785] logitech-hidpp-device 0003:046D:400A.002E: HID++ 2.0 device connected.
Apr 24 13:43:40 asus kernel: [25647.381963] input: Logitech M325 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.002D/0003:046D:400A.002E/input/input49
Apr 24 13:43:40 asus kernel: [25647.382293] logitech-hidpp-device 0003:046D:400A.002E: input,hidraw3: USB HID v1.11 Mouse [Logitech M325] on usb-0000:00:14.0-3/input2:1

ferrari · 05-07-2022, 06:10 PM

Quote:

Any ideas why I have to disconnect the receiver and plug it back in AFTER logging in to any of my various sessions? Seems pretty strange but some command I ran when trying to disable my touchscreen appears to have cause this problem.

What command(s) specifically? That might help others advise more meaningfully here.

The dconf editor may be your friend...
https://wiki.gnome.org/Apps/DconfEditor
Navigate to / org / gnome / desktop / peripherals / and check to see if the device in question has been disabled there perhaps.

Just in case the following "how to" is useful to you...
https://www.linuxuprising.com/2021/0...hpad-when.html

ferrari · 05-07-2022, 06:20 PM

Another thought...are you managing the Logitech device with solaar?
https://www.omgubuntu.co.uk/logitech...r-linux-solaar
https://tutorialforlinux.com/2020/02...ation-guide/2/

Is it configured to autostart?
https://wiki.archlinux.org/title/Log...eceiver#Solaar

NuxIT · 05-08-2022, 01:53 PM

Quote:

Originally Posted by ferrari

What command(s) specifically? That might help others advise more meaningfully here.

Thanks for the responses! I'm going to look into what you mentioned now. I was letting my OCD get to me but this hasn't bothered me as much as I thought it would since I rarely reboot or log out of my session. It doesn't happen when the system comes out of hibernation so this hasn't been that big of a deal. It just irritates me that I might of borked this up messing around.

Here's some of the commands I was running when I was trying to disable the touchscreen interface in "Wayland" session.

Basically I was following this Guys Video.

And here's some of that output.

Code:

1933  sudo nano /usr/share/X11/xorg.conf.d/40-libinput.conf
 1934  sudo logoff
 1935  sudo reboot now
 1936  sudo liblinput
 1937  xinput
 1938  xinput disable 9
 1939  9999
 1940  sudo xinput disable 9
 1941  sudo libinput list-devices
 1942  sudo xinput
 1943  xinput
 1944  cd /etc/X11/
 1945  ls
 1946  ls -ltr
 1947  xinput --disable $(xinput --list | grep -i 'touchscreen' | grep -o 'id=[9]*' | sed 's/id=//')
 1948  ls /sys/bus/hid/drivers/hid-multitouch/
 1949  cd /etc/udev
 1950  ls
 1951  cd rules.d/
 1952  ls
 1953  cat /proc/bus/input/devices
 1954  cat /proc/bus/input/devices |grep touch
 1955  cat /proc/bus/input/devices |more
 1956  cat /proc/bus/input/devices |grep tou
 1957  cat /proc/bus/input/devices |grep -i to
 1958  vi 80-touchscreen.rules
 1959  sudo vi 80-touchscreen.rules
 1960  udevadm control --reload-rules && udevadm trigger
 1961  sudo udevadm control --reload-rules && udevadm trigger
 1962  sudo vi 80-touchscreen.rules 
 1963  sudo udevadm control --reload-rules && udevadm trigger
 1964  sudo vi 80-touchscreen.rules 
 1965  cd /etc/modprobe.d/
 1966  ls
 1967  vi hid_multitouch.conf
 1968  sudo vi hid_multitouch.conf
 1969  sudo reboot now
 1970  xinput
 1971  xinput disable 9
 1972  sudo xinput disable 9
 1973  cd /etc/modprobe.d/
 1974  ls
 1975  vi hid_multitouch.conf 
 1976  sudo vi hid_multitouch.conf 
 1977  sudo reboot
 1978  whoami
 1979  lsb_release -a
 1980  echo $SHELL
 1981  xinput
 1982  cd /proc/bus/
 1983  cd /etc/udev
 1984  cd rules.d/
 1985  ls
 1986  sudo vi 80-touchscreen.rules 
 1987  history
 1988  sudo udevadm control --reload-rules && udevadm trigger
 1989  sudo rm 80-touchscreen.rules 
 1990  cd /etc/modprobe.d/
 1991  ls
 1992  sudo rm hid_multitouch.conf 
 1993  ls

I also learned a few new commands to get some "interesting" output when removing and plugging in the Logitech receiver.

Code:

asus:~$ sudo journalctl -f 
REMOVE Receiver (One Entry)
Apr 24 14:03:02 asus kernel: usb 3-3: USB disconnect, device number 12

PLUG in Recevier (Multiple Entries)
Apr 24 14:04:04 asus kernel: usb 3-3: new full-speed USB device number 13 using xhci_hcd
Apr 24 14:04:04 asus kernel: usb 3-3: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.10
Apr 24 14:04:04 asus kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 24 14:04:04 asus kernel: usb 3-3: Product: USB Receiver
Apr 24 14:04:04 asus kernel: usb 3-3: Manufacturer: Logitech
Apr 24 14:04:04 asus kernel: logitech-djreceiver 0003:046D:C52B.0033: hiddev2,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
Apr 24 14:04:04 asus kernel: input: Logitech M325 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0033/0003:046D:400A.0034/input/input50
Apr 24 14:04:04 asus kernel: logitech-hidpp-device 0003:046D:400A.0034: input,hidraw3: USB HID v1.11 Mouse [Logitech M325] on usb-0000:00:14.0-3/input2:1
Apr 24 14:04:04 asus mtp-probe[31989]: checking bus 3, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3"
Apr 24 14:04:04 asus mtp-probe[31989]: bus: 3, device: 13 was not an MTP device
Apr 24 14:04:04 asus mtp-probe[32014]: checking bus 3, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3"
Apr 24 14:04:04 asus mtp-probe[32014]: bus: 3, device: 13 was not an MTP device
Apr 24 14:04:04 asus thunar.desktop[32003]: thunar-volman: Unsupported USB device type "usb".
Apr 24 14:04:04 asus thunar.desktop[32022]: thunar-volman: Unsupported input device type "/dev/input/event6".
Apr 24 14:04:05 asus thunar.desktop[32034]: thunar-volman: Unsupported USB device type "usbhid".
Apr 24 14:04:05 asus thunar.desktop[32038]: thunar-volman: Unsupported USB device type "usbhid".
Apr 24 14:04:05 asus kernel: logitech-hidpp-device 0003:046D:400A.0034: HID++ 2.0 device connected.

NuxIT · 05-08-2022, 02:56 PM

Solid info ferrari!

I checked dconf and it appears my mouse is enabled?

Also, I'm not currently using Solar to manage my m325 mouse but it's listed as a supported device. I'll probably try that software out to see if that allows the mouse receiver to work when logging into a new session or rebooting without having to remove/re-insert the receiver.

ferrari · 05-09-2022, 03:28 AM

Hmmm...similar thread here...
https://forums.raspberrypi.com/viewtopic.php?t=310293
...users reporting that the Logitech input device is not recognized once the Wayland desktop session is started, however it does become functional if re-plugged. Inhibiting the hid_logitech_dj kernel module from loading is reported to help in that thread...

Code:

echo "blacklist hid_logitech_dj" >> /etc/modprobe.d/local-dontload.conf
echo "install hid_logitech_dj /bin/false" >> /etc/modprobe.d/local-dontload.conf
depmod -a
update-initramfs -u
reboot

Give that a whirl and report back!