https://bugs.winehq.org/show_bug.cgi?id=51890
Bug ID: 51890
Summary: A lot more old games would be so much more usable if
wine's virtual desktop had proper resizing
Product: Wine-staging
Version: 6.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: el(a)horse64.org
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I have a really significant amount of older games around, none of which will
launch on this machine without wine's virtual desktop feature because on a
widescreen monitor, they determine there is no "expected" fullscreen resolution
available and crash.
Now I'd just use the virtual desktop, except it feels archaic and not very
usable: why is it that for a 800x600 game on a 800x600 virtual desktop, I can't
just maximize the virtual desktop window and get the virtual desktop SCALED UP
with proper letterboxing so I can play in some other way than a tiny window
with zero immersion and everything so small I can barely see it? Funnily enough
I can even resize the virtual desktop window except the resizing is fully
ignored and I just get black void with no scaling up all around with the game
stuck in the top-left, and the maximizing is blocked.
Scaling up (with automatic letterboxing), maximizing would seem like such
obvious features to make virtual desktop gaming infinitely less clumsy and
weird that I am a bit surprised it's not in there yet. Can it please be added??
--
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=44931
Bug ID: 44931
Summary: This program requires at least 3MB of free virtual
memory to run in "Nine: The last Resort" game
Product: Wine
Version: 3.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: register001(a)free.fr
Distribution: ---
Created attachment 61032
--> https://bugs.winehq.org/attachment.cgi?id=61032
WINEDEBUG=+relay,+seh,+tid wine your_program.exe >> /tmp/output.txt 2>&1
I get this error dialog box when running the game Nine The last Resort after
installation.
Dialog Title: "Director Player 5.0"
Message: "This program requires at least 3MB of free virtual memory to run"
Config:
Ubuntu 16.04
wine-3.5
--
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=53371
Bug ID: 53371
Summary: 0024:fixme:ntdll:create_logical_proc_info stub
Product: Wine
Version: 7.12
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yklaxds(a)gmail.com
Created attachment 72755
--> https://bugs.winehq.org/attachment.cgi?id=72755
log
FreeBSD 13.1 release amd64
KDE plasma 5
emulators/wine-devel 7.12 not work at all.
--
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=52235
Bug ID: 52235
Summary: Many surfaces in the game Obduction look black
Product: Wine
Version: 7.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: zerooneo(a)01101001.net
Distribution: ---
Created attachment 71338
--> https://bugs.winehq.org/attachment.cgi?id=71338
Screenshot
When running the game Obduction in wine, an interesting effect occurs where
most surfaces are pure black, yet with some lighting etc. applied, leaving the
game looking extremely dark.
This effect does not occur when running the game with DXVK, meaning there's a
very specific difference the two implementations that has a large effect on
this game.
The log shows a few DirectX and Direct3D-messages initially (counts on the
left):
1 03d8:fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x1.
1 03d8:fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x20.
1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x12d2cad0, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d30, modes 0x7fe90cc3ac00
partial stub!
1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x12d2cad0, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d30, modes (nil) partial
stub!
1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed354e0, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ad0, modes 0x18fa4d80
partial stub!
1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed354e0, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ad0, modes (nil) partial
stub!
1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed39050, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ab0, modes 0x1aece780
partial stub!
1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed39050, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ab0, modes (nil) partial
stub!
1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xf0f51c0, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d50, modes 0x1af84680
partial stub!
1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xf0f51c0, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d50, modes (nil) partial
stub!
2 04a8:fixme:d3d:create_texture_view Depth slice (0-1) not supported.
10 04a8:fixme:d3d_shader:shader_glsl_handle_instruction Backend can't handle
opcode dcl_stream.
46 03d8:fixme:d3d11:d3d11_device_CheckFeatureSupport Unhandled feature 0x3.
432 04a8:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled
interpolation mode 0x3.
And then thousands of these:
1080 04a8:err:d3d:wined3d_debug_callback 0x578c00: "GL_INVALID_ENUM in
glTexBufferRange(internalFormat GL_RGBA16_SNORM)".
4632 04a8:err:d3d:wined3d_debug_callback 0x578c00: "GL_INVALID_ENUM in
glTexBufferRange(internalFormat GL_RGBA8_SNORM
Might it be that certain textures or shaders aren't supported, and that that
leads to them being rendered as black?
This game also requires some other features in order to work fully, but it
might be worth it to fix this issue either for the sake of other games, or in
case further support for this game is added in the future.
--
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=51678
Bug ID: 51678
Summary: Avogadro crashes when adding atoms
Product: Wine
Version: 6.15
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Just install, open the program (avogadro.exe) and click two times into the
black 3D part of the window.
Wine crashes with something like "Unhandled page fault on read access to
8010C497 at address 72A562D3"
--
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=53939
Bug ID: 53939
Summary: TextOut will output ASCII control character(0~31) as
tofu cause crash
Product: Wine
Version: 7.12
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: 399989567(a)qq.com
Distribution: ---
TextOut will output ASCII control character(0~31) as tofu cause crash
build a string on windows
> static WCHAR str[] = {0x1c,0x30,0x31,0x32,0}
use TextOut(hdc,x,y,str,wcslen(str)) to output this str
on windows: output is "012"
on wine : output is "?012"
The reason is that this API does not filter ASCII control characters, and
treats the control characters as an ordinary character to output.
by the way if we fillter the control character we alse need fix the API
:GetTextExtentExPointW
Because my program uses control characters, there will be problems when
calculating the length, resulting in a crash. If I filter out the control
characters in the code myself, it will not crash. And in principle, the focus
should be on whether control characters should be output
--
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=45329
Bug ID: 45329
Summary: Fresh steam install will not install games -- error:
"content servers unreachable"
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alasky(a)codeweavers.com
Distribution: ---
Created attachment 61617
--> https://bugs.winehq.org/attachment.cgi?id=61617
Steam error dialogue box
Ubuntu 18.04
Wine tip (most recent commit is
83f845dfa1bb4a6ec6e8b7f65e9469dc9a8a7787)
When attempting to install a game on a fresh Steam install, an error comes up
that says "content servers unreachable." The servers are not down and I am
able to install games correctly on my steam account not using wine. This issue
seems to be caused by an update on Steam's side.
--
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=54761
Bug ID: 54761
Summary: D3D12CreateDevice no longer in ABI of
libvkd3d-utils.so.1
Product: vkd3d
Version: 1.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: smcv(a)collabora.com
Distribution: ---
While looking at updating Debian's vkd3d package from 1.2 to 1.7, I noticed
that `D3D12CreateDevice@VKD3D_1_0` disappeared from the ABI of
libvkd3d-utils.so.1. Was this intentional?
(D3D12CreateDeviceVKD3D@VKD3D_1_0 is still there, but if I'm understanding the
intention of this library correctly, D3D12CreateDevice@VKD3D_1_0 should have
continued to be present for backwards compat with older library binaries.)
--
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=54784
Bug ID: 54784
Summary: mIRC 7.72 crashes after restoring from application
tray
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dragone2(a)risposteinformatiche.it
Distribution: ---
Created attachment 74279
--> https://bugs.winehq.org/attachment.cgi?id=74279
Unhandled exception: page fault on read access - mIRC - Wine-staging 8.5
mIRC was running for about 4-5 hours before the crash.
It was reduced on the tray and its icon was blinking to notify that there were
new messages / activities in channels or private messages.
I clicked on it to restore the window and see the messages and wine gave me
this backtrace (see the attachment).
I was forced to quit mIRC and restart it again.
This rarely happens, so it's not a real problem for me, but I don't know if it
could help you fix this.
Other infos:
- Executable path: D:\mIRC\mirc.exe
- mIRC Version: 7.72 (the latest one).
- mIRC running in portable mode from a specific drive (on Wine, D:\) formatted
in NTFS.
- mIRC was running using some custom scripts. But this crash never happen on
Windows.
- Distro: Linux Mint 21.1 with latest updates.
- Kernel: 5.15.0-69-generic
- Wine infos:
Wine build: wine-8.5 (Staging)
Platform: i386 (WOW64)
Version: Windows 10
- Drive Z: is a drive formatted in BTRFS.
- CPU: Intel Core i7-6700
- RAM: 32 GB, when the crash occurred I was using less than 8 GB.
--
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=52676
Bug ID: 52676
Summary: enigma protected software fails to work properly
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
CC: dark.shadow4(a)web.de
Distribution: ---
Created attachment 72003
--> https://bugs.winehq.org/attachment.cgi?id=72003
backtrace of the crash (note the garbage)
As I've said in bug 49052, the trial that's supposed to work just crashes
without displaying anything.
Attaching console output.
I've got one other trial that's also enigma protected - that one starts, but
enters an infinite loop without displaying anything. That one is using an
engine that's known to work here, so I suspect enigma being the reason of the
failure.
--
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.