gdm error messages

Steve zephod at cfl.rr.com
Fri Nov 7 18:45:29 UTC 2008


I posted this a few days ago but haven't had any takers. Do I have to subscribe to another, gdm, list?

Now I find that if I let the screensaver and then power management kick in, when I try to wake the computer up again, I get a very brief text screen that says something about starting the disks but it's too quick to read, and then nothing. I can't Ctrl-Alt-F1 and my only option is to reboot via the power switch.

The pm-suspend.log shows that the computer did wake up OK.

Fri Nov  7 12:31:28 EST 2008: performing suspend
Fri Nov  7 13:23:49 EST 2008: Awake.
Fri Nov  7 13:23:49 EST 2008: Running hooks for resume
/usr/lib64/pm-utils/sleep.d/99video resume: success.
/usr/lib64/pm-utils/sleep.d/99hd-apm-restore.hook resume: success.
/usr/lib64/pm-utils/sleep.d/95packagekit resume: method return sender=:1.106 -> dest=:1.105 reply_serial=2
success.
/usr/lib64/pm-utils/sleep.d/95led resume: not applicable.
/usr/lib64/pm-utils/sleep.d/94cpufreq resume: success.
/usr/lib64/pm-utils/sleep.d/90clock resume: success.
/usr/lib64/pm-utils/sleep.d/65alsa resume: success.
/usr/lib64/pm-utils/sleep.d/55battery resume: success.
/usr/lib64/pm-utils/sleep.d/50modules resume: success.
/usr/lib64/pm-utils/sleep.d/49bluetooth resume: not applicable.
/usr/lib64/pm-utils/sleep.d/10NetworkManager resume: success.
/usr/lib64/pm-utils/sleep.d/05led resume: not applicable.
/usr/lib64/pm-utils/sleep.d/01grub resume: not applicable.
/usr/lib64/pm-utils/sleep.d/00clear resume: success.
Fri Nov  7 13:23:51 EST 2008: Finished.

Any suggestions?
Thanks,
Steve.


---- Steve <zephod at cfl.rr.com> wrote: 
> I was looking through /var/log/messages and I came accross this error :
> 
> gconfd (gdm-2770): Error setting value for `/apps/gnome-screensaver/power_management_delay': Can't overwrite existing read-only value: Value for `/apps/gnome-screensaver/power_management_delay' set in a read-only source at the front of your configuration path
> 
> My home directory has no read, write or execute permissions for anybody besides me so the error message is no that suprising.
> 
> After a bit of googling I found a suggested solution of setting umask to 027 in /etc/init.d/functions but that interfered with loggng in resulting in no taskbar.
> 
> I decided to try adding my user group to gdm's group list and changing the permissions in my home directory structure to allow anyone in my group to read, write or execute. I was suprised to find that this did not work. Is this because gdm doesn't have a login shell? I tried adding my group to a different user, logging on as that user and then writing to the gnome-screensaver directory and had no problems.
> 
> How else can I get this to work?
> 
> This is on a fully up-to-date F8 system.
> 
> Thanks,
> Steve




More information about the fedora-list mailing list