Bug 137829 - Keeps crashing every now and then while running liquidweather
Summary: Keeps crashing every now and then while running liquidweather
Status: RESOLVED UNMAINTAINED
Alias: None
Product: superkaramba
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Ryan Nickell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-24 16:13 UTC by Florian Faber
Modified: 2018-09-04 20:26 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 Florian Faber 2006-11-24 16:13:54 UTC
Version:           0.41 (using KDE KDE 3.5.5)
Installed from:    Compiled From Sources
Compiler:          gcc (GCC) 4.1.1 (Gentoo 4.1.1-r2)
 CFLAGS="-O2 -march=k8 -pipe -ggdb"
OS:                Linux

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47231329958496 (LWP 21288)]
[KCrash handler]
#5  PyType_IsSubtype (a=<value optimized out>, b=0x5a7cd0)
    at Objects/typeobject.c:830
#6  0x00002af4e26a34cf in string_richcompare (a=0x2af4e6cf1030, 
    b=0x2af4e285b380, op=2) at Objects/stringobject.c:1066
#7  0x00002af4e269ee4b in PyObject_RichCompare (v=0x2af4e285b380, 
    w=0x2af4e6cf1030, op=2) at Objects/object.c:837
#8  0x00002af4e26d046e in PyEval_EvalFrame (f=0xa9f6e0) at Python/ceval.c:4009
#9  0x00002af4e26d090c in PyEval_EvalFrame (f=0xa9dbf0) at Python/ceval.c:3651
#10 0x00002af4e26d090c in PyEval_EvalFrame (f=0xb07f80) at Python/ceval.c:3651
#11 0x00002af4e26d090c in PyEval_EvalFrame (f=0xb045f0) at Python/ceval.c:3651
#12 0x00002af4e26d090c in PyEval_EvalFrame (f=0x9eb5d0) at Python/ceval.c:3651
#13 0x00002af4e26d29ac in PyEval_EvalCodeEx (co=0x2af4e7df7c70, 
    globals=<value optimized out>, locals=<value optimized out>, 
    args=0x2af4e6d40128, argcount=1, kws=0x0, kwcount=0, defs=0x0, 
    defcount=0, closure=0x0) at Python/ceval.c:2741
#14 0x00002af4e268d3c3 in function_call (func=0x2af4e767be60, 
    arg=0x2af4e6d40110, kw=0x0) at Objects/funcobject.c:548
#15 0x00002af4e26773b0 in PyObject_Call (func=0xb53560, arg=0x5a7cd0, kw=0x2)
    at Objects/abstract.c:1795
#16 0x00002af4e26cca2c in PyEval_CallObjectWithKeywords (func=0x2af4e767be60, 
    arg=0x2af4e6d40110, kw=0x0) at Python/ceval.c:3435
#17 0x0000000000470aee in KarambaPython::callObject (this=0x7f00c0, 
    func=0x48d20a "widgetUpdated", pArgs=0x2af4e6d40110, lock=true)
    at karamba_python.cpp:476
#18 0x00000000004710b5 in KarambaPython::widgetUpdated (this=0x7f00c0, 
    k=<value optimized out>) at karamba_python.cpp:504
#19 0x000000000043bbb8 in karamba::step (this=0x8a8540) at karamba.cpp:1658
#20 0x0000000000448357 in karamba::qt_invoke (this=0x8a8540, _id=45, 
    _o=0x7fffc8583620) at karamba.moc:212
#21 0x00002af4e43479ac in QObject::activate_signal (this=0xa0a310, 
    clist=<value optimized out>, o=0x7fffc8583620) at kernel/qobject.cpp:2356
#22 0x00002af4e4348653 in QObject::activate_signal (this=0xb53560, 
    signal=<value optimized out>) at kernel/qobject.cpp:2325
#23 0x00002af4e4366c35 in QTimer::event (this=0xa0a310, e=0x5a7cd0)
    at kernel/qtimer.cpp:219
#24 0x00002af4e42f1825 in QApplication::internalNotify (
    this=<value optimized out>, receiver=0xa0a310, e=0x7fffc85838c0)
    at kernel/qapplication.cpp:2635
#25 0x00002af4e42f2427 in QApplication::notify (this=0x7fffc8583b40, 
    receiver=0xa0a310, e=0x7fffc85838c0) at kernel/qapplication.cpp:2358
#26 0x00002af4e372bd2f in KApplication::notify (this=0x7fffc8583b40, 
    receiver=0xa0a310, event=0x7fffc85838c0) at kapplication.cpp:550
#27 0x00002af4e42e7f62 in QEventLoop::activateTimers (
    this=<value optimized out>) at kernel/qapplication.h:496
#28 0x00002af4e42a8ec2 in QEventLoop::processEvents (this=0x5eddf0, flags=0)
    at kernel/qeventloop_x11.cpp:389
#29 0x00002af4e4306002 in QEventLoop::enterLoop (this=0xb53560)
    at kernel/qeventloop.cpp:198
#30 0x00002af4e4305eb2 in QEventLoop::exec (this=0xb53560)
    at kernel/qeventloop.cpp:145
#31 0x000000000043ac1a in main (argc=<value optimized out>, 
    argv=<value optimized out>) at main.cpp:153
Current language:  auto; currently c
Comment 1 Olivier Vitrat 2007-11-03 23:17:43 UTC
Also reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448337
see backtrace:


Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb7e686c0 (LWP 5846)]
[New Thread 0xb5feeb90 (LWP 27261)]
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x4ec6e65e in sem_wait@GLIBC_2.0 () from /lib/i686/cmov/libpthread.so.0
#2  0x494a87de in PyThread_acquire_lock (lock=<value optimized out>, 
    waitflag=<value optimized out>) at ../Python/thread_pthread.h:313
#3  0x49478758 in PyEval_AcquireLock () at ../Python/ceval.c:228
#4  0x080b7eff in KarambaPython::getLock (this=0x82f0bf8, 
    myThreadState=0xbfe7f848)
    at /tmp/buildd/kdeutils-3.5.7/./superkaramba/src/karamba_python.cpp:440
#5  0x080b7fc2 in KarambaPython::callObject (this=0x82f0bf8, 
    func=0x80d2366 "widgetUpdated", pArgs=0xb751b44c, lock=true)
    at /tmp/buildd/kdeutils-3.5.7/./superkaramba/src/karamba_python.cpp:475
#6  0x080b86d8 in KarambaPython::widgetUpdated (this=0x82f0bf8, k=0x82cf190)
    at /tmp/buildd/kdeutils-3.5.7/./superkaramba/src/karamba_python.cpp:508
#7  0x0807e42c in karamba::step (this=0x82cf190)
    at /tmp/buildd/kdeutils-3.5.7/./superkaramba/src/karamba.cpp:1697
#8  0x08087662 in karamba::qt_invoke (this=0x82cf190, _id=46, _o=0xbfe7f9dc)
    at ./karamba.moc:217
#9  0x41e97b10 in QObject::activate_signal (this=) at kernel/qobject.cpp:2356
#10 0x41e985f5 in QObject::activate_signal (this=) at kernel/qobject.cpp:2325
#11 0x42229b94 in QTimer::timeout (this=)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#12 0x41ebf282 in QTimer::event (this=) at kernel/qtimer.cpp:219
#13 0x41e2c36a in QApplication::internalNotify (this=)
    at kernel/qapplication.cpp:2635
#14 0x41e2e193 in QApplication::notify (this=) at kernel/qapplication.cpp:2358
#15 0x4faca192 in KApplication::notify (this=<value optimized out>, 
    receiver=<value optimized out>, event=<value optimized out>)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550
#16 0x41dbd6c9 in QApplication::sendEvent (receiver=)
    at ../include/qapplication.h:520
#17 0x41e1f1b1 in QEventLoop::activateTimers (this=)
    at kernel/qeventloop_unix.cpp:556
#18 0x41dd219a in QEventLoop::processEvents (this=)
    at kernel/qeventloop_x11.cpp:389
#19 0x41e476e4 in QEventLoop::enterLoop (this=) at kernel/qeventloop.cpp:198
#20 0x41e473e2 in QEventLoop::exec (this=) at kernel/qeventloop.cpp:145
#21 0x41e2df13 in QApplication::exec (this=) at kernel/qapplication.cpp:2758
#22 0x0807d238 in main (argc=)
    at /tmp/buildd/kdeutils-3.5.7/./superkaramba/src/main.cpp:153
Comment 2 Christoph Feck 2011-12-20 02:58:18 UTC
This crash report is at least 4 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4.

If the crash still happens with a recent KDE version (4.7.4 or 4.8), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or NEW)
Comment 3 Andrew Crouthamel 2018-09-04 20:26:31 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug.