! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Running a procedure as as an alarm doesn't always work
Status:
CLOSED: WORKSFORME

Comments

Description Scott 2011-11-09 13:37:21 CET
I'm trying to use Orage as a daily alarm clock.  I want to access an internet radio stream using google-chrome at the alarm time.  When I test the alarm (by setting the time to a few minutes ahead and waiting to see if it works), the procedure executes properly and the internet stream starts like it should.  However, when I let it sit overnight to actually use it, the procedure does not appear to run.

I did enable a visual notification, and that appears to come up.

I do not use power settings to put the computer to sleep, though the display is turned off after 10 minutes of inactivity.

I'm using Xubuntu 11.10 with Orage 4.7 on a Acer Aspire One AOA-110 with 1.5GB RAM.
Comment 1 juha editbugs 2011-11-09 14:01:08 CET
if you get the visual alarm, we know that the alarm actually works.
So the question is why the procedure type alarm does not work.

Could you run a test and replace the procedure alarm by something simple, like:
date >> /tmp/orage_test.txt

Then we could see from the file if the alarm fired or not. Or if the issue is actually in the procedure script.

What is the exact Orage version? Do 
orage -v
and paste the results.

Perhaps you could also export the problematic event and paste it, so that I can try to reproduce it locally.
Comment 2 Scott 2011-11-10 03:00:55 CET
OK, here's the deal.  Apparently I'm running v4.8.1

scott@scott-AOA110:~$ orage -v	

This is orage version 4.8.1	
Released under the terms of the GNU General Public License.	
Compiled against GTK+-2.24.4, using GTK+-2.24.6.	
Using DBUS for import.	
Using libnotify.	

Using automatic archiving.	
Using operating system package libical.
scott@scott-AOA110:~$

I tried the date >> /tmp/orage.txt, and it seemed to work when I set the alarm for the next minute.  But when I used the "execute" button, it didn't work.  The notification window did come up in both cases.  I'm running a test right now that will see whether the procedure works after the screen turns off.  I'll let you know those results when I get them.

Here's the procedure I'm trying to run...

google-chrome http://www.klove.com/listen/player.aspx

As above, when I set the alarm time for a minute from now, the procedure seems to execute correctly.  However, when I use the "execute" button, it appears to drop the argument as chrome opens to my homepage instead of the streaming site.
Comment 3 juha editbugs 2011-11-10 12:49:26 CET
Yes, that execute button problem is bug 7848. (fixed in 4.8.2)

But that does not explain why your procedure does not run properly after a longer wait. Waiting for your test results.
Comment 4 Scott 2011-11-10 12:52:33 CET
So per my testing, the "date >> orage.txt" command seems to work, even after an extended period (overnight).  So there's something about running chrome (or perhaps other executables) that Orage doesn't like (or some dependency doesn't like).

Thanks,
Scott
Comment 5 juha editbugs 2011-11-10 13:06:44 CET
Orage is not doing anything special for that command. It is just thrown to the system command.

Don't you see any errors in the terminal? (start orage from a terminal so that you can see it's messages.) Or in the .xsession-errors if orage is running in the background?

Maybe google-chrome is not in the path? Try with absolute path?

You might also try to call a simple shell sript without any parameters and just put the real command into that shell script.
Comment 6 Scott 2011-11-10 13:16:12 CET
The command does work, as long as I'm testing by setting the alarm time for, say, a minute in the future and waiting for it.  It's just when I let the computer sit for a while (like overnight) that it doesn't.
Comment 7 juha editbugs 2011-11-12 14:32:39 CET
No ideas, but I doubt this is Orage problem.
Perhaps something changes in the OS when it is idel long time, looks really strange.
Comment 8 Scott 2011-11-14 13:40:14 CET
So it looks like taking the procedure command and argument, putting it in a Bash scrip file, and changing the procedure to execute the script worked, at least this morning.
Comment 9 juha editbugs 2011-11-24 09:28:34 CET
Very strange issue. But I have no clue how to fix it.

Bug #8127

Reported by:
Scott
Reported on: 2011-11-09
Last modified on: 2012-01-09

People

CC List:
0 users

Version

Attachments

Additional information