| Summary: | Kopete sometimes crashes when a contact comes on-line | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Volker Fröhlich <volker27> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | spearhead2k3, till2.schaefer |
| Priority: | NOR | ||
| Version First Reported In: | 1.0.80 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Volker Fröhlich
2011-06-05 09:44:52 UTC
Created attachment 65501 [details]
New crash information added by DrKonqi
kopete (1.1.3) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.2
- What I was doing when the application crashed:
the programm was idelling. someone may have send a message. messages for people comming online are deaktivated on my system. mybe thats a hint for the cause
-- Backtrace (Reduced):
#6 Kopete::ChatSession::myself (this=0x0) at /var/tmp/portage/kde-base/kopete-4.7.3/work/kopete-4.7.3/kopete/libkopete/kopetechatsession.cpp:218
#7 0x00007f5e7ceea1c9 in Kopete::ChatSession::account (this=0x0) at /var/tmp/portage/kde-base/kopete-4.7.3/work/kopete-4.7.3/kopete/libkopete/kopetechatsession.cpp:671
#8 0x00007f5e6995f474 in OtrMessageHandler::handleMessage (this=0x10e2220, event=0x23f0340) at /var/tmp/portage/kde-base/kopete-4.7.3/work/kopete-4.7.3/kopete/plugins/otr/otrplugin.cpp:302
#9 0x00007f5e7cf09422 in Kopete::ProcessMessageTask::qt_metacall (this=0x12aff30, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>) at /var/tmp/portage/kde-base/kopete-4.7.3/work/kopete-4.7.3_build/kopete/libkopete/kopetemessagehandlerchain.moc:124
#10 0x00007f5e7b25c2ea in QObject::event (this=0x12aff30, e=<value optimized out>) at kernel/qobject.cpp:1217
Created attachment 65818 [details]
New crash information added by DrKonqi
kopete (1.1.3) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4
- What I was doing when the application crashed:
kopete was idling and someone may have come online and/or an
online contact might have sent a message. But kopete crashed so
I cant tell for sure.
-- Backtrace (Reduced):
#6 Kopete::ChatSession::myself (this=0x0) at ../../../kopete/libkopete/kopetechatsession.cpp:218
#7 0x00007f126d561e49 in Kopete::ChatSession::account (this=0x0) at ../../../kopete/libkopete/kopetechatsession.cpp:671
#8 0x00007f12548fc9f0 in OtrMessageHandler::handleMessage (this=0x122dcd0, event=0x7f1248115740) at ../../../../kopete/plugins/otr/otrplugin.cpp:302
#9 0x00007f126d582102 in Kopete::ProcessMessageTask::qt_metacall (this=0x7f124824a230, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at ./kopetemessagehandlerchain.moc:124
#10 0x00007f126b93fa5e in QObject::event (this=0x7f124824a230, e=<optimized out>) at kernel/qobject.cpp:1217
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! 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! 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! |