Bug 236514 - Multiple contact sending crashes
Summary: Multiple contact sending crashes
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kab3
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-06 08:43 UTC by Jade Falcon
Modified: 2018-09-04 19:55 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 Jade Falcon 2010-05-06 08:43:18 UTC
Application that crashed: kontact
Version of the application: 4.3.5
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Steps to reproduce:

View list of contacts.
Select multiple contacts using shift-click.
Right-click on selection.
Click "Send Contact"
Enjoy your segfault.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x008039f9 in QString::operator== (this=0x9d71528, other=...) at tools/qstring.cpp:1920
#7  0x00e2e0a6 in qStringComparisonHelper (_to=..., _cc=..., _bcc=..., subject=..., body=..., attachURLs=..., startup_id=...) at /usr/include/qt4/QtCore/qstring.h:905
#8  QString::operator== (_to=..., _cc=..., _bcc=..., subject=..., body=..., attachURLs=..., startup_id=...) at /usr/include/qt4/QtCore/qstring.h:908
#9  KToolInvocation::invokeMailer (_to=..., _cc=..., _bcc=..., subject=..., body=..., attachURLs=..., startup_id=...) at ../../kdecore/kernel/ktoolinvocation_x11.cpp:220
#10 0x0833fcce in KABTools::mailVCards (uids=..., ab=0xa65da90) at ../../kaddressbook/kabtools.cpp:101
#11 0x082f4e07 in KABCore::mailVCard (this=0xa99b4f0, uids=...) at ../../kaddressbook/kabcore.cpp:435
#12 0x082f5d89 in KABCore::mailVCard (this=0xa99b4f0) at ../../kaddressbook/kabcore.cpp:430
#13 0x08301d87 in KABCore::qt_metacall (this=0xa99b4f0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbff19d28) at ./kabcore.moc:185
#14 0x008c7263 in QMetaObject::activate (sender=0xaaae208, from_signal_index=5, to_signal_index=6, argv=0xbff19d28) at kernel/qobject.cpp:3113
#15 0x008c76d8 in QMetaObject::activate (sender=0xaaae208, m=0x18b5e48, from_local_signal_index=1, to_local_signal_index=2, argv=0xbff19d28) at kernel/qobject.cpp:3207
#16 0x0104d9b1 in QAction::triggered (this=0xaaae208, _t1=false) at .moc/release-shared/moc_qaction.cpp:236
#17 0x0104ef32 in QAction::activate (this=0xaaae208, event=QAction::Trigger) at kernel/qaction.cpp:1160
#18 0x0149c9cc in QMenuPrivate::activateCausedStack (this=0xa3b5f78, causedStack=..., action=0xaaae208, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:967
#19 0x014a303b in QMenuPrivate::activateAction (this=0xa3b5f78, action=0xaaae208, action_e=QAction::Trigger, self=<value optimized out>) at widgets/qmenu.cpp:1060
#20 0x014a3bf7 in QMenu::mouseReleaseEvent (this=0xa386a20, e=0xbff1a480) at widgets/qmenu.cpp:2254
#21 0x0061b835 in KMenu::mouseReleaseEvent (this=0xa386a20, e=0xbff1a480) at ../../kdeui/widgets/kmenu.cpp:456
#22 0x010a9012 in QWidget::event (this=0xa386a20, event=0xbff1a480) at kernel/qwidget.cpp:7549
#23 0x014a5e34 in QMenu::event (this=0xa386a20, e=0xbff1a480) at widgets/qmenu.cpp:2353
#24 0x01053f54 in QApplicationPrivate::notify_helper (this=0x99c2328, receiver=0xa386a20, e=0xbff1a480) at kernel/qapplication.cpp:4056
#25 0x0105c033 in QApplication::notify (this=0xbff1be64, receiver=0xa386a20, e=0xbff1a480) at kernel/qapplication.cpp:3758
#26 0x0053125a in KApplication::notify (this=0xbff1be64, receiver=0xa386a20, event=0xbff1a480) at ../../kdeui/kernel/kapplication.cpp:302
#27 0x008b16cb in QCoreApplication::notifyInternal (this=0xbff1be64, receiver=0xa386a20, event=0xbff1a480) at kernel/qcoreapplication.cpp:610
#28 0x0105af6e in QCoreApplication::sendSpontaneousEvent (receiver=0xa386a20, event=0xbff1a480, alienWidget=0x0, nativeWidget=0xa386a20, buttonDown=0x18ceaa0, lastMouseReceiver=...)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#29 QApplicationPrivate::sendMouseEvent (receiver=0xa386a20, event=0xbff1a480, alienWidget=0x0, nativeWidget=0xa386a20, buttonDown=0x18ceaa0, lastMouseReceiver=...) at kernel/qapplication.cpp:2924
#30 0x010c9c87 in QETWidget::translateMouseEvent (this=0xa386a20, event=0xbff1bacc) at kernel/qapplication_x11.cpp:4343
#31 0x010c8c4b in QApplication::x11ProcessEvent (this=0xbff1be64, event=0xbff1bacc) at kernel/qapplication_x11.cpp:3428
#32 0x010f5502 in x11EventSourceDispatch (s=0x99c4788, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#33 0x080cee88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#34 0x080d2730 in ?? () from /lib/libglib-2.0.so.0
#35 0x080d2863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#36 0x008dc02c in QEventDispatcherGlib::processEvents (this=0x99a29f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#37 0x010f4be5 in QGuiEventDispatcherGlib::processEvents (this=0x99a29f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#38 0x008afc79 in QEventLoop::processEvents (this=0xbff1bdc4, flags=) at kernel/qeventloop.cpp:149
#39 0x008b00ca in QEventLoop::exec (this=0xbff1bdc4, flags=...) at kernel/qeventloop.cpp:201
#40 0x008b253f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#41 0x01053dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#42 0x0804b4e6 in main (argc=1, argv=0xbff1c084) at ../../../kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 222055

Reported using DrKonqi
Comment 1 Christoph Feck 2013-09-12 21:35:10 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

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

If the crash still happens with a recent KDE version (4.10.5 or 4.11), 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 CONFIRMED)
Comment 2 Andrew Crouthamel 2018-09-04 19:55:35 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.