[Bug 41245] New: Gameranger : crashes when trying to join a room
https://bugs.winehq.org/show_bug.cgi?id=41245 Bug ID: 41245 Summary: Gameranger : crashes when trying to join a room Product: Wine Version: 1.9.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fevrier.simon(a)gmail.com Distribution: --- Created attachment 55541 --> https://bugs.winehq.org/attachment.cgi?id=55541 A log from playonlinux debbuger Wine crashes when I try to join a Star Wars Battlefront II room in Gameranger. OS : Ubuntu/Kubuntu 16.04 amd64 Wine : 1.9.17 Programs : Gameranger (https://www.gameranger.com/download/) and Star Wars Battlefront II To have more information, I launched the programs through playonlinux. I have a "log" from the playonlinux debugger. If it can help, it is attached. When ubuntu whith unity is using, a black rectangle appears at the centre of the screen -- 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=41245 --- Comment #1 from Bruno Jesus <00cpxxx(a)gmail.com> --- Hi, your log does not contain a crash, only some standard output lines. Please use the plain version of Wine and try again, read https://wiki.winehq.org/FAQ#get_log and attach the crash. -- 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=41245 ImperatorS79 <fevrier.simon(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Gameranger : crashes when |Gameranger : |trying to join a room |crashes/freezes when trying | |to join a room -- 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=41245 --- Comment #2 from ImperatorS79 <fevrier.simon(a)gmail.com> --- (In reply to Bruno Jesus from comment #1)
Hi, your log does not contain a crash, only some standard output lines. Please use the plain version of Wine and try again, read https://wiki.winehq.org/FAQ#get_log and attach the crash.
The playonlinux debugger output exactly the wine logs. A precision for the bugs : first the program freezes, and when you try to close the windows, a window appear and and said that wine doesn't respond. That's is a crash for me. I hope we hadn't a misunderstood. -- 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=41245 --- Comment #3 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to ImperatorS79 from comment #2)
The playonlinux debugger output exactly the wine logs.
A precision for the bugs : first the program freezes, and when you try to close the windows, a window appear and and said that wine doesn't respond. That's is a crash for me. I hope we hadn't a misunderstood.
Ok, that is just a freeze then. That is why there is no crash in the log, a crash usually display a Wine error window that once dismissed will throw a lot of information in the console. Do you need the game to reproduce the issue or just by installing GameRanger and following some instructions the bug is triggable? -- 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=41245 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish(a)gmail.com --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- Does this help? https://wiki.winehq.org/FAQ#Failed_to_use_ICMP_.28network_ping.29.2C_this_re... -- 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=41245 --- Comment #5 from ImperatorS79 <fevrier.simon(a)gmail.com> --- (In reply to Austin English from comment #4)
Does this help?
https://wiki.winehq.org/FAQ#Failed_to_use_ICMP_.28network_ping.29. 2C_this_requires_special_permissions
With this trick, GameRanger does not start anymore. -- 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=41245 --- Comment #6 from ImperatorS79 <fevrier.simon(a)gmail.com> --- (In reply to Bruno Jesus from comment #3)
(In reply to ImperatorS79 from comment #2)
The playonlinux debugger output exactly the wine logs.
A precision for the bugs : first the program freezes, and when you try to close the windows, a window appear and and said that wine doesn't respond. That's is a crash for me. I hope we hadn't a misunderstood.
Ok, that is just a freeze then. That is why there is no crash in the log, a crash usually display a Wine error window that once dismissed will throw a lot of information in the console.
Do you need the game to reproduce the issue or just by installing GameRanger and following some instructions the bug is triggable?
With my other games I don't have any problem. I can launch and join rooms. Only Star Wars Battelfront II is a 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=41245 ImperatorS79 <fevrier.simon(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|1.9.17 |1.9.22 --- Comment #7 from ImperatorS79 <fevrier.simon(a)gmail.com> --- Still present in wine 1.9.22. (I won't update this thread for each version, don't worry). -- 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=41245 --- Comment #8 from ImperatorS79 <fevrier.simon(a)gmail.com> --- Created attachment 55993 --> https://bugs.winehq.org/attachment.cgi?id=55993 A new log for Gameranger with wine 1.9.22 -- 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=41245 fjfrackiewicz(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz(a)gmail.com --- Comment #9 from fjfrackiewicz(a)gmail.com --- (In reply to ImperatorS79 from comment #8)
Created attachment 55993 [details] A new log for Gameranger with wine 1.9.22
Do you have the backtrace of the crash? wine: Unhandled stack overflow at address 0x1002bbc7 (thread 00a4), starting debugger... -- 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=41245 --- Comment #10 from ImperatorS79 <fevrier.simon(a)gmail.com> --- The only thing i arrived to have is -- 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=41245 --- Comment #11 from ImperatorS79 <fevrier.simon(a)gmail.com> --- The only things I manage to have are : 0xf7723c97 __kernel_vsyscall+0x7 in [vdso].so: int $0x80 0x10040e21: pushl $0x1 -- 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=41245 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #12 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-5.21? -- 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 (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla