Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - google-musicmanager

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: google-musicmanager

Git Clone URL: https://aur-dev.archlinux.org/google-musicmanager.git (read-only)
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: vlad
Last Packager: vlad
Votes: 371
Popularity: 1.866004
First Submitted: 2011-07-22 04:41
Last Updated: 2016-06-25 21:42

Pinned Comments

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 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

jumpcannon commented on 2013-04-18 14:50

Thanks gridcol, unfortunately that sounds like an upstream bug. The following thread may be of interest to you:


You should also feel free to make a post on the archlinux forum to see if anyone there has encountered the problem and figured out a way to solve it.

gridcol commented on 2013-04-18 09:24

Thanks for your reply pajmullaney.

As I said, google-musicmanager worked fine a few weeks. I had the system tray and could work with it, all fine so far.
What I was doing is this:
I added folders to google-musicmanager incrementally:

Then I wanted google-musicmanager to recognize new music in my ../music/ folder. I removed all the folders and just added ../music/. Silly google-musicmanager wanted to upload all my files again, so I closed google-musicmanager, removed my whole library on Google Music, waited one day to do it properly, started google-musicmanager again and gave it a run.
After having google-musicmanager started a few seconds, it terminates with the following message:
"Successfully sent the minidump file."

google-musicmanager.log says (replaced user with $user):
2013-04-17 15:17:51,391 +0200 INFO TId 0x7f006bfff700 Calling ParseMp3 </home/$user/music/The Baseballs/Strings 'n' Stripes/17 Torn (live).mp3> [FileScanner.cpp:60 FileScanner::addFileTypeInformation()]
2013-04-17 15:17:51,429 +0200 INFO TId 0x7f00697fa700 Child Exited 0 [exception_handler_linux.cpp:78 ::LinuxCrashCallback()]

There's nothing wrong with the files. I had all of them already up on Google Music and didn't touch them since then. Does this information help in any way?

jumpcannon commented on 2013-04-18 07:19

gridcol, tyr0: As I've stated previously, the correct behavior for the program is to fork off into the background when started (thus if you start it from the command line it appears to have exited). The icon should appear in your system tray, if you have one - I do not recommend using it without a tray because then you will have no way to interact with the GUI. If your desktop environment or window manager does not provide a system tray, you can use e.g. stalonetray (which is in community).

Please note that this behavior is not in any way connected to the logging system - if you do not have log4cxx installed google-musicmanager will print the messages telling you so, but will still work normally (without logging, of course). If you want to get rid of those error messages or have access to the program's logs, please install log4cxx from the AUR. It is listed as an optional dependency because the core functionality of google-musicmanager does not depend on log4cxx being installed.

If you can confirm that the program actually crashes, you're going to need to do a bit of digging and provide some additional information. I have just tested the program on a fresh install and it continues to work as expected both with and without log4cxx installed.

gridcol commented on 2013-04-17 16:44

musicmanager worked fine here until I removed my folders and tried to re-upload all my stuff. Now musicmanager quits the way tyr0 explained.

I don't get it... looking forward for a genius solution.

gridcol commented on 2013-04-17 16:43

musicmanager worked fine here until I removed my folders and tried to re-upload all my stuff. Now musicmanager quits the way tyr0 explained.

I don't get it... looking forward for a genius solution.

tyr0 commented on 2013-04-11 18:53

I do have the same problem as mentioned by several other users:
log4cxx: No appender could be found for logger (root).
log4cxx: Please initialize the log4cxx system properly.

Afterwards I get the message "Successfully sent the minidump file." and google-musicmanager quits. Has anyone found a solution for this strange behavior?

oneeyed commented on 2013-03-28 19:45

==> Validating source files with md5sums...
google-musicmanager-beta-amd64- ... FAILED
==> ERROR: One or more files did not pass the validity check!

jumpcannon commented on 2013-03-01 23:31

That should be already been taken care of, jyc. Are you still having problems?

jyc commented on 2013-03-01 23:29

Needs to be updated for the qt -> extra/qt4 rename.


jumpcannon commented on 2013-02-27 20:56

ascarpino, thanks for the heads-up.