Bug 397035

Summary: Amarok 2.x syncronization target is always offline
Product: [Applications] amarok Reporter: Anderson Medeiros Gomes <amg1127>
Component: Tools/Statistics SynchronizationAssignee: Amarok Bugs <amarok-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: matej
Priority: NOR    
Version First Reported In: 2.9.0   
Target Milestone: kf5   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Anderson Medeiros Gomes 2018-08-01 01:33:29 UTC
Dear Amarok developers,

I am currently unable to configure synchronization of ratings and play count information embedded in my MP3 files with an external MariaDB database. I tried to execute the following steps:

* From the main window, I navigated to "Settings => Configure Amarok => Metadata => Statistics Synchronization";
* I clicked at the "Add" button and added a new synchronization target of type "Amarok 2.x" and database type "external";
* I clicked at the "Synchronize" button, selected the collections I wanted to synchronize, selected all information fields and clicked "Next";

On the "Synchronize Statistics" window, I can see a list of tracks from the local collection, however I am not able to see a list of tracks from my external database. In addition, on the "Configure" window, I see the message "This collection is currently offline" when I hover the mouse over the synchronization target I created.

When launching Amarok from a console window by using the command line "amarok --debug --nofork", I am able to see the following messages:

    -----------------

    amarok: END__: void Amarok2ConfigDialog::updateButtons() [Took: 0s] 
    QSqlDatabase: MYSQL driver not loaded
    QSqlDatabase: available drivers: QIBASE QSQLITE QMYSQL3 QMYSQL QPSQL7 QPSQL
    amarok: BEGIN: void Amarok2ConfigDialog::updateButtons() 

    -----------------

Additional troubleshooting of my issue has made me believe that in the source file src/importers/amarok/AmarokProvider.cpp:38 [1], the argument "MYSQL" is expected to be "QMYSQL", instead. That is because the ImporterSqlConnection:ImporterSqlConnection constructor, which is declared in src/importers/ImporterSqlConnection.cpp:32 [2], seems to pass the "MYSQL" string unmodified to QSqlDatabase::addDatabase [3] constructor.

Please, could you verify if my diagnostic makes sense?

-----------------

[1] https://github.com/KDE/amarok/blob/453aa79e03fc512abcca5b2109a2aecce6dab314/src/importers/amarok/AmarokProvider.cpp#L38
[2] https://github.com/KDE/amarok/blob/453aa79e03fc512abcca5b2109a2aecce6dab314/src/importers/ImporterSqlConnection.cpp#L32
[3] http://doc.qt.io/archives/qt-4.8/qsqldatabase.html#addDatabase-2
Comment 1 Justin Zobel 2022-11-29 05:06:21 UTC
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!
Comment 2 Bug Janitor Service 2022-12-14 05:13:22 UTC
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!
Comment 3 Bug Janitor Service 2022-12-29 05:24:58 UTC
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!