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

Song Change Notifications do not work in Flatpak version #677

Open
BaronKrause opened this issue Apr 29, 2022 · 4 comments · May be fixed by #680
Open

Song Change Notifications do not work in Flatpak version #677

BaronKrause opened this issue Apr 29, 2022 · 4 comments · May be fixed by #680
Labels

Comments

@BaronKrause
Copy link

Tested on 2 different 20.04 Pop_OS Machines using the Flatpak version, the song change notifications when enabled in the plugins do not seem to work.

I tested with and without enabling the "Notification Icon" plugin and making sure its closed/minimized to the system tray before the song change.

@TingPing
Copy link
Member

I can reproduce it not working.

@TingPing TingPing added the bug label Apr 29, 2022
@rcalixte rcalixte linked a pull request Aug 8, 2022 that will close this issue
@rcalixte
Copy link

@BaronKrause Would you be interested in testing #680? This PR aims to address the issue but I can only vouch for the environments I've tested on (or would be willing to install myself). If you can test with at least one of your Pop!_OS machines, I can generate a flatpak ref or you can build and install locally using flatpak-builder based on the branch of the forked repository.

@zdc26z
Copy link

zdc26z commented Sep 27, 2022

@rcalixte If this is still needs testing, I am having the same issue on EndeavourOS using i3wm with dunst for notifications, and I am willing to test.

@rcalixte
Copy link

@zdc26z The fix is still a work in progress. When we're ready, we can ping you for testing. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants