USB Mouse not working suddenly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Suddenly after turning on my laptop, the usb mouse stopped working. I tested it on another PC and it worked perfectly.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSign
Uname: Linux 3.13.0-79-generic x86_64
.tmp.unity.
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CompositorUnred
CompositorUnred
CurrentDesktop: Unity
Date: Sat Mar 19 14:33:53 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
ExtraDebuggingI
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0388]
InstallationDate: Installed on 2013-10-29 (872 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Lsusb:
Bus 002 Device 003: ID 04f2:b23d Chicony Electronics Co., Ltd
Bus 002 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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer Aspire 7551
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
dmi.bios.date: 04/25/2011
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.18
dmi.board.
dmi.board.name: Aspire 7551
dmi.board.vendor: Acer
dmi.board.version: V1.18
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Aspire 7551
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Sat Mar 19 14:28:53 2016
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.
Eduardo Brito, thank you for reporting this and helping make Ubuntu better.
In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http:// kernel. ubuntu. com/~kernel- ppa/mainline/ ?C=N;O= D ? Please keep in mind the following: /wiki.ubuntu. com/Kernel/ MainlineBuilds .
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https:/
If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.
If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: fixed-upstream fixed-upstream- X.Y-rcZ
kernel-
kernel-
Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.
If the mainline kernel does not fix the issue, please add the following tags: bug-exists- upstream bug-exists- upstream- X.Y-rcZ
kernel-
kernel-
Please note, an error to install the kernel does not fit the criteria of kernel- bug-exists- upstream.
Also, you don't need to apport-collect further unless specifically requested to do so.
Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.
Thank you for your understanding.