When the script console is enabled (Settings -> Configure Amarok -> Scripts) and the Apply or OK button clicked, an error popup appears with the error: "The document could not be saved, as it was not possible to write to /usr/share/apps/amarok/scriptconsole//Script-NNNNNNNN/main.js. Check that you have write access to this file or that enough disk space is available." (NNNNNNNN being a random number that changes each time) After closing the error message, amarok aborts silently. On each subsequent start, the error message reappears, and closing it terminates amarok immediately, so there is no way even to disable the script console again. The only way is to disable it in the config file ~/.kde/share/config/amarokrc in the [ScriptManager] section, set EnableScriptConsole=false. Reproducible: Always Steps to Reproduce: 1. Enable Script Console in Script Manager 2. Click Apply 3. Actual Results: amarok crashes with an error message and cannot be restarted
Please report this upstream, so that this is fixed in final release.
(In reply to Johannes Huber from comment #1) > Please report this upstream, so that this is fixed in final release. I'll gladly do. Would this be at bugs.kde.org?
This was reported upstream at https://bugs.kde.org/show_bug.cgi?id=363176
(In reply to Markus Wernig from comment #3) > This was reported upstream at https://bugs.kde.org/show_bug.cgi?id=363176 Thanks.
Thanks for reporting. Upstream patch added. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=87c151e54bf1f78cfc333845ca69df569cf27bc9