https://bugs.winehq.org/show_bug.cgi?id=53008
Bug ID: 53008
Summary: When playing civilizatin2, winevdm crash
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: clabbe.montjoie(a)gmail.com
Distribution: ---
Created attachment 72378
--> https://bugs.winehq.org/attachment.cgi?id=72378
backtrace of winevdm
When playing civilization 2, game menu start, but after some time, game crash.
I am sure that it worked before, but i need some time digging backup to find
which version of wine I used.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58456
Bug ID: 58456
Summary: tSIP: drop-down menu regression in Wine 10.10 (macOS)
Product: Wine
Version: 10.10
Hardware: x86-64
OS: MacOS
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cemer99797(a)isorax.com
Created attachment 78907
--> http://bugs.winehq.org/attachment.cgi?id=78907
tSIP drop-down menu not working
When running tSIP (a SIP client) there is a regression of not being able to use
any drop-down menus in the Settings with Wine-devel 10.10 (and possibly since
10.7, I haven't tested). Afterwards, all the settings below the "ghost"
drop-down menu are also inaccessible until quitting and restarting the app in
Wine.
Reproduce:
open tSIP (wine tSIP.exe) and from the menu bar choose Configuration > Settings
> General > and click the drop-down arrow for the Translation drop-down menu
also try any other drop-down menu
confirmed working with Wine-devel 10.6
tSIP 0.3.09
download:
https://github.com/tomek-o/tSIP/releases/download/v0.3.09/tSIP_0_3_09_bin.z…
sha256: c24da4f492de4e7344e4e2ea01a1c8df7ffb6632ec51f64e8518c30def61e258
--
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.
https://bugs.winehq.org/show_bug.cgi?id=57811
Bug ID: 57811
Summary: wikis/Building-Wine contains broken/obsolete link
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: depaoli.renzo(a)gmail.com
Distribution: ---
As per instruction on the 404 website
"If you followed a link from a WineHQ.org page and reached this page in error,
please report it to the WineHQ.org Bugzilla.":
The link on the Wine Wiki
https://gitlab.winehq.org/wine/wine/-/wikis/Building-Winehttps://www.winehq.org/pipermail/wine-devel/2016-January/111245.html
is broken resulting in 404.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58451
Bug ID: 58451
Summary: rpcrt4: Fix 'FIXME: should use CreateTimerQueueTimer
when implemented'
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: rpc
Assignee: wine-bugs(a)winehq.org
Reporter: winehq-bugs_serge_180716(a)gautherie.fr
Distribution: ---
wine-1.1.18
https://gitlab.winehq.org/wine/wine/-/commit/5f6ae94ad0163341c2cd79a89f29b2…
added
{
/* FIXME: should use CreateTimerQueueTimer when implemented */
thread = CreateThread(NULL, 0, rpcrt4_http_timer_thread, timer_data, 0,
NULL);
}
although CreateTimerQueueTimer() was already implemented, by
wine-1.1.2
https://gitlab.winehq.org/wine/wine/-/commit/d343f2baf76413eb690cbc44a0d56e…
{
NTSTATUS status = RtlCreateTimer(phNewTimer, TimerQueue, Callback,
Parameter, DueTime, Period, Flags);
}
Check and fix that FIXME.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58450
Bug ID: 58450
Summary: Total Annihilation (GOG, demo) – Wayland black screen
on startup.
Product: Wine
Version: 10.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: karol23145(a)gmail.com
Distribution: ---
Created attachment 78901
--> http://bugs.winehq.org/attachment.cgi?id=78901
WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`.
### Summary
Total Annihilation (GOG version and demo) shows a black screen on native
Wayland (Mutter 48.3). On X11 it works perfectly, and on XWayland the game has
a minor fullscreen issue (see Bug 57482).
### Steps to reproduce
1. Download the Total Annihilation demo (or use the GOG version).
GAME DEMO CAN BE DOWNLOADED FROM:
https://archive.org/details/TotalAnnihilation_201405
2. Launch the game executable (`TotalA.exe`) under Wine on a native Wayland
session (No XWayland).
### Current behavior
The game process starts, sound can be heard, and keyboard input works (buttons
can be pressed), but the entire game window is black. The window is also not
fullscreen.
### Expected behavior
The game's intro videos should play, followed by the main menu, which should be
visible and interactive.
### Relevant logs, screenshots, screencasts etc.
*Attached are the following files:*
1. `TA.log`: Full Wine debug log captured with
`WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`.
2. `system_info.txt`: Output of `inxi -Fxxxza`.
### System Details
- **Wine Version:** Custom build from source (also tested with Wine development
branch, same result)
- **Windowing System:** Mutter 48.3 (Wayland session)
- **Distribution:** Fedora 42
- **Graphics Driver:** Mesa 25.0.7
- **Kernel version:** 6.15.4
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58228
Bug ID: 58228
Summary: Move child object page unable to fully load because it
is too long
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dimesio(a)earthlink.net
Distribution: ---
When merging entries, the page that shows the entries to move the child objects
to displays as one long list in alphabetical order. That list is now so long
that the page cannot fully load:
Ooops! Something has gone terribly wrong!
Our monkey train has derailed! Worry not, a webmaster gopher help army has been
dispatched and is on the way.
If this error continues to be a problem, please report it to us on our Forums
error details:
Error Message: Maximum execution time of 60 seconds exceeded
File: query.php:119
Discovered while trying to merge 千千静听 (TTPlayer)
https://appdb.winehq.org/objectManager.php?sClass=application&iId=11003 with
TTPlayer
https://appdb.winehq.org/objectManager.php?sClass=application&iId=6077. The
move child objects page only got as far as the H's before timing out.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=52999
Bug ID: 52999
Summary: Redout fails to detect visual c++ runtimes
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blue-t(a)web.de
Distribution: ---
Created attachment 72366
--> https://bugs.winehq.org/attachment.cgi?id=72366
Logfile
When i try to run Redout, it says you need to install the c++ runtime.
The log does not indicate anything going wrong:
002c:fixme:winediag:LdrInitializeThunk wine-staging 7.8 is a testing version
containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when
filing bug reports on winehq.org.
0118:fixme:imm:ImeSetActiveContext (0000000000CDB7F0, 1): stub
0118:fixme:imm:ImmReleaseContext (000000000001006C, 0000000000CDB7F0): stub
007c:fixme:imm:ImeSetActiveContext (0000000000356C10, 0): stub
007c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000356C10): stub
0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
0000000000B9FD70
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58420
Bug ID: 58420
Summary: Wine crashes when running msys2 iff CPU's PKU/PKRU
feature is enabled
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pipcet(a)protonmail.com
Distribution: ---
This is a heads-up about a bug in cygwin/msys2 which may be misreported as a
wine bug.
The Cygwin code assumes CPUID leaf 0x0d to indicate in EBX a 64-byte-aligned
value. That may or may not be true on current Windows systems, but on current
Linux systems running Wine, with recent CPUs, a CPU feature called "PKU" or
"PKRU" (memory protection keys for userspace), enabled by default, indicates an
additional 8-byte XSAVE area.
This makes the Cygwin code attempt to xsave to a non-64-byte aligned area,
which causes a segfault and abnormal program termination.
While this is clearly a bug, it's a bug that apparently cannot be triggered by
current Windows systems. This means Wine fails to be bug-for-bug compatible in
this case. I don't think there's an easy way around that: we'd have to trap
XGETBV and CPUID instructions to pretend that a feature that is enabled by
Linux actually isn't available.
It would have been nice if the Linux kernel had provided a way to disable the
pku feature on a per-process basis, but AFAICT, it didn't. The nopku kernel
command line argument makes things work, but requires a reboot and disables the
very useful PKU feature for the entire system.
So I don't think there's a good workaround here, but maybe we should suggest to
the Linux kernel people to allow per-process activation of any future XCR0
features?
--
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.
https://bugs.winehq.org/show_bug.cgi?id=56761
Bug ID: 56761
Summary: So when I install Blizzard.net setup exe its crashes
and gives me the backtrace log
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adampigeons(a)gmail.com
Distribution: ---
Created attachment 76555
--> https://bugs.winehq.org/attachment.cgi?id=76555
the log of the error
i launch battlenet exe setup then the window becomes unusable then i get the
backtrace log
--
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.