https://bugs.winehq.org/show_bug.cgi?id=52212
Bug ID: 52212
Summary: Doom Eternal - Crash on Launch
Product: Wine-staging
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: linards.liepins(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 71270
--> https://bugs.winehq.org/attachment.cgi?id=71270
report_1
See attached bugreports for various wine and launch options.
--
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=46803
Bug ID: 46803
Summary: Diablo 1 GOG.com crash
Product: Wine
Version: 4.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xzgamertag(a)mail.com
Distribution: ---
Created attachment 63823
--> https://bugs.winehq.org/attachment.cgi?id=63823
Log
Diablo crashes immidiately after skipping intro, while using hi-res, latest
version. When I try to run Diablo (Classic) version, it requires original CD to
proceed.
--
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=49780
Bug ID: 49780
Summary: wineconsole reports VT sequence support when it does
not
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: magiblot(a)hotmail.com
Distribution: ---
Created attachment 68092
--> https://bugs.winehq.org/attachment.cgi?id=68092
Demo application to reproduce the issue
Wineconsole does not support applications writing Virtual Terminal sequences
through the Console API. That's fine. However, when enabling the console
ENABLE_VIRTUAL_TERMINAL_PROCESSING mode on stdout with SetConsoleMode, no error
is returned, so the application has no way to detect whether VT sequences are
supported or not. This is documented in
https://docs.microsoft.com/en-us/windows/console/setconsolemode.
The port of Turbo Vision at https://github.com/magiblot/tvision is affected by
this. When using the Console API, Turbo Vision prefers VT sequences over
SetConsoleCursorPosition/SetConsoleTextAttribute for code reusability and
performance. Nevertheless, it can fall back to the latter method when
SetConsoleMode fails to enable either ENABLE_VIRTUAL_TERMINAL_PROCESSING or
DISABLE_NEWLINE_AUTO_RETURN. Since SetConsoleMode does not return error on
wineconsole, garbage is shown instead of a colorful interface.
STEPS TO REPRODUCE
To reproduce the issue on Turbo Vision:
(A) - Using the attached 'tvdemo.exe'
1. Run the application on wineconsole. You should see a black-and-white
background and escape sequences drawn on the console.
2. Press Alt+F, then D. You should see the command prompt, and the message "VT
enabled" at the top, which demonstrates the issue in SetConsoleMode.
(B) - Compiling from source code (requires up-to-date CMake and MSVC).
1. Insert the following code after line 63 in source/linux/win32con.cpp
(https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63…):
```
if (supportsVT)
cerr << "VT enabled" << endl;
else
cerr << "VT not enabled: " << GetLastError() << endl;
```
2. Follow the build instructions at
https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63…
3. Follow the steps in (A).
EXPECTED BEHAVIOUR
On Windows, support for VT sequences can be disabled by turning on the "Legacy
Console" mode. If tvdemo.exe is ran in these conditions, the interface is
displayed properly. If entering the command prompt by pressing Alt+F, then D,
the message "VT not enabled: 87" is displayed (error 87 stands for
ERROR_INVALID_PARAMETER), which is what should be shown on wineconsole as well,
since it clearly does not support VT sequences.
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.
http://bugs.winehq.org/show_bug.cgi?id=16302
Summary: [oblivion] can not skip the intro movie by press ESC
Product: Wine
Version: 1.1.8
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wangbinrobin(a)yahoo.com.cn
when runing Oblivion on Windows, we can skip the intro movie by pressing ESC,
but when runing Oblivion by wine, we can not skip it by ESC. it is quite a long
time to wait the intro movie end.
The graphic card I use is ATI Radeon 2600, driver 8.10
--
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=45871
Bug ID: 45871
Summary: Several apps in .NET472 crash with unhandled
exception.\nException at
System.Windows.Media.Composition.DUCE+Channel.SyncFlus
h()\n at
System.Windows.Media.MediaContext.Complet"...(native
d3dcompiler works around it)
Product: Wine
Version: 3.16
Hardware: x86
OS: Linux
Status: NEW
Keywords: dotnet, download
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
Created attachment 62374
--> https://bugs.winehq.org/attachment.cgi?id=62374
part of crashlog
Hi
Seen this for a bunch of programs while trying to run them with installed
dotnet472.
The bug seems to be hidden for several apps as they ship their owm
d3dcompiler_47, but some don`t I found out, and they crash
Something like:
01c2:fixme:d3dcompiler:make_assignment Check for casts in the lhs.
01c2:err:d3dcompiler:compile_shader HLSL shader parsing failed.
01c2:err:ntdll:vDbgPrintExWithPrefix 65: MIL FAILURE: Unexpected HRESULT
0x88760b59 in caller: intermediate rendering error
01c2:err:ntdll:vDbgPrintExWithPrefix 65: MIL FAILURE: Unexpected HRESULT
0x88760b59 in caller: The render thread failed unexpectedly.
Then crash
Example: Slackinstaller.exe:
winetricks dotnet452 win7 corefonts, then start installer with builtin
d3dcomiler_47 works fine.
However
winetricks dotnet472 win7 corefonts, then start installer with builtin
d3dcomiler_47 --> crash
(Note: for Slackinstller one also needs Staging-patches for bug 40613)
--
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=52078
Bug ID: 52078
Summary: MusicBee: exception when attempting to drag tabs
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sangv(a)protonmail.com
Distribution: ---
Created attachment 71090
--> https://bugs.winehq.org/attachment.cgi?id=71090
The exception MusicBee gives + the console output, in a tarball
When attempting to move the tabs located near the top of the window (the ones
labelled "Music", "Now Playing", "Playlists", etc by default) MusicBee will
throw an exception. This happens on both my existing MusicBee wineprefix as
well as a fresh one, and on MusicBee versions 3.2.6804 and 3.4.7805. In
addition to happening in Wine version 6.21, the issue remains in 6.22. Both
versions of Wine were compiled from source. I'm using winetricks verbs
`windowscodecs dotnet45 mfc42 xmllite gdiplus d3dx9 vcrun2008 wmp10`. My OS is
EndeavourOS with kernel 5.15.2-zen1-1-zen. (I don't know how much of this
information is really needed but I thought it was all worth a mention just in
case?)
Attached I have both the error MusicBee provides, as well as terminal output
with debug channels warn+all as no information was printed in the terminal
without 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.
http://bugs.winehq.org/show_bug.cgi?id=10472
Summary: File open dialog buffer too short for multiple file
selection
Product: Wine
Version: 0.9.49.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wine-comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: freireclaudio(a)yahoo.com.ar
The file open dialog seems to be using a buffer which is too short for multiple
file selection. While Windows itself has this bug/feature, wine's version is
much more annoying since I'm unable to select over 6 files usually (using long
but not excessive names).
A dynamic buffer (with a reasonable limit for security reasons perhaps) would
be preferrable, but even a bigger buffer would help.
I think windows' buffer is 4k.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52105
Bug ID: 52105
Summary: Handle to \Device\NamedPipe\ cannot be used as the
RootDirectory for NtCreateNamedPipeFile
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
CC: jacek(a)codeweavers.com
Regression SHA1: 2600ecd4edfdb71097105c74312f83845305a4f2
Distribution: ---
Commit 2600ecd4edf (server: Use a separated object for each opened named pipe
device file., 2018-10-29) split the role of the named pipe device and the named
pipe file.
However, in doing so, it changed the semantics of opening \Device\NamedPipe\.
In particular, it is no longer possible to use a handle to \Device\NamedPipe\
as RootDirectory when creating a named pipe.
This bug makes Cygwin's named pipe creation
(https://github.com/cygwin/cygwin/blob/4f47e64b11ed8d47c62fa89e9b971f44b7e9a…)
loop forever.
--
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=42606
Bug ID: 42606
Summary: wine doesn't *fully* respect locale settings in some
corner cases
Product: Wine
Version: 2.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
This time it's a problem even if this is the only app currently running in the
prefix.
Download address for the engine:
http://kikyou.info/dl_redirect.php?%2Ftvp%2Ffiles%2Fkr2_232r2.zip
Instruction for setting up a project:
http://kirikirikag.sourceforge.net/contents/Prepare.html (instructions seem to
be for a different archive, but get the point across)
So, when running 'LANG=ja_JP.utf8 wine krkr.eXe'(as it's different from my
standard locale) and starting that project, most of the things seem to work
correctly (as I've got the standard overrides for Gothic/Mincho set already in
place), yet...
When right clicking the engine console (not the game window), there's mojibake
in that menu.
WINEDEBUG=font log shows that for some reason CreateFontIndirectExW for Tahoma
is called with charset determined by my standard locale, instead of the
Japanese one.
That somehow results in the text being treated as encoded in that locale's
Windows codepage, instead of cp932 (or is that vice versa ?).
--
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=53019
Bug ID: 53019
Summary: MusicBee: inconsistent CJK/non-Latin support with
Tahoma, no support on any other font.
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: activeds
Assignee: wine-bugs(a)winehq.org
Reporter: v_winebugs(a)outlook.com
Distribution: ArchLinux
Created attachment 72386
--> https://bugs.winehq.org/attachment.cgi?id=72386
All of the screenshots showcasing the bug, in a .tar.gz file.
Tested on wine 7.7 as well as wine-staging 7.7. Running Arch Linux. Font
replacements installed via winetricks - allfonts + fakechinese, fakejapanese,
fakekorean.
When Tahoma is selected as the default font, which is default on new
installations of MusicBee in WINE, MusicBee displays CJK and symbols very
inconsistently. 新しい日の誕生 by 2814 is a good example as not only is Japanese text
used, but the artist name uses full-width characters which comes under the
symbol part of this bug.
The artist and album names are displayed just fine on the left sidebar, tag
editor, track listing panel and mostly on the playing track panel. Generally,
if there is no formatting on the text, it is displayed. However in the Music
Explorer view, as well as playlist views such as Album & Tracks, Albums and
Artists, squares are put in the text's place, typically on the portions meant
to be formatted like headings (bolded, increased font size).
When any other font is used, whether included by the WINE prefix or brought in
from the distro, absolutely no font is displayed for those symbols whatsoever.
Everywhere that renders fonts on MusicBee will not render any non-Latin symbols
whatsoever.
In either case, the title on the Playing Tracks panel does not display any
non-Latin symbols whatsoever. I've checked the formatting and used the Regular
variant of Tahoma. Changing the others on the Playing Tracks panel to Bold will
result in squares, changing the size is fine.
A workaround is to use a font that has all of the scripts needed for use, such
as WenQuanYi Micro Hei for Japanese, Korean (on the font picker as Hangul and
Hangul(Johab)) and Chinese (CHINESE_GB2312 and CHINESE_BIG5). As long as it has
the relevant scripts, the symbols will be displayed, however since most fonts
don't include CJK scripts, WINE/MusicBee has trouble displaying them when those
fonts are picked. To make matters worse, due to .NET limitations, MusicBee can
only use TrueType fonts, and some fonts result in MusicBee complaining that
it's not a valid TrueType font, even though it only displays TrueType fonts in
the font picker (Yu Gothic UI was used for this example).
When searching for related bugs, I came across this:
https://bugs.winehq.org/show_bug.cgi?id=34298#c5
Adding a font that works to the registry changes basically nothing. MusicBee
still has trouble consistently rendering CJK and other symbols.
--
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.