| Summary: | Crashes when clicking OK in Configure KAlarm | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | BryanFRitt <BryanFRitt> |
| Component: | general | Assignee: | David Jarvie <djarvie> |
| Status: | CLOSED FIXED | ||
| Severity: | crash | CC: | christoph.paasch |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
BryanFRitt
2007-11-19 18:31:01 UTC
*** Bug 152168 has been marked as a duplicate of this bug. *** I later see: Cannot enable alarms: Failed to register with Alarm Daemon (kalarmd) I can still start kalamd from a konsole window kalarmd same error click OK (or apply) occurs in KAlarm... tried to create a new alarm for a minute later it asked to enable alarms gave back Cannot enable alarms: Failed to register with Alarm Daemon (kalarmd) but the alarm still showed up! I restarted and KAlarm works, without the error message Cannot enable alarms: Failed to register with Alarm Daemon (kalarmd) but, It still has the clicking OK crash in the Configure KAlarm config. p.s. I have compiz-fusion installed, and it likes to put the status icons on the top left instead of the task bar. (I close them sometimes), don't know if that makes a difference. The error message "Failed to register with Alarm Daemon" was probably because the kalarmd from the previous version was still running. The newest KAlarm package from the KAlarm website kills any running kalarmd to prevent that happening, but when you went back to the Ubuntu version, it may not have restarted kalarmd again. I tried it on Ubuntu Gutsy, and it doesn't crash. Can you please tell me your package version numbers of libqt3-mt and kalarm. I haven't got compix-fusion installed - I might try that if necessary. according to Adept it says I have libqt3-mt version 3:3.3.8really3.3.7-0ubuntu11.1 and KAlarm 4:3.5.7enterprise20070923-0ubuntu2 was the one from Adept and the compiled KAlarm is KAlarm 1.4.20 (Using KDE 3.5.8) After I installed and KDEPIM and reboot, KDE came up with window with first time using KDE options. Mine is the 64bit 7.10 Gusty Gibbon, Do you have the 32bit or 64bit version? Maybe it only occurs with one of them. Or it could be that I installed it via adept and then compiled a later version, but the duplicate of the bug didn't say any thing about compiling it... ops... kalarm from adept is 4:3.5.7enterprise20070926-0ubuntu2 must have typed the digit before 0ubuntu2 wrong p.s. looking at the dates... this one came after the one that is marked duplicate... I made a duplicate. I tried it out some more and it looks like some settings are saved and some are not, even though KAlarm crashes... It doesn't save "Start of day for date-only alarms",... yet it saves "Font & Color", "Confirm acknowledgment" "Maximum number of alarms",... Same here with KDE 3.5.8 on Kubuntu 7.10 32bit Kalarm 1.4.15 Could all reporters of this bug please let me know whether the executable xterm exists on your system. It will normally be /usr/bin/xterm. Type the following command in a terminal window to check whether it exists there or elsewhere:
which xterm
Fixed for KDE 3.5 and KDE 4 (SVN commits 747274, 747283, 747284). The fix will be in versions 1.4.21 and 1.9.10 beta. The new update(1.4.21) fixes the problem! I tired the command which xterm that return nothing looked for /usr/bin/xterm and the directory wasn't there |