Save screenshot to dropbox

neiaberau · June 17, 2017, 1:09pm

The only feature of Dropbox is still use and therefore the only reason why I still have Dropbox installed, is the save screenshot feature.

would it be possible to add something like this to Seafile?

epinez · June 18, 2017, 1:36am

Which client are you referring to?

Android

Open the app, go to settings
Enable camera upload
Follow the setup, tap on “manual selection of folders”
Select the Screenshot folder

Please note: In the history there were a few problems with automatic file uploading. Test it and feel free to share your result here.
Also important: I have the feeling that some of the Seafile developers said in this forum that the autoupload will be deprecated in the near future but I’m not 100% sure.
See also: https://github.com/haiwen/seadroid/issues/55

Linux (One possible solution)

Only applies to distros which save their Screenshots in ~/Pictures and save their home path config in `~/.config/user-dirs.dirs`

Open terminal
type in: nano ~/.config/user-dirs.dirs
Change the target folder on XDG_PICTURES_DIR="$HOME/Pictures" to a folder which is synchronized by the Seafile client
Save the file by typing Ctrl+O and exit by typing Ctrl+X

Please note: This will synchronize all of your Pictures saved in ~/Pictures to your Seafile instance.

Marook · June 18, 2017, 10:34pm

Just save the screnshot inside a synced folder and you’re done… If you want a screenshotapp which can be used with seafile, use ShareX - there is a plugin for seafile. You just need to configure it with login credentials and the target library. After that you can set this upload target as default. If you take a screenshot, it will be uploaded into seafile.

neiaberau · June 20, 2017, 10:12pm

it seems I was very not very precise in my original post:

obviously it should say screen shot to seafile
I meant screenshot, camera upload was just an example
mainly windows secondary Linux
it was about automatic saving of screenshots without manual saving

so having said this, it seems sharex does what I want and much more. I will see how it works, thanks for posting about it.

Calby · June 21, 2017, 5:01pm

For Windows you can just change The place where windows saves the screen shots to your seafile folder.

vetwhat · July 23, 2018, 11:10pm

Hey there,

I would like to re-discuss this topic.

Does anybody use the way to synchronise screenshots in the way described by Calby?
In my words: You sync a library from Seafile to your client and your client is putting screenshots into this folder. Seafile should sync the files as they are written accordingly.

I try to do so on my Mac and on every screenshot, my Seafile Client (6.1.8) will stop synching (libraries won’t be removed) unless I restart it. Then previous files are getting synced, but not as they are written.

Corresponding log messages:

#ccnet.log

Local peer down

#applet.log

Bad response: 515 peer down.
failed to get repo list: Transport Error
[FinderSync] update watch set failed
Bad response: 102 processor is dead.

Can anyone explain to me why the sync process dies?
Is there a way to get more debug information logging?

wthess · July 24, 2018, 4:19am

Can you post the corresponding errors from the Seafile server logs? Those are all symptoms that could be due to a variety of issues.

vetwhat · July 24, 2018, 10:19am

Below you see the snippets from the logs from startup to stop of sync:

#seafile.log

[07/24/18 00:58:46] seaf-daemon.c(558): starting seafile client 6.1.8
[07/24/18 00:58:46] seaf-daemon.c(560): seafile source code version 529172aa2ee41794299bc22289b555d391cf0beb
[07/24/18 00:58:46] …/common/mq-mgr.c(60): [mq client] mq cilent is started
[07/24/18 00:58:46] …/common/mq-mgr.c(106): [mq mgr] publish to heartbeat mq: seafile.heartbeat
[07/24/18 00:58:47] sync-mgr.c(2252): File syncing protocol version on server https:// is 2. Client file syncing protocol version is 2. Use version 2.
[07/24/18 00:58:48] sync-mgr.c(739): Repo ‘ws18’ sync state transition from ‘synchronized’ to ‘committing’.
[07/24/18 00:58:48] repo-mgr.c(3741): All events are processed for repo 4fb7ffa0-95fe-45d2-83e6-8de608980b87.
[07/24/18 00:58:48] sync-mgr.c(739): Repo ‘ws18’ sync state transition from ‘committing’ to ‘initializing’.
[07/24/18 00:58:49] sync-mgr.c(739): Repo ‘datahub’ sync state transition from ‘synchronized’ to ‘committing’.
[07/24/18 00:58:49] repo-mgr.c(3741): All events are processed for repo 407b7017-0c5b-486c-b5e3-66dd24cccc3e.
[07/24/18 00:58:49] sync-mgr.c(739): Repo ‘datahub’ sync state transition from ‘committing’ to ‘initializing’.
[07/24/18 00:58:50] sync-mgr.c(739): Repo ‘screenshots’ sync state transition from ‘synchronized’ to ‘committing’.
[07/24/18 00:58:50] repo-mgr.c(3741): All events are processed for repo 8422b862-9fb7-452a-900b-090ea21828a2.
[07/24/18 00:58:50] sync-mgr.c(739): Repo ‘screenshots’ sync state transition from ‘committing’ to ‘uploading’.
[07/24/18 00:58:50] http-tx-mgr.c(1153): Transfer repo ‘8422b862’: (‘normal’, ‘init’) --> (‘normal’, ‘check’)
[07/24/18 00:58:50] http-tx-mgr.c(1153): Transfer repo ‘8422b862’: (‘normal’, ‘check’) --> (‘normal’, ‘commit’)
[07/24/18 00:58:50] http-tx-mgr.c(1153): Transfer repo ‘8422b862’: (‘normal’, ‘commit’) --> (‘normal’, ‘fs’)
[07/24/18 00:58:51] http-tx-mgr.c(1153): Transfer repo ‘8422b862’: (‘normal’, ‘fs’) --> (‘normal’, ‘data’)
[07/24/18 00:58:51] sync-mgr.c(739): Repo ‘common’ sync state transition from ‘synchronized’ to ‘committing’.
[07/24/18 00:58:51] repo-mgr.c(3741): All events are processed for repo ca0b3bf1-7e0c-4380-a9b1-6b6c5741df68.
[07/24/18 00:58:51] sync-mgr.c(739): Repo ‘common’ sync state transition from ‘committing’ to ‘initializing’.
[07/24/18 00:58:51] http-tx-mgr.c(1153): Transfer repo ‘8422b862’: (‘normal’, ‘data’) --> (‘normal’, ‘update-branch’)
[07/24/18 00:58:51] http-tx-mgr.c(1153): Transfer repo ‘8422b862’: (‘normal’, ‘update-branch’) --> (‘finished’, ‘finished’)
[07/24/18 00:58:52] sync-mgr.c(739): Repo ‘screenshots’ sync state transition from ‘uploading’ to ‘initializing’.
[07/24/18 00:58:52] sync-mgr.c(1553): Removing blocks for repo screenshots(8422b862).
[07/24/18 00:59:22] sync-mgr.c(739): Repo ‘screenshots’ sync state transition from ‘synchronized’ to ‘committing’.

#ccnet.log

[07/24/18 00:58:45] ccnet-daemon.c(193): starting ccnet client 6.1.8
[07/24/18 00:58:45] ccnet-daemon.c(195): ccnet source code version 5b9f64c2438517e1c95b28678097419542d1d084
[07/24/18 00:58:45] …/common/session.c(132): using config file /Users//.ccnet/ccnet.conf
[07/24/18 00:58:45] …/common/session.c(455): socket file exists, delete it anyway
[07/24/18 00:58:45] …/common/session.c(484): Listen on /Users//.ccnet/ccnet.sock for local clients
[07/24/18 00:58:45] …/common/session.c(290): Update pubinfo file
[07/24/18 00:58:46] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:46] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:46] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:46] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:47] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:47] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:47] …/common/peer.c(943): Local peer down
[07/24/18 00:58:47] …/common/peer.c(943): Local peer down
[07/24/18 00:58:47] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:47] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:47] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:48] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:48] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:48] …/common/session.c(398): Accepted a local client
[07/24/18 00:58:48] …/common/session.c(398): Accepted a local client
[07/24/18 00:59:22] …/common/peer.c(943): Local peer down
[07/24/18 00:59:22] …/common/peer.c(943): Local peer down
[07/24/18 00:59:22] …/common/peer.c(943): Local peer down
[07/24/18 00:59:28] …/common/peer.c(943): Local peer down
[07/24/18 00:59:28] …/common/peer.c(943): Local peer down

#applet.log
[07/24/18 00:58:44]QObject::connect: No such slot AccountManager::reloginAccount(const Account &)
[07/24/18 00:58:45]starting ccnet: ("-c", “/Users//.ccnet”)
[07/24/18 00:58:46]trying to connect to ccnet daemon…

[07/24/18 00:58:46]connected to ccnet daemon

[07/24/18 00:58:46]starting seaf-daemon: ("-c", “/Users//.ccnet”, “-d”, “/Users//Sync/Seafile/.seafile-data”, “-w”, “/Users//Sync/Seafile”)
[07/24/18 00:58:47][Rpc Client] connected to daemon
[07/24/18 00:58:47][Rpc Client] connected to daemon
[07/24/18 00:58:47][MessageListener] connected to daemon
[07/24/18 00:58:48]Starting the network status detector
[07/24/18 00:58:48][AutoUpdateManager] cancel all download tasks
[07/24/18 00:58:48][AutoUpdateManager] clean file caches db
[07/24/18 00:58:48][AutoUpdateManager] clean file caches
[07/24/18 00:58:48][Rpc Client] connected to daemon
[07/24/18 00:58:48]setDockIconStyle show failure, status code: -50

[07/24/18 00:58:48][Rpc Client] connected to daemon
[07/24/18 00:58:49][network detector] got a network failure
[07/24/18 00:58:49][api] network error for http://127.0.0.1:8000/image-view/avatars/0/2/aa4f4cd3939368af49ffac70d9fd18/resized/80/adb6e1f0083f11e22d722c2d9661386b.png: Connection refused

[07/24/18 00:58:49]ServerStatusService: ignore request for host “127.0.0.1”
[07/24/18 00:58:49][network detector] resetting the qt network access manager
[07/24/18 00:59:22][Sea RPC] Bad response: 515 peer down.
[07/24/18 00:59:22]failed to get repo list: Transport Error

[07/24/18 00:59:22][FinderSync] update watch set failed
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22]failed to get path status: Transport Error

[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22]failed to get path status: Transport Error

[07/24/18 00:59:22][Sea RPC] Bad response: 515 peer down.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:22][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23]failed to get path status: Transport Error

[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23]failed to get path status: Transport Error

[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:23][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:24][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25]failed to get path status: Transport Error

[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25]failed to get path status: Transport Error

[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:25][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:26][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:27][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:27]failed to get repo list: Transport Error

[07/24/18 00:59:27][FinderSync] update watch set failed
[07/24/18 00:59:27][Sea RPC] Bad response: 102 processor is dead.
[07/24/18 00:59:27]failed to get path status: Transport Error

(and so on…)

By the way, the client itself won’t crash, it is only the sync that will stop. The green icons showing synced libraries on the client will switch to non-synced libraries in the UI.

wthess · July 24, 2018, 6:04pm

Can you also post the seahub.log and the controller.log from the server?

fakuivan · July 25, 2018, 2:06am

I use ShareX, it allows you to save the screenshot to a specific directory or to upload it to seafile using the API and then copying a share link to the clipboard

vetwhat · July 26, 2018, 7:35am

I don’t have access to these logs, I am no admin

vetwhat · July 26, 2018, 7:37am

Nice tool! I would have a look on it if it was a software for MacOS, too Do you know further similar software that uses the Seafile API?

vetwhat · August 22, 2018, 9:47am

Hi there, I could get rid of the crashes in the meanwhile: I set up a sync interval for the according library.

Maybe the client experiences some file issues when trying to grab a screenshot that belongs do a foreign process?
Anyway, I don’t need my screenshots synced in real-time and I found the sync interval feature. I am OK with 60 seconds delay. I don’t think that’s THE solution nor a workaround, since I am not sure if the client works as usual or if I really faced a problem here. At least it works for now and may help you.

Save screenshot to dropbox

Android

Linux (One possible solution)

Only applies to distros which save their Screenshots in ~/Pictures and save their home path config in ~/.config/user-dirs.dirs

Only applies to distros which save their Screenshots in ~/Pictures and save their home path config in `~/.config/user-dirs.dirs`