Summary: | Amarok crashes if it can not find mysql server | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Yurii Kolesnykov <yurii.kolesnykov> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | echidnaman, s.650.fischer, schwarzer |
Priority: | HI | ||
Version: | 2.5.0 | ||
Target Milestone: | 2.6 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/amarok/a3d9d08eb7eee7fea7b0d5141b513d959af122f5 | Version Fixed In: | 2.6 |
Sentry Crash Report: |
Description
Yurii Kolesnykov
2012-04-19 16:33:40 UTC
Problem resolved after I installed mysql-server. Well, yes, a working MySQL, either as an external server or an internal database are mandatory for Amarok to work, that is not a bug but a dependency. Please talk to your distribution, there is a packaging error somewhere as it should not be possible to have Amarok without MySQL or MySQLe Music player which requires sql server are you kidding me? I don't think this is a correct analysis. The packaging for Amarok already depends on the libraries required for running embedded MySQL, making it impossible for the Ubuntu Amarok package to be installed without at least MySQLe support. The issue here is that configuration taken from a computer with a local external database and placed on a computer without the configured database set up yet. If Yuriy decided to switch to using the embedded database, this crash would not occur. In the database configuration section of Amarok's settings, it does give the warning that Amarok expects external databases to already exist, but a case could be made that an incorrectly configured database shouldn't crash Amarok, but to instead provide an error reporting path that does not result in the immediate termination of the application. Either way the Amarok development team chooses to look at this, the issue is either an Amarok bug or a user configuration bug, and not a packaging bug. The problem is that I can not reach settings page because amarok had crashed at start. Well, you can set up a MySQL server without the configuration dialog of Amarok, please have a look at the wiki page here: http://amarok.kde.org/wiki/MySQL_Server Jonathan: the default is MySQLe, not an external server and it doesn't need any user intervention to set it up. While I agree with you that Amarok should give a warning and close instead of crash, this is really a corner case as it is due to a user configuration bug. *** Bug 300152 has been marked as a duplicate of this bug. *** Changing importance, apparently the MySQL version 5.5.23 shipped by Opensuse and Debian sid doesn't provide an embedded MySQLe. This is of course a MySQL problem, but it shouldn't crash Amarok. *** Bug 300191 has been marked as a duplicate of this bug. *** MySQLe is provided. In Debian the package just does not create the folder /etc/mysql/conf.d/. If that folder is there, Amarok runs fine. Git commit a3d9d08eb7eee7fea7b0d5141b513d959af122f5 by Ralf Engels. Committed on 08/08/2012 at 14:48. Pushed by rengels into branch 'master'. Prevent crash in case of non-working sql collection Add some validity checks for the case where a collection is non-initialized. FIXED-IN: 2.6 M +1 -0 ChangeLog M +21 -0 src/core-impl/collections/db/sql/SqlRegistry.cpp M +14 -15 src/core-impl/collections/db/sql/SqlScanResultProcessor.cpp http://commits.kde.org/amarok/a3d9d08eb7eee7fea7b0d5141b513d959af122f5 |