https://bugs.winehq.org/show_bug.cgi?id=54547
Bug ID: 54547
Summary: Hyperplanning software (index education) crashes all
the time for now
Product: Wine
Version: 8.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: olivier.corrio(a)gmail.com
Distribution: ---
Created attachment 74087
--> https://bugs.winehq.org/attachment.cgi?id=74087
It is the backtrace
The software works several minutes but often it crashes in less than 1mn. I can
use it but suddenly it crashes
--
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=54169
Bug ID: 54169
Summary: ntoskrnl.exe:ntoskrnl - test_pnp_devices() sometimes
fails on Windows and Linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntoskrnl.exe:ntoskrnl - test_pnp_devices() fails on Windows 10 with test
signing turned on:
ntoskrnl.c:1801: Test failed: failed to create device, error 0xe0000207
ntoskrnl.c:1805: Test failed: failed to create set hardware ID, error 0x57
ntoskrnl.c:1808: Test failed: failed to register device, error 0x57
ntoskrnl.c:1813: Test failed: got error 0x57
ntoskrnl.c:1817: Test failed: failed to install device, error 0xe000020b
ntoskrnl.c:1822: Test failed: got error 0x57
ntoskrnl.c:1823: Test failed: got flags 0x10
ntoskrnl.c:1824: Test failed: got type 0
ntoskrnl.c:1546: Test failed: failed to get interface, error 0x103
ntoskrnl.c:1547: Test failed: wrong class
{deadbeef-29ef-4538-a5fd-b69573a362c0}
ntoskrnl.c:1549: Test failed: got flags 0x1
ntoskrnl.c:1563: Test failed: got 0 bus arrival messages
ntoskrnl.c:1569: Test failed: failed to get interface, error 0x103
ntoskrnl.c:1570: Test failed: wrong class
{deadbeef-29ef-4538-a5fd-b69573a362c0}
ntoskrnl.c:1579: Test failed: got 0 bus arrival messages
ntoskrnl.c:1580: Test failed: got 0 bus removal messages
ntoskrnl.c:1585: Test failed: failed to get interface, error 0x103
ntoskrnl.c:1586: Test failed: wrong class
{deadbeef-29ef-4538-a5fd-b69573a362c0}
ntoskrnl.c:1588: Test failed: got flags 0x1
ntoskrnl.c:1605: Test failed: got 0 child arrival messages
ntoskrnl.c:1612: Test failed: failed to get device, error 0x103
ntoskrnl.c:1613: Test failed: wrong class
{4d36e97d-e325-11ce-bfc1-08002be10318}
ntoskrnl.c:1616: Test failed: failed to get device ID, error 0x57
ntoskrnl.c:1617: Test failed: got ID "\x08"
ntoskrnl.c:1621: Test failed: got error 0x57
ntoskrnl.c:1637: Test failed: got error 0x57
ntoskrnl.c:1639: Test failed: got flags 0x69f1b90b
ntoskrnl.c:1640: Test failed: got type 0
ntoskrnl.c:1645: Test failed: got error 0x57
ntoskrnl.c:1650: Test failed: got error 0x57
ntoskrnl.c:1654: Test failed: got error 0x57
ntoskrnl.c:1655: Test failed: got type 0
ntoskrnl.c:1656: Test failed: got size 0
ntoskrnl.c:1662: Test failed: got error 0x57
ntoskrnl.c:1663: Test failed: got type 0
ntoskrnl.c:1664: Test failed: got size 0
ntoskrnl.c:1669: Test failed: got error 0x57
ntoskrnl.c:1670: Test failed: got type 0
ntoskrnl.c:1671: Test failed: got size 0
ntoskrnl.c:1676: Test failed: got error 0x57
ntoskrnl.c:1688: Test failed: failed to open child: 0xc0000034
ntoskrnl.c:1692: Test failed: got error 6
ntoskrnl.c:1693: Test failed: got id -559038737
ntoskrnl.c:1694: Test failed: got size 0
ntoskrnl.c:1699: Test failed: failed to open child: 0xc0000034
ntoskrnl.c:1703: Test failed: got error 6
ntoskrnl.c:1711: Test failed: got 0 child arrival messages
ntoskrnl.c:1712: Test failed: got 0 child removal messages
ntoskrnl.c:1715: Test failed: got error 6
ntoskrnl.c:1718: Test failed: got 0xc0000034
ntoskrnl.c:1722: Test failed: got error 6
ntoskrnl.c:1728: Test failed: got 0 child arrival messages
ntoskrnl.c:1729: Test failed: got 0 child removal messages
ntoskrnl.c:1833: Test failed: failed to remove device, error 0x57
ntoskrnl.c:1836: Test failed: expected failure
ntoskrnl.c:1837: Test failed: got error 0
ntoskrnl.c:1857: Test failed: failed to open service, error 1060
ntoskrnl.c:291: Test failed: expected SERVICE_STOPPED, got 0
See https://test.winehq.org/data/patterns.html#ntoskrnl.exe:ntoskrnl
This happens a couple of times per month, mostly in the 64-bit w1064-tsign
tests.
However this also happened on:
* 2022-07-04 w7u-pt-PT despite it not having test signing turned on.
* 2022-10-24 master: this is the first known instance of these failures in
Wine.
* 2022-12-01 lastestmaster: these failures seem to have been systematic on this
Wine test configuration.
Unlike on Windows, none of the official Wine test configurations seem to be
having this failure.
--
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=54543
Bug ID: 54543
Summary: Avantree Leaf USB audio device does not play sound in
applications run via wine
Product: Wine
Version: 8.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: linux(a)bernd-steinhauser.de
Distribution: ---
I'm using an USB audio device called "Avantree Leaf" to pass audio via
Bluetooth to a receiver.
After this change in the kernel
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?…
applications run by wine via the pulseaudio output cannot initiate a stream on
the audio device and there is no sound. To test, I've used the audio player
foobar2000, but it's the same for other Windows applications. Native Linux
applications work without problems so far.
The latest Wine version that I tested is 8.1, but I haven't found any between
Wine versions in this regard.
It also does not work, if I select the usb device specifically in winecfg or in
foobar2000 itself. I do however get sound if I select another device, e.g. my
onboard sound card or the HDMI output, thus I know it is a problem with the usb
device only.
I usually use pipewire/wireplumber as an audio server with pipewire-pulse as a
Pulseaudio replacement, but the problem also exists if I'm using standard
Pulseaudio instead.
There are two possible workarounds that I can use to get sound from the device
when running Wine application:
1. Disable the usb audio latency management by loading the module with the
parameter lowlatency=0
2. Set clock.min-quantum 512 in pipewire/wireplumber, which I think also
increases the latency a bit
The maintainer of the kernel usb audio driver thinks that this an application
problem and that the kernel driver is working correctly. Therefore, I'm now
opening this bug report.
The corresponding bug report on the kernel side is, there I also have some
additional information available, not sure if I should replicate all of that
here:
https://bugzilla.kernel.org/show_bug.cgi?id=216909
Also, see this discussion on a pipewire issue, which was the first report I did
about this:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2739#note_1713023
--
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=53144
Bug ID: 53144
Summary: kernel32:debugger - test_kill_on_exit() sometimes
fails on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7:
debugger.c:2122: Test failed: NtSetInformationDebugObject failed c0000008
debugger.c:2144: Test failed: NtSetInformationDebugObject failed c0000008
https://test.winehq.org/data/patterns.html#kernel32:debugger
0xc0000008 == STATUS_INVALID_HANDLE
Sometimes only the second failure 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=54541
Bug ID: 54541
Summary: d3dx10_34:d3dx10 - test_get_image_info() gets
unexpected hr on Windows 21H1+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3dx10_34:d3dx10 - test_get_image_info() gets unexpected hr on Windows 21H1+:
d3dx10.c:2677: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2686: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
See https://test.winehq.org/data/patterns.html#d3dx10_34:d3dx10
For d3dx10_34 it's always the same two checks that fail (the other d3dx10_*
tests get similar failures in other places) and it always happens in the 32-bit
tests.
These failures are pretty rare too, only 5 instances in the past 6 months:
2022-09-07 on w1064 32-bit
2022-09-20 on w1064-tsign 32-bit
2022-11-29 on w10pro64 32-bit
2023-01-27 on fgtb-w10pro64 32-bit
2023-02-17 on w1064 32-bit
--
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=54513
Bug ID: 54513
Summary: wine: Call from 0000000170032138 to unimplemented
function CFGMGR32.dll.CM_MapCrToWin32Err, aborting
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sagar.ghuge(a)intel.com
Distribution: ---
When I run games through steam, I am running into an issue where I see the
following error and the game suddenly crashes.
wine: Call from 0000000170032138 to unimplemented function
CFGMGR32.dll.CM_MapCrToWin32Err, aborting
--
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=54467
Bug ID: 54467
Summary: Printing not possible after update to Wine 8.0
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: spooler
Assignee: wine-bugs(a)winehq.org
Reporter: n296869(a)rtrtr.com
Distribution: ---
Printing from windows-apps doesn't work anymore, after updating to wine-8.0. I
tried printing with PDFXChange-Viewer and PDFXChange-Editor. In both programs,
all cups printers are available. However, when trying to print, cups doesn't
receive any printjobs.
In the wine-directory the print-jobs seem to get spooled. There are files
created in:
$HOME/.wine/drive_c/windows/system32/spool/printers/
I can open them with ghostscript-viewer. I can find several old, unfinished
print-jobs in this folder.
I can't find any print-related error-messages. I looked in:
/var/log/cups/access_log
/var/log/syslog
/var/log/apport.log
...and the commandline, of course.
I also tried the command "aa-complain cupsd" on the commandline to enable
everything cups-related inside apparmor. It didn't help. BTW, I'm on ubuntu
18.04, 64-Bit, with cups 2.2.7. Registering/log-in on wine-forums isn't
possible for some reason and there are no similar reports for print-problems
with wine trying several search-enginges. This is a very annoying bug. I really
want to track it down.
--
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=54540
Bug ID: 54540
Summary: Wine Devel: needs to be updated error [MAC OS]
Product: Wine
Version: 5.7
Hardware: Other
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tanataba58(a)gmail.com
Created attachment 74081
--> https://bugs.winehq.org/attachment.cgi?id=74081
Error pop-up msg
Using Monterey on macOS, ver 12.5
Decided to download Wine Development 5.7
(https://dl.winehq.org/wine-builds/macosx/download.html), but after it's
finished downloading I keep getting an error that asks for Wine Devel to be
updated by the developer.
The "Learn more" leads to (https://support.apple.com/en-us/HT208436), so I
assume it has to do with the file being 32bit? I'm not tech savy so my
apologies. I made sure to download the "64bit support" that showed up on the
installer itself.
I'm unsure why it doesn't work though. Image is attached.
Any help is appreciated.
--
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=54512
Bug ID: 54512
Summary: Hardwar (Steam) crashes while loading the main menu
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
URL: https://store.steampowered.com/app/1500540/Hardwar/
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: a7fda2f8cb7e09b16fd7dc0ce2e40b5939757e78
Distribution: ArchLinux
Created attachment 74054
--> https://bugs.winehq.org/attachment.cgi?id=74054
terminal output
The game's launcher and the intro video work but the game crashes while loading
to the main menu.
Works in Wine-7.22 and the regression test points to
commit a7fda2f8cb7e09b16fd7dc0ce2e40b5939757e78
ntdll: Make realloc implementation more generic.
Either resizing a block in place, or reallocating through RtlHeap calls.
With the previous commit the game works properly.
Tested with wine-8.1-231-gdf5f6f66de8.
--
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=45057
Bug ID: 45057
Summary: "Wine Stable" is not optimized for your Mac.
Product: Wine
Version: unspecified
Hardware: Other
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sephirothfanatic(a)gmail.com
As of macOS High Sierra 10.13.4, Apple has issued a warning that 32 bit apps
are not going to work anymore and apps should be upgraded to 64 bit to
"increase compatibility"; siting this article:
https://support.apple.com/en-us/HT208436
--
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.