https://bugs.winehq.org/show_bug.cgi?id=54065
Bug ID: 54065
Summary: Windower 4 with FFXI Online has no keyboard input
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: reaper2021(a)protonmail.com
Distribution: ---
Created attachment 73616
--> https://bugs.winehq.org/attachment.cgi?id=73616
error log
Keyboard input in FFXI with Windower 4 has been broken for a long time. It
fails in 7.20, and all the way down to 5.0rc2 or earlier (I stopped testing
there).
Keyboard input works in wine-staging-5-0rc5, and no longer works in
wine-staging-5-0-rc6.
My installation for which I posted the log uses dxvk and dgVoodoo, but the
problem also occurs without that.
Steps to reproduce:
1. make a 32 bit prefix, windows version seems noncritical (7 or 10).
2. install official FFXI distribution from
http://www.playonline.com/ff11us/download/media/install_win.html
(install hangs for a seemingly long time at some step, disk space check if I
recall, just wait)
3. winetricks dotnet462 gdiplus (without dotnet, windower will not work.
Gdiplus just makes the fonts in the windower console look nicer, it's not
absolutely required for reproduction.)
4. install windower 4.3 from https://www.windower.net/ , to
$WINEPREFIX/drive_c/windower4.3/
5. wine $WINEPREFIX/drive_c/windower4.3/Windower.exe
At this step, you'll need an FFXI subscription and character to log in and get
to the point where you see that the keyboard doesn't work.
--
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=8532
temp82(a)luukku.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |temp82(a)luukku.com
--- Comment #14 from temp82(a)luukku.com ---
still valid as wine 8.6.
--
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=54851
Bug ID: 54851
Summary: comctl32:tooltips - test_TTN_SHOW() sometimes gets
extra or missing WM_NOTIFY messages in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
comctl32:tooltips - test_TTN_SHOW() sometimes gets extra or missing WM_NOTIFY
messages in Wine.
For instance:
tooltips.c:1218: Test failed: TTN_SHOW parent seq: the msg sequence is not
complete: expected 004e - actual 0000
tooltips.c:1218: Failed sequence TTN_SHOW parent seq:
tooltips.c:1218: 0: expected: msg 004e - actual: nothing
or
tooltips.c:1218: Test failed: TTN_SHOW parent seq: the msg sequence is not
complete: expected 0000 - actual 004e
tooltips.c:1218: Failed sequence TTN_SHOW parent seq:
tooltips.c:1218: 0: expected: 004e - actual: 004e wp 1234abcd lp 0072eec0
tooltips.c:1218: 1: expected: nothing - actual: 004e wp 1234abcd lp 0072ef20
See https://test.winehq.org/data/patterns.html#comctl32:tooltips
In are cases both issues happen or the same issue happens twice; once before
the load_v6_module() call, and once after.
--
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=54850
Bug ID: 54850
Summary: comctl32:tooltips - test_customdraw() sometimes fails
to get the current tool on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
comctl32:tooltips - test_customdraw() sometimes fails to get the current tool
on Windows
tooltips.c:252: Test failed: 3: Failed to get current tool 0.
tooltips.c:259: Test failed: 3: Unexpected hwnd CCCCCCCCCCCCCCCC.
tooltips.c:260: Test failed: 3: Unexpected hinst CCCCCCCCCCCCCCCC.
tooltips.c:261: Test failed: 3: Unexpected uId cccccccccccccccc.
tooltips.c:262: Test failed: 3: Unexpected lParam cccccccccccccccc.
See https://test.winehq.org/data/patterns.html#comctl32:tooltips
This can happen either before or after the load_v6_module() call, and in any of
the for loop iterations, though normally only one of them per run.
--
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=52987
Bug ID: 52987
Summary: comctl32:tooltips - test_customdraw() fails
systematically on some Windows 10 machines
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
comctl32:tooltips - test_customdraw() fails systematically on some Windows
machines:
tooltips.c:251: Test failed: 0: Failed to get current tool 0.
tooltips.c:258: Test failed: 0: Unexpected hwnd CCCCCCCCCCCCCCCC.
tooltips.c:259: Test failed: 0: Unexpected hinst CCCCCCCCCCCCCCCC.
tooltips.c:260: Test failed: 0: Unexpected uId cccccccccccccccc.
tooltips.c:261: Test failed: 0: Unexpected lParam cccccccccccccccc.
tooltips.c:251: Test failed: 1: Failed to get current tool 0.
tooltips.c:258: Test failed: 1: Unexpected hwnd CCCCCCCCCCCCCCCC.
tooltips.c:259: Test failed: 1: Unexpected hinst CCCCCCCCCCCCCCCC.
tooltips.c:260: Test failed: 1: Unexpected uId cccccccccccccccc.
tooltips.c:261: Test failed: 1: Unexpected lParam cccccccccccccccc.
[... all 6 iterations fail ...]
https://test.winehq.org/data/patterns.html#comctl32:tooltips
Also this impacts both test_customdraw() calls: the one after
test_create_tooltip(FALSE) and the one after test_create_tooltip(TRUE) though
the latter is more random. When the latter fails there is an extra couple of
failures in test_TTN_SHOW():
tooltips.c:261: Test failed: 5: Unexpected lParam cccccccccccccccc.
tooltips.c:1216: Test failed: TTN_SHOW parent seq: the msg sequence is not
complete: expected 004e - actual 0000
tooltips.c:1216: Failed sequence TTN_SHOW parent seq:
tooltips.c:1216: 0: expected: msg 004e - actual: nothing
v6util.h:92: created cc6.manifest
tooltips.c:251: Test failed: 0: Failed to get current tool 0.
[...]
tooltips.c:1216: Test failed: TTN_SHOW parent seq: the msg sequence is not
complete: expected 004e - actual 0000
However the failure pattern is strange:
* The failures mostly happen on the cw-gtx560 and cw-rx460 machines. But
w1064v1709-64 has the same failures so it's not a real hardware vs. VM issue.
* The failures happen on Windows 10 1709, 21h1 and 21h2, but not on 1507, 1607,
1809 or 2004. 1909 had failures on March 21 and 22 but not in the month since
then. So it does not really seem related to the Windows version.
* cw-gtx560-21H1 and cw-rx460-21H1 never had failures in the 32-bit tests but
the failures happen in 32-bit on cw-gtx560-1709 and cw-rx460-1709. So it's not
a bitness issue and it should not be a machine configuration issue either.
The failure on line 251 indicates that there is no tooltip at all. Maybe there
is a window that has the focus and prevented the tooltip from opening? (that
window if any is not visible in the final screenshot)
If it is a focus issue, skipping when the windows does not have the focus could
avoid the failures.
--
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
--- Comment #25 from temp82(a)luukku.com ---
still an issue. wine 8.6.
--
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=30826
Bug #: 30826
Summary: Gigasoft's ProEssentials demo crashes on startup
Product: Wine
Version: 1.5.5
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Classification: Unclassified
To reproduce,
wget http://www.gigasoft.com/PE7-Pro-Setup.exe
wine PE7-Pro-Setup.exe
cd .wine/drive_c/ProEssentials7/DEMO
wine PEDemo.exe
Click the popup window to make it go away.
Unhandled exception: page fault on read access to 0x5050ff98 in 32-bit code
(0x7ed36a26).
Or, sometimes:
Unhandled exception: page fault on read access to 0x00000048 in 32-bit code
(0x7ed2ea26).
The backtrace seems the same either way:
Backtrace:
=>0 get_log_fontW+0x16(font=0x720041, graphics=0x154780, lf=0x32e92c)
[dlls/gdiplus/font.c:486]
1 get_font_hfont+0x10e(graphics=0x154780, font=0x720041, hfont=0x32eb58)
[dlls/gdiplus/graphics.c:2139]
2 GdipDrawString+0x2c1(graphics=0x154780, string="Bollinger Upper",
length=0xf, font=0x720041, rect=0x32eba8, format=0x149e28, brush=0x154b68)
[dlls/gdiplus/graphics.c:5210]
486 lf->lfHeight = -em_size_to_pixel(font->emSize, font->unit,
font->family->dpi);
Installing corefonts doesn't help.
--
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=54813
Bug ID: 54813
Summary: Installation League of Legends crash
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: totinous.31(a)hotmail.fr
Distribution: ---
Created attachment 74304
--> https://bugs.winehq.org/attachment.cgi?id=74304
Program Error Details
Hello,
I'm not fluent english, i'll try my best to explain.
I tried to install and launch with the "snap method" (snap install
leagueoflegends --edge --devmode) the game League of Legends.
The first part is good : preparation of the environement works well, the
installation as well but when the "Riot Client Main" opens, it stays black and
a "Program Error" appears.
i'm using wine8.5 staging.
You can find the Program error details in the attachment.
let me know if any further information is required to resolve that issue
--
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=54842
Bug ID: 54842
Summary: Black Souls 2 (Rpg Maker Vx Ace Obscure Japanese Rpg)
crashes when trying to access mp3dmod and qasf
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: magmatuxedo(a)gmail.com
Distribution: ---
Created attachment 74345
--> https://bugs.winehq.org/attachment.cgi?id=74345
The above contains the error log as well as the terminal output right from when
the game is started
The game blacksouls II is as stated above an obscure rpg maker vx ace game
The game works fine when the it is started and the first boss is defeated
however going into the town and coming into contact with an enemy to commence
battle crashes the game
The above is also the way to reproduce the crash
The necessary information is in the attachment
wine version is 8.5 development
--
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=54843
Bug ID: 54843
Summary: Missing dependencies for speech recognition
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: besentv(a)gmail.com
Distribution: ---
The Testbot is missing the Linux side deps for speech recognition, namely
libvosk. Currently, this is blocked by Vosk not being packaged for APT.
I opened an issue on their repo
https://github.com/alphacep/vosk-api/issues/1308
This blocks https://gitlab.winehq.org/wine/wine/-/merge_requests/2091
Alternatively, libvosk could be installed as a pip package.
--
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=54013
Bug ID: 54013
Summary: Cannot install Trimble Sketchup Pro 2022 at all
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gdpo22(a)orange.fr
Distribution: ---
Created attachment 73589
--> https://bugs.winehq.org/attachment.cgi?id=73589
Trying to install sketchup without sed solution
After downloading the sketchup pro 2022 trial, the sketchup installer displayed
a lot of error windows "Invalid descriptor" with an "ok" button. After 6 or 7
click on "ok", the install terminates with a final window error of trimble
saying that the installation cannot complete. (see attachement)
The same with 7.0 wine stable version.
Then I succeeded to install by applying a dirty solution I have seen on a
forum:
sed 's/GetFinalPathNameByHandleW/QetFinalPathNameByHandleW/'
SketchUpPro-2022-0-354-126.exe > hacked_installer.exe
But when I try to click on 'connexion' button from welcome screen, nothing
happens.
--
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=48734
Bug ID: 48734
Summary: How to Survive crashes when starting a new game
Product: Wine
Version: 5.0-rc1
Hardware: x86
URL: https://store.steampowered.com/app/250400/How_to_Survi
ve/
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 94822bae5fed8a3bbda00adb4e79652cd9374309
Distribution: ---
Created attachment 66616
--> https://bugs.winehq.org/attachment.cgi?id=66616
terminal output
The game was started in windowed mode to work around bug #48732.
When I start a new single-player game from the menu, Wine crashes when
attempting to play the first video. I think it's 'prologue.avi' which should be
playing at this point.
Cutscenes didn't work properly before the regression, only a black screen was
shown and pressing <Space> or <Esc> made it possible to skip the video. Now
Wine crashes.
The crash was introduced by
commit 94822bae5fed8a3bbda00adb4e79652cd9374309
quartz/vmr9: Create the rendering window when the filter is created.
To reproduce the problem select <Local Game> in the main menu, then <Story
Mode>, <1 Player>, choose a character and difficulty level. After a short
loading animation Wine crashes.
Tested in wine-5.3-181-geb63713f60.
--
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=54837
Bug ID: 54837
Summary: Error when launching URU Live again via their app
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mbradfor42(a)yahoo.com
Distribution: ---
Created attachment 74340
--> https://bugs.winehq.org/attachment.cgi?id=74340
the error when luanching app
I hope I submitted this correctly.
--
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=51134
Bug ID: 51134
Summary: Support redirecting GetOpenFileName and
GetSaveFileName through
org.freedesktop.portal.FileChooser
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: from_wine_bugzilla(a)ssokolow.com
Distribution: ---
While not all options in the OPENFILENAME structure can be supported via the
org.freedesktop.portal.FileChooser interface, providing the option to redirect
an application's request for a common Open/Save dialog through the XDG chooser
system would have two beneficial effects on non-OSX POSIX systems:
1. Better integration, since the application run under Wine would use the
native desktop file pickers, complete with the user's Places sidebar bookmarks
and any other customizations they've enacted.
2. More practical security, since Wine could then be run in a filesystem
sandbox, with the portal host mounting files/directories into the sandboxed
environment on demand.
I'd suggest a three-state option exposed through winecfg's Desktop Integration:
1. Opportunistically (Qt's approach to integrating support for XDG portals into
QFileDialog provides precedent for making this the default. Uses the
portal-based file chooser unless an application requests a combination of
OPENFILENAME settings that cannot be represented by the portal API.)
2. Forced (An option for power users to set on a per-application basis to
intentionally sacrifice the application's customizations in favour of better
integration with the understanding that things may break.)
3. Never (An option for users who prefer consistency between their Windows
applications over consistency with the rest of their desktop or have deleted
the Z: mapping and configured their Wine prefix around the idea of only working
with drive letters.)
These high-level preferences could also apply equally well to any other
platform's native file chooser, should integration with it be implemented.
The D-Bus API in question is documented at
https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.fre…
While it is outside the scope of this feature request, it may also be possible
to use the TrashFile() method of this API to integrate with the host desktop's
Trash.
--
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=54463
Bug ID: 54463
Summary: wbemprox: wrong version value is returned from
win32_operatingsystem on win10 (regression)
Product: Wine
Version: 8.1
Hardware: x86-64
URL: https://github.com/PowerShell/PowerShell/releases/down
load/v7.0.3/PowerShell-7.0.3-win-x64.msi
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: wmi&wbemprox
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
CC: hans(a)meelstraat.net
Distribution: Debian
Following powershell script returns wrong version on win10 (winetricks dotnet48
is required):
$searcher = [wmisearcher]'Select version From win32_operatingsystem'
$searcher.scope.path = "\\.\root\cimv2"
$searcher.get()
Result:
__GENUS : 2
__CLASS : Win32_OperatingSystem
__RELPATH :
__PROPERTY_COUNT : 1
__DERIVATION : {}
__SERVER :
__NAMESPACE :
__PATH :
Version : 6.3.18362
PSComputerName :
In wine 8.0 it reports correctly:
__GENUS : 2
__CLASS : Win32_OperatingSystem
__RELPATH :
__PROPERTY_COUNT : 1
__DERIVATION : {}
__SERVER :
__NAMESPACE :
__PATH :
Version : 10.0.18362
PSComputerName :
This bug results in Chocolateley downloading tons off MB's off updates because
it believes version is <win10.
--
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=54781
Bug ID: 54781
Summary: Wine fails to update existed prefix
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: alexandros.frantzis(a)collabora.com
Regression SHA1: 4232312dffe1cd115aa6bfd755f5b7c6a403e3fc
Distribution: ---
Process stucks with '0074:fixme:xrandr:xrandr10_get_current_mode Non-primary
adapters are unsupported.'
Creating a new prefix doesn't help much. It works for the first launch with
configuration window; second launch brings xrandr again.
--
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=54106
Bug ID: 54106
Summary: taskschd:scheduler - test_GetTask() fails on Windows 7
when it has insufficient privileges
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: taskschd
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
test_GetTask() fails on Windows 7 when it has insufficient privileges:
scheduler.c:802: Test failed: DeleteTask error 0x80070005
scheduler.c:798: Test failed: 1: expected 0, got 0x800700b7
scheduler.c:798: Test failed: 2: expected 0x80070002, got 0
scheduler.c:802: Test failed: DeleteTask error 0x80070005
scheduler.c:802: Test failed: DeleteTask error 0x80070005
scheduler.c:814: Test failed: RegisterTask error 0x800700b7
scheduler.c:960: Test failed: DeleteTask error 0x80070005
scheduler.c:962: Test failed: DeleteTask error 0x80070005
scheduler.c:965: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070005
scheduler.c:993: Test failed: DeleteFolder error 0x80070091
This can be seen on the w7u_adm VM.
When run as part of the full WineTest run this test crashes in
test_FolderCollection() which prevents seeing this failure in the nightly
WineTest runs.
See https://test.winehq.org/data/patterns.html#taskschd:scheduler
But this set of failures is impacting merge requests such as MR!1732 and
MR!1736.
--
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=54594
Bug ID: 54594
Summary: dinput:device8 - test_dik_codes() sometimes gets
timeouts on the GitLab CI
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
dinput:device8 - test_dik_codes() sometimes gets timeouts on the GitLab CI.
MR2265 & MR2288:
device8.c:2182: Test failed: 0x800: lang 0x409: key 0x51, dik 0x10:
WaitForSingleObject returned 0x102
MR1714 & MR2185:
device8.c:2182: Test failed: 0x800: lang 0x409: key 0x52, dik 0x13:
WaitForSingleObject returned 0x102
MR2133:
device8.c:2182: Test failed: 0x800: lang 0x409: key 0x54, dik 0x14:
WaitForSingleObject returned 0x102
MR2254:
device8.c:2182: Test failed: 0x800: lang 0x409: key 0x59, dik 0x15:
WaitForSingleObject returned 0x102
The oldest known instance happened on 2023-02-16 (MR2185) so this issue may be
pretty recent.
This issue never happened in the nightly WineTest runs. It's possible it only
happens when the load on the machine running the tests is too high. That would
make sense given that the timeouts from from a WaitForSingleObject() call with
a 100 ms timeout.
One option would be to simply increase the timeout. Yet that timeout seemed
sufficient until mid February. So why is it no longer the case?
--
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=54109
Bug ID: 54109
Summary: schedsvc:rpcapi causes taskschd:scheduler to crash on
w7u_adm
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: taskschd
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
When run on its own taskschd:scheduler fails on w7u_adm because of its
insufficient privileges (see bug 54106).
But if schedsvc:rpcapi is run before, taskschd:scheduler crashes in
test_FolderCollection() instead:
scheduler.c:349: Test failed: DeleteFolder error 0x80070091
scheduler.c:351: Test failed: DeleteFolder error 0x80070091
scheduler.c:354: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070091
scheduler.c:450: Test failed: CreateFolder error 0x800700b7
scheduler.c:450: this is the last test seen before the exception
0a78:scheduler: unhandled exception c0000005 at 00403B53
See https://test.winehq.org/data/patterns.html#taskschd:scheduler
Where:
0x80070091 == HRESULT_FROM_WIN32(ERROR_DIR_NOT_EMPTY)
0x800700b7 == HRESULT_FROM_WIN32(ERROR_ALREADY_EXISTS)
This crash happens before the failures described in bug 54106 which explains
why taskschd:scheduler fails one way for regular TestBot jobs (such as when
testing merge requests) and another in the nightly WineTest runs.
--
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=49332
Bug ID: 49332
Summary: CounterPath Bria Solo crashes after login dialog
Product: Wine
Version: 5.10
Hardware: x86
URL: https://www.counterpath.com/bria-solo/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: whydoubt(a)gmail.com
Distribution: Fedora
After getting past the login dialog, the program crashes almost immediately.
It does pop up a dialog that offers to submit logs to the developers. I have
not found any logs produced by the software that provide insight into what
caused the crash.
However, after turning on several debug channels in wine, I found this right
before things go sideways:
0024:trace:nls:FormatMessageW
(0x1300,00000000,0xe000020e,0x400,0031E634,1,00000000)
I tracked down the 0xe000020e error code in this case as coming from
SetupDiDestroyDeviceInfoList,
even though the call had completed successfully.
--
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=54774
Bug ID: 54774
Summary: dinput:device8 - test_overlapped_format() sometimes
gets a timeout in Wine (GitLab CI)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
dinput:device8 - test_overlapped_format() sometimes gets a timeout in Wine:
device8.c:432: Test failed: 0x800: WaitForSingleObject returned 0x102
device8.c:437: Test failed: 0x800: got count 0
device8.c:452: Test failed: 0x800: WaitForSingleObject returned 0x102
device8.c:457: Test failed: 0x800: got count 0
See https://test.winehq.org/data/patterns.html#dinput:device8
The oldest known instance happened on 2023-03-03 and there has been about 1
instance per week since, all on the GitLab CI:
* 2023-03-03 gitlab-debian-32
* 2023-03-23 gitlab-debian-32
* 2023-03-29 MR2524 test-linux-32
* 2023-04-03 MR2562 test-linux-32
* MR2509 but the GitLab job is nowhere to be found anymore!
--
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=54772
Bug ID: 54772
Summary: LDAP Explorer (LEX) fails to connect without SSL
Product: Wine
Version: 8.5
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wldap32
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 74265
--> https://bugs.winehq.org/attachment.cgi?id=74265
WINEDEBUG=+wldap32
Steps to reproduce:
1. Run `winetricks dotnet452`
2. Run `wine LEX.msi`
3. Run `docker run --detach -p389:389 osixia/openldap`
4. Run `wine 'C:\Program Files (x86)\CerroTorre\LEX\LEX.exe'`
5. Wait for the splash screen to close, or move the "LDAP Connections" window
out from under it
6. Enter "localhost" for the server
6. Check "Anonymous bind"
7. Click "Fetch"
At this point, a "Connect Error" dialog appears that says "The feature is not
supported."
The problem is that a callback function is registered to check the server's TLS
certificate, but Wine incorrectly errors out when there is no certificate.
$ sha256sum LEX.msi
68810d827de3f90c0223fcb18a66dde49aee189789b37dd4cdeebe013fa402be
--
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=53269
Bug ID: 53269
Summary: uiautomationcore:uiautomation fails on Windows 10 1909
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: uiautomationcore
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
uiautomationcore:uiautomation fails on Windows 10 1909:
uiautomation.c:355: Test failed: unexpected call Accessible_get_accRole
uiautomation.c:379: Test failed: unexpected call Accessible_get_accState
uiautomation.c:256: Test failed: unexpected call Accessible_get_accChildCount
uiautomation.c:254: Test failed: unexpected call Accessible2_get_accChildCount
uiautomation.c:474: Test failed: unexpected call Accessible_accLocation
uiautomation.c:318: Test failed: unexpected call Accessible_get_accName
uiautomation.c:164: Test failed: unexpected call Accessible2_QI_IAccIdentity
uiautomation.c:234: Test failed: unexpected call Accessible2_get_accParent
uiautomation.c:316: Test failed: unexpected call Accessible2_get_accName
uiautomation.c:1478: Test failed: elprov != NULL, elprov 00000000007B2CA0
uiautomation.c:1486: Test failed: elprov != NULL, elprov 00000000007B2FB0
uiautomation.c:1524: Test failed: expected Accessible_get_uniqueID
uiautomation.c:355: Test failed: unexpected call Accessible_get_accRole
uiautomation.c:379: Test failed: unexpected call Accessible_get_accState
uiautomation.c:256: Test failed: unexpected call Accessible_get_accChildCount
uiautomation.c:254: Test failed: unexpected call Accessible2_get_accChildCount
uiautomation.c:474: Test failed: unexpected call Accessible_accLocation
uiautomation.c:318: Test failed: unexpected call Accessible_get_accName
uiautomation.c:164: Test failed: unexpected call Accessible2_QI_IAccIdentity
uiautomation.c:234: Test failed: unexpected call Accessible2_get_accParent
uiautomation.c:316: Test failed: unexpected call Accessible2_get_accName
uiautomation.c:1558: Test failed: expected Accessible_get_uniqueID
uiautomation.c:1559: Test failed: expected Accessible2_get_uniqueID
uiautomation.c:1586: Test failed: elprov != NULL, elprov 00000000007B2D80
uiautomation.c:1589: Test failed: expected Accessible_get_uniqueID
uiautomation.c:1590: Test failed: expected Accessible2_get_uniqueID
uiautomation.c:1596: Test failed: elprov != NULL, elprov 00000000007B2ED0
https://test.winehq.org/data/patterns.html#uiautomationcore:uiautomation
These failures are systematic on Windows 10 1909 and started on 2022-06-15.
--
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=32490
Bug #: 32490
Summary: Graphical issues in Inquisitor (red squares painted on
the screen)
Product: Wine
Version: 1.5.19
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Classification: Unclassified
Created attachment 42861
--> http://bugs.winehq.org/attachment.cgi?id=42861
terminal output
Inquisitor is an RPG released in 2012. I guess it uses DirectX8 (or DX7?)
because only +d3d8 produces output, not +d3d9.
Red squares are present on the screen while in the menus as well as in the main
game. This makes the game unplayable. I tested this bug with a Nvidia gfx card:
both the open source Nouveau and the binary drivers show the same problem.
Wine 1.2.3, 1.4.1, 1.5.19 etc. have the reported problem.
No demo available. Let me know if you need a debug log.
--
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.