Bug 191701 - plasma crashed when launching new mp3 via dolphin while another instance of dragon was already running
Summary: plasma crashed when launching new mp3 via dolphin while another instance of d...
Status: RESOLVED DUPLICATE of bug 191412
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-taskbar (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-05 17:38 UTC by Maxim Mueller
Modified: 2009-05-05 17:46 UTC (History)
0 users

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 Maxim Mueller 2009-05-05 17:38:09 UTC
Title: dragon crashed when launching new mp3 via dolphin while another instance of dragon was already running

What I was doing when the application crashed:
running fedora rawhide + git xorg stack which might have contributed to the problem

 -- Application and System information:
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.71 (KDE 4.2.71 (KDE 4.3 >= 20090428))
Qt Version: 4.5.0
Operating System: Linux 2.6.30-rc3 x86_64
Distribution: "Fedora release 10.93 (Leonidas)"

 -- Backtrace:
Application: Plasma-Arbeitsfläche (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f33fa648820 (LWP 2498))]

Thread 2 (Thread 0x7f33e3822910 (LWP 2499)):
#0  0x000000392f80b3b9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x000000393905b2db in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x000000393b282edc in ?? () from /usr/lib64/libQtNetwork.so.4
#3  0x000000393905a221 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x000000392f80687a in start_thread () from /lib64/libpthread.so.0
#5  0x000000392ece04cd in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f33fa648820 (LWP 2498)):
[KCrash Handler]
#5  0x00007f33e5bd8700 in TaskManager::Task::window() const () from /usr/lib64/libtaskmanager.so.4
#6  0x00007f33e59a4301 in AbstractTaskItem::timerEvent(QTimerEvent*) () from /usr/lib64/kde4/plasma_applet_tasks.so
#7  0x0000003939152353 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#8  0x000000393bd91f4b in QGraphicsWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#9  0x000000393b78deac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#10 0x000000393b7954de in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#11 0x00007f33fbadf248 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#12 0x0000003939142b7c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#13 0x000000393916e562 in ?? () from /usr/lib64/libQtCore.so.4
#14 0x000000393916c05d in ?? () from /usr/lib64/libQtCore.so.4
#15 0x000000393083818e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#16 0x000000393083b8e8 in ?? () from /lib64/libglib-2.0.so.0
#17 0x000000393083ba5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#18 0x000000393916bfa6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#19 0x000000393b8220de in ?? () from /usr/lib64/libQtGui.so.4
#20 0x0000003939141452 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#21 0x0000003939141824 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#22 0x0000003939143919 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#23 0x00007f33fcf6068f in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so
#24 0x000000392ec1e9dd in __libc_start_main () from /lib64/libc.so.6
#25 0x00000000004007a9 in _start ()
Comment 1 Pino Toscano 2009-05-05 17:46:27 UTC
That's not a dragonplayer crash, but a (known) Plasma one.

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