| Summary: | launching amarok failed remote peer disconnected | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Eddie <brownedward478> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | critical | CC: | brownedward478, tuomas |
| Priority: | NOR | ||
| Version First Reported In: | 3.0.1 | ||
| Target Milestone: | kf5 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
gbd debug
outcome of gdb backtrace |
||
|
Description
Eddie
2024-09-04 04:04:38 UTC
Thank you for the report! Looking at output, might be duplicate of https://bugs.kde.org/show_bug.cgi?id=486468 Can you try running gdb amarok run and checking if the output is similar to linked bug, i.e. Thread 1 "amarok" received signal SIGSEGV, Segmentation fault. vlc_pw_lock (ctx=0x8000000300080005) at modules/audio_output/vlc_pipewire.c:76 76 pw_thread_loop_lock(ctx->loop); Created attachment 173513 [details]
gbd debug
Ok ran gbd amarok run | output is
Thread 1 "amarok" received signal SIGSEGV, Segmentation fault.
___pthread_mutex_lock (mutex=mutex@entry=0x28) at pthread_mutex_lock.c:80
80 unsigned int type = PTHREAD_MUTEX_TYPE_ELISION (mutex);
(In reply to Eddie from comment #2) > Created attachment 173513 [details] > gbd debug > > Ok ran gbd amarok run | output is > Thread 1 "amarok" received signal SIGSEGV, Segmentation fault. > ___pthread_mutex_lock (mutex=mutex@entry=0x28) at pthread_mutex_lock.c:80 > 80 unsigned int type = PTHREAD_MUTEX_TYPE_ELISION (mutex); Great, thank you! Interesting, so this is apparently not quite the same issue as the other one. Could you also try getting a gdb backtrace by running gdb amarok run backtrace and pasting the out here, please? Created attachment 173749 [details]
outcome of gdb backtrace
(In reply to Eddie from comment #4) > Created attachment 173749 [details] > outcome of gdb backtrace Okay, thank you very much! So although some lines are slightly different, this apparently still is a duplicate of https://bugs.kde.org/show_bug.cgi?id=486468 so marking as such. There seems to be a potential solution in the latest message of the other bug report, hopefully it fixes the crash for you, too. *** This bug has been marked as a duplicate of bug 486468 *** |