-
Notifications
You must be signed in to change notification settings - Fork 767
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
loading music... (nothing happens) #3667
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of duplicate issues on this repo, so please double check now that your issue has not already been solved or doesn't have an open issue already. |
I have the same issue. Tried running as administrator and enabling some of the settings which mentioned W10 services, but still stuck. |
See #3660. |
That fixed it for me (Windows 10) - I just downloaded and ran the file here: https://ci.appveyor.com/project/MarshallOfSound/google-play-music-desktop-player-unofficial/build/artifacts |
That worked for me!! THX! |
That fixed the same problem I had on multiple systems. Thank you. |
Thanks, fixed for me as well!! |
I am having this issue as well, but I am running the Ubuntu version of the package. Is there an App Veyor for Ubuntu? |
The artifacts for ubuntu are under CircleCI. You can find the artifact links in the readme near the top. |
Also, this is a duplicate of #3660. |
I'm sorry--- It isn't clear to me as to how to pull the update out of there :-/ Sorry if this is a dense question. |
Err scratch last. I just got it to work by following the links in #3660. I appreciate your help! |
OS: W10 64bits
GPMDP Version: 4.6.1
Issue Descriptions: loading music... (nothing happens)
Steps to Reproduce: open the app (I had tried it in two computers that it works before)
DEBUG INFO:
{"level":"info","message":"Application started.","timestamp":"2019-11-07T09:09:58.678Z"}
{"level":"info","message":"Application exiting...","timestamp":"2019-11-07T09:18:31.544Z"}
{"level":"info","message":"Application started.","timestamp":"2019-11-07T09:18:50.993Z"}
The text was updated successfully, but these errors were encountered: