Bug 609652 - Suspend requires password
Summary: Suspend requires password
Alias: None
Product: Fedora
Classification: Fedora
Component: upower
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-30 18:47 UTC by Brad S
Modified: 2011-06-01 18:57 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2011-06-01 18:57:32 UTC

Attachments (Terms of Use)

Description Brad S 2010-06-30 18:47:24 UTC
Description of problem:
When I attempt to suspend my laptop (dell e4300) by shutting the lid, it doesn't always work.  In particular, it is unhappy after the laptop has been attached to my dock with 2 external hdds and external monitor.  But I tried shutting the lid while the external monitor was attached, and learned that what really happens is it is displaying the lock screen password prompt.  After I entered my password (with a wireless keyboard), the machine suspended.  This was not a problem whien I initially installed FC13, but after some level of updating it has occured.

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

How reproducible:
Every time while on dock.  Usually works once when laptop is standalone.  But not twice in a row.

Steps to Reproduce:
1. Place laptop on dock
2.  Close lid.
Actual results:
Password prompt is displayed

Expected results:
Suspend to memory.

Additional info:
Lots of junk in /var/log/messages about DELL WMI stuff.
Jun 30 14:29:50 lap0081157 kernel: Code: 28 01 00 00 48 8b b8 c0 20 00 00 48 83 c7 48 e8 8f 4b db e0 44 3b 65 cc 7e 15 44 89 e6 48 c7 c7 35 c8 6a a0 31 c0 e8 50 3a db e0 <0f> 0b eb fe 48 83 c4 38 31 c0 5b 41 5c 41 5d 41 5e 41 5f c9 c3
Jun 30 14:29:50 lap0081157 kernel: RIP  [<ffffffffa067532f>] write_all_supers+0x227/0x23c [btrfs]
Jun 30 14:29:50 lap0081157 kernel: RSP <ffff880103a2fca8>
Jun 30 14:29:50 lap0081157 kernel: ---[ end trace ffce3aadbe6e0f74 ]---
Jun 30 14:29:50 lap0081157 kernel: usb 1-4: USB disconnect, address 4
Jun 30 14:29:50 lap0081157 kernel: usb 1-4.1: USB disconnect, address 8
Jun 30 14:29:50 lap0081157 kernel: usb 1-4.1.1: USB disconnect, address 9
Jun 30 14:29:50 lap0081157 kernel: usb 1- USB disconnect, address 11
Jun 30 14:29:50 lap0081157 kernel: usb 1-4.1.2: USB disconnect, address 10
Jun 30 14:29:50 lap0081157 kernel: drivers/hid/usbhid/hid-core.c: can't reset device, 0000:00:1a.7-4.1.2/input0, status -108
Jun 30 14:29:50 lap0081157 kernel: usb 1-4.1: clear tt 1 (00a0) error -19
Jun 30 14:29:52 lap0081157 kernel: dell-wmi: Received unknown WMI event (0x11)

Is this related to btrfs?  I know suspend breaks when I have an sdcard stuck in the laptop sdslot.

Comment 1 Bug Zapper 2011-06-01 15:08:48 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13'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 Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 2 Brad S 2011-06-01 18:57:32 UTC
Close it.  This is not an issue for me any longer.

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