Bug 292315 - kmail crash while working in the inbox
Summary: kmail crash while working in the inbox
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-01-24 10:54 UTC by Bruno Haible
Modified: 2018-10-27 02:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Crash report (7.08 KB, application/octet-stream)
2012-06-15 09:05 UTC, Axel Braun
Details
crash report (7.92 KB, application/octet-stream)
2012-06-22 07:51 UTC, Axel Braun
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Haible 2012-01-24 10:54:54 UTC
Application: kmail (4.7.4)
KDE Platform Version: 4.7.4 (4.7.4) "release 11"
Qt Version: 4.7.4
Operating System: Linux 3.1.0-1.2-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

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

I had fetched mail (Ctrl-L).
Then I had moved a dozen of mails to a "Spam" folder.
Then I had selected 4 mails and deleted them (Del).
I was selecting a few more mails (with Ctrl-mouse-left), or had selected them and was deleting them (Del).

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

Thread 3 (Thread 0x7fc7792e2700 (LWP 1715)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fc7890369dc in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x00007fc789036b09 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x00007fc7928f5f05 in start_thread (arg=0x7fc7792e2700) at pthread_create.c:301
#4  0x00007fc794ad453d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc7789c9700 (LWP 1716)):
#0  0x00007fc794acb423 in poll () from /lib64/libc.so.6
#1  0x00007fc78cd65a98 in g_main_context_poll (n_fds=1, fds=0x7fc76c002030, timeout=6726, context=0x7fc76c0009b0, priority=<optimized out>) at gmain.c:3386
#2  g_main_context_iterate (context=0x7fc76c0009b0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3068
#3  0x00007fc78cd65f59 in g_main_context_iteration (context=0x7fc76c0009b0, may_block=1) at gmain.c:3136
#4  0x00007fc7960d6576 in QEventDispatcherGlib::processEvents (this=0x7fc76c0008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#5  0x00007fc7960aaa22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007fc7960aac1f in QEventLoop::exec (this=0x7fc7789c8e20, flags=...) at kernel/qeventloop.cpp:201
#7  0x00007fc795fc25df in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#8  0x00007fc795fc5025 in QThreadPrivate::start (arg=0xe84530) at thread/qthread_unix.cpp:331
#9  0x00007fc7928f5f05 in start_thread (arg=0x7fc7789c9700) at pthread_create.c:301
#10 0x00007fc794ad453d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc797729760 (LWP 1688)):
[KCrash Handler]
#6  0x00007fc794a2fd95 in raise () from /lib64/libc.so.6
#7  0x00007fc794a312ab in abort () from /lib64/libc.so.6
#8  0x00007fc79505ef2d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x00007fc79505d0d6 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#10 0x00007fc79505d103 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50
#11 0x00007fc79505d246 in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x00007fc7960aad56 in QEventLoop::exec (this=<optimized out>, flags=<optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007fc7960aede7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#14 0x0000000000402df3 in ?? ()
#15 0x00007fc794a1c23d in __libc_start_main () from /lib64/libc.so.6
#16 0x00000000004032d5 in _start ()

Possible duplicates by query: bug 289446, bug 288240, bug 284551, bug 284493, bug 284118.

Reported using DrKonqi
Comment 1 Laurent Montel 2012-01-24 14:16:20 UTC
not enough info from backtrace :(
Sorry I can't fix this bug.
Comment 2 Axel Braun 2012-06-15 09:05:40 UTC
Created attachment 71849 [details]
Crash report

I have a similar crash: working in the inbox of an POP3 account, deleting a mail, KMail crashed
KDE 4.8.4, openSUSE 12.1 x86
Let me know if this backtrace is useful for you
Comment 3 Axel Braun 2012-06-22 07:51:29 UTC
Created attachment 72036 [details]
crash report

another one bites the dust...on change of folders
Comment 4 Jekyll Wu 2013-09-30 14:08:07 UTC
Unfortunately, the backtrace doesn't contain much helpful information due to uncaught exception (not your fault). 

If you can reproduce the crash every time,  please follow the guide[1] and try to run it under gdb to get a better backtrace.  

[1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 5 Andrew Crouthamel 2018-09-25 03:33:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 02:39:37 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!