http://bugs.winehq.org/show_bug.cgi?id=58353
Bug ID: 58353
Summary: Wiki FAQ page: missing header in .reg-file examples
for import
Product: WineHQ Gitlab
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gitlab-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spin.in.het(a)web.de
Distribution: ---
On the section
https://gitlab.winehq.org/wine/wine/-/wikis/FAQ#how-do-i-associate-a-native…,
samples of registry snippets for importing do not work because the following
header line is not part of the snippets (it took some time to figure this out):
> Windows Registry Editor Version 5.00
It would be nice if this can be added.
Note: doing import via command line (regedit file.reg) shows no error. Only
when import is done from the regedit gui, an error is specified. Tested with
wine-9.0 (Ubuntu 9.0~repack-4build3), as part of Kubuntu 24.04.
--
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=58352
Bug ID: 58352
Summary: Magic School Bus Explores in the Age of Dinosaurs
doesn't play videos.
Product: Wine
Version: 10.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ir50_32
Assignee: wine-bugs(a)winehq.org
Reporter: hibbsncc1701(a)gmail.com
Distribution: ---
Under wine 10.9, attempting to start Magic School Bus Explores in the Age of
Dinosaurs in a clean prefix results in a silent black screen that requires
clicking the mouse a bunch of times to get past it.
Playing the game results in certain areas where the game will seem to stop
responding while waiting for a video to complete. Such as exiting the bus. The
BGM keeps playing, and the background image keeps updating, but the video
itself doesn't play at all, and the user's input is ignored until the video
finishes "playing".
When this happens, we see stub messages from mciavi in the console.
As a workaround for the required clicking, placing a copy of ir32_32.dll from a
WinXP SP3 x86 installation in the game's install directory will result in the
audio playing during the initial black screen and allow it to continue without
user input, but we still get no video output.
Console log attached.
As a note for anyone trying to reproduce this bug: The game's installer won't
work due it requiring 256 color mode to run, and the suggested workaround on
the Wiki (DxWnd) not being able to handle 16-bit NE executables.
To get past the installer issues, You'll either need to have old enough
hardware to run X in 256 color mode, or use a VM to install it and copy the
resulting files (and "HKLM\Software\Microsoft\Microsoft Kids" registry keys)
over.
You'll also need to fix the system.ini in the wine prefix, to enable the
vidc.IV31 and vidc.IV32 lines or the game will refuse to start.
--
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=43233
Bug ID: 43233
Summary: Disabling strict draw ordering causes background
textures in FFXIV not to render properly
Product: Wine-staging
Version: 2.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spryor(a)redhat.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
In FFXIV, there are several areas that have a sort of fog texture over some of
the lower "skybox" uninteractable area. When disabling strict draw ordering,
the game performs much faster, but these textures fail to render, or flicker,
or flicker in a grid. However, enabling strict draw ordering is a pretty big
performance hit (about 15-20 fps hit in most situations)
Attached are pictures of two areas both with strict draw ordering and without.
It was difficult to catch it at a moment where all the splotches of background
were there, but the difference should still be clear
--
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=40916
Bug ID: 40916
Summary: The Bureau: XCOM Declassified (Steam) fails to start
(.Net4 installed)
Product: Wine
Version: 1.9.13
Hardware: x86
URL: http://store.steampowered.com/app/65930/
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Distribution: ---
Created attachment 55015
--> https://bugs.winehq.org/attachment.cgi?id=55015
plain terminal output + Protection Id log
I installed .Net4 via winetricks in the 32-bit Wine prefix to prevent an early
crash due to bug #34643. Other than that, only corefonts and Nvidia Physx are
installed, gameoverlayrenderer.dll is disabled.
When I launch the game an empty, black window is opened, titled 'The Bureau:
XCOM Declassified (32-bit, DX9)'. The game executable constantly uses 100% CPU,
but the game doesn't load. The process has to be killed to quit.
Changing Windows profile to Vista or Seven doesn't help.
This bug seems to be specific to the Steam version because the game starts
properly when using an 'unofficial' .exe for the game.
wine-1.9.13-114-gb1930ee
Fedora 24 x86_64
--
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=20843
Summary: Virtual colour depth & full screen resolution?
Product: Wine
Version: 1.1.33
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ezekiel000(a)lavabit.com
Would it be technically possible to implement a virtual desktop that allows you
to set the colour depth and resolution, but then wine will stretch the virtual
desktop to full-screen or to a custom resolution?
What would happen if you fooled a game that needed 256 colour depth into
thinking that's what it is running in while it is actually running at 24bit?
I ask this as I am unable to change my colour depth and reduce my resolution
below 640x480. And even when I could change my colour depth it meant restarting
the X-server. I assume other people will also have this problem.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=31367
Bug #: 31367
Summary: "OK" button in folder selecting dialog of XMPSetup is
always unavailable
Product: Wine
Version: 1.5.9
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
Created attachment 41208
--> http://bugs.winehq.org/attachment.cgi?id=41208
Log: XMPSetup folder open dialog broken
1. Download XMPSetup:
http://xmp.down.sandai.net/kankan/XMPSetup_4.9.0.1099-www.exe
1.5. (Optional)
Works around bug 31366 with `winetricks riched20` for displaying file path in
the file open dialog
2. Start with Wine XMPSetup
3.
- Click "接受"/"OK"
- Click "下一步"/"Next"
- Click "浏览"/"open" to open the "Select an Folder Dialog"/"选择文件夹"
- Select any folder in the dialog
Expect result:
the "OK"/"确定" button should be available
Actual result:
the button is always grey and unavailable
Not sure if the below message is related:
--- snip ---
fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
fixme:shell:BrsFolder_OnCreate flags 110 not implemented
--- snip ---
--
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.
http://bugs.winehq.org/show_bug.cgi?id=32445
Bug #: 32445
Summary: PuTTY window does not receive focus when "Allow window
manager to control windows" option disabled
Product: Wine
Version: 1.5.19
Platform: x86-64
URL: http://www.chiark.greenend.org.uk/~sgtatham/putty/
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
I noticed this issue testing PuTTY 0.62 with wine-1.5.19-74-g4bb92e1. Testing
on Lubuntu 11.10 (OpenBox 3.5.0 WM).
When the "Allow the window manager to control the windows" option has been
disabled using winecfg, the PuTTY terminal window does not receive keyboard
input. Instead the console window which you ran putty.exe from receives input.
That only applies to the PuTTY terminal window, not the initial settings
window. It also only applies when *not* in virtual desktop mode.
To reproduce:
- Disable "Allow the window manager to control the windows" in winecfg
- Download and run putty.exe. The PuTTY Configuration window appears. Note
that initially it does not seem to have focus; the window title bar is grey not
blue. However the window does actually have focus and receives keyboard input.
- Connect to a server. E.g. enter telehack.com for Host Name, Telnet for
connection type and click the Open button.
- The terminal window appears after a few seconds. It seems to be focused
(title bar blue) but even if you click in the window, the characters you type
appear in the console. (If you activate another window before clicking in the
PuTTY one, input goes to that window instead.)
--
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.
http://bugs.winehq.org/show_bug.cgi?id=23301
Summary: Steam 2010 version: tooltips popups even when the
steam windows isn't top-active one
Product: Wine
Version: 1.2-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mooroon2(a)mail.ru
Created an attachment (id=29052)
--> (http://bugs.winehq.org/attachment.cgi?id=29052)
Fragment of a screenshot showing the bug in action.
If I've got Steam client window opened on a page where some help tooltips are
expected to popup on mouseover's over some UI elements they would popup and
show as a top z-order window no matter is the Steam windows currently active
one or not. An example how might it look like may be seen in attached
screenshot.
Easiest page to trigger the bug is the "Game details" view in the games library
for the games with "Achievements" available - there would be tooltip popups
when moving the mouse pointer over the pictures representing the achievements.
This behavior was spotted with wine versions starting at about 1.2-rc1 and up
to current 1.2-rc4. Can't tell if earlier versions of Wine suffered the same
bug as I haven't got enough free time to compile and do some tests with em.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=51310
Bug ID: 51310
Summary: Steam - gameoverlayrenderer.dll issue, fps loss and/or
stuttering if not disabled
Product: Wine
Version: 6.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gab.pulcio(a)gmail.com
Distribution: ---
Basically many games relies on gameoverlayrenderer.dll, if I disable it (which
I did for now) they won't launch at all... a game that doesn't launch is
"Spintires - Mudrunner" for example.
Disabling it though resolves a lot of problems, more FPS in a lot of games
(with it enabled there is an annoying stuttering and constant FPS drop, every
second) BUT there is this little problem: many games won't launch with it
disabled.
So, I tried to disable the steam overlay and re-enabling
gameoverlayrenderer.dll, it should've fixed the FPS issue, only a few games
benefits from this though.
I think that disabling the overlay through steam settings doesn't completely
remove that garbage, thus the FPS drop/stuttering even without overlay.
--
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.