usb mouse will not start again after wakeup from sleeping modus

Bug #1586622 reported by Manfredo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

also sometimes it is not possible to enter my password in below my name in the startup window after wakeup from sleeping modus (close and reopen my laptop)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ma 1886 F.... pulseaudio
 /dev/snd/controlC0: ma 1886 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat May 28 12:01:18 2016
EcryptfsInUse: Yes
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=ddc5f05c-ee77-4134-bf3e-7d8c14d9df0b
HotplugNewDevices:

HotplugNewMounts:

InstallationDate: Installed on 2016-05-27 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: MEDION AKOYA E1318T
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=82346f7c-9fb1-437b-b3d3-0451e6f1739b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 12:01:38.659: The udisks-daemon is running (name-owner :1.95).
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 601
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: AKOYA E1318T
dmi.board.vendor: MEDION
dmi.board.version: 1.0
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: MEDION
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnInsydeCorp.:bvr601:bd10/24/2013:svnMEDION:pnAKOYAE1318T:pvr1.0:rvnMEDION:rnAKOYAE1318T:rvr1.0:cvnMEDION:ct10:cvr1.0:
dmi.product.name: AKOYA E1318T
dmi.product.version: 1.0
dmi.sys.vendor: MEDION

Revision history for this message
Manfredo (m-v1) wrote :
Revision history for this message
Manfredo (m-v1) wrote :

Thks !
you make avery GOOD JOB !!!

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
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
penalvch (penalvch) wrote :

Manfredo, 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:
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://wiki.ubuntu.com/Kernel/MainlineBuilds .

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:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

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:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

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.

Changed in linux (Ubuntu):
importance: High → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.