Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flameshot: autostart doesn't work & bad desktop file #141873

Closed
2 tasks done
YizhePKU opened this issue Oct 16, 2021 · 4 comments · Fixed by #142669
Closed
2 tasks done

flameshot: autostart doesn't work & bad desktop file #141873

YizhePKU opened this issue Oct 16, 2021 · 4 comments · Fixed by #142669
Labels
9.needs: package (update) This needs a package to be updated

Comments

@YizhePKU
Copy link

Checklist
Project name

nix search name: flameshot

current version: 0.10.1
desired version: master (7977cbb), see below for explanation

Notify maintainers

maintainers: @scode

Note for maintainers

Please tag this issue in your PR.


Currently, there're two issues that affacts flameshot in NixOS:

  1. Autostart doesn't work when the directory ~/.config/autostart doesn't exist (Autostart doesn't work on NixOS flameshot-org/flameshot#1975)
  2. Desktop file points to /usr/bin/flameshot instead of just flameshot

I've landed a PR that fixes issue 1. To fix issue 2, flameshot needs to be built with cmake flag -DUSE_LAUNCHER_ABSOLUTE_PATH:BOOL=OFF. This flag is also newly added (not present in v0.10.1).

We could upgrade right now, or wait for another minor release.

@YizhePKU YizhePKU added the 9.needs: package (update) This needs a package to be updated label Oct 16, 2021
@newAM
Copy link
Member

newAM commented Oct 16, 2021

I appreciate you looking into this, it was on my TODO list.

Are you going to open a PR for the second issue? I think it makes sense to fix now instead of waiting for the next release.

@YizhePKU
Copy link
Author

Well, I can certainly open a PR, but it's probably up to the maintainers to decide whether to upgrade or not? If you can "call the shots" then sure consider it done :)

@newAM
Copy link
Member

newAM commented Oct 16, 2021

I do not call the shots 😅

I have seen packages update from a release version to an "unstable" version to fix problems, for example:

I do not know if there is any criteria for updating to an unstable version, but it seems like a good idea in this case.

@YizhePKU
Copy link
Author

Well then, I guess I'll open a PR and ask for someone to review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
9.needs: package (update) This needs a package to be updated
Projects
None yet
2 participants