Error: Command failed: which... #37

punkscience · 2018-11-24T02:14:01Z

Basic informations

Splash CLI version: 3.3.0
Node version: v8.10.0
Your OS: Ubuntu 18.04.1

Before you go

[?] I've read the FAQ section.

^ 404 Error

I've the latest version of Splash CLI installed
[X ] I've searched other issues like mine but I haven't found a solution.

The ISSUE

✔ Connected!
✔ Something is happening...
Error: Command failed: which -a gsettings; which -a setroot; which -a pcmanfm; which -a feh; which -a nitrogen; which -a xfconf-query; which -a gconftool-2; which -a dcop; which -a dconf; which -a qdbus

at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:567:12)

To Reproduce
Steps to reproduce the behavior:

Run splash --today

Expected behavior
I expected it to download and replace my wallpaper. :/

Console Output
See above.

The text was updated successfully, but these errors were encountered:

rawnly · 2018-11-24T02:20:17Z

The “—today” flag does not exist. It is —day..

However I don’t think that this is the cause o f the problem. Tomorrow morning I’ll investigate 🤔

I’m sorry to all Linux users but I don’t have a Linux machine to test Splash Cli on.

punkscience · 2018-11-24T02:27:37Z

Sorry -- my bad. :) Also tried with '--day' and '-c' -- got this result:

✔ Connected!
✔ Something is happening...
Error: Command failed: which -a gsettings; which -a setroot; which -a pcmanfm; which -a feh; which -a nitrogen; which -a xfc
onf-query; which -a gconftool-2; which -a dcop; which -a dconf; which -a qdbus

at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

punkscience · 2018-11-24T02:27:57Z

Happy to help you debug if you need it.

rawnly · 2018-11-25T17:22:13Z

Hi, does the splash command (without flags/options) works?

punkscience · 2018-11-26T00:44:47Z

I get the following (screenshot attached). ✔ Connected! 🌍 Magic stuffevents.js:183 throw er; // Unhandled 'error' event ^ Error: EACCES: permission denied, open '/home/darrylwright/Pictures/splash_photos/ATsEkysmm0Y.jpg' Sent from Mailspring (https://link.getmailspring.com/link/1543192992.local-5f2b4d98-329d-v1.5.2-31660462@getmailspring.com/0?redirect=https%3A%2F%2Fgetmailspring.com%2F&recipient=cmVwbHkrMDAwMzFkOWZmMjQ5ZWUzNmZlYWM5N2UwZGI1YTE2MGRjZjhjNDdiMDAzNzRkZGQ5OTJjZjAwMDAwMDAxMTgxMjljNDU5MmExNjljZTE2ZTJhMjQ4QHJlcGx5LmdpdGh1Yi5jb20%3D), the best free email app for work

…

On Nov 25 2018, at 1:22 pm, Federico Vitale ***@***.***> wrote: Hi, does the splash command (without flags/options) works? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub ***@***.***/1?redirect=https%3A%2F%2Fgithub.com%2Fsplash-cli%2Fsplash-cli%2Fissues%2F37%23issuecomment-441456678&recipient=cmVwbHkrMDAwMzFkOWZmMjQ5ZWUzNmZlYWM5N2UwZGI1YTE2MGRjZjhjNDdiMDAzNzRkZGQ5OTJjZjAwMDAwMDAxMTgxMjljNDU5MmExNjljZTE2ZTJhMjQ4QHJlcGx5LmdpdGh1Yi5jb20%3D), or mute the thread ***@***.***/2?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMdnyWZ2Egj42v9NekZb-dltHxvYvKwks5uytHFgaJpZM4YxPB2&recipient=cmVwbHkrMDAwMzFkOWZmMjQ5ZWUzNmZlYWM5N2UwZGI1YTE2MGRjZjhjNDdiMDAzNzRkZGQ5OTJjZjAwMDAwMDAxMTgxMjljNDU5MmExNjljZTE2ZTJhMjQ4QHJlcGx5LmdpdGh1Yi5jb20%3D).

rawnly · 2018-11-26T00:47:15Z

Have you tried editing permissions of the following path?

home/darrylwright/Pictures/splash_photos

punkscience · 2018-11-26T03:51:58Z

That folder doesn't exist. The pictures are getting downloaded to my home folder.

…

On Nov 25 2018, at 8:47 pm, Federico Vitale ***@***.***> wrote: Have you tried editing permissions of the following path? home/darrylwright/Pictures/splash_photos — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub ***@***.***/0?redirect=https%3A%2F%2Fgithub.com%2Fsplash-cli%2Fsplash-cli%2Fissues%2F37%23issuecomment-441489445&recipient=cmVwbHkrMDAwMzFkOWYwNWQzNjViNDljOWUwOTNkYjRlMWFhNzg1MGEzM2NjNWYyNzExNjE5OTJjZjAwMDAwMDAxMTgxMzA0OTM5MmExNjljZTE2ZTJhMjQ4QHJlcGx5LmdpdGh1Yi5jb20%3D), or mute the thread ***@***.***/1?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAMdn7S5g6MnpKH3bhjPdI1BzA_eWcX7ks5uyzoTgaJpZM4YxPB2&recipient=cmVwbHkrMDAwMzFkOWYwNWQzNjViNDljOWUwOTNkYjRlMWFhNzg1MGEzM2NjNWYyNzExNjE5OTJjZjAwMDAwMDAxMTgxMzA0OTM5MmExNjljZTE2ZTJhMjQ4QHJlcGx5LmdpdGh1Yi5jb20%3D).

rawnly · 2018-11-26T17:01:59Z

Try by creating it via mkdir -p ~/Pictures/splash_photos or may be changing the default dir in splash-cli to a custom path.

To change the dir of splash-cli just do the following:

  splash settings
  # ... Then is the 2nd question that is presented.

punkscience · 2018-11-26T23:39:21Z

I tried creating ~/Pictures/splash_photos manually and it had no effect. When I tried to run splash settings I saw the following screen (below). I am afraid I don't know what any of these means so it wasn't clear where to set the folder. I couldn't get past the first question. _(_) ___ _ __ | | __ _ ___| |__ (_) _ (_) _ (_) _ / __| '_ \| |/ _` / __| '_ \ _ (_) (_) _ (_) \__ \ |_) | | (_| \__ \ | | | _ (_) _ (_) _ |___/ .__/|_|\__,_|___/_| |_| (_) _ (_) (_) (_)|_| (_) (_) (_)(_) (_)(_) (_)(_) ( B | y ) ( D | a | n | i | e | l ) ( P | r | i | c | e ) ( v2.8.0 [6th April 2018] Copyright (C) 2005-2017 ) * SPLASH comes with ABSOLUTELY NO WARRANTY. This is free software; and you are welcome to redistribute it under certain conditions (see LICENCE file for details). * Updates/userguide: http://users.monash.edu.au/~dprice/splash Email: daniel.price@monash.edu or splash-users@googlegroups.com Please cite Price (2007), PASA, 24, 159-173 (arXiv:0709.0832) if you use SPLASH in print and don't forget to send pics for the gallery. splash.defaults not found: using default settings reading ascii format

>>>>>>>>>>>>>>>>>>>>>>>>> settings <<<<<<<<<<<<<<<<<<<<<<<<<<

*** error: settings: file not found *** splash.limits not found No data: You may choose from the options below ------------------------------------------------------- d(ata) p(age) o(pts) l(imits) le(g)end s,S(ave) q(uit) ------------------------------------------------------- Please enter your selection now (y axis or option):

rawnly · 2018-11-29T00:45:03Z

Are you sure you had installed splash-cli correctly?

v2.8.0 [6th April 2018] Copyright (C) 2005-2017 ) * SPLASH comes with ABSOLUTELY NO WARRANTY. This is free software; and you are welcome to redistribute it under certain conditions (see LICENCE file for details). * Updates/userguide: http://users.monash.edu.au/~dprice/splash Email: daniel.price@monash.edu or splash-users@googlegroups.com Please cite Price (2007), PASA, 24, 159-173 (arXiv:0709.0832) if you use SPLASH in print and don't forget to send pics for the gallery. splash.defaults not found: using default settings reading ascii format

This doesn't seems to be splash-cli, maybe you have some conflict.

NPM

Uninstall: npm remove -g splash-cli
Installation: npm i -g splash-cli

YARN

Uninstall: yarn global remove splash-cli
Installation: yarn global add splash-cli

punkscience · 2018-11-29T16:02:17Z

Ok -- so I uninstalled and reinstalled and this time the settings worked perfectly. There is a default folder setup for the splash images. But I still seem to get the same crash. The download part seems to function perfectly but whatever that last step is results in this:

Error: Command failed: which -a gsettings; which -a setroot; which -a pcmanfm; which -a feh; which -a nitrogen; which -a xfconf-query; which -a gconftool-2; which -a dcop; which -a dconf; which -a qdbus

at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

rawnly · 2019-01-03T02:09:49Z

Sorry for inactivity, please keep watching #34

rawnly · 2019-01-21T14:44:49Z

@eyesno any news? Have you tried with newer versions?

punkscience · 2019-01-21T15:39:34Z

Sorry guys -- I actually wound up buying a Macbook Pro and switching back to MacOS! :)

…

On Mon, Jan 21, 2019 at 10:44 AM Federico Vitale ***@***.***> wrote: @eyesno <https://github.com/eyesno> any news? Have you tried with newer versions? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMdnzP6GzbAmLq4ZhxOsKeOvNs1z5D0ks5vFdJigaJpZM4YxPB2> .

rawnly · 2019-01-21T15:40:36Z

So I can close this issue?

punkscience · 2019-01-21T17:46:31Z

It's up to you, of course, but if nobody else has reported it and you're unable to reproduce it, I suppose it would make sense. Darryl

…

On Mon, Jan 21, 2019 at 11:40 AM Federico Vitale ***@***.***> wrote: So I can close this issue? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMdnwvY3uyQ4L0mi2rmPIol5-aOT7RDks5vFd90gaJpZM4YxPB2> .

rawnly · 2019-01-22T01:04:25Z

Perfect 👌🏻 I just wanted your confirm before closing it✌️

rawnly added the 👷‍♂️ Work In Progress I'm working on it label Nov 25, 2018

rawnly self-assigned this Nov 25, 2018

rawnly added the Platform: Linux 🐧 Linux related problems label Nov 25, 2018

rawnly added the node v8.x Issues about Node v8.x label Dec 1, 2018

rawnly added Help Wanted and removed 👷‍♂️ Work In Progress I'm working on it labels Jan 2, 2019

rawnly closed this as completed Jan 22, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Command failed: which... #37

Error: Command failed: which... #37

punkscience commented Nov 24, 2018 •

edited

rawnly commented Nov 24, 2018

punkscience commented Nov 24, 2018

punkscience commented Nov 24, 2018

rawnly commented Nov 25, 2018

punkscience commented Nov 26, 2018 via email

rawnly commented Nov 26, 2018

punkscience commented Nov 26, 2018 via email

rawnly commented Nov 26, 2018

punkscience commented Nov 26, 2018 via email •

edited

rawnly commented Nov 29, 2018 •

edited

punkscience commented Nov 29, 2018

rawnly commented Jan 3, 2019

rawnly commented Jan 21, 2019

punkscience commented Jan 21, 2019 via email

rawnly commented Jan 21, 2019

punkscience commented Jan 21, 2019 via email

rawnly commented Jan 22, 2019

Error: Command failed: which... #37

Error: Command failed: which... #37

Comments

punkscience commented Nov 24, 2018 • edited

Basic informations

Before you go

The ISSUE

rawnly commented Nov 24, 2018

punkscience commented Nov 24, 2018

punkscience commented Nov 24, 2018

rawnly commented Nov 25, 2018

punkscience commented Nov 26, 2018 via email

rawnly commented Nov 26, 2018

punkscience commented Nov 26, 2018 via email

rawnly commented Nov 26, 2018

punkscience commented Nov 26, 2018 via email • edited

rawnly commented Nov 29, 2018 • edited

NPM

YARN

punkscience commented Nov 29, 2018

rawnly commented Jan 3, 2019

rawnly commented Jan 21, 2019

punkscience commented Jan 21, 2019 via email

rawnly commented Jan 21, 2019

punkscience commented Jan 21, 2019 via email

rawnly commented Jan 22, 2019

punkscience commented Nov 24, 2018 •

edited

punkscience commented Nov 26, 2018 via email •

edited

rawnly commented Nov 29, 2018 •

edited