Bug 290178 - Plasma crashed after sending a mail with thunderbird 8.0 with an attachment droped from dolphin
Summary: Plasma crashed after sending a mail with thunderbird 8.0 with an attachment d...
Status: RESOLVED DUPLICATE of bug 272495
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-30 13:41 UTC by philx71sl
Modified: 2011-12-30 14:06 UTC (History)
1 user (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 philx71sl 2011-12-30 13:41:19 UTC
Application: plasma-desktop (0.4)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-14-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
write a mail.
copy a big directory with dolphin
add an icon in dolphin toolbar
drop a pdf inside the writing mail from the previous directory
send the mail

-- Backtrace:
Application: Outil de gestion de fenêtres Plasma (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f5d082727c0 (LWP 1603))]

Thread 3 (Thread 0x7f5ce4ca2700 (LWP 1604)):
#0  0x00007f5cfcce3034 in __pthread_mutex_lock (mutex=0x1533ae8) at pthread_mutex_lock.c:61
#1  0x00007f5cfc1d2649 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f5cfc1d3d81 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f5cfc1d4429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f5d04e3af3e in QEventDispatcherGlib::processEvents (this=0x14e4090, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#5  0x00007f5d04e0ecf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f5d04e0eef7 in QEventLoop::exec (this=0x7f5ce4ca1d90, flags=...) at kernel/qeventloop.cpp:201
#7  0x00007f5d04d2627f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#8  0x00007f5d04df1cbf in QInotifyFileSystemWatcherEngine::run (this=0x14d4720) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007f5d04d28d05 in QThreadPrivate::start (arg=0x14d4720) at thread/qthread_unix.cpp:331
#10 0x00007f5cfcce0efc in start_thread (arg=0x7f5ce4ca2700) at pthread_create.c:304
#11 0x00007f5d07c5589d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f5ce22d6700 (LWP 1608)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f5ce22d5ab0 in ?? ()
#2  0x00007f5d083b97e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f5d082727c0 (LWP 1603)):
[KCrash Handler]
#6  isNull (this=0x6) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:568
#7  operator! (this=0x6) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:574
#8  TaskManager::TaskItem::task (this=0x2d5d590) at ../../../libs/taskmanager/taskitem.cpp:113
#9  0x00007f5cee1b8112 in WindowTaskItem::publishIconGeometry (this=0x34122e0) at ../../../../../plasma/desktop/applets/tasks/windowtaskitem.cpp:120
#10 0x00007f5cee1c6b7c in AbstractTaskItem::timerEvent (this=0x34122e0, event=<optimized out>) at ../../../../../plasma/desktop/applets/tasks/abstracttaskitem.cpp:439
#11 0x00007f5d04e26789 in QObject::event (this=0x34122e0, e=<optimized out>) at kernel/qobject.cpp:1181
#12 0x00007f5d047de89b in QGraphicsWidget::event (this=0x34122e0, event=0x7fff62ffda00) at graphicsview/qgraphicswidget.cpp:1455
#13 0x00007f5d041c0424 in notify_helper (e=0x7fff62ffda00, receiver=0x34122e0, this=0xb60b00) at kernel/qapplication.cpp:4486
#14 QApplicationPrivate::notify_helper (this=0xb60b00, receiver=0x34122e0, e=0x7fff62ffda00) at kernel/qapplication.cpp:4458
#15 0x00007f5d041c5291 in QApplication::notify (this=0xb51630, receiver=0x34122e0, e=0x7fff62ffda00) at kernel/qapplication.cpp:4365
#16 0x00007f5d05abe126 in KApplication::notify (this=0xb51630, receiver=0x34122e0, event=0x7fff62ffda00) at ../../kdeui/kernel/kapplication.cpp:311
#17 0x00007f5d04e0fafc in QCoreApplication::notifyInternal (this=0xb51630, receiver=0x34122e0, event=0x7fff62ffda00) at kernel/qcoreapplication.cpp:787
#18 0x00007f5d04e3cd62 in sendEvent (event=0x7fff62ffda00, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0xb64e40) at kernel/qeventdispatcher_unix.cpp:603
#20 0x00007f5d04e3a514 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 0x00007f5cfc1d3a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f5cfc1d4258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f5cfc1d4429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f5d04e3aed6 in QEventDispatcherGlib::processEvents (this=0xae7f40, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#25 0x00007f5d0426807e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f5d04e0ecf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x00007f5d04e0eef7 in QEventLoop::exec (this=0x7fff62ffdc90, flags=...) at kernel/qeventloop.cpp:201
#28 0x00007f5d04e13789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#29 0x00007f5d07f541a3 in kdemain (argc=1, argv=0x7fff62ffe078) at ../../../../plasma/desktop/shell/main.cpp:120
#30 0x00007f5d07b9530d in __libc_start_main (main=0x400640 <main(int, char**)>, argc=1, ubp_av=0x7fff62ffe078, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff62ffe068) at libc-start.c:226
#31 0x0000000000400671 in _start ()

Possible duplicates by query: bug 290165, bug 290152, bug 290148, bug 290147, bug 290129.

Reported using DrKonqi
Comment 1 Jekyll Wu 2011-12-30 14:06:26 UTC

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