Disabling gamma support as X is not running. about clight HOT 8 CLOSED

Haha, I can't make promises here, my recovery from the flue is over and I have to work again (unfortunately).

from clight.

Sorry for the boring news, just updated the debs and all seems to work well!
Thank you very much!

from clight.

These are the changes i committed yesterday evening.
Well, at least now we found the root of your issues: it seems that when clight starts, you're not on X (or, well, X is not loaded?).
This is really weird though; i only see a reason for it: you're either running gdm as your DM (that nowadays runs on wayland), or lightdm runs on wayland too (i cannot find any source for this though).
This would explain the issue: as far as you login, you're still on wayland when clight starts; after you manually restart clight.service, from your X session, it does not fail anymore.
If this is the case, the best and simplest thing to do is to disable user service, and add
systemctl --user start clight.service
to your autostart scripts/DE autostart configuration.

from clight.

Another thing you can do is to delay init of clight user service with a timer service: https://wiki.archlinux.org/index.php/Systemd/Timers, using probably

[Unit]
Description=clight.service
[Timer]
RemainAfterElapse=no
[Timer]
OnUnitActiveSec=5s

should fix your issue (call it clight.timer, put it in /usr/lib/systemd/user/ and enable the timer and disable your clight.service).

EDIT: if you think this is a better approach then running manually "systemctl --user start clight" from your session manager, i can ship the timer unit.
In my opinion, it is better to use your DE autostart at this point (so there won't be any "fake delay" to assure unit is started when X should be there, but it will be started as part of your DE)

from clight.

And fixed, thanks a lot again! I decided to take the autostart route directly as I also don't like the idea of an artificial service delay.
Probably Cannonical activated Mir for LightDM at some point like GNOME for GDM. But I can't find a definitive statement about that.
Probably its best if you update your readme and install instructions that Ubuntu (or maybe just Unity) user should use it via autostart and ask for user reports if that happens in other DEs as well.

from clight.

Yes! Indeed i am really thinking about switching to that (ie manually add service start to session autostart config) instead of enabling the service. It causes much less troubles.
BTW for now i'll add that to readme (are you willing to? :D otherwise i'll do that later in the afternoon!)
Thanks for reporting this issue!

from clight.

No problem, i know those struggles :D

from clight.

@donhugo69 I updated both clightd and clight with some improvements (most notably, dropped xhost call as it was a small security hole).
Moreover, it is now stated clearly in readme that recommended way to start clight is through:
systemctl --user start clight.service
in DE startup configuration.
Again, let me know if you encounter any issue :)

from clight.