Bug 249220 - knotify crash adjusting time
Summary: knotify crash adjusting time
Status: RESOLVED DUPLICATE of bug 226721
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: knotify (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Olivier Goffart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-27 13:57 UTC by oneforall
Modified: 2010-08-27 17:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description oneforall 2010-08-27 13:57:06 UTC 
Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

this is another one when changing the time , after its changed the knotify crash popup happens.

Reproducible: Always

Steps to Reproduce:
same as above


Expected Results:  
no popup/crash
Comment 1 Pino Toscano 2010-08-27 13:59:12 UTC 
Please add the backtrace of the crash.
Comment 2 oneforall 2010-08-27 14:04:33 UTC 
thats was quick ;)
Application: KNotify (knotify4), signal: Segmentation fault
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2305.0-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[KCrash Handler]
#6  0x00007fc48ce84210 in QVariant::userType() const () from /usr/lib64/qt/lib64/libQtCore.so.4
#7  0x00007fc48d1a0f7c in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#8  0x00007fc48d1a1ca7 in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#9  0x00007fc48d1a6aa9 in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#10 0x00007fc48d1a6d0b in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#11 0x00007fc48d1a70fe in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#12 0x00007fc48d1aab3a in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#13 0x00007fc486259a86 in dbus_connection_dispatch () from /usr/lib64/libdbus-1.so.3
#14 0x00007fc48d19d4b5 in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#15 0x00007fc48d1a1e05 in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#16 0x00007fc48d1e24a3 in ?? () from /usr/lib64/qt/lib64/libQtDBus.so.4
#17 0x00007fc48ce7ccbf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt/lib64/libQtCore.so.4
#18 0x00007fc48cec291e in QSocketNotifier::activated(int) () from /usr/lib64/qt/lib64/libQtCore.so.4
#19 0x00007fc48ce8189b in QSocketNotifier::event(QEvent*) () from /usr/lib64/qt/lib64/libQtCore.so.4
#20 0x00007fc48bdc7004 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt/lib64/libQtGui.so.4
#21 0x00007fc48bdcb0ea in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt/lib64/libQtGui.so.4
#22 0x00007fc48dfbb956 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#23 0x00007fc48ce68c3c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt/lib64/libQtCore.so.4
#24 0x00007fc48ce91109 in ?? () from /usr/lib64/qt/lib64/libQtCore.so.4
#25 0x00007fc487c4d300 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#26 0x00007fc487c51158 in ?? () from /usr/lib64/libglib-2.0.so.0
#27 0x00007fc487c5130c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#28 0x00007fc48ce916ff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib64/libQtCore.so.4
#29 0x00007fc48be66dfe in ?? () from /usr/lib64/qt/lib64/libQtGui.so.4
#30 0x00007fc48ce68022 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib64/libQtCore.so.4
#31 0x00007fc48ce6825c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt/lib64/libQtCore.so.4
#32 0x00007fc48ce6c66b in QCoreApplication::exec() () from /usr/lib64/qt/lib64/libQtCore.so.4
#33 0x000000000040902f in _start ()
Comment 3 Christoph Feck 2010-08-27 17:18:40 UTC 

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