From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Clightd not working
Date: Mon, 04 Jul 2022 04:15:16 +0200 [thread overview]
Message-ID: <20220704021516.jeaqGWnFtyiCXDFsMGXkyrnA0IRjZLw2iUq1-9gAwYc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34630@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2074 bytes --]
Closed issue by danjenson on void-packages repository
https://github.com/void-linux/void-packages/issues/34630
Description:
### System
* xuname:
```
Void 5.15.9_1 x86_64 GenuineIntel uptodate rFFFF
```
* package:
```
Clight-4.7_1
```
### Expected behavior
Clight daemon would respond to clight, without sudo.
### Actual behavior
The daemon/service does not seem to respond to clight. Even running, `dbus-run-session clight` with the `Clightd` service running returns an Idle Error. It will only work with `sudo dbus-run-session clight`, which seems to circumvent using Clightd. (The point of Clightd is so clight can be run without sudo privileges). I have added my user to `i2c`, `dbus`, and dbus is running (so is polkitd). I also start bspwm with `exec dbus-launch --exit-with-x11 bspwm`. The author of `clight` is unfamiliar with void/bspwm, so is having a hard time debugging (https://github.com/FedeDP/Clight/issues/240).
### Steps to reproduce the behavior
1. Install `Clightd`
2. Enable `dbus`, `polkitd`, and `Clightd`
3. Start a bspwm session with `exec dbus-launch --exit-with-x11` (in ~/.xinitrc)
4. Start clight with `dbus-run-session clight`
5. Check the log at `~/.local/share/clight/clight.log`. It will have the following lines:
```
(I)[10:02:12]{main.c:127} Clightd found, version: 5.4.
(I)[10:02:12]{keyboard.c:158} Keyboard backlight calibration supported.
(I)[10:02:12]{interface.c:180} org.freedesktop.ScreenSaver dbus interface exposed.
(I)[10:02:12]{upower.c:54} AC cable disconnected.
(I)[10:02:12]{upower.c:65} Laptop lid opened.
(W)[10:02:12]{idler.c:22} Clightd idle error.
(W)[10:02:12]{dimmer.c:55} Failed to init. Killing module.
(W)[10:02:12]{idler.c:22} Clightd idle error.
(W)[10:02:12]{dpms.c:48} Failed to init. Killing module.
(W)[10:02:42]{location.c:89} Timed out waiting on location provided by Geoclue2. Killing module.
(W)[10:02:42]{daytime.c:68} No location provider found; fallback to DAY daytime.
(W)[10:02:42]{gamma.c:91} Killing GAMMA as no location provider is available.
```
prev parent reply other threads:[~2022-07-04 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 18:20 [ISSUE] " danjenson
2021-12-20 18:41 ` danjenson
2022-06-19 2:16 ` github-actions
2022-07-04 2:15 ` github-actions [this message]
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=20220704021516.jeaqGWnFtyiCXDFsMGXkyrnA0IRjZLw2iUq1-9gAwYc@z \
--to=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).