https://bugs.winehq.org/show_bug.cgi?id=40363
Bug ID: 40363
Summary: Wine Stabilization - Gentoo Slow to Adopt With Valid
Reason
Product: Wine-staging
Version: 1.8.1
Hardware: x86-64
URL: https://bugs.gentoo.org/show_bug.cgi?id=578202
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ecyoung(a)grandecom.net
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: Gentoo
I opened the bug that I'm asking you to comment on. I opened this bug because
Gentoo's Stable version is still at 1.6.2. I use an old RPG, Istaria which is
blocky in 1.9.5, and Eve Online, which is unplayable in my case using 1.6.2.
In order to properly regression test where my issues are coming from, I thought
I would start at finding out why Gentoo's stable version lagged behind WineHQ's
stable version. Our package maintainer is doing the best he can, as our
distribution is source based, and he is perfectly within his right not to use a
custom patchset (See Comment 3).
Comment 7 in my bug states:
Let's keep this open with the info from NP-Hardass so that anybody else who
seeks for 1.8.1 knows.
I'm closing #578272 as I see no point of having it open. NP-Hardass stated he
wants to bump and stabilize 1.8.x, so it's on upstream now.
Thanks for your interest Carter, maybe try to convince upstream to get it going
;)
----------------------------------------
Bug 578272 was implemented as a tracker, but the commenter is correct in
assuming that the issue lies upstream. I present Snippets from Comment 3:
I'd prefer that our stable wine 1.8 use the official gstreamer 1.0 patchset,
but upstream never released that under the 1.8 branch. Once again though, I'd
rather not be hosting a custom patchset for stable. There is currently a
request to the upstream wine stable maintainer to include this in 1.8.2.
1.8.1 was never bumped because Wine Staging never released a patchset for 1.8.1
and I'd rather not have a stable candidate in package.use.stable.mask and not
have staging support. I'd also rather not have to host a custom staging patch
just for 1.8.1. I've cc'd the Staging devs in case they'd like to weigh in on
making an official release for 1.8.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.
https://bugs.winehq.org/show_bug.cgi?id=41344
Bug ID: 41344
Summary: err:seh:setup_exception_record stack overflow crash in
SAO visual novel
Product: Wine
Version: 1.9.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wyrex(a)openmailbox.org
Distribution: ---
Created attachment 55691
--> https://bugs.winehq.org/attachment.cgi?id=55691
Log without +seh
Game plays opening video but crashes after second screen of text ingame.
Happens every time. Trial version which I used is available here (NSFW!)
http://sample9.dmm.co.jp/digital/cg_game/d_066395/d_066395t.lzh.
winecfg is set to Win 7 and "devenum ffdshow quartz vcrun6 native_oleaut32" are
installed from winetricks.
--
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=41054
Bug ID: 41054
Summary: Battle.net.exe deadlocks in CriticalSection
Product: Wine-staging
Version: 1.9.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rankincj(a)yahoo.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Trying to launch Blizzard's Battle.net.exe using Wine Staging 1.9.15 RPMs from
Fedora 24. However, the process deadlocks and prints messages like:
err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in
thread 0063, blocked by 0000, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in
thread 0063, blocked by 0000, retrying (60 sec)
This happens with both 32 bit and 64 bit prefixes. Disabling all "staging"
options via winecfg does not help.
--
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=40225
Bug ID: 40225
Summary: NtQuerySection returns wrong size
Product: Wine
Version: 1.9.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)georg.so
Distribution: ---
Created attachment 53743
--> https://bugs.winehq.org/attachment.cgi?id=53743
NtQuerySection test case via boost interprocess
When using NtQuerySection to get the file size of a file mapping the wine
result deviates from the native one.
With wine, it seems that the size is rounded up to the next page. On native
windows, the real file size is returned.
How to reproduce (e.g. with a mingw cross compile environment):
mkdir build
cd build
mingw64-cmake ..
mingw64-make
wine64 main
Actual behavior:
fixme:winediag:start_process Wine Staging 1.9.3 is a testing version containing
experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug
reports on winehq.org.
region.get_size() == 4096
sizeof(inp)-1 == 5
Assertion failed!
Program: Z:\home\gms\program\libixxxutil\build-case-win-rel\main.exe
File: /home/gms/program/libixxxutil/test/mapped_size_case/main.cc, Line 28
Expression: region.get_size() == sizeof(inp)-1
abnormal program termination
Expected behavior (as e.g. on Windows 7):
No output and success exit code.
How reproducible:
always
The test program uses Boost Interprocess functions for creating that mapping
and getting the size.
See also:
cf.
http://www.boost.org/doc/libs/1_60_0/doc/html/boost/interprocess/mapped_reg…
> The OS could allocate more pages than size/page_size(), but get_address() will always return the address passed in this function (if not null) and get_size() will return the specified size.
http://stackoverflow.com/a/26983182/427158
-> NtQuerySection
--
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=39368
Bug ID: 39368
Summary: Some games (F.E.A.R. 1, Hitman: Contracts) crash on
start when EAX(Environmental Audio Extensions) enabled
Product: Wine-staging
Version: 1.7.40
Hardware: x86
URL: http://www.gamershell.com/download_10167.shtml
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 52478
--> https://bugs.winehq.org/attachment.cgi?id=52478
F.E.A.R. demo backtrace
When EAX is enabled in staging, some games crash on start.
Two examples are F.E.A.R. or Hitman: Contracts.
Both games have demos to reproduce the problem.
Hitman: Contracts demo:
http://www.gamershell.com/download_5663.shtml
wine-1.7.51-268-g781b88b (Staging)
Fedora 22 32-bit
Alsa 1.0.29, stereo speaker setup (PA is not running)
Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
--
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=40458
Bug ID: 40458
Summary: Photoshop CC 2015 Amtlib issues
Product: Wine-staging
Version: 1.9.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: msnduy(a)hotmail.de
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 54210
--> https://bugs.winehq.org/attachment.cgi?id=54210
logs
I have issues with running Photoshop CC 2015 (64bit) in Wine-Staging.
It installs fine with both staging and stable (PDApp only works with Staging).
But I can't start it in staging without an error although in wine stable it
works normally but the user interface of photoshop is somehow not correctly
rendered.
Wine-Staging (Compiled from git upstream):
Photoshop shows an error with the error code 16. By luck I also came across the
amtlib.log file which also contained error message with the same error code,
saying:
04/12/16 22:38:32:097 | [ERROR] | | | | AMT | | | 57 | Error: Failed to
update RW check key !
04/12/16 22:38:32:097 | [ERROR] | | | | AMT | | | 57 | ERROR: SLCache is
not writable, hence exiting. (Errno = 16)
I am sure it's the amtlib what is causing the issue as I didn't get these lines
with wine-stable.
The tricky part is that I don't know what patch from wine-staging is causing
this issue.
I attached the log files which are interesting.
I am not sure now how to debug this further as the wine debug output isn't
helpful either (basically the same output as wine stable).
What might by broken can be Registry/memory/file access, the problem is that I
don't know what api calls amtlib is doing.
Well, if someone can give me further instructions how to debug the issue I
would be glad. Also if you have enough time or whatsoever you could try install
Photoshop CC 2015 :).
--
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=41544
Bug ID: 41544
Summary: Pressing L-ALT key loses focus from game
Product: Wine-staging
Version: 1.9.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xkendy(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Uppon started game, after I press button L-ALT, the game lose mouse focus.
Focus mouse pointer is in system (above the game window). After another
pressing L-ALT, or mouse click focus is returned to game.
Affected (tested) games: World Of Tanks (patch 0.9.16), World Of Warplanes
(patch 1.9.6).
How to reproduce:
Fresh instalation WOT and WOWP using this guide for WOT:
https://www.youtube.com/watch?v=CTU0vICF9O4
WOT:
1.9.20-staging L-ALT problem present
1.9.19-staging (or lower): wot not work
WOWP:
1.9.20-staging L-ALT problem present
1.9.19-staging (or lower): L-ALT work correctly
Tested on:
- old installed game WOT
- fresh installed WOT (using guid on youtube)
- fresh installed WOWP (using guid on youtube for WOT)
System: UBUNTU 14.04 LTS x86_64, Graphics: GeForce GT640 (driver 340, tested
also version 372), 8GB RAM, CPU: i5
--
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=39348
Bug ID: 39348
Summary: Multiple games hang on exit when CSMT enabled
Product: Wine-staging
Version: unspecified
Hardware: x86
URL: http://www.fileplanet.com/191497/190000/fileinfo/Nikop
ol:-Secrets-of-the-Immortals-Demo
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de,
stefan(a)codeweavers.com
Distribution: ---
Created attachment 52444
--> https://bugs.winehq.org/attachment.cgi?id=52444
winedbg bt all
I have some games that freeze on exit when CSMT is enabled.The game executable
remains in memory and constantly uses 100% cpu after exiting the game.
Most of the games with this problem are older titles, using Directx 6-8, some
of them are newer ones, built on DX9.
With disabled CSMT those games always quit properly.
Plain terminal output doesn't show anything related.
Reproduced with nvidia binary driver 340.93 and nouveau/mesa git.
Two examples:
1. Freespace 2 demo (DX7, 60M):
http://www.fileplanet.com/126954/120000/fileinfo/Freespace-2-Demo-
(in the launcher select <Detect Available cards>, then select a video mode with
3D support, start the game. In the main menu press <Esc> a couple times to quit
the demo).
2. Nikopol demo (DX9, 355M):
http://www.fileplanet.com/191497/190000/fileinfo/Nikopol:-Secrets-of-the-Im…
wine-1.7.51-225-g3966aff
Fedora 22 32-bit
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NV92
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.0-devel
--
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=40943
Bug ID: 40943
Summary: System Shock demo (DX 11): loads to a white screen
then switches to a black screen
Product: Wine
Version: 1.9.14
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: ---
Created attachment 55080
--> https://bugs.winehq.org/attachment.cgi?id=55080
Terminal output Wine 1.9.14
When attempting to run the demo for the System Shock remake, it loads to a
white screen and then after a minute or so it switches to a black screen. I can
hear the game's ambient music and sound effects and I assume that, if the game
could render graphics in Wine, I am in the main menu screen.
Windows 7 64-bit prefix Wine 1.9.14
--
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=41573
Bug ID: 41573
Summary: Battle.net: SystemSurvey.exe crashes on starting
Battle.net
Product: Wine
Version: 1.9.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sworddragon2(a)aol.com
Distribution: ---
Created attachment 55909
--> https://bugs.winehq.org/attachment.cgi?id=55909
Terminal output
On starting Battle.net immediately a window is shown that SystemSurvey.exe has
encountered a problem but this doesn't seem to affect directly the Battle.net
launcher as it continues to work. In the attachments is the terminal output.
--
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.