I'm suffering from recurrent plasma-desktop crashes after upgrading to 4.11.1 on my openSUSE 12.2/x86_64 desktop system. I have a worldclock plasmoid attached on my desktop. While I also use the evil nvidia driver (G03-319), I think, this is a valid marble bug: Thread 1 (Thread 0x7f8028231780 (LWP 4594)): [KCrash Handler] #6 0x00007f80257d5d25 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007f80257d71a8 in __GI_abort () at abort.c:91 #8 0x00007f8025813fcb in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f80259056c0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:198 #9 0x00007f8025819b66 in malloc_printerr (action=3, str=0x7f80259057d0 "double free or corruption (!prev)", ptr=<optimized out>) at malloc.c:5007 #10 0x00007f80178a107c in ?? () from /usr/X11R6/lib64/libGL.so.1 #11 0x00007f80166dc17a in ?? () from /usr/lib64/tls/libnvidia-tls.so.319.32 #12 0x00007f8026da28ae in QThread::start (this=0xa2bcaa0, priority=<optimized out>) at thread/qthread_unix.cpp:658 #13 0x00007f8026d972bf in QThreadPoolPrivate::startThread (this=this@entry=0x328d750, runnable=runnable@entry=0x3e08780) at concurrent/qthreadpool.cpp:260 #14 0x00007f8026d974db in QThreadPoolPrivate::tryStart (this=0x328d750, task=0x3e08780) at concurrent/qthreadpool.cpp:178 #15 0x00007f8026d976d3 in QThreadPool::start (this=<optimized out>, runnable=0x3e08780, priority=0) at concurrent/qthreadpool.cpp:474 #16 0x00007f7ffd8bd45a in ?? () from /usr/lib64/libmarblewidget.so.16 #17 0x00007f7ffd8bd672 in ?? () from /usr/lib64/libmarblewidget.so.16 #18 0x00007f7ffd8154c3 in ?? () from /usr/lib64/libmarblewidget.so.16 #19 0x00007f7ffd88bd85 in ?? () from /usr/lib64/libmarblewidget.so.16 #20 0x00007f7ffd831bea in Marble::MarbleMap::paint(Marble::GeoPainter&, QRect const&) () from /usr/lib64/libmarblewidget.so.16 #21 0x00007f7ffdcd9d58 in ?? () from /usr/lib64/kde4/plasma_applet_worldclock.so #22 0x00007f801d647e1d in Plasma::Applet::paint (this=0x1f660b0, painter=0x7fff289a5ae0, option=0x1535a48, widget=0x0) at /usr/src/debug/kdelibs-4.11.1/plasma/applet.cpp:1466 #23 0x00007f802660b1e9 in _q_paintItem (item=item@entry=0x1f660c0, painter=painter@entry=0x7fff289a5ae0, option=option@entry=0x1535a48, widget=widget@entry=0x0, useWindowOpacity=useWindowOpacity@entry=false, painterStateProtection=painterStateProtection@entry=true) at graphicsview/qgraphicsscene.cpp:4335 #24 0x00007f802660b4e2 in _q_paintIntoCache (pix=pix@entry=0x7fff289a5dc0, item=item@entry=0x1f660c0, pixmapExposed=..., itemToPixmap=..., renderHints=..., option=option@entry=0x1535a48, painterStateProtection=painterStateProtection@entry=true) at graphicsview/qgraphicsscene.cpp:4373 Reproducible: Always Steps to Reproduce: 1. start KDE 2. work a bit 3. crashes sometime (no correlation to user activity noticable( Actual Results: SIGABRT Expected Results: no crashes, please Everybody thinks, his bug is grave, but plasma-desktop crashes due to Marble (I think) is a serious problem.
Created attachment 82289 [details] full crash log I have a couple of them, here's the latest and greatest..
Thanks for the report. Sadly it seems to never have been solved? The Plasma worldclock widget has been rewritten now in QML for Plasma5 (and lacking some of the old features still). The old code is no longer maintained, so closing this now. Please try the new widget and report any issues or features you would like to see (re-)implemented. See also https://frinring.wordpress.com/2016/08/04/wip-plasma-world-map-wallpaper-world-clock-applet-powered-by-marble/