Bug 199240

Summary: kontact crashes with SIGSEGV when clicking on a certain link
Product: [Applications] akregator Reporter: Sergiu Bivol <sergiu>
Component: internal browserAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sergiu Bivol 2009-07-07 08:07:58 UTC
Application that crashed: kontact
Version of the application: 4.3.0 rc1
KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1))
Qt Version: 4.5.2
Operating System: Linux 2.6.31-1-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
Kontact crashes when I do the following steps:
1. Open Feeds tab
2. Click on a "KDE Apps" feed, e.g. "Firewall Builder 3.0.5"
3. The feed has a small image, click on it. A new tab opens.
4. In the new tab, click on one of the preview images. Another tab opens, showing the full-sized images.
5. Under the image, there is a "[close]" link. Clicking on the link crashes Kontact.

Expected behavior: The current tab closes
Reproducible: Always

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f026b931205 in QObjectPrivate::cleanConnectionLists (this=0x2340e70) at kernel/qobject.cpp:306
#6  0x00007f026b9370ce in QMetaObject::activate (sender=0x2426420, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x7fffccae8090) at kernel/qobject.cpp:3148
#7  0x00007f026b937354 in QObject::destroyed (this=0x2340e70, _t1=0x2426420) at .moc/release-shared/moc_qobject.cpp:143
#8  0x00007f026b9381bb in ~QObject (this=<value optimized out>) at kernel/qobject.cpp:757
#9  0x00007f026af38273 in ~Part (this=0x2426420, __vtt_parm=0x7f026ac4c9f0) at ../../kparts/part.cpp:212
#10 0x00007f026a59282b in ~KHTMLPart (this=0x2426420) at ../../khtml/khtml_part.cpp:625
#11 0x00007f026b93115d in QObject::event (this=0x2426420, e=0x7fffccae8000) at kernel/qobject.cpp:1094
#12 0x00007f026c23a62c in QApplicationPrivate::notify_helper (this=0x778d60, receiver=0x2426420, e=0x1561340) at kernel/qapplication.cpp:4056
#13 0x00007f026c2418fe in QApplication::notify (this=0x7fffccae8ba0, receiver=0x2426420, e=0x1561340) at kernel/qapplication.cpp:4021
#14 0x00007f026ce703a6 in KApplication::notify (this=0x7fffccae8ba0, receiver=0x2426420, event=0x1561340) at ../../kdeui/kernel/kapplication.cpp:302
#15 0x00007f026b921c6c in QCoreApplication::notifyInternal (this=0x7fffccae8ba0, receiver=0x2426420, event=0x1561340) at kernel/qcoreapplication.cpp:610
#16 0x00007f026b92284a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x746c60)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0x00007f026b94a583 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#18 0x00007f026572b8fe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x00007f026572efd8 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x00007f026572f100 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00007f026b94a1f6 in QEventDispatcherGlib::processEvents (this=0x746850, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x00007f026c2ceace in QGuiEventDispatcherGlib::processEvents (this=0x2340e70, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f026b920572 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007f026b920944 in QEventLoop::exec (this=0x7fffccae8ae0, flags=) at kernel/qeventloop.cpp:201
#25 0x00007f026b922af9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x0000000000403f27 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-07 12:10:09 UTC
This is reported as bug 193146. Thanks!

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