https://bugs.winehq.org/show_bug.cgi?id=53574
Bug ID: 53574
Summary: MSYS2 "pacman -Sy" fails key lookup
Product: Wine
Version: 7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joel(a)airwebreathe.org.uk
Distribution: ---
Created attachment 72951
--> https://bugs.winehq.org/attachment.cgi?id=72951
Log of console interaction
With a fresh Msys2 installation, pacman fails to run, because it keeps
producing "key lookup failed" errors. The user is prompted to with the
following message:
error: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown
:: Import PGP key 5F944B027F7FE2091985AA2EFA11531AA0AA7F57? [Y/n] Y
However, if the user selects "yes", pacman simply asks the same question again
after a short delay, in an infinite loop.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53121
Bug ID: 53121
Summary: IrfanView: In full screen mode the image title is not
correctly repainted when switching between images
Product: Wine
Version: 7.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aros(a)gmx.com
Distribution: ---
Created attachment 72576
--> https://bugs.winehq.org/attachment.cgi?id=72576
Example
Steps to reproduce:
1. Download IrfanView
2. File -> Open an image file (which matches or exceeds your display
resolution)
3. Press Enter (goes in full screen mode)
4. Press right arrow or left arrow (alternatively "Space" and "Back Space") to
browse through images forward or backward.
The area where the image path and name are being rendered starts to look bad
(i.e. it's not correctly repainted). It's in the left top corner.
The example is attached.
--
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=42284
Bug ID: 42284
Summary: Enable using Wine with Wayland and without X on Linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
Currently, Wine on Linux is strongly dependent on X, and when used with the
desktop environment with new Wayland display server, Wine is forced to run
through XWayland, which so far remains a poor experience.
The whole Linux desktop is now strongly pushing the switch from X to Wayland,
and many major applications are now in the process of enabling this switch.
Is there some plan for such effort in Wine? Is it even feasible? I couldn't
find any bugs opened for it, so I'm opening one here to track this.
--
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=10941
Summary: Wine does not print in a newly allocated console window
Product: Wine
Version: 0.9.52.
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-console
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mail2benny(a)gmail.com
Created an attachment (id=9867)
--> (http://bugs.winehq.org/attachment.cgi?id=9867)
The binary which recreates the bug
Wine does not print in a newly allocated console window using the function
FreeConsole(); and AllocConsole();
I've written a program which recreates the bug. I'll post the binary and the
source.
(compiled on Dev-C++ 4.9.9.2, in Wine)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55759
Bug ID: 55759
Summary: Cinebench 2024 needs
Windows.System.Profile.SystemIdentification
Product: Wine
Version: 8.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: etaash.mathamsetty(a)gmail.com
Distribution: ---
09d4:fixme:combase:RoGetActivationFactory
(L"Windows.System.Profile.SystemIdentification",
{5581f42a-d3df-4d93-a37d-c41a616c6d01}, 00007FFFFE1FD840): semi-stub
09d4:err:combase:RoGetActivationFactory Failed to find library for
L"Windows.System.Profile.SystemIdentification"
The app works fine in windows 7 mode for the most part, the above is preventing
it from running in windows 11 mode
--
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=55886
Bug ID: 55886
Summary: No more audio (FreeBSD and OSS) since Wine 8.15
Product: Wine
Version: 8.15
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineoss.drv
Assignee: wine-bugs(a)winehq.org
Reporter: adrien_fernandes2(a)hotmail.com
Created attachment 75418
--> https://bugs.winehq.org/attachment.cgi?id=75418
winecfg under Wine 8.20
OS : FreeBSD
Processor architecture : amd64
Version : 14.0-CURRENT #0 main-n263139-baef3a5b585f: Thu May 25 08:14:14 UTC
2023
----------
Hello,
Wine 8.14 is the latest version that actually gives me audio. I'm not using
ALSA nor PulseAudio, only OSS, as usual.
I know there were changes on the audio part by Davide Beatrici, on the Wine
8.15 Wine Announcement :
[...]
wineoss: Update device cache in get_device_guid().
wineoss: Export get_device_guid().
wineoss: Remove GetEndpointIDs.
[...]
I don't know if this causes my OS to not offering sound anymore.
Since Wine 8.15 (and up to Wine 8.20), I still see "wineoss.drv" as my selected
driver and all my pcm just as it should but if I press "Test Sound", there's no
sound played and no error displayed in my terminal.
--
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=55639
Bug ID: 55639
Summary: OSS driver sends output to wrong device
Product: Wine
Version: 8.16
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineoss.drv
Assignee: wine-bugs(a)winehq.org
Reporter: sean-freebsd(a)farley.org
Created attachment 75175
--> https://bugs.winehq.org/attachment.cgi?id=75175
trace:oss of test sound using default device in winecfg
Sometime after Wine 8.11, the OSS driver sends to the device node one higher
than selected. Whether the "System Default" or the specific node device is
picked in winecfg, the "Test Sound" goes to one higher than chosen.
In my case, the speakers are on /dev/dsp4. In the log, that device is
considered the default devnode. However, the devnode chosen for output is
/dev/dsp5. If I chose /dev/dsp3 specifically, then the audio will be output
via the speakers.
It definitely looks like an off-by-one bug.
Workaround: select lower device by number
--
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=54336
Bug ID: 54336
Summary: Wow64 compatibility breaks on newer 64-bit glibc
releases
Product: Wine
Version: 8.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ruanformigoni(a)gmail.com
Distribution: ---
Newer versions of 64-bit glibc break current Wow64 compatibility
implementation.
For a new vm of fedora 36:
$ ./wine-ge-7-35-continuous-x86_64.AppImage --version
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
wine --help Display this help and exit
wine --version Output version information and exit
glibc.x86_64 version is 2.35-20.fc36
glibc.i686 is not installed.
--
For a new vm of fedora 37:
$ /wine-ge-7-35-continuous-x86_64.AppImage --version
/tmp/.mount_wine-gEI9DJM/bin/wine: No such file or directory
glibc.x86_64 version is 2.36-9.fc37
glibc.i686 is not installed (installing fixes it).
--
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=19769
Summary: STATISTICA 6 demo fails to display any child windows
Product: Wine
Version: 1.1.27
Platform: PC
URL: http://www.statsoft.ru/_Rainbow/documents/STATISTICADe
mo.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
With wine-1.1.27-266-gda1784b, when starting the STATISTICA 6 demo, the demo is
supposed to display a window entitled "Data: Adstudy (25v by 50c)" on startup,
but the demo fails to do that. The only window that is usually visible is a
"Welcome to STATISTICA 6" helper window. In addition, opening any STATISTICA
files yields the same result, no visible child windows.
--
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.