[gutsy] Suspend does not work from GDM login screen

Bug #132939 reported by Anthony DeStefano
28
Affects Status Importance Assigned to Milestone
gdm
Fix Released
Medium
gdm (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gdm

On an IBM Thinkpad T23 suspend does not work when at the GDM login screen. I have tried three different ways:

1. Closing the lib
2. Pressing the suspend key ont he keybord (Fn+F3)
3. Selecting Suspend from the Options menu.

Suspend and hibernate work after a user has logged in.

Related branches

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. What happens when you click on the item? does running "sudo pmi action sleep" works correctly?

Changed in gdm:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Anthony DeStefano (ajd-tasteslikeburning) wrote :

When I click on suspend in the gdm menu I get a pop-up with the message "Are you sure you want to suspend the computer?" After clicking OK nothing happens.

"sudo pmi action sleep" suspends the computer just fine from both the console and an xterm.

Changed in gdm:
status: Incomplete → New
Revision history for this message
Will (tcosprojects) wrote :

I can confirm this. Nothing happens when clicking suspend from GDM. However, if I am already logged in I can suspend from within GNOME.

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

I can confirm this. I guess this is a design bug, not specific to any configuration.

Revision history for this message
Mal (mal-gamble) wrote :

I have the same problem with 2 different desktop computers. The following error message appears in /var/log/syslog after an unsuccessful attempt to suspend from the gdm login screen:

"... gdm[6792]: WARNING: Request for configuration key daemon/SuspendCommand=, but not type STRING"

The SuspendCommand setting in /etc/gdm/gdm.conf looks OK to me.

The Shutdown option on the gdm login screen works fine.

Changed in gdm:
status: New → Confirmed
Revision history for this message
Stas Boukarev (stassats) wrote :

I have fixed this with the following patch

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Stas, thanks for the patch. Can you check if this patch is still needed in the Hardy version? In this case, maybe you could make a debdiff? It would also be good if you can check if it's fixed upstream in Gnome, because then we'd know it will be fixed in Hardy anyway.

Revision history for this message
Stas Boukarev (stassats) wrote :

Yes, it is needed for hardy's gdm. Source code of development version of gdm was changed so deeply, I can't find corresponding code.

Revision history for this message
Peter Meiser (meiser79) wrote :

Hi,

here is the commit to the GNOME SVN:

http://svn.gnome.org/viewvc/gdm?view=revision&revision=5532

Best regards,
Whoopie

Changed in gdm:
status: Confirmed → Fix Committed
Changed in gdm:
status: Unknown → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gdm - 2.20.3-0ubuntu1

---------------
gdm (2.20.3-0ubuntu1) hardy; urgency=low

  * New upstream version:
    - Now "Esc" key acts like the "Start Again" button in the greeter program.
    - Fix regression in GDM 2.20 that caused the daemon to not read
      any [server-foo] sections that were not referenced in the
      [servers] section of the configuration file. This caused
      problems for gdmsetup when you tried to edit the Xserver configuration.
    - Fix regression in GDM 2.20 that caused HaltCommand,
      SuspendCommand, and RebootCommand to not get updated properly
      when modified from gdmsetup. (LP: #132939)
    - Fix gdmsetup so that it doesn't use gtk_init when run with
      the "--command" option. This allows the gdmflexiserver --command
      option to be run with setuid/setgid without problems. (LP: #132833)
    - Fix counting of open XDMCP sessions. In some situations this
      problem would cause GDM to think the maximum number of XDMCP
      sessions had been started when this wasn't the case. (LP: #152068)
    - Fix Suspend configuration option so it works.
    - Fix so that XDMCP Willing configuration option works.
    - Fixes to avoid compiler warnings.
    - Fix gdmsetup so it does not crash if it cannot read any
      displays from the configuration file.
  * debian/patches/10_noxkeepcrashing.patch,
    debian/patches/70_mandatory-relibtoolize.patch:
    - updated
  * debian/patches/90_workaround_init_color.patch:
    - removed, the issue is fixed in the new version

 -- Sebastien Bacher <email address hidden> Wed, 09 Jan 2008 18:41:35 +0100

Changed in gdm:
status: Fix Committed → Fix Released
Revision history for this message
Xiaoyang Yu (xiaoyang-yu) wrote :

This bug is occurred in Hardy Alpha-3 i386 version, which uses gdm 2.20.2-1ubuntu. Why Hardy use such an older gdm version?

Changed in gdm:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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