terminal commands not remembered in Ubuntu 11.04

Bug #780790 reported by Alan Mandler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Automate
New
Undecided
Unassigned

Bug Description

(Just switched from 10.4 to 11.04. Love your product.) Let's say I have multiple alarms. If I specify a terminal command in one, as I go through the others, I see that the last command entered (for the previous alarm) appears in the dialog box for the next. If I go back to previous alarm, the previously specified alarm is lost. If I restart my session, most or all of the commands are lost. (Could it be permissions problem somewhere?) Thanks!

Revision history for this message
Johannes H. Jensen (joh) wrote :

Which version of alarm-clock-applet are you running? I'm not sure I understand how to reproduce this? Could you provide step-by-step instructions?

Revision history for this message
Alan Mandler (alan-saidanotherway) wrote :

I started from scratch.

First and second screen shots show that no terminal action was specified for two of my alarms: one that stops Dropbox and another that restarts it.

Third screen shot taken after I specified a terminal command for the "Start Dropbox" alarm ("dropbox start").

Fourth screen shot taken after I opened the terminal setting for the "Stop Dropbox" It shows that "dropbox start" was in the settings window although I didn't enter it. In other words, it appeared because of the previous alarm setting.

Not shown: I changed the "Stop Dropbox" terminal command to be "dropbox stop".

I then restarted the computer and re-opened the setting windows. Both terminal execution statements were missing.

Revision history for this message
Alan Mandler (alan-saidanotherway) wrote :

Ooops. Forgot to answer your question. I am using version 1.25, freshly downloaded from Ubuntu's Software Center. (BTW: The link inside of the About box is broken.)

Revision history for this message
Johannes H. Jensen (joh) wrote :

Yeah, that's not a screenshot of alarm-clock-applet. You're reporting against the wrong package.

Maybe this is what you're using: https://launchpad.net/alarmclock/

affects: alarm-clock → alarmclock
Revision history for this message
sabby7890 (tsalacinski) wrote :

This is an old version, this bug is fixed in newer releases. Soon the application will be renamed to GNOME Automate, so the name will change and package alarm-clock will be deprecated.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.