Bug 234549 - kopete crashes while chatting, problem probably linked to kmail or kontact
Summary: kopete crashes while chatting, problem probably linked to kmail or kontact
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: 0.80.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-16 19:03 UTC by sedo_5
Modified: 2018-11-28 04:54 UTC (History)
0 users

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 sedo_5 2010-04-16 19:03:09 UTC
Application that crashed: kopete
Version of the application: 0.80.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-20-generic-pae i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Since i've been starting using Kontact and Kmail instead of thunderbird, it often happens that kopete crashes during chat sessions while korganizer daemon is on, or when i'm using kmail or kontact. Never ever happened before though...

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[Current thread is 1 (Thread 0xb4f46700 (LWP 19595))]

Thread 2 (Thread 0xb258db70 (LWP 19596)):
#0  0xb78d0430 in __kernel_vsyscall ()
#1  0xb557de15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb608187d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb6bcde67 in QWaitConditionPrivate::wait (this=0x8d2ef10, mutex=0x8d2ef0c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x8d2ef10, mutex=0x8d2ef0c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0xb5897922 in QHostInfoAgent::run (this=0x8d2ef00) at kernel/qhostinfo.cpp:260
#6  0xb6bcce32 in QThreadPrivate::start (arg=0x8d2ef00) at thread/qthread_unix.cpp:188
#7  0xb557980e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb60748de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4f46700 (LWP 19595)):
[KCrash Handler]
#6  0xb60155b3 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7  0xb6017898 in malloc () from /lib/tls/i686/cmov/libc.so.6
#8  0xb61a7bb7 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
#9  0xb6dda4c3 in QDBusMessage (this=0xbfda0c4c) at qdbusmessage.cpp:469
#10 0xb6ddb705 in QDBusMessagePrivate::fromDBusMessage (dmsg=0x93918f0) at qdbusmessage.cpp:195
#11 0xb6dd88da in qDBusSignalFilter (connection=0x88af458, message=0x93918f0, data=0x88ad1d8) at qdbusintegrator.cpp:512
#12 0xb4dd1c8d in dbus_connection_dispatch () from /lib/libdbus-1.so.3
#13 0xb6dc7f32 in q_dbus_connection_dispatch (this=0x88ad1d8) at ./qdbus_symbols_p.h:113
#14 QDBusConnectionPrivate::doDispatch (this=0x88ad1d8) at qdbusintegrator.cpp:1067
#15 0xb6dc807b in QDBusConnectionPrivate::socketRead (this=0x88ad1d8, fd=5) at qdbusintegrator.cpp:1087
#16 0xb6e0bd97 in QDBusConnectionPrivate::qt_metacall (this=0x88ad1d8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfda0eb8) at .moc/release-shared/moc_qdbusconnection_p.cpp:89
#17 0xb6cd3263 in QMetaObject::activate (sender=0x89bf588, from_signal_index=4, to_signal_index=4, argv=0xbfda0eb8) at kernel/qobject.cpp:3113
#18 0xb6cd3ec2 in QMetaObject::activate (sender=0x89bf588, m=0xb6dae8b0, local_signal_index=0, argv=0xbfda0eb8) at kernel/qobject.cpp:3187
#19 0xb6d0d503 in QSocketNotifier::activated (this=0x89bf588, _t1=5) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#20 0xb6cd7c87 in QSocketNotifier::event (this=0x89bf588, e=0xbfda1274) at kernel/qsocketnotifier.cpp:316
#21 0xb6300f54 in QApplicationPrivate::notify_helper (this=0x8891b20, receiver=0x89bf588, e=0xbfda1274) at kernel/qapplication.cpp:4056
#22 0xb630867c in QApplication::notify (this=0xbfda15b4, receiver=0x89bf588, e=0xbfda1274) at kernel/qapplication.cpp:3603
#23 0xb723dbfa in KApplication::notify (this=0xbfda15b4, receiver=0x89bf588, event=0xbfda1274) at ../../kdeui/kernel/kapplication.cpp:302
#24 0xb6cbd6cb in QCoreApplication::notifyInternal (this=0xbfda15b4, receiver=0x89bf588, event=0xbfda1274) at kernel/qcoreapplication.cpp:610
#25 0xb6ce82ca in QCoreApplication::sendEvent (source=0x8894800) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#26 socketNotifierSourceDispatch (source=0x8894800) at kernel/qeventdispatcher_glib.cpp:110
#27 0xb55c6e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#28 0xb55ca730 in ?? () from /lib/libglib-2.0.so.0
#29 0xb55ca863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#30 0xb6ce802c in QEventDispatcherGlib::processEvents (this=0x8874ee8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#31 0xb63a1be5 in QGuiEventDispatcherGlib::processEvents (this=0x8874ee8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#32 0xb6cbbc79 in QEventLoop::processEvents (this=0xbfda1514, flags=) at kernel/qeventloop.cpp:149
#33 0xb6cbc0ca in QEventLoop::exec (this=0xbfda1514, flags=...) at kernel/qeventloop.cpp:201
#34 0xb6cbe53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#35 0xb6300dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#36 0x08059a8c in _start ()

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-29 23:58:01 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bug Janitor Service 2018-11-13 14:25:28 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-28 04:54:27 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!