Bug 254597 - Kopete crashes after closure
Summary: Kopete crashes after closure
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 1.0.80
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-18 23:05 UTC by Filipe
Modified: 2018-11-29 04:48 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Filipe 2010-10-18 23:05:56 UTC
Application: kopete (1.0.80)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
I just closed Kopete with Ctrl+Q.

- Unusual behavior I noticed:
After starting Kopete again my  msn account was missing.

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7ffb5236a710 (LWP 18044)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007ffb52369a90 in ?? ()
#2  0x00007fffbf777852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7ffb684e7760 (LWP 18038)):
[KCrash Handler]
#6  0x00007ffb67babcd2 in Kopete::Account::~Account (this=0x15aff70, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopeteaccount.cpp:129
#7  0x00007ffb4c2a4ad7 in WlmAccount::~WlmAccount (this=0x15aff70, __in_chrg=<value optimized out>) at ../../../../kopete/protocols/wlm/wlmaccount.cpp:99
#8  0x00007ffb65f96d5f in QObjectPrivate::deleteChildren (this=0x1d11550) at kernel/qobject.cpp:1957
#9  0x00007ffb65f9e41b in QObject::~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#10 0x00007ffb67c0289a in Kopete::Protocol::~Protocol (this=0x279bcb0, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopeteprotocol.cpp:77
#11 0x00007ffb4c2990db in WlmProtocol::~WlmProtocol (this=0x279bcb0, __in_chrg=<value optimized out>) at ../../../../kopete/protocols/wlm/wlmprotocol.cpp:97
#12 0x00007ffb67bfdfa3 in Kopete::PluginManagerPrivate::~PluginManagerPrivate (this=0x12aacd0, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopetepluginmanager.cpp:78
#13 0x00007ffb67bf7777 in destroy () at ../../../kopete/libkopete/kopetepluginmanager.cpp:104
#14 0x00007ffb648694f2 in __run_exit_handlers (status=0) at exit.c:78
#15 exit (status=0) at exit.c:100
#16 0x00007ffb6484ed95 in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffbf7567e8) at libc-start.c:258
#17 0x0000000000411c69 in _start ()

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-30 00:02:42 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-14 11:27:34 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-29 04:48:45 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!