https://bugs.winehq.org/show_bug.cgi?id=42247
Bug ID: 42247
Summary: Chrome 39 Offline installer dosen't Install even on
the latest version of Wine
Product: Wine
Version: 1.7.50
Hardware: x86-64
URL: https://docs.google.com/uc?id=0B4aAK9c4Px0Ud3EwWG5Td1V
zR28&export=download
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: samashokp(a)gmail.com
CC: samashokp(a)gmail.com
Distribution: Other
Created attachment 56925
--> https://bugs.winehq.org/attachment.cgi?id=56925
Logs of Failed to install Chrome 39 Offline Installer, Generated by Wine
Chrome 39 Offline installer dosen't Install even on the latest version of Wine
Chrome 39 Offline Installer
https://docs.google.com/uc?id=0B4aAK9c4Px0Ud3EwWG5Td1VzR28&export=download
I've tested the following on Ubuntu, Linux Mint, Knoppix, etc..
Failed to Install on all of them.
--
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=57958
Bug ID: 57958
Summary: Caps lock issue when holding Caps lock with other key
and Caps lock state was already on
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: daniel.gaba(a)protonmail.com
Distribution: ---
Hello,
most of the time when holding Caps lock with another button game will register
double click first on CAPS LOCK.
In "Arma 3" and in "Arma: Reforger" CapsLock is used as push to talk button for
radio and you are often holding it alongside other buttons.
How to reproduce:
1. Caps lock state need to be on.
2. Hold other key, for example W for walking forward
3. Hold CAPS LOCK
4. In Arma 3 it will start broadcasting for ms and stop and after 1s it will
start broadcasting again.
In Arma: Reforger this will toggle between Squad <-> Platoon radio instead
because it detected double click on Caps Lock. Game will ignore you are still
holding caps lock.
There is small chance that bug will not trigger.
There is also possibility that game may mistakenly detect that you are still
holding the Caps Lock key after releasing it, causing it to continue
broadcasting until you press it again. I don't know how to reproduce this one.
This is very common issue for Arma players on Linux.
OS: Opensuse Tumbleweed Kernel version: 6.13.6-1-default
KDE plasma Version: 6.3.2 Wayland
Wine 10.3 but issue also happens on Proton 7,8 and 9
I tested it also with wayland driver and I was not able to reproduce it.
--
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=55076
Bug ID: 55076
Summary: Steam fills terminal output with "ResizeObserver loop
limit exceeded" messages.
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 74626
--> https://bugs.winehq.org/attachment.cgi?id=74626
Steam default terminal output wine 8.9
Hello,
This started after a Steam update sometimes ago I don't remember.
> [0617/144308.788:INFO:CONSOLE(1)] "ResizeObserver loop limit exceeded", source: https://steamloopback.host/index.html?IN_CLIENT=true&LOCAL_HOSTNAME=piezo1&… (1)
Searching the quoted string on the web shows that it's related to Chrome [1],
thus Chrome Embedded Framework too (libCEF).
The constant flow of messages fills the HD with several MB after a few hours.
It may be an application bug, but I can't compare to Windows because there is
no output at all when running steam from the Windows command prompt.
Regards.
[1]
https://stackoverflow.com/questions/49384120/resizeobserver-loop-limit-exce…
--
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=57537
Bug ID: 57537
Summary: Steuersparerklärung 2024 fails to install
Product: Wine
Version: 9.22
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: ---
Found while testing a report from the forums:
https://forum.winehq.org/viewtopic.php?t=39775
Ran in a clean WINEPREFIX, used trial version and express installation. It
gives a messagebox with
> Die Installation von >>Steuersparerklärung 2024<< konnte nicht durchgeführt werden! Prüfen Sie bitte, ob die notwendigen Installationsvoraussetzungen erfüllt sind
Translated:
The installation of >>Steuersparerklärung 2024<< could not be completed! Please
check whether the necessary installation requirements are met
--
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=57954
Bug ID: 57954
Summary: Watch_Dogs black splash screen 10.3
rawinput:add_device Failed to open device
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zlice(a)crtdrift.us
Distribution: ---
Created attachment 78201
--> https://bugs.winehq.org/attachment.cgi?id=78201
wd-winedbg
10.2 seems to work fine, 10.3 gives an error about rawinput and the splash
screen that should have the main character and game title is a black box and
hangs
using wow64 build, other 32bit games seem to work fine.
running with WINEDBEUG ends in multiple varying lines of
`0158:warn:rawinput:add_device Failed to open device file
L"\\??\\HID#some-device-name#{hex-hash-id}", status 0xc0000034.`
--
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=56941
Bug ID: 56941
Summary: EA app fails to launch game if total size of
environment variables exceeds ~32000 characters
Product: Wine
Version: 9.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: tinozzo123(a)gmail.com
Distribution: ---
### Steps to reproduce
Preparation:
- Have the EA app installed:
https://origin-a.akamaihd.net/EA-Desktop-Client-Download/installer-releases…
- I installed it through Bottles, which installs the following Winetricks
dependencies:
https://github.com/bottlesdevs/programs/blob/main/Games/eaclient.yml
Reproducing:
- Set a very long environment variable, before launching the EA app
- From the EA app, launch any game
- Alternatively, execute the game directly, it will automatically launch the
EA app to launch the game
- If you don't have any game, "The Sims 4" is free
- The game won't launch, an error popup from the EA app will appear (see notes)
### Notes
It doesn't matter whether these ~32000 characters are from a single environment
variable, or from the combination of many of them.
I didn't test on Windows. It may be impossible to test there, since the
environment block there has a limit of 32760 characters (which may probably be
the reason for this issue in the first place).
I say "~32000", because the issue starts occurring a little before 32760
characters. However, my counting method was imprecise (I simply typed `set` in
`wine cmd`, then counted the characters), and there's also the fact that the EA
app also sets its own environment variables.
The issue also occurs with games bought from Steam (thus launched with Proton)
that also have to go through the EA app (thanks EA).
This issue existed before, and the weird thing is that the error popup from the
EA app is different from some time ago (I imagine due to the app being
updated).
Before it was: "Failed to launch game. An error on our end caused the launch to
fail. Try again a little later."
Now it's: "The game hasn't released yet" (which is obviously untrue).
Is it a stack overflow issue?
Logs obtained with `WINEDEBUG=EADesktop.exe:+relay` are too big to attach, even
compressed. Let me know what `WINEDEBUG` parameters I should use instead.
I can see that the app calls `GetEnvironmentStringsW`, shortly followed by a
`WideCharToMultiByte` for each variable (key and value separately). This is
done three times.
--
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=57439
Bug ID: 57439
Summary: FL Studio: many 3rd party plugins violently flash in
child windows
Product: Wine
Version: 9.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lildebil.mgt(a)gmail.com
Distribution: ArchLinux
Created attachment 77436
--> https://bugs.winehq.org/attachment.cgi?id=77436
terminal log
As the title says, In FL Studio, many 3rd party vsts have flashing GUIs that
make them unusable and possibly hazardous to a select amount of people with
photosensitive epilepsy.
This only happens in FL Studio, likely due to how it handles plugin windows. In
other DAWs that let the window manager handle the plugin windows this does not
happen.
Side notes:
1. Most of the plugins with this issues are based on the JUCE framework
2. Whenever there is an option akin to "Disable OpenGL rendering" in the plugin
settings, turning it on will usually fix the flashing, but it is almost never
available.
Steps to reproduce:
1. Set the wineprefix to Windows 7, to avoid bug 57247
2. Download and install FL Studio 2024 Trial -
https://install.image-line.com/flstudio/flstudio_win64_24.1.2.4430.exe
3. Download and install one of the plugins with this problem (put .vst3 file
into C:\Program Files\Common Files\VST3) -
https://github.com/tobanteAudio/modEQ/releases/download/v0.4.0/modEQ-v0.4.0…
4. Scan and open plugin in a mixer track, drag plugin window or start audio
playback to see the issue.
I am using wine-staging 9.21 and proprietary Nvidia drivers
--
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=54227
Bug ID: 54227
Summary: Altium Designer 20.x - 22.x slowness in 2D schematics
editor - possibly GDI font rendering problem
Product: Wine-staging
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kepszlok(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 73773
--> https://bugs.winehq.org/attachment.cgi?id=73773
Wine's output
This is a problem that affects all Altium Designer versions from 20.x to
current, with all wine-staging versions of 7.xx branch.
See AD compatibility reports:
20.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=38478
21.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=40170
22.x https://appdb.winehq.org/objectManager.php?sClass=version&iId=40683
All of them shows slowness in the 2D schematics editor, while the 3D PCB editor
works fine.
Using the schematics editor, this message appears in constantly:
0118:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style
0000000001647F70.
(the schematics editor itself working fine, just unusably slow)
Possible reason:
"probably because X2 uses GDI font rendering by default and lacks option to
turn it off"
--
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=54906
Bug ID: 54906
Summary: Menu items with icons are drawn with black squares if
Wine is running in Vista+ mode
Product: Wine
Version: 8.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: george.hazan(a)gmail.com
Distribution: ---
The following construction fails in the all 8.x versions of Wine (currently I
upgraded to version 8.7 devel) and works Ok in Wine 7.1:
MENUITEMINFO mii = {};
mii.cbSize = sizeof(mii);
mii.fMask = MIIM_STRING | MIIM_STATE;
if (pimi->iconId != -1) {
mii.fMask |= MIIM_BITMAP;
if (IsWinVerVistaPlus() && IsThemeActive()) {
if (pimi->hBmp == nullptr)
pimi->hBmp = ConvertIconToBitmap(pimi->parent->m_hMenuIcons,
pimi->iconId);
mii.hbmpItem = pimi->hBmp;
}
else mii.hbmpItem = HBMMENU_CALLBACK;
}
InsertMenuItemW(hMenu, uItem, TRUE, &mii);
I.e. if I run command 'winecfg -v win2003', then everything is Ok with icons,
otherwise I see black squares instead of icons. This code works Ok under all
versions of Windows, from XP to Windows 11, the problem is specific to Wine 8.x
under Linux (I use Kubuntu 23.04).
To see the problem you can download my open source messenger Miranda NG from
https://miranda-ng.org/downloads, just download a ZIP, run it and open main or
tray icon menu. The full source code is avalable here:
https://github.com/miranda-ng/miranda-ng, you need module menu_utils.cpp inside
mir_app, InsertMenuItemWithSeparators or BuildRecursiveMenu functions.
WMBR, George Hazan.
--
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=50382
Bug ID: 50382
Summary: Lego Star Wars Saga needs native d3dcompiler_47
Product: Wine
Version: 6.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: j-r(a)online.de
Distribution: ---
After installing Lego Star Wars Saga (GOG version) into a fresh 32 bit prefix,
the game starts up fine including sound and controls, but with the exception of
backgrounds and some effects nothing (logo, menu, in game characters etc) is
displayed or replaced by grey boxes.
winetricks d3dcompiler_47 fixes that problem. (An older App DB report using
wine 3.3 mentions the same problem and fixing it by installing d3d9.)
There is no console output indicating a problem in that area (recreating the
test with wine 3.3 gives plenty of d3dcompiler error messages; perhaps they
have been silenced since then?). Since the other d3dcompiler related bugs I
checked all seemed to have d3dcompiler error messages I opened this new report,
though it very likely still is a duplicate.
Please advise which debug channels to turn on to generate a useful 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.