Bug 152564 - Crashes when clicking OK in Configure KAlarm
Summary: Crashes when clicking OK in Configure KAlarm
Status: CLOSED FIXED
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
: 152168 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-11-19 18:30 UTC by BryanFRitt
Modified: 2008-07-02 15:00 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 BryanFRitt 2007-11-19 18:31:01 UTC
Version:           1.4.20 (using KDE 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.1)
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.22-14-generic

When I start KAlarm then click Settings->Configure KAlarm-> then click OK it crashes, it will do this rather or not any setting were changed
KUbuntu 7.10 64bit, added PIM then installed the latest stable KAlarm (1.4.20) via compile.  I tried uninstalling and recompiling, but still the same error.  Even tried going back to the one in version in adept, but still same error.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47780705032960 (LWP 4347)]
[KCrash handler]
#5  0x00002b74c94dee87 in QString::mid () from /usr/lib/libqt-mt.so.3
#6  0x00000000004d8d91 in translateXTermPath ()
#7  0x00000000004da675 in Preferences::save ()
#8  0x00000000004e5add in MiscPrefTab::apply ()
#9  0x00000000004ea300 in KAlarmPrefDlg::slotApply ()
#10 0x00000000004dccb6 in KAlarmPrefDlg::slotOk ()
#11 0x00002b74c6e8093c in KDialogBase::qt_invoke ()
   from /usr/lib/libkdeui.so.4
#12 0x00000000004dbf20 in KAlarmPrefDlg::qt_invoke ()
#13 0x00002b74c91dcd76 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002b74c91dd910 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#15 0x00002b74c955318f in QButton::clicked () from /usr/lib/libqt-mt.so.3
#16 0x00002b74c92779c3 in QButton::mouseReleaseEvent ()
   from /usr/lib/libqt-mt.so.3
#17 0x00002b74c92114c4 in QWidget::event () from /usr/lib/libqt-mt.so.3
#18 0x00002b74c91782a2 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#19 0x00002b74c917a400 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#20 0x00002b74c77d7248 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#21 0x00002b74c910ad84 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#22 0x00002b74c910998e in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#23 0x00002b74c9107b5a in QApplication::x11ProcessEvent ()
   from /usr/lib/libqt-mt.so.3
#24 0x00002b74c911e43e in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#25 0x00002b74c91917e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0x00002b74c91915ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0x00002b74c9179d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0x0000000000447a85 in main ()
Comment 1 David Jarvie 2007-11-19 19:01:00 UTC
*** Bug 152168 has been marked as a duplicate of this bug. ***
Comment 2 BryanFRitt 2007-11-19 20:03:07 UTC
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!
Comment 3 BryanFRitt 2007-11-19 20:25:52 UTC
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.
Comment 4 David Jarvie 2007-11-19 20:40:59 UTC
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.
Comment 5 BryanFRitt 2007-11-19 20:52:58 UTC
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)
Comment 6 BryanFRitt 2007-11-19 21:03:44 UTC
After I installed and KDEPIM and reboot, KDE came up with window with first time using KDE options.
Comment 7 BryanFRitt 2007-11-20 00:54:23 UTC
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.
Comment 8 BryanFRitt 2007-11-20 01:23:05 UTC
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",...
Comment 9 Jaro 2007-11-25 19:47:22 UTC
Same here with KDE 3.5.8 on Kubuntu 7.10 32bit
Kalarm 1.4.15
Comment 10 David Jarvie 2007-12-11 15:51:37 UTC
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

Comment 11 David Jarvie 2007-12-11 17:03:55 UTC
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.
Comment 12 BryanFRitt 2008-01-02 04:22:25 UTC
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