I have recently installed openSUSE 12.1 with KDE 4.7.2 on my system, and there seem to be rather strange problems here. First of all, when starting Amarok, I get this error:

Code: Select all

GREPME MySQLe query failed! (2000)  on init

If I press OK, it launches, but the music database is completely empty, even though I defined the directories to search for music from. If I keep the message open for a while, Amarok crashes.

Another issue that is probably related is that if I close Amarok, the GUI closes, but the process continues in the background as a zombie process and has to be killed manually and forcibly in order to launch the application anew. It also seems that sometimes two instances of amarok are launched at the same time.

If I launch Amarok through the console, I get these warnings:

Code: Select all

KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work

Object::connect: No such signal Collections::MemoryQueryMakerInternal::newResultReady(Meta::DataList)

Any idea about what is wrong here? The Amarok version is 2.4.3.

Apparently a workaround for this is to switch to the unstable version of Amarok. None of the issues I encountered are there, so that's a good sign. I guess I'll stick to that one, unless I happen to find some other critical bugs there.

Hi there,

I had the same issue than you and I found the soution in an bug report at novell.com.

The issue is caused by the mysql version of the database repository at OBS. So the solution is to downgrade to the mysql version which is located at the OSS repository.

I just removed the databases: repo and downgraded to mysql of OSS and the error was gone.

I've had the same problem, but neither downgrading MySQL nor switching to the Packman version of Amarok helped. I'm switching to another radio player for now

Hey,

yesterday I made an update and now, I've got the same problem too:

"GREPME MySQLe query failed! (2000) on init"

My system:
OpenSuse 12.1
KDE 4.8.3
Amarok 2.5.0 -19 (Packman Repo)

I don't know what to do. This problem I've got the first time and I'm using amarok for many years.

Anybody there whon can help us?

Thanks
jukebox

Hm, did you try asking in the Opensuse forum? as this tread shows this appears to be Opensuse related, since it happened after an update.

Mamarok wrote:Hm, did you try asking in the Opensuse forum? as this tread shows this appears to be Opensuse related, since it happened after an update.

It happens in Debian too. At least to me, and a few more according to this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672207

The suggested workaround (downgrading to mysql 5.1) also implied, at least in my case, removing a few packages that I don't want to remove, so I opted for moving ~/.kde/share/apps/amarok/mysqle instead since I could afford to lose the data, but it didn't seem to work so I've restored that folder.

Here's the output of running amarok on konsole:

Code: Select all

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
mysql_embedded: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
**********************************************************************************************
** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: **
** amarok --debug                                                                           **
**********************************************************************************************
user@localhost:~$ amarok(17316)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(17316)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(17316)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QWidget::insertAction: Attempt to insert null action
amarok(17316)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:


amarok --debug gives a huge wall of text full of errors about amarok trying to perform this and that on uninitialized mysql.

Hallo @Mamarok,

yes, now I have posted this problem in the german OpenSuse-Forum "Linux-Club" (SQL and ODBC).

hallo @Luther Blisset,
when I'm starting amarok on konsole, I get the same output like you

jukebox wrote:hallo @Luther Blisset,
when I'm starting amarok on konsole, I get the same output like you

Looking at it closely, perhaps it's a problem with MySQL and not Amarok? I do not have the '/etc/mysql/conf.d/' folder mentioned in the output. However, I don't think creating it would solve anything because I assume Amarok would need a file that should be inside it.

There is most likely something wrong with the MySQL installation on your system, the debug output doesn't show errors in Amarok but apparently MySQLe is not available.

Please check in your update logs if there was not something removed by the upgrade.

FWIW: on Kubuntu, which is a Debian based distribution the MySQL 5.5 version works quite well, so I am more incline that something went wrong in the update.

Mamarok wrote:There is most likely something wrong with the MySQL installation on your system, the debug output doesn't show errors in Amarok but apparently MySQLe is not available.

Please check in your update logs if there was not something removed by the upgrade.

FWIW: on Kubuntu, which is a Debian based distribution the MySQL 5.5 version works quite well, so I am more incline that something went wrong in the update.

According to /var/log/apt/history the upgrade to KDE SC 4.8 removed the following packages: libplasmaclock4abi2:amd64 (4.7.4-2+b1), libtaskmanager4abi2:amd64 (4.7.4-2+b1), plasma-widget-smooth-tasks:amd64 (0.0~wip20100227-1.1+b2). There's no mysql related package there, but nevertheless your assumption seems to be right. It's just not immediately obvious from the aforementioned apt log.

The mysql related packages that are installed on my system are as follows:

akonadi-backend-mysql (1.7.2-1)
libmysql-java (5.1.16-2)
libmysqlclient-dev (5.5.23-2)
libmysqlclient16 (5.1.62-1)
libmysqlclient18:amd64 (5.5.23-2)
libqt4-sql-mysql:amd64 (4:4.8.1-1)
mysql-common (5.5.23-2)
mysql-server-core-5.5 (5.5.23-2)

And Amarok depends, among other things, on libmysqlclient16 (>= 5.1.50-1), which in turn depends on mysql-common (>= 5.1.62-1), which is in fact missing from my system and can't be safely installed. I'd guess that's probably the cause of the problem.

It seems I'll have to wait for a new version of one or more of the packages involved in this problem (possibly recompiling amarok against libmysqlclient18 and/or updating the package to depend on it would suffice).

You should report this to Debian as well, as it is looks like a packaging issue.

Mamarok wrote:You should report this to Debian as well, as it is looks like a packaging issue.

Judging from the bug report I linked to in one of my previous comments, I think they're aware of it.

Oops, silly me, sorry for that.

Mamarok wrote:Oops, silly me, sorry for that.

No worries. Thanks for helping me diagnose the cause of the problem.