Bug 156631 - plasma segfault, possibly when removing a desktop icon
Summary: plasma segfault, possibly when removing a desktop icon
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-25 09:18 UTC by Marcus Better
Modified: 2008-02-03 18:24 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 Marcus Better 2008-01-25 09:18:09 UTC
Version:            (using KDE 4.0.0)
Installed from:    Debian testing/unstable Packages

Plasma crashed shortly after startup. At that point some apps were starting, and I tried to delete an icon from the desktop using the "close" button that shows up when you hover over it.

It's possible that I also opened its properties page at the same time by accident.

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb62556c0 (LWP 3983)]
[New Thread 0xb2cfcb90 (LWP 3985)]
[New Thread 0xb3e0cb90 (LWP 3984)]
[KCrash handler]
#5  QGraphicsItemPrivate::setVisibleHelper (this=0x0, newVisible=false, 
    explicitly=true, update=true) at graphicsview/qgraphicsitem.cpp:1093
#6  0xb73754ac in QGraphicsItem::setVisible (this=0x8184178, 
    visible=<value optimized out>) at graphicsview/qgraphicsitem.cpp:1152
#7  0xb7d30ad4 in Plasma::Phase::timerEvent (this=0x813f9e8, event=0xbfe1ec78)
    at /usr/include/qt4/QtGui/qgraphicsitem.h:139
#8  0xb7c0ca64 in QObject::event (this=0x813f9e8, e=0xb4965200)
    at kernel/qobject.cpp:1095
#9  0xb6e8321d in QApplicationPrivate::notify_helper (this=0x8077ec0, 
    receiver=0x813f9e8, e=0xbfe1ec78) at kernel/qapplication.cpp:3556
#10 0xb6e86c77 in QApplication::notify (this=0x805ab68, receiver=0x813f9e8, 
    e=0xbfe1ec78) at kernel/qapplication.cpp:3115
#11 0xb7757cdd in KApplication::notify (this=0x805ab68, receiver=0x813f9e8, 
    event=0xbfe1ec78)
    at /build/buildd/kde4libs-4.0.0/kdeui/kernel/kapplication.cpp:314
#12 0xb7bfaffb in QCoreApplication::notifyInternal (this=0x805ab68, 
    receiver=0x813f9e8, event=0xbfe1ec78) at kernel/qcoreapplication.cpp:530
#13 0xb7c21f79 in QTimerInfoList::activateTimers (this=0x807acdc)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:200
#14 0xb7c1eaa0 in timerSourceDispatch (source=0x807aca8)
    at kernel/qeventdispatcher_glib.cpp:155
#15 0xb675a1c6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0xb675d552 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x0807a098 in ?? ()
#18 0x00000000 in ?? ()
#0  0xb7f34410 in __kernel_vsyscall ()
Comment 1 Marcus Better 2008-01-25 09:19:16 UTC
Oh, and I'm running Debian experimental 4.0.0 packages on i386.
Comment 2 Riccardo Iaconelli 2008-02-03 18:24:15 UTC
I'm sorry but this really looks like a compilation optimization that makes the code unstable.

The suspicious part is this:

#6  0xb73754ac in QGraphicsItem::setVisible (this=0x8184178,
    visible=<value optimized out>) at graphicsview/qgraphicsitem.cpp:1152 

Try to update your Qt packages. In case this happens again, please report the bug to Debian. =)

Just FYI, here, compiling from source, it doesn't crash.