• [ ] GNOME 2 support. Currently it targets GNOME 3. Should be pretty easy to support GNOME 2. Just detect the version and fall back. See: http://askubuntu.com/questions/66914/how-to-change-desktop-background-from-command-line-in-unity
• [ ] KDE4 support. http://blog.zx2c4.com/699 https://code.google.com/p/ksetwallpaper/ https://gist.github.com/X4/5197205
• [x] Cinnamon support.

Running your example:

const wallpaper = require('wallpaper');

wallpaper.set('unicorn.jpg').then(() => {
    console.log('done');
});

wallpaper.get().then(imagePath => {
    console.log(imagePath);
    //=> '/Users/sindresorhus/unicorn.jpg'
});

On Linux Ubuntu throws an error on /lib/linux.js:

return cp.execFile(app.cmd, app.get).then(stdout => 

TypeError: Cannot read property 'cmd' of undefined

Seems to be due to using async functions (get and set) at the same time (same problem with different error if using get before set

The problem solves simply using the second command inside the callback:

const wallpaper = require('wallpaper');

wallpaper.set('unicorn.jpg').then(() => {
    console.log('done');
    wallpaper.get().then(imagePath => {
        console.log(imagePath);
        //=> '/Users/sindresorhus/unicorn.jpg'
    });
});

I'm not sure if the problem is just in linux, and if its an error in the example code or in the linux library.

My script looks like this:

wallpaper.set(fullImagePath).then(() => {
  console.log('Set as wallpaper')
  wallpaper.get().then(imagePath => {
       console.log(`Current wallpaper: ${imagePath}`)
  })
})

which is run by crontab on Ubuntu 16.04 (with GNOME). The wallpaper doesn't change, and the logged imagePath does not equal fullImagePath. The output was like:

Image already downloaded at: /home/doma/scripts/bing-wallpaper-script/downloads/20170605.jpg
Set as wallpaper
Current wallpaper: /usr/share/backgrounds/warty-final-ubuntu.png

However when I run this script manually (not invoke by crontab), it works fine.

I get this error when I run

wallpaper.get().then(console.log)

Error:

UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Command failed: gsettings get org.cinnamon.desktop.background picture-uri
No such schema 'org.cinnamon.desktop.background'

First I thought it was a bug on my fork, so I tried pulling from your repo, and then I tried installing the package from npm again. Same problem, my guess is that the command for Cinnamon somehow replaces the command for GNOME (probably because they both use gsettings).

On my linux system with Plasma (running Arch Linux/Manjaro) this tool does not work since neither gsettings nor gconftool-2 nor dcop work even though they are present.

This PR adds a working method using qdbus.

Without #27 or similar this does not really help as the other ones (gsettings ...) are present and used first. As a workaround I just manually delete all other services from the lib/linux.js script for now.

Hi. I was using your package and suddenly it seemed to have stopped working, it's not really a bug though (Linux).

I am using elementaryOS (Ubuntu) and gsettings set picture-uri seems to be caching wallpapers/paths and does not update the wallpaper if a same path is used (I was changing wallpapers every x seconds with the same name in one folder). It doesn't fail, and doesn't give any errors, I'm not too certain how well-known this knowledge is but maybe it is worth mentioning in a readme section? Once you know this it's easy enough to generate random names.

Alternative, something like clearing cache might work? But, this isn't best practice I guess?

Edit^: cache is maybe a bit a wrong explanation/terminology. The path image-uri gets set but wallpaper (when same path) does not update until reboot.

Or, maybe something like wallpaper.set => "get > set > get > if is the same give warning". Although, it might not be the package it's responsibly.

Thanks for all your work!

I promisified linux.js. Did some major refactoring work and wasn't able to test so there might be some flaws in it. It's also getting late here so an upfront sorry for some things I overlooked :).

This PR is in response of issue #42

I purpose you a new file organization for manage the multiple background manager on Linux. I'm using nitrogen so for me it is working. It would be cool if some people could test before merge.

What is it changed ?

setAvailableApps iterate over all manager and test if they are available, if it is they are stored set method just call the set method of each available background managers get method is more difficult to write, due to multiple managers. I use a strategy consisting of count the apparition of a file, and the most used will be return.

The final point is personnal, I think it is the more discutable. I'm ok to debate on this point. I hope this work can help.

Thanks for reading.

i want to set wallpaper from a url like wallpaper.set("ImAgeurl.jpg").then(() => { }); but it dosent work and desktop wallpaper goes black

UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Command failed: E:\new Object\node\small\getpic\[email protected]@wallpaper\lib\win-wallpaper.exe E:\new Object\node\small\getpic\RoyalAlcazars_EN-AU13378849776.png

this is the error message. i have the picture

UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Command failed: D:\ionic\demos\electron\electron-tutorial\node_mo dules\wallpaper\lib\win-wallpaper.exe D:\ionic\demos\electron\electron-tutorial\google.png Failed to set the desktop wallpaper (node:2432) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js proces s with a non-zero exit code.

I have the google.png image in my path but it's still not setting the wallpaper but generating an error.

Hi,

I'm using Ubuntu Jammy with Gnome 42 and the service is not working anymore when gnome set to darkMode. It seems the nes gsetting command is gsettings set org.gnome.desktop.background picture-uri-dark {filename}

Hello, using

• electron (17.1.2) and
• wallpaper (6.1.1)

When building dist with electron builder and running the app - the path to macos-wallpaper is for some reason hardcoded to the path of the local project of the device on which it was building.

The problem is the same with asar false and I tried to manually include wallpaper lib in dist and reference it in the project - it works locally but not after the build again.

I didn't even notice this before trying to run the app on another device where there is no locally saved dev directory with macos-wallpaper lib in the same place.

import { screens } from "wallpaper";
// ...
const currentMonitors = await screens();

Sentry error after running the build

Error
spawn /Users/bumtomica/Development/splashy-desktop/dist/wallpaper/source/macos-wallpaper ENOENT
// or
spawn /Users/bumtomica/Development/splashy-desktop/node_modules/wallpaper/source/macos-wallpaper ENOENT

Not sure if I'm doing something wrong with init or build, please advise.

If I set the wallpaper twice, the second time it will remove the wallpaper and set it to the default desktop wallpaper. The issue is, I can't rely on get to tell me that the wallpaper is correctly set. When the wallpaper is changed back to default, get still returns the wallpaper I set initially. In fact, on MacOS settings, it still shows the correct wallpaper. My program is setting the wallpaper every 24 hours, but it has to be able to reliably recover from a crash, waking from sleep, and timezone shifts. So what I want to do is be able to check if the wallpaper that is currently set is the correct one, and if not, change it. However, because I can't rely on get to do that, I'm not sure what to do.

Am I doing something wrong here? I've tried this on multiple computers and am running into this issue consistently. Maybe there's a good way to work around this limitation?

This is what it looks like if you're running it from the CLI:

// Set the wallpaper
$ /macos-wallpaper set ~/Pictures/wallpaper.jpg --screen all --scale auto
// Wallpaper gets set to this image

// Get the wallpaper
$ /macos-wallpaper get
// Correct image is returned
/wallpaper.jpg

// Run a second set
$ /macos-wallpaper set ~/Pictures/wallpaper.jpg --screen all --scale auto
// Wallpaper now becomes default desktop

// Get the wallpaper again
$ /macos-wallpaper get
// The image I set earlier is returned, even though the desktop is showing the default wallpaper
/wallpaper.jpg

Here's a gif that shows the issue:

When invoking simple script that should change wallpaper with sudo ie: sudo /abs/path/script.js or from cron * * * * * /abs/path/script.js wallpaper stays the same. When called manually and without sudo/cron it works as intended.

Any ideas what might be wrong?

When calling wallpaper.set('img/artwork.png') in a node app running on Mojave, the default wallpaper (not set via this API) is shown for approximately 0.5 sec. Is this a known issue? If so: any ways to get around it? Thanks.

There is a $60.00 open bounty on this issue. Add more on Issuehunt.

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.