Same, 3.7 when closing the window doesn't show crash error anymore. My workaround is to revert back to Winbox v3.7 Then when back at the connect window pick file and then exit. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4).Ī workaround seems to be click on the session menu and pick disconnect. When quitting winbox wine is left running. Downgrading to Winbox 3.7 solves the problem. I am still seeing the same thing using "Crossover", remaining Winbox processes after exiting. ![]() If any assistance is required testing please feel free to let me know. I realize this is a bit outside normal support (I am attempting to run winbox on a mac) but since it was working in 3.7 it seems there is a regression in 3.8 (and 3.9) to a state where it no longer closes completely. If you just open winbox and don't connect to a device and then click either the os x menu close button, or pick the file menu and select exit, winbox closes as expected and wine doesn't leave any extra processes running. Also using force close to terminate the wine process works. Right clicking on the icon in the dock and picking quit doesn't actually quit things. Running killall wine will close any outstanding processes. Observed result: Winbox's windows closes but the process is still left running. click on the session menu and then select exit (or click on the exit button on the left menu)Įxpected result: Winbox closes and completely exits. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4) When quitting winbox wine is left running. ![]() Noticed this in 3.8 but now I see 3.9 is out and it still occurs.
0 Comments
Leave a Reply. |