SMPlayer, being a Qt-based application, has had to adapt to the changing landscape of Linux graphics. Qt, a popular cross-platform application framework, has supported Wayland since Qt 5.4. However, SMPlayer's developers had to ensure that their application works seamlessly with the new display server.
A major missing feature is "Disable Screen Saver" . On X11, SMPlayer inhibits the screensaver. On pure Wayland, the standard xdg-screensaver command often fails, meaning your screen might blank or lock while watching a movie unless your compositor supports the idle-inhibit protocol (most modern ones like KDE/GNOME do, but SMPlayer/mpv must call it).
He had to ensure Qt was using the Wayland platform plugin. QT_QPA_PLATFORM=wayland . He typed the command into the terminal. He launched SMPlayer. smplayer wayland
He spent the next three hours refactoring the screen capture logic, replacing Xlib calls with modern Qt Wayland interfaces.
The video scaled. The frame rate jumped. Not a single frame dropped. The OSD (On Screen Display) stayed locked to the bottom of the video, not floating away as it sometimes did with buggy Wayland ports. SMPlayer, being a Qt-based application, has had to
"Let's see what you've got," he whispered, and hit play.
The Last Render
Initially, SMPlayer had some issues with Wayland, such as problems with video playback, seeking, and fullscreen mode. These issues were largely due to the differences in how X11 and Wayland handle graphics and input. However, with the release of SMPlayer 18.10, the developers announced that their application was now fully compatible with Wayland.
As of my latest knowledge, SMPlayer does have a specific, dedicated "Wayland feature" listed in its official changelogs. However, here is the relevant context regarding SMPlayer and Wayland: A major missing feature is "Disable Screen Saver"