sad
/
dwl
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add startup errors, mention XDG_RUNTIME_DIR in README 

It was just exiting with code 1 for me. The problem turned out to be
that you *need* to set XDG_RUNTIME_DIR or it won't work (I think e.g.
systemd does that for you, but on Void it's not set by default), so
mention that in the README.
This commit is contained in:
Martin Tournoij 2020-06-07 14:50:50 +08:00
parent 8c0afa7c73
commit da5b4d965d
No known key found for this signature in database
GPG Key ID: A6258419189EE585
2 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -74,6 +74,10 @@ this process a SIGTERM and wait for it to terminate (if it hasn't already).
This makes it ideal not only for initialization but also for execing into a
user-level service manager like s6 or `systemd --user`.
You'll have to explicitly set `XDG_RUNTIME_DIR` if your system doesn't do it for
you, e.g. `export XDG_RUNTIME_DIR=/tmp/xdg-runtime-$USER && mkdir -p
$XDG_RUNTIME_DIR`.
More/less verbose output can be requested with flags as well:
* `-q`: quiet (log level WLR_SILENT)

2
dwl.c
View File

@ -1074,6 +1074,7 @@ run(char *startup_cmd)
const char *socket = wl_display_add_socket_auto(dpy);
if (!socket) {
wlr_backend_destroy(backend);
perror("startup: socket");
exit(EXIT_FAILURE);
}
@ -1082,6 +1083,7 @@ run(char *startup_cmd)
if (!wlr_backend_start(backend)) {
wlr_backend_destroy(backend);
wl_display_destroy(dpy);
perror("startup: backend_start");
exit(EXIT_FAILURE);
}