From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ratbagd starts too early?
Date: Sun, 22 Nov 2020 14:50:30 +0100 [thread overview]
Message-ID: <20201122135030.FxyrIt-xBu6SGeb6MWiLmvasi8rovVkyajzKcD1FaMs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26430@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/26430#issuecomment-731738805
Comment:
You probably don't even need to start the service. It should be activated by dbus. Make sure your `dbus` service is enabled and that you start your window manager wrapped by `dbus-run-session` to make sure you have a consistent user session.
If, for some reason, you really do need the daemon, your modifications to the run script have several issues. The `xset q` test is guaranteed to fail because the service script doesn't know what `DISPLAY` to use. The udev check is effectively a no-op. (The `sv check` construct works for dbus because the dbus service defines a `check` script that properly defines conditions under which it may be considered "up". Most services, udev included, do not; in that case, `sv check` effectively tests whether the service is linked in `/var/service`, not whether it's running, and certainly not whether it's in a stable state.) The `w` check, if one user is logged in, may be ok, but will crash and burn with more than one logged-in user because you aren't quoting the subshell output.
next prev parent reply other threads:[~2020-11-22 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:05 [ISSUE] ratbgagd " sardior
2020-11-16 15:16 ` ratbagd " ericonr
2020-11-17 13:16 ` sardior
2020-11-22 12:15 ` ahesford
2020-11-22 13:50 ` Duncaen [this message]
2020-11-24 15:58 ` sardior
2020-11-24 16:02 ` ericonr
2020-11-24 16:03 ` ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201122135030.FxyrIt-xBu6SGeb6MWiLmvasi8rovVkyajzKcD1FaMs@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).