Gnome-do (and probalby other mono apps) won't start after broken hibernation

[Ve2dmn]

Binary package hint: gnome-do

This bug could be classified as "wishful" and "behavioral" rather than a bug.
Gnome-do crashed on startup. This happen following a failed hibernation attempt which force the hard power-off of the laptop. The lock files were left in place, and the application would not start. Starting gnome-do in a terminal produced:

** (/usr/lib/gnome-do/Do.exe:2725): CRITICAL **: _wapi_shm_file_open: shared file [/home/tron/.wapi/shared_data-ubuntu-Linux-i686-312-12-0] open error: Input/output error

** (/usr/lib/gnome-do/Do.exe:2725): CRITICAL **: _wapi_shm_attach: shared file [/home/tron/.wapi/shared_data-ubuntu-Linux-i686-312-12-0] open error
**
And the app would fail with a SIGABRT. The above errors which where easily corrected with the command "rm -R ~/.wapi"

Correct behavior would be to warn the user that "another instance is running" just like Kontact does, which then permit the user to still run the app despite the warning. Complete error listing is included in an attachement.

ProblemType: Bug
Architecture: i386
Date: Wed Nov 25 11:04:17 2009
DistroRelease: Ubuntu 9.10
Package: gnome-do 0.8.2+dfsg-1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: gnome-do
Uname: Linux 2.6.31-15-generic i686

[Ve2dmn (david-montminy)]

Relevant Forum post:
http://ubuntuforums.org/showthread.php?t=1317874

[Robert Dyer (psybers)]

This is actually a Mono problem directly. Do *does* check for a running instance on startup and refuses to start a second. The problem is that Mono itself crashes before Do has a chance to check that. Please file this bug against Mono.