todo.sr.ht

On 5/7/24 12:46 AM, ~bmiww wrote:

If someone knows of a way to set the XDG_SESSION_ID - i'm also all ears, wouldn't need this patchiness then, i've had no luck digging it up.

It's just an environment variable which you'd set the same way as the XDG_SESSION_ID_OVERRIDE variable you add here.

XDG_SESSION_ID=1234 ./mycompositor

Alternatively, if seatd is running things will just work as seatd grants any eligible user access to the current VT if it is not already in use. If you don't have it running as a service with the seat group set up, you can just do sudo seatd -u YOUR_USERNAME & to run it as a one-off granting only your user access.

It can run in parallel with logind for debugging/development. They only trample on each other if you try to take devices through both in parallel.

#1 Ability to filter out notifications 4 months ago

Comment by ~kennylevinsen on ~kennylevinsen/poweralertd

~anarcat, I asked on that patch about the exact messages, as collected with upower --monitor-detail or sudo busctl monitor, so that I could understand what exactly it is we want to silence.

~tardypad, doing it on notification category has the caveat that any of the warnings also depend on power.cleared to undo them cleanly, which would then need to be ignored if the previous state was a muted state to not cause confusing clear messages. Instead, you probably want to pick which event categories (state, warning, online) to process.

Configuring notifications behavior on the mako side is not really a workaround though.

#4 -s flag does not work 4 months ago

Comment by ~kennylevinsen on ~kennylevinsen/poweralertd

REPORTED RESOLVED FIXED

#1 Ability to filter out notifications 5 months ago

on ~kennylevinsen/poweralertd

~kennylevinsen if I find the time to work on this, would be open to accept the addition of another flag like -c device.removed -c power.critical that can be used several times to list the categories we want to be notified about?

#13 wlsunset not working on river-0.2.6 5 months ago

Comment by ~kennylevinsen on ~kennylevinsen/wlsunset

Unless you set -s/-S, wlsunset runs in sun tracking mode. No lat/lon just means it runs assuming coordinates 0,0, making your test results dependent on time of day. Nothing should have changed in this regard.

You can force a mode by sending SIGUSR1 to wlsunset, but that's meant for dynamic control. You can also just specify both -t and -T to the same value, but it's a little silly and I'm not sure if the math will break.

This is not really an intended usecase, as fixed color adjustments can usually just be made on the monitor.

#13 wlsunset not working on river-0.2.6 5 months ago

on ~kennylevinsen/wlsunset

Thanks for your comment. I was aware of those options, but I wanted to always reduce blue light regardless of the time of day, and found that simply using the -t option worked.

If it was indeed working with the -t option before, I think it did because it was assuming that it was night and hence time to set the low temperature, but now it assumes the opposite for some reason.

On Sun, Mar 24, 2024 at 7:06 PM ~kennylevinsen outgoing@sr.ht wrote:

On 3/24/24 08:40, ~Khalid Bin Walid wrote:

Turns out -T works. Either -t used to work before, or I'm going insane!

-t sets the low temperature target for dimming, -T sets the high temperature target for normal operation.

Make sure you set your position with -l <lat> -L <long> for automatic sun tracking, or alternatively specify manual sunrise/sunset times with -S and -s.

-- View on the web: https://todo.sr.ht/~kennylevinsen/wlsunset/13#event-337888

#13 wlsunset not working on river-0.2.6 5 months ago

Comment by ~kennylevinsen on ~kennylevinsen/wlsunset

On 3/24/24 08:40, ~Khalid Bin Walid wrote:

Turns out -T works. Either -t used to work before, or I'm going insane!

-t sets the low temperature target for dimming, -T sets the high temperature target for normal operation.

Make sure you set your position with -l <lat> -L <long> for automatic sun tracking, or alternatively specify manual sunrise/sunset times with -S and -s.

#45 [greetd cargo error] 7 months ago

Comment by ~kennylevinsen on ~kennylevinsen/greetd

Should be fixed in master.

REPORTED RESOLVED CLOSED

#19 pam.d hardcoded location doesn't account vendor dirs 7 months ago

Comment by ~kennylevinsen on ~kennylevinsen/greetd

Not to my knowledge, and I'm not sure if there's official support for /usr/etc in the first place.

Either way, the "right" way to do this is to remove the probing and thereby decouple greetd from the paths altogether. I just dropped the check for login fallback service, and we should be able to change the greeter service file behavior to not care either.

#12 Not working on mirroring monitor 8 months ago

Comment by ~kennylevinsen on ~kennylevinsen/wlsunset

Yeah, I think you should open a wayfire issue. Wayfire only exposes one output in this setup, so we're doing all we can.