November 2021 - Wine-Bugs - list.winehq.org

[Bug 51942] dlls/ntdll/unix/loader.c: In function ‘start_server’: error: expected identifier before ‘=’ token

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51942 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC| |z.figura12(a)gmail.com --- Comment #2 from Zebediah Figura <z.figura12(a)gmail.com> --- I think this is pretty clearly a duplicate of bug 51926. *** This bug has been marked as a duplicate of bug 51926 *** -- 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.

Nov. 1, 2021

[Bug 51926] Wine fails to build with glibc headers < 2.24

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51926 --- Comment #7 from Zebediah Figura <z.figura12(a)gmail.com> --- *** Bug 51942 has been marked as a duplicate of this 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.

Nov. 1, 2021

[Bug 51940] dlls/ntdll/unix/loader.c: In function ‘start_server’: warning: declaration does not declare anything

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51940 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- I think this is pretty clearly a duplicate of bug 51926. *** This bug has been marked as a duplicate of bug 51926 *** -- 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.

Nov. 1, 2021

[Bug 51926] Wine fails to build with glibc headers < 2.24

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51926 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |version2013(a)protonmail.com --- Comment #6 from Zebediah Figura <z.figura12(a)gmail.com> --- *** Bug 51940 has been marked as a duplicate of this 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.

Nov. 1, 2021

[Bug 51926] Wine fails to build with glibc headers < 2.24

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51926 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Regression SHA1| |d4259ac8e9326a8173d6f83f0d5 | |25c97b90a1da0 Status|UNCONFIRMED |NEW Summary|Cannot build wine 6.20 on |Wine fails to build with |Slackware Linux 14.2 |glibc headers < 2.24 Keywords| |regression --- Comment #5 from Zebediah Figura <z.figura12(a)gmail.com> --- Nice find. Those are static analyzer macros, which are littered throughout Microsoft's headers (e.g. denoting parameter values as input or output), and as a result they need to be included pretty much everywhere. Unfortunately they conflict with the C namespace... I think the best solution is to #undef after including the headers. -- 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.

Nov. 1, 2021

[Bug 51956] Morrowind: freezes when control keys are changing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51956 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |89c59e77c100bd4e6038a8cdcca | |97f2f9e13786e Component|-unknown |directx-dinput Keywords| |regression CC| |gyebro69(a)gmail.com, | |rbernon(a)codeweavers.com --- Comment #1 from Béla Gyebrószki <gyebro69(a)gmail.com> --- I can confirm the problem in Morrowind. It was introduced by commit 89c59e77c100bd4e6038a8cdcca97f2f9e13786e. -- 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.

Nov. 1, 2021

[Bug 5382] Add QT/GTK Integration

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=5382 Bamm Gabriana <bammgabriana(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bammgabriana(a)gmail.com --- Comment #27 from Bamm Gabriana <bammgabriana(a)gmail.com> --- Sorry for reviving this. The original post said, "Would even dynamic color scheme be an option?" and yet this was closed with the reason "Wine can not and will not use GTK/QT tool kits for it's GUI". I find this non-sequitur. One does not need to have GTK/QT tool kits in Wine just to import its colors. In fact, I once made an "external tool to get theme data from GTK/QT and import into Wine", and I implemented it using only a POSIX shell script, making calls to gsettings and then writing them as a .reg file importable by Wine Regedit. The issue is not about writing a tool, it's about making it work automagically. Let's say the user switches from a light to a dark desktop theme. Next time he opens a Wine application it would be blindingly bright. In my case, I would need to run my tool after I change the theme and before I run a program in Wine. The solution would be to find a way to run such a tool everytime wineboot runs, and this is where the cooperation of Wine developers is needed. It cannot be purely external since it needs a hook into wine's startup. I don't want this to be purely internal also, because those who do not want this feature shouldn't be forced to have it. (It might increase startup time by a small fraction of a second) I just want to ask the Wine developers to revisit this posibility of dynamic color theming by allowing such an external tool to run at startup, perhaps by having something like an autoexec file that a user can edit or that can be set by an external package. I'm thinking creating a directory like /etc/wine/autoexec.d/ and have packages drop scripts there that wineboot can run. Also, it should be opt-in, so that users can decide if they want this feature, otherwise, wineboot just ignores it. Is it possible to create such a hook? -- 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.

Nov. 1, 2021

[Bug 51926] Cannot build wine 6.20 on Slackware Linux 14.2

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51926 --- Comment #4 from studiosg(a)giustetti.net --- Thanks for the feedback Zebediah, I added a couple of #pragma directives to your example and can confirm that the problem only arises when building release 6.20. In your test and in wine <= 6.19 definitions are expanded as follows: Your Test / wine 6.19 The value of WIFEXITED(status): ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0x7f) == 0) The value of __WAIT_INT (status): (__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i)) While in Wine 6.20 they are expanded in: The value of WIFEXITED(status): ((((__extension__ (((union { __typeof(status) ; int __i; }) { . = (status) }).__i))) & 0x7f) == 0) The value of __WAIT_INT (status): (__extension__ (((union { __typeof(status) ; int __i; }) { . = (status) }).__i)) Please note the missing "__in"s. As far as I can tell, both "__in"s are replaced by an empty string (Lenght 0) resulting in a wrong definition and a syntax error. Adding line of code: #undef __in before the "start_server" function definition solves the problem for loader.c, but the very same error arises again later on when compiling process.c. __in is defined in "include/sal.h", line 347: #define __in This presented no problem before Wine 6.20. As far as I can tell the header is included where it should not, but I wasn't able to determine where so far. -- 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.

Nov. 1, 2021

[Bug 46472] Linux kernel 4.19 breaks startup of BO2 due to change in PTRACE_POKEUSER hw breakpoint behavior

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=46472 --- Comment #69 from tjb <troyb(a)us.ibm.com> --- (In reply to Lectrode from comment #67) > quick follow up: fixed directx issue by disabling nvapi support (new default > in lutris). game is running like normal (hangs on close, and sometimes needs > to be re-launched to connect to online services, but these are unrelated > issues) > > findings are the same: unhandled exception with wine-git as is, and playable > once those 5 ptrace lines are added from attachment 63662 [details]. > > > (latest commit on wine-git as of testing was > 5f93c683ab0163cb34482fe18549cf249b8b074b ) My ptrace patches are only needed if the ptrace poke to 0x11115555 is still in the code (this poke turned on interrupts for uninitialized trap addresses which caused the unhandled exception crash). If the 0x11115555 poke is removed (most likely removing workarounds and support for earlier linux versions) the trap addresses should not need to be iniitialized with 0s (an address which won't be hit) -- 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.

Nov. 1, 2021

[Bug 51961] Multiple errors when starting "winepath" command

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51961 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- fixmes are not errors -- 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.

Nov. 1, 2021