http://bugs.winehq.org/show_bug.cgi?id=5130
------- Additional Comments From saulius.krasuckas@elst.vtu.lt 2007-24-05 11:21 ------- * Tom wrote: | I retraced my steps from after install thru what I did on the first run and it | still wont crash. My guess is that something is not initialized/ created during | install and is during first run, right after you hit close but before the | program closes. Then whatever it is that gets done, is already there on | subsequent runs and that prevents the crash.
Tom, I think about Wine state as of some collection of files ("~/.wine/drive_c/*") and registry entries. You could try finding minimal changes in files or registry, which stops Viewer crashing.
At first I'd try to determine, which part of Wine state is crucial: registry, drive_c files or both. For that I would install Viewer and would make a backup of registry (regedit /e BACKUP.reg) and BACKUP of actual files (cp -a ~/.wine/drive_c ~/.wine/drive_c_BACKUP).
Then I'd reinstall Wine, install fresh copy of Viewer, import BACKUP.reg and would see if crash is gone. If not, I'd repeat all this, except restoring registry - here would go file restoration. If not again, then both parts carriy crucial changes.
With crash gone I'd cut the restored part in a half (half of directories, half of files in a single directory, half of a registry branches) and would restore only one half of it. And so on, until only crucial changes are left.