Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18697 - [amarok] unable to scan collection

Attached to Project: Arch Linux
Opened by Dario Bertero (Arthnr) - Monday, 15 March 2010, 21:39 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 16 March 2010, 13:26 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Everytime I try to perform a full scan of the collection, it does not load any
file. Using -d option I get continuously
amarok: [ERROR!] Tried to perform escape() on uninitialized MySQL
amarok: [ERROR!] Tried to query an uninitialized m_db!
I have enabled the external database, and it is the same which worked with the
previous version. I've also reported this bug on bugs.kde.com, but they cannot find anything.


Additional info:
* package version(s)
* config and/or log files etc.
amarok 2.3.0-1

Steps to reproduce:
start amarok (with -d flag) and try to scan the collection.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 16 March 2010, 13:26 GMT
Reason for closing:  Not a bug
Comment by Andrea Scarpino (BaSh) - Monday, 15 March 2010, 21:51 GMT
did you try with a clean config?
Comment by Dario Bertero (Arthnr) - Monday, 15 March 2010, 22:00 GMT
I did.
Comment by Andrea Scarpino (BaSh) - Monday, 15 March 2010, 22:20 GMT
I cannot reproduce this on my system here...anyone else got this problem?

please Dario try removing the database and re-create it, then give to amarok access rights to db.
Comment by Dario Bertero (Arthnr) - Tuesday, 16 March 2010, 13:17 GMT
Unfortunately I've already tried it, nothing had changed.
Comment by Dario Bertero (Arthnr) - Tuesday, 16 March 2010, 13:24 GMT
I tried again reconfiguring everything and now it works, also with the old db (maybe I did a mistake somewhere previously).

Loading...