https://bugs.winehq.org/show_bug.cgi?id=49378
Bug ID: 49378
Summary: kernel32.WriteFile with multi byte characters reports
incorrect number of written bytes
Product: Wine
Version: 5.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: suokkos(a)gmail.com
Distribution: ---
Created attachment 67438
--> https://bugs.winehq.org/attachment.cgi?id=67438
Wine test case to trigger the bug
Writing utf-8 multibyte characters to stdout using stdio led to uncovering this
bug. Attached test case is a simple way to trigger the underlying issue.
Minimal steps leading to issue:
1. Set console output to CP_UTF8
2. Use WriteFile with multibyte characters
Expect outcome:
WriteFile reports number of bytes written.
Actual outcome:
WriteFile reports number of characters written.
Other observations while writing test case:
I first run same test case using kernelbase.WriteFile. Base version seems to
behavior differently because my test case passed. I only then noticed the
important detail that there is multiple WriteFile entry points.
--
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=45110
Bug ID: 45110
Summary: Crash when running courselab 2.4
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cjrw42(a)gmail.com
Distribution: ---
Created attachment 61295
--> https://bugs.winehq.org/attachment.cgi?id=61295
courselab 2.4 backtrace
I have installed courselab 2.4 (educational resource dev package which creates
HTML based sites), using the MSI, and all appears to have gone OK. Courselab
runs, grabs credentials, generates the licence key which is emailed and entered
fine, but as soon as you begin to create a new project it crashes out.
backtrace included.
--
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=40223
Bug ID: 40223
Summary: Mesa: User error: GL_INVALID_OPERATION in
glTexImage3D(bad target for depth texture)
Product: Wine
Version: 1.9.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ovariegata(a)yahoo.com
Distribution: Slackware
When starting the GOG version of Deus Ex with wine-staging 1.9.4 and a debug
version of mesa this error is printed several times.
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Here is the full output:
$ deusex
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
fixme:winediag:start_process Wine Staging 1.9.4 is a testing version containing
experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug
reports on winehq.org.
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
fixme:module:load_dll Loader redirect from L"uxtheme.dll" to L"uxtheme-gtk.dll"
fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32f314,0x32f30c): stub
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth
texture)
err:ole:CoGetClassObject class {92fa2c24-253c-11d2-90fb-006008a1f441} not
registered
err:ole:CoGetClassObject no class object {92fa2c24-253c-11d2-90fb-006008a1f441}
could be created for context 0x1
err:ole:CoGetClassObject class {d8f1eee0-f634-11cf-8700-00a0245d918b} not
registered
err:ole:CoGetClassObject no class object {d8f1eee0-f634-11cf-8700-00a0245d918b}
could be created for context 0x1
fixme:winediag:IKsPropertySetImpl_QuerySupport EAX sound effects are enabled -
try to disable it if your app crashes unexpectedly
fixme:ddraw:ddraw7_FlipToGDISurface iface 0x16e2a8 stub!
OS: Slackware-current
Relevant packages:
wine-staging-1.9.4-x86_64-1_SBo
mesa-compat32-847f1cc_2015.12.16_master-x86_64-1_gitcompat32
libdrm-compat32-4274539_2016.02.26_master-x86_64-1_gitcompat32
--
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=43433
Bug ID: 43433
Summary: Sony Vegas Pro 8
Product: Wine
Version: 2.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bameylan(a)bluewin.ch
Distribution: ---
Created attachment 58799
--> https://bugs.winehq.org/attachment.cgi?id=58799
Backtrace genered at the crash
This are the problems I encountered
I am using Linux Mint 18.2 x64.
I installed Sony Vegas Pro 8.0 on wine 2.13. Installation without problem.
But when I tried to run it, it stop at the moment that he "Adding GStreamer
AudioConvert filter"
--
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=49583
Bug ID: 49583
Summary: Assassin's Creed Odyssey displays black bars on top
and bottom.
Product: Wine
Version: 5.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: GloriousEggroll(a)gmail.com
Distribution: ---
Created attachment 67739
--> https://bugs.winehq.org/attachment.cgi?id=67739
AC Odyssey black bar fix
It's been a long known issue that AC: Odyssey renders with black bars on the
top and bottom of the screen (see screenshot 1).
Derek Lesho came up with a stub patch that both fixed this -and- allowed STEEP
to run (it would not display previously). That patch can be found here:
https://github.com/GloriousEggroll/proton-ge-custom/blob/5.12-GE-1/patches/…
Recently, the relevant function QueryDisplayConfig was implemented, however it
did not contain some of the changes Derek's patch adds. This allowed steep to
work, however AC: Odyssey still retained the black bar issue.
I modified Derek's patch by adding the relevant parts to QueryDisplayConfig,
and removing the relevant flag checks (Derek's patch did this previously), and
this allowed AC: Odyssey to render properly without the black bars. (see
screenshot 2). The patch is hacky but may provide more information towards
fixing this properly.
--
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=49748
Bug ID: 49748
Summary: Multisim 14.2 installer fails with "Directory name
invalid"
Product: Wine
Version: 5.15
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
When running the installer, it terminates with a MessageBox showing "Directory
name invalid".
--
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=49788
Bug ID: 49788
Summary: mountmgr is no longer detecting SCSI devices
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mountmgr.sys
Assignee: wine-bugs(a)winehq.org
Reporter: winebugzilla(a)tasossah.com
Regression SHA1: 19549d11a72f63efe0d689374446a56a68264a1f
Distribution: ---
Created attachment 68104
--> https://bugs.winehq.org/attachment.cgi?id=68104
regedit screenshot
Commit 19549d11a72f63efe0d689374446a56a68264a1f switched to using udisks2 to
detect devices, however this no longer detects SCSI devices.
This results in ASPI_GetNumControllers always returning 0, and ASPI
applications not detecting any optical drives.
Compiling wine one commit before the one mentioned above
(8388ea840fedbb9b646213a26cd59ceb3a48680b) restores the ability to detect and
use SCSI devices.
Tested on two different Ubuntu 20.04 installations, both with fully functional
udisks2.
Steps to reproduce:
Start up wine regedit
Navigate to HKLM\Hardware\DEVICEMAP\Scsi
Observe that it is empty
When functioning correctly, it should report all SCSI devices, including hard
disks and optical drives. In general, all devices that exist in /proc/scsi/scsi
should show up in the registry.
https://bugs.winehq.org/show_bug.cgi?id=31592 was opened presumably to move
away from /proc/scsi, however it is now a regression.
--
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=49825
Bug ID: 49825
Summary: GetNamedSecurityInfoA with LABEL_SECURITY_INFORMATION
returns ERROR_ACCESS_DENIED
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: vladimir.kokovic(a)gmail.com
Distribution: ---
Created attachment 68159
--> https://bugs.winehq.org/attachment.cgi?id=68159
wine log file
Hi,
I don't understand at all what this is all about even though I have a complete
WINEDEBUG log, when it comes to GetNamedSecurityInfoA with
LABEL_SECURITY_INFORMATION where ERROR_ACCESS_DENIED returns.
Although at first glance everything is normal, it is obvious that I do not know
enough wine and that is why I need help to resolve this situation and if
possible remove this bug for the sake of others and not just me.
Attached are 2 files:
1. TestGetNamedSecurityInfoA.cpp - test program
2. WINEDEBUG.log - part of a very large log file
--
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=50002
Bug ID: 50002
Summary: BlackBerry (Research in Motion) USB and Modem Drivers
installs files in the wrong place and fails to install
kernel drivers
Product: Wine
Version: 5.19
Hardware: x86-64
URL: https://swdownloads.blackberry.com/Downloads/contactFo
rmPreload.do?code=A8BAA56554F96369AB93E4F3BB068C22&dl=
F5937D3FABCEC4C05D26AB6F3FEEC891
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Created attachment 68409
--> https://bugs.winehq.org/attachment.cgi?id=68409
hack: set CommonFiles64Folder to the 32-bit common files dir
The installer is more than a bit of a mess. It seems to be trying to install
64-bit files into the 64-bit "Common Files" folder, and 32-bit files into the
32-bit folder. It has this <trimmed> in its Directory table:
Directory Directory_Parent DefaultDir
----------------------------------------------------------
TARGETDIR SourceDir
RESEARCH_IN_MOTION ProgramFilesFolder RESEAR~1|Research In Motion
BLACKBERRY RESEARCH_IN_MOTION BLACKB~1|BlackBerry
INSTALLDIR BLACKBERRY .
CommonFiles64Folder TARGETDIR .:Common64
CommonFilesFolder TARGETDIR .:Common
CommonFilesRIM.191... CommonFilesFolder RESEAR~1|Research In Motion
CommonFilesRIM.07D... CommonFiles64Folder RESEAR~1|Research In Motion
On Wine this behaves essentially as expected, and files get installed into
64-bit "Common Files". On Windows, however, for some reason, everything gets
installed into the 32-bit "Common Files" directory. This problem is compounded
when the program subsequently tries to install PnP drivers (from a 64-bit
custom action) using files from the 32-bit "Common Files" folder—working around
their own bug, I guess—and on Wine nothing gets installed.
I'm more than a little baffled as to how this could possibly break on Windows.
It'll probably take some more involved debugging.
Anyway, the attached patch works around the bug. The installer successfully
creates a couple of root PnP devices, but the driver subsequently fails to load
due to missing WDF. (In fact it needs quite a substantial chunk of WDF, which I
have partially implemented in my local tree).
--
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=40099
Bug ID: 40099
Summary: IFileOpenDialog with FOS_PICKFOLDERS option
Product: Wine
Version: 1.9.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nozomimasao(a)gmail.com
Distribution: ---
IFileOpenDialog sometimes returns a bad path if FOS_PICKFOLDERS option is
specified.
for example, if you selected C:\Windows folder *inside* Windows folder,
GetResult method returns C:\Windows\Windows.
Steps of the user:
1. Go inside C:\Windows by double-clicking Windows folder.
2. Click select button.
Then the path will be C:\Windows\Windows.
*The user can avoid this issue by below steps.
1. Select C:\Windows by clicking Windows folder *without* going inside it.
2. Click select button.
Then the path will be C:\Windows.
For your information, the code is like this;
IFileOpenDialog *fo = nullptr;
CoCreateInstance(CLSID_FileOpenDialog, NULL, CLSCTX_INPROC_SERVER,
IID_PPV_ARGS(&fo));
DWORD opt = 0;
fo->GetOptions(&opt);
fo->SetOptions(opt | FOS_PICKFOLDERS);
fo->Show(hWnd);
IShellItem *si = nullptr;
fo->GetResult(&si);
LPWSTR path = nullptr;
si->GetDisplayName(SIGDN_FILESYSPATH, &path);
--
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.