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.
https://bugs.winehq.org/show_bug.cgi?id=44094
Bug ID: 44094
Summary: need for speed carbon game is working but only audio
is coming , no display comes and looks like evry thing
hangs
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: srivastava.avichal(a)gmail.com
Distribution: ---
Created attachment 59816
--> https://bugs.winehq.org/attachment.cgi?id=59816
need for speed carbon game is working but only audio is coming , no display
comes and looks like evry thing hangs
my wine never work properly,
it never installs an application, nor updates nor unstalls
--
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=17277
Summary: Remote virtual memory allocation error
Product: Wine
Version: 1.1.13
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: loader
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gabmoa(a)yahoo.it
ZFlash is a win32 application used to simulate and edit part programs
for a cnc. The simulator part is achieved running a reduced version
of numerical control into a fixed memory map from 1 to 8 MB (the current
version is from 1-16 MB but it's the same principle). The numerical control
need to be mapped in this way because it uses fixed addresses.
The application runs in NT 4 SP6, 2000, XP and Vista MS OS but in wine
it doesn't work.
I have seen there is a problem in the memory mapping when I try to run the
application into wine so I've created a reduced example with the only
"incriminated" part. In the attached zip file there are 3 projects:
ZLoader, Z32Sim and Test.
The steps involved are the same of the complete win32 application.
ZLoader.exe create the process 'Test', suspended, and try to reserve memory
of 'Test' from 1 to 8 MB, then it resumes the process.
Test.exe is compiled with the linker flags
/base:"0x800000" /stack:0x800000,0x1000
so the big stack can not be inserted into the first 8MB and the
base of exe is changed from the default 4MB assigned by Visual Studio.
Z32Sim.dll is loaded into 'Test' and it have to map the memory (1-8MB).
To test it in the Debug directory we can execute ZLoader Test.exe
In wine Test fail when ZLoader try to resume it (I've seen that with winedbg)
with the following error:
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr
0x7ef9e617
Unfortunately it seems a not so easy task because with winedbg I can't
attach to Test process when it's suspended.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=20439
Summary: TroopMaster hangs on startup
Product: Wine
Version: 1.1.31
Platform: PC-x86-64
URL: http://www.troopmaster.com
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: al_turner(a)comcast.net
TroopMaster installs, but hangs on startup. Main window will not activate
(animation works, but no response to keyboard or mouse). Does not even get to
the DotNet download hangup as mentioned in bug 8997. More like 18801 but I
don't even get the popup window showing the attempt to connect to FTP.
As far as I can tell, the FTP attempt only happens if you activate the DOTNET
function (after installing the software). I have not been able to get to the
point of activating the DOTNET since I can't get it that far yet.
I followed the HOWTO from the AppDB that describes the install/kill/restart
process.
--
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=47150
Bug ID: 47150
Summary: [Overwatch] Game freezes when new menu music starts
playing
Product: Wine
Version: 4.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hewanci(a)gmail.com
Distribution: ---
Few days ago the new Lucio and Mercy League skins were introduced, and the menu
got a new music, and a showcase of aforementioned new skins.
Since then the game freezes as soon as the menu music starts playing. The music
(and later the regular menu ambient music) still plays, but the GUI is frozen
and unresponsive.
The only workaround I could find was to very quickly open one of the sub-pages
(eg. Play, Hero gallery, etc.) before the music starts. This way the music will
never play, and then I can go back to the menu and everything works fine,
including the showcase of the new skins playing in the background.
Arch Linux, fully updated
Wine Staging 4.7
--
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=48054
Bug ID: 48054
Summary: gdi32:bitmap fails on Windows XP and 2003
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:bitmap started failing on Windows XP and 2003 right after the winehq.org
upgrade:
bitmap.c:1015: Test failed: StretchDIBits failed for 32/62/0/0
bitmap.c:1023: Test failed: GetDIBits failed for 32/62/0/0
bitmap.c:1052: Test failed: StretchDIBits failed for 32/62/0/0
(repeated 12 times)
See http://winetest.dolphin/data/tests/gdi32:bitmap.html
See also the attached screenshot showing the failures did start on Sept 09.
And this wine-devel thread:
https://www.winehq.org/pipermail/wine-devel/2019-October/152082.html
The failures are systematic and happen on all machines running one of these two
Windows versions. What's strange is that the TestBot's wxppro and w2003std VMs
have not been modified in this timeframe and neither has the gdi32:bitmap test.
In fact this appears related to the compiler which would explain why the
failure started when winehq.org (which builds the official WineTest binaries)
was upgraded to Debian 10.
Specifically, letting wtbbuild, which still runs Debian 9.9
(i686-w64-mingw32-gcc 6.3.0 20170516), compile the test binaries results in no
failure:
https://testbot.winehq.org/JobDetails.pl?Key=59354
But using a binary compiled with i686-w64-mingw32-gcc 8.3-win32 20190406 (in
this case on my development machine) produces the 36 failures:
https://testbot.winehq.org/JobDetails.pl?Key=59355
Either that or it's quite possibly a result of the new everything-as-PE vs. the
old cross-compilation approach still used by wtbbuild.
--
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=28083
Summary: Agenda Circling Forth GPU particle demo:bunch of fixme
and errors
Product: Wine
Version: 1.3.26
Platform: x86
URL: http://downloads.guru3d.com/Agenda-Circling-Forth-GPU-
particle-demo-download-2591.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: 810d4rk(a)gmail.com
Created an attachment (id=35956)
--> (http://bugs.winehq.org/attachment.cgi?id=35956)
terminal
It is not possible to see the techdemo as intended due to bugs.
--
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.