After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 502072 - SuspendCommand is not executed
SuspendCommand is not executed
Status: RESOLVED DUPLICATE of bug 500362
Product: gdm
Classification: Core
Component: general
2.20.x
Other All
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-06 15:00 UTC by Pacho Ramos
Modified: 2007-12-07 19:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20

Attachments
custom.conf (3.54 KB, text/plain)
2007-12-06 15:01 UTC, Pacho Ramos 		Details

Description Pacho Ramos 2007-12-06 15:00:43 UTC 
Please describe the problem:
I have tried to configure SuspendCommand from gdmsetup, the following line is added to /etc/X11/gdm/custom.conf:

SuspendCommand=/usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux

/usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux is the script that I use under my system for suspend, it works fine except from gdm-2.20* (it worked in gdm-2.18.4

I get the following error in /var/log/messages:

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

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Pacho Ramos 2007-12-06 15:01:38 UTC 
Created attachment 100391 [details]
custom.conf

This is my gdm custom.conf file generated with gdmsetup
Comment 2 Brian Cameron 2007-12-06 19:32:29 UTC 

*** This bug has been marked as a duplicate of 501010 ***
Comment 3 Pacho Ramos 2007-12-06 19:42:42 UTC 
Are you sure that this is the same bug? :-/
Comment 4 Brian Cameron 2007-12-06 19:58:09 UTC 
I think so, the problem in the other bug is that the value was being read in as an integer rather than a string, which seems to be the same problem here.  Can you try applying the patch in bug 501010 and let me know if there is still any problems?
Comment 5 Brian Cameron 2007-12-06 19:59:27 UTC 
Oops you are right.  The right bug is bug #500362.
Comment 6 Brian Cameron 2007-12-06 19:59:53 UTC 

*** This bug has been marked as a duplicate of 500362 ***
Comment 7 Pacho Ramos 2007-12-06 21:29:38 UTC 
Yes, this is fixed with 500362 patch

Thanks a lot :-D
Comment 8 Brian Cameron 2007-12-06 21:34:52 UTC 
Would you mind checking if 502074 is also fixed with this patch?
Comment 9 Pacho Ramos 2007-12-07 19:41:48 UTC 
I have tried but 502074 problem persists :-(