Bug 187378 - Crash at startup when clicking at e.g. "Work week"
Summary: Crash at startup when clicking at e.g. "Work week"
Status: RESOLVED NOT A BUG
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-17 08:43 UTC by Alex Back
Modified: 2009-10-23 10:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Back 2009-03-17 08:43:09 UTC
Version:           4.2 rc1 (using KDE 4.2.0)
Compiler:          gcc 4.3.2 20081105 (Red Hat 4.3.2-7) 
OS:                Linux
Installed from:    Fedora RPMs

Korganizer starts at startup and the first click at any Radiobutton which shows the calendars (like "Work week") are resulting in a crash of the application.

=== Backtrace ===
Application: KOrganizer (korganizer), signal SIGSEGV
[Current thread is 1 (Thread 0xb7fea770 (LWP 2379))]

Thread 1 (Thread 0xb7fea770 (LWP 2379)):
[KCrash Handler]
#6  0x0064ffbb in KCal::CalFilter::filterIncidence () from /usr/lib/libkcal.so.4
#7  0x0065053e in KCal::CalFilter::apply () from /usr/lib/libkcal.so.4
#8  0x0060cfa2 in KCal::Calendar::todos () from /usr/lib/libkcal.so.4
#9  0x00773a67 in QWidget::setUpdatesEnabled () from /usr/lib/libkorganizerprivate.so.4
#10 0x0077473e in QWidget::setUpdatesEnabled () from /usr/lib/libkorganizerprivate.so.4
#11 0x0076d249 in QWidget::setUpdatesEnabled () from /usr/lib/libkorganizerprivate.so.4
#12 0x0076d36e in QWidget::setUpdatesEnabled () from /usr/lib/libkorganizerprivate.so.4
#13 0x007c9066 in ?? () from /usr/lib/libkorganizerprivate.so.4
#14 0x007c92da in ?? () from /usr/lib/libkorganizerprivate.so.4
#15 0x007c9700 in ?? () from /usr/lib/libkorganizerprivate.so.4
#16 0x013e6750 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0x013e6b50 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0x019d3cf1 in QAction::triggered () from /usr/lib/libQtGui.so.4
#19 0x019d465f in QAction::activate () from /usr/lib/libQtGui.so.4
#20 0x01df8882 in QToolButton::nextCheckState () from /usr/lib/libQtGui.so.4
#21 0x01d1bfb3 in ?? () from /usr/lib/libQtGui.so.4
#22 0x01d1c286 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#23 0x01df8d7c in QToolButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#24 0x01a32052 in QWidget::event () from /usr/lib/libQtGui.so.4
#25 0x01d1a2be in QAbstractButton::event () from /usr/lib/libQtGui.so.4
#26 0x01df8844 in QToolButton::event () from /usr/lib/libQtGui.so.4
#27 0x019d9fec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#28 0x019e27e1 in QApplication::notify () from /usr/lib/libQtGui.so.4
#29 0x003bffdd in KApplication::notify () from /usr/lib/libkdeui.so.5
#30 0x013d1b21 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#31 0x019e1a6e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#32 0x01a4bdb6 in ?? () from /usr/lib/libQtGui.so.4
#33 0x01a4b145 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#34 0x01a7377a in ?? () from /usr/lib/libQtGui.so.4
#35 0x03c8a238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#36 0x03c8d8e3 in ?? () from /lib/libglib-2.0.so.0
#37 0x03c8daa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#38 0x013fc158 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#39 0x01a72e75 in ?? () from /usr/lib/libQtGui.so.4
#40 0x013d01ea in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#41 0x013d03aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#42 0x013d2a65 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#43 0x019d9e67 in QApplication::exec () from /usr/lib/libQtGui.so.4
#44 0x080506fe in _start ()
Comment 1 Dario Andres 2009-03-17 15:29:33 UTC
Please, can you install the "kdepim4-debuginfo" package to get a complete backtrace? Thanks!
Comment 2 Alex Back 2009-03-17 16:58:07 UTC
Unfortunately not since the "kdepim4-debuginfo" package is not available for my distribution (Fedora Core 10).
Is there any other way I can provide some additional infos to get a better understanding of this issue?

By the way: many thanks for the fast answer. This was my first bug report and I'm really impressed by the reaction time. Keep up the good work!
Comment 3 Dario Andres 2009-04-01 23:37:04 UTC
Mh, I don't know how Fedora names its packages, but there should be a package related to "kdepim" and with the "debug" or "debuginfo" suffix. There should be one for KDE3 and another for KDE4. You also need the debug package for "kdepimlibs". Thanks
Comment 4 Alex Back 2009-04-02 18:25:32 UTC
(In reply to comment #3)
> Mh, I don't know how Fedora names its packages, but there should be a package
> related to "kdepim" and with the "debug" or "debuginfo" suffix. There should be
> one for KDE3 and another for KDE4. You also need the debug package for
> "kdepimlibs".
The hint with "debuginfo" did it. One need to install the "yum-utils" package with comes with the "debuginfo-install" command.
This lets you easily install the debuginfo package you need.

--snip--
sudo debuginfo-install kdepim
--snip--

The command above did the trick for me. 

How to setup it is linked here:
http://fedoraproject.org/wiki/StackTraces

I'll provide a complete backtrace as soon as I encounter it again.

Thanks for the help!
Comment 5 Dario Andres 2009-05-17 23:01:50 UTC
Marking as NEEDSINFo. Thanks
Comment 6 Christophe Marin 2009-10-23 10:36:08 UTC
Closing the old crash reports which don't have a useful backtrace. Thanks.