[Bug 58604] New: Unable to handle Ctrl+C signal correctly，02c0:fixme:console:default_ctrl_handler Terminating process e0 on event 0
http://bugs.winehq.org/show_bug.cgi?id=58604 Bug ID: 58604 Summary: Unable to handle Ctrl+C signal correctly，02c0:fixme:console:default_ctrl_handler Terminating process e0 on event 0 Product: Wine Version: 10.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 1514704742(a)qq.com Distribution: --- Unable to handle Ctrl+C signal correctly -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Component|-unknown |cmd Status|UNCONFIRMED |NEEDINFO Severity|major |normal Keywords| |download, source --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- How is this causing an issue for you? You have provided NO details. Please provide the required information. https://gitlab.winehq.org/wine/wine/-/wikis/Bugs -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 --- Comment #2 from 邹卓林 <1514704742(a)qq.com> --- Hello, thank you very much for your reply I am using Wine to run SCUM server, and the command is as follows: wine64 SCUM/Binaries/Win64/SCUMServer.exe Due to the special nature of this game server, it needs to send a ^ C signal in order to properly save server data, But in versions after Wine9. x, the ^ C signal cannot be processed properly. In my terminal, I used the keyboard to type Ctrl+C, which directly ended the entire game process. I also tried to use kill -2 to end my game process, but without waiting, I ended the entire process group directly Here are some related logs, I don't know if they can visually reflect the problem Warning: [Unknown Source] Adding element (bIsValid=true, Min=(X=-5545295872.000 Y=-97701404672.000), Max =(X=-5545294848.000 Y=-97701404672.000)) that is outside the bounds of the quadtree root (bIsValid=true, Min") 00fc:fixme:advapi:ReportEventW (00000000CAFE4242,0x0002,0x0000,0x80000002,0000000000000000,0x0001,0x00000000,00007FFFFEC7CAC8,0000000000000000): stub 000000f8:000000fc: output debug string ("[2025.08.16-21.04.54:863][ 24]LogQuadTree: Warning: [Unknown Source] Adding element (bIsValid=true, Min=(X=60785811456.000 Y=77255458816.000), Max= (X=60785811456.000 Y=77255458816.000)) that is outside the bounds of the quadtree root (bIsValid=true, Min=(") 00fc:fixme:advapi:ReportEventW (00000000CAFE4242,0x0002,0x0000,0x80000002,0000000000000000,0x0001,0x00000000,00007FFFFEC7CAC8,0000000000000000): stub 000000f8:000000fc: output debug string ("[2025.08.16-21.05.00:032][ 50]LogSCUM: Global Stats: 199.2ms ( 5.0FPS), 199.7ms ( 5.0FPS), 200.2ms ( 5.0FPS) | C: 0 ( 0), P: 0 ( 0), Z: 0 ( 0), R: 0 ( 0), S: 0 ( 0), A: 0 ( 0), V: 0 | IV: 3715 ( 0) | NO: 734 ( 734)\r\n") ^C 02c0:fixme:console:default_ctrl_handler Terminating process e0 on event 0 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 --- Comment #3 from 邹卓林 <1514704742(a)qq.com> --- If you need more detailed information, please reply to me. Thank you very much -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- Can you try running it from 'wine cmd'? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 --- Comment #5 from 邹卓林 <1514704742(a)qq.com> --- I haven't tried it before, this may be a solution -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|download, source | Summary|Unable to handle Ctrl+C |SCUM server cannot process |signal |CTRL+C |correctly，02c0:fixme:consol | |e:default_ctrl_handler | |Terminating process e0 on | |event 0 | -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 --- Comment #6 from 邹卓林 <1514704742(a)qq.com> --- Hello, I tried running my SCUMServer server using the wine cmd method, but unfortunately it's not much different from running normal wine. I directly sent the running log of ^ C or kill -2 wine on the terminal, but it still prompted me: 0290:fixme:console:default_ctrl_handler Terminating process 130 on event 0 Z:\home\engine> Here are my process details: ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 23:36 ? 00:00:00 sh -c java $JAVA_OPTS -jar agent-main.jar config.yaml root 7 1 1 23:36 ? 00:00:13 java -Xms128m -Xmx256m -Djdk.lang.Process.launchMechanism=vfork -jar agent-main.jar config.yaml root 271 7 0 23:39 ? 00:00:00 /bin/bash root 272 271 0 23:39 ? 00:00:00 su - engine engine 276 272 0 23:39 ? 00:00:00 -bash root 287 0 0 23:40 pts/0 00:00:00 bash root 296 287 0 23:40 pts/0 00:00:00 su - engine engine 297 296 0 23:40 pts/0 00:00:00 -bash engine 308 297 0 23:40 pts/0 00:00:00 start.exe /exec root 498 0 0 23:42 pts/1 00:00:00 bash root 518 498 0 23:42 pts/1 00:00:00 tail -f scum/SCUM/Saved/Logs/SCUM.log root 519 0 0 23:43 pts/2 00:00:00 bash root 597 519 0 23:45 pts/2 00:00:00 su - engine engine 598 597 0 23:45 pts/2 00:00:00 -bash engine 620 598 0 23:47 pts/2 00:00:00 start.exe /exec cmd /home/engine/scum/SCUM/Binaries/Win64/SCUMServer.exe engine 622 1 12 23:47 ? 00:00:07 /opt/wine-stable/bin/wineserver engine 628 1 0 23:47 ? 00:00:00 C:\windows\system32\services.exe engine 631 1 0 23:47 ? 00:00:00 C:\windows\system32\winedevice.exe engine 633 1 0 23:47 ? 00:00:00 C:\windows\system32\explorer.exe /desktop engine 642 1 0 23:47 ? 00:00:00 C:\windows\system32\plugplay.exe engine 653 1 0 23:47 ? 00:00:00 C:\windows\system32\svchost.exe -k LocalServiceNetworkRestricted engine 660 1 1 23:47 ? 00:00:01 C:\windows\system32\winedevice.exe engine 678 1 0 23:47 ? 00:00:00 C:\windows\system32\rpcss.exe engine 687 1 0 23:47 ? 00:00:00 C:\windows\system32\conhost.exe --unix --width 188 --height 31 --server 0x10 engine 689 1 0 23:47 pts/2 00:00:00 C:\windows\system32\cmd.exe /home/engine/scum/SCUM/Binaries/Win64/SCUMServer.exe -Port=24952 root 780 0 0 23:48 pts/3 00:00:00 bash root 808 780 0 23:48 pts/3 00:00:00 ps -ef -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 Eric Pouech <eric.pouech(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech(a)gmail.com --- Comment #7 from Eric Pouech <eric.pouech(a)gmail.com> --- if you get the message: 02c0:fixme:console:default_ctrl_handler Terminating process e0 on event 0 it means that a process has received the ctrl-c signal; but this process (assuming it's the SCUM server one) didn't trigger any callback fro ctrl-c handling also in #6, how come the SCUM server process isn't running (is that after you hit ctrl-c?) a WINEDEBUG=+console,+process trace could help understanding what happens -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 --- Comment #8 from 邹卓林 <1514704742(a)qq.com> --- Yes, SCUMServer stopped directly after pressing ctrlc in # 6 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58604 --- Comment #9 from 邹卓林 <1514704742(a)qq.com> --- Oh, I need to add that in Wine8.0 version, using the same running instructions can correctly handle ctrlc signals, but it doesn't work in versions 9.0 and later. I hope it's helpful for this issue -- 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