Bug 197202 - knotify crashes when switching phonon backend to xine
Summary: knotify crashes when switching phonon backend to xine
Status: RESOLVED UPSTREAM
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: Xine backend (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Matthias Kretz
URL:
Keywords:
: 214409 221273 270690 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-19 22:46 UTC by Dominik Tritscher
Modified: 2011-04-13 03:56 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Tritscher 2009-06-19 22:46:54 UTC
Application that crashed: knotify4
Version of the application: 4.0
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.0
Operating System: Linux 2.6.28-13-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I tried the gstreamer backend once. After a reboot i decided to switch back to the xine-backend. When I applied the settings in systemsettings, knotify crashed with the following backtrace.

 -- Backtrace:
Application: KNotify (knotify4), signal: Segmentation fault
[Current thread is 0 (LWP 5264)]

Thread 2 (Thread 0x7fa9c7951950 (LWP 5428)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007fa9c7ed494b in ?? () from /usr/lib/libjack.so.0
#2  0x00007fa9d1c613ba in start_thread (arg=<value optimized out>) at pthread_create.c:297
#3  0x00007fa9d391dfcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa9d6756750 (LWP 5264)):
[KCrash Handler]
#5  _register_plugins_internal (this=0x2037a00, file=0x1e969d0, info=0x1e515f0) at load_plugins.c:372
#6  0x00007fa9c38d1cf3 in collect_plugins (this=0x2037a00, path=<value optimized out>) at load_plugins.c:629
#7  0x00007fa9c38d20bb in _x_scan_plugins (this=0x2037a00) at load_plugins.c:1177
#8  0x00007fa9c38c534b in xine_init (this=0x2037a00) at xine.c:1709
#9  0x00007fa9c3b28617 in XineEngineData (this=0x1efcd10) at /build/buildd/phonon-4.3.1/xine/xineengine.cpp:58
#10 0x00007fa9c3b28a45 in Phonon::Xine::XineEngine::create (this=0x1d00448) at /build/buildd/phonon-4.3.1/xine/xineengine.cpp:83
#11 0x00007fa9c3b463b3 in Backend (this=0x1d00400, parent=<value optimized out>) at /build/buildd/phonon-4.3.1/xine/backend.cpp:77
#12 0x00007fa9c3b46aab in qt_plugin_instance () at /build/buildd/phonon-4.3.1/xine/backend.cpp:53
#13 0x00007fa9cbc7f35a in Phonon::KdePlatformPlugin::createBackend (this=<value optimized out>, newService={d = 0x7fffde790c40})
    at /build/buildd/kdebase-runtime-4.2.90/phonon/platform_kde/kdeplatformplugin.cpp:155
#14 0x00007fa9cbc8047d in Phonon::KdePlatformPlugin::createBackend (this=0x1d92690) at /build/buildd/kdebase-runtime-4.2.90/phonon/platform_kde/kdeplatformplugin.cpp:204
#15 0x00007fa9d5d53ecc in Phonon::FactoryPrivate::createBackend (this=0x1da75c0) at /build/buildd/phonon-4.3.1/phonon/factory.cpp:118
#16 0x00007fa9d5d555b8 in Phonon::FactoryPrivate::phononBackendChanged (this=0x1da75c0) at /build/buildd/phonon-4.3.1/phonon/factory.cpp:279
#17 0x00007fa9d5d55835 in Phonon::FactoryPrivate::qt_metacall (this=0x1da75c0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffde791320)
    at /build/buildd/phonon-4.3.1/obj-x86_64-linux-gnu/phonon/factory.moc:71
#18 0x00007fa9d565ef83 in QDBusConnectionPrivate::deliverCall (this=0x1c68ad0, object=0x1da75c0, msg=@0x237a598, metaTypes=@0x237a5a0, slotIdx=7) at qdbusintegrator.cpp:891
#19 0x00007fa9d5666d0f in QDBusCallDeliveryEvent::placeMetaCall (this=0x0, object=0x0) at qdbusintegrator_p.h:101
#20 0x00007fa9d5350848 in QObject::event (this=0x1da75c0, e=0x237a550) at kernel/qobject.cpp:1118
#21 0x00007fa9d452a78d in QApplicationPrivate::notify_helper (this=0x1c7a3f0, receiver=0x1da75c0, e=0x237a550) at kernel/qapplication.cpp:4084
#22 0x00007fa9d453297a in QApplication::notify (this=0x7fffde791d70, receiver=0x1da75c0, e=0x237a550) at kernel/qapplication.cpp:4049
#23 0x00007fa9d617c06b in KApplication::notify (this=0x7fffde791d70, receiver=0x1da75c0, event=0x237a550) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302
#24 0x00007fa9d534075c in QCoreApplication::notifyInternal (this=0x7fffde791d70, receiver=0x1da75c0, event=0x237a550) at kernel/qcoreapplication.cpp:602
#25 0x00007fa9d53413ca in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1c4eff0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#26 0x00007fa9d536a1e3 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#27 0x00007fa9d0a5920a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0x00007fa9d0a5c8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#29 0x00007fa9d0a5ca7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0x00007fa9d5369e6f in QEventDispatcherGlib::processEvents (this=0x1c4e800, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#31 0x00007fa9d45c2bef in QGuiEventDispatcherGlib::processEvents (this=0x1, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#32 0x00007fa9d533f002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -562488208}) at kernel/qeventloop.cpp:149
#33 0x00007fa9d533f3cd in QEventLoop::exec (this=0x7fffde791cb0, flags={i = -562488128}) at kernel/qeventloop.cpp:200
#34 0x00007fa9d5341694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#35 0x000000000040774b in main (argc=1, argv=0x7fffde7920f8) at /build/buildd/kdebase-runtime-4.2.90/knotify/main.cpp:73

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-11 21:55:29 UTC
I guess this is fixed already.. Have you experienced it again ? Can you reproduce ?
Thanks
Comment 2 Jonathan Thomas 2009-12-16 07:32:13 UTC
*** Bug 214409 has been marked as a duplicate of this bug. ***
Comment 3 Jonathan Thomas 2009-12-17 18:50:16 UTC
Looks like a crash inside xine-lib to me. Not much we can mess up telling xine to scan for plugins, I would think.
Comment 4 Christoph Feck 2010-01-04 21:28:06 UTC
*** Bug 221273 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2011-04-13 03:56:06 UTC
*** Bug 270690 has been marked as a duplicate of this bug. ***