nullobsi

f601899 should add the ability to add regression points, let me know if that works for you :)

did you enable the milliseconds option in clight? i don't think that's properly handled in clight-gui

The QT error says > could not connect to display This isn't a flameshot bug but a natural issue with the way cron jobs work :) Cronie runs as a...

hmm, flameshot is dbus activated right? flameshot gui just calls the dbus interface to open the currently running instance. if you do `XDG_CURRENT_DESKTOP=sway flameshot` with no `gui`, I wonder if...

this occurs because sway doesn't automatically update the systemd activation environment. so when `flameshot gui` requests activation of flameshot, it doesn't have XDG_CURRENT_DESKTOP or WAYLAND_DISPLAY set, so it falls back...

@RealOrangeOne , xdg-desktop-portal-wlr uses grim to take a screenshot, so you should be sure you have grim installed as well. that's what I think the failed execvp call is. @cvanelteren...

perhaps flameshot should have a wiki page for wlroots support. :)

i will probably make a PR later. @cvanelteren , please make sure you've imported the activation environment as described above, and restart xdg-desktop-portal and flameshot by killing it

``` export XDG_CURRENT_DESKTOP=sway systemctl --user import-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP dbus-update-activation-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP pkill xdg-desktop-portal pkill flameshot ``` the two first commands and the export signal to systemd the environment variables for...

@cvanelteren , all I can think of is try running xdg-desktop-portal like `XDG_CURRENT_DESKTOP=sway /usr/lib/xdg-desktop-portal -v` and make sure it loads xdpw you may also have to kill the old instance...