October 2022 - Wine-Bugs - list.winehq.org

[Bug 53754] Wine set up impossible

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53754 --- Comment #2 from martensenjonah(a)gmail.com --- Created attachment 73222 --> https://bugs.winehq.org/attachment.cgi?id=73222 One of the logs -- 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.

Oct. 2, 2022

[Bug 53754] Wine set up impossible

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53754 --- Comment #1 from martensenjonah(a)gmail.com --- Created attachment 73221 --> https://bugs.winehq.org/attachment.cgi?id=73221 One of the logs - here it says my version 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.

Oct. 2, 2022

[Bug 53754] New: Wine set up impossible

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53754 Bug ID: 53754 Summary: Wine set up impossible Product: Wine Version: 0.9-pre Hardware: arm OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: martensenjonah(a)gmail.com Created attachment 73220 --> https://bugs.winehq.org/attachment.cgi?id=73220 Output of the terminal when I ran "make" Hey y'all, I am trying to install Wine from "wine-7.0.tar.xz". It's my first time and I found that using the usual package install method would not work for my system. That's why I went for this way which is supposedly a bit more complicated. However, I figured it out and ran the "./configure" without an issue. Then, come the "make" part, however, some issues appeared. The log told me to file a bug report (see "terminal output" attached). I also attached the files mentioned in that document. I have no clue what to make of this and cannot continue in installing Wine :( Maybe you guys can help me? -- 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.

Oct. 2, 2022

[Bug 53753] TikTok Live Studio crashes on start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53753 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu Ever confirmed|0 |1 Summary|TikTok Live studio will not |TikTok Live Studio crashes |run |on start Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Your wine version is over 2 years old. Please update to a newer version of wine. Instructions for Ubuntu can be found here: https://wiki.winehq.org/Ubuntu Also, please always attach the full terminal output, not only the backtrace, see: https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._termina… -- 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.

Oct. 2, 2022

[Bug 53753] TikTok Live studio will not run

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53753 Erik Dansbo <erik(a)dansbo.dk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erik(a)dansbo.dk -- 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.

Oct. 2, 2022

[Bug 53753] New: TikTok Live studio will not run

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53753 Bug ID: 53753 Summary: TikTok Live studio will not run Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: erik(a)dansbo.dk Distribution: --- Created attachment 73219 --> https://bugs.winehq.org/attachment.cgi?id=73219 backtrace of error from wine TikTok Live Studio crashes before even starting up. -- 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.

Oct. 2, 2022

[Bug 53711] Final Fantasy XI crashes randomly at multiple points

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53711 --- Comment #23 from pandora.xero(a)gmail.com --- Created attachment 73218 --> https://bugs.winehq.org/attachment.cgi?id=73218 Graphical Glitch Example .tar.xz Unfortunately, I was just casually playing when this one came up, so I don't have logs. But this one shows a screenshot of what it might look like if the game is about to crash. I know if I see this kind of glitching, it's going to crash within just a couple screen transitions. I included the backtrace and the memory map, for whatever good that does, but my intent here is more to show what happens when the problem DOESN'T immediately cause a crash. SUPER-weird. -- 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.

Oct. 2, 2022

[Bug 50779] thread changes in winegstreamer lead to increased virtual address space consumption which may lead to permanent freezes

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50779 --- Comment #28 from Rafał Mużyło <galtgendo(a)o2.pl> --- I wouldn't say 'always' and 'never'. As the log suggests, this was tested with a simple sounds effect - essentially a short beep. Engine caches only limited number of them - as I've said in earlier comments, in other games of that engine (even one affected by this bug, just not brutally so), the growth stops at (IIRC) 32 cached sound effects, then they get reused. It's simply that in the brutal example, game runs out of vm before it reaches that point - though the usage is still high enough to risk a random freeze later of a random reason. Given the time taken, some of the freezes with first commit only might have been of this nature. -- 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.

Oct. 2, 2022

[Bug 50779] thread changes in winegstreamer lead to increased virtual address space consumption which may lead to permanent freezes

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50779 --- Comment #27 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Rafał Mużyło from comment #26) > Created attachment 73210 [details] > log in wine 7.18 > > Hmm, you know, part of the problem might just be on the box. > Cause I might be barking up the wrong tree, but glib's "-Wl,-z,nodelete" > might play some role here. Thanks. I don't think nodelete matters, because that'll only add more VM usage once, rather than every time. Rather, it looks like the application is just creating a new filter graph every time it plays a given sound, and then never destroying it. It does stop the filter graph after the sound is done, though. This is consistent with 90107bba making things worse; previously we would essentially clean up all the GStreamer resources by also resetting the GStreamer filter to the null state. It's also consistent with 3b885fb5f making things worse, since that's another thread we create for every filter graph. Testing shows that Windows doesn't even leak the filter graph's message thread (rather, it seems to be shared among all filter graphs). So while it's possible that we're doing something wrong (missing graph events?) and that the game is supposed to be cleaning up its filter graphs, my guess is that we really do need to avoid creating any extra threads. That will be annoying. -- 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.

Oct. 2, 2022

[Bug 53752] New: Rayman 3: glitched graphics (black textures)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53752 Bug ID: 53752 Summary: Rayman 3: glitched graphics (black textures) Product: Wine Version: 7.3 Hardware: x86-64 URL: https://archive.org/download/rayman-3-pc-demo/Rayman3_ PC-Demo.zip OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 1b1b03055db8bf03c6783d4fcb19abf670d53338 Distribution: --- There are lots of black textures in Rayman 3 thus not so much of the game can be seen. Can be reproduced with the demo: the issue is already present in the main menu. According to my testing the problem appeared with commit 1b1b03055db8bf03c6783d4fcb19abf670d53338 wined3d: Try to allocate new OpenGL BOs from the client thread for DISCARD maps. With the previous commit in-game scenery looks good. Workaround: disable hardware TnL in the video settings utility called R3_Setup_DX8.exe in the demo. Rayman3_PC-Demo.zip (184M) md5: d6d3c2d76931feff73f56295a0dee6a3 Still present in wine-7.18-120-g001665d7354. OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03 OpenGL core profile shading language version string: 4.60 NVIDIA -- 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.

Oct. 2, 2022