Run Do from a terminal with the --debug flag. That way if it crashes you should see a stack trace. It's quite possible this bug is a duplicate of another bug.
Ok i will do this tomorow ... so to be more precise it stais open for a long time but yesturday it just died bi it self and i wasn`t using the machine and today it happened again ... so i think there might be some conflick and something is killing him but this happens after a fair amout of time (hours)
Actually I would like to also submit that it randomly crashes for me as well on Jaunty 9.04. I disabled all but one plugin (tracker) and it seems to be stable this far. I am running it with --debug and hopefully I'll have something to report back when/if it crashes. I feel it was the delicious plug-in that crashed it for me but have no proof and considering its not a official plug-in I feel part of my issue was that plugin.
Well after disabling all community plugins and using minimal official plugins Gnome-Do is very stable. Looks like the un-official plugins are the culprit.
OK guys i reinstalled my ubuntu this days and with it do and now looks really stable with all the plugins i need so i guess something was killing it ...
I have a fresh install of Ubuntu 9.04 and the latest gnome-do and it also crashes with no warning sometimes. I do not use the delicious plug-in so I doubt it has anything to do with that plug-in. I have been using gnome-do for about a week and it crashes about every 12-14 hours. I only use a couple extra plug-ins like google-search, google-maps, archiver, disk-mounter, and the read-man-pages community plug-ins. If others a using these and having the same problems maybe you should list them here to help track down the offending bug. I will also try running in debug to get the stack trace to post here.
I have just finally got a small stack trace. It would have been sooner but it seems that you are not using the standard error stream so all I was getting in the debug log was information about events it was doing during normal operation and the stack trace would go to the terminal not the log. Well here it is:
'Exception in Gtk# callback delegate
Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.NullReferenceException: Object reference not set to an instance of an object
at GLib.Timeout+TimeoutProxy.Handler () [0x00000]
at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
at GLib.Timeout+TimeoutProxy.Handler()
at Gtk.Application.gtk_main()
at Gtk.Application.Run()
at Do.Do.Main(System.String[] args)'
I think it has something to do with the mount plugin because I have a apple TimeCapsule router/nas that I log into and I have set the permissions to +s on the execution bit so I don't have to be root to mount things to my home directory. It seems that because I also have several different points I mount on the TimeCapsule that if I try to mount them in an order different to what is in my /etc/fstab I can crash 'Do' on demand. I have also noticed that 'Do' is throwing exceptions about firefox:
'Firefox.PlacesItemSource "Firefox Places" encountered an error in UpdateItems: Object reference not set to an instance of an object.
closing
closing
closing
' but I will file a separate bug for that one as there is more to it than just that.
Try to get a stack trace or log or something.
Run Do from a terminal with the --debug flag. That way if it crashes you should see a stack trace. It's quite possible this bug is a duplicate of another bug.