Summary: | Kopete crashing upon start (no window shown) | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Andreas Krohn <Hamburger1984> |
Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | hubn3rd, manisandro, qw9876543 |
Priority: | NOR | ||
Version: | 1.2.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Andreas Krohn
2012-05-21 19:08:12 UTC
Created attachment 71628 [details]
New crash information added by DrKonqi
kopete (1.2.80) on KDE Platform 4.8.80 (4.8.80) using Qt 4.8.2
- What I was doing when the application crashed:
Started kopete. Crashes every time.
- Additional info:
The issue appeared suddenly with no apparent reason.
I saw this issue on multiple machines. One one machine, the issue eventually disappeared after a few days, again without any apparent reason.
The issue only appears when using jabber.
-- Backtrace (Reduced):
#6 0x00007f4658a37c25 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
#7 0x00007f4658a393d8 in __GI_abort () at abort.c:90
[...]
#9 0x00007f4658b0e387 in __GI___fortify_fail (msg=msg@entry=0x7f4658b7d365 "buffer overflow detected") at fortify_fail.c:31
#10 0x00007f4658b0c450 in __GI___chk_fail () at chk_fail.c:28
#11 0x00007f4642f5c793 in memset (__len=8, __dest=<optimized out>, __ch=0) at /usr/include/bits/string3.h:85
This also happens to me on KDE 4.8.4. Turning off the WLM Plugin fixes it. Created attachment 72164 [details]
New crash information added by DrKonqi
kopete (1.2.3) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2
- What I was doing when the application crashed:
kopete crashes when it starts, no window shown
-- Backtrace (Reduced):
#6 0x0000003042035965 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x0000003042037118 in __GI_abort () at abort.c:91
[...]
#9 0x00000030421097e7 in __GI___fortify_fail (msg=msg@entry=0x3042177806 "buffer overflow detected") at fortify_fail.c:32
#10 0x00000030421079a0 in __GI___chk_fail () at chk_fail.c:29
#11 0x00007f5f61fe9793 in memset (__len=8, __dest=<optimized out>, __ch=0) at /usr/include/bits/string3.h:85
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! |