[Bug 909189] Re: Request for new upstream version 1.2 upgrade.

newbuntu 909189 at bugs.launchpad.net
Fri Jan 6 16:36:52 UTC 2012


Okay, thanks. Just for clarification, do such temporary files need to be
generated randomly? There are 2 files I am specifically concerned about.
These are the files which play the actual alarms (ie, the alarms are
executable bash scripts called by /usr/bin/wakeup):

1. ~/.wakeup/playable_tmp: this is generated by wakeup-settings via alarm.py and is made executable, but is never run with elevated access. It is deleted as soon as the wakeup-settings window is closed. Does this have to have a random file name?
2. ~/.wakeup/alarm[#]/playable_text: this is also generated by wakeup-settings via alarm.py and made executable, but is run from cron, either root's or user's depending on whether the boot-for-alarm option is checked. This must be generated in a random file every time the alarm is run?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/909189

Title:
  Request for new upstream version 1.2 upgrade.

Status in “wakeup” package in Ubuntu:
  New

Bug description:
  Adds some important features (user-defined hot text items/commands),
  as well as some important bug fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wakeup/+bug/909189/+subscriptions



More information about the Ubuntu-sponsors mailing list