Bug 189283 - kopete crashes without a crash handler
Summary: kopete crashes without a crash handler
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 0.70.2
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-04-10 15:27 UTC by Miguel Tadeu
Modified: 2018-10-21 04:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miguel Tadeu 2009-04-10 15:27:40 UTC
Version:           0.70.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-11-generic

kopete is crashing 2 or 3 times a day, but no crash handler shows up. I'll be waiting for some tips to improve this report.
Comment 1 Dario Andres 2009-04-10 15:33:35 UTC
Have you find something similar between the crashes (kind of pattern). Is anyone of your contacts using "emesene". There is a known bug which causes Kopete to crash when receiving a message from the emesene client.
If you found another type of pattern you can try to reproduce it manually

To try to get a backtrace you can do:
- Close Kopete
- Open Konsole
- Type "gdb kopete" press Return
- Type "run --nofork" press Return
Kopete will start a bit slowly
- Now, reproduce the crash (or wait for it)
When the application crashed:
- GO back to the Konsole/GDB window
- Type "bt full" and press Return until there is no more output.
You will get a trace (may be an incomplete one ), that you can paste here.

Thanks
Comment 2 Dario Andres 2009-05-17 22:49:15 UTC
No response. Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-19 04:34:49 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 4 Andrew Crouthamel 2018-10-21 04:49:26 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!