https://bugs.winehq.org/show_bug.cgi?id=53323
Bug ID: 53323
Summary: Wireshark doesn't update list of packets during
capture
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: rpisl(a)seznam.cz
Distribution: ---
This is a continuation of bug 53104. Now Wireshark starts capturing packets
successfully but the packets aren't shown on the list. Either "Update list of
packets in real-time" option must be deselected or Ctrl+R must be pressed after
capture is stopped to update the list. This bug is not very interesting as
Wireshark is also native for Linux, but my unqualified guess would be that this
a file/pipe handling problem in Wine.
"setcap cap_net_raw,cap_net_admin=eip wine64-preloader" is needed to give Wine
permissions to capture packets.
--
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=53314
Bug ID: 53314
Summary: ptrace attach timeout freezes processes to stopped
state
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: superemppu+winehq(a)live.fi
Distribution: ---
Created attachment 72691
--> https://bugs.winehq.org/attachment.cgi?id=72691
patch remove timeout
When wineserver wants to attach ptrace to a process, ptrace() is first called
with PTRACE_ATTACH and then wineserver waits on waitpid() until the process has
received a SIGSTOP. This is correct behavior and described on ptrace manpage.
https://linux.die.net/man/2/ptrace
However, there is a timeout: If the SIGSTOP hasn't reached the process in 3
seconds, wineserver will give up on the PTRACE_ATTACH and immediately do a
PTRACE_DETACH. According to the manpage, PTRACE_DETACH takes effect only when
the process is already stopped, so that PTRACE_DETACH does nothing. When
eventually the SIGSTOP reaches the process, it will be stopped forever and
wineserver thinks that the ptrace session is already over.
This bug only occurs when receiving a SIGSTOP takes over 3 seconds for a
process. On most setups that never happens, but on slow running fuse
filesystems the kernel may be in uninterruptible disk sleep for over 3 seconds.
In our setup this happens consistently when the process runs on fuse-overlayfs
on top of a slow NFS, and it probably happens on sshfs too. As a result, games
such as Subnautica and Arma Cold War Assault freeze to stopped state.
How can we fix this?
Method 1: Just remove the timeout entirely (patch attached). The only case
where that timeout matters is if the kernel is doing something important, in
which case we should probably wait, or a kernel thread is stuck, in which case
we have bigger problems. The fact that this bug has been in Wine for 20 years
and not reported proves that the timeout is not triggered much.
Disadvantages: If a kernel thread of one wine process is stuck, wineserver will
also be stuck for other wine processes even if their kernel threads are fine.
Method 2: If we want to keep the timeout, we should not do PTRACE_DETACH
immediately, but rather set a flag that PTRACE_ATTACH failed. When the SIGSTOP
eventually comes, a SIGCHLD will be sent to wineserver and we can do the
PTRACE_DETACH in the SIGCHLD handler if the flag was set.
Disadvantages: We need an arbitrary timeout. 3 seconds is not enough for slow
fuse filesystems. If the timeout is triggered, processes may still crash
because they could not use whatever windows API wineserver was emulating with
ptrace.
--
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=53322
Bug ID: 53322
Summary: Ride 2 config tool needs mfc140u.dll
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: mfc
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
049c:err:module:import_dll Library mfc140u.dll (which is needed by
L"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Ride
2\\ConfigDialogX64.dll") not found
wine-7.12-111-g9af3a79b963
--
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=40865
Bug ID: 40865
Summary: Steam needs to be online to update. Please confirm
your network connection and try again.
Product: Wine
Version: 1.9.12
Hardware: x86
OS: NetBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adrien_fernandes2(a)hotmail.com
Created attachment 54877
--> https://bugs.winehq.org/attachment.cgi?id=54877
WINEDEBUG=+winhttp,+wininit,+winsock,+teh,+sid wine Steam.exe
Steam can not fetch client (http problem ?).
I don't think it is because it can't find my network, I was using mupen64pp.exe
and I successfully joined a friend online to play with him.
--
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=53318
Bug ID: 53318
Summary: error on c sharp program
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pingo-power(a)hotmail.fr
Distribution: ---
Created attachment 72699
--> https://bugs.winehq.org/attachment.cgi?id=72699
logs
a
--
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=53320
Bug ID: 53320
Summary: Star Craft 2 bad textures
Product: Wine-staging
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: terapy-session(a)bk.ru
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 72702
--> https://bugs.winehq.org/attachment.cgi?id=72702
screen
Red squares around some units, such as those from the company. Launched with
DXVK installed, but the HUD in the game did not work, perhaps DXVK does not
work for this game, and bugs with OpenGL (which sometimes happens with OpenGL)
--
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=53316
Bug ID: 53316
Summary: WGL context sharing does not work on Intel driver
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: trass3r(a)gmail.com
Originally encountered when testing DK2:
https://bugs.winehq.org/show_bug.cgi?id=44260#c8
3de8:trace:d3d:texture2d_blt dst_texture 00B11400, ...
3de8:warn:d3d:context_create_wgl_attribs Failed to create a WGL context with
wglCreateContextAttribsARB, last error 0xaa.
3de8:err:d3d:wined3d_context_gl_create_wgl_ctx Failed to create a WGL context.
0xaa is ERROR_BUSY, which is returned because the context to be shared by the
new context in the helper thread is still current in the main thread.
See
https://github.com/roxlu/windows-opengl-context#solution-https://bugzilla.gnome.org/show_bug.cgi?id=792407#c2https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/blob/master/ext/q…
Tested on Win11, Intel UHD620 Driver 30.0.101.3113
with
wine reg add 'HKCU\Software\Wine\Direct3D' /v csmt /t REG_DWORD /d 0
The problem does not occur when replacing the driver with GLonD3D12 from
https://github.com/pal1000/mesa-dist-win
--
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=53179
Bug ID: 53179
Summary: Can't get into the Lineage 2 server
Product: Wine-staging
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: terapy-session(a)bk.ru
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Не зайти на сервер Lineage 2. После авторизации прохожу до выбора сервера, и
при нажатии войти никакой реакции, через несколько минут происходит дисконнект.
3 июня работало, возможно повлияло обновление Wine. Старого пакета Wine не
сохранилось чтоб проверить.
В ошибках логах есть:
0298:err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this
requires special permissions.
Сервер использует WMI, возможно там что-то меняли.
--
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=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.
https://bugs.winehq.org/show_bug.cgi?id=53271
Bug ID: 53271
Summary: Elder Scrolls Online crashes/refuses to start after
pressing Play in launcher
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: schwemley.lyle(a)gmail.com
Distribution: ---
Created attachment 72643
--> https://bugs.winehq.org/attachment.cgi?id=72643
txt file it told me to upload
I downloaded ESO directly from the website (not Steam) and installed it using
Wine. It installed perfectly. I press "play" and it says "eso64.exe has
encountered a serious problem and needs to close."
--
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=53132
Bug ID: 53132
Summary: Stack overflow in Lotus Approach on installation and
in document number dialogue
Product: Wine
Version: 7.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq.bugs(a)kjpetrie.co.uk
CC: zzhang(a)codeweavers.com
Regression SHA1: ccc2c6c613264aa228bd6b113dffebc7bcf2c1f3
Distribution: ---
If Approach is already installed it will mostly function normally, until
opening the Document number selection dialogue box.
If installing Approach it will proceed as far as the box confirming
installation is complete. This will have a pale blue title bar instead of the
shaded version seen when the bug is not present and clicking the Done button
will crash with a Stack Overflow.
A Regression Test shows:
ccc2c6c613264aa228bd6b113dffebc7bcf2c1f3 is the first bad commit
commit ccc2c6c613264aa228bd6b113dffebc7bcf2c1f3
Author: Zhiyi Zhang <zzhang(a)codeweavers.com>
Date: Wed Mar 2 14:21:48 2022 +0800
wine.inf: Enable Light theme by default.
Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
loader/wine.inf.in | 10 ++++++++++
1 file changed, 10 insertions(+)
Steps to reproduce installation error:
1. Clear .wine and using the above commit or later begin the Smartsuite
installation process, selecting default options and at least Approach as the
program to install. Continue accepting defaults until files are copied across.
If you see boxes reporting errors click Ignore. A dialogue box appears to
confirm installation.
2. Click the Done button.
Expected results:
The dialogue will have the same shaded titlebar as earlier ones in the process
and clicking Done will bring up questions about registration.
Actual result:
The box has a plain royal blue titlebar and clicking Done crashes the program
and abruptly closes the window. However the installed program still functions
if called using wine from a terminal.
Steps to reproduce the number selection crash:
1. Use wine <7.4 to install Approach from a Smartsuite '97 ISO and create a
simple sample database with at least two records for testing. Store that DB
outside ~/.wine to ensure it remains available after removing .wine.
2. Clear .wine and install the above commit or later.
3. Open the sample database and select a view (eg form) which contains the
Document number box near the bottom left.
4. Click the "Document number 1" box.
Expected result:
An active dialogue box opens inviting entry of the required document number.
Actual result. An inactive small window frame appears and freezes with its
initial background as content. The terminal reports a Stack Overflow. Clicking
the close button will produce a "not responding" query.
--
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=53164
Bug ID: 53164
Summary: Enter the Gungeon broken after Alt+Tab or Alt+Enter
Product: Wine
Version: 7.10
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: ---
Created attachment 72607
--> https://bugs.winehq.org/attachment.cgi?id=72607
error from Wine 7.10
1. character won't move at all
2. character can shoot
3. Ammonomicon won't open and will freeze game instead
Users can close the game with Alt+F4 and without rebooting the OS.
--
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=53243
Bug ID: 53243
Summary: Ctrl-number keys type the number, instead of sending
Ctrl-number
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: emendelson(a)mac.com
Ctrl-number (Ctrl-2, Ctrl-6, etc.) types the number, does not send Ctrl-2,
Ctrl-6, etc.
In macOS Monterey (Intel), with wine-devel installed via Brew, and testing with
the 64-bit version of the vDos MS-DOS emulator. The MS-DOS word processor
WordPerfect for DOS uses Ctrl-2 and Ctrl-6, but with vDos under Wine, Ctrl-2
types "2" in the editing window and Ctrl-6 types "3" in the editing window.
Ctrl-letter keys like Ctrl-C and Ctrl-V work correctly; only Ctrl-number keys
don't work.
Ctrl-number keys work correctly in the DOSBox-X emulator on the same Mac. They
only fail to work under vDos.
Is it possible to fix this?
--
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=6893
temp82(a)luukku.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |temp82(a)luukku.com
--- Comment #23 from temp82(a)luukku.com ---
still a checksum mismatch and a crash.
wine 7.12.
--
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=35294
Bug ID: 35294
Summary: Window borders shown over other windows
Product: Wine
Version: 1.7.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: p91paul(a)gmail.com
Classification: Unclassified
Created attachment 47074
--> http://bugs.winehq.org/attachment.cgi?id=47074
Opened Line window on top
Workflow: open a Line (http://line.naver.jp/en/) chat window. (window.png
attachment)
Switch to another window, so that the line window moves back.
Line window borders will remain visible(borders.png attachment: watch were
there was the window in window.png, you will see the borders)
I'm also unable to minimize the window, the button does nothing. The bug is
reproducible with "Allow window manager to manage the windows" checked; if I
uncheck it before launching wine, simply Line window stays over all other
windows (you will stay in the situation of window.png also if you focus another
window).
Running cinnamon on Arch Linux.
--
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.