https://bugs.winehq.org/show_bug.cgi?id=53551
Bug ID: 53551
Summary: Unable to run a hello world console program: unhandled
page fault
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ufospoke(a)gmail.com
Distribution: ---
Created attachment 72913
--> https://bugs.winehq.org/attachment.cgi?id=72913
Log file with failure on the Intel Xeon computer
I cannot run windows programs anymore on my Intel Xeon linux computer (after
upgrade of the OS).
A simple Hello World program (console application) does not work at all (see
the log file). Here is the part of the log that seems to be the problem:
wine: Unhandled page fault on execute access to 00007F9B141858D0 at address
00007F9B141858D0 (thread 0084), starting debugger...
wine: Unhandled page fault on execute access to 00007F55F46193F0 at address
00007F55F46193F0 (thread 00c8), starting debugger...
What is strange is that this happens only on one of the 2 computers that I use.
Both run the same OS (Fedora 36) with wine 7.12. The second computer run an
Intel i7.
The Xeon runs 2 Xeon CPU E5-2660 v4 which means it has 56 cores. Therefore I
first get some warnings with regards to the number of CPU:
0024:fixme:ntdll:create_logical_proc_info Improve CPU info reporting: system
supports 56 logical cores, but only 32 supported!
0024:fixme:ntdll:create_logical_proc_info skipping logical processor 33
...
0024:fixme:ntdll:create_logical_proc_info skipping logical processor 55
I'm not sure this is an issue.
Note that the binary file was compiled on the Xeon computer with a fresh
cross-compiler and with -static -s option:
x86_64-w64-mingw32-g++-12.1.0 -o hello_world.exe -static -s hello_world.cpp
Also, when I run the binary file on the i7 computer, it runs fine (see attached
log). So the binary file is fine.
In addition, I can add that both computers run an Nvidia GPU but only the Xeon
computer runs the nvidia proprietary driver from rpmfusion. The i7 uses
nouveau.
--
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=53662
Bug ID: 53662
Summary: winehq-bullseye.sources file links to incorrect
location for GPG key for Debian Bullseye only
Product: Wine
Version: 7.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: eric.wheez(a)gmail.com
Distribution: ---
Big impact, but easy fix-
This file points to the wrong location for the winehq-archive.key:
https://dl.winehq.org/wine-builds/debian/dists/bullseye/winehq-bullseye.sou…
"Signed-By: /etc/apt/keyrings/winehq-archive.key"
Other .sources files (for other Debian releases, newer and older) point to the
correct location: "Signed-By: /usr/share/keyrings/winehq-archive.key"
The WineHQ wiki (https://wiki.winehq.org/Debian) tells people to download the
key using "sudo wget -nc -O /usr/share/keyrings/winehq-archive.key
https://dl.winehq.org/wine-builds/winehq.key"
Workarounds include...
1. Editing the .sources file to point to the key file download location
specified by the WineHQ wiki:
sudo sed -i
's&/etc/apt/keyrings/winehq-archive.key&/usr/share/keyrings/winehq-archive.key&g'
/etc/apt/sources.list.d/winehq-bullseye.sources
2. Adding the key/repo the old way:
wget -O - https://dl.winehq.org/wine-builds/winehq.key | sudo apt-key add -
sudo add-apt-repository "deb https://dl.winehq.org/wine-builds/debian/
${VERSION_CODENAME} main"
sudo apt-get update -y
This one stumped me for a few hours today, so I wanted to report it in.
--
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=53688
Bug ID: 53688
Summary: Ubuntu install instruction are wrong and not working
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sayanel(a)protonmail.com
Distribution: ---
As of today (2022-09-15) the ubuntu install instructions
(https://wiki.winehq.org/Ubuntu) do not work properly
The repo key is placed in /usr/share/keyrings
But the source info
(https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources)
indicates to search /etc/apt/keyrings/
Either change instruction to copy the key to /etc or change the .source file to
point to /usr
--
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=47163
Bug ID: 47163
Summary: Photoshop 6 not working on Wine Ubuntu
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ichbinleider1(a)web.de
Distribution: ---
Created attachment 64396
--> https://bugs.winehq.org/attachment.cgi?id=64396
Description of Bug Report, Photoshop 6 not working on Wine Ubuntu
Photoshop 6 not working on Wine Ubuntu, not even starting up! Log file 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=40625
Bug ID: 40625
Summary: photoshop 6 froze after wine upgrade from 1.6 to 1.8
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: site(a)rotasul.net
Distribution: ---
Created attachment 54491
--> https://bugs.winehq.org/attachment.cgi?id=54491
wine error log
Hi,
When I used the wine 1.6 and Ubuntu Wily with kernel 3.4 the Photoshop
6 worked fine (yes a very old 32bit version six just 70MB)!!
After an upgrading the to kernel 4.2 and same wine 1.6 the Photoshop stopped
during the program load!
Now, some upgrades later, with Xenial and kernel 4.4.8 and wine 1.9.9 the
Photoshop load a little more during the opening but froze! I made several tries
winecfg XP and Win7.
Any solution in horizon?
Att.
Art
--
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=46740
Bug ID: 46740
Summary: Photoshop CS5 crashes upon opening in Wine-4.0
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Syogren.Asherushi(a)gmail.com
Distribution: ---
Created attachment 63744
--> https://bugs.winehq.org/attachment.cgi?id=63744
The backtrace
See attachment.
--
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=42877
Bug ID: 42877
Summary: SumatraPDF 3.1.2 tabs are covered by wine title bar
Product: Wine
Version: 2.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ericbasil.rabi(a)gmail.com
Distribution: ---
The SumatraPDF 3.1.2 has tabs and menu button at the top of the window. These
are partially covered by the wine title bar when not in full screen. When in
full screen, the tabs and the menu button are almost complete covered. This
makes accessing the menu and closing tabs impossible in full screen. I use
ubuntu 16.04.
--
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=48361
Bug ID: 48361
Summary: Honkai Impact 3rd doesn't start
Product: Wine
Version: 5.0-rc2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Without wine-staging the game crashes, with wine-staging the game simply
"terminates".
The log simply says
######
000b:fixme:winediag:__wine_start_process Wine Staging 5.0-rc2 is a testing
version containing experimental patches.
000b:fixme:winediag:__wine_start_process Please mention your exact version when
filing bug reports on winehq.org.
Terminated
######
Any logs I should provide?
--
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=40376
Bug ID: 40376
Summary: Black screen in Epic Games Launcher caused by d3d11
Product: Wine
Version: 1.9.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: felix-bachl(a)web.de
Distribution: ---
A black screen can be seen. The following output is repeated endlessly.
fixme:d3d11:d3d11_immediate_context_OMSetBlendState Color mask > 3 not
implemented.
fixme:d3d11:d3d11_immediate_context_RSSetState Ignoring FrontCounterClockwise
0x1.
fixme:d3d11:d3d11_immediate_context_OMSetBlendState Per-rendertarget blend not
implemented.
--
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=44840
Bug ID: 44840
Summary: Icewind Dale unusably glitchy starting with Wine
Version 3.2
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wodencafe(a)gmail.com
Distribution: ---
Starting with Wine 3.2 and on, Icewind Dale (2.0.0.11 (GOG)) is having very
strange input / glitchy rendering issues.
I have attached a video comparison with 3.1 where it works fine.
Tested with 3.2, 3.3, and 3.4, and all have the strange input and glitchy
problem.
There are no additional wine modifications.
Please see the video for example of problem, and comparison of when it was
working with 3.1
--
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.