Created attachment 168912 [details] screenshot of the error *** amarok-2.9.71^git20240330.7ec45dd-1.fc40.x86_64 ***@fedora:~$ amarok 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 QObject::connect(Playlist::Model, Playlist::ProxyBase): invalid nullptr parameter QObject::connect(Playlist::Model, Playlist::ProxyBase): invalid nullptr parameter QObject::connect(Playlist::Model, Playlist::ProxyBase): invalid nullptr parameter QObject::connect(Playlist::Model, Playlist::ProxyBase): invalid nullptr parameter 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: Неправильный дескриптор файла *** SUMMARY STEPS TO REPRODUCE 1. Запуск Amarok из меню. Ни какой реакции, даже сообщения об ошибке нет. 2. Переустановка приложения через терминал (sudo dnf reinstall amarok) 3. Запуск Amarok из меню, не работает. 4. Запуск Amarok из терминала (описание информации из терминала выше, + скрин во вложении) OBSERVED RESULT Не запускается EXPECTED RESULT Запуск приложения SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION
Thank you for report. Unfortunately I don't read fluent Russian, but looking at errors, seems like a packaging/installation related problem. Make sure you have mariadb-embedded installed. You can also try resetting amarok settings & embedded database by deleting ~/.config/amarokrc and ~/.local/share/amarok/. If that does not help, running `amarok --debug` or getting a backtrace with KDE crash reporter (or manually through gdb) might provide more information.
(In reply to Tuomas Nurmi from comment #1) > Спасибо за отчет. К сожалению, я плохо читаю по-русски, но, глядя на ошибки, > кажется, что проблема связана с упаковкой / установкой. Убедитесь, что у вас > установлена mariadb-embedded. Вы также можете попробовать сбросить настройки > amarok и встроенную базу данных, удалив ~/.config/amarokrc и > ~/.local/share/amarok/ . Если это не поможет, запуск `amarok -- debug` или > получение обратной трассировки с помощью KDE crash reporter (или вручную > через gdb) может предоставить дополнительную информацию. Good afternoon. 1. I checked that the mariadb-embedded package is installed. 2. Performed the removal of the Amarok program, then deleted the directories you specified (~/.config/amarokrc and ~/.local/share/amarok/). After that, I restarted the computer. Next, I installed Amarok through the terminal. Unfortunately, the error is the same. The program did not start.. 3. Performed `amarok --debug` - the result is below (+ screenshot in the attachment). ***@fedora:~$ amarok -- debug QObject::connect(Playlist::Model, Playlist::ProxyBase): invalid nullptr parameter QObject::connect(Playlist::Model, Playlist::ProxyBase): invalid nullptr parameter QObject::connect(Playlist::Model, Playlist::ProxyBase): invalid nullptr parameter QObject::connect(Playlist::Model, Playlist::ProxyBase): invalid nullptr parameter 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/avestov/.local/share/amarok/mysqle/amarok/admin' is marked as crashed and should be repaired" errno: 2000 Got ERROR: "unknown: Table '/home/avestov/.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: Неправильный дескриптор файла Next, I will try to get a backtrace using KDE crash reporter, if possible, I will supplement this message with the results.
Closing this in favour of another apparently corresponding report of 2.9.71 crashing on Fedora 40, which, although was filed some days after this, contains a backtrace and more information. *** This bug has been marked as a duplicate of bug 486468 ***