- This topic is empty.
March 8, 2012 at 5:42 pm #7168
We are trying to utilize a floating graphic wallpaper through the wlx.ini file. In the old wnos.ini we utilized on the V10, we were able to specificy a jpg in the bitmap folder to accomplish this. Is it possible to repeat this same method?
Thanks in advance.
Edit: just so I’m clear, I’m referring to the screensaver that appears at the VMWare View sign in screen if the end user leaves it idle. Obviously we have our own screen saver policy for when the user is in to their VM.March 15, 2012 at 3:19 pm #21933
One more screensaver related message: we have been testing our wlx.ini with Screensaver= 90, 99, 119, 120, etc. All types of different values (we’d prefer 120), and, it seems at PURE RANDOM, the screensaver will work and come on when specified, or, the system will idled after ~10 minutes and put the monitor too sleep. We were recommended to put PowerManager=0,0 in our wlx.ini file, but, that seems to have made little difference.
I had a machine this AM that was going to a black screen saver at 90 minutes, exactly the way I wanted. I did a factory reset on it, changed NOTHING in the INI, and this time after loading the wlx, it idled after 10 minutes. I don’t get it.
Our INI Display section:
Screensaver=120March 15, 2012 at 3:48 pm #21935NENPLParticipant
- Total Post: 18
- Regular Joe
Back in July, I found a bug with my C50LEs, which probably effects all the Enhanced SUSE Linux thin clients. I use some of my C50LEs as displays which autologin and connect to a VMWare View session, then sit idle pretty much indefinitely. What I found is that even if you add the Screensaver=0 to your INI file, the screen will still go black after 10 minutes if there is no interaction with the thin client. Once there is any interaction with it, whether at the terminal or over VNC, the Thin Client screen will not go black again. Wyse Support has been able to reproduce this problem and filed a CIR for this issue. The tech I have dealing with hoped the latest firmware (11.1.053) would address the issue, but it has not.
If this is the problem your having, you may want to contact Wyse about it. There is no solution, but if enough people show its affecting them, maybe it will be higher priority for them to develop a fix.March 15, 2012 at 4:37 pm #21936
It looks like you’re absolutely right, moving the mouse around after it went idle at the View login screen, now seems to have disabled the idlingt. 10 minutes have passed and it hasn’t idled as it did previously. I will definitely share this with my Wyse contact.March 15, 2012 at 7:02 pm #21938
Now that I have some understanding of the idling (and sent it off to my contact), back to the customizing of the actual screen saver. I feel like I have to be missing something in term of configuring a specific graphic for the screensaver. The fading to black is ok I suppose, but, I can definitely see end users thinking the machine is off mistakenly, and restarting the R50.March 16, 2012 at 4:46 pm #21939
Wow another screensaver related issue: when in a session through View, the VM itself has a screensaver pushed via group policy, but then the SUSE screensaver of darkening the screen activates after 90 minutes. Therefore the screensaver we push becomes useless. The SUSE side doesn’t know if View is in use to disable it’s screen saver setting?
This is another setting ThinOS pulled off fine. If we were in session to our VM, thinOS did not activate it’s screen saver.
- You must be logged in to reply to this topic.