Bug 325 - Can't install workrave after exiting it
Status:
RESOLVED WORKSFORME
Component:
Core
Version:
unspecified
Hardware:
Other Other
Importance:
P2 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
Reported:
Oct 13 2003 23:54:20 UTC
by:
Kees-Jan Dijkzeul
Modified:
Nov 4 2003 05:33:13 UTC
WhoWhenWhatRemovedAdded
Raymond PennersOct 14 2003 00:15:38 UTCresolutionWONTFIX
statusNEWRESOLVED
Kees-Jan DijkzeulOct 14 2003 00:41:15 UTCstatusRESOLVEDREOPENED
resolutionWONTFIX
summaryCan't install workrave after crash.Can't install workrave after exiting it
Raymond PennersNov 4 2003 05:33:13 UTCresolutionWORKSFORME
statusREOPENEDRESOLVED
Description
Kees-Jan Dijkzeul  Oct 13 2003 23:54:20 UTC
Wr 030922 crashed (see bug 324). After that I attempted to upgrade to 031013. 
However, the installer refuses, claiming that wr is still running and asking me 
to close it.

However, there is no running wr to be found on screen or in the task manager 
(though the Windows ME taskmanager seems a little incomplete, so it may be 
missing something).
Comment 1
Raymond Penners  Oct 14 2003 00:15:38 UTC
Workrave creates a named mutex when it is started. The installer checks to see
if this mutex exists, and assumes that Workrave is running. Apparently, during
your crash, Windows messed up and did not free all resources, at least not the
mutex. A reboot will surely help. 

Marking invalid, it is just not doable to have Workrave crash nicely, and
cleaning up after it is not Workrave's task.
Comment 2
Kees-Jan Dijkzeul  Oct 14 2003 00:41:15 UTC
I was a bit hasty. I reproduced this bug without crashing workrave :-).

The same message gets shown after just exiting workrave.
Comment 3
Raymond Penners  Oct 14 2003 05:08:12 UTC
Did you reproduce this during a clean Windows session in which no Workrave crash
occured? As in, does this hold?:

(!exists t : windows_reboot_time <= t <= reproduction_time : crash_at(t))

If not => WONTFIX
Comment 4
Raymond Penners  Nov 4 2003 05:33:13 UTC
Time-out...