Version: (using KDE Devel) Installed from: Compiled sources OS: Linux Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1248352544 (LWP 5846)] [New Thread -1275462768 (LWP 5847)] [KCrash handler] #6 0xb6cba96a in QPaintEngineState::painter () from /usr/lib/libQtGui.so.4 #7 0xb6cbea58 in ?? () from /usr/lib/libQtGui.so.4 #8 0xec815356 in ?? () #9 0xb360c4d0 in ?? () from /opt/kde4/lib/kde4/amarok_containment_context.so #10 0xb7f4fff4 in ?? () from /lib/ld-linux.so.2 #11 0x01604f08 in ?? () #12 0x53e58955 in ?? () #13 0xbfae4650 in ?? () #14 0xbfae4638 in ?? () #15 0xb6cba54e in QPainter::isActive () from /usr/lib/libQtGui.so.4 #16 0xb6cbfaa1 in QPainter::save () from /usr/lib/libQtGui.so.4 #17 0xb36091a2 in Context::ColumnApplet::paintInterface () from /opt/kde4/lib/kde4/amarok_containment_context.so #18 0xb7e5450b in Plasma::Applet::flushUpdatedConstraints () from /opt/kde4/lib/libplasma.so.1 #19 0xb7e562b9 in Plasma::Applet::qt_metacall () from /opt/kde4/lib/libplasma.so.1 #20 0xb7e7698a in Plasma::Containment::qt_metacall () from /opt/kde4/lib/libplasma.so.1 #21 0xb3287502 in Context::Containment::qt_metacall () from /opt/kde4/lib/libamaroklib.so.1 #22 0xb360a71a in Context::ColumnApplet::qt_metacall () from /opt/kde4/lib/kde4/amarok_containment_context.so #23 0xb73f8c04 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0xb73f9079 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #25 0xb7403e45 in ?? () from /usr/lib/libQtCore.so.4 #26 0x0815fc70 in ?? () #27 0xb746b968 in ?? () from /usr/lib/libQtCore.so.4 #28 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall ()
There's a lot of debug info missing from the traceback, but this seems to be in amarok. Can you explain what you were doing when this happened, please? Does "plasma crash on start" refer to "start"ing plasma (aka logging in)?
yes, when i log in in kde4 plasma crash. Perhaps the problem is amarok2, the my is oldest svn-version of amarok2.
Try recompiling amarok2 first then. There have been some binary incompatible changes in plasma recently that cause crashes in the paint routines (for some wierd reason), which is also where your crash appears to be happening.
ok, I am recompiling amarok2, now is all ok! Mark this bug RESOLVED