Package Details: amarok 3.2.1-1

Git Clone URL: https://aur.archlinux.org/amarok.git (read-only, click to copy)
Package Base: amarok
Description: The powerful music player for KDE
Upstream URL: https://apps.kde.org/amarok/
Licenses: GPL2, FDL, LGPL2.1
Submitter: arojas
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 47
Popularity: 0.75
First Submitted: 2018-08-28 13:52 (UTC)
Last Updated: 2025-01-11 22:03 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »

zebulon commented on 2019-01-29 19:57 (UTC)

@frealgagu: works for me, many thanks.

nicoadamo commented on 2019-01-24 19:07 (UTC) (edited on 2019-01-24 22:22 (UTC) by nicoadamo)

I'm suffering a similar (but not the same) message: "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." It also came up after an overall upgrade, including the mariadb package as mentioned by zebulon. EDIT: I've just built amarok-2.9.0.r351.0362c32b7a-1-x86_64 with mariadb 10.3.12-2 previously installed and Amarok launched alright, without any errors. I also corrected before compiling the file /etc/mysql/my.cnf, which should be based on a much simplified /etc/mysql/my.cnf.pacnew (I don't know from which version it got shorter).

zebulon commented on 2019-01-19 09:17 (UTC)

Hi, since 2019-01-18 amarok does not start, complaining with:

The Amarok database reported the following errors: MySQLe query failed! (0) on Error setting option to use embedded connection MySQLe query failed! (2002) Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) on call to mysql_real_connect In most cases you will need to resolve these errors before Amarok will run properly.

I am wondering if this is caused by the mariadb upgrade yesterday. Rebuilding amarok does not fix the issue. Any idea?

billypilgrim commented on 2019-01-18 05:36 (UTC)

Hi maintainer,

Would you mind not bumping the package version for this when there's a new git commit? For one thing this isn't a -git package so it should just be the latest stable version and, for another, you don't need to bump the package version for -git packages either (users can just rebuild when they want a new version).

frealgagu commented on 2018-11-09 17:56 (UTC) (edited on 2018-11-09 17:56 (UTC) by frealgagu)

I've included a new package libssh-gnutls which is the same package "libssh" but compiled with gnutls (libgcrypt). This a new dependency to amarok so amarok shouldn't crash at start.

https://bbs.archlinux.org/viewtopic.php?pid=1810619#p1810619

nicoadamo commented on 2018-11-05 00:58 (UTC)

@frealgagu: Thanks for clarifying so quickly!

frealgagu commented on 2018-11-04 21:54 (UTC)

@nicoadamo there is no a stable 2.9.70 yet, so I've been including the last commits in master branch. Version 2.9.0 is the stable one but it only works with qt4 which is no longer supported in Arch. Once the version 2.9.70 is released i'll keep it as the version of this package.

nicoadamo commented on 2018-11-04 21:45 (UTC)

Sorry, but are version names fine inside the package? I compiled today theoretically "amarok 2.9.0.r258.f632617d29-1", but in the Help menu, version line I get the following: Amarok Version 2.9.70 Using KDE Frameworks 5.51.0

Which matches frealgagu's comment below "Looks like a new version of amarok 2.9.70 will be released soon."

I got confused.

Regards,

Nicolás Adamo

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »