Bug 6071 - Usb disappear after suspend
Summary: Usb disappear after suspend
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-24 20:03 CEST by Claude Abraham
Modified: 2013-11-01 18:22 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments
lspcidrake.txt (4.05 KB, text/plain)
2012-05-29 13:52 CEST, Claude Abraham
Details
dmesg.txt (5.58 KB, text/plain)
2012-05-29 13:53 CEST, Claude Abraham
Details

Description Claude Abraham 2012-05-24 20:03:05 CEST
Description of problem:

After awaking no more usb and an another suspend impossible.

Version-Release number of selected component (if applicable):
Megeia 2

Laptop Acer Timeline X 3820TG

How reproducible:
Every time

Steps to Reproduce:
1.Boot machine into KDE
2.Suspend machine by closing lid (laptop) or through battery monitor
3.After awaking- no more usb (mouse, usb key etc.)
Comment 1 Manuel Hiebel 2012-05-28 10:46:19 CEST
what is the output of lspcidrake -v ?
Comment 2 Claude Abraham 2012-05-29 13:52:14 CEST
Created attachment 2398 [details]
lspcidrake.txt
Comment 3 Claude Abraham 2012-05-29 13:53:59 CEST
Created attachment 2400 [details]
dmesg.txt
Comment 4 Claude Abraham 2012-05-31 22:27:14 CEST
I have a partial solution.
Boot on Windows, (Fn-F3) put Bluetooth OFF.
Reboot in Mageia 2.
Suspend et wake-up are OK. but no more Bluetooth.
Comment 5 Manuel Hiebel 2013-10-22 12:09:10 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 6 Claude Abraham 2013-10-25 12:51:32 CEST
(In reply to Manuel Hiebel from comment #5)
> This message is a reminder that Mageia 2 is nearing its end of life.
> Approximately one month from now Mageia will stop maintaining and issuing
> updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL)
> if it remains open with a Mageia 'version' of '2'.
> 
> 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 Mageia version prior to Mageia 2's end of life.
> 
> Bug Reporter: Thank you for reporting this issue and we are sorry that we
> may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change
> it against that version of Mageia.
> 
> 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 Mageia release includes newer upstream software that fixes bugs or
> makes them obsolete.
> 
> -- 
> The Mageia Bugsquad

All is OK. with Mageia 3.
Comment 7 Manuel Hiebel 2013-11-01 18:22:42 CET
Ok, closing it now then.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.