Bug 119686 - error: Die Indexdatei......inbox.index</b> kann nicht synchronisiert werden:
Summary: error: Die Indexdatei......inbox.index</b> kann nicht synchronisiert werden:
Status: RESOLVED DUPLICATE of bug 106650
Alias: None
Product: kmail
Classification: Unmaintained
Component: index (other bugs)
Version First Reported In: 1.8.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-07 15:22 UTC by Günter Ohmer
Modified: 2007-09-14 12:17 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Günter Ohmer 2006-01-07 15:22:23 UTC 
Version:           1.8.2 (using KDE KDE 3.4.2)
Installed from:    SuSE RPMs

After starting kmail I get the error message:
=================================================
Ein schwerwiegender Fehler ist in KMail aufgetreten. Das Programm wird beendet.
Die Fehlermeldung lautet:
Die Indexdatei
<b>/home/guenter/.kde/share/apps/kmail/mail/.inbox.index</b>
kann nicht synchronisiert werden: Interner Fehler. Bitte notieren Sie die Details und senden Sie einen Fehlerbericht ein.
==================================================
After removing the files ".inbox.index", ".inbox.index.ids" and ".inbox.index.sorted"
I saved the old .index-files and a backtrace.
Comment 1 Günter Ohmer 2006-01-07 15:27:30 UTC 
kmail started without an error after removing the files ".inbox.index", ".inbox.index.ids" and ".inbox.index.sorted" the programm started
Comment 2 Thiago Macieira 2006-01-07 16:01:19 UTC 
Corrupt indices? Did you experience a crash before this started happening?
Comment 3 Günter Ohmer 2006-01-08 11:11:13 UTC 
Am Samstag, 7. Januar 2006 16:01 schrieb Thiago Macieira:
[bugs.kde.org quoted mail]
No crash, kmail ended regular before the error.
The only  speciality is, that my kmail-files are on a samba-share.
Comment 4 Thomas McGuire 2007-07-17 15:25:37 UTC 

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