-
Notifications
You must be signed in to change notification settings - Fork 198
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
Integrate mpris #93
Comments
Found mpris-service, but it seems like it uses native deps. |
Could better system integration also include notifications and computer specific shortcuts for play/pause ? Notifications could be a whole new issue though ... |
@vprigent what kind of info do you expect to see in notifications? |
Which music in currently playing Depending on the notification system, you can probably include prev/next buttons |
@vprigent so when a track changes, add a native notification ? Seems fair to me. About prev/next buttons, they are present on Windows, the Ubuntu integration is in progress but it's kind of complicated, and the native key for next/prev/play on Mac should work fine in the next release. |
@KeitIG Yup ! I've seen that kind in Rhythmbox ( Linux app ) |
And sometimes Fn+F11 / Fn+F12 key combinations for prev & next song not working.. OS: ElementaryOS 0.4 ( Ubuntu 16.04 ) |
@marzochi Playback keyboard shortcuts "should" be supported, even if I could not test it personally (all laptops have different shortcuts for these). Can you send us the model of your laptop? |
Thanks for reply.
|
So I war re-reading http://www.omgubuntu.co.uk/2017/09/will-you-miss-gnome-legacy-tray again to understand why Gnome wanted Trays to disappear. The explanation is basically: don't use Trays when you can use MPRIS. Reminder: |
Apparently https://getharmony.xyz managed to do it |
|
Working on it ;) |
with
Ubuntu 18.10:
|
@acrisci Any idea what could go wrong here? When editing the module directly and forcing it to be |
You should be running this on the session bus which for me is at The dbus library should be reading the
I'm looking at the code for dbus-next and it might not actually be doing that. It might just be trying to read it from the x11 property, but I need to look into that. If you're running this on Wayland, that's not tested and may introduce some bugs that need to be fixed. Looking into all of this now. |
I looked into dbus-next and confirmed it is reading None of the X11 code is working, so that's pretty much the only way to specify the bus address right now. The session manager should be starting dbus (like with |
thanks; I'll investigate on my side why they are not set! |
@acrisci Mint 19.1 is based on Ubuntu 18.04. So if it works there, it should work in here too. I agree with you on fixing dbus-next X11 would solve the problem. |
I don't think it is a X11 problem, because Maybe a missing DE dependency... |
I did a detailed writeup on the issue on dbus-next here. |
With
(Ubuntu 18.04.2) |
I've run the mpris-service integration test suite on stock Ubuntu 18.04 and it works fine. Both the Can you give me some more info on your setup so I can try to reproduce the issue? |
Ah, interesting thing, I am running the Communitheme snap session. Let me try with the default one. |
Mmh getting the same with the classic session, let me try with a fresh install. |
Getting the same issue on a fresh install. I guess there is a problem with the environment variables then. Maybe Wepback is doing something nasty. I am now trying to not bundle |
Does it look good? @acrisci How do you usually get the |
ok, I think Wepback or Electron is somewhat sanitizing these variables at build/runtime. I need to find a way to let these variables be accessible at runtime |
BAM! Now The problem was indeed Webpack, and more specifically the
Would replace all |
Closed by #477 🎉 Base64 covers are not supported, but I guess it's fine for now. |
Wow!! Excellent!! 👍 |
Basically:
Edit: 11/09/18
Things to think about:
The text was updated successfully, but these errors were encountered: