https://bugzilla.novell.com/show_bug.cgi?id=482678 Summary: In all Yast Application that we enable to run at a specific time we currently have no way to wake the PC to run the task if it has been suspended. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: alpha096@virginbroadband.com.au QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1 Firefox/3.0.6 I found this very hard to put in the right classification. Increasingly we offer tasks to be run that are configured in Yast - Online Update- Apparmour reports, notifications from events etc etc. What we don't offer it an open to wake the PC from suspend to run the task if the user so desires it - I think its is not of much value to schedule any task or to set any type of notification if the user has no option to wake the PC from suspend Reproducible: Always Steps to Reproduce: 1. Set online update to run in 30 minutes time. 2. Suspend the PC. 3. We have lost our instructions to initiate any schedule by NOT offering a way or option to wake a PC from sleep. Actual Results: If the PC suspends itself is is told to suspend any scheduled task set during that period will never run. Expected Results: This is a problem as we are setting a task but don't provide a way for the task we have set to run if the PC is suspended at the time - This could easily mean that any scheduled task may never run if it is scheduled inside say.......23:00 - 04:00 Hours Dont like my luck with default priority ;-) But I think I have a valid point to leave default Severity and aim for 11.2 implementation. Please correct classification in above - I found it difficult to classify in just one component. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.