On Thu, 2003-12-11 at 08:50, Donald Henson wrote: > On Thu, 2003-12-11 at 07:12, Dan Winship wrote: > > > > > did not start up. I logged off/on again. Same result. Then I used > > > > > (gasp!) a Windows technique. I rebooted the system. This worked. > > > > > Evolution came back up like there had never been a problem. > > > > > > > > Did you try "evolution --force-shutdown"? My guess is that you had > > > > some hung evolution process (logging off and logging back on does > > > > not necessarily kill all processes). > > > > > > > No, I didn't. Where's the evolution --force-shutdown button located? > > > I'm joking, of course, but my point is that ordinary users, such as > > > Windows refugees, are not going to take the time to learn how to use > > > the command line. > > > > Fortunately though, we've had no success in breaking Windows refugees > > from the habit of rebooting any time something goes wrong, so they don't > > need to learn the command-line way. :-} > > > > -- Dan > > I've only done it twice. :-) (It worked both times, though.) > > Don Henson If someone tries to run a second evolution (locally), how about popping up a window that says: You can only run one copy of evolution at a time. Kill old one and start again Leave old one and don't run another -- Dan Stromberg DCS/NACS/UCI <strombrg dcs nac uci edu>
Attachment:
signature.asc
Description: This is a digitally signed message part