Summary: | Kontact crashed after viewing a Pop-Up note | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Sam Azer <sam> |
Component: | notes | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | bugsnmd, sam, tim |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Sam Azer
2011-01-21 02:44:02 UTC
Created attachment 58705 [details]
New crash information added by DrKonqi
kontact (4.4.10) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
i think this crash is exactly the same one as the already reported one.
-- Backtrace (Reduced):
#6 0x00007ff576174e00 in setText (this=0x32c4cf0, item=0x3f46410) at /usr/include/qt4/QtGui/qlistwidget.h:174
#7 setIconText (this=0x32c4cf0, item=0x3f46410) at ../../../../kontact/plugins/knotes/knotes_part_p.h:107
#8 KNotesPart::editNote (this=0x32c4cf0, item=0x3f46410) at ../../../../kontact/plugins/knotes/knotes_part.cpp:428
#9 0x00007ff5761775ff in KNotesPart::qt_metacall (this=0x32c4cf0, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x7fff6a3e4cf0) at ./knotes_part.moc:110
[...]
#11 0x00007ff5a911474f in KListWidget::executed (this=<value optimized out>, _t1=0x3f46410) at ./klistwidget.moc:103
please retry with at least kdepim 4.4.10 > please retry with at least kdepim 4.4.10
my backtrace was generated with kontact 4.4.10
right, sorry Created attachment 59185 [details]
New crash information added by DrKonqi
kontact (4.4.9) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.0
- What I was doing when the application crashed:
Followed the list of steps from the first bug report
- Unusual behavior I noticed:
Kontact crashed as above
-- Backtrace (Reduced):
#7 0x077d2e04 in setText (this=0xb28d740, item=0x9daf6c0) at /usr/include/qt4/QtGui/qlistwidget.h:174
#8 setIconText (this=0xb28d740, item=0x9daf6c0) at ../../../../kontact/plugins/knotes/knotes_part_p.h:107
#9 KNotesPart::editNote (this=0xb28d740, item=0x9daf6c0) at ../../../../kontact/plugins/knotes/knotes_part.cpp:428
#10 0x077d6a47 in KNotesPart::qt_metacall (this=0xb28d740, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfa8dd38) at ./knotes_part.moc:110
[...]
#13 0x00ef5ab3 in KListWidget::executed (this=0xc99ada0, _t1=0x9daf6c0) at ./klistwidget.moc:103
(sorry - thought I was using the latest kontact.) I'm getting the same problem: Application: kontact (4.13.3) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.13.0-35-generic x86_64 Distribution: Ubuntu 14.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I opened Kontact and then clicked to open one of the pop-up notes ; crashed immediately. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2dd2618800 (LWP 4545))] Thread 4 (Thread 0x7f2db2187700 (LWP 4546)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f2dcd3c381d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f2dcd3c3859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f2dc9ae5182 in start_thread (arg=0x7f2db2187700) at pthread_create.c:312 #4 0x00007f2dcfb96fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f2d71884700 (LWP 4547)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f2dcd10420d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f2dcd3f2fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f2dc9ae5182 in start_thread (arg=0x7f2d71884700) at pthread_create.c:312 #4 0x00007f2dcfb96fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f2d61b5a700 (LWP 4553)): #0 0x00007f2dcfb89c6d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f2dc9605fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f2dc96060ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f2dd03107be in QEventDispatcherGlib::processEvents (this=0x7f2d5c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x00007f2dd02e20af in QEventLoop::processEvents (this=this@entry=0x7f2d61b59de0, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f2dd02e23a5 in QEventLoop::exec (this=this@entry=0x7f2d61b59de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f2dd01dec5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537 #7 0x00007f2dd01e132f in QThreadPrivate::start (arg=0x1836cf0) at thread/qthread_unix.cpp:349 #8 0x00007f2dc9ae5182 in start_thread (arg=0x7f2d61b5a700) at pthread_create.c:312 #9 0x00007f2dcfb96fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f2dd2618800 (LWP 4545)): [KCrash Handler] #6 QApplicationPrivate::notify_helper (this=this@entry=0x151af70, receiver=receiver@entry=0x4550c40, e=e@entry=0x7fff9b599110) at kernel/qapplication.cpp:4545 #7 0x00007f2dd0cdc5dd in QApplication::notify (this=this@entry=0x7fff9b599960, receiver=receiver@entry=0x4550c40, e=e@entry=0x7fff9b599110) at kernel/qapplication.cpp:4110 #8 0x00007f2dd19e0d1a in KApplication::notify (this=0x7fff9b599960, receiver=0x4550c40, event=0x7fff9b599110) at ../../kdeui/kernel/kapplication.cpp:311 #9 0x00007f2dd02e34dd in QCoreApplication::notifyInternal (this=0x7fff9b599960, receiver=receiver@entry=0x4550c40, event=event@entry=0x7fff9b599110) at kernel/qcoreapplication.cpp:953 #10 0x00007f2dd0cdbd93 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #11 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x4550c40, event=event@entry=0x7fff9b599110, alienWidget=alienWidget@entry=0x4550c40, nativeWidget=nativeWidget@entry=0x1feb180, buttonDown=buttonDown@entry=0x7f2dd17bb318 <qt_button_down>, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3178 #12 0x00007f2dd0d509cb in QETWidget::translateMouseEvent (this=this@entry=0x1feb180, event=event@entry=0x7fff9b599490) at kernel/qapplication_x11.cpp:4634 #13 0x00007f2dd0d50269 in QApplication::x11ProcessEvent (this=0x7fff9b599960, event=event@entry=0x7fff9b599490) at kernel/qapplication_x11.cpp:3627 #14 0x00007f2dd0d77b02 in x11EventSourceDispatch (s=0x151c600, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #15 0x00007f2dc9605e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x00007f2dc9606048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x00007f2dc96060ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x00007f2dd03107a1 in QEventDispatcherGlib::processEvents (this=0x14e0bb0, flags=...) at kernel/qeventdispatcher_glib.cpp:434 #19 0x00007f2dd0d77bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #20 0x00007f2dd02e20af in QEventLoop::processEvents (this=this@entry=0x7fff9b599860, flags=...) at kernel/qeventloop.cpp:149 #21 0x00007f2dd02e23a5 in QEventLoop::exec (this=this@entry=0x7fff9b599860, flags=...) at kernel/qeventloop.cpp:204 #22 0x00007f2dd02e7b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #23 0x00007f2dd0cd437c in QApplication::exec () at kernel/qapplication.cpp:3828 #24 0x0000000000403660 in main (argc=1, argv=0x7fff9b599aa8) at ../../../kontact/src/main.cpp:219 Possible duplicates by query: bug 338926, bug 338260, bug 338059, bug 338015, bug 337985. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |