Bug 297179 - Plasma Crash
Summary: Plasma Crash
Status: RESOLVED DUPLICATE of bug 286829
Alias: None
Product: plasma4
Classification: Unmaintained
Component: desktop (show other bugs)
Version: 4.6.5
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-31 13:00 UTC by TomG
Modified: 2012-06-22 09:13 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
plasma desktop kde crash (2.70 KB, application/octet-stream)
2012-03-31 13:00 UTC, TomG
Details

Note You need to log in before you can comment on or make changes to this bug.
Description TomG 2012-03-31 13:00:32 UTC
Created attachment 70037 [details]
plasma desktop kde crash

Actually this was the notice I received when I got up in the morning, my desktop was running in the evening. So, I am submitting it.
Comment 1 Jekyll Wu 2012-05-27 09:56:26 UTC
Pasting the backtrace inline for better searching


Application: plasma-desktop (0.4)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.3
Operating System: Linux 2.6.38.8-pclos1.bfs i686
Distribution: "PCLinuxOS"

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.6-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[KCrash Handler]
#7  0x468dc205 in QImageData::~QImageData() () from /usr/lib/libQtGui.so.4
#8  0x468dc339 in QImage::~QImage() () from /usr/lib/libQtGui.so.4
#9  0x4690c8e0 in QRasterPixmapData::~QRasterPixmapData() () from /usr/lib/libQtGui.so.4
#10 0x4690c932 in QRasterPixmapData::~QRasterPixmapData() () from /usr/lib/libQtGui.so.4
#11 0x468fb0b6 in QPixmap::~QPixmap() () from /usr/lib/libQtGui.so.4
#12 0x468ff5ca in ?? () from /usr/lib/libQtGui.so.4
#13 0x468ff622 in ?? () from /usr/lib/libQtGui.so.4
#14 0x4690200f in ?? () from /usr/lib/libQtGui.so.4
#15 0x468ff7f9 in ?? () from /usr/lib/libQtGui.so.4
#16 0x468ff968 in ?? () from /usr/lib/libQtGui.so.4
#17 0x43690054 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#18 0x4680fe44 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0x46814df7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#20 0x4420e881 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#21 0x4367a84e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#22 0x436abd9b in ?? () from /usr/lib/libQtCore.so.4
#23 0x436a8a32 in ?? () from /usr/lib/libQtCore.so.4
#24 0x43c27369 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0x43c27b70 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0x43c27e2a in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0x436a918b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x468c694a in ?? () from /usr/lib/libQtGui.so.4
#29 0x43679a5d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x43679cd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0x4367e7e0 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#32 0x4680dbc4 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#33 0x45c06e3b in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#34 0x080487bb in _start ()

Report to https://bugs.kde.org
Comment 2 Thijs 2012-06-22 09:13:27 UTC
Hard to tell for sure, but looks like bug 286829. If this can be triggered with a recent version of KDE (4.8.4 or later) and Qt (4.8.x or later), please report a full  backtrace, preferably including debug symbols.

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