Classic confinement request for aurora-video-wallpaper

store-requests classic-confinement
1

  • name: aurora-video-wallpaper

  • description: Animated video wallpaper manager for Linux / GNOME. Sets video files as desktop wallpapers with multi-monitor support, hardware-accelerated playback via libmpv, and auto-pause when windows cover the display.

  • snapcraft: aurora-wallpaper/snap/snapcraft.yaml at main · daniacosta-dev/aurora-wallpaper · GitHub

  • upstream: GitHub - daniacosta-dev/aurora-wallpaper: Secure, open-source video wallpapers for Ubuntu and GNOME. Minimal permissions, community-driven, and designed with a modular architecture. · GitHub

  • upstream-relation: I am the author and sole maintainer of the upstream project.

  • supported-category: Legacy desktop applications that have not been able to implement strict confinement support

  • reasoning: Aurora Video Wallpaper requires classic confinement for the following technical reasons:

    1. X11 desktop window hints via Xlib: The player binary sets _NET_WM_WINDOW_TYPE_DESKTOP directly using XChangeProperty to position the video window behind all other windows. This requires unrestricted X11 access that is not available under strict confinement.

    2. X11 window monitoring: The player polls _NET_CLIENT_LIST and _NET_WM_STATE atoms to detect when a window covers the wallpaper and auto-pause playback. This requires querying arbitrary windows across the display, which strict confinement does not permit.

    3. DBus session service: The UI and player communicate via a custom DBus service (com.aurorawall.Player). While DBus interfaces exist, they are insufficient in combination with the X11 requirements above.

I understand that strict confinement is generally preferred over classic. I’ve tried the existing interfaces to make the snap to work under strict confinement.

2

This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.

3

This request has been added to the queue for review by the @reviewers team.

4

Hey @daniacosta-dev

Sorry for the delay in my response.

I don’t think your snap fits any of the supported categories as listed in the Process for reviewing classic confinement snaps . Thus, we cannot proceed with this request.

If you want to share the errors you find while running this application under confinement, maybe we can try to make it work

Thanks!

5

Hi jslarraz, thanks for the reply, okay I’ll look into how to integrate it in strict mode