Bug 105780 - Machine left idle, then its unusable
Summary: Machine left idle, then its unusable
Status: RESOLVED DUPLICATE of bug 105787
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Beta 2
Hardware: i386 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-19 09:19 UTC by A Nagappan
Modified: 2005-09-14 00:42 UTC (History)
1 user (show)

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
My PC hardware info (181.63 KB, text/plain)
2005-08-19 09:21 UTC, A Nagappan 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description A Nagappan 2005-08-19 09:19:46 UTC 
Installed only default GNOME
When the machine is left idle, I can recover for the first time, by restarting
xdm. So all the applications running will be quit. For this I need to do Ctrl +
Alt + F1 and do a restart. If I try Alt + F7 once from text mode (when the X is
in hung state), only way to recover is reboot the machine.

Additional info:
If I kill gnome-screensaver immediately after login to my gnome-session, my
screen doesnot goto idle state and I tried running one whole day. Things are
running fine and no issue.

Please let me know what all further info do you need ? Let me try to provide.
Let me also attach my PC hardware info. Could this be because of my installation
and X running steps (Bug #105769)?
Comment 1 A Nagappan 2005-08-19 09:21:02 UTC 
Created attachment 46658 [details]
My PC hardware info
Comment 2 Stanislav Brabec 2005-08-19 09:44:28 UTC 
I have experienced in older betas something similar - it was because both
xscreensaver and gnome-screensaver were running. I am not sure, whether this can
be the same case.
Comment 3 Stanislav Brabec 2005-08-19 11:10:12 UTC 
Later bug already contains discussion.

*** This bug has been marked as a duplicate of 105787 ***
Comment 4 JP Rosevear 2005-09-14 00:42:53 UTC 
*** Bug 105787 has been marked as a duplicate of this bug. ***