https://bugs.winehq.org/show_bug.cgi?id=52255
Bug ID: 52255 Summary: Playing Constantine. It flies out. code 1280 Product: Wine Version: 7.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: jon9097@gmail.com Distribution: ---
Playing Constantine. It flies out.
When I start the game opens a black screen and the game crashes.
The terminal says: Initial process has exited (return code: 1280) Exit with return code 1280
The game is Constantine.
https://bugs.winehq.org/show_bug.cgi?id=52255
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Summary|Playing Constantine. It |Constantine crashes on |flies out. code 1280 |start
--- Comment #1 from Gijs Vermeulen gijsvrm@gmail.com --- Please attach the full terminal output + backtrace, see: https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal_output.29.3F
https://bugs.winehq.org/show_bug.cgi?id=52255
--- Comment #2 from Konstantin jon9097@gmail.com --- Created attachment 71410 --> https://bugs.winehq.org/attachment.cgi?id=71410 Constantine_log
https://bugs.winehq.org/show_bug.cgi?id=52255
--- Comment #3 from Konstantin jon9097@gmail.com --- (In reply to Gijs Vermeulen from comment #1)
Please attach the full terminal output + backtrace, see: https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a. _terminal_output.29.3F
I did what you said.
https://bugs.winehq.org/show_bug.cgi?id=52255
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #4 from joaopa jeremielapuree@yahoo.fr --- And more important: does the bug occur with plain wine instead of staging?
https://bugs.winehq.org/show_bug.cgi?id=52255
--- Comment #5 from joaopa jeremielapuree@yahoo.fr --- And is there a freely legally download demo of this game showing the problem.
https://bugs.winehq.org/show_bug.cgi?id=52255
--- Comment #6 from Konstantin jon9097@gmail.com --- (In reply to joaopa from comment #4)
And more important: does the bug occur with plain wine instead of staging?
Yes
https://bugs.winehq.org/show_bug.cgi?id=52255
--- Comment #7 from Konstantin jon9097@gmail.com --- (In reply to joaopa from comment #5)
And is there a freely legally download demo of this game showing the problem.
No. There are repacks, you can find them on the Internet. For example from R.G. Mechanics.
https://bugs.winehq.org/show_bug.cgi?id=52255
--- Comment #8 from joaopa jeremielapuree@yahoo.fr --- Too funny. You wrote textually "WINEDEBUG=+relay,+seh,+tid wine your_program.exe >> /tmp/output.txt 2>&1"
your_program.exe meant the name of the executable you want to run. You must change that. And for the first log, except if the developers request it explicitly, you don't need to set the winedebug channels.
So in a terminal cd (the folder where is located your executable) wine "the_name_of_the_exectable.exe" &> log.txt
don't write the quotes !!!
And then attach the file log.txt here. Important, do that with plain wine, not staging. And try to update to wine-7.0-rc2, better to wine-7.0-rc3. Maybe the bug is already fixed.
Thank you in advance.
https://bugs.winehq.org/show_bug.cgi?id=52255
--- Comment #9 from Konstantin jon9097@gmail.com --- (In reply to Konstantin from comment #6)
(In reply to joaopa from comment #4)
And more important: does the bug occur with plain wine instead of staging?
Yes
(In reply to joaopa from comment #8)
Too funny. You wrote textually "WINEDEBUG=+relay,+seh,+tid wine your_program.exe >> /tmp/output.txt 2>&1"
your_program.exe meant the name of the executable you want to run. You must change that. And for the first log, except if the developers request it explicitly, you don't need to set the winedebug channels.
So in a terminal cd (the folder where is located your executable) wine "the_name_of_the_exectable.exe" &> log.txt
don't write the quotes !!!
And then attach the file log.txt here. Important, do that with plain wine, not staging. And try to update to wine-7.0-rc2, better to wine-7.0-rc3. Maybe the bug is already fixed.
Thank you in advance.
I did everything as I was told. "full terminal output + backtrace" "Please attach the full terminal output + backtrace, see:
<https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a."
https://bugs.winehq.org/show_bug.cgi?id=52255
--- Comment #10 from Konstantin jon9097@gmail.com --- (In reply to joaopa from comment #8)
Too funny. You wrote textually "WINEDEBUG=+relay,+seh,+tid wine your_program.exe >> /tmp/output.txt 2>&1"
your_program.exe meant the name of the executable you want to run. You must change that. And for the first log, except if the developers request it explicitly, you don't need to set the winedebug channels.
So in a terminal cd (the folder where is located your executable) wine "the_name_of_the_exectable.exe" &> log.txt
don't write the quotes !!!
And then attach the file log.txt here. Important, do that with plain wine, not staging. And try to update to wine-7.0-rc2, better to wine-7.0-rc3. Maybe the bug is already fixed.
Thank you in advance.
I didn't change anything in the file, I entered a command and sent what it gave me. "WINEDEBUG=+relay,+seh,+tid wine your_program.exe >> /tmp/output.txt 2>&1 "