Bug 290465 - Plasma crashes randomly
Summary: Plasma crashes randomly
Status: RESOLVED DUPLICATE of bug 287387
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: 2012-01-03 03:53 UTC by gerardocb
Modified: 2012-01-03 15:40 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 gerardocb 2012-01-03 03:53:54 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-tuxonice x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
Using Kubuntu 11.10.

This time it happened after opening an attachment on Thunderbird. It opened with okular, but sometimes it has happened with nothing special that I can remember. I've modified my panels layout and added some extra widgets (like a nagios monitor), but it happened before too.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f867b1877a0 (LWP 10470))]

Thread 4 (Thread 0x7f865ad30700 (LWP 10471)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f865ad2fad0 in ?? ()
#2  0x00007fff001ff7e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0x7f864a66f700 (LWP 10510)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f864a66ead0 in ?? ()
#2  0x00007fff001ff7e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0x7f8647c44700 (LWP 10512)):
#0  pthread_mutex_lock (mutex=0x33ea498) at forward.c:182
#1  0x00007f866eff94ca in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f866eff9f82 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f866effa792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f8648722516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x00007f866f01f2b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f866fb06efc in start_thread (arg=0x7f8647c44700) at pthread_create.c:304
#7  0x00007f867aa7b89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f867b1877a0 (LWP 10470)):
[KCrash Handler]
#6  QGraphicsLayoutItem::setParentLayoutItem (this=0x3229af0, parent=0x0) at graphicsview/qgraphicslayoutitem.cpp:856
#7  0x00007f867759bbd4 in QGraphicsGridLayout::removeAt (this=0x244a720, index=<optimized out>) at graphicsview/qgraphicsgridlayout.cpp:583
#8  0x00007f865bc13bb3 in SystemTray::TaskArea::relayoutHiddenTasks (this=0x244cb40) at ../../../../../plasma/generic/applets/systemtray/ui/taskarea.cpp:422
#9  0x00007f865bc140cc in SystemTray::TaskArea::qt_metacall (this=0x244cb40, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff00159bd0) at ./taskarea.moc:93
#10 0x00007f8677c48eba in QMetaObject::activate (sender=0x244c780, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#11 0x00007f8677c4c789 in QObject::event (this=0x244c780, e=<optimized out>) at kernel/qobject.cpp:1181
#12 0x00007f8676fe6424 in notify_helper (e=0x7fff0015a130, receiver=0x244c780, this=0x16b9cb0) at kernel/qapplication.cpp:4486
#13 QApplicationPrivate::notify_helper (this=0x16b9cb0, receiver=0x244c780, e=0x7fff0015a130) at kernel/qapplication.cpp:4458
#14 0x00007f8676feb291 in QApplication::notify (this=0x169bcf0, receiver=0x244c780, e=0x7fff0015a130) at kernel/qapplication.cpp:4365
#15 0x00007f86788e4126 in KApplication::notify (this=0x169bcf0, receiver=0x244c780, event=0x7fff0015a130) at ../../kdeui/kernel/kapplication.cpp:311
#16 0x00007f8677c35afc in QCoreApplication::notifyInternal (this=0x169bcf0, receiver=0x244c780, event=0x7fff0015a130) at kernel/qcoreapplication.cpp:787
#17 0x00007f8677c62d62 in sendEvent (event=0x7fff0015a130, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#18 QTimerInfoList::activateTimers (this=0x16c7e90) at kernel/qeventdispatcher_unix.cpp:603
#19 0x00007f8677c60514 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#20 0x00007f866eff9a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f866effa258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f866effa429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f8677c60ed6 in QEventDispatcherGlib::processEvents (this=0x1648f40, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#24 0x00007f867708e07e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007f8677c34cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f8677c34ef7 in QEventLoop::exec (this=0x7fff0015a3c0, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007f8677c39789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#28 0x00007f867ad7a1a3 in kdemain (argc=1, argv=0x7fff0015a7a8) at ../../../../plasma/desktop/shell/main.cpp:120
#29 0x00007f867a9bb30d in __libc_start_main (main=0x400640 <main(int, char**)>, argc=1, ubp_av=0x7fff0015a7a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff0015a798) at libc-start.c:226
#30 0x0000000000400671 in _start ()

Possible duplicates by query: bug 289385, bug 288804, bug 288096, bug 287387, bug 285813.

Reported using DrKonqi
Comment 1 Thijs 2012-01-03 08:03:55 UTC

*** This bug has been marked as a duplicate of bug 287387 ***
Comment 2 gerardocb 2012-01-03 15:29:32 UTC
I don't get it. Bug 287387 says "- Error after active compiz and restart session". I'm not even using compiz. I'm using only kwin.

Is this report duplicated from 287387 because of the backtrace?
Comment 3 Thijs 2012-01-03 15:40:10 UTC
Indeed, the backtrace. If you look at both threads 1, they are very similar, with #8 as giveaway. The third duplicate of this bug had nothing to do with compiz or okular, but it still provided another path to the same crash. Thanks for posting!