SourceForge has been redesigned. Learn more.
Close

#66 kplayer crashed on logout

open
nobody
None
5
2008-09-16
2008-09-16
Regnaron
No

Not sure how helpful it is as I cannot reproduce this bug, but just in case...

I was watching an akademy video in kplayer-0.6.2 (KDE-3.5.9). Some time after the video had finished I restarted the computer without quitting kplayer. On shutdown (during logout), kplayer then crashed with the following backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x7f3d8c7e8700 (LWP 25154)]
[KCrash handler]
#5 KPlayerEngine::workspace (this=0x0) at kplayerengine.h:164
#6 0x0000000000477985 in KPlayer::resizeEvent (this=0x90ea90,
event=<value optimized out>) at kplayer.cpp:1723
#7 0x00007f3d8736e4a0 in QWidget::event (this=0x90ea90, e=0x7fff9481d660)
at kernel/qwidget.cpp:4788
#8 0x00007f3d8746897e in QMainWindow::event (this=0x90ea90, e=0x7fff9481d660)
at widgets/qmainwindow.cpp:1687
#9 0x00007f3d872af97f in QApplication::internalNotify (this=0x7fff9481def0,
receiver=0x90ea90, e=0x7fff9481d660) at kernel/qapplication.cpp:2635
#10 0x00007f3d872b26c5 in QApplication::notify (this=0x7fff9481def0,
receiver=0x90ea90, e=0x7fff9481d660) at kernel/qapplication.cpp:2523
#11 0x00007f3d87d7a76c in KApplication::notify (this=0x7fff9481def0,
receiver=0x90ea90, event=0x7fff9481d660) at kapplication.cpp:550
#12 0x000000000047de68 in KPlayerApplication::notify (this=0x7fff9481def0,
object=0x90ea90, event=0x7fff9481d660) at kplayer.cpp:338
#13 0x00007f3d8723142e in QApplication::sendSpontaneousEvent (
receiver=0x90ea90, event=0x7fff9481d660) at kernel/qapplication.h:499
#14 0x00007f3d8721cba2 in QETWidget::translateConfigEvent (this=0x90ea90,
event=0x7fff9481db90) at kernel/qapplication_x11.cpp:5736
#15 0x00007f3d8722e201 in QApplication::x11ProcessEvent (this=0x7fff9481def0,
event=0x7fff9481db90) at kernel/qapplication_x11.cpp:3502
#16 0x00007f3d872475a4 in QEventLoop::processEvents (this=0x83cbe0, flags=4)
at kernel/qeventloop_x11.cpp:192
#17 0x00007f3d872cf5e5 in QEventLoop::enterLoop (this=0x83cbe0)
at kernel/qeventloop.cpp:198
#18 0x00007f3d872cf3eb in QEventLoop::exec (this=0x83cbe0)
at kernel/qeventloop.cpp:145
#19 0x00007f3d872b17c4 in QApplication::exec (this=0x7fff9481def0)
at kernel/qapplication.cpp:2758
#20 0x000000000047fbb2 in main (argc=3, argv=<value optimized out>)
at main.cpp:47
#21 0x00007f3d85449486 in __libc_start_main (main=0x47fb00 <main>, argc=3,
ubp_av=0x7fff9481e1f8, init=0x52ede0 <__libc_csu_init>,
fini=<value optimized out>, rtld_fini=<value optimized out>,
stack_end=0x7fff9481e1e8) at libc-start.c:226
#22 0x000000000043c0a9 in _start ()
Current language: auto; currently c

Discussion

  • kiriuja

    kiriuja - 2008-09-17

    Please try version 0.6.3, it fixed a few bugs like this one.

    Let me know how it goes.

     
  • Regnaron

    Regnaron - 2008-09-21

    Hi and thanks for your response.

    However, as the the bug is not reproducible anyway, updating to a newer version wont really help. I mostly dumped it here as I had the debugging packages installed anyway and thought the backtrace might be interesting after all :). So, if you say that you fixed some of these bugs in 0.7, just close this report. If I should stumble upon something similar with a newer version again, I'll just comment on this one or file a new report.

     

Log in to post a comment.