https://bugs.winehq.org/show_bug.cgi?id=44066
Bug ID: 44066
Summary: mintty/msys2 doesn't work since wine 2.5.0 (named
pipes)
Product: Wine-staging
Version: 2.22
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.gursky(a)e-mail.ua
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Hi!
According to [1], I'm opening a new issue.
msys2 (based on Cygwin up to 2.5.x) does work on wine-staging.
Since 2.5.0 mintty starts but has no visible output. You can work only blindly
(ctrl+d closes the session).
Actually I've expected that since wine 2.5 msys2 will work not only on
wine-staging but also on wine. Unfortunately the opposite has happened.
Regards,
Andrey
[1] https://bugs.winehq.org/show_bug.cgi?id=17195#c189
--
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=52646
Bug ID: 52646
Summary: Trying to run wit (Wimms Iso Tools) , it works, its
just when I start the iso extraction it gives me this
error.
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: madeinclt26(a)gmail.com
Distribution: ---
Created attachment 71966
--> https://bugs.winehq.org/attachment.cgi?id=71966
After it starts extracting the iso it says " The program wit.exe has
encountered a serious problem and needs to close. We are sorry for the
inconvenience.
After it starts extracting the iso it says " The program wit.exe has
encountered a serious problem and needs to close. We are sorry for the
inconvenience.
--
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=54975
Bug ID: 54975
Summary: win32u:win32u exits prematurely, leaves child process
behind, interferes with
windows.globalization:globalization
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
win32u:win32u exits prematurely, leaves child process behind:
win32u:win32u start dlls/win32u/tests/win32u.c
[...]
win32u.c:1037: Test marked todo: res = 4
win32u.c:1040: Test marked todo: buf[1] = 0
win32u:win32u:09f0 done (0) in 0s 1295B
win32u.c:1045: Test failed: res = 0
win32u.c:1046: Test failed: buf = d
win32u.c:1049: Test failed: res = 0
win32u.c:1059: Test failed: res = 0
09e0:win32u: 14 tests executed (2 marked as todo, 0 as flaky, 4 failures), 0
skipped.
See https://test.winehq.org/data/patterns.html#win32u:win32u
There are two things to notice in the above log:
* The main win32u:win32u process is 09e0 but it did not issue a 'tests
executed' summary. This means it exited prematurely.
* 09e0 is a child process that continues running and printing messages which
interferes with the next test, specifically
windows.globalization:globalization.
Also on the TestBot one can find the corresponding Wine log which contains
these lines that seem strongly correlated to this issue:
0480:err:seh:KiUserCallbackDispatcher ignoring exception
0480:err:seh:KiUserCallbackDispatcher ignoring exception
wine client error:480: partial write 57344
Running: win32u:win32u (694 of 774)
Running tests - 6 failures
This issue only happens on Linux and happens systematically but only on three
configurations:
fg-deb64-t32 but not for the wow32 and wow64 builds on the same
machine
fgtb-debian11-wow64 but not for the wow32 build on the same machine
debian11b-wow64 but but not for the wow32 build on the same machine
(and none of the 32-bit builds on debian11 is impacted)
And I have been unable to reproduce this failure on my machine (fg-deb64-t32).
So it's unclear what causes this failure but it clearly started on 2023-05-15
so it's probably some commit on that day.
--
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=55143
Bug ID: 55143
Summary: unimplemented function
winegstreamer.dll.winegstreamer_create_video_decoder
called in 32-bit code (0x7b012566)
Product: Wine
Version: 8.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: zeroredgrave(a)gmail.com
Distribution: ---
Created attachment 74705
--> https://bugs.winehq.org/attachment.cgi?id=74705
Cannot Launch the App probably the introduction of the game( before main menu)
cannot create a video decoder i think
Max Payne 2 Cannot Launch due an unimplemented function
winegstreamer.dll.winegstreamer_create_video_decoder called in 32-bit code
(0x7b012566)
--
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=58041
Bug ID: 58041
Summary: PlayOnline Viewer: Black screen when running via
winewayland.
Product: Wine
Version: 10.4
Hardware: x86-64
URL: https://web.archive.org/web/20210810150839/http://www.
playonline.com/ff11eu/download/media/install_win.html
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: chiitoo(a)gentoo.org
Distribution: Gentoo
Running PlayOnline Viewer via Wayland by setting DISPLAY="" in an LXQt/Wayfire
session results into a completely black window.
The application still works, just no content can be seen.
Final Fantasy XI Online, which PlayOnline Viewer is used to launch, seems to
work OK so far, when navigated to blindly.
Did not spot anything different in the default terminal output yet.
Running via XWayland works as expected, though that also means a black screen
in displays other than the primary screen, or rather the content just isn't
updated in the other screens.
Without XWayland, the result is the same regardless of the display.
Thank you!
--
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=50484
Bug ID: 50484
Summary: Far Manager 3 crashes when Shift+Enter Execute in
separate window pressed
Product: Wine
Version: 5.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: lanthruster(a)gmail.com
Distribution: ---
Far Manager 3 crashes when executing a file association.
1. Download and extract farmanager3
https://www.farmanager.com/download.php?l=en (zip archive)
2. Create a text file with no or arbitrary content test.txt
3. Select test.txt and press Shift + Enter
Wine will crash. That bug was there for years, including Wine 2.3 and earlier
releases.
--
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=44253
Bug ID: 44253
Summary: Access violation in multiple cases
Product: Wine
Version: 3.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ihormcd+wine(a)gmail.com
Distribution: ---
Created attachment 60052
--> https://bugs.winehq.org/attachment.cgi?id=60052
crash
Access violation exception due to access by 0x0000 address in multiple use
cases while using Far3.
>From Far app try to:
1) on lunch of EXE file (Far.exe, WinMergeU.exe, others)
2) switch drive for the pane (Alt+F1/F2)
3) switch to Quick view mode for a file (Ctrl+Q)
*) few other cases
App: Far Manager 3.0 build 5100 x64
Wine details: wine-3.0-rc3, the app runs using wineconsole
--
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=58276
Bug ID: 58276
Summary: pulse.c should silence_buffer after calloc
Product: Wine
Version: 8.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winepulse.drv
Assignee: wine-bugs(a)winehq.org
Reporter: jxvhulzowyrobfwwze(a)nbmbb.com
Distribution: ---
When pulse_write is “prebuffering … frames of silence,” it uses calloc to zero
out a buffer, then immediately calls pa_stream_write.
This isn’t correct for an unsigned 8-bit (u8) stream, since the neutral value
should be 128 instead of zero. This causes noticeable clicking whenever the
sender stops or resumes playback. (For example, old games that play occasional
WAV files as sound effects.) The issue can be reproduced using Sound Recorder
from Win3.1 and an 8-bit mono WAV file. Play the same sound over and over until
it starts clicking/popping.
I’m not sure if this scenario (the end of a WAV file) should even trigger
“buffer underrun” logic at all, since it’s an intentional gap. But regardless
of the reason for the underrun, there should be a silence_buffer call there.
I tested this in Wine 8, but confirmed the logic is the same in the latest
version.
--
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=58198
Bug ID: 58198
Summary: Wine missing WH_JOURNALPLAYBACK, required by VB
SendKeys
Product: Wine
Version: 8.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user16
Assignee: wine-bugs(a)winehq.org
Reporter: jxvhulzowyrobfwwze(a)nbmbb.com
Distribution: ---
Wine doesn’t implement WH_JOURNALPLAYBACK, which is required by the Visual
Basic SendKeys function. This makes the game “Mordor: The Depths of Dejenol”
unplayable after entering the dungeon.
I’ve confirmed with 32-bit Wine 8 and 16-bit VB3, but the logic seems unchanged
in more recent Wine (and VB) versions. Microsoft eventually released a VB6
runtime that reimplemented SendKeys using SendInput instead of
WH_JOURNALPLAYBACK, but that only fixes VB6 binaries.
https://archives.miloush.net/michkap/archive/2007/09/10/4850360.htmlhttps://web.archive.org/web/20130615064311/http://blogs.msdn.com/b/michkap/…
The story gets worse for programs that invoke DoEvents after SendKeys. Since
DoEvents “first clears all pending keystrokes from the SendKeys function,” it
enters an endless loop waiting for PeekMessage to return the expected
WH_JOURNALPLAYBACK messages. CPU usage goes to 100%, and it’s easy to run out
of stack space if DoEvents is invoked repeatedly.
https://nolongerset.com/how-doevents-works/
Thankfully, running with WINEDEBUG=warn emits a clear message,
“SetWindowsHookEx16 hook type 1 broken in Win16” pointing us to
https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/user.exe16/hook.c
This game is particularly creative, using SendKeys as some sort of input
filter. Many keyboard and mouse inputs are apparently translated to SendKeys
calls. I don’t fully understand the logic, except that the game is unplayable
without it.
I can’t say whether it’s worth fixing this or not. At the very least, it’s
helpful to know why this game doesn’t work, without having to keep trying each
new Wine release.
The free demo of “Mordor: The Depths of Dejenol” can be downloaded from
https://www.decklinsdemise.com/mordor.htm
--
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=46930
Bug ID: 46930
Summary: DirectX 1 installer Closes after open without
installing
Product: Wine
Version: 3.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: sk9258user(a)mail.ru
Distribution: ---
Created attachment 64037
--> https://bugs.winehq.org/attachment.cgi?id=64037
log
I change wine Windows version to 95 and open DirectX 1.0 installer, but window
instant closes and Installing stopped on unpacking. In logs I see msvcp error
missing shm_open() function. WTF???
--
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.