Kmail crash: "Could not create collection outbox, resourceId 15"
Hi, I just got a kmail crash out of the blue with a message "Could not create collection outbox, resourceId 15" I updated a few weeks back to Debian 12, but apart from that I am not aware of any updates. I tried to run akonadictl fsck and got a similar result [...] org.kde.pim.akonadiserver: Error during insertion into table "CollectionTable" "Duplicate entry '8-outbox' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Der Befehl konnte nicht ausgeführt werden" org.kde.pim.akonadiserver: Failed to append Collection "outbox" in resource "akonadi_maildir_resource_0" org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Could not create collection outbox, resourceId 15" org.kde.pim.akonadiserver: Error while handling command CreateCollection on connection akonadi_maildispatcher_agent (0x555c6ad0ccc0) org.kde.pim.maildispatcher: Failed to get outbox folder. Giving up. org.kde.pim.akonadicore: Failed CollectionCreateJob. "Could not create collection outbox, resourceId 15" I am wondering if https://userbase.kde.org/KMail/ FAQs_Hints_and_Tips#Clean_start_after_a_failed_migration is still the correct way to fix this. Unfortunately, this implies to configure all the accounts, identities, folders etc. again. I am wondering why resetting the cached imap etc. data requires to reset all user configuration data as well. Many thanks Rainer signature.asc Description: This is a digitally signed message part.
Re: kmail crash
Graham Smith skrev: Ok, I couldn't find out specifically what was wrong but hunting around I heard quite a few people mentioning corrupt index files being a problem. I moved the contents of ~/.kde/share/apps/kmail/imap to another folder and tried kmail again (well kontact actually) and it worked. Of course this leads to two questions: what went wrong and how can I stop it going wrong again? I suppose there is a third as well: what can I do to help fix this exceedingly annoying bug? I'll file a bug report but it won't be much use as I have basically no information to go on. You are not alone. See this bug report: http://bugs.kde.org/show_bug.cgi?id=122124 Anders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kmail crash
Ok, I couldn't find out specifically what was wrong but hunting around I heard quite a few people mentioning corrupt index files being a problem. I moved the contents of ~/.kde/share/apps/kmail/imap to another folder and tried kmail again (well kontact actually) and it worked. Of course this leads to two questions: what went wrong and how can I stop it going wrong again? I suppose there is a third as well: what can I do to help fix this exceedingly annoying bug? I'll file a bug report but it won't be much use as I have basically no information to go on. Graham On Thursday 16 February 2006 12:45, Graham Smith wrote: > Hi, > > I am having some trouble starting kmail. This has happened a few times > recently but normally seems to fix itself (it's not this time though). > > Starting kmail from the command line gives the output shown below. This > crash, I have noticed, is normally associated with kmail losing all my > per folder settings which is very annoying. > > Anyone got any ideas what's wrong? > > Many thanks, > > Graham > > kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] > ignoring empty path > kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] > ignoring empty path > kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] > ignoring empty path > kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] > ignoring empty path > kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] > ignoring empty path > kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] > ignoring empty path > kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] > ignoring empty path > WeaverThreadLogger: thread (ID: 1) suspended. > WeaverThreadLogger: thread (ID: 2) suspended. > WeaverThreadLogger: thread (ID: 3) suspended. > WeaverThreadLogger: thread (ID: 4) suspended. > kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated > action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa13340 ): > KAccel object already contains an action name "delete" > kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated > action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa13340 ): > KAccel object already contains an action name "edit" > kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated > action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa13340 ): > KAccel object already contains an action name "display_message" > [EMAIL PROTECTED]:/tmp$ *** KMail got signal 11 (Crashing) > KCrash: Application 'kmail' crashing... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kmail crash
Hi all First of all, I hope I'm talking the right mailing-list, and if not, I'm sorry to disturb. I'm using debian sarge, with this : Qt: 3.3.4 KDE: 3.3.2 KMail: 1.7.2 For a few days now, I have a problem with Kmail, which is reproductible : - I open a mail (double-click on it, so it's in its own window) - right-click --> save as... : I give it a name, etc... - I click on the main Kmail window : Kmail just crashes. I have attached the report : it this a known bug ? how could I solve that ? Don't forget that I would prefer to stay in stable KDE. And please, email-me the answer, as I'm not subscribed to the list. Thanks in advance. Nicolas --- CNRS - UPR 9080 : Laboratoire de Biochimie Theorique Institut de Biologie Physico-Chimique 13 rue Pierre et Marie Curie 75005 PARIS - FRANCE Tel : +33 158 41 51 70 Fax : +33 158 41 50 26 KrashKonqueror Description: Binary data
Re: kmail crash
Graham Smith wrote: > This > crash, I have noticed, is normally associated with kmail losing all my > per folder settings which is very annoying. > ime, _every_ KMail crash is associated with losing all per-folder settings. You're right, that's very annoying. Sorry, I can't help with the actual problem. -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kmail crash
Hi, I am having some trouble starting kmail. This has happened a few times recently but normally seems to fix itself (it's not this time though). Starting kmail from the command line gives the output shown below. This crash, I have noticed, is normally associated with kmail losing all my per folder settings which is very annoying. Anyone got any ideas what's wrong? Many thanks, Graham kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa13340 ): KAccel object already contains an action name "delete" kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa13340 ): KAccel object already contains an action name "edit" kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa13340 ): KAccel object already contains an action name "display_message" [EMAIL PROTECTED]:/tmp$ *** KMail got signal 11 (Crashing) KCrash: Application 'kmail' crashing... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kontact / Kmail crash on start up
I believe this is a known bug; check KDE bug 106030. I had to downgrade to 1.8.3 for now. Contribute some backtraces if you want, and definitely vote for the bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kontact / Kmail crash on start up
On Thursday 26 January 2006 18:02, [EMAIL PROTECTED] wrote: > Am Donnerstag, 26. Januar 2006 09:45 schrieb Graham Smith: > > Does anyone have any idea what is going on? More specifically any idea on > > how I can stop this happening :o) > > start kmail from the kosole and watch the messages > > check the permissions on your files ~/mail and /.kde/... Hi, thanks for the help. I have a some more information about the problem... My main Kmail account is am IMAP account connecting to a Courier IMAP server (which I run). The problem only seems to occur after I first start the computer and seems to be associated with new messages in the inbox. For instance, this morning the problem happened again and my work around (moving the messages with thunderbird) worked perfectly again. Oddly though this morning it didn't loose all the settings. Folders that I threaded yesterday are still threaded today. I checked the permissions of ~/Mail and ~/.kde and their sub-folders and they are fine read write me and nothing for anyone else. I forgot to start Kmail from the command line again to get the output but I will do that next time the problem surfaces (tomorrow morning). This problem is driving me nuts :o) Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kontact / Kmail crash on start up
Am Donnerstag, 26. Januar 2006 09:45 schrieb Graham Smith: > Does anyone have any idea what is going on? More specifically any idea on > how I can stop this happening :o) > start kmail from the kosole and watch the messages check the permissions on your files ~/mail and /.kde/... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kontact / Kmail crash on start up
Hi, I'm running AMD64 sid and I am experiencing an exceedingly annoying problem with Kontact. I think the problem is actually Kmail as when I try and run Kmail on it's own I see the same problem. Anyway, the symptoms: When I start Kontact almost immediately exits with a SIGSEGV. It last just about long enough to flash up the window before exiting. Starting it from the command line doesn't really show anything useful (Sorry I forgot to get the output). Repeatedly opening kontact or kmail shows exactly the same behaviour every time. The only way I have found to fix this is to open thunderbird (or another mail client) and move the message in the inbox into another folder (eg delete my spam). Then kmail works fine. Thinking it was choking on one of the messages I tried moving them back into the inbox to see if that would trigger the problem again - it didn't. The most annoying part of the problem, however, is that kmail forgets some of it's settings when this problem occurs. In particular it forgets all per directory settings such as expiry times and "act on new mail in this folder" settings. Does anyone have any idea what is going on? More specifically any idea on how I can stop this happening :o) Cheers, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kmail crash
On Friday 19 August 2005 10:29, Marco Calviani wrote: > Hi Debian-kde, >i'm trying to use kmail 1.8 with KDE 3.4.1 from Alioth. Sometimes > (very often) kmail crashes and give this backtrace: this one was > produces by clicking on the "subject" button on the message list, but it > happens also with other commands: > [...] > [KCrash handler] > #3 0xb74a108e in QGDict::look_string () from /usr/lib/libqt-mt.so.3 > #4 0xb7cdbb51 in KMHeaders::writeSortOrder () >from /usr/lib/libkmailprivate.so > #5 0xb7cdb038 in KMHeaders::setSorting () from /usr/lib/libkmailprivate.so > #6 0xb7cdce04 in KMHeaders::dirtySortOrder () >from /usr/lib/libkmailprivate.so > #7 0xb7ce0a27 in KMHeaders::qt_invoke () from /usr/lib/libkmailprivate.so > #8 0xb71eb696 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 > #9 0xb71eb87d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 > #10 0xb7537c02 in QHeader::clicked () from /usr/lib/libqt-mt.so.3 > #11 0xb72a35df in QHeader::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 > #12 0xb7221b37 in QWidget::event () from /usr/lib/libqt-mt.so.3 > #13 0xb718ee1f in QApplication::internalNotify () from > /usr/lib/libqt-mt.so.3 > #14 0xb718e514 in QApplication::notify () from /usr/lib/libqt-mt.so.3 > #15 0xb7740ac5 in KApplication::notify () from /usr/lib/libkdecore.so.4 > #16 0xb71235b0 in QETWidget::translateMouseEvent () >from /usr/lib/libqt-mt.so.3 > #17 0xb712123e in QApplication::x11ProcessEvent () from > /usr/lib/libqt-mt.so.3 > #18 0xb7138254 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 > #19 0xb71a11d8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 > #20 0xb71a1088 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 > #21 0xb718f071 in QApplication::exec () from /usr/lib/libqt-mt.so.3 > #22 0x0804a0b4 in ?? () > #23 0xb9b0 in ?? () > #24 0xb8c0 in ?? () > #25 0x in ?? () > #26 0x in ?? () > #27 0xb7632c40 in vtable for QGArray () from /usr/lib/libqt-mt.so.3 > #28 0x08128678 in ?? () > #29 0xb7a02618 in __malloc_initialize_hook () from /lib/tls/libc.so.6 > #30 0xb7a02218 in __malloc_initialize_hook () from /lib/tls/libc.so.6 > #31 0xb7fb27d0 in vtable for KMKernel () from /usr/lib/libkmailprivate.so > #32 0xb78e1ec0 in __libc_start_main () from /lib/tls/libc.so.6 > #33 0xb78e1ec0 in __libc_start_main () from /lib/tls/libc.so.6 > #34 0x08049e11 in ?? () > > > > Any clues from other users of kmail from alioth? > > MC Don't know if this is related, but kontact (kmail) has crashed a few times with this stack trace that has to do with QGDict as well: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -122064 (LWP 19386)] [KCrash handler] #3 0x41f54b03 in QGDict::clear () from /usr/lib/libqt-mt.so.3 #4 0xb69edec5 in KMFolderCachedImap::listMessages () from /usr/lib/libkmailprivate.so #5 0xb69ec68e in KMFolderCachedImap::serverSyncInternal () from /usr/lib/libkmailprivate.so #6 0xb69ef62f in KMFolderCachedImap::listDirectory2 () from /usr/lib/libkmailprivate.so #7 0xb69ec2d2 in KMFolderCachedImap::serverSyncInternal () from /usr/lib/libkmailprivate.so #8 0xb69ef0b4 in KMFolderCachedImap::slotListResult () from /usr/lib/libkmailprivate.so #9 0xb69f25d6 in KMFolderCachedImap::qt_invoke () from /usr/lib/libkmailprivate.so #10 0x41c9df9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11 0xb690b177 in KMail::ListJob::receivedFolders () from /usr/lib/libkmailprivate.so #12 0xb690a58c in KMail::ListJob::slotListResult () from /usr/lib/libkmailprivate.so #13 0xb690b23d in KMail::ListJob::qt_invoke () from /usr/lib/libkmailprivate.so #14 0x41c9df9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #15 0x42269eea in KIO::Job::result (this=0x897caf8, t0=0x4114e1f0) at jobclasses.moc:156 #16 0x422521dc in KIO::Job::emitResult (this=0x897caf8) at job.cpp:218 #17 0x422536fc in KIO::SimpleJob::slotFinished (this=0x897caf8) at job.cpp:547 #18 0x4225c74e in KIO::ListJob::slotFinished (this=0x897caf8) at job.cpp:2050 #19 0x4226d343 in KIO::ListJob::qt_invoke (this=0x897caf8, _id=16, _o=0xbfffee60) at jobclasses.moc:1713 #20 0x41c9df9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0x41c9ddc4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #22 0x422483ee in KIO::SlaveInterface::finished (this=0x4114e1f0) at qmetaobject.h:261 #23 0x42246f51 in KIO::SlaveInterface::dispatch (this=0x89b8850, _cmd=104, [EMAIL PROTECTED]) at slaveinterface.cpp:243 #24 0x42246459 in KIO::SlaveInterface::dispatch (this=0x89b8850) at slaveinterface.cpp:173 #25 0x42243e8b in KIO::Slave::gotInput (this=0x89b8850) at slave.cpp:300 #26 0x42245ba8 in KIO::Slave::qt_invoke (this=0x89b8850, _id=4,
Re: kmail crash
Tommi Tervo wrote: In linux.debian.maint.kde, you wrote: Hi Debian-kde, i'm trying to use kmail 1.8 with KDE 3.4.1 from Alioth. Sometimes (very often) kmail crashes and give this backtrace: this one was produces by clicking on the "subject" button on the message list, but it happens also with other commands: Do you have installed kdelibs-data package from unstable? ii kdelibs-data3.4.2-1 For me kmail started to crash after that package updated. You propably have to unroll back to aliot-version, because that c++ transition. HTH, HAND T Thanks, but unfortunately i don't have it installed, i have still the 3.4.1 alioth version, since i've stop on kde upgrading as long as the KDE mantainer did not send the awaited mail! (http://lists.debian.org/debian-kde/2005/08/msg00089.html) Regards, MC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kmail crash
Hi Debian-kde, i'm trying to use kmail 1.8 with KDE 3.4.1 from Alioth. Sometimes (very often) kmail crashes and give this backtrace: this one was produces by clicking on the "subject" button on the message list, but it happens also with other commands: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xe000' has disappeared; keeping its symbols. (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 -1246894400 (LWP 9270)] (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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #3 0xb74a108e in QGDict::look_string () from /usr/lib/libqt-mt.so.3 #4 0xb7cdbb51 in KMHeaders::writeSortOrder () from /usr/lib/libkmailprivate.so #5 0xb7cdb038 in KMHeaders::setSorting () from /usr/lib/libkmailprivate.so #6 0xb7cdce04 in KMHeaders::dirtySortOrder () from /usr/lib/libkmailprivate.so #7 0xb7ce0a27 in KMHeaders::qt_invoke () from /usr/lib/libkmailprivate.so #8 0xb71eb696 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0xb71eb87d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #10 0xb7537c02 in QHeader::clicked () from /usr/lib/libqt-mt.so.3 #11 0xb72a35df in QHeader::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 #12 0xb7221b37 in QWidget::event () from /usr/lib/libqt-mt.so.3 #13 0xb718ee1f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #14 0xb718e514 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #15 0xb7740ac5 in KApplication::notify () from /usr/lib/libkdecore.so.4 #16 0xb71235b0 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #17 0xb712123e in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #18 0xb7138254 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #19 0xb71a11d8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #20 0xb71a1088 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #21 0xb718f071 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #22 0x0804a0b4 in ?? () #23 0xb9b0 in ?? () #24 0xb8c0 in ?? () #25 0x in ?? () #26 0x in ?? () #27 0xb7632c40 in vtable for QGArray () from /usr/lib/libqt-mt.so.3 #28 0x08128678 in ?? () #29 0xb7a02618 in __malloc_initialize_hook () from /lib/tls/libc.so.6 #30 0xb7a02218 in __malloc_initialize_hook () from /lib/tls/libc.so.6 #31 0xb7fb27d0 in vtable for KMKernel () from /usr/lib/libkmailprivate.so #32 0xb78e1ec0 in __libc_start_main () from /lib/tls/libc.so.6 #33 0xb78e1ec0 in __libc_start_main () from /lib/tls/libc.so.6 #34 0x08049e11 in ?? () Any clues from other users of kmail from alioth? MC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subje
Re: KMail Crash With Multi-Level Folders
Am Dienstag, 22. Juni 2004 15:52 schrieb Robert Tilley: > > But anyway, did you try something at all? Disabling single filter entries > > would be a good start... > I have search the KMail documentation for the term "single filter" without > result. Please provide a humble KDE user with such information, if you so > possess it. Are you nuts? My english may not be perfect but is the above so hard to understand? "disabling single filter entries" -> disable filter entries one by one until it does not crash you got it now? HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org
Re: KMail Crash With Multi-Level Folders
> But anyway, did you try something at all? Disabling single filter entries > would be a good start... > > HS I have search the KMail documentation for the term "single filter" without result. Please provide a humble KDE user with such information, if you so possess it. Bob (Yes, I do know about Google and will visit it shortly.) -- Your lucky color has faded.
Re: KMail Crash With Multi-Level Folders
Am Sonntag, 20. Juni 2004 21:58 schrieb Robert Tilley: > I began using a two-level tier of folders > (Inbox->FirstLevel->Second.1,Second.2, etc.) > for email storage. > > When a large group of email (more than about 50) is filtered, KMail quickly > crashes with the following backtrace: What do you want with the backtrace here? This is not a KMail development list. But anyway, did you try something at all? Disabling single filter entries would be a good start... HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org
KMail Crash With Multi-Level Folders
I began using a two-level tier of folders (Inbox->FirstLevel->Second.1,Second.2, etc.) for email storage. When a large group of email (more than about 50) is filtered, KMail quickly crashes with the following backtrace: This backtrace appears to be useless. This is probably because your packages are built in a way which prevents creating of proper backtraces, or the stack frame was seriously corrupted in the crash. (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)... [Thread debugging using libthread_db enabled] [New Thread 1107680928 (LWP 30270)] (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)...0x41b8b40e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #0 0x41b8b40e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #1 0x41303dd0 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #2 #3 0x41e98893 in __after_morecore_hook () from /lib/tls/libc.so.6 #4 0x417b56e4 in QListViewItem::firstChild () from /usr/lib/libqt-mt.so.3 #5 0x401c6469 in KMHeaders::msgRemoved () from /usr/lib/libkmailprivate.so.0 #6 0x401d0ab4 in KMHeaders::qt_invoke () from /usr/lib/libkmailprivate.so.0 #7 0x416d3e9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #8 0x40205c02 in KMFolder::msgRemoved () from /usr/lib/libkmailprivate.so.0 #9 0x40202866 in KMFolder::take () from /usr/lib/libkmailprivate.so.0 #10 0x402bc61c in KMFolderMaildir::take () from /usr/lib/libkmailprivate.so.0 #11 0x402b97b9 in KMFolderMaildir::addMsg () from /usr/lib/libkmailprivate.so.0 #12 0x40202ec8 in KMFolder::moveMsg () from /usr/lib/libkmailprivate.so.0 #13 0x4024e0aa in KMFilterMgr::process () from /usr/lib/libkmailprivate.so.0 #14 0x401c6f5e in KMHeaders::slotFilterMsg () from /usr/lib/libkmailprivate.so.0 #15 0x401c7912 in KMHeaders::applyFiltersOnMsg () from /usr/lib/libkmailprivate.so.0 #16 0x4033a55a in KMMainWidget::slotApplyFilters () from /usr/lib/libkmailprivate.so.0 #17 0x40332aa9 in KMMainWidget::qt_invoke () from /usr/lib/libkmailprivate.so.0 #18 0x416d3e9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #19 0x416d3cc4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #20 0x41046acb in KAction::activated () from /usr/lib/libkdeui.so.4 #21 0x410464af in KAction::slotActivated () from /usr/lib/libkdeui.so.4 #22 0x41046cd1 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4 #23 0x416d3e9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #24 0x416d3cc4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #25 0x412fe38b in KAccelPrivate::menuItemActivated () from /usr/lib/libkdecore.so.4 #26 0x412fcc0c in KAccelPrivate::eventFilter () from /usr/lib/libkdecore.so.4 #27 0x416d19be in QObject::activate_filters () from /usr/lib/libqt-mt.so.3 #28 0x416d18ec in QObject
Kmail Crash for unknown gpg keys
I have kmail installed whith crypto-plugin compiled as told at: http://kmail.kde.org/kmail-pgpmime-howto.html But I have two problems: 1) It happens sometimes when I'm typing my gpg-key password that pinentry exits when I type too fast. I meen when two letters are entered very fastly ;-). So it comes back to the mail editor and tells me my password is incorrect. Sometimes I have to type it five or six times for it to be accepted. 2) Kmail crashes when I want to see a signed mail I don't have the key i my keyring. (It doesn't crashes fully since I have to wait for 2 or 3 min before it comes back). It is a heavy loss of time when reading this list ;-). I use sarge (testing) and I tried to recompile all the OpenPGP plugin for Kmail but it didn't change anything. I don't want to try again because of the mess there is in sarge for QT libs (I can't compile or install any package using them). I use this plugin: "gpgme-openpgp.so". There is another ".so" file in the same dir called "gpgme-smime.so" but seems it is useless for Kmail. If someone can help me. thank you -- Germs pgpZoJZqrjolo.pgp Description: signature
Kmail Crash with kde 3.1.1 and debian testing
Hi all, I've just upgrade my Kde distribution from the third time from kde 2.2 to kde 3.1.1 with a debian testing system. I've got pb with the xfstt font server. I remove it and evrything work fine but not kmail. I have previously remove every configuration files from my homedir (.kde, .kderc) and from /etc/kde3 .I have also made a mv of my Mail directory. So normaly everything start from scratch kmail crashs with the message: kmail: relocation error: kmail: undefined symbol: _8DwString.npos A ldd /usr/bin/kmail gives me: libkhtml.so.4 => /usr/lib/libkhtml.so.4 (0x40021000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40223000) libkdeprint.so.4 => /usr/lib/libkdeprint.so.4 (0x4024) libkparts.so.2 => /usr/lib/libkparts.so.2 (0x402d1000) libkutils.so.1 => /usr/lib/libkutils.so.1 (0x40303000) libkspell.so.4 => /usr/lib/libkspell.so.4 (0x40314000) libkdenetwork.so.2 => /usr/lib/libkdenetwork.so.2 (0x4032e000) libmimelib.so.1 => /usr/lib/libmimelib.so.1 (0x403d8000) libkabc.so.1 => /usr/lib/libkabc.so.1 (0x40408000) libvcard.so.0 => /usr/lib/libvcard.so.0 (0x4047) libkio.so.4 => /usr/lib/libkio.so.4 (0x40492000) libkdeui.so.4 => /usr/lib/libkdeui.so.4 (0x406ca000) libkdesu.so.4 => /usr/lib/libkdesu.so.4 (0x408ba000) libkdecore.so.4 => /usr/lib/libkdecore.so.4 (0x408d3000) libDCOP.so.4 => /usr/lib/libDCOP.so.4 (0x40a43000) libdl.so.2 => /lib/libdl.so.2 (0x40a7) libresolv.so.2 => /lib/libresolv.so.2 (0x40a73000) libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0x40a83000) libkdefx.so.4 => /usr/lib/libkdefx.so.4 (0x40a98000) libqt-mt.so.3 => /usr/lib/libqt-mt.so.3 (0x40abf000) libpng.so.3 => /usr/lib/libpng.so.3 (0x41057000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4107f000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4108c000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x41146000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x4114e000) libpthread.so.0 => /lib/libpthread.so.0 (0x41165000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x411b4000) libutil.so.1 => /lib/libutil.so.1 (0x411b9000) libz.so.1 => /lib/libz.so.1 (0x411bc000) libfam.so.0 => /usr/lib/libfam.so.0 (0x411c9000) libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x411d2000) libm.so.6 => /lib/libm.so.6 (0x4121c000) libc.so.6 => /lib/libc.so.6 (0x4123d000) libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x4134d000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x413f6000) libaudio.so.2 => /usr/lib/libaudio.so.2 (0x413ff000) libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x41413000) libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x4145d000) libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x414c3000) libXft.so.1 => /usr/X11R6/lib/libXft.so.1 (0x414d7000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x4150) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) Any Idea? Please could you also reply to my personal email addresse. Thank's a lot for your help. I've got all my mail in this diretory ... Francois
Kmail Crash with kde 3.1.1 and testing
Hi all, I've just upgrade from the third time from kde 2.2 to kde 3.1.1 with a debian testing. I've got pb with the xfstt font server. I remove it and evrything work fine but kmail. I have previously remove every configuration files from my homedir (.kde, .kderc) and from /etc/kde3 And I have also made a mv of my Mail directory. So normaly everything start from scratch kmail crashs with the message: kmail: relocation error: kmail: undefined symbol: _8DwString.npos A ldd /usr/bin/kmail gives me: libkhtml.so.4 => /usr/lib/libkhtml.so.4 (0x40021000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40223000) libkdeprint.so.4 => /usr/lib/libkdeprint.so.4 (0x4024) libkparts.so.2 => /usr/lib/libkparts.so.2 (0x402d1000) libkutils.so.1 => /usr/lib/libkutils.so.1 (0x40303000) libkspell.so.4 => /usr/lib/libkspell.so.4 (0x40314000) libkdenetwork.so.2 => /usr/lib/libkdenetwork.so.2 (0x4032e000) libmimelib.so.1 => /usr/lib/libmimelib.so.1 (0x403d8000) libkabc.so.1 => /usr/lib/libkabc.so.1 (0x40408000) libvcard.so.0 => /usr/lib/libvcard.so.0 (0x4047) libkio.so.4 => /usr/lib/libkio.so.4 (0x40492000) libkdeui.so.4 => /usr/lib/libkdeui.so.4 (0x406ca000) libkdesu.so.4 => /usr/lib/libkdesu.so.4 (0x408ba000) libkdecore.so.4 => /usr/lib/libkdecore.so.4 (0x408d3000) libDCOP.so.4 => /usr/lib/libDCOP.so.4 (0x40a43000) libdl.so.2 => /lib/libdl.so.2 (0x40a7) libresolv.so.2 => /lib/libresolv.so.2 (0x40a73000) libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0x40a83000) libkdefx.so.4 => /usr/lib/libkdefx.so.4 (0x40a98000) libqt-mt.so.3 => /usr/lib/libqt-mt.so.3 (0x40abf000) libpng.so.3 => /usr/lib/libpng.so.3 (0x41057000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4107f000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4108c000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x41146000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x4114e000) libpthread.so.0 => /lib/libpthread.so.0 (0x41165000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x411b4000) libutil.so.1 => /lib/libutil.so.1 (0x411b9000) libz.so.1 => /lib/libz.so.1 (0x411bc000) libfam.so.0 => /usr/lib/libfam.so.0 (0x411c9000) libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x411d2000) libm.so.6 => /lib/libm.so.6 (0x4121c000) libc.so.6 => /lib/libc.so.6 (0x4123d000) libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x4134d000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x413f6000) libaudio.so.2 => /usr/lib/libaudio.so.2 (0x413ff000) libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x41413000) libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x4145d000) libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x414c3000) libXft.so.1 => /usr/X11R6/lib/libXft.so.1 (0x414d7000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x4150) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) Any Idea? Please could you also reply to my personal email addresse. Thank's a lot for your help. I've got all my mail in this Mail diretory Francois with
Re: KMail crash on attaching a file (Debian testing packages)
On Wednesday 02 January 2002 07:01 am, Rachel Andrew wrote: > hy> > Resent-From: debian-kde@lists.debian.org > X-Mailing-List: archive/latest/6129 > X-Loop: debian-kde@lists.debian.org > Precedence: list > Resent-Sender: [EMAIL PROTECTED] > > Hi > > I have a Debian Woody system with the KDE packages from testing, all is > running really well apart from a couple of issues with KMail, the worst of > which is if I try to attach a file it crashes with a Signal 11, when I OK > the file I have selected by browsing to it. I've pasted the backtrace > below. The crash happens every time i try to attach a file. > > Its a standard up to date install from the testing packages on an Athlon > 1gig machine, Abit KT7A mainboard. > > Rachel > > (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)... > (no debugging symbols found)...0x40fd78f9 in wait4 () > from /lib/libc.so.6 > #0 0x40fd78f9 in wait4 () from /lib/libc.so.6 > #1 0x410501f0 in __check_rhosts_file () from /lib/libc.so.6 > #2 0x407e70b8 in KCrash::defaultCrashHandler () from > /usr/lib/libkdecore.so.3 #3 0x40f60848 in sigaction () from /lib/libc.so.6 > #4 0x080cfecd in KDialog::marginHint () > #5 0x080ad0d9 in KDialog::marginHint () > #6 0x40492a6f in KIO::Job::result () from /usr/lib/libkio.so.3 > #7 0x40479d7c in KIO::Job::emitResult () from /usr/lib/libkio.so.3 > #8 0x4047ab96 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.3 > #9 0x4047ccc1 in KIO::TransferJob::slotFinished () from > /usr/lib/libkio.so.3 #10 0x40a6ea0d in QObject::activate_signal () from > /usr/lib/libqt.so.2 #11 0x4046ccd5 in KIO::SlaveInterface::finished () from > /usr/lib/libkio.so.3 #12 0x4046911c in KIO::SlaveInterface::dispatch () > from /usr/lib/libkio.so.3 #13 0x40468e68 in KIO::SlaveInterface::dispatch > () from /usr/lib/libkio.so.3 #14 0x40467aa0 in KIO::Slave::gotInput () from > /usr/lib/libkio.so.3 #15 0x40a6ecce in QObject::activate_signal () from > /usr/lib/libqt.so.2 #16 0x40ac6658 in QSocketNotifier::activated () from > /usr/lib/libqt.so.2 #17 0x40aa5242 in QSocketNotifier::event () from > /usr/lib/libqt.so.2 #18 0x40a1aa87 in QApplication::notify () from > /usr/lib/libqt.so.2 #19 0x40755da4 in KApplication::notify () from > /usr/lib/libkdecore.so.3 #20 0x409e53ba in qt_set_socket_handler () from > /usr/lib/libqt.so.2 #21 0x409e > 5abe in QApplication::processNextEvent () from /usr/lib/libqt.so.2 > #22 0x40a1cf4f in QApplication::enter_loop () from /usr/lib/libqt.so.2 > #23 0x409ec9c3 in QApplication::exec () from /usr/lib/libqt.so.2 > #24 0x08133ae3 in KDialog::marginHint () > #25 0x40f5065f in __libc_start_main () from /lib/libc.so.6 Rachel: That is correct. If you are running a pure Woody box, then parts of KDE are broken and we are kind of in limbo waiting for some new packages to trickle down from Sid to fix these problems. An option is to install the Sid version of KDE, or wait until the repaired newer packages make it into Woody. tatah -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
KMail crash on attaching a file (Debian testing packages)
Hi I have a Debian Woody system with the KDE packages from testing, all is running really well apart from a couple of issues with KMail, the worst of which is if I try to attach a file it crashes with a Signal 11, when I OK the file I have selected by browsing to it. I've pasted the backtrace below. The crash happens every time i try to attach a file. Its a standard up to date install from the testing packages on an Athlon 1gig machine, Abit KT7A mainboard. Rachel (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)... (no debugging symbols found)...0x40fd78f9 in wait4 () from /lib/libc.so.6 #0 0x40fd78f9 in wait4 () from /lib/libc.so.6 #1 0x410501f0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x407e70b8 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3 #3 0x40f60848 in sigaction () from /lib/libc.so.6 #4 0x080cfecd in KDialog::marginHint () #5 0x080ad0d9 in KDialog::marginHint () #6 0x40492a6f in KIO::Job::result () from /usr/lib/libkio.so.3 #7 0x40479d7c in KIO::Job::emitResult () from /usr/lib/libkio.so.3 #8 0x4047ab96 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.3 #9 0x4047ccc1 in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.3 #10 0x40a6ea0d in QObject::activate_signal () from /usr/lib/libqt.so.2 #11 0x4046ccd5 in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.3 #12 0x4046911c in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.3 #13 0x40468e68 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.3 #14 0x40467aa0 in KIO::Slave::gotInput () from /usr/lib/libkio.so.3 #15 0x40a6ecce in QObject::activate_signal () from /usr/lib/libqt.so.2 #16 0x40ac6658 in QSocketNotifier::activated () from /usr/lib/libqt.so.2 #17 0x40aa5242 in QSocketNotifier::event () from /usr/lib/libqt.so.2 #18 0x40a1aa87 in QApplication::notify () from /usr/lib/libqt.so.2 #19 0x40755da4 in KApplication::notify () from /usr/lib/libkdecore.so.3 #20 0x409e53ba in qt_set_socket_handler () from /usr/lib/libqt.so.2 #21 0x409e5abe in QApplication::processNextEvent () from /usr/lib/libqt.so.2 #22 0x40a1cf4f in QApplication::enter_loop () from /usr/lib/libqt.so.2 #23 0x409ec9c3 in QApplication::exec () from /usr/lib/libqt.so.2 #24 0x08133ae3 in KDialog::marginHint () #25 0x40f5065f in __libc_start_main () from /lib/libc.so.6
