Version: 0.0 (using 4.00.80 (KDE 4.0.80 >= 20080104), compiled sources) Compiler: gcc OS: Linux (i686) release 2.6.22-3-k7 Plasma crash at KDE4 startup since todays SVN update. Backtrace : Application: Espace de travail Plasma (plasma), signal SIGSEGV Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb59f16e0 (LWP 12606)] [New Thread 0xb33d9b90 (LWP 12607)] [KCrash handler] #6 0xb716146c in QGraphicsSceneContextMenuEvent::scenePos () from /usr/lib/libQtGui.so.4 #7 0xb7efc50f in Plasma::Containment::contextMenuEvent (this=0x81e9880, event=0xbfdea0dc) at /home/loacoon/Documents/Downloads/SVN/KDE4/KDE/kdebase/workspace/libs/plasma/containment.cpp:210 #8 0xb7f3abeb in Plasma::Widget::contextMenuEvent (this=0x81f9010, event=0xbfdea0dc) at /home/loacoon/Documents/Downloads/SVN/KDE4/KDE/kdebase/workspace/libs/plasma/widgets/widget.cpp:598 #9 0xb7f3a8cf in Plasma::Widget::paint (this=0x81f9010, painter=0xbfdeaf50, option=0x83abcb8, widget=0x83a47a8) at /home/loacoon/Documents/Downloads/SVN/KDE4/KDE/kdebase/workspace/libs/plasma/widgets/widget.cpp:491 #10 0xb7154707 in QGraphicsScene::drawItems () from /usr/lib/libQtGui.so.4 #11 0xb7162cbc in QGraphicsView::drawItems () from /usr/lib/libQtGui.so.4 #12 0xb7169937 in QGraphicsView::paintEvent () from /usr/lib/libQtGui.so.4 #13 0xb6c9ce3d in QWidget::event () from /usr/lib/libQtGui.so.4 #14 0xb6f95163 in QFrame::event () from /usr/lib/libQtGui.so.4 #15 0xb701b18f in QAbstractScrollArea::viewportEvent () from /usr/lib/libQtGui.so.4 #16 0xb716be32 in QGraphicsView::viewportEvent () from /usr/lib/libQtGui.so.4 #17 0xb701c385 in ?? () from /usr/lib/libQtGui.so.4 #18 0x0824a328 in ?? () #19 0xbfdeb474 in ?? () #20 0xbfdeb128 in ?? () #21 0xb6c531d2 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 Backtrace stopped: frame did not save the PC #0 0xffffe410 in __kernel_vsyscall ()
binary incompatible changes in libplasma; you need to rebuild all applets/containments.
Okay, but shouldn't you add a security for those cases, to avoid Plasma to completely crash as soon as a plugin is incompatible?
Not really. If you are building a development version from source, it's something you should be aware of. If you are using packages, then it's up to the packaging system to keep everything sane. The ABI will be stable for 4.0 and for 4.1+ (although it will change between the two), so 4.0 applets should work for all of 4.0, and 4.1 applets should work for all of 4.1 (and probably for all of 4.2, 4.3 etc.). Given that stability in the released versions, it's not really worth adding version checks.
... not to mention this is precisely why we're offering scripting options for random add-ons.