*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. launch amarok 2. it should start 3. it dosn,t OBSERVED RESULT plasma reports launching amarok failed remote peer disconnected EXPECTED RESULT That it would start SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION running in a terminal gives QObject::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int) QObject::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int) Got ERROR: "Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist" errno: 2000 Got ERROR: "unknown: Table '/home/john/.local/share/amarok/mysqle/amarok/admin' is marked as crashed and should be repaired" errno: 2000 Got ERROR: "unknown: Table '/home/john/.local/share/amarok/mysqle/amarok/devices' is marked as crashed and should be repaired" errno: 2000 QWidget::insertAction: Attempt to insert null action QWidget::insertAction: Attempt to insert null action KCrash: Application 'amarok' crashing... The Wayland connection experienced a fatal error: Bad file descriptor
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 ***