wine-bugs October 2016

wine-bugs@winehq.org

1 participants
7770 discussions

[Bug 20617] New: Multithreaded crashing programs create misleading backtraces when winedbg --auto is called
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=20617 Summary: Multithreaded crashing programs create misleading backtraces when winedbg --auto is called Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg AssignedTo: wine-bugs(a)winehq.org ReportedBy: bugzilla.winehq.org(a)urbanec.net Created an attachment (id=24590) --> (http://bugs.winehq.org/attachment.cgi?id=24590) MultipleThreads test case executable - requires Zoo.dll When a multithreaded program crashes and winedbg --auto is called to generate a back trace, the result is not always a back trace for the thread that caused the crash in the first place. The attached files can be used to reproduce this problem. The program MultipleThreads.exe takes no arguments and creates three new threads, each with a data structure that contains a timeout variable set to 200ms and the thread start function is set to a function in Zoo.dll. The main thread also calls the same function in Zoo.dll with the timeout variable set to 240ms. The function in Zoo.dll prints the value of the timeout, then sleeps for the duration of the timeout. After this, the function prints that it will crash, then causes an exception by a write to 0x00000000. When I run this program, the output is non-deterministic, but more often than not, the reported crashing thread does not match the thread which is shown in the backtrace. The discrepancy can be seen from this output: Thread 0x0019 *** C R A S H I N G *** wine: Unhandled page fault on write access to 0x00000000 at address 0x10001123 (thread 0019), starting debugger... Thread 0x001a *** C R A S H I N G *** Thread 0x001b *** C R A S H I N G *** Thread 0x0009 *** C R A S H I N G *** Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x10001123). ... [Register, and stack dumps, backtrace, module list] ... Threads: process tid prio (all id:s are in hex) 00000008 (D) Z:\tmp\WineCrashTest\MultipleThreads.exe 0000001b -2 0000001a -2 <== 00000019 -2 00000009 -2 Notice how the first thread to report crash intent was 0x0019, which matches the the page fault reported by except.c:start_debugger(). However, the thread list generated by winedbg shows the current thread to be 0x001a. Also notice that even though the crashing process invoked the debugger on exception in thread 0x0019, the other three threads in the crashing process continued to run and generated further page faults before the debugger started. I would expect that when a crash occurs, all threads in the process would be suspended immediately and the debugger would be able to determine the thread that caused the exception. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 10

[Bug 20584] New: Lemmings Revolution - Crash on exit.
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=20584 Summary: Lemmings Revolution - Crash on exit. Product: Wine Version: 1.1.32 Platform: PC-x86-64 URL: http://downloads.gamezone.com/demosfiles/t1178.htm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ezekiel000(a)lavabit.com Created an attachment (id=24561) --> (http://bugs.winehq.org/attachment.cgi?id=24561) Terminal output When exiting the game wine crashes and then crashes the dialogue saying that wine has crashed. Running Ubuntu 9.10 amd64 wine 1.1.32 with nVidia Geforce 8200 with 185.18.36 official drivers. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 13

[Bug 23781] New: Parsing of money amount in "BNC Express" ignores decimal separator
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=23781 Summary: Parsing of money amount in "BNC Express" ignores decimal separator Product: Wine Version: unspecified Platform: x86-64 OS/Version: Mac OS X 10.6 Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pierre.guerrier(a)m4x.org CC: pierre.guerrier(a)m4x.org Created an attachment (id=29819) --> (http://bugs.winehq.org/attachment.cgi?id=29819) Screenshot of buggy input field I have been trying to run the "BNC Express" program in CrossOver Pro for Mac (commercial product based on wine by CodeWeavers, and per the CrossOver support opinion, the bug below belongs to wine. What follows is an updated repost of the ticket in the CodeWeaver DB: http://www.codeweavers.fr/support/tickets/browse/?ticket_id=809692 ) Quick context: BNC Express is an accounting program for the self-employed, generating income reports validated by the french IRS, quite popular I think in France. It looks like a VB program, publisher website here http://www.trefle-rouge.com/ - all in french I'm afraid. The GUI is generally OK, but there is a nasty bug whenever inputting a monies amount in the program (which of course, happens quite a lot). You are supposed to type in, say "45,34" (for 45 euros and 34 cents). The part after the separator is optional. In any case, the software will the normalize the input and turn it into "45,00" e.g. if you just entered "45". The bug is that it misses out the separator in Wine/CrossOver. So "45,34" turns into "4534,00". I have not found anything similar in the ticket database (neither codeweaver or winehq) or on web. I did try to change the sDecimal and sMonDecimal values in the Registry (seen another ticket for a VB app that was solved this way). This DOES change the separator used when re-displaying the normalized amount (display is set by sDecimal). But it does not change the buggy behavior of ignoring the separator when parsing the input (it is not possible to input anything other than numbers and , and . in monies field, the program filters it and turns "." into "," immediately upon typing - this is an expected behavior, same as windows). (this is not a locale problem, the windows environment did inherit the french locale of the Mac system all right) When looking further, I found some vaguely reminiscent stuff on winehq, for instance: http://bugs.winehq.org/show_bug.cgi?id=10765 (except the bug seems to be on parsing, not on output format) There is a freely downloadable demo version on the TrefleRouge website above (or I can e-mail it you if you can't find your way in the french website). Launching the demo, loading the sample balance sheet takes you to the main screen which is simply bill/receipts input, and the bug shows up immediately. I have attached a screenshot of this screen with the problem highlighted. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 14

[Bug 34126] New: RaidCall 7.2.6: high (100%) CPU usage (on login)
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=34126 Bug #: 34126 Summary: RaidCall 7.2.6: high (100%) CPU usage (on login) Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gonhidi(a)gmail.com Classification: Unclassified Created attachment 45385 --> http://bugs.winehq.org/attachment.cgi?id=45385 MacPorts Wine 1.6 Raidcall 7.2.6 log: launch and login Wine 1.6 causes RaidCall's 7.2.6 CPU usage to spike after a successful login. The offending process remains active after exiting the application preventing the wineserver and the other wine processes from closing. I have observed this behaviour when running MacPort's 1.6 wine port, on OS X 10.8.4. It is not present on the previous version of the build, 1.4.1_4. Running winedbg and calling info processes before and after RaidCall login shows a new process likely to be the CPU hog, 'Wizard.exe' (part of the RaidCall installation). Wine-dbg>info process pid threads executable (all id:s are in hex) 00000025 9 'raidcall.exe' 00000041 12 \_ 'Wizard.exe' 00000022 2 'explorer.exe' 0000000e 5 'services.exe' 0000001a 3 \_ 'plugplay.exe' 00000012 4 \_ 'winedevice.exe' The way I run RaidCall is by executing "wine start 'C:\Program Files\RaidCall\raidcall.exe'" (after having installed the program using "wine raidcall.exe"). The result of a "wine start 'C:\Program Files\RaidCall\raidcall.exe' &> log-run.txt" is attached. Killing the offending process doesn't seem to break RaidCall, at least superficially. I have not tested deeper to see if it is a valid workaround. I have tried using git bisect to trace the behaviour to a commit. I followed the instructions from “MacOSX/Building” section “Build Wine git version, the MacPorts way” (<http://wiki.winehq.org/MacOSX/Building#head-ca82f43f942cbed405199780ca73d07…>), but running wine from within the build directory (i.e. skipping the make install step): make clean ./configure CPPFLAGS='-I/usr/X11/include -I/opt/local/include' LIBS='-lGL -lGLU' LDFLAGS='-L/usr/X11/lib -L/opt/local/lib' make DYLD_FALLBACK_LIBRARY_PATH="/usr/X11/lib:/usr/lib:/opt/local/lib" ./wine raidcall.exe DYLD_FALLBACK_LIBRARY_PATH="/usr/X11/lib:/usr/lib:/opt/local/lib" ./wine start 'C:\Program Files\RaidCall\raidcall.exe' Doing nothing but that I soon started having build problems (likely reason being that of the “Compiling Wine on Mac OS X 10.8.2?” February 2013 wine-devel mailing list thread) so I set CC to MacPort's clang 3.3 (@3.3_0+analyzer+python27). From then on, things went smoothly and led to the following git commit: [2f48b12c575c4e1afc6115a39d60722acda73d7d] gdi32: Use the Mac driver by default Note that using the aforementioned build process the 100% CPU usage also appears when launching the RaidCall installer, so perhaps the issue is not the same or something else is showing up. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 9

[Bug 22689] New: Bonzai3D - dialogue boxes inactive when opened
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=22689 Summary: Bonzai3D - dialogue boxes inactive when opened Product: Wine Version: 1.1.44 Platform: x86-64 URL: http://formz.com/products/bonzai3d/bonzai3dDownloadTri al.html OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nick(a)lasventajas.com In Bonzai3D dialogue boxes are inactive until the window bar of the box is clicked. For example, right clicking on an object in the project window and selecting, 'Attributes', invokes a dialogue box with a number of options relative to the object. All options are inactive until the window bar of the dialogue box is clicked at which point the box becomes live. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 9

[Bug 24979] New: halfworking tab key
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=24979 Summary: halfworking tab key Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: emoxam(a)gmail.com "tab" key works only "to tree". not "from tree" of a connections list! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 12

[Bug 30901] New: [PunkBuster && 64Bits Prefix]Assassin's Creed Multiplayer does not works
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=30901 Bug #: 30901 Summary: [PunkBuster && 64Bits Prefix]Assassin's Creed Multiplayer does not works Product: Wine Version: 1.5.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: berillions(a)gmail.com Classification: Unclassified Since i create the hack to pass the Ubisoft Game Launcher properly, it's possible to play at the recent Ubisoft's games like AC : Revelations without a crack. Actually, i try to play at this game in 2 prefix (the first is a 32Bits prefix and the second is a 64Bits prefix) 32Bits Prefix : There are no problems, the game works correctly in Soloplayer mode and Multiplayer. For this second point, it's great because the Multiplayer use Punkbuster. 64Bits Prefix : It's in this prefix that i have the problem. The Soloplayer mode works perfectly but impossible to join a session in the Multiplayer Mode. I'm always kicked by Punkbuster. PnkBstrA and PnkBstrB services are the problems : 1- When i launch game in the 32Bits Prefix, these services are launched automatically without problem. They appear in my process list so the multiplayer works fine. 2- But, when i launch the game in my 64Bits prefix, these services are not launched so it's impossible to launch a multiplayer session. When i launch "winecfg" in the 64Bits prefix, i have this fixme in my console : Code: fixme:service:scmdatabase_autostart_services Auto-start service L"PnkBstrA" failed to start: 2 I haven't this message in my 32Bits prefix because PnkBstrA.exe/PnkBstrB.exe services are launched Thanks -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 18

[Bug 36065] New: PunkBuster service tests fail (DeleteService should mark active services in SCM database as pending for deletion)
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=36065 Bug ID: 36065 Summary: PunkBuster service tests fail (DeleteService should mark active services in SCM database as pending for deletion) Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, although not really a problem because of the state of PunkBuster (bug 9685) it still highlights a Wine bug. PunkBuster service components test tool: http://www.evenbalance.com/index.php?page=pbsvcfaq.php --- snip --- ... Checking PnkBstrK driver status NOT FOUND Extracting new PnkBstrK to: "C:\users\focht\Application Data\PnkBstrK.sys" OK Sending load packet to PnkBstrB SENT Checking PnkBstrK driver status NOT FOUND Manually stopping PnkBstrB FAILED - no handle --- snip --- Relevant part of trace log: --- snip --- $ WINEDEBUG=+tid,+seh,+loaddll,+service,+relay wine ./pbsvc.exe >>log.txt 2>&1 ... 0044:Call advapi32.CreateServiceA(00135c48,0041e168 "PnkBstrK",0041e168 "PnkBstrK",000f01ff,00000001,00000003,00000001,0041b000 "C:\\windows\\system32\\drivers\\PnkBstrK.sys",00000000,00000000,00000000,00000000,00000000) ret=004078e5 0044:trace:service:CreateServiceA 0x135c48 "PnkBstrK" "PnkBstrK" 0044:trace:service:CreateServiceW 0x135c48 L"PnkBstrK" L"PnkBstrK" ... 0016:trace:service:svcctl_CreateServiceW (L"PnkBstrK", L"PnkBstrK", 0xf01ff, L"C:\\windows\\system32\\drivers\\PnkBstrK.sys") ... 0016:Call advapi32.RegCreateKeyW(00000024,00119aa0 L"PnkBstrK",0084e4a8) ret=7edeb767 0016:Ret advapi32.RegCreateKeyW() retval=00000000 ret=7edeb767 0016:Call advapi32.RegSetValueExW(00000130,7edf93c4 L"DisplayName",00000000,00000001,0011a890,00000012) ret=7edeb689 0016:Ret advapi32.RegSetValueExW() retval=00000000 ret=7edeb689 ... 0016:trace:service:scmdatabase_add_service 0x11a950 ... 0044:Ret advapi32.CreateServiceA() retval=001f6108 ret=004078e5 0044:Call advapi32.CloseServiceHandle(001f6108) ret=004078f8 0044:trace:service:CloseServiceHandle 0x1f6108 ... 0044:Ret advapi32.OpenServiceA() retval=001f55c8 ret=00407901 0044:Call advapi32.StartServiceA(001f55c8,00000000,00000000) ret=0040793b 0044:trace:service:StartServiceA (0x1f55c8,0,(nil)) 0044:trace:service:StartServiceW 0x1f55c8 0 (nil) ... 0042:trace:service:svcctl_StartServiceW (0x118d38, 0, (nil)) ... 0042:Call KERNEL32.CreateProcessW(00000000,001191a0 L"C:\\windows\\system32\\winedevice.exe PnkBstrK",00000000,00000000,00000000,00000400,00540000,00000000,00c4e4c8,00c4e50c) ret=7edece8f ... 000d:Call KERNEL32.__wine_kernel_init() ret=7bc5a402 ... 0042:Ret KERNEL32.CreateProcessW() retval=00000001 ret=7edece8f ... 0042:trace:service:service_send_start_message L"PnkBstrK" (nil) 0 ... 000d:trace:service:service_run_main_thread Starting 1 services running as process 71 ... 0025:trace:service:service_control_dispatcher got request 1 for service L"PnkBstrK" 0025:trace:service:SERV_OpenServiceW 0x119790 L"PnkBstrK" 32768 ... 0025:trace:service:SERV_OpenServiceW returning 0x11ac48 0025:trace:service:service_handle_start L"PnkBstrK" argsize 10 ... 0034:Call advapi32.RegisterServiceCtrlHandlerExW(00115292 L"PnkBstrK",7edfc61f,00000000) ret=7edfc86c 0034:trace:service:RegisterServiceCtrlHandlerExW L"PnkBstrK" 0x7edfc61f (nil) 0034:Ret advapi32.RegisterServiceCtrlHandlerExW() retval=0011a918 ret=7edfc86c 0034:Call advapi32.SetServiceStatus(0011a918,0053e97c) ret=7edfc8c9 0042:trace:service:service_wait_for_startup 0x11a950 0034:trace:service:SetServiceStatus 0x11a918 30 2 0 0 0 0 2710 ... 0016:trace:service:svcctl_SetServiceStatus (0x11aed8, 0x11adc4) ... 0044:Ret advapi32.StartServiceA() retval=00000001 ret=0040793b ... 0034:Call driver init 0x100033c0 (obj=0x7edff4c0,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\PnkBstrK") ... 0034:Call advapi32.SetServiceStatus(0011a918,0053e97c) ret=7edfc8f8 0034:trace:service:SetServiceStatus 0x11a918 30 4 5 0 0 0 2710 ... 0044:Call advapi32.DeleteService(00137f70) ret=00407549 0044:trace:service:DeleteService (0x137f70) ... 0016:trace:service:scmdatabase_remove_service 0x11a950 0016:Call advapi32.RegDeleteTreeW(00000024,00119aa0 L"PnkBstrK") ret=7edebbce 0016:Ret advapi32.RegDeleteTreeW() retval=00000000 ret=7edebbce ... 0044:Ret advapi32.DeleteService() retval=00000001 ret=00407549 ... 0043:Call advapi32.OpenServiceA(00137f20,0041e168 "PnkBstrK",000f01ff) ret=00407510 0043:trace:service:OpenServiceA 0x137f20 "PnkBstrK" 983551 0043:trace:service:SERV_OpenServiceW 0x137f20 L"PnkBstrK" 983551 ... 0016:trace:service:svcctl_OpenServiceW (L"PnkBstrK", 0xf01ff) ... 0043:trace:service:SERV_OpenServiceW returning (nil) ... 0043:Ret advapi32.OpenServiceA() retval=00000000 ret=00407510 ... --- snip --- The tool extracts, installs and starts the kernel service. Meanwhile, the tool issues a request to mark the service for deletion - kind of "auto-cleanup". After that it starts polling of the service status to check if the service is actually running (it is). The problem: Wine doesn't implement the deferred deletion of active services and removes the service entry while the service is alive (state 'running'). All subsequent service lookup/status requests fail because the entry is now missing from database. MSDN: http://msdn.microsoft.com/en-us/library/windows/desktop/ms682562%28v=vs.85%… --- quote --- DeleteService function Marks the specified service for deletion from the service control manager database. ... The DeleteService function marks a service for deletion from the service control manager database. The database entry is not removed until all open handles to the service have been closed by calls to the CloseServiceHandle function, and the service is not running. A running service is stopped by a call to the ControlService function with the SERVICE_CONTROL_STOP control code. If the service cannot be stopped, the database entry is removed when the system is restarted. --- quote --- While you're at it ... please add a TRACE to DeleteService(): http://source.winehq.org/git/wine.git/blob/929d9fb9f79b9ba0b7392215e51a152e… I used the 'service' debug channel first and lost some time because I didn't see the the service deletion part (it's only visible if one uses the heavy relay gun). This would be consistent with other TRACE messages for service API. Regards -- 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.

2 7

[Bug 26998] New: Football manager just start process sometimes
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=26998 Summary: Football manager just start process sometimes Product: Wine Version: 1.3.19 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jakob(a)knugen.nu Sometimes when i start the game trough steam only a process named fm.exe and i need to kill it and restart the game a couple of time to get it to start. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 15

[Bug 23995] New: FM2010 Fails to start every time.
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=23995 Summary: FM2010 Fails to start every time. Product: Wine Version: 1.3.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: admin(a)pokemonger.com FM2010 (Demo Download - http://www.gamershell.com/download_52136.shtml ) Fails to start every time, it stalls, I have progressed all the way back to 1.1.31 (didnt run at all on 1.0) to try and do a regression test, but I cant find a version of wine that the game starts each and every time on. It does start in the end, but it can take multiple attempts. This has been tested on Debian and Ubuntu, I have tried as I said regression testing but I just dont know where to start with the fact I cant find a version of wine that does not have this issue. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 15

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs October 2016