Summary: | Configuring a podcast crashes Amarok | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Dan Dart <kde> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED LATER | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | kf5 | ||
Target Milestone: | kf5 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Dan Dart
2019-08-16 14:16:16 UTC
Unfortunately you do not have debugging symbols installed, so the backtrace is not really helpful. I presume you compiled the kf5-port of Amarok yourself as it is not released yet, so you will have to rebuild it with debugging enabled. FWIW, Current Amarok master is not released yet, the software is pretty much in alpha stage lacking the port of the context view. Crashes are to be expected Ah yes, well this is from https://launchpad.net/~joe-yasi/+archive/ubuntu/amarok-kde5 which doesn't seem to have separate debugging symbols as a package. Guess I'll try to find a source so I can go back to 2.8 because I didn't realise 2.9 was in beta. Thanks this is not Amarok 2.9.0 you have, but the master build 2.9.70, aka "kde5" (which btw is a misnaming, it's KDE Frameworks 5 based). That's why I said its pre-alpha as we have as of yet not made any releases of it. 2.9.0 on the other hand is very stable though, has a final release and is definitely not in beta stage and should just work. But I don't think you can install it so easily anymore as most dependencies are not shipped with the most recent Kubuntu version anymore. You can ask the maintainer of that PPA to provide debugging symbols which they absolutely should, as they provide a pre-alpha build of a yet unreleased version, so debugging is absolutely mandatory to have in such a situation. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Alright, I'll just make sure - will bring up again if still an issue with dymbols. Marking as unmaintained - I think that's the right thing here. not unmaintained at all, just slowed down. |