https://bugs.winehq.org/show_bug.cgi?id=50211
Bug ID: 50211 Summary: Quicken crashes on start with page fault on read access to 0x00000000 Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: wine@themudrest.com Distribution: ---
Created attachment 68718 --> https://bugs.winehq.org/attachment.cgi?id=68718 backtrace
This has been working great for years but this week now fails to start, does not get as far as the splash screen.
Its an old version of quicken, quicken XG
Please advise what extra information or testing is needed.
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #1 from Kevin Swift wine@themudrest.com --- Actually version Release 2,2004
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #2 from Kevin Swift wine@themudrest.com --- Created attachment 68719 --> https://bugs.winehq.org/attachment.cgi?id=68719 "Wine Uninstall Software" also fails.
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #3 from Kevin Swift wine@themudrest.com --- Attempting to uninstall also fails, see attached
https://bugs.winehq.org/show_bug.cgi?id=50211
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Quicken crashes on start |Quicken 2004 XG Release 2 |with page fault on read |crashes on startup |access to 0x00000000 | CC| |focht@gmx.net Keywords| |regression
--- Comment #4 from Anastasius Focht focht@gmx.net --- Hello Kevin,
do you know the last "good" version of Wine when it still worked? Wine 5.21?
I've updated the summary line to be more specific since there are multiple bugs for multiple Quicken versions.
Found Quicken 2004 Deluxe Release R4 here:
https://www.quicken.com/support/how-and-when-use-intermediate-version-conver...
https://web.archive.org/web/20171203034100/https://assistant.quicken.com/pat...
But I couldn't reproduce the crash on start. Runs fine here with Wine 5.22 and HEAD (current git).
If you reused an old WINEPREFIX throughout Wine upgrades could you try to install into a new/separate WINEPREFIX ("virtual c: drive")?
https://wiki.winehq.org/FAQ#Can_I_store_the_virtual_Windows_installation_som...
---
Current list of regressions reported against Wine 5.22
https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NE...
$ sha1sum QW04DLX.exe 09e7d6583ba7a5b85e94da8ec135df76c19c0ead QW04DLX.exe
$ du -sh QW04DLX.exe 48M QW04DLX.exe
Regards
https://bugs.winehq.org/show_bug.cgi?id=50211
Arc C. achapkis@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |achapkis@gmail.com
--- Comment #5 from Arc C. achapkis@gmail.com --- I have similar issue with Quicken Deluxe 2000: just updated my Fedora 32 system with the latest packages including wine (going from 5.17-1 to 5.22.-1) and my Quicken crashes on startup with the following:
Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x5f40fce8).
I can attach my backtrace here.
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #6 from Arc C. achapkis@gmail.com --- Created attachment 68760 --> https://bugs.winehq.org/attachment.cgi?id=68760 Backtrace from Quicket deluxe 2000
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #7 from Anastasius Focht focht@gmx.net --- Hello achapkis,
--- quote --- I have similar issue with Quicken Deluxe 2000 --- quote ---
Quicken 2000 Deluxe installs and runs fine here using:
http://www.oldversion.com/windows/download/quicken-2000-deluxe
From your backtrace:
--- snip --- 0000005c jqs.exe ["C:\Program Files (x86)\Java\jre6\bin\jqs.exe" -service -config "C:\Program Files (x86)\Java\jre6\lib\deploy\jqs\jqs.conf"] --- snip ---
That's certainly not part of software from year 1999. Java SE 6 was released first in December 2006.
Don't reuse the same WINEPREFIX with different software installations. It makes bug reports potentially invalid. It's unlikely related to the problem here tho.
Anyway, I've debugged Quicken Deluxe 2000 using breakpoints on certain app functions from your crash callstack. The breakpoint on app plugin function 'BGTBRWSR_GenericInternetWindow' never triggers - although the plugin gets loaded.
Is your crash really on startup, without any user interaction (not clicked any menu yet)?
$ sha1sum Windows\ 2000\ Deluxe_QuickenWin2000Deluxe.zip 73869993d1c55cbe5567a5bd00a622030625ae46 Windows 2000 Deluxe_QuickenWin2000Deluxe.zip
$ du -sh Windows\ 2000\ Deluxe_QuickenWin2000Deluxe.zip 17M Windows 2000 Deluxe_QuickenWin2000Deluxe.zip
$ wine --version wine-6.0-rc1
Regards
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #8 from Arc C. achapkis@gmail.com --- There are few things I tried yesterday and today. I have another Fedora 32 computer, where I have not yet pulled down the latest updates. That one has wine-5.21 but never had any Quicken installed on. I pulled down the Quicken 2004 installation file available from Intuit and installed it on that wine-5.21. Ran OK, was able to import my previous data. Going back to this desktop with the latest wine-5.22 I tried to use the same installation file. It seems to install OK, but upon starting it I get the following error: "Your Quicken program files (not your data files) may have been damaged. You will need to reinstall Quicken."
So then I tried to remove ${HOME}.wine folder and start from scratch. Again, it installs just fine but then I receive the same error as above.
Then I tried to install the older Quicken 2000 Deluxe from the link you provided. It also installs fine (I used a different installation directory from Q2004) and when I start it seems to start OK with the registering dialog and Welcome dialog box, but after I click "OK" it says "Cannot open file" and crashes. I attached the new stack trace.
Note that I had Quicken 2000 Deluxe installed into my ${HOME}/.wine and working fine over the years, surviving multiple computer upgrades (all the the way from Fedora Core 9) up until I pulled down wine-5.22 packages a couple days ago.
I am not of much use to help with any programming, but hope I can help troubleshot this issue, let me know if there's anything you'd like me to try.
Thank you,
Arc C.
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #9 from Arc C. achapkis@gmail.com --- Created attachment 68783 --> https://bugs.winehq.org/attachment.cgi?id=68783 Fresh backtrace
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #10 from Anastasius Focht focht@gmx.net --- Hello Arc,
--- quote --- Note that I had Quicken 2000 Deluxe installed into my ${HOME}/.wine and working fine over the years, surviving multiple computer upgrades (all the the way from Fedora Core 9) up until I pulled down wine-5.22 packages a couple days ago. --- quote ---
while re-using the same WINEPREFIX with many Wine releases over many years is certainly preferred by end-users, it won't work all the time. Over time it will accumulate files and registry entries that might cause a breakage at one point. If you share the prefix with multiple applications the risk is even higher. Sometimes it's better to start over with fresh prefix. That's why its important to keep personal data always separate from the WINEPREFIX itself ("virtual c: drive"). Usually this is taken care of if you save to "My Documents" as it points outside of prefix into user's $HOME. But it's better to even further relocate your app-specific data into an own folder structure as these "special" folders are shared among prefixes.
Coming back to original problem: Your backtrace is essentially the same as previous one. I still can't reproduce the crash with clean (new) WINEPREFIX. Neither with Wine 5.22 nor with Wine 6.0-rc1
I get the same error 'Cannot open file' on first startup and just dismiss it. The app searches for '*.QDF', '*.QDB' and '*.QDT' in 'C:\QUICKENW' (default install dir). Since nothing is found the app tries to open 'C:\QUICKENW\~QW~LINK.QDF' which doesn't exist either. It gets created the first time one creates a new project -> error is harmless.
After that the splash screen disappears. The main user interface is shown and I create a new project (via file menu). This gets one to the 'Account setup' and input of actual finance data.
I'm on Fedora 32 as well, with XFCE desktop.
Summarizing: You install Quicken 2000 Deluxe in a fresh (new) WINEPREFIX = no other software installed and still get the crash on first run?
Could you run the following command in terminal ("cd" to Quicken installation directory before):
--- snip --- WINEDEBUG=+seh,+relay,+loaddll,+win,+msg wine ./QW.EXE >>log.txt 2>&1 --- snip ---
The log file will be large. You need to compress it before attaching to the bug report.
--- snip --- tar cjvf log.tar.bz2 log.txt --- snip ---
Attach 'log.tar.bz2' file to the ticket.
Regards
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #11 from Arc C. achapkis@gmail.com --- Hello Anastasius,
I somehow receive strange results. Before your update I tried to downgrade wine with "dnf downgrade wine", the only available version was 5.5-1, so I went with it. Then I removed my ${HOME}/.wine again and installed Quicken 2000 and 2004. Both started up OK without any issues.
Then I updated all the wine packages back (or rather forward) to 5.22-1 and tried again with those Quicken 2000 and 2004 that were already installed in .wine. Again the problem came back. So I tried to run the command with debugging, the way you suggested to collect the debugging output. But somehow running it with debugging does not crash, the program works as it should be, albeit a bit slow (naturally dumping a lot into the output file).
So between these two commands:
WINEDEBUG=+seh,+relay,+loaddll,+win,+msg wine ./QW.EXE
~/wine_quicken_2000_debug_log.txt 2>&1
wine ./QW.EXE
The first brings up Quicken2000 and is working, the second brings up Q2000 and crashes.
I can attach the compressed debug log, but I am not sure it will be of any help since it doesn't crash.
I use KDE as my desktop. Do you think this may matter?
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #12 from Arc C. achapkis@gmail.com --- Created attachment 68786 --> https://bugs.winehq.org/attachment.cgi?id=68786 Output of .wine and qicken 2000 installation
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #13 from Arc C. achapkis@gmail.com --- Hi Anastasius,
I just wiped out my .wine and tried installing and running Quicken 2000 again, this time I attached an output of my steps.
Thank you,
Arc C.
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #14 from Arc C. achapkis@gmail.com --- As a test, I went ahead and removed all the wine packages provided by Fedora repo and installed the packages from WineHQ. So this is what I have now:
root@caocao~# dnf list installed wine* Installed Packages wine-staging-common.i686 1:6.0.rc1-3.1 @WineHQ wine-staging64.x86_64 1:6.0.rc1-3.1 @WineHQ winehq-staging.x86_64 1:6.0.rc1-3.1 @WineHQ
With this I was able to install and run Quicken 2000 just fine. One difference I noticed is that with brand new .wine the winecfg from the Fedora-provided 5.22-1 does not install anything else, whereas winecfg from 6.0.rc1 installs mono and gecko. Fedora does provide wine-mono package which I did have installed with 5.22-1 though.
I am not sure if this information of any use to you, let me know if there's anything else I can provide.
Thank you,
Arc C.
https://bugs.winehq.org/show_bug.cgi?id=50211
--- Comment #15 from Kevin Swift wine@themudrest.com --- I am running openSUSE Leap 15.2, the failing versions reported here were:
q4wine-1.3.7-lp152.3.10.x86_64 q4wine-lang-1.3.7-lp152.3.10.noarch wine-32bit-5.22-lp152.1222.1.x86_64 wine-5.22-lp152.1222.1.x86_64 wine-gecko-2.47.1-lp152.57.1.noarch wine-mono-5.1.1-lp152.17.1.noarch winetricks-20200412-lp152.23.1.x86_64
This weekend with the latest SUSE updates, wine has updated to 6.0-rc1:
q4wine-1.3.7-lp152.3.10.x86_64 q4wine-lang-1.3.7-lp152.3.10.noarch wine-32bit-6.0~rc1-lp152.1229.1.x86_64 wine-6.0~rc1-lp152.1229.1.x86_64 wine-gecko-2.47.2-lp152.58.1.noarch wine-mono-5.1.1-lp152.17.1.noarch winetricks-20200412-lp152.23.1.x86_64
Now Quicken is working again for me. I think I plan to try to upgrade to something newer or native Linux.
In answer to the questions in comment 4.
The failure on 5.22 occurred in a new prefix as well so it didn't seen to be a problem with the existing configuration.
Unfortunately I don't have the previous working version to hand.
https://bugs.winehq.org/show_bug.cgi?id=50211
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #16 from Alexandre Julliard julliard@winehq.org --- Reported fixed in 6.0-rc1.
https://bugs.winehq.org/show_bug.cgi?id=50211
Kevin Swift wine@themudrest.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine@themudrest.com
https://bugs.winehq.org/show_bug.cgi?id=50211
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #17 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 6.0-rc2.