After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome

Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031

Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078

Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

changing background wallpaper remotely hangs winvnc?

Post Reply
ruamdro
8
8
Posts: 9
Joined: 2010-08-06 11:37

changing background wallpaper remotely hangs winvnc?

Post by ruamdro »

Hello

i have "bginfo" (systinternal) run every time i log on for the first time.
A window pops up where i could say which parameters should be displayed as wallpaper.
Too there i a point to enable the background wallpaper.
If i do that remotely, the winvnc immediately hangs.
The mouse freezes if dealt with by server. There is no refresh anymore On the local screen of the server there the mouse can be moved etc..
I still can "connect" to the server. Say client is waiting for protocol nego, but nothing happens.
I can do net stop ultrasrv, net start ultrasrv, but no success:
No remote access.
If i kill in taskmanager the winvnc process and restart the vnc server, all is well again.
Bug or feature?

i have tested that without mirror driver and with.
It's cmpletely reproducibe. but i don't really think that's a feature.

Is a a bug?
Why?

(Workarround: don't finger at the wallpaper remotely)
Post Reply