Ubuntu

Computer suspends after mounting Kingston

Bug #129337 reported by Piotr Bukowczyk
8
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

My computer suspends after I mount pen drive (Kingston USB 2.0). I have "Feisty Fawn" installed and Intel Celeron Processor. BIOS is about 8 years old. I solve this problem by resetting (restarting) the computer with my pen drive installed. After that operation it works fine and I can read information from Kingston or demount and safely remove it.

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

Revision history for this message
Adam Niedling (krychek) wrote :

This bug sound very unrealistic. Is it still occurring in Hardy?

Revision history for this message
Piotr Bukowczyk (piotr-bukowczyk) wrote : Re: [Bug 129337] Re: Computer suspends after mounting Kingston
  • unnamed Edit (135 bytes, text/html; charset=ISO-8859-1)

Yes, it does. However, my computer doesn't suspend if I mount Kingston
before switching on the machine.

Piotr Bukowczyk

Revision history for this message
Piotr Bukowczyk (piotr-bukowczyk) wrote :
  • unnamed Edit (59 bytes, text/html; charset=ISO-8859-1)

I have mistaken. I still have "Feisty Fawn".

Revision history for this message
Adam Niedling (krychek) wrote :

Wouldn't you wanna upgrade? Or just try a Live CD.

Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Connor Imes (ckimes) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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

Other bug subscribers

Remote bug watches

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