GNOME Automate

power interruption and alarm clock

Asked by worldhello

Hi,
I'm running alarm-clock 0.9.19 in 32 bit Karmic. It's been doing just fine until last night,
when I ran the laptop on AC only and I accidentally pulled the power cable. When I
restarted the machine and ran alarm-clock, I got the following error messages in xterm:

Traceback (most recent call last):
  File "/usr/bin/alarm-clock", line 44, in <module>
    alarmclock.MainClass.StartGUI().Initialize()
  File "/usr/lib/pymodules/python2.6/alarmclock/MainClass.py", line 146, in Initialize
    StartGUI().RunMe(Min)
  File "/usr/lib/pymodules/python2.6/alarmclock/MainClass.py", line 186, in RunMe
    self.LoadConfigFiles()
  File "/usr/lib/pymodules/python2.6/alarmclock/MainClass.py", line 2898, in LoadConfigFiles
    self.ParseTupletToList(line)
  File "/usr/lib/pymodules/python2.6/alarmclock/MainClass.py", line 2936, in ParseTupletToList
    string = eval(line)
TypeError: expected string without null bytes

I assumed this is because of some lock-type files not properly cleared, but I didn't know where
to look. I did a "complete removal" using the synaptic package manage, followed by an reinstall,
but the problem persists. Your comments and suggestions are most welcome!

THANKS!

Question information

Language:
English Edit question
Status:
Answered
For:
GNOME Automate Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
sabby7890 (tsalacinski) said : 		#1

This happens when alarms are not correctly saved, and because of bug in older version of Alarm Clock (the one you're using). This version performed read operation on hard drive every second (which was very bad for laptops with SSD drives). Right now, it just loads the configuration into memory (as it should). If the configuration is bad, Alarm Clock 1.3 may not display any templates or alarms, but it should run correctly (it has better error checking with GTK).

Revision history for this message
sabby7890 (tsalacinski) said : 		#2

Ah, this is not complete answer. Setting "purge" in synaptic won't remove configuration directory. Alarm Clock stores it's configuration in ~/.config/Alarm-Clock.

Replace ~ with your home directory. Remove settings directory and everything should be back to normal. You may also consider upgrading to 1.3, since it has some new features and works a lot better.

Can you help with this problem?

Provide an answer of your own, or ask worldhello for more information if necessary.

To post a message you must log in.