Bug 161339 - plasma core dumps on startup and all that is shown is the crash handler and a grey screen
Summary: plasma core dumps on startup and all that is shown is the crash handler and a...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-27 18:44 UTC by James Pike
Modified: 2008-05-07 10:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description James Pike 2008-04-27 18:44:37 UTC 
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          g++ 4.2.3 
OS:                Linux

It's pretty much in the description, I compiled KDE from svn HEAD today (28th April). Here is the backtrace:

Application: Plasma Workspace (plasma), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb52368e0 (LWP 31683)]
[New Thread 0xb351fb90 (LWP 31685)]
[KCrash handler]
#6  0x00000010 in ?? ()
#7  0xb7dc80b7 in Plasma::Applet::flushPendingConstraintsEvents (
    this=0x81279d8)
    at /home/kde-devel/kde/src/KDE/kdebase/workspace/libs/plasma/applet.cpp:978
#8  0xb7dca260 in Plasma::Applet::qt_metacall (this=0x81279d8, 
    _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb2ee44)
    at /home/kde-devel/kde/build/KDE/kdebase/workspace/libs/plasma/applet.moc:113
#9  0xb354a5ee in DeviceNotifier::qt_metacall (this=0x81279d8, 
    _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbfb2ee44)
    at /home/kde-devel/kde/build/KDE/kdebase/workspace/plasma/applets/devicenotifier/devicenotifier.moc:79
#10 0xb64d9015 in QMetaObject::activate (sender=0x80e5130, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at /home/kde-devel/kde/src/qt-copy/src/corelib/kernel/qobject.cpp:3010
#11 0xb64d959f in QMetaObject::activate (sender=0x80e5130, m=0xb65cc8e8, 
    local_signal_index=0, argv=0x0)
    at /home/kde-devel/kde/src/qt-copy/src/corelib/kernel/qobject.cpp:3080
#12 0xb64e3cf5 in QSingleShotTimer::timeout (this=0x80e5130)
    at .moc/debug-shared/qtimer.moc:74
#13 0xb64e3e12 in QSingleShotTimer::timerEvent (this=0x80e5130)
    at /home/kde-devel/kde/src/qt-copy/src/corelib/kernel/qtimer.cpp:300
#14 0xb64d6c12 in QObject::event (this=0x80e5130, e=0xbfb2f434)
    at /home/kde-devel/kde/src/qt-copy/src/corelib/kernel/qobject.cpp:1105
#15 0xb5978a2d in QApplicationPrivate::notify_helper (this=0x8073f50, 
    receiver=0x80e5130, e=0xbfb2f434)
    at /home/kde-devel/kde/src/qt-copy/src/gui/kernel/qapplication.cpp:3766
#16 0xb5978d46 in QApplication::notify (this=0x8077d60, receiver=0x80e5130, 
    e=0xbfb2f434)
    at /home/kde-devel/kde/src/qt-copy/src/gui/kernel/qapplication.cpp:3360
#17 0xb6c05587 in KApplication::notify (this=0x8077d60, receiver=0x80e5130, 
    event=0xbfb2f434)
    at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:311
#18 0xb64c135d in QCoreApplication::notifyInternal (this=0x8077d60, 
    receiver=0x80e5130, event=0xbfb2f434)
    at /home/kde-devel/kde/src/qt-copy/src/corelib/kernel/qcoreapplication.cpp:587
#19 0xb7595723 in QCoreApplication::sendEvent (receiver=0x80e5130, 
    event=0xbfb2f434)
    at ../../../../include/QtCore/../../../../src/qt-copy/src/corelib/kernel/qcoreapplication.h:215
#20 0xb64f9eb3 in QTimerInfoList::activateTimers (this=0x8079734)
    at /home/kde-devel/kde/src/qt-copy/src/corelib/kernel/qeventdispatcher_unix.cpp:563
#21 0xb64f7684 in timerSourceDispatch (source=0x8079700)
    at /home/kde-devel/kde/src/qt-copy/src/corelib/kernel/qeventdispatcher_glib.cpp:166
#22 0xb5448ecb in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb544bf16 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x08078c20 in ?? ()
#25 0x00000000 in ?? ()
#0  0xb7ef1410 in __kernel_vsyscall ()
Comment 1 James Pike 2008-05-07 10:31:03 UTC 
This has gone away now.