[Lucid] kontact / kmail hangs and then crashes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdepim (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kontact
Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic x86_64
Distribution: Ubuntu 10.04 LTS
-- Information about the crash:
I was typing a message in kmail, then it hanged, using 100% CPU. After around 30 seconds I straced it:
stat("/
stat("/
stat("/
in endless loop
Then I terminated the process and I got the kde crash:
-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7f325a662780 (LWP 21894))]
Thread 2 (Thread 0x7f3230e94710 (LWP 21909)):
#0 0x00007f3257743f53 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/
#1 0x00007f32502784a9 in ?? () from /lib/libglib-
#2 0x00007f32502788fc in g_main_
#3 0x00007f3258b2e566 in QEventDispatche
#4 0x00007f3258b03992 in QEventLoop:
#5 0x00007f3258b03d6c in QEventLoop::exec (this=0x7f3230e
#6 0x00007f3258a0dd59 in QThread::exec (this=<value optimized out>) at thread/
#7 0x00007f3258ae4178 in QInotifyFileSys
#8 0x00007f3258a10775 in QThreadPrivate:
#9 0x00007f32527ef9ca in start_thread (arg=<value optimized out>) at pthread_
#10 0x00007f325775069d in clone () at ../sysdeps/
#11 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7f325a662780 (LWP 21894)):
[KCrash Handler]
#5 0x00007f325769da75 in *__GI_raise (sig=<value optimized out>) at ../nptl/
#6 0x00007f32576a15c0 in *__GI_abort () at abort.c:92
#7 0x00007f3258a08844 in qt_message_output (msgType=
#8 0x00007f3258a08a22 in qt_message (msgType=
at global/
#9 0x00007f3258a08bd5 in qFatal (msg=0x5586 <Address 0x5586 out of bounds>) at global/
#10 0x00007f32595c728f in KMainWindow:
#11 0x00007f32387475db in KMKernel:
#12 0x00007f3259561642 in KCrash:
#13 <signal handler called>
#14 0x00007f325769da75 in *__GI_raise (sig=<value optimized out>) at ../nptl/
#15 0x00007f32576a15c0 in *__GI_abort () at abort.c:92
#16 0x00007f32576d74fb in __libc_message (do_abort=<value optimized out>, fmt=<value optimized out>) at ../sysdeps/
#17 0x00007f32576e15b6 in malloc_printerr (action=3, str=0x7f32577b34b8 "munmap_chunk(): invalid pointer", ptr=<value optimized out>) at malloc.c:6264
#18 0x00007f32580c89db in QX11PaintEngine
#19 0x00007f3258004d01 in QScopedPointerD
#20 ~QScopedPointer (this=0x3043350, __in_chrg=<value optimized out>) at ../../include/
#21 ~QPaintEngine (this=0x3043350, __in_chrg=<value optimized out>) at painting/
#22 0x00007f32580bdea0 in ~QX11PaintEngine (this=0x3043350, __in_chrg=<value optimized out>) at painting/
#23 0x00007f3257fb3868 in QX11PixmapData:
#24 0x00007f3257fb409a in ~QX11PixmapData (this=0x339a4f0, __in_chrg=<value optimized out>) at image/qpixmap_
#25 0x00007f3257fa1e69 in ~QExplicitlySha
#26 ~QPixmap (this=0x2f17508, __in_chrg=<value optimized out>) at image/qpixmap.
#27 0x00007f323fa983b5 in ?? () from /usr/lib/
#28 0x00007f323fa983fe in ?? () from /usr/lib/
#29 0x00007f323faabdef in ?? () from /usr/lib/
#30 0x00007f32576a3262 in __run_exit_handlers (status=1) at exit.c:78
#31 *__GI_exit (status=1) at exit.c:100
#32 0x00007f32479ac476 in ?? () from /usr/lib/
#33 0x00007f32594ed288 in KApplication:
#34 0x00007f3251e767fe in _XIOError () from /usr/lib/
#35 0x00007f3251e7e355 in ?? () from /usr/lib/
#36 0x00007f3251e7ec07 in _XEventsQueued () from /usr/lib/
#37 0x00007f3251e6740b in XEventsQueued () from /usr/lib/
#38 0x00007f3257f6e697 in x11EventSourceP
#39 0x00007f3250277eb1 in g_main_
#40 0x00007f3250278318 in ?? () from /lib/libglib-
#41 0x00007f32502788fc in g_main_
#42 0x00007f3258b2e513 in QEventDispatche
#43 0x00007f3257f6e46e in QGuiEventDispat
#44 0x00007f3258b03992 in QEventLoop:
#45 0x00007f3258b03d6c in QEventLoop::exec (this=0x7fff5d9
#46 0x00007f3258b07aab in QCoreApplicatio
#47 0x0000000000403e8e in _start ()
Report to https:/
Hi there!
Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: https:/ /bugs.kde. org/show_ bug.cgi? id=226282
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.
Thanks!