Amarok keeps crashing at each start up: hj@aspire ~ $ gksudo amarok QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. amarok(5076)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QWidget::insertAction: Attempt to insert null action amarok(5076)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QSystemTrayIcon::setVisible: No Icon set "sni-qt/5076" WARN 13:31:04.146 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE Could not parse stylesheet of widget 0xb9e54a8 KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/root/.kde/socket-aspire/kdeinit4__0 unnamed app(5075): Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message recipient disconnected from message bus without replying" " pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor QSocketNotifier: Invalid socket 55 and type 'Read', disabling... Unable to start Dr. Konqi Not forwarding the crash to Apport. hj@aspire ~ $ amarok QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. amarok(5127)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QWidget::insertAction: Attempt to insert null action amarok(5127)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (0,-1) are not possible QSystemTrayIcon::setVisible: No Icon set "sni-qt/5127" WARN 13:31:14.699 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE Could not parse stylesheet of widget 0xc2d1730 QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible unnamed app(5126): Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message recipient disconnected from message bus without replying" " KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/hj/.kde/socket-aspire/kdeinit4__0 hj@aspire ~ $ pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor Invalid write to eventfd: Ongeldige bestandsdescriptor Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post(). Aborting. Unable to start Dr. Konqi Not forwarding the crash to Apport.
We need a proper backtrace, please see also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Hi Myriam, the crash assistant will not generate a backtrace anymore. It now tells me to manually file the bug. One information that I can add. Mint is always running in fall back mode, an issue I am unable to solve untill present. This does not seem to affect any application, nore system performance. Best regards, Henderikus. __________________________ Myriam Schweingruber schreef op wo 07-03-2018 om 18:12 [+0000]: > https://bugs.kde.org/show_bug.cgi?id=391522 > > Myriam Schweingruber <myriam@kde.org> changed: > > What |Removed |Added > ------------------------------------------------------------------- > --------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |BACKTRACE > > --- Comment #1 from Myriam Schweingruber <myriam@kde.org> --- > We need a proper backtrace, please see also > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_crea > te_useful_crash_reports >
why do you even try to start it with sudo rights? Bad idea, as it is a GUI application. You should never start GUI applications in sudo mode, unless there are really things you need to do as an admin with, which for Amarok is never the case. At least try installing debugging symbols and get a backtrace by other means, see also the link I gave you, you can always get a proper backtrace with gdb