Bug 181805 - plasma crashes on startup
Summary: plasma crashes on startup
Status: RESOLVED DUPLICATE of bug 179909
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-24 20:57 UTC by Federico
Modified: 2009-01-25 00:34 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 Federico 2009-01-24 20:57:03 UTC
Version:            (using KDE 4.1.96)
Compiler:          gcc 
OS:                Linux
Installed from:    SuSE RPMs

Im using opensuse 11.1, i added the factory repos and then update to kde 4.2 RC.
Now on startup after login, plasma crashes.

This is the backtrace:

Aplicación: Área de trabajo de Plasma (plasma), señal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
0x00007fa85ae51cb0 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fa8606c1790 (LWP 4482))]

Thread 1 (Thread 0x7fa8606c1790 (LWP 4482)):
[KCrash Handler]
#5  Plasma::ToolBox::setIsMovable (this=0x0, movable=false) at /usr/src/debug/kdelibs-4.1.96/plasma/private/toolbox.cpp:325
#6  0x00007fa860046b24 in Plasma::ContainmentPrivate::containmentConstraintsEvent (this=0x980d10, constraints={i = 1753225520}) at /usr/src/debug/kdelibs-4.1.96/plasma/containment.cpp:1603
#7  0x00007fa86003ab52 in Plasma::Applet::flushPendingConstraintsEvents (this=0x8d2570) at /usr/src/debug/kdelibs-4.1.96/plasma/applet.cpp:984
#8  0x00007fa86003b365 in Plasma::Applet::timerEvent (this=0x8d2570, event=<value optimized out>) at /usr/src/debug/kdelibs-4.1.96/plasma/applet.cpp:1722
#9  0x00007fa85bbf4da3 in QObject::event (this=0x8d2570, e=0x0) at kernel/qobject.cpp:1120
#10 0x00007fa85c82628b in QGraphicsWidget::event (this=0x8d2570, event=0x7fff68802150) at graphicsview/qgraphicswidget.cpp:1239
#11 0x00007fa85c2cc1bd in QApplicationPrivate::notify_helper (this=0x6497c0, receiver=0x8d2570, e=0x7fff68802150) at kernel/qapplication.cpp:3803
#12 0x00007fa85c2d3f8a in QApplication::notify (this=0x634fc0, receiver=0x8d2570, e=0x7fff68802150) at kernel/qapplication.cpp:3768
#13 0x00007fa85eac6afb in KApplication::notify (this=0x634fc0, receiver=0x8d2570, event=0x7fff68802150) at /usr/src/debug/kdelibs-4.1.96/kdeui/kernel/kapplication.cpp:307
#14 0x00007fa85bbe6091 in QCoreApplication::notifyInternal (this=0x634fc0, receiver=0x8d2570, event=0x7fff68802150) at kernel/qcoreapplication.cpp:587
#15 0x00007fa85bc121c0 in QTimerInfoList::activateTimers (this=0x64cdb0) at kernel/qcoreapplication.h:209
#16 0x00007fa85bc0e58d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:160
#17 0x00007fa8582920db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#18 0x00007fa8582958ad in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fa858295a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fa85bc0e4ef in QEventDispatcherGlib::processEvents (this=0x646110, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319
#21 0x00007fa85c35c9af in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198
#22 0x00007fa85bbe49a2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1753228400}) at kernel/qeventloop.cpp:143
#23 0x00007fa85bbe4b2d in QEventLoop::exec (this=0x7fff688024b0, flags={i = 1753228480}) at kernel/qeventloop.cpp:194
#24 0x00007fa85bbe6ffd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#25 0x00007fa8603aae7b in kdemain (argc=1, argv=0x7fff688027b8) at /usr/src/debug/kdebase-workspace-4.1.96/plasma/shells/desktop/main.cpp:54
#26 0x00007fa85adce586 in __libc_start_main () from /lib64/libc.so.6
#27 0x0000000000400819 in _start () at ../sysdeps/x86_64/elf/start.S:113
Comment 1 Dario Andres 2009-01-25 00:34:38 UTC
This should be fixed in 4.2final :)

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