Example provided in Amarok on how to setup external database for Amarok is invalid - GRANT is not working. Reproducible: Always Steps to Reproduce: $ mysql -u root -p MariaDB [(none)]> CREATE DATABASE amarokdb; MariaDB [(none)]> GRANT ALL PRIVILEGES ON amarokdb.* TO 'amarokuser' IDENTIFIED BY 'password'; FLUSH PRIVILEGES; Actual Results: MariaDB [(none)]> CREATE DATABASE amarokdb; Query OK, 1 row affected (0.00 sec) MariaDB [(none)]> GRANT ALL PRIVILEGES ON amarokdb.* TO 'amarokuser' IDENTIFIED BY 'password'; FLUSH PRIVILEGES; Query OK, 0 rows affected (0.00 sec) Amarok then fails to connect to the external database and complains about it. http://dev.mysql.com/doc/refman/5.0/en/show-grants.html Expected Results: Amarok works with external database as usual.
Please note, I used external database on MariaDB and it worked. Then I did upgrade: 1398510981: >>> emerge (4 of 21) dev-db/mariadb-5.5.37-r1 to / 1398511133: === (4 of 21) Cleaning (dev-db/mariadb-5.5.37-r1::/usr/portage/dev-db/mariadb/mariadb-5.5.37-r1.ebuild) 1398511134: === (4 of 21) Compiling/Merging (dev-db/mariadb-5.5.37-r1::/usr/portage/dev-db/mariadb/mariadb-5.5.37-r1.ebuild) 1398511296: === (4 of 21) Merging (dev-db/mariadb-5.5.37-r1::/usr/portage/dev-db/mariadb/mariadb-5.5.37-r1.ebuild) 1398511300: >>> AUTOCLEAN: dev-db/mariadb:0 1398511300: === Unmerging... (dev-db/mariadb-5.5.32) 1398511301: >>> unmerge success: dev-db/mariadb-5.5.32 1398511306: === (4 of 21) Post-Build Cleaning (dev-db/mariadb-5.5.37-r1::/usr/portage/dev-db/mariadb/mariadb-5.5.37-r1.ebuild) 1398511306: ::: completed emerge (4 of 21) dev-db/mariadb-5.5.37-r1 to / 1398511306: >>> emerge (5 of 21) virtual/mysql-5.5 to / 1398511306: === (5 of 21) Cleaning (virtual/mysql-5.5::/usr/portage/virtual/mysql/mysql-5.5.ebuild) 1398511306: === (5 of 21) Compiling/Merging (virtual/mysql-5.5::/usr/portage/virtual/mysql/mysql-5.5.ebuild) 1398511307: === (5 of 21) Merging (virtual/mysql-5.5::/usr/portage/virtual/mysql/mysql-5.5.ebuild) 1398511308: >>> AUTOCLEAN: virtual/mysql:0 1398511308: === Unmerging... (virtual/mysql-5.5) 1398511309: >>> unmerge success: virtual/mysql-5.5 1398511311: === (5 of 21) Post-Build Cleaning (virtual/mysql-5.5::/usr/portage/virtual/mysql/mysql-5.5.ebuild) 1398511311: ::: completed emerge (5 of 21) virtual/mysql-5.5 to / After upgrade of mariadb I restarted it and then ran: mysql_upgrade -p Enter password: Phase 1/3: Fixing table and database names Phase 2/3: Checking and upgrading tables Processing databases information_schema .... SHOW DATABASES; +--------------------+ | Database | +--------------------+ | information_schema | | akonadi | | amarokdb | | mysql | | performance_schema | +--------------------+
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Hello. To be honest I no longer care. Amarok was already removed from Gentoo and so I have no means to retest properly. I'm also wondering if Amarok is still alive. Feel free to close the bug as you see fit.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!