You are not logged in.
Hi,
Google Music Manager worked for me (x86_64) before but I didn't use it for a while and now after an update I get the message
"Login failed. Could not identify your computer"
I've read in a Fedora forum to add biosdevname=0 to the kernel line but this doesn't work here (does this even apply to Arch?).
Any ideas? The password is correct and I can log in through the web interface. I also tried to delete the music manager folder under ~/.config.
Offline
Same problem here. I've never tried Google Music before but now have 1.0.18 installed from the AUR (on an x64 system). I'm using Google's two-factor authentication, but I can't login via the Music Manager with either my standard password or an application-specific one.
Offline
Also have the problem
Offline
Me too...
Offline
same here, Arch 64 bit, wireless (wlan0) with 2-step password verification. Have tried every single solution suggested on the forums
* editing .config/google-musicmanager/Peer.db with sqllite, adding a record pair of
MachineIdentifier = 00:24:d7:8c:3c:d4
* adding kernel boot option biosdevname=0 to /boot/grub/menu.lst
* starting manager with -p [my2steppwdprhase]
It's all the same, "could not identify my computer", even when I enter wrong password. The log file
2012-02-22 13:43:31,398 +0100 INFO TId 0x7fec77ecb780 ************* Music Manager process is starting up ************ [ConfigManager.cpp:1473 ConfigManager::Init()]
2012-02-22 13:43:31,398 +0100 INFO TId 0x7fec77ecb780 Executable: google-musicmanager - Build Number: 247712 Date: Jan 11 2012 Time: 01:29:03 [ConfigManager.cpp:1474 ConfigManager::Init()]
2012-02-22 13:43:31,398 +0100 WARN TId 0x7fec77ecb780 Translation not found, using native strings [AppUtils.cpp:287 AppUtils::SetApplicationLocale()]
2012-02-22 13:43:34,034 +0100 INFO TId 0x7fec77ecb780 Login attempt #0 with screen name -396681481 [../Shared/AccountManager/AccountSession.cpp:89 AccountSession::Login()]
2012-02-22 13:43:34,034 +0100 INFO TId 0x7fec77ecb780 Disconnected (14) [../Shared/AccountManager/AccountSession.cpp:380 AccountSession::OnDisconnected()]
2012-02-22 13:43:34,034 +0100 INFO TId 0x7fec77ecb780 UserSession::HandleDisconnect - status: 14 [UserSession.cpp:100 UserSession::HandleDisconnect()]
2012-02-22 13:43:34,034 +0100 INFO TId 0x7fec77ecb780 Name: lo Physical Address : 00:00:00:00:00:00 [AppUtils.cpp:1090 bool<unnamed>::LinuxMachineIdentifierDumper()]
2012-02-22 13:43:34,034 +0100 INFO TId 0x7fec77ecb780 Name: wlan0 Physical Address : 00:24:D7:8C:3C:D4 [AppUtils.cpp:1090 bool<unnamed>::LinuxMachineIdentifierDumper()]
2012-02-22 13:43:34,034 +0100 INFO TId 0x7fec77ecb780 Name: lo Physical Address : 00:00:00:00:00:00 [AppUtils.cpp:1090 bool<unnamed>::LinuxMachineIdentifierDumper()]
2012-02-22 13:43:34,034 +0100 INFO TId 0x7fec77ecb780 Name: wlan0 Physical Address : 00:24:D7:8C:3C:D4 [AppUtils.cpp:1090 bool<unnamed>::LinuxMachineIdentifierDumper()]
2012-02-22 13:43:37,098 +0100 INFO TId 0x7fec77ecb780 Disconnect requested. [../Shared/AccountManager/AccountSession.cpp:80 AccountSession::Disconnect()]
2012-02-22 13:43:37,098 +0100 INFO TId 0x7fec7003d700 PeerInterface::StopPeer() called [PeerInterface.cpp:81 PeerInterface::StopPeer()]
2012-02-22 13:43:37,098 +0100 INFO TId 0x7fec7003d700 PeerShutdown() [Core/PeerMain.cpp:416 ::PeerShutdown()]
2012-02-22 13:43:37,098 +0100 WARN TId 0x7fec7003d700 The App processor is not created but shutdown was called. [Core/PeerMain.cpp:435 ::PeerShutdown()]
2012-02-22 13:43:37,098 +0100 INFO TId 0x7fec7003d700 Exiting PeerInterface::StopPeer() [PeerInterface.cpp:93 PeerInterface::StopPeer()]
2012-02-22 13:43:37,098 +0100 INFO TId 0x7fec77ecb780 Exiting app [MainWindow.cpp:697 MainWindow::exitApplication()]
2012-02-22 13:43:37,098 +0100 INFO TId 0x7fec77ecb780 Closed 1 database handles for /home/david/.config/google-musicmanager/Peer.db [../../Shared/TpnOpt/SqliteUtils.cpp:88 Database::~Database()]
EDIT: works with eth0 (but I need wlan0 functionality!)
What's up Google?
Last edited by dabbi2000 (2012-02-22 12:50:34)
Offline
The problem has appeared again with the renaming of the interfaces with systemd 197...
Offline
Yes, this is too bad, as I just installed it yesterday...
Offline
So I read on Kay Siever's g+ page that google music manager uses MAC addresses and network interface ids to identify your computer (stooopid I know). So I changed my network naming scheme back to the old system (eth0 and wlan0) and lo and behold, the f*cking thing works again. It is too bad because I actually rather liked the built in persistent naming scheme.
Anyway, hopefully this might help someone, as it is unfortunately the only way I have found to upload my music to google play.
Offline
So I changed my network naming scheme back to the old system (eth0 and wlan0) and lo and behold, the f*cking thing works again.
Can you please tell me how you did it or point me to a guide that explains the renaming process?
Also... if anyone knows... Why is the naming scheme changed? Is there any consequence in going back to the old scheme?
Thank you so much in advance...
Offline
This has been covered many times throughout these forums and in the wiki. But basically it is for instances in which more than one of the same kind of network card are present, and therefore creates persistent network interfaces.
You need to mask 80-net-name-slot.rules.
Offline
thank you so much! your hint pointed me in the right direction...
Giving the command:
ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules
and rebooting did revert to the old naming scheme.
This is the only thing needed for current Google Music Manager version to work.
Thank you again!
Offline
Yeah, no problem. It really rather pissed me off that GMM sucks so much.
Last edited by WonderWoofy (2013-02-19 23:23:18)
Offline
I only have one song to add currently, but am embroiled in an ongoing conversation with Google Play help about this exact issue. I'll keep pressing them to identify my computer by the new naming scheme or through other means. If it works, I'll let you all know.
Last edited by papabean (2013-03-10 04:36:56)
The world is full of tough guys. It does not need me to be one, too.
Offline
I was informed that the new method of interface naming would be passed along to the developers responsible for the Google Music Manager.
Was able to get it working, like others here, by creating the /dev/null symlink for the udev rules.
The world is full of tough guys. It does not need me to be one, too.
Offline
I was informed that the new method of interface naming would be passed along to the developers responsible for the Google Music Manager.
Was able to get it working, like others here, by creating the /dev/null symlink for the udev rules.
Good work papabean... though I am not sure how this was seen as a reasonable design decision in the first place.
Offline
Good work papabean... though I am not sure how this was seen as a reasonable design decision in the first place.
They meant to lock out multiple instances on the same computer by denying to work on virtual machines.
But I still don't understand why.
Offline
Well, it's not over yet and future versions may work out-of-the-box (well, out-of-the-AUR). The latest version of the Music Manager correctly parses the network names, but still fails to recognize the computer correctly.
However, Google support reached out to me after a 3-week gap, so they're working on it. I had sort of assumed that "we'll pass it on to the developers" was a polite way of saying "we've sent that to /dev/null," but that's apparently not the case.
The world is full of tough guys. It does not need me to be one, too.
Offline
seems like that they finally fixed it, currently downloading my library without changing the naming scheme
I see connected people - The seventh sense
Offline
I too can confirm that it is working. Excellent work papabean!
Offline
I'm sure I'm not the only one that submitted logs, but you're welcome.
The world is full of tough guys. It does not need me to be one, too.
Offline