Bug 263639 - amarok crashed without a crash report
Summary: amarok crashed without a crash report
Status: RESOLVED DUPLICATE of bug 246080
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: Xine backend (show other bugs)
Version: 4.4.3 (KDE 4.6.x)
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-19 12:21 UTC by Miguel Tadeu
Modified: 2011-02-10 19:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miguel Tadeu 2011-01-19 12:21:14 UTC
Version:           2.4.0 (using KDE 4.5.5) 
OS:                Linux

amarok is crashing between songs, so this is the only info I'm able to supply. It doesn't generate a crash report window.

Reproducible: Didn't try




OS: Linux (i686) release 2.6.35-24-generic
Compiler: cc
Comment 1 Robby Engelmann 2011-01-19 17:07:40 UTC
I observe this behaviour too. From time to time between tracks, amarok immediately shuts down without any crash report.
I will try to let amarok run from console in debugging mode, hopefully I will see that crash ;-) and can post some more infos.

PS: I use Kubuntu 10.10 with KDE 4.6 RC2.
Comment 2 Myriam Schweingruber 2011-01-20 02:03:44 UTC
Well, a crash report without backtrace is useless, changing status.
Comment 3 Robby Engelmann 2011-01-20 07:49:22 UTC
How can I obtain a complete backtrace when DrKonq does not start after that crash? I only had the idea of letting amarok run in debugmode from console and post the console output.

Yesterday, I didn't see the crash again, but it will happen according to Murphy, when I am far away from the PC or during a party, when guys can make fun of my system :-).
Comment 4 Myriam Schweingruber 2011-01-20 13:23:58 UTC
Please see here on how to get a valid backtrace:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Also running Amarok from a konsole with these options should trigger Dr. Konqi usually:

Amarok -d --nofork

You need to run this at least twice in a row, as debugging is only enabled the first time, the display only happens on the next run.
Comment 5 Robby Engelmann 2011-01-26 07:46:38 UTC
It took a while, but now I am able to post an output from "gdb amarok". I am still using KDE 4.6 RC2 with Kubuntu 10.10. It reads like related to pulseaudio and xine-plugin, is it?


amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
TagLib: You must at least specify a frame ID.
TagLib: You must at least specify a frame ID.
TagLib: A frame of unsupported or unknown type '' has been discarded
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
amarok(4548)/kdeui (KIconLoader): Trying to remove an entry which is already invalid. This  cache is likely corrupt. 
TagLib: You must at least specify a frame ID.
TagLib: You must at least specify a frame ID.
TagLib: A frame of unsupported or unknown type '' has been discarded
TagLib: You must at least specify a frame ID.
TagLib: You must at least specify a frame ID.
TagLib: A frame of unsupported or unknown type '' has been discarded
TagLib: You must at least specify a frame ID.
TagLib: You must at least specify a frame ID.
TagLib: A frame of unsupported or unknown type '' has been discarded
TagLib: You must at least specify a frame ID.
TagLib: You must at least specify a frame ID.
TagLib: A frame of unsupported or unknown type '' has been discarded
TagLib: You must at least specify a frame ID.
TagLib: You must at least specify a frame ID.
TagLib: A frame of unsupported or unknown type '' has been discarded
TagLib: You must at least specify a frame ID.
TagLib: You must at least specify a frame ID.
TagLib: A frame of unsupported or unknown type '' has been discarded
ASSERT: "m_state == BufferingState" in file ../../xine/mediaobject.cpp, line 235
QSocketNotifier: Invalid socket 36 and type 'Read', disabling...
KCrash: Application 'amarok' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/robby/.kde/socket-robby-TravelMate-6292/kdeinit4__0
QSocketNotifier: Invalid socket 58 and type 'Read', disabling...
Assertion 'pa_close(fds[0]) == 0' failed at pulsecore/core-util.c:2215, function pa_close_pipe(). Aborting.
Unable to start Dr. Konqi
Comment 6 Robby Engelmann 2011-01-26 07:50:02 UTC
A few days before, I obtained another output from "gdb amarok". This time amarok crashed on shutdown. Without having gdb running, I would not had recognized that crash. It sounds related:

delete widgets created by createItemWidgets! 
amarok(3191)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(3191)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QSocketNotifier: Invalid socket 36 and type 'Read', disabling...
KCrash: Application 'amarok' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/robby/.kde/socket-robby-TravelMate-6292/kdeinit4__0
QSocketNotifier: Invalid socket 58 and type 'Read', disabling...
Assertion 'pa_close(fds[0]) == 0' failed at pulsecore/core-util.c:2215, function pa_close_pipe(). Aborting.
Unable to start Dr. Konqi
Comment 7 Myriam Schweingruber 2011-01-26 20:57:16 UTC
Re Comment #5: That looks indeed as if it were pulseaudio related. Still, what we need is a backtrace :) Start Amarok like this:

gdb amarok
run -d --nofork

once it crashes, type:

bt all

And give us the output of that last command.
Comment 8 Robby Engelmann 2011-01-26 21:17:11 UTC
OK, I will give it another try and looking forward to the next crash :-)
Comment 9 Robby Engelmann 2011-01-27 07:45:19 UTC
It took some hours, but now I hope I have a good backtrace:


amarok: END__: void Albums::dataUpdated(const QString&, const QHash<QString, QVariant>&) [Took: 1.7s] 
amarok: BEGIN: void CurrentTrack::dataUpdated(const QString&, const QHash<QString, QVariant>&) 
amarok:   BEGIN: void CurrentTrack::resizeCover(const QPixmap&, qreal) 
amarok:   END__: void CurrentTrack::resizeCover(const QPixmap&, qreal) [Took: 0.003s] 
amarok: END__: void CurrentTrack::dataUpdated(const QString&, const QHash<QString, QVariant>&) [Took: 0.007s] 
ASSERT: "m_state == BufferingState" in file ../../xine/mediaobject.cpp, line 235
Program received signal SIGABRT, Aborted.
0x0012e416 in __kernel_vsyscall ()

(gdb) bt all
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x02036941 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0x02039e42 in abort () at abort.c:92
#3  0x01cc52dc in qt_message_output (msgType=QtFatalMsg, 
    buf=0x9791a28 "ASSERT: \"m_state == BufferingState\" in file ../../xine/mediaobject.cpp, line 235")
    at global/qglobal.cpp:2259
#4  0x01cc54aa in qt_message (msgType=<value optimized out>, msg=0x1e3da7c "ASSERT: \"%s\" in file %s, line %d", 
    ap=0xbfffe5e4 "x\247\v\006]\247\v\006", <incomplete sequence \353>) at global/qglobal.cpp:2305
#5  0x01cc55b9 in qFatal (msg=0x1e3da7c "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2488
#6  0x01cc5645 in qt_assert (assertion=0x60ba778 "m_state == BufferingState", 
    file=0x60ba75d "../../xine/mediaobject.cpp", line=235) at global/qglobal.cpp:2004
#7  0x060934a1 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#8  0x06093e53 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#9  0x01dd68ca in QMetaObject::metacall (object=0x8259760, cl=2551, idx=21, argv=0x2) at kernel/qmetaobject.cpp:237
#10 0x01de1df6 in QMetaCallEvent::placeMetaCall (this=0xaa946aa0, object=0x8259760) at kernel/qobject.cpp:534
#11 0x01de36a2 in QObject::event (this=0x8259760, e=0x6) at kernel/qobject.cpp:1219
#12 0x01028fdc in QApplicationPrivate::notify_helper (this=0x816a468, receiver=0x8259760, e=0xaa946aa0)
    at kernel/qapplication.cpp:4396
#13 0x0102f04e in QApplication::notify (this=0xbfffef48, receiver=0x8259760, e=0xaa946aa0)
    at kernel/qapplication.cpp:3798
#14 0x00338f7a in KApplication::notify (this=0xbfffef48, receiver=0x8259760, event=0xaa946aa0)
    at ../../kdeui/kernel/kapplication.cpp:311
#15 0x01dd0b3b in QCoreApplication::notifyInternal (this=0xbfffef48, receiver=0x8259760, event=0xaa946aa0)
    at kernel/qcoreapplication.cpp:732
#16 0x01dd3d8b in sendEvent (receiver=0x0, event_type=0, data=0x8065178)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8065178)
    at kernel/qcoreapplication.cpp:1373
#18 0x01dd3f4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#19 0x01dffa74 in sendPostedEvents (s=0x816c708) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#20 postEventSourceDispatch (s=0x816c708) at kernel/qeventdispatcher_glib.cpp:277
#21 0x033a5855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x033a9668 in ?? () from /lib/libglib-2.0.so.0
#23 0x033a9848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x01dff565 in QEventDispatcherGlib::processEvents (this=0x8064c28, flags=...)
    at kernel/qeventdispatcher_glib.cpp:415
#25 0x010eabe5 in QGuiEventDispatcherGlib::processEvents (this=0x8064c28, flags=...)
---Type <return> to continue, or q <return> to quit---
    at kernel/qguieventdispatcher_glib.cpp:204
#26 0x01dcf609 in QEventLoop::processEvents (this=0xbfffeea4, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece.
) at kernel/qeventloop.cpp:149
#27 0x01dcfa8a in QEventLoop::exec (this=0xbfffeea4, flags=...) at kernel/qeventloop.cpp:201
#28 0x01dd400f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#29 0x01027e07 in QApplication::exec () at kernel/qapplication.cpp:3672
#30 0x08050e75 in main (argc=3, argv=0xbffff904) at ../../src/main.cpp:268
Comment 10 Myriam Schweingruber 2011-01-28 11:38:17 UTC
Indeed, the backtrace would be good, but you don't have debugging symbols installed for Phonon, and the backtrace indicates the crash is with the xine backend in Phonon.phonon-dbg is the package to install
Comment 11 Robby Engelmann 2011-01-28 22:41:42 UTC
I use Kubuntu 10.10 now with KDE 4.6 final release. I had the package phonon-dbg installed and cannot find a package called Phonon.phonon-dbg :-(
Phonon-related I can only find this debugging packages: python-qt-phonon-dbg and phonon-backend-vlc-dbg as packages are not installed on my system.
Comment 12 Robby Engelmann 2011-01-29 11:32:32 UTC
I found the packages phonon-backend-xine-dbg and libxine1-dbg, installed them and got another backtrace, though it was the same like the bt posted some days ago. Do I have to restart the system to get the debugging symbols recognized? I restartet gdb and amarok but not the hole system nor did log out/login.
Comment 13 Myriam Schweingruber 2011-01-31 00:17:33 UTC
You could just paste the backtrcae you got so I can see if something is changed :)
Comment 14 Robby Engelmann 2011-02-06 12:36:13 UTC
up to now, I didn't see the above mentioned bug again, instead sometimes I get a crash with this bt:
(gdb) bt all
#0  0x066a7475 in ?? () from /usr/lib/i686/cmov/libavcodec.so.52
#1  0x00000000 in ?? ()

Unfortunately, I cannot find any debugging symbols for libav in my repos :-(. Should I open a new bug for that? Is an already known problem?
Comment 15 Myriam Schweingruber 2011-02-10 19:01:33 UTC
This is a known problem with the libavcodec library, please check with your distribution.

*** This bug has been marked as a duplicate of bug 246080 ***