http://bugzilla.novell.com/show_bug.cgi?id=562086 http://bugzilla.novell.com/show_bug.cgi?id=562086#c0 Summary: Computer froze with black screen and message "Constructing molecules..." Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: Ulrich.Windl@rz.uni-regensburg.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091017 SUSE/2.0.0-1.1.3 SeaMonkey/2.0 The computer was not powered down over night. When returning to the computer, the screen was black with only "Constructing molecules..." on the upper left (gnome screensaver, I guess). Moving the Mouse or pressing keys did not show any response. Likewise unplugging/replugging the USB for mouse and keyboard did not help. Also pressing the ACPI power button shortly did not shutdown the system. I had to press the power button long to power-off the hard way. Inspecting /var/log/messages after reboot, I found the USB unplug/replug events, and no unusual events (Which seems strange). Digging further into it, I found out that the system did (at least try to) suspend automatically: Dec 9 15:04:28 mypc pm-suspend[9253]: Entering suspend. In case of problems, please check /var/log/pm-suspend.log Dec 9 15:19:48 mypc smartd[3130]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 181 to 187 Dec 9 15:29:48 mypc rsyslogd: -- MARK -- Dec 9 15:49:48 mypc rsyslogd: -- MARK -- So I guess suspend failed, and left the system in some bad state. Reproducible: Didn't try Steps to Reproduce: 1. Leave your PC alone over night Actual Results: In the morning your PC refuses to work with you Expected Results: The PC should be happy to see me again Probably the problem is a power-save problem actually. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.