wine-bugs December 2021

wine-bugs@winehq.org

1 participants
4540 discussions

[Bug 42668] New: RealMYST crashes with "Too many open files" error
by wine-bugs＠winehq.org 17 Jul '23

17 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42668 Bug ID: 42668 Summary: RealMYST crashes with "Too many open files" error Product: Wine Version: 2.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: psychonaut(a)nothingisreal.com Distribution: --- Created attachment 57619 --> https://bugs.winehq.org/attachment.cgi?id=57619 Console output from Wine 2.3 realMYST (as distributed by GoG) crashes near the end of the introductory sequence, right before the book lands at the bottom of the screen. If I abort the introduction, I can start playing the game, which seems to work fine, except that it crashes after a few minutes (usually, but not always, when I try to save). The console output gives a message about too many files open: err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased I note that this is the same problem reported by Comment #10 of Bug 18975. I haven't tried increasing my maximum number of open file descriptors. It's currently set to 1024, though I think it would be bizarre for the game to require even that many. Unfortunately, it is not possible for me to get a backtrace. When I use winedbg, the game slows to a crawl and it's impossible to do anything. -- 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 21983] New: Buttons come on each other in Proteus
by wine-bugs＠winehq.org 16 Jul '23

16 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=21983 Summary: Buttons come on each other in Proteus Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ssserkkk(a)yahoo.com hi! The buttons in ISIS and ARES come on each other. The ones that create this problem are "subcircuit mode ile terminals mode", "virtual instruments mode and 2D graphics line mode" in ISIS program; "connectivity highlight mode and round through-hole pad mode", "padstack mode and 2D graphics line mode" in ARES. -- 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 31

[Bug 47325] New: Steam Login: cannot select Account Name or Password text boxes when emulating a Virtual Desktop
by wine-bugs＠winehq.org 14 Jul '23

14 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=47325 Bug ID: 47325 Summary: Steam Login: cannot select Account Name or Password text boxes when emulating a Virtual Desktop Product: Wine Version: 4.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeffersoncarpenter2(a)gmail.com Distribution: --- Steps to reproduce: * Emulate a virtual desktop through winecfg. * Install and run Steam. Proceed to the login prompt. * Attempt to select the "Account name" and "Password" textboxes. Expected Behavior: Textbox is selected when it is clicked on, i.e. it displays a flashing cursor and characters accumulate in it when keys are pressed. Actual Behavior: Textbox is not selected. No cursor is displayed, and it does not respond to key presses. Easy Workaround: Grab and move the steam login window inside of the virtual desktop. After doing this it becomes possible to select the text boxes in the window and enter Account Name and Password. -- 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 41976] New: Very high CPU usage while downloading stuff in Steam
by wine-bugs＠winehq.org 14 Jul '23

14 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=41976 Bug ID: 41976 Summary: Very high CPU usage while downloading stuff in Steam Product: Wine Version: 2.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Distribution: --- I'm now downloading Crysis in the latest Steam/Wine releases and CPU usage is extremely high: PID USER PR NI VIRT RES %CPU %MEM TIME+ nTH COMMAND 31543 birdie 20 0 2731.0m 227.1m 51.7 1.4 6:43.52 42 Steam.exe 31401 birdie 20 0 8.0m 5.6m 49.0 0.0 5:44.30 1 wineserver One extra note: I'm downloading to tmpfs so disk IO has zero effect on this process. The current download speed is around 3MB/sec (24Mb/sec). This is a bug. -- 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 20

[Bug 36511] New: widl fails to build with clang -fsanitize=undefined
by wine-bugs＠winehq.org 14 Jul '23

14 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=36511 Bug ID: 36511 Summary: widl fails to build with clang -fsanitize=undefined Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com make[1]: Entering directory `/home/austin/src/wine-clang/tools/widl' clang -fsanitize=undefined -m32 -g -O2 -o widl client.o expr.o hash.o header.o proxy.o register.o server.o typegen.o typelib.o typetree.o utils.o widl.o write_msft.o parser.tab.o parser.yy.o ../../libs/wpp/libwpp.a ../../libs/port/libwine_port.a ../../libs/wpp/libwpp.a(ppy.tab.o): In function `ppy_parse': /home/austin/src/wine-clang/libs/wpp/ppy.y:397: undefined reference to `__mulodi4' /home/austin/src/wine-clang/libs/wpp/ppy.y:397: undefined reference to `__mulodi4' /home/austin/src/wine-clang/libs/wpp/ppy.y:397: undefined reference to `__mulodi4' clang: error: linker command failed with exit code 1 (use -v to see invocation) make[1]: *** [widl] Error 1 make[1]: Leaving directory `/home/austin/src/wine-clang/tools/widl' make: *** [tools/widl] Error 2 -- 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 49560] New: Ashes of the Singularity: Escalation freezes at Turinium Optimized
by WineHQ Bugzilla 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49560 Bug ID: 49560 Summary: Ashes of the Singularity: Escalation freezes at Turinium Optimized Product: Wine Version: 5.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mo78(a)abv.bg Distribution: --- Created attachment 67700 --> https://bugs.winehq.org/attachment.cgi?id=67700 Ashes of the Singularity: Escalation Wine log Ashes of the Singularity: Escalation freezes at Turinium Optimized caption. The game starts fine and when reaches "Turinium Optimized" in the loading menu, it freezes and I have to kill it manually. I can't reach the main menu, it's the initioal loading screen of the game. Tried with clean prefix and on two different Linux distros - Arch and Linux Mint. It's the latest GOG version. https://i.imgur.com/N9RgT5g.png -- 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 11

[Bug 42562] New: Act of War stuck at open (GOG and Steam Versions Affected )
by wine-bugs＠winehq.org 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42562 Bug ID: 42562 Summary: Act of War stuck at open (GOG and Steam Versions Affected) Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Act of War direct action steam and gog versions stuck at try open, one cpu core go to 100% and actofwar.exe process cant be closed -- 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 52111] New: <144dpi fonts aren't anti-aliased when using greyscale method
by WineHQ Bugzilla 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52111 Bug ID: 52111 Summary: <144dpi fonts aren't anti-aliased when using greyscale method Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: fonts Assignee: wine-bugs(a)winehq.org Reporter: teamworks1732(a)gmail.com Distribution: --- Created attachment 71135 --> https://bugs.winehq.org/attachment.cgi?id=71135 96dpi with sub-pixel anti-alias method When setting the scaling dpi to <144dpi while the system is using "greyscale" font anti-alias method, Wine won't anti-alias any font. But using "sub-pixel" method will make it working. I have tried adding "+font" into the "WINEDEBUG" env var, and I got a pretty interesting log saying "0110:trace:font:freetype_get_aa_flags font L"Tahoma" -11 aa disabled by GASP" (more log info at the attachment) -- 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 10

[Bug 39830] New: TomTom Home 2 TomTomHOMERuntime.exe failed with Error 87
by wine-bugs＠winehq.org 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=39830 Bug ID: 39830 Summary: TomTom Home 2 TomTomHOMERuntime.exe failed with Error 87 Product: Wine Version: 1.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: detlef.bieritz(a)gmx.de Distribution: --- Created attachment 53171 --> https://bugs.winehq.org/attachment.cgi?id=53171 Screenshot Ubuntu 15.10 Wine 1.8 TomTom Home 2 TomTomHOMERuntime.exe failed with Error 87: Ungültiger Parameter (siehe Screenshot) Installation: OK Start: NOK Run: NOK -- 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 45070] New: closing threads causes "wine client error" and kills process when run under winedbg --gdb
by wine-bugs＠winehq.org 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45070 Bug ID: 45070 Summary: closing threads causes "wine client error" and kills process when run under winedbg --gdb Product: Wine Version: 3.6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Created attachment 61208 --> https://bugs.winehq.org/attachment.cgi?id=61208 test program showing problem When run under winedbg in gdb mode, closing a thread consistently causes 'wine client error:30: write: Bad file descriptor', aborting the program. The basic problem seems to be that gdb will inject breakpoints into dlopen() to allow hooking that function if desired. Normally this works fine, but this can also be triggered during thread teardown, i.e. inside of pthread_exit(). In this case we catch the SIGTRAP, but abort when we try to pass it along to wineserver, since we've already closed our file handle to the server pipe. The obvious solution seems to be to block SIGTRAP during thread shutdown. Attempting this makes the 'bad file descriptor' message go away, but the process still gets killed prematurely. I haven't figured out why. -- 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

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