Bug 284810 - Amarok MySqlStorage fails with "GREPME MySQLe query failed! (2000) on init"
Summary: Amarok MySqlStorage fails with "GREPME MySQLe query failed! (2000) on init"
Status: RESOLVED DOWNSTREAM
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 2.4-GIT
Platform: Compiled Sources Linux
: NOR major
Target Milestone: 2.5
Assignee: Amarok Developers
URL:
Keywords:
: 301918 305258 374891 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-10-23 20:30 UTC by Robert Riemann
Modified: 2017-01-12 15:16 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Riemann 2011-10-23 20:30:22 UTC
Version:           2.4.3 (using KDE 4.7.2) 
OS:                Linux

I compiled amarok from trunk and experienced the same problem.
Is this anyhow related to mysql->mariadb migration?


Kind regards,
Robert

Version:
Qt: 4.7.4
KDE Development Platform: 4.7.2 (4.7.2)
Amarok: 2.4.3


Distribution: openSUSE Factory (12.1 rc) 64bit

Output from amarok --debug:

amarok:         BEGIN: void CollectionManager::init(const QList<Plugins::PluginFactory*>&) 
amarok:           BEGIN: void CollectionManager::loadPlugins(const QList<Collections::CollectionFactory*>&) 
amarok:             [CollectionManager] initializing "amarok_collection-mysqlecollection" 
amarok:             [ERROR__] MySQL library initialization failed. 
amarok:             [ERROR__] [MySqlStorage] "GREPME MySQLe query failed! (2000)  on init" 
amarok:             BEGIN: bool DatabaseUpdater::update() 
amarok:               [MySqlStorage] Initialized thread, count== 1 
amarok:               [ERROR__] [MySqlStorage] Tried to perform query on uninitialized MySQL 
amarok:               Database version:  0 
amarok:               BEGIN: void DatabaseUpdater::createTables() const 
amarok:                 [ERROR__] [MySqlStorage] Tried to perform query on uninitialized MySQL 
amarok:                 [ERROR__] [MySqlStorage] Tried to perform query on uninitialized MySQL 
amarok:                 [ERROR__] [MySqlStorage] Tried to perform query on uninitialized MySQL 


Reproducible: Didn't try

Steps to Reproduce:
install amarok, start amarok. Happens after each start

Actual Results:  
Collection is empty

Expected Results:  
No error and a filled music collection

I ran into this problem after upgrading opensuse 12.1 beta to the recent RC. After that I tried to resolve this problem by compiling from git master, but the problem is still there.
Comment 1 Bernhard M. Wiedemann 2011-10-24 07:52:05 UTC
bug was also observed in automated tests of stock openSUSE amarok

first seen 2011-10-05
http://openqa.opensuse.org/viewimg/opensuse/testresults/openSUSE-NET-i586-Build0323/amarok-2.png
Comment 2 Myriam Schweingruber 2011-10-24 12:00:04 UTC
I can't reproduce this here with Kubuntu 11.10. Please check you have no conflicting installations in your MySQL files.
Comment 3 Robert Riemann 2011-10-24 14:34:46 UTC
> Please check you have no conflicting installations in your MySQL files.

How do I do this? What information do you need to help me debugging?
Comment 4 Myriam Schweingruber 2011-10-24 15:13:13 UTC
Well, check the versions of the MySQL packages yo have installed.
Comment 5 Robert Riemann 2011-10-24 21:25:28 UTC
My problem went away after uninstalling mariadb and mariadb-client and installing mysql-community-server{,-client}.

MariaDB seems to got installed by accident when I installed opensuse beta.

So it looks like amarok doesn't accept the drop-in replacement mariadb.
Comment 6 BartOtten 2011-12-20 19:34:36 UTC
I can confirm the work-around from Robert. Who should we talk to to fix this?
Comment 7 Myriam Schweingruber 2011-12-20 23:50:35 UTC
(In reply to comment #6)
> I can confirm the work-around from Robert. Who should we talk to to fix this?

To the distribution IMHO, we clearly ship Amarok with MySQL as a dependency, so does kdelibs btw
Comment 8 BartOtten 2011-12-20 23:57:03 UTC
openSUSE is working on it:

https://bugzilla.novell.com/show_bug.cgi?id=712749
Comment 9 Myriam Schweingruber 2012-06-15 07:58:16 UTC
*** Bug 301918 has been marked as a duplicate of this bug. ***
Comment 10 Myriam Schweingruber 2012-08-16 23:19:01 UTC
*** Bug 305258 has been marked as a duplicate of this bug. ***
Comment 11 saya.bara 2012-08-17 13:43:05 UTC
Thank you so much, the bug not appear again in new version of amarok... :D

On Fri, Aug 17, 2012 at 7:19 AM, Myriam Schweingruber <myriam@kde.org>wrote:

> https://bugs.kde.org/show_bug.cgi?id=284810
>
> Myriam Schweingruber <myriam@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |jtamate@gmail.com
>
> --- Comment #10 from Myriam Schweingruber <myriam@kde.org> ---
> *** Bug 305258 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
Comment 12 Myriam Schweingruber 2012-08-18 07:58:38 UTC
(In reply to comment #11)
> Thank you so much, the bug not appear again in new version of amarok... :D

Which has again nothing to do with Amarok, please check with your distribution, this is a downstream issue with their MySQL implementation.
Comment 13 saya.bara 2012-08-19 15:23:54 UTC
Oh,,
Okay, thanks for the information.. :D

On Sat, Aug 18, 2012 at 3:58 PM, Myriam Schweingruber <myriam@kde.org>wrote:

> https://bugs.kde.org/show_bug.cgi?id=284810
>
> --- Comment #12 from Myriam Schweingruber <myriam@kde.org> ---
> (In reply to comment #11)
> > Thank you so much, the bug not appear again in new version of amarok...
> :D
>
> Which has again nothing to do with Amarok, please check with your
> distribution,
> this is a downstream issue with their MySQL implementation.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
Comment 14 Myriam Schweingruber 2017-01-12 15:16:31 UTC
*** Bug 374891 has been marked as a duplicate of this bug. ***