This problem has been plaguing me for a long time. I tried the Both the rebooting trick and the window maximize trick to very limited success. I had even searched for every crossover process and killed it, to no avail. It was not until I discovered that the processes don't show as standard Linux processes.
[~] $ ps auxwww | grep ${USER} | grep -i "c:"
dean 9603 0.0 0.0 2646968 2840 ? Ssl 10:33 0:00 C:\windows\system32\services.exe
dean 9615 0.0 0.0 2658476 11344 ? Sl 10:33 0:00 C:\windows\system32\winedevice.exe MountMgr
dean 9621 0.0 0.0 2645484 2376 ? Sl 10:33 0:00 C:\windows\system32\plugplay.exe
dean 9666 0.0 0.0 2647680 2572 ? Ssl 10:33 0:00 C:\windows\system32\rpcss.exe
After quicken was closed and no other cxoffice application was running, I still see stray Windows style processes running. By killing them off before running Quicken,it starts normally. I have tested and restarted Quicken about 50 times with 100% success.
I wrote a little script that kills Windows processes that I can run before or after I run Quicken:
---Begin script --
!/bin/bash
cx_kill.sh
Quicken opens without menus when there
are residual processes running. This
script kills all running Windows proceses.
WARNING: This will not just target the
Quicken botle.
Get a list of PIDs related to Windows proceses
List="$(ps auxwww | grep ${USER} | grep -i "c:" |grep -v grep | awk '{print $2}')"
Cycle through each PID and kill it
for PIDs in $(echo -e "${List}")
do
kill -9 $PIDs
done
Send notification of the action
zenity --info --text="CX Kill Complete.\n${List}"
--end script--
I know that this is a sledgehammer approach, but it at least proves the cause of the issue and provides a solution for me.. Maybe someone can streamline my solution.
I hope this helps someone else.
Regards,
Dean
This issue has been forwarded to the Official CodeWeavers Ticket System. If you have observed this issue and would like to report it as well, please open a support ticket or send an email to info@codeweavers.com with a description of what you are seeing and a link to this post.
Thank you!
The CodeWeavers Team