[Bug 269974] Re: suspend via Fn+F1 or lid-close behave differently

2009-11-18 Thread Yung-Chin Oei
I updated the description: the previous description conflated lots of
different issues.

(also, better late than never I guess: thanks Andres!)

** Description changed:

- I just installed Ubuntu 8.04.1 with the amd64 alternate installer on a
- Dell Latitude D630. It's an all-Intel version, ie X3100 graphics and
- iwl3945 Wifi. All the latest updates have been installed.
+ Hardware: Dell Latitude D630, with X3100 graphics and iwl3945 Wifi.
  
- Funny behaviour: when I close the lid, it smoothly goes into suspend,
- and on opening the lid comes back again (great!). However, when instead
- I hit Fn+F1, it takes much longer to go into suspend, then actually
- seems to power down the hardware: no more blinking suspend light. So it
- seems to call different scripts for these two cases! I checked in System
- - Preferences - Power Management, and both for laptop lid is closed
- and suspend button is pressed the setting is suspend.
+ Odd behaviour: when pressing the suspend button (Fn+F1), the system
+ hibernates, despite it being configured to suspend. On lid-close, it
+ does however properly suspend as expected. I checked in System -
+ Preferences - Power Management, and both for laptop lid is closed and
+ suspend button is pressed the setting is suspend.
  
- Further info: when I try to restart the machine after the Fn+F1 way of
- suspending, it cold-boots and shows grub, then refuses to mount the swap
- partition - saying that this contains a valid suspend image. But it
- doesn't use that image, and instead continues booting, only without the
- swap space. I can then reenable the swap later using swapon - this
- reinitialises the swap space.
+ Expected behaviour: the system ought to suspend instead of hibernate, as
+ specified in Preferences.
  
- It's not important to me as I can get all the functionality I need
- through lid-close, but I'd be happy and curious to investigate if you
- can tell me where to look. Thanks.
- 
- (There's also a second but probably unrelated issue - sometimes keyboard
- and touchpad are not detected after resuming from lid-close. This can be
- remedied by closing the lid again, sending the machine back into
- suspend, then opening it once more. Not easy to replicate though and as
- I said probably unrelated).
+ The same behaviour previously with Ubuntu 8.04, and now on 9.10.

** Description changed:

  Hardware: Dell Latitude D630, with X3100 graphics and iwl3945 Wifi.
  
  Odd behaviour: when pressing the suspend button (Fn+F1), the system
  hibernates, despite it being configured to suspend. On lid-close, it
  does however properly suspend as expected. I checked in System -
  Preferences - Power Management, and both for laptop lid is closed and
  suspend button is pressed the setting is suspend.
  
  Expected behaviour: the system ought to suspend instead of hibernate, as
  specified in Preferences.
  
- The same behaviour previously with Ubuntu 8.04, and now on 9.10.
+ The same odd behaviour previously with Ubuntu 8.04, and the same on
+ 9.10.

-- 
suspend via Fn+F1 or lid-close behave differently
https://bugs.launchpad.net/bugs/269974
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 269974] Re: suspend via Fn+F1 or lid-close behave differently

2009-01-12 Thread Andres Mujica
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. This bug did not have a package associated with it, which is important 
for ensuring that it gets looked at by the proper developers. You can learn 
more about finding the right package at 
https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a 
bug in ACPI-SUPPORT.
For future reference you might be interested to know that a lot of applications 
have bug reporting functionality built in to them. This can be accessed via the 
Report a Problem option in the Help menu for the application with which you are 
having an issue. You can learn more about this feature at 
https://wiki.ubuntu.com/ReportingBugs.

** Changed in: acpi-support (Ubuntu)
Sourcepackagename: None = acpi-support

-- 
suspend via Fn+F1 or lid-close behave differently
https://bugs.launchpad.net/bugs/269974
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 269974] Re: suspend via Fn+F1 or lid-close behave differently

2008-10-03 Thread Yung-Chin Oei
Further info, update: I get the same behaviour as I get with Fn+F1 when
I choose hibernate from the quit-menu, so I guess that that's related.

I believe the problem with resuming from hibernation is that the disk
volume layout on my system, which consists of an LVM partition with
several separately encrypted logical volumes, is something the resume-
scripts weren't designed to deal with, so that's actually a separate bug
(how do I deal with that? I'm relatively new to bug reporting).

-- 
suspend via Fn+F1 or lid-close behave differently
https://bugs.launchpad.net/bugs/269974
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs