Bug 217545 - Kontact krashed when trying to close the program
Summary: Kontact krashed when trying to close the program
Status: RESOLVED DUPLICATE of bug 199375
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-06 11:04 UTC by Borden
Modified: 2009-12-06 20:23 UTC (History)
1 user (show)

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 Borden 2009-12-06 11:04:27 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-2-686 i686
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
I just set up two IMAP email accounts and after checking them closed the program using the window's close button. The dump looks very close to the bug I've identified as a possible duplicate

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x00000000 in ?? ()
#7  0xb625650e in qDeleteAll<KIO::SchedulerPrivate::ProtocolInfoDict> () at /usr/include/qt4/QtCore/qalgorithms.h:358
#8  ~SchedulerPrivate () at ../../kio/kio/scheduler.cpp:103
#9  destroy () at ../../kio/kio/scheduler.cpp:209
#10 0xb618bcfb in ~KCleanUpGlobalStatic (this=0xb6355214, __in_chrg=<value optimized out>) at ../../kdecore/kernel/kglobal.h:62
#11 0xb6a5a481 in __run_exit_handlers (status=0, listp=0xb6b6e324, run_list_atexit=true) at exit.c:78
#12 0xb6a5a4df in *__GI_exit (status=0) at exit.c:100
#13 0xb6a41b5d in __libc_start_main (main=0x804ab90 <main>, argc=1, ubp_av=0xbfb1cbd4, init=0x804c100 <__libc_csu_init>, fini=0x804c0f0 <__libc_csu_fini>, rtld_fini=0xb7f96980 <_dl_fini>, 
    stack_end=0xbfb1cbcc) at libc-start.c:254
#14 0x0804a551 in _start () at ../sysdeps/i386/elf/start.S:119

This bug may be a duplicate of or related to bug 215245

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-06 20:23:53 UTC
Fixed recently. Thanks

*** This bug has been marked as a duplicate of bug 199375 ***