Activity log for bug #226816
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2008-05-05 08:58:47 | cdemoulins | bug | added bug | ||
| 2008-06-11 11:45:54 | Richard Harding | do: status | New | Confirmed | |
| 2008-08-05 06:43:14 | Chris Halse Rogers | do: status | Confirmed | Incomplete | |
| 2008-08-05 06:43:14 | Chris Halse Rogers | do: importance | Undecided | Medium | |
| 2008-08-05 06:43:14 | Chris Halse Rogers | do: statusexplanation | I also seem to get this. I also had it in the previous version and it's showed up in the new 0.5.0.1 release as well a couple of times so far. I've tried running from the command line to see what's up. It will show as running in the process list, but neither the key command nor running the command gnome-do will bring it back up. Killing and restarting it is the only way to get it going. It's very inconsistent though. It may go hours and hours before "locking up" again. | I *think* this is related to a deadlock we traced down in the Google Calendar plugin. It's possible that the Rhythmbox plugin also suffers from a similar problem. Can either of you duplicate this problem with neither of Google Calendar and Rhythmbox enabled? You should restart Do after disabling them. | |
| 2008-08-05 06:44:34 | Chris Halse Rogers | do: assignee | raof | ||
| 2008-08-05 06:44:34 | Chris Halse Rogers | do: statusexplanation | I *think* this is related to a deadlock we traced down in the Google Calendar plugin. It's possible that the Rhythmbox plugin also suffers from a similar problem. Can either of you duplicate this problem with neither of Google Calendar and Rhythmbox enabled? You should restart Do after disabling them. | ||
| 2008-08-07 23:05:56 | Jason Smith | do: status | Incomplete | Fix Committed | |
| 2008-09-14 03:39:43 | Chris Halse Rogers | do: status | Fix Committed | Fix Released | |
| 2008-09-14 03:39:43 | Chris Halse Rogers | do: assignee | raof | ||
| 2008-09-14 03:39:43 | Chris Halse Rogers | do: statusexplanation | This should be fixed in 0.6.0.1 |
