Version: (using KDE KDE 3.0.8) Installed from: Debian testing/unstable Packages OS: Linux While composing an email, kmail crashed because my disk was full. This in itself wasn't a problem (once I figured out why). The big problem was that this corrupted my mail directory. I tried removing all the index and sorting files, but kmail still crashes. It seems like kmail should be able to survive such an event. Personally, I back up all 500 megs of my email every day, but I'm sure most folks don't. Also, if I dug around enough I could probably unmangle my mail files, but many folks wouldn't be able to do this either. I wish that I could provide more information. I'm going to keep this Mail/ directory around in case you have any tests that you'd like me to perform. Thanks, kmail is the application I use more than any other (okay, behind bash and emacs ;-).
Subject: Re: New: kmail crashed because the disk was full and corrupted my mailbox. After this, mail could not be restarted Please send us the backtrace you get when KMail crashes.
Subject: Re: kmail crashed because the disk was full and corrupted my mailbox. After this, mail could not be restarted (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)...[New Thread 1024 (LWP 1583)] (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)...0x412a3609 in wait4 () from /lib/libc.so.6 #0 0x412a3609 in wait4 () from /lib/libc.so.6 #1 0x41318dd0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x4113feeb in waitpid () from /lib/libpthread.so.0 #3 0x409a500a in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x4113da44 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x4122c518 in sigaction () from /lib/libc.so.6 #6 0x08120dae in KDialog::marginHint () #7 0x080fdeaf in KDialog::marginHint () #8 0x080da336 in KDialog::marginHint () #9 0x080dae42 in KDialog::marginHint () #10 0x080df5f3 in KDialog::marginHint () #11 0x40c8ebda in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #12 0x40ef3374 in QListView::currentChanged () from /usr/lib/libqt-mt.so.3 #13 0x40d3dd30 in QListView::setCurrentItem () from /usr/lib/libqt-mt.so.3 #14 0x080db4fc in KDialog::marginHint () #15 0x080debcc in KDialog::marginHint () #16 0x080da8b1 in KDialog::marginHint () #17 0x080d7244 in KDialog::marginHint () #18 0x0809119d in KDialog::marginHint () #19 0x08090e92 in KDialog::marginHint () #20 0x08089881 in KDialog::marginHint () #21 0x40c8ebda in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #22 0x080ce16a in KDialog::marginHint () #23 0x080cb613 in KDialog::marginHint () #24 0x080ce3ed in KDialog::marginHint () #25 0x40c8ebda in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #26 0x40ef3374 in QListView::currentChanged () from /usr/lib/libqt-mt.so.3 #27 0x40d3dd30 in QListView::setCurrentItem () from /usr/lib/libqt-mt.so.3 #28 0x080cb5d4 in KDialog::marginHint () #29 0x0808a76d in KDialog::marginHint () #30 0x0816dc3c in KDialog::marginHint () #31 0x08170a94 in KDialog::marginHint () #32 0x08171fe0 in KDialog::marginHint () #33 0x409b8e7d in KUniqueApplication::processDelayed () from /usr/lib/libkdecore.so.4 #34 0x409b91cb in KUniqueApplication::qt_invoke () from /usr/lib/libkdecore.so.4 #35 0x40c8ebda in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #36 0x40ee0243 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #37 0x40ca40e5 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #38 0x40ca9543 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #39 0x40c3d1a3 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #40 0x40c3d047 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #41 0x4094b3a4 in KApplication::notify () from /usr/lib/libkdecore.so.4 #42 0x40c20fe3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #43 0x40c03a7c in QEventLoop::processNextEvent () from /usr/lib/libqt-mt.so.3 #44 0x40c4e72e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #45 0x40c3d32a in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3 #46 0x40db35e1 in QDialog::exec () from /usr/lib/libqt-mt.so.3 #47 0x407fbacb in KWritePermsIcon::qt_static_property () from /usr/lib/libkdeui.so.4 #48 0x407fe1a7 in KMessageBox::informationList () from /usr/lib/libkdeui.so.4 #49 0x407fded2 in KMessageBox::information () from /usr/lib/libkdeui.so.4 #50 0x08153781 in KDialog::marginHint () #51 0x0816f321 in KDialog::marginHint () #52 0x0816fa2c in KDialog::marginHint () #53 0x08172db4 in KDialog::marginHint () #54 0x4121c0bf in __libc_start_main () from /lib/libc.so.6 On 16 Oct 2002, Ingo Kl
Thanks for the backtrace. This bug was already fixed in cvs. *** This bug has been marked as a duplicate of 48688 ***
I have the same problem with kmail 1.9.5 After my disk got full, kmail complained (and some other apps did, too). I logged out and in again, and after that neither Kontact nor kmail, nor akregator, nor kaddressbook start anymore. (Sidenote: I then deleted the index-files after reading some other bug reports). A reboot of the system did the trick in the end and fixed it. Don't know why, though...