| Summary: | summary in kontact crashed | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | falconblue <falconblue> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | arne.schmitz, bugs.kde, drazzib-web, leonardokroeger, matt, olivier.delemar, olsonbg, rdieter, smartins, t.buchloh, venkatraghavan |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Kontact startup crash backtrace
Backtrace for this crash. Backtrace of kontact crashing with full detail. |
||
|
Description
falconblue
2006-10-15 23:00:40 UTC
Kontact starts and loads mail components, but gets crached when switching to the summary interface. *** Bug 136026 has been marked as a duplicate of this bug. *** Do you still have this problem? Perhaps you could post the calendar (or mail it privately) so it can be reproduced? Yes, I still have this problem (same backtrace as posted earlier). My ICS resource is on a HTTPS Webdav resource, automatic reload is set on start and automatic save is delayed. I'll send you my ICS file in private. Thanks I have what appears to be a very similar problem ... backtrace to follow. In my case it's with a DIMAP calendar resource. All the individual PIM components, including korganizer, start successfully when launched independently. This is with Rex Dieter's 3.5.5 kde-redhat packages for FC5. Created attachment 18313 [details]
Kontact startup crash backtrace
Another data point on this ... If it start Korganizer standalone and deselect the imap resource and then quit, I'm able to start Kontact successfully. From within Kontact I can then renable the imap resource and see my events. If I leave the imap resource selected Kontact will crash on the summary page the next time it's launched. Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. One more data point. This crash goes away if I disable the ToDo plugin in Kontact's Summary view. I got the very same crash as the first backtrace above indicates, when I deleted an event in my fish:// calendar. Maybe I should also note, that I was using korganizer embedded in kontact. And that I used the summary plugin a little while before deleting the event. My system is Debian with kontact and korganizer versions 3.5.5.dfsg.1-2 Do you have automatic saving enabled and if yes, in which mode? (see the resource configuration dialog inside KOrganizer). I do. I have "Enable automatic saving of manually open calendar files" checked, "Confirm deletes" checked, and "Be asked which resource to use" selected. Nb. this is with a DIMAP calendar resource. *** Bug 139261 has been marked as a duplicate of this bug. *** I consistently get this crash since upgrading to 3.5, both with Gentoo and Kubuntu 6.10. It doesn't seem to matter where the remote calendar is stored, or how it's accessed; but after the save has finished Kontact will always crash with the same stack trace (as above). I'm using the calendar component of Kontact and have tried using FTP, SFTP and WebDAV to say the calendar. I've also tried removing ToDo from the Summary view (as suggested above), but this had no effect. *** Bug 144730 has been marked as a duplicate of this bug. *** I have the same issue, with a webdavs:// calendar. In the resource configuration dialog: Automatic reload on startup, automatic save delayed after changes. Comment #7 applies, #9 does not (I tried hiding Todo from the summary but still get the crash). Created attachment 20942 [details]
Backtrace for this crash.
I have something similar - Kontact can cause kicker to crash and itself when it is trying to copy a calendar over from webdav. The problem seems to be to do with Kwallet as well. The file is trying to be copied over before the copy program has received the password from Kontact or Kwallet. i.e. If I'm not paying attention when KDE is loading the copy file process dialogue will crash kicker and kontact. However, if I am quick to enter the password into kwallet then it seems to go okay. Created attachment 27344 [details]
Backtrace of kontact crashing with full detail.
Kontact is crashing when i try to scroll on the calendar. It basically crashes when it needs to be redrawn (except for the first initial draw).
Here is my calendar rc file:
[General]
PassiveResourceKeys=
ResourceKeys=HQpwzJ8X4U,7j57llqDI5
Standard=HQpwzJ8X4U
[Resource_7j57llqDI5]
DownloadUrl=fish://host/home/user/calendars/school
LastLoad=2935093,2,28,0,0,0
LastSave=2935093,2,28,0,0,0
ReloadInterval=10
ReloadPolicy=0
ResourceIdentifier=7j57llqDI5
ResourceIsActive=true
ResourceIsReadOnly=false
ResourceName=School
ResourceType=remote
SaveInterval=10
SavePolicy=0
UploadUrl=fish://host/home/user/calendars/school
[Resource_HQpwzJ8X4U]
CalendarURL[$e]=file://$HOME/.kde/share/apps/korganizer/std.ics
Format=ical
ResourceIdentifier=HQpwzJ8X4U
ResourceIsActive=true
ResourceIsReadOnly=false
ResourceName=Default Calendar
ResourceType=file
*** This bug has been confirmed by popular vote. *** *** Bug 133086 has been marked as a duplicate of this bug. *** Kontact is chrashing if I switch to kalendar. But only if I have activated a webdav kalendar file. If it's deactivated the program works fine. If I start korganizer standalone it works with the webdav file. backtrace: Überprüfung der Systemkonfiguration beim Start deaktiviert. [?1034h(no debugging symbols found) (no debugging symbols found) ... (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb5e856d0 (LWP 11853)] [New Thread 0xb3075b90 (LWP 11857)] [New Thread 0xb3876b90 (LWP 11856)] [New Thread 0xb4077b90 (LWP 11855)] [New Thread 0xb4878b90 (LWP 11854)] (no debugging symbols found) .... (no debugging symbols found) [KCrash handler] #6 0xb535be72 in KOAgenda::setNoActionCursor () from /opt/kde3/lib/libkorganizer.so.1 #7 0xb53642d9 in KOAgenda::eventFilter_mouse () from /opt/kde3/lib/libkorganizer.so.1 #8 0xb535ca26 in KOAgenda::eventFilter () from /opt/kde3/lib/libkorganizer.so.1 #9 0xb6b97a43 in QObject::activate_filters () from /usr/lib/qt3/lib/libqt-mt.so.3 #10 0xb6b97aab in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0xb6bd23ec in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0xb6b325bd in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0xb6b337c6 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #14 0xb7221882 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #15 0xb6accaee in QApplication::sendSpontaneousEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0xb6ac9910 in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0xb6ac821e in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0xb6adcd54 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0xb6b4af00 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb6b4ad96 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb6b32c4f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0x0805b9a4 in ?? () #23 0xb66d85f5 in __libc_start_main () from /lib/libc.so.6 #24 0x0805add1 in ?? () Same crash when adding an event to a webdav calendar in standalone KOrganizer from trunk:
#0 0xb6b19880 in QString::operator== (this=0xbf9ac010, other=@0xbf9ac04c) at tools/qstring.cpp:1774
#1 0xb7a98acb in KCal::ResourceCached::clearChange (this=0x8229708, uid=@0xbf9ac04c)
at /home/kde-devel/kde/src/KDE/kdepimlibs/kcal/resourcecached.cpp:769
#2 0xb7a98d5b in KCal::ResourceCached::clearChange (this=0x8229708, incidence=0x846d9d0)
at /home/kde-devel/kde/src/KDE/kdepimlibs/kcal/resourcecached.cpp:761
#3 0xb3b13e24 in KCal::ResourceRemote::slotSaveJobResult (this=0x8229708, job=0x828fc30)
at /home/kde-devel/kde/src/KDE/kdepim/kresources/remote/resourceremote.cpp:299
#4 0xb3b1488a in KCal::ResourceRemote::qt_metacall (this=0x8229708, _c=QMetaObject::InvokeMetaMethod, _id=-2, _a=0xbf9ac17c)
at /home/kde-devel/kde/build/KDE/kdepim/kresources/remote/resourceremote.moc:70
#5 0xb6bd72ab in QMetaObject::activate (sender=0x828fc30, from_signal_index=<value optimized out>, to_signal_index=7,
argv=<value optimized out>) at kernel/qobject.cpp:3028
#6 0xb6bd7914 in QMetaObject::activate (sender=0x828fc30, m=0xb6f5cca8, local_signal_index=3, argv=0xbf9ac17c) at kernel/qobject.cpp:3098
#7 0xb6df1ffa in KJob::result (this=0x828fc30, _t1=0x828fc30) at /home/kde-devel/kde/build/KDE/kdelibs/kdecore/kjob.moc:186
#8 0xb6df2a2f in KJob::emitResult (this=0x828fc30) at /home/kde-devel/kde/src/KDE/kdelibs/kdecore/jobs/kjob.cpp:295
#9 0xb707f8b9 in KIO::FileCopyJob::slotResult (this=0x828fc30, job=0x822d4d8) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/job.cpp:2219
#10 0xb7086367 in KIO::FileCopyJob::qt_metacall (this=0x828fc30, _c=QMetaObject::InvokeMetaMethod, _id=32, _a=0xbf9ac2bc)
at /home/kde-devel/kde/build/KDE/kdelibs/kio/jobclasses.moc:658
#11 0xb6bd72ab in QMetaObject::activate (sender=0x822d4d8, from_signal_index=<value optimized out>, to_signal_index=7,
argv=<value optimized out>) at kernel/qobject.cpp:3028
#12 0xb6bd7914 in QMetaObject::activate (sender=0x822d4d8, m=0xb6f5cca8, local_signal_index=3, argv=0xbf9ac2bc) at kernel/qobject.cpp:3098
---Type <return> to continue, or q <return> to quit---
#13 0xb6df1ffa in KJob::result (this=0x822d4d8, _t1=0x822d4d8) at /home/kde-devel/kde/build/KDE/kdelibs/kdecore/kjob.moc:186
#14 0xb6df2a2f in KJob::emitResult (this=0x822d4d8) at /home/kde-devel/kde/src/KDE/kdelibs/kdecore/jobs/kjob.cpp:295
#15 0xb707747f in KIO::SimpleJob::slotFinished (this=0x822d4d8) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/job.cpp:489
#16 0xb707dd75 in KIO::TransferJob::slotFinished (this=0x822d4d8) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/job.cpp:966
#17 0xb7086cfe in KIO::TransferJob::qt_metacall (this=0x822d4d8, _c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbf9ac4f8)
at /home/kde-devel/kde/build/KDE/kdelibs/kio/jobclasses.moc:336
#18 0xb6bd72ab in QMetaObject::activate (sender=0x82be058, from_signal_index=<value optimized out>, to_signal_index=8,
argv=<value optimized out>) at kernel/qobject.cpp:3028
#19 0xb6bd7914 in QMetaObject::activate (sender=0x82be058, m=0xb7240c04, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3098
#20 0xb714f0ec in KIO::SlaveInterface::finished (this=0x82be058) at /home/kde-devel/kde/build/KDE/kdelibs/kio/slaveinterface.moc:163
#21 0xb7152b7d in KIO::SlaveInterface::dispatch (this=0x82be058, _cmd=104, rawdata=@0xbf9ac6a4)
at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slaveinterface.cpp:175
#22 0xb714f67b in KIO::SlaveInterface::dispatch (this=0x82be058) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slaveinterface.cpp:91
#23 0xb713dbc3 in KIO::Slave::gotInput (this=0x82be058) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slave.cpp:322
#24 0xb713e8cd in KIO::Slave::qt_metacall (this=0x82be058, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf9ac7a8)
at /home/kde-devel/kde/build/KDE/kdelibs/kio/slave.moc:75
#25 0xb6bd72ab in QMetaObject::activate (sender=0x8233248, from_signal_index=<value optimized out>, to_signal_index=4,
argv=<value optimized out>) at kernel/qobject.cpp:3028
#26 0xb6bd7914 in QMetaObject::activate (sender=0x8233248, m=0xb723d6e0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3098
#27 0xb703cf29 in KIO::Connection::readyRead (this=0x8233248) at /home/kde-devel/kde/build/KDE/kdelibs/kio/connection.moc:84
---Type <return> to continue, or q <return> to quit---
#28 0xb703ecfb in KIO::ConnectionPrivate::dequeue (this=0x8223d58) at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/connection.cpp:82
#29 0xb703ed95 in KIO::Connection::qt_metacall (this=0x8233248, _c=QMetaObject::InvokeMetaMethod, _id=-3, _a=0x81fd3a0)
at /home/kde-devel/kde/build/KDE/kdelibs/kio/connection.moc:72
#30 0xb6bd0b29 in QMetaCallEvent::placeMetaCall (this=0x8425fd0, object=0x8233248) at kernel/qobject.cpp:535
#31 0xb6bd2a61 in QObject::event (this=0x8233248, e=0x8425fd0) at kernel/qobject.cpp:1152
#32 0xb616af7f in QApplicationPrivate::notify_helper (this=0x8072878, receiver=0x8233248, e=0x8425fd0) at kernel/qapplication.cpp:3809
#33 0xb616fa79 in QApplication::notify (this=0xbf9acf60, receiver=0x8233248, e=0x8425fd0) at kernel/qapplication.cpp:3399
#34 0xb7dce660 in KApplication::notify (this=0xbf9acf60, receiver=0x8233248, event=0x8425fd0)
at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307
#35 0xb6bc2397 in QCoreApplication::notifyInternal (this=0xbf9acf60, receiver=0x8233248, event=0x8425fd0)
at kernel/qcoreapplication.cpp:593
#36 0xb6bc352d in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x80562d0) at kernel/qcoreapplication.h:215
#37 0xb6beee68 in QEventDispatcherUNIX::processEvents (this=0x8072400, flags=@0xbf9ace68) at kernel/qeventdispatcher_unix.cpp:867
#38 0xb61fa6d6 in QEventDispatcherX11::processEvents (this=0x8072400, flags=@0xbf9ace98) at kernel/qeventdispatcher_x11.cpp:154
#39 0xb6bc156d in QEventLoop::processEvents (this=0xbf9acf10, flags=@0xbf9aced8) at kernel/qeventloop.cpp:149
#40 0xb6bc170d in QEventLoop::exec (this=0xbf9acf10, flags=@0xbf9acf18) at kernel/qeventloop.cpp:200
#41 0xb6bc3886 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851
#42 0xb616a7a7 in QApplication::exec () at kernel/qapplication.cpp:3337
#43 0x0804ec9d in main (argc=Cannot access memory at address 0xdc00c2
) at /home/kde-devel/kde/src/KDE/kdepim/korganizer/main.cpp:60
==============================================
VALGRIND says:
==6267== Invalid read of size 4
==6267== at 0x458E007: KCal::ErrorFormat::errorCode() (exceptions.cpp:128)
==6267== by 0x4844DAD: KOEventEditor::processInput() (koeventeditor.cpp:324)
==6267== by 0x4841E51: KOIncidenceEditor::slotButtonClicked(int) (koincidenceeditor.cpp:98)
==6267== by 0x4156C64: KDialog::qt_metacall(QMetaObject::Call, int, void**) (kdialog.moc:181)
==6267== by 0x42270CF: KPageDialog::qt_metacall(QMetaObject::Call, int, void**) (kpagedialog.moc:63)
==6267== by 0x4842359: KOIncidenceEditor::qt_metacall(QMetaObject::Call, int, void**) (koincidenceeditor.moc:106)
==6267== by 0x4845179: KOEventEditor::qt_metacall(QMetaObject::Call, int, void**) (koeventeditor.moc:69)
==6267== by 0x545F2AA: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3028)
==6267== by 0x545F913: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3098)
==6267== by 0x54635B0: QSignalMapper::mapped(int) (moc_qsignalmapper.cpp:93)
==6267== by 0x5463D0A: QSignalMapper::map(QObject*) (qsignalmapper.cpp:277)
==6267== by 0x5463EFD: QSignalMapper::map() (qsignalmapper.cpp:268)
==6267== Address 0xc is not stack'd, malloc'd or (recently) free'd
==6267==
==6267== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==6267== Access not within mapped region at address 0xC
==6267== at 0x458E007: KCal::ErrorFormat::errorCode() (exceptions.cpp:128)
==6267== by 0x4844DAD: KOEventEditor::processInput() (koeventeditor.cpp:324)
==6267== by 0x4841E51: KOIncidenceEditor::slotButtonClicked(int) (koincidenceeditor.cpp:98)
==6267== by 0x4156C64: KDialog::qt_metacall(QMetaObject::Call, int, void**) (kdialog.moc:181)
==6267== by 0x42270CF: KPageDialog::qt_metacall(QMetaObject::Call, int, void**) (kpagedialog.moc:63)
==6267== by 0x4842359: KOIncidenceEditor::qt_metacall(QMetaObject::Call, int, void**) (koincidenceeditor.moc:106)
==6267== by 0x4845179: KOEventEditor::qt_metacall(QMetaObject::Call, int, void**) (koeventeditor.moc:69)
==6267== by 0x545F2AA: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3028)
==6267== by 0x545F913: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3098)
==6267== by 0x54635B0: QSignalMapper::mapped(int) (moc_qsignalmapper.cpp:93)
==6267== by 0x5463D0A: QSignalMapper::map(QObject*) (qsignalmapper.cpp:277)
==6267== by 0x5463EFD: QSignalMapper::map() (qsignalmapper.cpp:268)
==6267== If you believe this happened as a result of a stack overflow in your
==6267== program's main thread (unlikely but possible), you can try to increase
==6267== the size of the main thread stack using the --main-stacksize= flag.
==6267== The main thread stack size used in this run was 8388608.
*** Bug 144579 has been marked as a duplicate of this bug. *** Fixed some months ago in rev r931230. |