Wyrd produces an error message on start: "Error in reminders file: "Error reading file ~/.reminders: Can't open file""

Bug #68152 reported by Robin Sheat on 2006-10-25
6
Affects Status Importance Assigned to Milestone
wyrd
Undecided
Unassigned
wyrd (Ubuntu)
Undecided
Unassigned

Bug Description

When launching wyrd, it draws as expected, and then spits out this error at the bottom of the screen. It then behaves almost normally, aside from not having any reminders that it knows about.

Remind is being launched by the following:
[pid 10122] execve("/usr/bin/remind", ["remind", "-s", "-l", "-g", "-b2", "~/.reminders", "Sep", "1", "2006"], [/* 1 var */]) = 0

the '~' on the pathname isn't being translated by the shell, and so remind fails.

(I think this is something to do with calls to 'sh' now behaving more like the original 'sh' shell rather than having a bash-nature to them. That's just a hunch though)

Robin Sheat (eythian) wrote :

A few notes: attempting to edit reminders results in similar errors, e.g pressing 'enter' on a time causes '/bin/sh: +999999: not found' to be output to the console.

The '~/.reminders' reference comes from /etc/wyrdrc. Changing it to '$HOME/.reminders' doesn't help.

Joseph Iacobucci (gtg312i) wrote :

I get the same error when I try to use wyrd. remind works. I created a .reminders file, but it will not open it from wyrd.

Changed in wyrd:
status: Unconfirmed → Confirmed
Dan O'Huiginn (daniel-ohuiginn) wrote :

I can confirm this. Workaround is:
1) copy /etc/wyrdrc to .wyrdrc in your home directory
2) edit the line
set reminders_file="~/.reminders"
so that it doesn't rely on expansion of ~:
set reminders_file="/path/to/your/home/dir/.reminders"

I imagine you could also edit /etc/wyrdrc in situ, if you're the only user of the computer.

Dan O'Huiginn (daniel-ohuiginn) wrote :

I have now emailed the upstream author about this.

Changed in wyrd:
status: Unconfirmed → In Progress
Paul Pelzl (pelzlpj) wrote :

I am "upstream". I'm hoping to get a Wyrd release out the door in about the next week, and that will include a fix for this bug. Could someone take a few minutes to verify that this development snapshot corrects the problem?

http://www.eecs.umich.edu/~pelzlpj/wyrd/wyrd-1.4.2pre2.tar.gz

Paul Pelzl (pelzlpj) on 2010-10-21
Changed in wyrd:
status: In Progress → Fix Released
Changed in wyrd (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers