| Summary: | Intermittent segmentation fault when exiting Amarok | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Nick <nick.craig.law> |
| 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: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Valgrind output | ||
|
Description
Nick
2018-08-08 18:42:48 UTC
We would need a backtrace, please see also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Normally I install the dbg files, however in this case the auto installation of the dbg files did not work. I installed the obvious ones for amarok manually, but it's not clear exactly which dbg files or how many are required. Does anybody know what debug files should be installed? Also the backtrace just consisted of a couple of lines that simple said a segmentation fault had occurred. Usually debugging symbols are needed from the application and for the library dependencies, in this case Qt, KDE libraries and Phonon. It is quite hard to debug segmentation faults, running valgrind might give an idea as well. Valgrind does complain about definite memory leaks and other initialisation issues. I'll add an attachment when I get a moment. Created attachment 114435 [details]
Valgrind output
Some of Amarok's output while running valgrind QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioDataOutput ( no objectName ). Object::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int) in /workspace/build/phonon/mediacontroller.cpp:65 Object::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int) in /workspace/build/phonon/mediacontroller.cpp:66 QWidget::insertAction: Attempt to insert null action amarok(14337)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: ********************************************************************************************** ** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: ** ** amarok --debug ** ********************************************************************************************** nick@nick-X681X:~$ Calling appendChild() on a null node does nothing. "<?xml version="1.0" encoding="UTF-8"?> <lfm status="failed"> <error code="8">Operation failed - Most likely the backend service failed. Please try again.</error> </lfm> " QMetaObject::invokeMethod: No such method App::onWsError(lastfm::ws::Error) "<?xml version="1.0" encoding="UTF-8"?> <lfm status="failed"> <error code="3">Invalid Method - No method with that name in this package</error> </lfm> " "<?xml version="1.0" encoding="UTF-8"?> <lfm status="failed"> <error code="3">Invalid Method - No method with that name in this package</error> </lfm> " amarok(14337)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: amarok(14337)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: amarok(14337)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: Calling appendChild() on a null node does nothing. (In reply to Nick from comment #7) > Some of Amarok's output while running valgrind > ... > ** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING > INFORMATION, PLEASE USE: ** > ** amarok --debug > ** > It would be very helpful to also use the --debug flag for this Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |