Bug 131667 - Kmail crashes at start with only "KCrash: Application 'kmail' crashing..." meassage
Summary: Kmail crashes at start with only "KCrash: Application 'kmail' crashing..." me...
Status: RESOLVED DUPLICATE of bug 110862
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-01 17:07 UTC by Oleg Ruchayskiy
Modified: 2007-09-14 12:17 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 Oleg Ruchayskiy 2006-08-01 17:07:30 UTC
Version:            (using KDE KDE 3.5.3)
Installed from:    Fedora RPMs
OS:                Linux

Very strange crash. I've updated to KDE 3.5.3 (using yum from "kde-redhat-stable-all" repository) under FC3. Everything works fine, Kmail won't start. Kmail won't start without saying much.

I have a pretty wild guess. In my "/var/log/messages" I see the following record on startup

Aug  1 16:47:45 orion kdm: :0[4019]: PAM unable to dlopen(/lib/security/pam_loginuid.so)
Aug  1 16:47:45 orion kdm: :0[4019]: PAM [dlerror: /lib/security/pam_loginuid.so: cannot open shared object file: No such file or directory]
Aug  1 16:47:45 orion kdm: :0[4019]: PAM adding faulty module: /lib/security/pam_loginuid.so

This is due to the fact (I assume) that FC3 uses pam-0.77, while "pam_loginuid.so" is in FC4's pam-0.79. I do not know whether this could be the reason for kmail to crash, in any case I believe that such a silent desperate crash is not a way for a decent application to behave :o)

Below is the backtrace and I will be happy to provide you with any information/experiment with my system if it'll help:

Hope you'll help me -- after so many years of using kmail it's hard to live without it

Oleg
--------------------------------------------------------------------
BACKTRACE

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1246562016 (LWP 4977)]
[KCrash handler]
#6  0xb7c286b6 in KMFolderTree::slotFolderExpanded ()
   from /usr/lib/libkmailprivate.so
#7  0xb7e7cd13 in KMFolderTree::qt_invoke () from /usr/lib/libkmailprivate.so
#8  0xb73d00be in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#9  0xb7717698 in QListView::expanded ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#10 0xb74b2c8c in QListViewItem::setOpen ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0xb7e17fbe in KMFolderTree::addDirectory ()
   from /usr/lib/libkmailprivate.so
#12 0xb7e17fe6 in KMFolderTree::addDirectory ()
   from /usr/lib/libkmailprivate.so
#13 0xb7e18408 in KMFolderTree::reload () from /usr/lib/libkmailprivate.so
#14 0xb7e5aec6 in KMMainWidget::readConfig () from /usr/lib/libkmailprivate.so
#15 0xb7e5ba36 in KMMainWidget::KMMainWidget ()
   from /usr/lib/libkmailprivate.so
#16 0xb7e5bfc6 in KMMainWin::KMMainWin () from /usr/lib/libkmailprivate.so
#17 0xb7e5c329 in KMKernel::mainWin () from /usr/lib/libkmailprivate.so
#18 0xb7e5eb29 in KMail::ImapAccountBase::makeConnection ()
   from /usr/lib/libkmailprivate.so
#19 0xb7e830c6 in KMail::ImapAccountBase::readConfig ()
   from /usr/lib/libkmailprivate.so
#20 0xb7e834d2 in KMAcctImap::readConfig () from /usr/lib/libkmailprivate.so
#21 0xb7d7a4a9 in KMail::AccountManager::readConfig ()
   from /usr/lib/libkmailprivate.so
#22 0xb7ecf885 in KMKernel::init () from /usr/lib/libkmailprivate.so
#23 0x0804a023 in ?? ()
#24 0xbffdc8c0 in ?? ()
#25 0x00000000 in ?? ()
Comment 1 Oleg Ruchayskiy 2006-08-02 10:51:27 UTC
Upon further investigation, it seems that removing 
~/.kde/share/config/kmailrc and ~/.kde/share/config/kmail.eventrc helped.

The problem seems to be in kmail.eventrc, where I have one extra line (as compared to defaults) -- custom "New mail notification". However, kmail crashes on startup, long before it could evoke this "notification"

Comment 2 Tommi Tervo 2006-08-19 13:50:48 UTC

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