Version: (using KDE 4.2.0) Installed from: Fedora RPMs Application: KAlarm (kalarm), signal SIGSEGV 0x0000003875aa7f81 in nanosleep () from /lib64/libc.so.6 Current language: auto; currently c [Current thread is 1 (Thread 0x7feec736a800 (LWP 18947))] Thread 2 (Thread 0x7feec0ac0950 (LWP 18966)): #0 0x0000003875adeaa2 in select () from /lib64/libc.so.6 #1 0x0000003881322626 in QProcessManager::run (this=0x14afe90) at io/qprocess_unix.cpp:301 #2 0x0000003881259852 in QThreadPrivate::start (arg=0x14afe90) at thread/qthread_unix.cpp:185 #3 0x00000038766073da in start_thread (arg=<value optimized out>) at pthread_create.c:297 #4 0x0000003875ae62bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 Thread 1 (Thread 0x7feec736a800 (LWP 18947)): [KCrash Handler] #5 AlarmCalendar::atLoginAlarms (this=0x0) at /usr/src/debug/kdepim-4.2.0/kalarm/alarmcalendar.cpp:1267 #6 0x00000000004948f9 in KAlarmApp::processQueue (this=0x149da70) at /usr/src/debug/kdepim-4.2.0/kalarm/kalarmapp.cpp:970 #7 0x0000000000494ef0 in KAlarmApp::qt_metacall (this=0x149da70, _c=QMetaObject::InvokeMetaMethod, _id=21617153, _a=0x7fffcf3ace30) at /usr/src/debug/kdepim-4.2.0/x86_64-redhat-linux-gnu/kalarm/kalarmapp.moc:94 #8 0x0000003881356764 in QMetaObject::activate (sender=0x1887200, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x7fffcf3ace30) at kernel/qobject.cpp:3031 #9 0x000000388135c9cf in QSingleShotTimer::timerEvent (this=0x1887200) at kernel/qtimer.cpp:294 #10 0x0000003881351073 in QObject::event (this=0x1887200, e=0x0) at kernel/qobject.cpp:1120 #11 0x0000003f39d828dd in QApplicationPrivate::notify_helper (this=0x14a9660, receiver=0x1887200, e=0x7fffcf3ad4f0) at kernel/qapplication.cpp:3803 #12 0x0000003f39d8a68a in QApplication::notify (this=0x149da70, receiver=0x1887200, e=0x7fffcf3ad4f0) at kernel/qapplication.cpp:3768 #13 0x0000003f3ae04deb in KApplication::notify (this=0x149da70, receiver=0x1887200, event=0x7fffcf3ad4f0) at /usr/src/debug/kdelibs-4.2.0/kdeui/kernel/kapplication.cpp:307 #14 0x0000003881342391 in QCoreApplication::notifyInternal (this=0x149da70, receiver=0x1887200, event=0x7fffcf3ad4f0) at kernel/qcoreapplication.cpp:587 #15 0x000000388136e0d6 in QCoreApplication::sendEvent () at ../../src/corelib/kernel/qcoreapplication.h:209 #16 QTimerInfoList::activateTimers (this=0x14afcb0) at kernel/qeventdispatcher_unix.cpp:557 #17 0x000000388136a83d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:160 #18 0x000000387723779b in g_main_dispatch () at gmain.c:2144 #19 IA__g_main_context_dispatch (context=0x14af080) at gmain.c:2697 #20 0x000000387723af6d in g_main_context_iterate (context=0x14af080, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2778 #21 0x000000387723b12b in IA__g_main_context_iteration (context=0x14af080, may_block=1) at gmain.c:2841 #22 0x000000388136a79f in QEventDispatcherGlib::processEvents (this=0x14a5d30, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319 #23 0x0000003f39e1328f in QGuiEventDispatcherGlib::processEvents (this=0x7fffcf3acd30, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198 #24 0x0000003881340cb2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:143 #25 0x0000003881340e3d in QEventLoop::exec (this=0x7fffcf3ad7a0, flags=) at kernel/qeventloop.cpp:194 #26 0x00000038813432ed in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #27 0x0000000000453fc2 in main (argc=3, argv=0x7fffcf3ae648) at /usr/src/debug/kdepim-4.2.0/kalarm/main.cpp:123 it crashes every time i log in. x86_64, fedora 10.
rpm -q libical kdepim please.
rpm -q libical kdepim libical-0.41-2.fc10.x86_64 kdepim-4.2.0-2.fc10.x86_64
mind trying yum --enablerepo=updates-testing update libical (to try libical-0.43 ) ?
To help track this one down, could you please enable debug logging for KAlarm, and attach the log file. Here are the steps to take: 1) Run 'kdebugdialog --fullmode'. Select 5950 kalarm, and 5951 kalarm (resources), and in both cases set the output to a file (/tmp/kalarm.log for example). 2) Log out, and log in again. 3) Once KAlarm has crashed, attach the log file to this bug report. 4) Run 'kdebugdialog --fullmode' again and set the output back to its original settings so as not to fill up the disk. P.S. I don't think the crash is related to libical.
Well, today morning i booted my machine and it doesn't crash anymore :-( Could it be related to the audio subsystem and notifications? Before I also got an error about pulseaudio and how it doesn't work, dialog offered me to remove some AMD stuff from configuration and it kept coming too in every login. I tried different answers and now it doesn't complain anymore either. If i see my system settings, there are two gray broken icons in output devices list. If i change the order list to whatever, now they all work and that error dialog does not appear. Well, now i know that kdebugdialog utility and try that next time. I wish that would have been a button in crash output dialog so I could have found that myself. Thanks for your time.
Have you updated Qt since you originally reported the bug? If so, that might be the reason the bug is now fixed.
Name : qt Relocations: (not relocatable) Version : 4.4.3 Vendor: Fedora Project Release : 10.fc10 Build Date: Tue 13 Jan 2009 10:47:14 PM EET Install Date: Tue 24 Feb 2009 05:28:36 PM EET Build Host: x86-5.fedora.phx.redhat.com $ grep qt /var/log/yum.log Feb 26 17:52:05 Installed: 1:qt-debuginfo-4.4.3-10.fc10.x86_64 Feb 26 17:58:53 Installed: dbus-qt3-0.9-1.fc10.x86_64 Feb 26 19:26:09 Installed: qt3-devel-3.3.8b-17.fc10.x86_64 Feb 26 19:26:10 Installed: qt3-designer-3.3.8b-17.fc10.x86_64 No, I don't think I have. Anyway, after system being reinstalled, I have done lot of other pkg installations: $ grep "Feb 26" /var/log/yum.log |wc -l 141