Summary: | kontact crashes when clicking on calendar | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Stefan Endrullis <stefan> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | expendable.0, finex, kde.org, rm, roth, smartins, tschenturs, veskoteque |
Priority: | NOR | ||
Version: | 1.2.9 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | korganizer.kcrash |
Description
Stefan Endrullis
2008-09-08 09:55:24 UTC
Same phenomenon over here (on Gentoo, with KDE compiled from source). I don't think it's really kontakt related as the same issues also occur if I run korganizer stand alone. OK, your right. KOrganizer itself crashes when I click on "Next 3 Days" for example. Both are not usable anymore :( I've searched for a related bug report for korganizer. But there are sooo many open bugs concerning korganizer/kontact and crashes. OMG! I'm a bit disappointed. Seems there's no developer anymore who cares for KDE 3.5 programs. I don't understand that. Since KDE 3.5 is frozen in months it should become more stable because of only bug fixes but instead it's going to be more unstable with every further release. I receive always the same impression: The KDE 4 developers want us to migrate to KDE 4! But please don't force us until KDE 4 is missing lots of KDE 3 features. I'm rather willing to migrate to alternatives to KDE programs. I'm still a KDE 3.5 fan because of the unique configuration options but I regard with horror the current trend of KDE. When years old feature requests (bug #77486, bug #33857) are marked as resolved without implementing it, just to get rid of them, and "stable releases" become much more unstable then then it should be a signal to change something. My personal conclusion: I'm searching for another organizer now. Sorry for my last comment. Normally such things should not be part of comments to bugs, but I suppose this bug is also going to be marked as fixed even if it's not fixed in reality. :[ Created attachment 27639 [details]
korganizer.kcrash
Sorry, I'm not used to bugzilla. I have the same problem, gentoo 64bit, kontact and korganizer 3.5.10. Above you can find my krcrash-log. CFLAGS="-march=nocona -O2 -pipe -ggdb" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="${CFLAGS}" I think that this bug may be related to #172488 Changed severity to "crash". I hope to have selected only the right bugs (>100) :-) *** Bug 172488 has been marked as a duplicate of this bug. *** *** Bug 173432 has been marked as a duplicate of this bug. *** Looking at a valgrind report of one of the dups it looks like an invalid read inside libical. Can you upgrade to a recent libical and see what happens? I'm using libical 0.27-1 now, but the problem remains the same. And same issue with libical 0.33-1. Back trace: (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f843e3246f0 (LWP 9137)] [KCrash handler] #5 0x00007f8431a2ca46 in KOAgendaItem::paintEvent () from /usr/kde3/lib/libkorganizer.so.1 #6 0x00007f8438899835 in QWidget::event (this=0x3079940, e=0x7fff4635e030) at kernel/qwidget.cpp:4808 #7 0x00007f84388074a5 in QApplication::internalNotify ( this=<value optimized out>, receiver=0x3079940, e=0x7fff4635e030) at kernel/qapplication.cpp:2638 #8 0x00007f843880827a in QApplication::notify (this=0x7fff4635e7a0, receiver=0x3079940, e=0x7fff4635e030) at kernel/qapplication.cpp:2526 #9 0x00007f8439a20c22 in KApplication::notify (this=0x7fff4635e7a0, receiver=0x3079940, event=0x7fff4635e030) at /build/buildd/kdelibs-kde3-3.5.10/./kdecore/kapplication.cpp:550 #10 0x00007f843879bacd in QETWidget::translatePaintEvent (this=0x3079940, event=<value optimized out>) at kernel/qapplication.h:526 #11 0x00007f84387a4d79 in QApplication::x11ProcessEvent (this=0x7fff4635e7a0, event=0x7fff4635e500) at kernel/qapplication_x11.cpp:3546 #12 0x00007f84387b782a in QEventLoop::processEvents (this=0x2266830, flags=4) at kernel/qeventloop_x11.cpp:195 #13 0x00007f843881dec1 in QEventLoop::enterLoop (this=0x7fff4635d8c0) at kernel/qeventloop.cpp:201 #14 0x00007f843881dd82 in QEventLoop::exec (this=0x7fff4635d8c0) at kernel/qeventloop.cpp:148 #15 0x0000000000418cd5 in ?? () #16 0x00007f84350be466 in __libc_start_main () from /lib/libc.so.6 #17 0x00000000004181d9 in ?? () #18 0x00007fff4635eb68 in ?? () #19 0x000000000000001c in ?? () #20 0x0000000000000001 in ?? () #21 0x00007fff46360a93 in ?? () #22 0x0000000000000000 in ?? () I think this bug is connected with bug #170273 http://bugs.kde.org/show_bug.cgi?id=170273 That might be. It looks like the paintEvent() method is "responsible" (it's the first visible method in the back trace) for the crash in both bugs. But I'm wondering why I'm able to click on the buttons "next 3 days", etc. in kontact but not in korganizer. Stefan, it would be great if you provided a valgrind report. 1. Install valgrind 2. run: valgrind korganizer --nofork &> report.txt 3. Make korganizer crash No feedback. Closing. |