Regression: Mouse stuck at start-up

Bug #1578317 reported by josep
110
This bug affects 24 people
Affects Status Importance Assigned to Milestone
Fwupd
New
Undecided
Unassigned
GNOME Software
Unknown
Medium
gnome-software (Fedora)
Won't Fix
Medium
gnome-software (Ubuntu)
Confirmed
High
Unassigned

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
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.05
dmi.board.name: Berkeley
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd07/11/2007:svnHP-Pavilion:pnGJ306AA-ABEm8175.es:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: GJ306AA-ABE m8175.es
dmi.sys.vendor: HP-Pavilion

Revision history for this message
In , Asif (asif-redhat-bugs) wrote :

Description of problem:
Mouse does not work on the launch of gnome-software

Version-Release number of selected component (if applicable):
fedora 23 workstation

How reproducible:
always

Expected results:
fedora 22 did not have this problem

Additional info:
the mouse becomes unusable unless we restart fedora 23 workstation.

dmesg shows:

[ 1786.xxxxxx ] usb 6-4: input irq status -75 received
[ 1786.xxxxxx ] usb 6-4: input irq status -75 received
[ 1786.xxxxxx ] usb 6-4: input irq status -75 received
[ 1786.xxxxxx ] usb 6-4: input irq status -75 received
[ 1786.xxxxxx ] usb 6-4: input irq status -75 received
[ 1786.539254 ] usb 6-4: input irq status -75 received

the xxxxxx are numbers.

Revision history for this message
In , Kalev (kalev-redhat-bugs) wrote :

Could be fwupd poking the hardware in a wrong way

Revision history for this message
In , Richard (richard-redhat-bugs) wrote :

Can you try setting EnableOptionROM=false in /etc/fwupd.conf and rebooting please.

Revision history for this message
In , Richard (richard-redhat-bugs) wrote :

*** Bug 1295465 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Andrew (andrew-redhat-bugs) wrote :

I had the same issue and not sure what EnableOptionROM=false in /etc/fwupd.conf did as I am not a developer but this suggestion fixed the issue for me.

Revision history for this message
josep (josep-ubuntu) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Mouse stuck at start-up

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
status: Confirmed → Incomplete
Revision history for this message
josep (josep-ubuntu) wrote : Re: [Bug 1578317] Re: Mouse stuck at start-up
Download full text (4.6 KiB)

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...

Read more...

summary: - Mouse stuck at start-up
+ Regression: Mouse stuck at start-up
tags: added: regression-release
Revision history for this message
Mitsuya Shibata (cosmos-door) wrote :

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?

Revision history for this message
josep (josep-ubuntu) wrote :

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

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

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

tags: added: kernel-bug-exists-upstream
removed: kernel-fixed-upstream
Revision history for this message
josep (josep-ubuntu) wrote :

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.

Revision history for this message
Mitsuya Shibata (cosmos-door) wrote : Re: [Bug 1578317] Re: Regression: Mouse stuck at start-up

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"

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

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

affects: linux (Ubuntu) → gnome-software (Ubuntu)
tags: removed: kernel-bug-exists-upstream
Changed in gnome-software:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Agustin Baez (agustin-rc89) wrote :

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

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

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

Revision history for this message
Will Cooke (willcooke) wrote :

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.

Revision history for this message
mdo (mdowle) wrote :

@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.

Revision history for this message
Tr4sK (tr4sk) wrote :

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.

Revision history for this message
Tr4sK (tr4sk) wrote :

Sysout gnome-software --verbose

Revision history for this message
Tr4sK (tr4sk) wrote :

errorlog

Revision history for this message
cm-t 🦄🏂🌈🎵 (cm-t) wrote :

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

Revision history for this message
In , Will (will-redhat-bugs) wrote :

A few people have tried setting the EnableOptionROM=false and rebooting in Ubuntu (bug here: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1578317) and reports are that it didn't help.

Will Cooke (willcooke)
tags: added: desktop-trello-import
Revision history for this message
Will Cooke (willcooke) wrote : Automatically added comment
tags: removed: desktop-trello-import
Revision history for this message
In , Oleg (oleg-redhat-bugs) wrote :

Iwonder if the root cause here is fwupd hogging file descriptor to the usb device via usbfs and thus interfering with the driver operations (bug 1340587)?
Possibly just stopping fwupd (killall fwupd) might be all that's needed here?

Will Cooke (willcooke)
tags: added: desktop-trello-import
Revision history for this message
Will Cooke (willcooke) wrote :
tags: removed: desktop-trello-import
Revision history for this message
In , Asif (asif-redhat-bugs) wrote :

EnableOptionROM=false in /etc/fwupd.conf does not do anything on fedora 23, and fedora 24.

Also in fedora 24 workstation, as soon as I login, gnome-software starts as a service, which hangs the mouse. I had to remove gnome-software to use the mouse for work in fedora 24.

Also in ubuntu 16.04 64bit, starting gnome-software hangs the mouse.

Revision history for this message
In , Noel (noel-redhat-bugs) wrote :

*** Bug 1286396 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Noel (noel-redhat-bugs) wrote :

On my Fedora 24 box, I had to uninstall the gnome-software package to prevent it from starting. Removing the desktop file from /etc/xdg/autostart didn't do it. Somehow it was still getting started each time I logged in.

The problem has not re-appeared since uninstalling gnome-software.

Changed in gnome-software:
status: Confirmed → Unknown
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Jeremy Bícha (jbicha)
Changed in gnome-software (Ubuntu):
importance: Medium → High
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
TomaszChmielewski (mangoo-wpkg) wrote :

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

Revision history for this message
Ads20000 (ads20000) wrote :

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?

Revision history for this message
archenroot (archenroot-gmail) wrote :

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

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

Revision history for this message
Iain Lane (laney) wrote :

Did this stop happening?

Revision history for this message
mdo (mdowle) wrote : Re: [Bug 1578317] Re: Regression: Mouse stuck at start-up
Download full text (4.0 KiB)

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
> ...

Read more...

Changed in gnome-software (Fedora):
importance: Unknown → Medium
status: Unknown → Won't Fix
Revision history for this message
Shannon O (smash591) wrote :

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.

Revision history for this message
Shannon O (smash591) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.