Sir,

I have export kmail settings from kde 3 to kde 4.4 but when i have load kmail than it will display same mail but after reading 2 or 3 messages it will crash with segmentation fault.

Please help.

Rajeev

Please tell us:

Which Linux distribution are you using?

When you changed from KDE3 to KDE SC4.4, was this a routine upgrade, or a change of distribution?

Can you describe exactly what you did to 'export' the KDE3 settings? Which files are involved, and what method did you use?

From your description, it sounds as though you have never had KMail working under KDE SC4.4 - is that correct?

Do you use KMail alone, or do you use Kontact?

Sir,

I am using Fedora 12 and this is not a routine upgrade i have switch from Fedora 6 to Fedora 12.

I have make compress file of home directory of each user from Fedora 6 and extract it to new Fedora 12 home directory.

I have not use KMail in KDE SC4.4 earlier.

I am using KMail alone.

Basically i have migrate all user from Fedora 6 to Fedora 12 with all Fedora 6 settings.

The user who using Thunderbird in Fedora 6 having no problem in Fedora 12.

I am using IMAP server.


Please help.


Rajeev.

Fedora 6 to 12 is a huge jump and there have been many changes on the way. Unfortunately I can't tell you which config file is likely to be causing the problem. If I were trying to solve this one, I'd go to /home/rajeev/.kde/share/config and rename kmailrc to kmailrc.sav (with kmail/kontact closed, of course) then try to restart kmail. That should create a default config file and you will need to go through the kmail settings again, if kmail is then stable. Just set up your incoming and outgoing accounts and your main identity first, and try it.

If that doesn't cure it you can restore your renamed kmailrc then go on to test in the same way all the files mentioned in http://userbase.kde.org/KMail/FAQs_Hint ... #Migration . Remember that you must always make any changes with kmail closed.

Hopefully you will identify a single file problem and quickly get things working again.

At the same time, bear in mind that in Fedora 12 you must have nepomuk working to use kmail. I would have thought that kmail simply wouldn't start if that was your problem, but it's worth checking anyway. You'll find it in SystemSettings, advanced tab, under Desktop Search

when i have enable nepomuk it will say nepomuk server is not runing. So, will you please tell me how to start nepomuk server permanently.

Rajeev.

First of all - get all updates if you haven't done that very recently - Fedora release updates several times a week. Nepomuk still gives a few problems in 4.4.0, though most have work-arounds. 4.4.1 for Fedora 12 is due any day now, and solves just about everything else.

Now, for your particular problems, you need to read http://userbase.kde.org/Akonadi. This has notes about the problems that various people have seen, and how to deal with them. Try out the fixes that seem appropriate to your system, then let us know how you are doing. If you get any error messages it's very helpful to copy and paste them here.

Actully problem is related to attachments. because Kmail crash on the messages who having attachments. But when i have change View->Smart to View->Inline or View->As Icon than it will not crash but again when i have change for inline to smart than again it will crash.

Please help.

Rajeev.

I have no idea what could be causing that, but I'll speak to the developers, then get back to you.

There are some bug reports about some circumstances involving attachments, so the developers now need to know whether your problem is a new one. Happily Fedora makes this relatively easy for you. When you get a crash like that you should be seeing a dialog box asking you if you want to report it. You then have to wait while it gathers information. It will probably say that it doesn't have enough information, and you have to agree to it downloading a debug package. Once that has installed it will again go through the available information and prepare a bug report, which goes to the Fedora bugzilla. However, the kmail developers would like to see it as well, so please post here the bug report number, so that I can pass it to them.

Error report

Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6 0x07ad746c in QTreeWidgetItem::addChild (this=0xa53f780, child=0xa1f7648) at itemviews/qtreewidget.cpp:1882
#7 0x07ad76a1 in QTreeWidgetItem::QTreeWidgetItem (this=0xa1f7648, parent=0xa53f780, type=0) at itemviews/qtreewidget.cpp:1428
#8 0x0070aaf5 in KMMimePartTreeItem::KMMimePartTreeItem (this=0xa1f7648, parent=0xa53f780, node=0xa1df050, description=..., mimetype=..., encoding=..., size=0, revertOrder=false)
at /usr/src/debug/kdepim-4.4.0/kmail/kmmimeparttree.cpp:378
#9 0x007524fe in partNode::fillMimePartTree (this=0xa1df050, parentItem=0xa53f780, mimePartTree=0x0, labelDescr=..., labelCntType=..., labelEncoding=..., size=0, revertOrder=false)
at /usr/src/debug/kdepim-4.4.0/kmail/partNode.cpp:549
#10 0x0073fa9d in KMail::ObjectTreeParser::insertAndParseNewChildNode (this=0xbf9aa910, startNode=..., content=0x6d19518 "", cntDesc=0x992222 "encapsulated message", append=false,
addToTextualContent=false) at /usr/src/debug/kdepim-4.4.0/kmail/objecttreeparser.cpp:232
#11 0x00743cde in KMail::ObjectTreeParser::processMessageRfc822Subtype (this=0xbf9aa910, node=0xa53dd48) at /usr/src/debug/kdepim-4.4.0/kmail/objecttreeparser.cpp:1582
#12 0x0074d0ec in (anonymous namespace)::MessageRfc822BodyPartFormatter::process (this=0xa4a4770, otp=0xbf9aa910, node=0xa53dd48, result=...)
at /usr/src/debug/kdepim-4.4.0/kmail/bodypartformatter.cpp:116
#13 0x0073f0d3 in KMail::ObjectTreeParser::parseObjectTree (this=0xbf9aa910, node=<value optimized out>) at /usr/src/debug/kdepim-4.4.0/kmail/objecttreeparser.cpp:318
#14 0x0073f448 in KMail::ObjectTreeParser::stdChildHandling (this=0xbf9aab2c, child=0xa5c8038) at /usr/src/debug/kdepim-4.4.0/kmail/objecttreeparser.cpp:1278
#15 0x0073f842 in KMail::ObjectTreeParser::processMultiPartMixedSubtype (this=0xbf9aab2c, node=0xa542780) at /usr/src/debug/kdepim-4.4.0/kmail/objecttreeparser.cpp:1291
#16 0x0074d0ac in (anonymous namespace)::MultiPartMixedBodyPartFormatter::process (this=0xa4ad570, otp=0xbf9aab2c, node=0xa542780, result=...)
at /usr/src/debug/kdepim-4.4.0/kmail/bodypartformatter.cpp:118
#17 0x0073f0d3 in KMail::ObjectTreeParser::parseObjectTree (this=0xbf9aab2c, node=<value optimized out>) at /usr/src/debug/kdepim-4.4.0/kmail/objecttreeparser.cpp:318
#18 0x005c1ecd in KMReaderWin::parseMsg (this=0x9d85cf0, aMsg=0xa4d4ba0) at /usr/src/debug/kdepim-4.4.0/kmail/kmreaderwin.cpp:1611
#19 0x005b6276 in KMReaderWin::displayMessage (this=0x9d85cf0) at /usr/src/debug/kdepim-4.4.0/kmail/kmreaderwin.cpp:1535
#20 0x005b645d in KMReaderWin::updateReaderWin (this=0x9d85cf0) at /usr/src/debug/kdepim-4.4.0/kmail/kmreaderwin.cpp:1478
#21 0x005b6d60 in KMReaderWin::update (this=0x9d85cf0, observable=0xa4d4c10) at /usr/src/debug/kdepim-4.4.0/kmail/kmreaderwin.cpp:903
#22 0x007e3962 in KMail::ISubject::notify (this=0xa4d4c10) at /usr/src/debug/kdepim-4.4.0/kmail/isubject.cpp:33
#23 0x004e5075 in KMMessage::updateBodyPart (this=0xa4d4ba0, partSpecifier=..., data=...) at /usr/src/debug/kdepim-4.4.0/kmail/kmmessage.cpp:3185
#24 0x007bbb80 in KMail::ImapJob::slotGetMessageResult (this=0xa4bac50, job=0xa62fc98) at /usr/src/debug/kdepim-4.4.0/kmail/imapjob.cpp:435
#25 0x007bd35f in KMail::ImapJob::qt_metacall (this=0xa4bac50, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0xbf9ab128) at /usr/src/debug/kdepim-4.4.0/i686-redhat-linux-gnu/kmail/imapjob.moc:88
#26 0x06c095db in QMetaObject::metacall (object=0xa4bac50, cl=InvokeMetaMethod, idx=12, argv=0xbf9ab128) at kernel/qmetaobject.cpp:237
#27 0x06c184af in QMetaObject::activate (sender=0xa62fc98, m=0x73b9f08, local_signal_index=3, argv=0xbf9ab128) at kernel/qobject.cpp:3293
#28 0x0722bc84 in KJob::result (this=0xa62fc98, _t1=0xa62fc98) at /usr/src/debug/kdelibs-4.4.0/i686-redhat-linux-gnu/kdecore/kjob.moc:194
#29 0x0722c019 in KJob::emitResult (this=0xa62fc98) at /usr/src/debug/kdelibs-4.4.0/kdecore/jobs/kjob.cpp:312
#30 0x0249fdb3 in KIO::SimpleJob::slotFinished (this=0xa62fc98) at /usr/src/debug/kdelibs-4.4.0/kio/kio/job.cpp:486
#31 0x024a0afe in KIO::TransferJob::slotFinished (this=0xa62fc98) at /usr/src/debug/kdelibs-4.4.0/kio/kio/job.cpp:1058
#32 0x0249ed93 in KIO::TransferJob::qt_metacall (this=0xa62fc98, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0xbf9ab3bc)
at /usr/src/debug/kdelibs-4.4.0/i686-redhat-linux-gnu/kio/jobclasses.moc:367
#33 0x06c095db in QMetaObject::metacall (object=0xa62fc98, cl=InvokeMetaMethod, idx=47, argv=0xbf9ab3bc) at kernel/qmetaobject.cpp:237
#34 0x06c184af in QMetaObject::activate (sender=0x9f9be48, m=0x2663c64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3293
#35 0x0255f098 in KIO::SlaveInterface::finished (this=0x9f9be48) at /usr/src/debug/kdelibs-4.4.0/i686-redhat-linux-gnu/kio/slaveinterface.moc:171
#36 0x025622a5 in KIO::SlaveInterface::dispatch (this=0x9f9be48, _cmd=104, rawdata=...) at /usr/src/debug/kdelibs-4.4.0/kio/kio/slaveinterface.cpp:175
#37 0x0255f504 in KIO::SlaveInterface::dispatch (this=0x9f9be48) at /usr/src/debug/kdelibs-4.4.0/kio/kio/slaveinterface.cpp:91
#38 0x025538c8 in KIO::Slave::gotInput (this=0x9f9be48) at /usr/src/debug/kdelibs-4.4.0/kio/kio/slave.cpp:324
#39 0x02553af3 in KIO::Slave::qt_metacall (this=0x9f9be48, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0xbf9ab6cc) at /usr/src/debug/kdelibs-4.4.0/i686-redhat-linux-gnu/kio/slave.moc:82
#40 0x06c095db in QMetaObject::metacall (object=0x9f9be48, cl=InvokeMetaMethod, idx=30, argv=0xbf9ab6cc) at kernel/qmetaobject.cpp:237
#41 0x06c184af in QMetaObject::activate (sender=0x9f95208, m=0x2660540, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#42 0x0246ad08 in KIO::Connection::readyRead (this=0x9f95208) at /usr/src/debug/kdelibs-4.4.0/i686-redhat-linux-gnu/kio/connection.moc:92
#43 0x0246cdae in KIO::ConnectionPrivate::dequeue (this=0x9f965c0) at /usr/src/debug/kdelibs-4.4.0/kio/kio/connection.cpp:82
#44 0x0246ced6 in KIO::Connection::qt_metacall (this=0x9f95208, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0xa4323e8)
at /usr/src/debug/kdelibs-4.4.0/i686-redhat-linux-gnu/kio/connection.moc:79
#45 0x06c095db in QMetaObject::metacall (object=0x9f95208, cl=InvokeMetaMethod, idx=5, argv=0xa4323e8) at kernel/qmetaobject.cpp:237
#46 0x06c13bd7 in QMetaCallEvent::placeMetaCall (this=0xa4bde80, object=0x9f95208) at kernel/qobject.cpp:561
#47 0x06c14c4e in QObject::event (this=0x9f95208, e=0xa4bde80) at kernel/qobject.cpp:1248
#48 0x07507d2c in QApplicationPrivate::notify_helper (this=0x9bd73a0, receiver=0x9f95208, e=0xa4bde80) at kernel/qapplication.cpp:4300
#49 0x0750e556 in QApplication::notify (this=0xbf9ac0cc, receiver=0x9f95208, e=0xa4bde80) at kernel/qapplication.cpp:3704
#50 0x021c258b in KApplication::notify (this=0xbf9ac0cc, receiver=0x9f95208, event=0xa4bde80) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:302
#51 0x06c04c03 in QCoreApplication::notifyInternal (this=0xbf9ac0cc, receiver=0x9f95208, event=0xa4bde80) at kernel/qcoreapplication.cpp:704
#52 0x06c05ac3 in sendEvent (receiver=0x0, event_type=0, data=0x9ba5f70) at kernel/qcoreapplication.h:215
#53 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9ba5f70) at kernel/qcoreapplication.cpp:1345
#54 0x06c05c1e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238
#55 0x06c2d350 in sendPostedEvents (s=0x9bd9fb0) at kernel/qcoreapplication.h:220
#56 postEventSourceDispatch (s=0x9bd9fb0) at kernel/qeventdispatcher_glib.cpp:276
#57 0x03303f88 in g_main_dispatch (context=<value optimized out>) at gmain.c:1960
#58 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513
#59 0x033078b8 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#60 0x033079e4 in IA__g_main_context_iteration (context=0x9bd9690, may_block=<value optimized out>) at gmain.c:2654
#61 0x06c2ce46 in QEventDispatcherGlib::processEvents (this=0x9ba5c30, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#62 0x075b60c6 in QGuiEventDispatcherGlib::processEvents (this=0x9ba5c30, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#63 0x06c032da in QEventLoop::processEvents (this=0xbf9abf84, flags=...) at kernel/qeventloop.cpp:149
#64 0x06c0361a in QEventLoop::exec (this=0xbf9abf84, flags=...) at kernel/qeventloop.cpp:201
#65 0x06c05ce7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#66 0x07507dd8 in QApplication::exec () at kernel/qapplication.cpp:3579
#67 0x0804aa6a in main (argc=1, argv=0xbf9ac294) at /usr/src/debug/kdepim-4.4.0/kmail/main.cpp:156

The developers will not be reading this forum. Did you complete the bug report as I advised? Please give the bug number so that I can pass it to them.