| Summary: | amarok freezes | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Germano Massullo (Thetra) <germano.massullo> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.9.0 | ||
| Target Milestone: | kf5 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | gdb backtrace | ||
Unfortunately you do not have debugging symbols installed for Amarok, so the backtrace is not really useful. If this crash is reproducible, please install the debugging symbols and provide a better backtrace. Please post it inline, not as an attachment. See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports (In reply to Myriam Schweingruber from comment #1) > Unfortunately you do not have debugging symbols installed for Amarok, so the > backtrace is not really useful. If this crash is reproducible, please > install the debugging symbols and provide a better backtrace. Yes you are right, I have missed some debuginfo because if this weird GDB behaviour in Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1571898 > Please post it inline, not as an attachment. No, it exceeds the maximum chars limit in a message. I think we better close this ticket, I will reopen a new one in case I will get better debuginfos Trim it, then. Comments are searchable, attachments not directly. Usually the issue is not at the start of the GDB output, if there is no mention of Amarok strings there, you can easily discard that part. In your particular example only the last thread seems to have been relevant. Closing for now, please reopen if this happens again and you have debugging info. (In reply to Myriam Schweingruber from comment #3) > Trim it, then. Comments are searchable, attachments not directly. Usually > the issue is not at the start of the GDB output, if there is no mention of > Amarok strings there, you can easily discard that part. In your particular > example only the last thread seems to have been relevant. > Closing for now, please reopen if this happens again and you have debugging > info. Users may not be programmers, it is developers work to take care of users logs. Trim them when necessary, paste them here and make them searchable. (In reply to Germano Massullo from comment #4) > > Users may not be programmers, it is developers work to take care of users > logs. Trim them when necessary, paste them here and make them searchable. I am not a developer... We already have a lot on our plate as bug triagers, the developers will not see any reports until a bug is triaged, work done by a handful of volunteers... So much for "responsibilities". |
Created attachment 132210 [details] gdb backtrace Amarok freezed during playback 2.9.0 on Fedora 32