http://bugs.winehq.org/show_bug.cgi?id=58424
Bug ID: 58424
Summary: WakeMeOnLan: Doesn't scan IP addresses
Product: Wine
Version: 10.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: iphlpapi
Assignee: wine-bugs(a)winehq.org
Reporter: claytmp+foj0w(a)gmail.com
Distribution: ---
Created attachment 78845
--> http://bugs.winehq.org/attachment.cgi?id=78845
Contains screenshots for comparison and logs from terminal
When scanning the IP addresses (Click on Play button), it doesn't find anything
as if nothing are found. I did double check if the IP range are correct
--
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=53407
Bug ID: 53407
Summary: Hogia Hemekonomi Missing date picker widget
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)jonass.user.lysator.liu.se
Distribution: ---
Created attachment 72799
--> https://bugs.winehq.org/attachment.cgi?id=72799
How the calendar widget looks when run on Windows XP.
When showing transactions there is a date entry field where the user can enter
a date. Or press "enter" to get a date picker widget. The widget seems to be
missing in Wine.
To reproduce:
- Run the software like "wine Hemeko.exe"
- There will be dialogue asking about number format, click Yes.
- On first run you get an intro (or error see Bug 53384). If error, just
dismiss. If intro, press "Återgå till Hemekonomi" to dismiss.
- Click "Arkiv" and "Ny" to create a new database to work with. When asked
"Ange namnet på den nya databasen" enter something like "foo.mdb" and click OK.
- Click "Fortsätt med Hemekonomi" to dismiss setup wizard.
- Press CTRL-K or click on icon Kontoutdrag.
- Click OK.
- Use mouse to set focus on entry field in lower right corner called "Fr o m"
- Press enter.
- See Program Error.
On subsequent runs click Arkiv/Öppna instead to use the existing foo.mdb
database.
--
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=58261
Bug ID: 58261
Summary: Ys Origin: videos playing upside down
Product: Wine
Version: unspecified
Hardware: x86-64
URL: https://store.steampowered.com/app/207350/Ys_Origin/
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: 2f180106471a41fa3d95f21919b87b94d8e13e63
Distribution: ---
Created attachment 78600
--> http://bugs.winehq.org/attachment.cgi?id=78600
terminal output
Intro and in-game videos are playing upside down in Ys:Origin.
Tested with the Steam and GOG.com versions. Demo is available on Steam but it
is not affected (the demo uses different video format for videos).
This is after
commit 2f180106471a41fa3d95f21919b87b94d8e13e63
amstream: Implement the custom ddraw stream allocator.
The allocator has a lot of custom behaviour that is very visible in how it
interacts with Update().
Naturally this has the benefit of writing directly into the mapped
surfaces.
The gstreamer errors in my log were present before that commit too.
wine-10.8-103-g8f91df4c4e4
--
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=58412
Bug ID: 58412
Summary: winedbg recursively forks until the memory is
exhausted
Product: Wine
Version: 10.0-rc2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
This bug is just to document my findings from this Debian Bug:
https://bugs.debian.org/1104317
It was just observed with a 32-bit Trixie/testing system.
It looks like for some reason the executable image gets relocated and cannot
be placed at its desired base address.
Unfortunately the entry point gets not relocated.
With a rebuilt package including these patches winecfg could startup normally.
https://gitlab.winehq.org/wine/wine/-/commit/398da92511b51d3ee4ce7c77bfe6d7…https://gitlab.winehq.org/wine/wine/-/commit/5c45391e9f79854915c50a15054f2d…
--
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=58364
Bug ID: 58364
Summary: Major change from 10.9 to 10.10 with Pegasus Email
Program
Product: Wine
Version: 10.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikes(a)kuentos.guam.net
Distribution: ---
Created attachment 78762
--> http://bugs.winehq.org/attachment.cgi?id=78762
Image after 10.10 installed? Bad
Has worked fine with version of 10.9 and before, but now 10.10 comes with an
unusable screen.
Adding to screen shots with 10.9 and 10.10.
Works fine after downgrade back to 10.9?
--
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=42882
Bug ID: 42882
Summary: rs232 port access no working with ubuntu 17.10 worked
fine with previous versions of ubuntu
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: arcadeshopper(a)gmail.com
Distribution: ---
I am able to connect to the serial port via applications in wine but there is
never any data received.
I can communicate outside of wine without issue using minicom.
I am using a ftdi usb to serial adapter that worked fine in previous versions
of ubuntu. I am having this problems with all relases of wine I have tried
including the default ubuntu package and 2.4 from the PPA
--
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=58422
Bug ID: 58422
Summary: Soldier of Fortune II crashes on start
Product: Wine
Version: 10.9
Hardware: x86-64
URL: https://www.moddb.com/games/soldier-of-fortune-ii/down
loads/soldier-of-fortune-2-demo-version
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: opengl
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: 17b86a90037004bda1eac142238f21a56b9bfd77
Distribution: ---
Created attachment 78844
--> http://bugs.winehq.org/attachment.cgi?id=78844
terminal output
This is one of the games affected by bug #25362 so I have to launch the game
using the workaround '__GL_ExtensionStringVersion=17700 wine SOF2.exe'.
Since Wine-10.9 the game crashes early on start regardless of that workaround.
Reverting
commit 17b86a90037004bda1eac142238f21a56b9bfd77
opengl32: Move legacy extensions fixup from winex11.
fixes the crash for me.
Can be reproduced with the demo version.
sp_demo.exe
md5sum: 25aae86e835747174523861d40facec1
Still present in Wine-10.11.
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 575.64
X.Org X Server 1.21.1.18
XFCE 4.20
--
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=58410
Bug ID: 58410
Summary: dotnet35 and dotnet35sp1 fail to install
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: sergiolaverde0(a)gmail.com
Distribution: ---
Created attachment 78820
--> http://bugs.winehq.org/attachment.cgi?id=78820
Console output of `winetricks dotnet35sp1`
When trying to install .NET 3.5 in any of its forms it fails.
The installer allows you to accept the License, and after hitting next a
download bar fills, but then the installer says the installation failed.
I have attached the console output of `winetricks dotnet35sp1`, and the output
of dotnet35 is nearly identical. The bug persists after deleting the local
cache, and .NET 4.8 installed successfully.
Winetricks version: 20250102 - sha256sum:
53194dead910f8a5eb1deacaa4773d4e48f5873633d18ab1ecd6fdb0cb92243b
Wine version: wine-10.0
--
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=58420
Bug ID: 58420
Summary: Wine crashes when running msys2 iff CPU's PKU/PKRU
feature is enabled
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pipcet(a)protonmail.com
Distribution: ---
This is a heads-up about a bug in cygwin/msys2 which may be misreported as a
wine bug.
The Cygwin code assumes CPUID leaf 0x0d to indicate in EBX a 64-byte-aligned
value. That may or may not be true on current Windows systems, but on current
Linux systems running Wine, with recent CPUs, a CPU feature called "PKU" or
"PKRU" (memory protection keys for userspace), enabled by default, indicates an
additional 8-byte XSAVE area.
This makes the Cygwin code attempt to xsave to a non-64-byte aligned area,
which causes a segfault and abnormal program termination.
While this is clearly a bug, it's a bug that apparently cannot be triggered by
current Windows systems. This means Wine fails to be bug-for-bug compatible in
this case. I don't think there's an easy way around that: we'd have to trap
XGETBV and CPUID instructions to pretend that a feature that is enabled by
Linux actually isn't available.
It would have been nice if the Linux kernel had provided a way to disable the
pku feature on a per-process basis, but AFAICT, it didn't. The nopku kernel
command line argument makes things work, but requires a reboot and disables the
very useful PKU feature for the entire system.
So I don't think there's a good workaround here, but maybe we should suggest to
the Linux kernel people to allow per-process activation of any future XCR0
features?
--
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=55138
Bug ID: 55138
Summary: msys2: bash.exe is not able to fork/start another
process.
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 74697
--> https://bugs.winehq.org/attachment.cgi?id=74697
allocation stacks in parent and child bash.exe
This is a followup to bug 47808.
If I understand it right, bug 47808 was primarily about native libraries
getting called at a win32 stack which was not yet committed.
Those native libraries then jumped over the guard page, therefore the stack
got not grown, instead a crash reported.
This aspect was fixed by using the syscall interface and
therefore bug 47808 was closed.
But there is another issue that causes a msys2-forked process crashing,
because after the stack was grown it still misses the PAGE_READWRITE flags.
For this Zeb Figura included in the first attachement to bug 47808
"always expand the stack if within the stack reserve"
a line adding the flags "VPROT_COMMITTED | VPROT_READ | VPROT_WRITE"
to the page that gets the VPROT_GUARD removed in grow_thread_stack.
This modification still enables a forked process to run.
The issue can be reproduced with an unmodified wine by just
- running msys2 bash.exe interactively
- then trying to start e.g. notepad from it.
Attached file shows the stack when the stack gets allocated
- in a working msys2-parent process and
- in a failing msys2-forked child process.
Therefore it looks like the forked stack get really setup differently,
but it is still not clear if or when this memory gets the READ/WRITE
added in native windows.
--
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.