UbuntuThis forum is for the discussion of Ubuntu Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I usually leave my computer on 24 hrs a day. Lots of times I'll leave it on with Firefox open connected to the net. Recently I have noticed usually over nite or getting back from work when I go to my computer I'm greeted with the login screen. And when I restart Firefox it gives me the dialog box to restore my previous session because it closed unexpectedly.
I figure If I'm greeted with the login screen either it rebooted or just logged out suddenly. This usually happens overnite and at least once a day sometimes twice.
is merely the syslogd service restarting not my computer.
Now why I'm receiving these messages when I'm not using the computer:
"Apr 1 14:55:39 newbie-desktop gconfd (newbie-29525): Received signal 15, shutting down cleanly
Apr 1 14:55:43 newbie-desktop gconfd (newbie-29525): Exiting"
And what is killing the gdm daemon randomly I suspect may have to do with the gnome-screensaver. Several posts on ubuntuforums have said not using "random" for the screensaver or using the option "blank" have stopped the random gdm crashes. I'm going to try some of these options overnight and see what happens.
Well I have had the gnome-screensaver set to "blank" and not random. And I haven't been greeted by the login screen. I'm going to set my gnome-screensaver to something else and see the results. But something about the screensaver running for a long time is killing my gnome sessions. Maybe it's memory issue. I have a old ATI integrated video card with only 4 MB's of ram. Maybe be X is killing for that?
It's not my computer rebooting I figured that out. It's the fact that if I leave my gnome-screensaver on over nite on "random"(haven't tested other screensaver options yet) gdm is killed and I'm left at the login display.
I'm just wondering if it could be the one particular screensaver from the "random" option is consuming too much cpu resources or memory and it's forcing X to kill gdm and thus logging off.
I haven't really found a reason for this in the ubuntuforums yet.
I have the same symptom as nick623. I'm running Fedora Core 6, automatically updated overnight via yum. I leave this box on all the time. Lately I've come in in the morning to find the one and only user i log on as, logged off. The value of "uptime" is 14 days, so it's certainly not the case that there's been a power outage or my computer has rebooted.
In all the cases I've investigated, these few lines appear in /var/log/messages:
gconfd (rbh00-10121): Received signal 15, shutting down cleanly
--- followed 30s later by
gconfd (rbh00-12474): GConf server is not in use, shutting down.
I note that xscreensaver was updated Apr 23 to version "1:5.02-1.fc6"; it feels right to say that this symptom started at about that time. I've seen others here mention that this might be due to xscreensaver problems. I'd had "Advanced" screensaver settings set to uncheck "Power Management Enabled" but a few days ago checked it, and set "Off After" to 0 minutes. This seemed to ameliorate the problem, which before that seemed to be happening every morning; but it still happens maybe 50% of mornings. Standby After is set to 120min, Suspend After is set to 0 min.
I may decide to backlevel my xscreensaver, just to see what happens.