This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Empty database, proposed solutions don't work

Tags: None
(comma "," separated)
ebisudave
Registered Member
Posts
87
Karma
0
I am using Amarok 2.4, and trying to use an external MySQL database.

When I check the amarokdb database in phpMyAdmin, it is completely empty and devoid of tables. When I scan my collection, nothing gets written to it.

When I run amarok --debug, I am getting this error, which I have seen reported before:

Code: Select all
[ERROR__] Tried to query an uninitialized m_db!


However, I have tried two different solutions that others have reported as working, but they do not work for me.

Proposed solution #1 is to edit ~/.kde/share/config/amarokrc and ensure the Password=password line is present in the MySQL database information. In my case, the database line was already present. It looks like this:
Code: Select all
[MySQL]
CheckCount=19
Password=xxxxxxxx
UseServer=true
User=amarok


Note: On my system I do not seem to have a .kde4 directory. It is .kde. The machine is running Mythbuntu 10.10.

Proposed solution #2 is to ensure I have the following packages installed:
Code: Select all
libdbd-mysql-perl
libdbi-perl
libhtml-template-perl
libnet-daemon-perl
libplrpc-perl
mysql-client
mysql-server
mysql-server-core-5.1


I have all of them installed, and they all claim to be the latest version.

What else do I need to do to get Amarok to talk to MySQL?

Thank you for any advice.
User avatar
Dieter Schroeder
Registered Member
Posts
714
Karma
7
OS
amarokuser has all needed privileges on amarokdb?
Open konsole and enter
mysql -u amarokuser -p
Now enter amarokuser's password
Check the privileges, if login fails
As far as I can remember amarok creates the tables on first launch, but the db must already exist.

m0nk


If men could get pregnant, abortion would be a sacrament.
ebisudave
Registered Member
Posts
87
Karma
0
Thank you for replying.

While checking to confirm that I had priveleges, I noticed in phpMyAdmin that the user "amarok" was listed as being "amarok@%", not "amarok@localhost".

I don't know what a percent sign means in this context, but I changed it to "amarok@localhost", and now it is working.

Thank you for the suggestion that moved me in the right direction.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar