https://bugs.winehq.org/show_bug.cgi?id=38784
Bug ID: 38784
Summary: Age of Empires II: wine 1.7.x series do not work with
the external monitor as the primary output
Product: Wine
Version: 1.7.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexander.sayenko(a)gmail.com
Distribution: ---
Hi
I had pretty old Fedora 18 om my laptop with wine 1.6.x, where I was able to
launch successfully Age of Empires II: Forgotten Empires. Furthermore, I was
able to launch it in such a way that I used my external monitor as the primary
output i.e. the game was on the external monitor.
I upgraded recently to Fedora 22, which comes with wine 1.7.44, and (at least)
Age of Empires II does not launch anymore on the external monitor. Wine crashes
with the "page fault" error (see more comments below). Interestingly enough, if
I use laptop screen as the primary output, it works without problems.
I downgraded wine to 1.7.5, same issue. However, once I installed wine 1.6.1,
it started to work on the external monitor without any problem! So, I heavily
suspect that this is 1.7.x series issue. I ufortunately cannot say whether it
is somehow specific to Age of Empires II and/or my video card. If needed, I can
try other games.
Coming back to the "page fault" error itself.. Based on my personal programming
experience, it looks like some uninitialized pointer because there were a few
rare cases when wine 1.7.x actually started on the external monitor!! The
success rate was however quite low, maybe 1 out of 20. What I noticed is that
the first launch after reboot has a high probability of succeeding, but all the
next runs always fail.
With best regards,
Alex
--
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=49369
Bug ID: 49369
Summary: Error while make install on NetBSD 9.0
Product: Wine
Version: 5.10
Hardware: x86
OS: NetBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nikitastepan0v(a)mail.ru
Created attachment 67418
--> https://bugs.winehq.org/attachment.cgi?id=67418
log
Error while make install on NetBSD 9.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.
https://bugs.winehq.org/show_bug.cgi?id=40437
Bug ID: 40437
Summary: Smartdraw 2013 won't run, crashes.
Product: Wine
Version: 1.9.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bbaker6212(a)gmail.com
Distribution: ---
Created attachment 54188
--> https://bugs.winehq.org/attachment.cgi?id=54188
wine crash dump file
Nothing to say really. Trying to run it and it crashes right away.
--
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=34433
Bug #: 34433
Summary: D&C Scheme Editor 5: Crash after drawing onto sheet
Product: Wine
Version: 1.7.0
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Classification: Unclassified
Created attachment 45841
--> http://bugs.winehq.org/attachment.cgi?id=45841
Terminal output on wine-1.7.0-346-g1bf936c
Steps to reproduce:
1) remove ~/.wine
2) winetricks dotnet40 corefonts
3) install D&C Scheme Editor 5
4) start D&C Scheme Editor 5
5) try to draw e.g. rectangle onto sheet
Behaviour:
Program crash.
Expected behaviour:
No program crash.
--
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=42382
Bug ID: 42382
Summary: Adam Standalone demo doesn't progress past the initial
loading screen
Product: Wine
Version: 2.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fjfrackiewicz(a)gmail.com
Distribution: ---
When attempting to run the Adam Standalone demo from Unity3D, the demo never
makes it past the initial "Loading" screen. It doesn't freeze because there is
continuous terminal output in the background but it doesn't go any further than
the loading screen.
Steps to reproduce:
1. Download the demo.
2. Run "wine Adam.exe"
3. Wait and see the demo not make it past the "Loading" screen.
--
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=49368
Bug ID: 49368
Summary: Enhancement: check if wine can access native dll's
Product: Wine
Version: 5.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vedeifun(a)byom.de
Distribution: ---
This is not a bug. But this is suggestion for an improvement. Wine would be
more user friendly if we could add this functionality.
Until now, when we open winecfg tab library and choose a dll from the list of
overwritable dll's, then we do not know, if there is really a "nativ dll" in
our prefix. And if wine can find it.
So when a particular program does not work correctly in wine it could be, that
it is just, because wine can not find the dll we have overritten.
Suggestion:
When we select a dll for overriding and wine can not access it, wine should
display a warning message right after we select the DLL.
Alternatively you could implement an additional button called "Check access to
native dll's" in the library register.
This way we were able to check if wine really can find the native dll's when
selecting the dll's. Or if we have to copy one 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=49348
Bug ID: 49348
Summary: Wine windows are not visible in Gnome-Shell preview
due using _NET_WM_STATE_SKIP_TASKBAR
Product: Wine
Version: 5.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal54(a)gmail.com
Distribution: ---
Some gog installers are visible in Gnome-shell preview, but some are not.
_NET_WM_STATE(ATOM) = _NET_WM_STATE_SKIP_TASKBAR - cause that this windows
aren't shown.
This maybe is "correct" behavior but is very it's very annoying and hard to
find correct window when this flag is set, so maybe this flag should be
forbidden.
Closed issue in Gnome: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2886
Gif with current behavior is also inside gnome issue
--
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=48894
Bug ID: 48894
Summary: large screen size cause fail with directx9
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: a1_canon(a)yahoo.co.jp
Distribution: ---
Created attachment 66840
--> https://bugs.winehq.org/attachment.cgi?id=66840
dialog
os: fedora31
wine: winehq stable wine 5.0
software: Final Fantasy XIV V5.21
directx: dx9
WINEARCH: win32
There is no problem, if screen size is 1280x720.
There is a little problem , if screen size is 1280x768.
Operation of the software is no problem, but d3d error appears in terminal like
this:
0089:err:d3d:wined3d_debug_callback 0x3db1ce0: "GL_OUT_OF_MEMORY error
generated. Failed to allocate CPU address space mapping for texture (consider
building 64-bit app).".
0089:err:d3d:wined3d_debug_callback 0x3db1ce0: "GL_INVALID_OPERATION error
generated. The source or destination texture is not complete.".
---------------------------------------------------------------
A dialog appear(attached), the software is hung, if screen size is 1280x960.
--
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=39816
Bug ID: 39816
Summary: Crash related to dxgi
Product: Wine
Version: 1.7.53
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gabriel.corona(a)enst-bretagne.fr
Distribution: ---
Since commit 895c5f8234813d2b445376aa73e1fc93b5061b0b (dxgi: Partially
implement dxgi_adapter_CheckInterfaceSupport()), many softwares crash/fail to
start (for example BioShock 2) silently. This still happens in 1.8.
This is fixed by disabling dxgi in winecfg.
--
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=49360
Bug ID: 49360
Summary: Bioshock hangs on saving/loading
Product: Wine
Version: 5.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mtmkls(a)gmail.com
Distribution: ---
Bioshock 1.1 has a 50% chance of getting stuck when loading or saving the game.
When it hangs during saving, both Bioshock.ini and the savegame to be
overwritten get deleted, so it's very inconvenient.
Console output:
0024:fixme:thread:SetThreadIdealProcessor section 0x110060 "heap.c: main
process heap section" wait timed out in thread 0024, blocked by 0130, retrying
(60 sec)
00cc:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 00cc, blocked by 0130, retrying
(60 sec)
0024:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 0024, blocked by 0130, retrying
(60 sec)
00cc:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 00cc, blocked by 0130, retrying
(60 sec)
0024:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 0024, blocked by 0130, retrying
(60 sec)
00cc:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 00cc, blocked by 0130, retrying
(60 sec)
0024:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 0024, blocked by 0130, retrying
(60 sec)
00cc:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 00cc, blocked by 0130, retrying
(60 sec)
--
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.