Package Details: google-musicmanager 1.0.467.4929_r0-6

Git Clone URL: https://aur.archlinux.org/google-musicmanager.git (read-only, click to copy)
Package Base: google-musicmanager
Description: A simple application for adding the music files on your computer to your Google Music library
Upstream URL: http://music.google.com
Licenses: custom:musicmanager
Submitter: jumpcannon
Maintainer: FredBezies
Last Packager: FredBezies
Votes: 389
Popularity: 0.41
First Submitted: 2011-07-22 04:41
Last Updated: 2018-10-17 05:16

Pinned Comments

FredBezies commented on 2018-09-17 04:29

September 17th, 2018: Some namcap cleanup. And we're blocked by google old deb package about libidn. Until there is an update, you'll have to made a symlink for libidn.

Until then, DO NOT FLAG IT as out of date. Thanks.

kyndair commented on 2016-06-28 18:14

the options menu not appearing is a known bug, the workaround is to quit musicmanager and delete the ~/.config/google-musicmanager folder then rerun musicmanager and select an empty folder for uploading, it might complain that it can't upload anything but that can be ignored. You should know be able to open the options widow and select the correct upload and download folders.

Latest Comments

« First ‹ Previous ... 7 8 9 10 11 12 13 14 15 16 17 ... Next › Last »

ilpianista commented on 2013-02-27 14:54

Please drop qt from the depends array as qt is already required by qtwebkit.

Otherwise people that use [testing] will get:
:: spotify: requires qt>=4.5.0

There's no more a 'qt' package in [testing] (and in the next days in [extra])

duffydack commented on 2013-02-15 17:44

I can confirm that reverting my interface naming back to eth0 has fixed my authentication issue.

Anonymous comment on 2013-02-14 18:45

I was able to get past this goofy nonsense by doing the following:

tunctl -t wlan0 -u myusername
ip link set up address 00:04:5a:xx:xx:xx
ip addr add 10.0.0.1/24 dev wlan0

I do not pretend to know if it needed a valid mac (which I didn't have, I use a private number scheme). It wasn't able to identify my computer until I added the ip address with the link up. So, does it use interface names inappropriately, the mac? the IP? it didn't work for me until it had all three to this pretend interface. Now I'm logged in. ymmv.

alucryd commented on 2013-02-12 11:07

Apparently I'm not the only one affected, see here:
http://productforums.google.com/forum/#!msg/apps/PjN5g6Mujuw/p1H8Rm0Uvc4J
http://ubuntuforums.org/showthread.php?t=2087385

There are some temporary workarounds...

alucryd commented on 2013-02-11 15:04

I'm getting the same log4cxx error as everyone, but MusicManager runs almost fine afterwards. I'm saying almost cause I can successfully log in, and choose to download my library in my music folder. However as soon as I click "start" (or whatever that button is called) the window disappears. It seems the downloading is taking place since my music is regularly appearing and the MusicManager process is active, but is the window supposed to disappear?

jumpcannon commented on 2013-02-10 19:38

systemd isn't the problem, I'm using systemd and it works just fine.

Do let me know if the RPM version works for you, I can switch the package over to that version if it helps, but since the DEB version is working for me I can't really test it myself.

Anonymous comment on 2013-02-10 19:32

I am also getting the error message "Login Failed: Could not identify your computer".
I am using systemd and I don't see why it should not work with it.

@dblue
I tried you approach, unfortunatly with no success.

How does the authentification work on other platforms? I think Fedora is using systemd since version 15 or 16.

Maybe you should use the RPM instead of the DEB. I think I give it a try tomorrow and let you know...

Anonymous comment on 2013-02-08 19:05

After I updated my system to use systemd, I started getting the login failed error too. It was fixed for me by reverting back to the eth0 style names using:

ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules

I only tried it with my wi-fi adapter, changing back to wlan0 from wlXXX0, but I guess it'd work for ethN as well as wlanN devices.

Anonymous comment on 2013-02-05 18:06

I am getting the same error message "Login Failed: Could not identify your computer" I am not using a virtual machine

laydros commented on 2013-02-04 16:04

I'm getting the error "Login Failed: Could not identify your computer" Are those of you having success using the kernel switch to enable eth0 style interface names, or am do I have another problem?