Bug 174204 - SIGABRT, KMail, crash, refresh
Summary: SIGABRT, KMail, crash, refresh
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-03 23:02 UTC by Marco Walther
Modified: 2009-03-19 00:34 UTC (History)
2 users (show)

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 Marco Walther 2008-11-03 23:02:04 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

So far, I thought KMail (and Kopete for that matter) would only crash when they were started when my VPN(vpnc) was active and later the vpnc would stop. But today I have this KMail crash while vpnc is still running:

Application: KMail (kmail), signal SIGABRT
(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 0xb41126c0 (LWP 25359)]
(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)
(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)
(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]
#6  0xb7f2c430 in __kernel_vsyscall ()
#7  0xb6392880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6394248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6f15795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb6f15872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb6f15915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7a1d52d in ?? () from /usr/lib/libkmailprivate.so.4
#13 0xb799952e in KMail::AccountManager::~AccountManager ()
   from /usr/lib/libkmailprivate.so.4
#14 0xb7a8911e in KMKernel::cleanup () from /usr/lib/libkmailprivate.so.4
#15 0x0804a6ca in _start ()
#0  0xb7f2c430 in __kernel_vsyscall ()

I'll try to see if I can install the -dbg packages in case, this happens again.
Comment 1 Jaime Torres 2008-11-04 20:41:07 UTC
Hello,
 
Thanks for your report. Unfortunately, the backtrace provided does not carry any useful information. Can have a look at
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports,
try to install the debugging packages for your distribution and post a more
detailed backtrace for the crash? Also giving a step-by-step instruction what
exactly you do in order to make it crash could help.
Comment 2 George Kiagiadakis 2009-01-18 15:58:38 UTC
No information from the reporter for > 2 months. Closing... If it ever happens again, please reopen with an appropriate backtrace.