Bug 107360

Summary:	Kontact / KOrg crashes when using an empty new remote file
Product:	[Unmaintained] kresources	Reporter:	Carlos Woelz <carloswoelz>
Component:	remote	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	finex
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Crash backtrace

Description Carlos Woelz 2005-06-13 22:13:28 UTC

Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc version 3.4.3 (Mandrakelinux 10.2 3.4.3-7mdk) 
OS:                Linux

Steps to reproduce:

1- create an empty file (name it remote.ics, for instance)
2- add a new remote resource, pointing to this file
3- make it writable
4- make it save after each modification
5- enable it
6- add an incident
7- crash!

Comment 1 Carlos Woelz 2005-06-13 22:15:54 UTC

Created attachment 11433 [details]
Crash backtrace

Comment 2 Thiago Macieira 2005-06-14 12:52:53 UTC

Pasting the backtrace for easier searching:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240684864 (LWP 18979)]
[KCrash handler]
#7  0xffffe410 in ?? ()
#8  0xbfffe7d8 in ?? ()
#9  0x00000006 in ?? ()
#10 0x00004a23 in ?? ()
#11 0xb60f66e5 in raise () from /lib/tls/libc.so.6
#12 0xb60f8049 in abort () from /lib/tls/libc.so.6
#13 0xb62cbdee in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#14 0xb62c98f5 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.6
#15 0xb62c9932 in std::terminate () from /usr/lib/libstdc++.so.6
#16 0xb62c9e46 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6
#17 0xb4fc3c7b in KOAgenda::setNoActionCursor (this=0x8822180,
    moveItem=0x8aae158, viewportPos=@0xbfffea80)
    at /home/kdedev/src/kde/kdepim/korganizer/koagenda.cpp:1167
#18 0xb4fc159b in KOAgenda::eventFilter_mouse (this=0x8822180,
    object=0x8aae158, me=0xbfffeef0)
    at /home/kdedev/src/kde/kdepim/korganizer/koagenda.cpp:641
#19 0xb4fc0696 in KOAgenda::eventFilter (this=0x8822180, object=0x8aae158,
    event=0xbfffeef0)
    at /home/kdedev/src/kde/kdepim/korganizer/koagenda.cpp:353
#20 0xb6810cb0 in QObject::activate_filters (this=0x8aae158, e=0xbfffeef0)
    at kernel/qobject.cpp:902
#21 0xb6810b24 in QObject::event (this=0x8aae158, e=0xbfffeef0)
    at kernel/qobject.cpp:735
#22 0xb684b613 in QWidget::event (this=0x8aae158, e=0xbfffeef0)
    at kernel/qwidget.cpp:4658
#23 0xb67b08b5 in QApplication::internalNotify (this=0xbffff3d0,
    receiver=0x8aae158, e=0xbfffeef0) at kernel/qapplication.cpp:2635
#24 0xb67b0070 in QApplication::notify (this=0xbffff3d0, receiver=0x8aae158,
    e=0xbfffeef0) at kernel/qapplication.cpp:2421
#25 0xb6de9645 in KApplication::notify (this=0xbffff3d0, receiver=0x8aae158,
    event=0xbfffeef0)
    at /home/kdedev/src/kde/kdelibs/kdecore/kapplication.cpp:502
#26 0xb674510d in QApplication::sendSpontaneousEvent (receiver=0x8aae158,
    event=0xbfffeef0) at qapplication.h:494
#27 0xb673f6de in QETWidget::translateMouseEvent (this=0x8aae158,
    event=0xbffff290) at kernel/qapplication_x11.cpp:4291
#28 0xb673d341 in QApplication::x11ProcessEvent (this=0xbffff3d0,
    event=0xbffff290) at kernel/qapplication_x11.cpp:3442
#29 0xb67576dd in QEventLoop::processEvents (this=0x8100208, flags=4)
    at kernel/qeventloop_x11.cpp:192
#30 0xb67c4a7c in QEventLoop::enterLoop (this=0x8100208)
    at kernel/qeventloop.cpp:198
#31 0xb67c499a in QEventLoop::exec (this=0x8100208)
    at kernel/qeventloop.cpp:145
#32 0xb67b0a35 in QApplication::exec (this=0xbffff3d0)
    at kernel/qapplication.cpp:2758
#33 0x0805b4ad in main (argc=1, argv=0xbffff5a4)
    at /home/kdedev/src/kde/kdepim/kontact/src/main.cpp:156

Comment 3 Reinhold Kainhofer 2006-11-02 19:03:24 UTC

Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.

Comment 4 FiNeX 2007-12-11 18:30:48 UTC

Tested on KDE 3.5.8 and KDE4. It is working fine.
Bug closed.
If someone still have this bug just reopen this report.