wine-bugs June 2021

wine-bugs@winehq.org

1 participants
5243 discussions

[Bug 33422] New: reporting 'EditWndProc_common undocumented message 0xbf' on behalf of the message
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=33422 Bug #: 33422 Summary: reporting 'EditWndProc_common undocumented message 0xbf' on behalf of the message Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: heinrich5991(a)gmx.de Classification: Unclassified fixme:edit:EditWndProc_common undocumented message 0xbf, please report That's how you can reproduce it: 1. Download Kaiser 1.22a (http://www.yadam.de/KAISER/kaiser.htm). 2. Start it. 3. When prompted for the names of the players, focus the edit field and click somewhere else in the window where no other input are. -- 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 7

[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 49800] New: World of Warcraft appears on the wrong monitor when running full screen
by WineHQ Bugzilla 10 Jan '22

10 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=49800 Bug ID: 49800 Summary: World of Warcraft appears on the wrong monitor when running full screen Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: brgerst(a)gmail.com Distribution: --- Prior to 5.16, World of Warcraft appeared full screen on the primary (right) monitor of a dual monitor setup. On 5.16, it appears on the left monitor and can't be moved back to the right unless set to windowed mode. Reverting commit c5ec1585f6e5211a2b63e3435748210552250534 ("winex11.drv: Always update _NET_WM_STATE in update_net_wm_states().") fixes the problem. The desktop environment is MATE on Fedora 32. Trace output without the patch reverted: 0024:trace:x11drv:update_net_wm_states setting wm state 0 for window 0x1006a/4000005 to 1 prev 1 0024:trace:x11drv:update_net_wm_states setting wm state 1 for window 0x1006a/4000005 to 0 prev 0 0024:trace:x11drv:update_net_wm_states setting wm state 2 for window 0x1006a/4000005 to 0 prev 0 0024:trace:x11drv:update_net_wm_states setting wm state 3 for window 0x1006a/4000005 to 0 prev 0 0024:trace:x11drv:update_net_wm_states setting wm state 4 for window 0x1006a/4000005 to 0 prev 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.

1 16

[Bug 46075] New: Delta Rune: Wine crashes after going past the first Forest room
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=46075 Bug ID: 46075 Summary: Delta Rune: Wine crashes after going past the first Forest room Product: Wine Version: 3.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ryu.ketsueki(a)outlook.com Distribution: --- Created attachment 62687 --> https://bugs.winehq.org/attachment.cgi?id=62687 Crash backtrace This recently released game called Delta Rune, commonly known as well as SURVEY PROGRAM, because this is how it was publicly released. The game works just fine until this specific area of the game called Forest. Past the save point, wine crashes and forces the game to close. Backtrace is attached. -- 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 6

[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 46176] New: Altium Designer 13.2.5 (10.1810.28368) hangs on startup
by wine-bugs＠winehq.org 10 Jan '22

10 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=46176 Bug ID: 46176 Summary: Altium Designer 13.2.5 (10.1810.28368) hangs on startup Product: Wine Version: 3.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lvd.mhm(a)gmail.com Distribution: --- Created attachment 62837 --> https://bugs.winehq.org/attachment.cgi?id=62837 Short (default) log output After the software starts, it shows splashscreen with some activity indicated inside it. After that activity ceases and splashscreen disappears, the main window does not appear and the software seems to hang (no CPU usage). I've compiled wine 3.20 (git rev-parse HEAD : 488432317206bc816432af0dd740e18979e37e58) within pure 32-bit install of ubuntu 14.04 server edition on KVM virtual machine. I've used "./configure --disable-win16 --prefix=/home/lvd/wine". After a (successfull) compile, I've copied wine directory to my real machine (64bit install of the same ubuntu 14.04) and after preparations ( cd /home/lvd, export $WINEPREFIX=/home/lvd/.wine32, export $WINEARCH=win32, wine/bin/winecfg ) run install: wine/bin/wine start 'H:\AltiumInstaller.exe' where H: was automatically configured by winecfg to /mnt/cdrom where .iso was mounted. then run the software: wine/bin/wine start 'C:\Program Files\Altium\AD13\DXP.EXE' and after splashscreen and loading activity the hang happens. short (default) log, the log made with "WINEDEBUG=+relay,+seh,+tid wine/bin/wine start 'C:\Program Files\Altium\AD13\DXP.EXE' >/tmp/wine_longlog.txt 2>&1" and backtrace made with "winedbg \ bt all" after the hang are attached. -- 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 5

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 June 2021