1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking Benchmarking Platform
Phoromatic Test Orchestration

A Screensaver Interface Comes To Wayland

Wayland

Published on 22 November 2011 10:29 AM EST
Written by Michael Larabel in Wayland
22 Comments

For those wishing to follow the development of Wayland Display Server, there's some new progress to report on. This time it's about supporting screensavers under Wayland.

Pekka Paalanen has proposed a screensaver interface for Wayland, which includes adding the interface to the protocol file, compositor stubs, and other changes.

Details and the patch for Wayland screensaver can be found in this mailing list message. Below is also a description of the work. Pardon for the terse posting due to needing to go meet-up with Egbert Eich of SUSE/RadeonHD, Martin Gräßlin of KDE/KWin, and other Linux stakeholders.
Add the screensaver interface to the desktop-shell protocol file. Also add stubs for it in the compositor, and make wscreensaver to bind to the screensaver interface. Wscreensaver gets a new option --demo to retain the current behaviour as a regular wayland client.

When a screensaver application starts, it should bind to the screensaver interface, enumerate all outputs, create a surface per output, and register those surfaces via screensaver::set_surface request. Then it continues with the usual animation loop, waiting for frame events. The compositor will decide, when the given screensaver surfaces are displayed. A screensaver application should respond to outputs coming and going away by creating and destroying surfaces.

The compositor is supposed to activate a screensaver by exec'ing it, and stop the screensaver by killing the client process. Only one client may be bound to the screensaver interface at a time. If there already is a client, the compositor could either kill it first, or not exec a new one.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux News
  1. Phoronix Turns 11 Years Old Next Week: How Should We Celebrate?
  2. Ubuntu Community Council Reaffirms Its Decision Against Kubuntu's Leader
  3. Future Plans For Changing Fedora's Installer
  4. Confusion Mounts Over Wayland's Actual License
  5. GNOME's Mutter Now Supports Drag-n-Drop To/From Wayland & X11
  6. Wine 1.7.44 Works On More 64-bit ARM Support
  7. Phoronix Test Suite 5.8 Milestone 5 Brings Near Final "Belev" Experience
  8. For AMD Users, Linux 4.2 Will Bring The New AMDGPU Driver & VCE1 For Radeon
  9. Atomic Mode-Setting Still Baking For Samsung's Exynos DRM Driver
  10. Ubuntu Phone Update This Month Brings Many Improvements
Latest Articles & Reviews
  1. Btrfs RAID 0/1/5/6/10 Five-Disk Benchmarks On Linux 4.1
  2. Opening The Gates To Our Daily Open-Source Linux Benchmark Results
  3. The Latest Features For Linux Performance Management + Benchmark Monitoring
  4. Noctua NH-U12DX i4 + NF-F12
Most Viewed News This Week
  1. NVIDIA's Proprietary Driver Is Moving Closer With Kernel Mode-Setting
  2. Zapcc Claims To Be A "Much Faster C++ Compiler"
  3. OpenWRT 15.05 Preparing Improved Security & Better Networking
  4. Features Added To Mesa 10.6 For Open-Source GPU Drivers
  5. Ubuntu's LXD vs. KVM For The Linux Cloud
  6. The Latest Linux Kernel Git Code Fixes The EXT4 RAID0 Corruption Problem
  7. Friction Building Around An Ubuntu Community Council Decision
  8. Fedora 22 Is Being Released Next Tuesday