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=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=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=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=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.
http://bugs.winehq.org/show_bug.cgi?id=28586
Bug #: 28586
Summary: Team Fortress Arcade and Pixel Force: Left 4 Dead have
no sound
Product: Wine
Version: 1.3.29
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dmusic
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sagman.staredsi(a)gmail.com
Classification: Unclassified
Created attachment 36730
--> http://bugs.winehq.org/attachment.cgi?id=36730
Full Team Fortress Arcade log
Team Fortress Arcade and Pixel Force: Left 4 Dead have no sound due a
unimplemented function of directmusic:
fixme:dmfile:IDirectMusicSegment8Impl_IPersistStream_Load : WAVE form (loading
to be checked)
fixme:dswave:IDirectMusicWaveImpl_IPersistStream_Load (0x5f148e8, 0x5f148b8):
loading not implemented yet (only descriptor is loaded)
This two lines are a message that wine repeat often in the output and inform
this.
--
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=53128
Bug ID: 53128
Summary: Without elevated privileges schedsvc:rpcapi fails on
Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Without elevated privileges schedsvc:rpcapi fails on Windows 7:
rpcapi.c:169: Test failed: expected S_OK, got 0x80070005
rpcapi.c:164: Test failed: 1: expected 0, got 0x800700b7
rpcapi.c:164: Test failed: 2: expected 0x80070002, got 0
rpcapi.c:169: Test failed: expected S_OK, got 0x80070005
rpcapi.c:169: Test failed: expected S_OK, got 0x80070005
rpcapi.c:232: Test failed: expected S_OK, got 0x80070005
rpcapi.c:234: Test failed: expected S_OK, got 0x80070091
rpcapi.c:236: Test failed: expected S_OK, got 0x80070091
rpcapi.c:242: Test failed: expected ERROR_FILE_NOT_FOUND, got 0
rpcapi.c:243: Test failed: expected 0, got 1
rpcapi.c:244: Test failed: expected 0, got 1
rpcapi.c:245: Test failed: expected NULL, got 002ED3F0
rpcapi.c:248: Test failed: expected S_OK, got 0x800700b7
rpcapi.c:255: Test failed: expected 0, got 1
rpcapi.c:256: Test failed: expected 0, got 1
rpcapi.c:257: Test failed: expected NULL, got 002EE9F8
rpcapi.c:260: Test failed: expected S_OK, got 0x800700b7
rpcapi.c:346: Test failed: expected S_OK, got 0x80070091
rpcapi.c:354: Test failed: expected ERROR_FILE_NOT_FOUND, got 0
rpcapi.c:355: Test failed: expected 0, got 1
rpcapi.c:356: Test failed: expected 0, got 1
rpcapi.c:357: Test failed: expected NULL, got 002EEA18
rpcapi.c:362: Test failed: expected S_OK, got 0x800700b7
rpcapi.c:363: Test failed: expected \Wine\Task1, task actual path (null)
rpcapi.c:508: Test failed: expected S_OK, got 0x80070005
rpcapi.c:510: Test failed: expected S_OK, got 0x80070005
rpcapi.c:512: Test failed: expected S_OK, got 0x80070005
rpcapi.c:514: Test failed: expected S_OK, got 0x80070091
https://test.winehq.org/data/patterns.html#schedsvc:rpcapi
In particular the value at the end of the "expected NULL" failure changes with
every run so this failures always looks like it is new :-(
This happens systematically on the w7u-adm TestBot VM. Interestingly it does
not happen on more recent Windows versions that also run the tests without
elevated privileges such as w8adm and w1064-adm. Maybe Microsoft realized they
were too strict with the elevated privileges checks.
--
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.