Bug 90540 - kpim crash autosave open document
Summary: kpim crash autosave open document
Status: RESOLVED DUPLICATE of bug 85289
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 1.0
Platform: Mandrake RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-30 14:45 UTC by Vasco Pinheiro
Modified: 2004-10-22 23:07 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 Vasco Pinheiro 2004-09-30 14:45:14 UTC
Version:           1.0 (using KDE KDE 3.2.3)
Installed from:    Mandrake RPMs
OS:                Linux

It's the second time that this happens, so i'm submiting this crash report. It happened when I leave the computer idle about 10m+ and when I return the program has crashed. Don't know if it crashes only with idle computer, but when i'm working with it, it haven't crashed. I remember that a message that appears in the Kcrash program said something about "Auto Save Open Documents" or something like that...

Backtrace:

(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 1099193824 (LWP 4538)]
[New Thread 1132522416 (LWP 4611)]
[Thread debugging using libthread_db enabled]
[New Thread 1099193824 (LWP 4538)]
[New Thread 1132522416 (LWP 4611)]
[Thread debugging using libthread_db enabled]
[New Thread 1099193824 (LWP 4538)]
[New Thread 1132522416 (LWP 4611)]
[New Thread 1124129712 (LWP 4610)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0xbfffdfec in ?? ()
#2  0x00000000 in ?? ()
#3  0x00000000 in ?? ()
#4  0x416172db in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#5  0x40aacece in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4
#6  <signal handler called>
#7  0x40e6b17d in QObject::receivers () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xbfffe2f0 in ?? ()
#9  0x00000000 in ?? ()
#10 0x00000100 in ?? ()
#11 0x412d8e10 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x00000000 in ?? ()
#13 0x01b65980 in ?? ()
#14 0x08228278 in ?? ()
#15 0x40149a20 in ?? () from /usr/lib/libkdepim.so.1
#16 0x00000000 in ?? ()
#17 0xbfffe650 in ?? ()
#18 0xbfffe378 in ?? ()
#19 0x400dc6fb in KPIM::ProgressItem::progressItemProgress ()
   from /usr/lib/libkdepim.so.1
Comment 1 Stephan Kulow 2004-10-22 23:07:08 UTC
your stack trace is very broken. But let's assume it's the same bug.

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