| Summary: | Amarok Database Error - local Collection shows "0 tracks" | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | notger <notger> |
| Component: | Collections/Local | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | ralf-engels |
| Priority: | NOR | ||
| Version First Reported In: | kf5 | ||
| Target Milestone: | kf5 | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
notger@disroot.org
2020-09-10 10:06:22 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. 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" 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 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 ? Did you build your previous version yourself? AFAIK Pedros PPA should reflect current master 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! |