Bug 426362 - Amarok Database Error - local Collection shows "0 tracks"
Summary: Amarok Database Error - local Collection shows "0 tracks"
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (other bugs)
Version First Reported In: kf5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: kf5
Assignee: Amarok Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-10 10:06 UTC by notger@disroot.org
Modified: 2020-10-18 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description notger@disroot.org 2020-09-10 10:06:22 UTC
SUMMARY
The following Error Message appears when staring Amarok 2.9.70 Build from sept 10 2020

"The Amarok database reported the following errors:
The configured database plugin could not be loaded.
In most cases you will need to resolve these errors before Amarok will run properly."

"Use External Mysql database" is unchecked and was never used

After ignoring the Error Message
The Local Collection shows "0 tracks" after scanning trough the Music directories for about 10 Minutes


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Kubuntu 20.04

KDE Plasma Version: 
KDE Frameworks Version: 5.68.0
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Myriam Schweingruber 2020-09-12 22:43:41 UTC
I have the same build and can't reproduce this here, my collection shows correctly. 

Please make sure you have not accidentally removed any of the required dependencies (a force reinstall usually helps for that), that the location of the database and collection are mounted and try restarting Amarok.
Comment 2 notger@disroot.org 2020-09-13 13:30:29 UTC
I did a purge uninstall and a reinstall and still
the following Error Message appears
"The Amarok database reported the following errors:
The configured database plugin could not be loaded.
In most cases you will need to resolve these errors before Amarok will run properly."

What do you exactly mean with
"that the location of the database and collection are mounted"
Comment 3 Myriam Schweingruber 2020-09-16 17:05:50 UTC
Make sure you have libmariadbd installed correctly, you probably modified something in your dependencies installation.

Since you can have your collection and/or database elsewhere than on the partition you run Amarok from, these need to be mounted and accessible
Comment 4 notger@disroot.org 2020-09-17 12:36:30 UTC
i tried that, including reinstall, purge, but the database Error remained..

The interesting Thing is that, after giving up on Amarok for now i tried to install it from ppa:pgomes/amarok Version 2.9.70
And everything worked right away, no Database Error, and some GUI troubles like Playlist Fontsize.
Whats actually the different approach between your and ppa:pgomes/amarok Developement ?
Comment 5 Myriam Schweingruber 2020-09-18 02:36:47 UTC
Did you build your previous version yourself? AFAIK Pedros PPA should reflect current master
Comment 6 Bug Janitor Service 2020-10-03 04:33:14 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 7 Bug Janitor Service 2020-10-18 04:33:25 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!