Kontact SIGSERVs after upgrade to KDE 3.5.10 when opening calendar after new mail has been received

Bug #288145 reported by Daniel Kulesz
4
Affects Status Importance Assigned to Milestone
KDE PIM
New
Unknown
kdepim (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: kontact

Hi,

i have recently upgraded from KDE 3.5.9 to KDE 3.5.10 via the package manager in Kubuntu 8.0.4. ( i have also kde 4.1.2 installed using the repositories from the kubuntu website) Since then, I have experienced reproducible crashes in kontact. Here is the instructions:

1.) start up kontact
2.) receive some new mails (via receive)
3.) read the mails, marking them as read
4.) change over to the calendar
5.) now when you hover over an calendar item, the complete application crashes with SIGSERV. It does run fine, until you hover over the calendar items.

Any ideas/suggestions?

Tags: kde3.5.10
Revision history for this message
Trax (forum-traxbyte) wrote :

I experience the same issue. Here's the backtrace

[Thread debugging using libthread_db enabled]
[New Thread 0x7f93be6616f0 (LWP 8804)]
[New Thread 0x43e6f950 (LWP 8808)]
[New Thread 0x4366e950 (LWP 8807)]
[New Thread 0x42e6d950 (LWP 8806)]
[New Thread 0x4266c950 (LWP 8805)]
[KCrash handler]
#5 0x00007f93b163c27e in KOAgendaItem::paintEvent (this=0x13e0e80,
    ev=0x7fffc669ba00)
    at /build/buildd/kdepim-3.5.10/./korganizer/koagendaitem.cpp:753
#6 0x00007f93b8734858 in QWidget::event (this=0x13e0e80, e=0x7fffc669ba00)
    at kernel/qwidget.cpp:4808
#7 0x00007f93b869833a in QApplication::internalNotify (this=0x7fffc669cdf0,
    receiver=0x13e0e80, e=0x7fffc669ba00) at kernel/qapplication.cpp:2638
#8 0x00007f93b869abe3 in QApplication::notify (this=0x7fffc669cdf0,
    receiver=0x13e0e80, e=0x7fffc669ba00) at kernel/qapplication.cpp:2526
#9 0x00007f93b9dce6bd in KApplication::notify (this=0x7fffc669cdf0,
    receiver=0x13e0e80, event=0x7fffc669ba00)
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#10 0x00007f93b862920e in QApplication::sendEvent (receiver=0x13e0e80,
    event=0x7fffc669ba00) at ../include/qapplication.h:523
#11 0x00007f93b86639e7 in QWidget::repaint (this=0x13e0e80, x=0, y=0, w=322,
    h=39, erase=true) at kernel/qwidget_x11.cpp:1595
#12 0x00007f93b163cdca in KOAgendaItem::paintEvent (this=0x13e0e80,
    ev=0x7fffc669c5b0) at /usr/share/qt3/include/qwidget.h:842
#13 0x00007f93b8734858 in QWidget::event (this=0x13e0e80, e=0x7fffc669c5b0)
    at kernel/qwidget.cpp:4808
#14 0x00007f93b869833a in QApplication::internalNotify (this=0x7fffc669cdf0,
    receiver=0x13e0e80, e=0x7fffc669c5b0) at kernel/qapplication.cpp:2638
#15 0x00007f93b869abe3 in QApplication::notify (this=0x7fffc669cdf0,
    receiver=0x13e0e80, e=0x7fffc669c5b0) at kernel/qapplication.cpp:2526
#16 0x00007f93b9dce6bd in KApplication::notify (this=0x7fffc669cdf0,
    receiver=0x13e0e80, event=0x7fffc669c5b0)
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#17 0x00007f93b8629280 in QApplication::sendSpontaneousEvent (
    receiver=0x13e0e80, event=0x7fffc669c5b0) at kernel/qapplication.h:526
#18 0x00007f93b8618a7c in QETWidget::translatePaintEvent (this=0x13e0e80,
    event=0x7fffc669cb40) at kernel/qapplication_x11.cpp:5787
#19 0x00007f93b86260f6 in QApplication::x11ProcessEvent (this=0x7fffc669cdf0,
    event=0x7fffc669cb40) at kernel/qapplication_x11.cpp:3505
#20 0x00007f93b863d106 in QEventLoop::processEvents (this=0x696880, flags=4)
    at kernel/qeventloop_x11.cpp:195
#21 0x00007f93b86b25bf in QEventLoop::enterLoop (this=0x696880)
    at kernel/qeventloop.cpp:201
#22 0x00007f93b86b22ab in QEventLoop::exec (this=0x696880)
    at kernel/qeventloop.cpp:148
#23 0x00007f93b8699e00 in QApplication::exec (this=0x7fffc669cdf0)
    at kernel/qapplication.cpp:2761
#24 0x0000000000419299 in main (argc=<value optimized out>,
    argv=<value optimized out>)
    at /build/buildd/kdepim-3.5.10/./kontact/src/main.cpp:163

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Confirming since 2 users report the same issue

Changed in kdepim:
importance: Undecided → Low
status: New → Confirmed
Changed in kdepim:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.