• 0 Votes
    9 Posts
    443 Views
    C
    @AdFundum no problem! the process is basically 3 steps: verify image/PATH copy to lss wallpaper directory (so user can see the background in lss), this is optional if you don't care about the user being able to reset the background from lss its not necessary but still useful as a place the user wont casually delete unless they want the wallpaper gone. send the correct dbus calls to set URI (from new PATH of step 2) then call update on two services via dbus calls. EDIT: i think, or its close to that its been a month since i touched the background code in wallpaper.cpp
  • Notifications: Out of the comfort zone?

    OS notifications background
    29
    2 Votes
    29 Posts
    14k Views
    S
    @Flohack I know that any DBus call - except for some - is by default denied by AppArmor, therefore we should for sure update the confinement AA templates. I think we'd probably need to define a new AppArmor profile for headless apps, in order to prevent e.g. usage of the UriHandler service