kAlarm fails to start in Ubuntu 6.10

Have you tried adding it to System -> Preferences -> Sessions?

When I added /usr/bin/kalarm to startup items in the Sessions menu, it starts as it should. Just wish it would do that when installed.

Thanks for this report.

I am not sure if I understand the problem, however, it might just be that this issue is not relevant anymore.

if you install kalarm in gutsy, and you start it once, there is an option in the settings (that is actually by default enabled) that automatically starts kalarm up during login.

Could you please check if this is still an issue for you in gutsy?

Thanks

Ubuntu on my machine says Edgy Eft. I got it to work, I was just pointing out the installer was supposed to add it to the menus so I could get to the preference settings.

When I installed kalarm, it got added to the KDE-Menus under Utilities. Are you using KDE (Kubuntu) or Gnome (Ubuntu) as Desktop?

I'm using Gnome (Ubuntu) in Ubuntu 6.10

Thank You

Roger Oren
GLR Inc.
937-890-0510
937-890-3094 fax
3795 Wyse Rd
Dayton OH 45414

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
Ralph Janke
Sent: Saturday, December 01, 2007 5:04 AM
To: Roger Oren
Subject: [Bug 131606] Re: kAlarm fails to start in Ubuntu 6.10

When I installed kalarm, it got added to the KDE-Menus under Utilities.
Are you using KDE (Kubuntu) or Gnome (Ubuntu) as Desktop?

--
kAlarm fails to start in Ubuntu 6.10
https://bugs.launchpad.net/bugs/131606
You received this bug notification because you are a direct subscriber of
the bug.

As I understand, it is about that kAlarm will appear in the gnome menus in order to be started there.

I am not sure if the setting for automatic startup in gnome will work, since KAlarm is really inetgrated into KDE and not into gnome. Will test that on hardy as soon as ubuntu-desktop installs without dependency problems.

Ralph, did you ever get to test this?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!