Bug 285772 - kmail2 crashes on startup
Summary: kmail2 crashes on startup
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-04 18:47 UTC by daniel.schiller
Modified: 2012-03-08 12:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description daniel.schiller 2011-11-04 18:47:32 UTC
Application: kmail (4.7.2)
KDE Platform Version: 4.7.2 (4.7.2) (Compiled from sources)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

since the last update there always has been an error reporting of kmail on shutting down the system. The next time, I started the system again, there where no problems with kmail. But today there was an other update on clamav, which I use for kmial, too. After the update I restarted the system and kmail. Then I reconfigured spamassassin and clamav in kmail. Kmail was doing something and crashed.... I tried to restart kmail, restart akonadi-server and restart the system, but nothing worked. Kmail now always seems to crash on startup.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
[Current thread is 1 (Thread 0x7f15fc81c7a0 (LWP 3497))]

Thread 4 (Thread 0x7f15dcbc4700 (LWP 3501)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f15eeaf4c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f15eeaf4d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f15f773fefc in start_thread (arg=0x7f15dcbc4700) at pthread_create.c:304
#4  0x00007f15f9b9989d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f15dc2c3700 (LWP 3502)):
#0  0x00007f15f145e07b in __GI_clock_gettime (clock_id=1, tp=0x7f15dc2c2ba0) at ../sysdeps/unix/clock_gettime.c:100
#1  0x00007f15fa44a074 in do_gettime (frac=0x7f15dc2c2bb8, sec=0x7f15dc2c2bb0) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x00007f15fa50c6ed in QTimerInfoList::updateCurrentTime (this=0x2926f90) at kernel/qeventdispatcher_unix.cpp:339
#4  0x00007f15fa50c371 in timerSourceCheckHelper (src=<optimized out>) at kernel/qeventdispatcher_glib.cpp:150
#5  timerSourceCheckHelper (src=<optimized out>) at kernel/qeventdispatcher_glib.cpp:144
#6  0x00007f15f25e2734 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f15f25e2f82 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007f15f25e3429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007f15fa50bf3e in QEventDispatcherGlib::processEvents (this=0x2926250, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#10 0x00007f15fa4dfcf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#11 0x00007f15fa4dfef7 in QEventLoop::exec (this=0x7f15dc2c2de0, flags=...) at kernel/qeventloop.cpp:201
#12 0x00007f15fa3f727f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#13 0x00007f15fa3f9d05 in QThreadPrivate::start (arg=0x29254f0) at thread/qthread_unix.cpp:331
#14 0x00007f15f773fefc in start_thread (arg=0x7f15dc2c3700) at pthread_create.c:304
#15 0x00007f15f9b9989d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#16 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f1593fff700 (LWP 3506)):
#0  0x00007f15f25e1f71 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f15f25e2dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f15f25e3429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f15fa50bf3e in QEventDispatcherGlib::processEvents (this=0x2d91680, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f15fa4dfcf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f15fa4dfef7 in QEventLoop::exec (this=0x7f1593ffedb0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f15fa3f727f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007f15fa4c2cbf in QInotifyFileSystemWatcherEngine::run (this=0x2d90360) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f15fa3f9d05 in QThreadPrivate::start (arg=0x2d90360) at thread/qthread_unix.cpp:331
#9  0x00007f15f773fefc in start_thread (arg=0x7f1593fff700) at pthread_create.c:304
#10 0x00007f15f9b9989d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f15fc81c7a0 (LWP 3497)):
[KCrash Handler]
#6  0x00007f15f9aee3a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f15f9af1b0b in __GI_abort () at abort.c:92
#8  0x00007f15fa128d7d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f15fa126f26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f15fa126f53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007f15fa127096 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007f15fa4e002e in QEventLoop::exec (this=<optimized out>, flags=<optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007f15fa4e4789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#14 0x0000000000402bd3 in main (argc=<optimized out>, argv=<optimized out>) at ../../kmail/main.cpp:145

Possible duplicates by query: bug 285748, bug 285599, bug 284950, bug 284718, bug 284551.

Reported using DrKonqi
Comment 1 daniel.schiller 2011-11-04 18:51:40 UTC
Now, after I wrote this bug report, I tried to start kmail again and now it works.... Don't know why.
Comment 2 Laurent Montel 2011-11-04 20:10:51 UTC
With this backtrace we can see pb.
I close it as it works after.
Reopen if you have bug still