[Bug 51876] New: "Program has encountered a serious problem"
https://bugs.winehq.org/show_bug.cgi?id=51876 Bug ID: 51876 Summary: "Program has encountered a serious problem" Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: anonsquest(a)protonmail.com Distribution: --- Created attachment 70800 --> https://bugs.winehq.org/attachment.cgi?id=70800 backtrace I am trying to run a program called ATAS trading I was able to install it successfully and even updated the program to the latest version. Then when I tried to run it, I got an error from wine saying it encountered a serious problem. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #1 from anonsquest(a)protonmail.com --- Created attachment 70801 --> https://bugs.winehq.org/attachment.cgi?id=70801 log -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #2 from Hans Leidekker <hans(a)meelstraat.net> --- Created attachment 70805 --> https://bugs.winehq.org/attachment.cgi?id=70805 patch Looks like it needs Win32_OperatingSystem.Status. Can you try this patch? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #3 from anonsquest(a)protonmail.com --- (In reply to Hans Leidekker from comment #2)
Created attachment 70805 [details] patch
Looks like it needs Win32_OperatingSystem.Status. Can you try this patch?
thanks for the suggestion. Because I have never patched wine before and I am relatively new to linux and github, I just wanted to be sure what I'm doing is correct. git clone git://source.winehq.org/git/wine.git cd wine git-apply patch #the patch you posted. git commit -a and then I'm a bit lost from here. Is there a way to build from the local git using pacman or yay? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #4 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to anonsquest from comment #3)
git clone git://source.winehq.org/git/wine.git cd wine git-apply patch #the patch you posted. git commit -a
and then I'm a bit lost from here. Is there a way to build from the local git using pacman or yay?
See https://wiki.winehq.org/Building_Wine for build instructions. I'll submit the patch anyway, so you could also wait and try again after the next Wine release. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #5 from anonsquest(a)protonmail.com --- perfect. Eager to try it after the patch. Would I have to remove wine and reinstall wine-staging? How long would it take approximately for the patch to be applied? Thanks -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #6 from anonsquest(a)protonmail.com --- (In reply to Hans Leidekker from comment #4)
(In reply to anonsquest from comment #3)
git clone git://source.winehq.org/git/wine.git cd wine git-apply patch #the patch you posted. git commit -a
and then I'm a bit lost from here. Is there a way to build from the local git using pacman or yay?
See https://wiki.winehq.org/Building_Wine for build instructions. I'll submit the patch anyway, so you could also wait and try again after the next Wine release.
oops forgot to hit reply. pinging now -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|"Program has encountered a |ATAS Trading crashes on |serious problem" |start -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #7 from anonsquest(a)protonmail.com --- Created attachment 70866 --> https://bugs.winehq.org/attachment.cgi?id=70866 backtrace backtrace log in 6.20 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #8 from anonsquest(a)protonmail.com --- Created attachment 70867 --> https://bugs.winehq.org/attachment.cgi?id=70867 /home/Documents/ATAS/Logs/app_20211022.log (In reply to Hans Leidekker from comment #4)
(In reply to anonsquest from comment #3)
git clone git://source.winehq.org/git/wine.git cd wine git-apply patch #the patch you posted. git commit -a
and then I'm a bit lost from here. Is there a way to build from the local git using pacman or yay?
See https://wiki.winehq.org/Building_Wine for build instructions. I'll submit the patch anyway, so you could also wait and try again after the next Wine release.
Hi, I installed the new 6.20 today and installed ATAS and updated it. After running it, it crashed again. Please see the 2 attachments. Thanks -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 anonsquest(a)protonmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux Version|6.19 |6.20 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #9 from joaopa <jeremielapuree(a)yahoo.fr> --- Unless backtrace is requested explicitly, it is usually pretty useless. Attach the full console output instead. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #10 from anonsquest(a)protonmail.com --- (In reply to joaopa from comment #9)
Unless backtrace is requested explicitly, it is usually pretty useless. Attach the full console output instead.
could you tell me where this is located? thanks(In reply to joaopa from comment #9)
Unless backtrace is requested explicitly, it is usually pretty useless. Attach the full console output instead.
Can you tell me where this log is located? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 --- Comment #11 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51876 Martin <martinaugustine91(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martinaugustine91(a)gmail.com --- Comment #12 from Martin <martinaugustine91(a)gmail.com> --- Created attachment 73011 --> https://bugs.winehq.org/attachment.cgi?id=73011 Same issue I am attaching the log as requested in the previous post. Thanks -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla