Google-Play-Music-Desktop-Player-UNOFFICIAL-: Doesn't open on ubuntu 18.10

The version with the fix is not released yet. If you want to download a working version, you have to go to : https://circleci.com/gh/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL- and the check the last build for “#master”. Then, go to “artifacts” and download the package you want.

This is for deb 64 bits :

https://2838-40008106-gh.circle-artifacts.com/0/home/circleci/project/dist/installers/debian/google-play-music-desktop-player_4.6.1_amd64.deb

And this for deb 32 bits :

https://2838-40008106-gh.circle-artifacts.com/0/home/circleci/project/dist/installers/debian/google-play-music-desktop-player_4.6.1_i386.deb

PS: This is dev version so it may have some bugs or instability.

@MarshallOfSound Any plans for a release soon? seems folks are still hitting this issue a lot.

Any chance on seeing a 4.6.2 or 4.7.0 or whatever actually being released? It’s been a year since this issue has been noticed in 4.6.1, and almost a year since it has been fixed, and yet workarounds are still needed…

The problem is, the RC you linked to is just that - a release candidate. Any distribution packaging GPMDP is gonna have the previously released 4.6.1 - which, as this issue shows, doesn’t work anymore.

Yes, I agree with you. I commented because I found a work-around that met my personal criteria, and didn’t see it mentioned on the thread.

TBH a showstopper issue with a working fix should have warranted a hotfix release a year ago, or whenever it got fixed. The maintainer should probably solicit help if they can’t manage to do that sort of thing in a timely manner.

WORKAROUND: If you install Visual Studio Code, you can use the working libnode.so from that to get this to work on Fedora 29.

Just run this command: sudo ln -fs /usr/share/code/libnode.so /usr/share/google-play-music-desktop-player/libnode.so

This links the working libnode from VS Code to the player.

FYI the same problem happens on Fedora 29 which will be released today.

https://2911-40008106-gh.circle-artifacts.com/0/home/circleci/project/dist/installers/redhat/google-play-music-desktop-player-4.6.1.x86_64.rpm

Okay, maybe I’m going mad, but I cannot see an Artifacts tab for any recent build in CircleCI.

For any Fedora users who end up here, your latest URLs (as of 19/12/18) are:

https://2911-40008106-gh.circle-artifacts.com/0/home/circleci/project/dist/installers/redhat/google-play-music-desktop-player-4.6.1.x86_64.rpm

https://2911-40008106-gh.circle-artifacts.com/0/home/circleci/project/dist/installers/redhat/google-play-music-desktop-player-4.6.1.i386.rpm

the quickest fix for me on Ubuntu 18.10 was sudo apt-get purge google-play-music-desktop-player to remove the broken install. Then use snap, sudo snap install google-play-music-desktop-player

Adding a comment for Fedora 29:

Make sure you don’t have any garbage from a failed installation:

sudo rpm -qa | grep google-play-music-desktop-player 
sudo yum remove google-play-music-desktop-player 

Download the package mentioned by @pb1051 and @jostrander Finally, install it with:

yum install google-play-music-desktop-player-4.6.1.x86_64.rpm

It will install all the necessary dependencies and or boi runs nice and smoothly afterwards. Thanks, guys

I did a gif to explain what to do :

You have to be logged to see the “artifact tab” and go to https://circleci.com/gh/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/tree/master .

Little confused how this is closed. on Fedora 29 issue still persists. Went as far as to try the flatpak as well but it has the same issue (realize not related here but just for reference).

Have no need for Visual Studio and did the work around using Atom. But a workaround isn’t really a fix. It is likely I have missed something obvious.

sudo dnf install ~/Downloads/atom.x86_64.rpm sudo mv /usr/share/google-play-music-desktop-player/libnode.so /usr/share/google-play-music-desktop-player/libnode.so.bad sudo ln -s /usr/share/atom/libnode.so /usr/share/google-play-music-desktop-player/libnode.so

Second Answer

@JoshuaGarrison27 doh, my bad, meant to tag @jostrander 😂