Regression: Mouse stuck at start-up

This change was made by a bot.

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

Yes, this started happening when I updated to 16.04

2016-05-05 18:43 GMT+02:00 Joseph Salisbury <email address hidden>
:

> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.6 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1578317
>
> Title:
> Mouse stuck at start-up
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> My mouse is stuck at start-up. A workaround is to enter "sudo rmmod
> usbhid; modprobe usbhid" and the mouse starts working.
>
> josep@josep-GJ306AA-ABE-m8175-es:~$ lsusb
> Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card
> Reader/Writer
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 008 Device 005: ID 050d:016a Belkin Components Bluetooth Mini Dongle
> Bus 008 Device 004: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface
> Subclass)
> Bus 008 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface
> Subclass)
> Bus 008 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
> (part of BCM2046 Bluetooth)
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 004: ID 15d9:0a4c Trust International B.V. USB+PS/2
> Optical Mouse
> Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified:
> boot/vmlinuz-4.4.0-21-generic]
> ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
> Uname: Linux 4.4.0-21-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: josep 1664 F.... pulseaudio
> CurrentDesktop: Unity
> Date: Wed May 4 19:08:48 2016
> HibernationDevice: RESUME=UUID=b0bbcadd-00af-44cd-8f5d-eea7fee41c90
> InstallationDate: Installed on 2016-04-28 (6 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "X...

Same issue occurred in Fedora 23.
https://bugzilla.redhat.com/show_bug.cgi?id=1277837

Is this a bug of gnome-software or fwupd instead of linux.
If "/etc/xdg/autostart/gnome-software-service.desktop" is removed, then logout and login,
doesn't this problem occurred?

I installed and tried kernel 4.6.0-040600rc6-generic and the mouse is still stuck when I start my system.

cosmos-door, in the Fedora bug it seems that the mouse is only stuck in gnome-software, not in general, isn't it?

When entering

sudo mv /etc/xdg/autostart/gnome-software-service.desktop /etc/xdg/autostart/gnome-software-service.desktop.old

and restart the mouse works normally.

2016-05-06 23:20 GMT+09:00 Walter Garcia-Fontes <email address hidden>:
> cosmos-door, in the Fedora bug it seems that the mouse is only stuck in
> gnome-software, not in general, isn't it?

walter-garcia,

Yes. It seems when gnome-software started, mouse will not be work.

A Japanese user reported to ubuntu-jp ML, "I can workaround by
removing gnome-software."
https://lists.ubuntu.com/archives/ubuntu-jp/2016-May/005490.html

Additionaly he said "I reproduced on Ubuntu GNOME, but not on Ubuntu MATE"

cosmos-door and josep, thanks, it seems clear that this is not a kernel bug, so changing the package to gnome-software

I have the same problem. My USB mouse worked fine in ubuntu 14.04, but after doing a clean install of 16.04 it freezes just after login and dmesg is full of "status -75".

[ 1.224340] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 1.356707] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[ 1.356709] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.628335] usb 2-1.1: new low-speed USB device number 3 using ehci-pci
[ 1.725971] usb 2-1.1: New USB device found, idVendor=0e8f, idProduct=0022
[ 1.725974] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.725975] usb 2-1.1: Product: USB KB V11
[ 1.725976] usb 2-1.1: Manufacturer: GASIA
[ 1.796326] usb 2-1.3: new low-speed USB device number 4 using ehci-pci
[ 1.893017] usb 2-1.3: New USB device found, idVendor=15d9, idProduct=0a4c
[ 1.893022] usb 2-1.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.893025] usb 2-1.3: Product: USB OPTICAL MOUSE
[ 313.448227] usb 2-1.3: input irq status -75 received
[ 313.464221] usb 2-1.3: input irq status -75 received
[ 313.472219] usb 2-1.3: input irq status -75 received
[ 313.480219] usb 2-1.3: input irq status -75 received

agustin-rc89, does the workaround mentioned in message #8 work for you?

From the Red Hat bug linked:

Richard Hughes 2016-01-08 04:34:44 EST
Can you try setting EnableOptionROM=false in /etc/fwupd.conf and rebooting please.

@willcooke I just tried EnableOptionROM=false and rebooted. No it made no difference. I still needed to do :
    sudo rmmod usbhid
    sudo modprobe usbhid
and then the mouse worked again. I've reverted back to EnableOptionROM=true.

Just to reiterate in case it helps, the USB mouse works fine after reboot when the login password box appears. But stops working after I log in successfully and the desktop appears.

Hi,
I have the same issue with a fresh Ubuntu 16.04 install.
Comment #8 solved the issue for login. But it freeze again after starting gnome software.

Sysout gnome-software --verbose

errorlog

Just spend 3 days in a music festival where our Loco host an ubuntu webcafé with ~10 PC running the lastest LTS (here 16.04)

that bug happens at 2 key moment:

 * when logging on the (guest) session

 * when launching the software center

Added to Trello: https://trello.com/c/POejPoat/4-bug-1578317-regression-mouse-stuck-at-start-up

Added to Trello: https://trello.com/c/cGhAoPoZ/57-bug-1578317-regression-mouse-stuck-at-start-up

I'm seeing this on a HP laptop after upgrading from 14.04 to 16.04: USB mouse is not working anymore.

From the upstream bug tracker:

 'Richard Hughes 2016-08-15 08:16:19 UTC

This isn't a gnome-software problem; it could be caused by fwupd probing the system at gnome-software startup, but the root problem is a kernel issue IMHO.'

Should the package affected by this bug be changed?

I raised a bug against kernel, I am on Gentoo linux but same issue symptoms.

https://bugzilla.kernel.org/show_bug.cgi?id=193231

Did this stop happening?

The problem still exists. I upgraded to 16.10 and then 17.04 in the hopes
it had been fixed, but it still isn't.

On Fri, May 19, 2017 at 1:43 AM, Iain Lane <email address hidden> wrote:

> Did this stop happening?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1578317
>
> Title:
> Regression: Mouse stuck at start-up
>
> Status in Fwupd:
> New
> Status in GNOME Software:
> Unknown
> Status in gnome-software package in Ubuntu:
> Confirmed
> Status in gnome-software package in Fedora:
> Unknown
>
> Bug description:
> My mouse is stuck at start-up. A workaround is to enter "sudo rmmod
> usbhid; modprobe usbhid" and the mouse starts working.
>
> josep@josep-GJ306AA-ABE-m8175-es:~$ lsusb
> Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card
> Reader/Writer
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 008 Device 005: ID 050d:016a Belkin Components Bluetooth Mini Dongle
> Bus 008 Device 004: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface
> Subclass)
> Bus 008 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface
> Subclass)
> Bus 008 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
> (part of BCM2046 Bluetooth)
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 004: ID 15d9:0a4c Trust International B.V. USB+PS/2
> Optical Mouse
> Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified:
> boot/vmlinuz-4.4.0-21-generic]
> ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
> Uname: Linux 4.4.0-21-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: josep 1664 F.... pulseaudio
> CurrentDesktop: Unity
> Date: Wed May 4 19:08:48 2016
> HibernationDevice: RESUME=UUID=b0bbcadd-00af-44cd-8f5d-eea7fee41c90
> InstallationDate: Installed on 2016-04-28 (6 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
> IwConfig:
> enp0s25 no wireless extensions.
>
> lo no wireless extensions.
>
> enp1s0 no wireless extensions.
> MachineType: HP-Pavilion GJ306AA-ABE m8175.es
> ProcFB: 0 nouveaufb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic
> root=UUID=816f2dbe-34e1-4512-a2b8-565bc86cb28e ro quiet splash
> vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.4.0-21-generic N/A
> linux-backports-modules-4.4.0-21-generic N/A
> linux-firmware 1.157
> RfKill:
> 0: hci0: Bluetooth
> ...

I clean installed Ubuntu 16.04 on a Dell Optiplex 390 and experience the same lack of mouse function after successful login. I attempted the workaround listed at the top of page but received the following error: "modprobe: ERROR: could not insert 'usbhid': operation not permitted.
  I then noticed my keyboard, which had previously worked normally, had stopped working. I unplugged both my keyboard and my mouse and reconnected both in turn and now my mouse and keyboard both work - even after log out and successful login. I am not a Dev, just reporting what I've noticed and wondering when a permanent fix will be available.

The above work-around only worked once. After reboot I can't repeat the success.still no mouse after login. Gonna dump this install, no mouse equals no work.