Bug 244166

Summary: Kaffeine (DVB-T) crashes on exit after lifeview
Product: [Applications] kaffeine Reporter: Rupert Weber <rpwh>
Component: generalAssignee: Christoph Pfister <christophpfister>
Status: RESOLVED DUPLICATE    
Severity: crash CC: adaptee
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Rupert Weber 2010-07-10 23:10:57 UTC
Application: kaffeine (1.0-svn3)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-23-generic x86_64
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
After using timeshift for a longish (gut feeling: ~1 hour) time, Kaffeine will crash when I close it. 
I don't think it's a duplicate of the two bugs found by this assistant, as I don't have crashes in the situations described there.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: Kaffeine (kaffeine), signal: Segmentation fault
[KCrash Handler]
#5  0x00000180ffffffff in ?? ()
#6  0x0000000000477ccb in DvbLiveView::osdTimeout (this=0x1f1f3b0) at /build/buildd/kaffeine-1.0~pre3/src/dvb/dvbliveview.cpp:393
#7  0x000000000042244c in DvbLiveView::qt_metacall (this=0x1f1f3b0, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fff63066c00)
    at /build/buildd/kaffeine-1.0~pre3/obj-x86_64-linux-gnu/src/moc_dvbliveview.cpp:97
#8  0x00007ffeb1933e3f in QMetaObject::activate (sender=0x1f1f418, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff63066c00) at kernel/qobject.cpp:3293
#9  0x00007ffeb1930a63 in QObject::event (this=0x1f1f418, e=0x7fff63067350) at kernel/qobject.cpp:1212
#10 0x00007ffeb0abd22c in QApplicationPrivate::notify_helper (this=0x1be6be0, receiver=0x1f1f418, e=0x7fff63067350) at kernel/qapplication.cpp:4300
#11 0x00007ffeb0ac36fb in QApplication::notify (this=0x7fff630676a0, receiver=0x1f1f418, e=0x7fff63067350) at kernel/qapplication.cpp:4183
#12 0x00007ffeb27dd526 in KApplication::notify (this=0x7fff630676a0, receiver=0x1f1f418, event=0x7fff63067350) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007ffeb192106c in QCoreApplication::notifyInternal (this=0x7fff630676a0, receiver=0x1f1f418, event=0x7fff63067350) at kernel/qcoreapplication.cpp:704
#14 0x00007ffeb194dd42 in QCoreApplication::sendEvent (this=0x1bea2a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QTimerInfoList::activateTimers (this=0x1bea2a0) at kernel/qeventdispatcher_unix.cpp:603
#16 0x00007ffeb194a824 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#17 0x00007ffead6b18c2 in g_main_dispatch (context=0x1be9520) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:1960
#18 IA__g_main_context_dispatch (context=0x1be9520) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2513
#19 0x00007ffead6b5748 in g_main_context_iterate (context=0x1be9520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2591
#20 0x00007ffead6b58fc in IA__g_main_context_iteration (context=0x1be9520, may_block=1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2654
#21 0x00007ffeb194a513 in QEventDispatcherGlib::processEvents (this=0x1bbafd0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#22 0x00007ffeb0b6d46e in QGuiEventDispatcherGlib::processEvents (this=0x1e96730, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007ffeb191f992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007ffeb191fd6c in QEventLoop::exec (this=0x7fff630675f0, flags=) at kernel/qeventloop.cpp:201
#25 0x00007ffeb1923aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#26 0x0000000000439a70 in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kaffeine-1.0~pre3/src/main.cpp:91

Possible duplicates by query: bug 240499, bug 233835.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-05-30 19:35:10 UTC

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