https://bugs.winehq.org/show_bug.cgi?id=53313
Bug ID: 53313
Summary: Weird characters without proper LC_ALL with Inno Setup
4.2.2 installers
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: abacadacaba(a)gmail.com
Distribution: ---
Users shouldn't prepend LC_ALL for every executable if executable contains one
or several language(s).
Proper language for executable can be guessed from installer. Installer had
just one language and this language was correct.
Contained Resources by Language:
NEUTRAL 6
DUTCH 4
ENGLISH US 3
--
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=47871
Bug ID: 47871
Summary: gameux:gameexplorer crashes randomly
Product: Wine
Version: 4.17
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gameux
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gameux:gameexplorer crashes randomly on Windows 8 and 10:
gameexplorer.c:633: prepared EXE path:
L"C:\\Users\\winetest\\AppData\\Local\\Temp\\wct"
gameux:gameexplorer:0940 done (-1073741819) in 1s
Test failed: crash (c0000005)
Every line with a 'mixed' result is a date when the test crashed:
https://test.winehq.org/data/tests/gameux:gameexplorer.html
Unfortunately there is no backtrace but the last visible trace is in
test_install_uninstall_game() which is the last function to be called. So that
narrows down the range where the test crashes.
The crash happens in both 32 and 64 bit tests on the following configurations:
* cw-rx460-32 *real hardware* machine running Windows 8.1
* w8 and w8adm both Windows 8.1 TestBot VMs, the former running with elevated
privileges and the latter just in an administrator account.
* w1064v1507 a Windows 10 1507 TestBot VM (elevetated privileges).
--
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=53305
Bug ID: 53305
Summary: SketchUp 2017: Keyboard entry doesn't work correctly
after reinstall.
Product: Wine
Version: 7.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: HeartwoodJack(a)gmail.com
Distribution: ---
SketchUp 2017 stopped working so I reinstalled. Now it works again, very
nicely* but keyboard entry doesn't work correctly. I thought that it was just
the [Esc] key (to cancel an operation) but numerical entry (to set dimensions
etc) don't work. Keyboard shortcuts continue to work.
Exploring the behaviour, it seems that if I move or resize the SketchUp window,
then the keys work until after an operation. This doesn't apply to internal
windows like toolbars or attributes like 'Materials'. It feels like the cursor
click on the drawing space steals focus from the part of the program that
listens for data or cancellation. Nevertheless, mid-operation, you can still
cancel it by selecting a new operation (using a tool shortcut like [M] or [B])
so it isn't deaf to the keyboard input all together.
Any ideas?
* Works nicely, although this needs to be open in the background, as usual and
without effect:
Bug 50775 - Sketchup Make 2017 displays error message about
sketchup_webhelper.exe
--
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=53303
Bug ID: 53303
Summary: Tycho: When Tycho tries to run a companion exe it
corrupts the exe (VirusTotal check is clean)
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jessethecandent(a)gmail.com
Distribution: ---
Created attachment 72680
--> https://bugs.winehq.org/attachment.cgi?id=72680
sha1 hashes for files
A VirusTotal scan for the programs involved is clean along with the corrupted
programs.
I am using the development version of wine (wine-7.12).
Tycho uses a modified version of Find_Orb (find_o64_modified.exe) for some of
its tasks but will corrupt it when it tries to use it. If dosbox is available,
wine will run the corrupt exe in dosbox. Wine versions 5.16 and below will make
a corrupt find_o64_modified.exe.tmp instead of replacing the original exe,
which allows Tycho to properly use Find_Orb so Tycho can identify known minor
planets. However, a version of wine that old has bad OpenCL support. In a
windows 10 VM the hash of find_o64_modified.exe does not change when Tycho uses
it. Given Find_Orb's important place in the workflow of searching for minor
planets, people would quickly notice if it got corrupted in windows.
Corrupt exe observations:
-The corrupt exe is usually smaller than the original, even if you target
smallexe64.exe (https://github.com/katahiromz/smallexe), giving you a 3 byte
exe.
-The corrupt exe contains pieces of the original exe and stuff not in the
original exe.
-The same target exe produces the same corrupt exe but a different target exe
produces a different corrupt exe.
-Corrupting a corrupt exe does not change it.
warn+all doesn't give anything useful and a trace+all capture of the corruption
event ran my VM out of disk space.
Reproduction instructions:
Running Linux in a VM is recommended due to exe corruption. Uninstall dosbox if
you don't want to run the corrupted exe.
Go to www.tycho-tracker.com/download and download the "Tycho" (v9.2) installer
zip and the "Find_Orb [modified for Tycho]" (2021-07-20) zip file.
Extract the Tycho installer from its zip file.
In a 64 bit wine prefix run the Tycho installer.
Extract the find_orb_2021-07-20/find_o64/ directory and place the find_o64
directory in the wine drive_c directory.
Make a copy of find_o64_modified.exe and place it somewhere for future
reference.
Use wine to run Program Files/Tycho/Tycho.exe .
Click continue at the invitation to register window.
Go to the Settings dropdown menu and click on Find_Orb.
In the "Full Path to Find_Orb Modified Executable" section click browse and go
to the find_o64_modified.exe extracted previously (or put in a different file
you wish to corrupt)
Click on "Run Diagnostic Test". THIS WILL CORRUPT THE SELECTED EXE. IT WILL RUN
IF YOU HAVE DOSBOX INSTALLED!!
A successful test would look like:
[2022/07/02 16:20:20]: Ready.
[2022/07/02 16:20:22]: Beginning test...
[2022/07/02 16:20:23]: [INFO] Returned identifier=[131075], num tries=[0]
[2022/07/02 16:20:23]: [ OK ] Version [5] is a supported version.
[2022/07/02 16:20:23]: End of test.
[2022/07/02 16:20:23]: Ready.
Close Tycho and compare the find_o64_modified.exe (or other file you corrupted)
to the good copy you have.
--
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=9027
odecif(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |odecif(a)gmail.com
--- Comment #65 from odecif(a)gmail.com ---
Bug still present in wine-7.10.
--
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=53302
Bug ID: 53302
Summary: BayPhoto ROES crash after several minutes
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thirtythreeforty(a)gmail.com
Distribution: ---
Created attachment 72679
--> https://bugs.winehq.org/attachment.cgi?id=72679
stdout log of ROES
Bay ROES, downloadable from this page [1] (set your user agent to Windows to
get the .msi, or try link [2] directly), is a photo ordering application for
Bay Photo. It installs, launches, and runs well, and orders can be submitted
successfully.
I'm not exactly sure what version it is, since it's an evergreen wrapper that
downloads a Java app (I think).
However, after about 3 minutes the application will spontaneously quit - not
sure if it's a crash or not. This happens even if it's just launched and
allowed to sit. I am unsure why, although the stdout log (attached) has a
suspicious looking line:
> # [ timer expired, abort... ]
near the bottom.
Wine version: 7.12.r0.gb2bf7b6b899 (installed via wine-git AUR package)
[1]: https://bayphoto.com/order/bay-roes/
[2]: https://www.roeslaunch.com/ROES/labs/BayPhotoLab/launch.msi
--
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=53301
Bug ID: 53301
Summary: Misaligned button text until first mouseover in about
dialogs
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: taho(a)dnsdeer.com
Distribution: ---
In the "about" dialogs in winemine and winefile, the text of the "Wine license"
button is initially shifted to the left and shifts to a centered position the
first time it's hovered over.
--
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=53284
Bug ID: 53284
Summary: Syberia 2: game occasionally crashes following
graphical glitch
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: memax(a)gmx.fr
Distribution: Ubuntu
Created attachment 72650
--> https://bugs.winehq.org/attachment.cgi?id=72650
terminal output
Ubuntu 20.04.4 LTS 64bit
NVIDIA GeForce 940MX with driver 510.73.05
Wine staging 7.11 (WineHQ binary package) with a clean Wine directory and the
default Wine configuration
Syberia 2 french GOG.com version
syberia_2_french_20171109_(16283)
07df47be888add1d1ce0c3003338f790cfe8c92e Game.exe
Level of detail: high
Screen depth: 32bit
Anti-aliasing: on
Occasionally the display becomes corrupted with parts of the screen turning
black, and then the game crashes.
It seems to be similar to what happens in Syberia 1
(https://bugs.winehq.org/show_bug.cgi?id=53266) but it happens much less
frequently in Syberia 2.
--
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.