Summary: | crash at startup after KDE upgrade | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | Juha Tuomala <tuju> |
Component: | general | Assignee: | David Jarvie <djarvie> |
Status: | CLOSED NOT A BUG | ||
Severity: | crash | CC: | rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: |
Description
Juha Tuomala
2009-02-26 18:39:44 UTC
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 |