wakeup

new alarm will not allow time to be set

Bug #998927 reported by Eric Draven
40
This bug affects 6 people
Affects Status Importance Assigned to Milestone
wakeup
Fix Released
Undecided
Unassigned

Bug Description

as instructed i belive ive found a new bug. i am running ubuntu 12.04LTS and am a newb so be nice im just trying to help.

alarm0: Loaded wakeup settings
no crontab for root
Traceback (most recent call last):
  File "/usr/share/wakeup/setnextalarm.py", line 63, in <module>
    curcron = subprocess.check_output(['sudo', 'crontab', '-l'])
  File "/usr/lib/python2.7/subprocess.py", line 544, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['sudo', 'crontab', '-l']' returned non-zero exit status 1

thats what i get when i run the coomand line and yes im making a crontab for root to see if this fixes the issue

See original description

Related branches

lp:ubuntu/quantal/wakeup
Revision history for this message
Eric Draven (evileric3) wrote :

ive added a contab to root to see if that was the issue and still no luck. now going to start trying other things. will report as soon as i have a fix, if i find a fix.

description: updated
Revision history for this message
Eric Draven (evileric3) wrote :

OK ive got the fix for you guys if anyone els has the same problem. you MUST first make a crontab in root befor wakeup will work it dose not make one for you and sudo will not let you make one either so break out su guy guys and crontab -e make some fake crontab job up then run wake up and save your preferances works like a charm now and dont forget to delete the fake cron job
thanks

Revision history for this message
newbuntu (dsglass) wrote :

Thanks for reporting this bug. You should be able to run sudo crontab -e to set up cron for the first time before running wakeup. I will work on a fix for this to include in the next version, but for the current the easiest is to just use the workaround suggested by Eric:

$ sudo crontab -e

newbuntu (dsglass)
Changed in wakeup:
status: New → Fix Released
Revision history for this message
newbuntu (dsglass) wrote :

Fixed in version 1.3

Revision history for this message
nameremoved (errorwhywhywhy-deactivatedaccount) wrote :

This bug also occurs in quantal.

Revision history for this message
newbuntu (dsglass) wrote :

Quantal is not yet updated to version 1.3.

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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