| Summary: | Amarok does not start and you have already tried it 3 times | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Achim25 <achimxm369> |
| Component: | Notifications | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | tuomas |
| Priority: | NOR | ||
| Version First Reported In: | 3.2.1 | ||
| Target Milestone: | kf5 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Achim25
2025-02-19 14:46:27 UTC
Thank you for your report. As Fedora RPMs are generally known to work, there is likely some system specific problem, but this report doesn't unfortunately yet contain any hints on what might be the problem. Let's try to find some: Do you get the KDE crash handler when trying to start Amarok? If yes, does it provide any developer information on the crash? If not: Could you please try starting amarok by running amarok --debug in console and seeing if there's any output. If yes, please paste it here. If not, it's likely due to Fedora not showing debug output by default - it can be enabled by editing /usr/share/qt5/qtlogging.ini to read something like [Rules] *.debug=true qt.qpa.xcb.xcberror.warning=false qt.*=false kf.*=false and then trying amarok --debug again Pending for more information ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! ๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |