https://bugs.winehq.org/show_bug.cgi?id=41512
Bug ID: 41512
Summary: Adobe Creative Cloud application crashing
Product: Wine-staging
Version: unspecified
Hardware: x86
URL: http://ccmdls.adobe.com/AdobeProducts/KCCC/1/win32/Cre
ativeCloudSet-Up.exe
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrypsilons(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 55876
--> https://bugs.winehq.org/attachment.cgi?id=55876
backtrace from the crash dialog
The application immediately crashes on startup.
Did a regression test, the crash is happening if this patch is applied:
https://github.com/wine-compholio/wine-staging/blob/master/patches/kernel32…
I can provide terminal output, but I don't know what WINEDEBUG flags to use.
Steps to reproduce:
- Set version to Windows 7
- Run the installer (see URL field)
- Installer automatically starts installed "Creative Cloud.exe", which
immediately crashes
--
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=42679
Bug ID: 42679
Summary: no alpha while blitting in batches
Product: Wine-staging
Version: 2.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: keloero(a)oreolek.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 57641
--> https://bugs.winehq.org/attachment.cgi?id=57641
fireurq2.1 - run test.qst
[I'm not the app developer, but I noticed the bug.]
The bug occurs only in staging version, Wine 2.0 stable and lower are
unaffected.
There is no alpha channel while blitting in batches, the bitmaps have black
background.
How to reproduce: see the fireurq.7z attachment;
run fireURQ2.exe, choose test.qst as the game or just run like this: wine
fireURQ2.exe test.qst
Look at the button, the letters have rough black edges on them. It shouldn't
look like that and it doesn't in Wine 2.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=42123
Bug ID: 42123
Summary: Missing icons in jsMSIx
Product: Wine
Version: 2.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhansonxi(a)gmail.com
Distribution: Ubuntu
Created attachment 56657
--> https://bugs.winehq.org/attachment.cgi?id=56657
White icons
Xubuntu 14.04 (and 16.04) x86_64, AMD Phenom 9550, GeForce GTX 750Ti with
Nvidia 340.98 driver.
Windows version: Windows XP
Wine Staging (wine PPA) and git
There's a regression in jsMSIx. Most button icons are completely white
(compare to screenshot in AppDB). I first noticed it with 1.9.23 (PPA).
Worked with 1.8-rc1 when I last filed a test report.
It works with 1.7.55 and 1.8.0 from the repos so I began regression testing. I
first compiled from git at current head a few days ago and retested.
Unexpectedly the icons displayed properly. I retested 2.0-rc3 from the PPA on
Xubuntu 16.04 and they were white again. Seems like there is a problem with
the PPA packages. May be related to bug #42121.
Requires VB6 runtime (winetricks -q vb6run).
--
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=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=43636
Bug ID: 43636
Summary: Age of Empires 2 HD Launcher doesn't work
Product: Wine-staging
Version: 2.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Regression SHA1: 12008817958ed954b2d38b2bb69e508fe72377c3
Distribution: ---
With wine-staging, the steam Game Age of Empires 2 HD has a broken Launcher.
It doesn't display the html contents, and the buttons don't work, making it
impossible to start the game.
Clean 32Bit WINEPREFIX. Launcher needs vcrun2015 installed to start up at all.
Bisected to
commit 12008817958ed954b2d38b2bb69e508fe72377c3
Author: Dmitry Timoshkov <dmitry(a)baikal.ru>
Date: Wed May 17 23:55:55 2017 +0800
server: Add support for a layered window region. (v2)
Reverting fixes the issue. If you need logs, just tell me.
--
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=42288
Bug ID: 42288
Summary: Shantae and the Pirate's Curse - gameplay area resized
to a tiny rectangle
Product: Wine-staging
Version: 2.0-rc6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ikk_pl(a)yahoo.co.uk
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 56999
--> https://bugs.winehq.org/attachment.cgi?id=56999
Screenshot showing the problem
Normally the game uses pixelized graphics during gameplay. In wine the play
area does not get resized to the entire screen, but instead stays at the same
size in a tiny rectangle in the middle of the screen.
(Note that the game doesn't run on vanilla wine, it needs staging patches for
the CreateDeferredContext call.)
--
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=42127
Bug ID: 42127
Summary: DOOM (2016): Crash on the main menu.
Product: Wine-staging
Version: 2.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: b.adam.martin(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 56667
--> https://bugs.winehq.org/attachment.cgi?id=56667
terminal output and backtrace
Since only one attachment is allowed, I have pasted the terminal output at the
head of the backtrace.txt. Search for "backtrace" to skip.
4.8.13-1-ARCH
GTX 770
nvidia 375.26-1
i5 4670k
wine-2.0-rc2 (Staging) --- The Arch repos haven't yet updated to rc3; it's
flagged.
$ wine DOOMx64vk.exe
The game launches fine, goes through the splash screen, and then when presented
with the main menu, abruptly crashes.
I have tried setting different Windows versions winecfg, same result with each.
I have also run $ wine DOOMx64.exe, same result.
--
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=43543
Bug ID: 43543
Summary: Wrong sounds in Within a Deep Forest
Product: Wine-staging
Version: 2.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)thecybershadow.net
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
The sound effects in Within a Deep Forest seem to be broken. Specifically, the
wrong samples seem to be used.
For example, selecting a ball material produces a metallic sound (instead of
the loud "twirp"), and bouncing around with the initial ball material plays
various hums and occasionally splashing noises.
Reproducible with WaDF version 1.1.4 and wine-staging 2.14 on a clean
WINEPREFIX. Not reproducible with wine 2.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=42318
Bug ID: 42318
Summary: Sleeping Dogs - CSMT prevents getting past
introductory videos, without CSMT the videos are all
purple and continue looping without starting the
actual game.
Product: Wine
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: casparcedro96(a)gmail.com
Distribution: ---
Created attachment 57063
--> https://bugs.winehq.org/attachment.cgi?id=57063
Crash with CSMT enabled
So it seems Sleeping Dogs does not like CSMT for some reason and even without
it I cannot seem to get past the intro videos which show up pink but the audio
is perceptible - it continues to loop playing the videos but never gets into
the game.
--
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=43761
Bug ID: 43761
Summary: World of Warcraft d3d11 textures rendering regression
and other... Wine Staging 2.17
Product: Wine-staging
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zefkerrigan(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 59257
--> https://bugs.winehq.org/attachment.cgi?id=59257
World of Warcraft d3d11 textures rendering regression. Wine Staging 2.17
Sorry, but I really do not have the opportunity to find out if this bug is in
the development Wine branch, because World of Warcraft can only be launched in
Wine Staging, but it can not be launched in a "vanilla" development Wine
branch.
So, I using only Wine Staging.
I could not get the output of the console, because, unfortunately, when I tried
to run the game through the console, I did not manage to run the game until the
stage of character management/movement. That is, the game hangs up every time
the progress bar ends after clicking on the "Enter the World" button. But, I
was surprised that the game is normally run through a shortcut on the dock bar,
which also contains the same command in the line
Exec=wine64 'c:/Program Files (x86)/World of Warcraft/Wow-64.exe'
which I entered into the console (but, without "Exec=", of course).
When I used Wine Staging 2.16 I did not have any noticeable rendering bugs with
the World of Warcraft in DirectX11 mode, or DirectX9.
But, with Wine Staging 2.17 I began to see what's on the attached screenshot if
WoW is running in DirectX11 mode. But, in DirectX9 mode this bug does not
appear, and there are no any distortions in the graphics.
My specs:
Arch Linux x86_64 with latest updates, GNOME.
GPU Radeon HD7770 with latest Mesa.
Wine Staging 2.17 with CSMT is on, x64 Wine prefix, 64bit WoW build.
--
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=43793
Bug ID: 43793
Summary: d3d11-Deferred_Context patchset is missing dependency
on wined3d-1DTextures
Product: Wine-staging
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
When d3d11-Deferred_Context is applied, compilation fails like this:
gcc -m64 -c -o wspool.o
/home/user/build/wine-git/wine-source/dlls/winspool.drv/wspool.c -I. \
-I/home/user/build/wine-git/wine-source/dlls/winspool.drv -I../../include \
-I/home/user/build/wine-git/wine-source/include -D__WINESRC__ -D_SPOOL32_
-D_REENTRANT -fPIC \
-Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers \
-Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits
-Wunused-but-set-parameter -Wvla \
-Wwrite-strings -Wpointer-arith -Wlogical-op -O3
../../tools/winegcc/winegcc -o winscard.dll.so -B../../tools/winebuild -m64
-fasynchronous-unwind-tables -shared
/home/user/build/wine-git/wine-source/dlls/winscard/winscard.spec \
winscard.o rsrc.res ../../libs/port/libwine_port.a
/home/user/build/wine-git/wine-source/dlls/wined3d/resource.c: In function
‘wined3d_resource_update_info’:
/home/user/build/wine-git/wine-source/dlls/wined3d/resource.c:403:32: error:
‘WINED3D_RTYPE_TEXTURE_1D’ undeclared (first use in this function); did you
mean ‘WINED3D_RTYPE_TEXTURE_3D’?
else if (resource->type == WINED3D_RTYPE_TEXTURE_1D ||
^~~~~~~~~~~~~~~~~~~~~~~~
WINED3D_RTYPE_TEXTURE_3D
Explicitly adding wined3d-1DTextures helps.
--
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=42815
Bug ID: 42815
Summary: Autodetection of drives in winecfg crashes Wine in
Wine (Staging)
Product: Wine-staging
Version: 2.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: frail.knight(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 57876
--> https://bugs.winehq.org/attachment.cgi?id=57876
Backtrace
Autodetection of drives in winecfg crashes Wine in Wine (Staging)
I did a clean system install.
I did a clean install of Wine 2.5 (Staging).
$ wine --version
wine-2.5 (Staging)
I was going through the basic setup in Wine.
I started winecfg.
I clicked the Drives tab.
I clicked the Autodetect button on the Drives tab.
Wine Crashes.
This has not happened to me in previous versions such as Wine 2.4 Staging.
Uploading the backtrace and console 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.
https://bugs.winehq.org/show_bug.cgi?id=43435
Bug ID: 43435
Summary: x32dbg hangs when starting program
Product: Wine-staging
Version: 2.13
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
CC: dmitry(a)baikal.ru, erich.e.hoover(a)wine-staging.com,
michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
When starting a program to debug, it displays a message like "Breakpoint at
1000154C7 set" and then freezes.
Bisected to
commit 9c509cbf8879a4283cb134321764c1024bcaf855
Author: Dmitry Timoshkov <dmitry(a)baikal.ru>
Date: Wed Mar 16 20:23:28 2016 +0800
kernel32: Implement K32GetMappedFileName. (v2)
Reverting fixes the 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=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=43511
Bug ID: 43511
Summary: Crash when launching Assassins Creed 4
Product: Wine-staging
Version: 2.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jgarciaalo(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 58896
--> https://bugs.winehq.org/attachment.cgi?id=58896
Crash log
An error occurs when starting Assassins Creed 4.
The game arrives to the first screen but throws a fatal error (seems a
nullpointer).
Note that this game worked on 2.7-Staging, 2.8-Staging and 2.9-Staging.
The next version I checked was the 2.13-staging that had another crash already
solved.
Now in 2.14-staging it crash here.
Submited files:
Error screenshot: ac4_error.png
Crash log: ac4_error.txt
--
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=43063
Bug ID: 43063
Summary: MetaTrader 4 has no internet connection
Product: Wine-staging
Version: 2.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: danielbermond(a)yahoo.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 58234
--> https://bugs.winehq.org/attachment.cgi?id=58234
MT4 startup log
After starting MetaTrader 4 the message 'Common error' is shown in connection
status (bottom right corner of the window).
All charts shows a big message 'Waiting for update'. No graphics/data is shown
on charts.
MetaTrader 4 was working fine until wine-staging 2.7.
This problem is occurring only in wine-staging 2.8.
Downgrading wine-staging to version 2.7 "fixes" the problem.
Using regular wine version _2.8_ also "fixes" it.
So it seems to be a regression of wine-staging 2.8. The bug also seems to be
_not_ present in the regular wine version.
System information:
OS: Arch Linux x86_64
wine: 2.8 staging
Notes:
1) MetaQuotes do not provide the (unbranded) MT4 download in their website
anymore. Now there are only broker-branded versions and the links the can found
at broker websites. For example, FxPro MT4 can be downloaded from:
https://download.mql5.com/cdn/web/fxpro.financial.services/mt4/fxprocom4set…
2) MT4 seems to need gnutls for proper installation (dependency lib32-gnutls is
needed for install).
3) Using comctl32 from winetricks fixes tooltips problems in charts.
--
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=44660
Bug ID: 44660
Summary: Microsoft Office: smoothing does not apply
Product: Wine-staging
Version: 3.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: genaloner(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 60664
--> https://bugs.winehq.org/attachment.cgi?id=60664
On fisrt window vanilla wine with good-looking fonts. On second - staging
branch with weird fonts
`winetricks fontsmooth=rgb` don't work with Office applications. On wanilla
wine this command makes fonts smooth. But on staging it does nothing.
--
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=42287
Bug ID: 42287
Summary: Shantae and the Pirate's Curse - moving sprites leave
smudges behind them
Product: Wine-staging
Version: 2.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ikk_pl(a)yahoo.co.uk
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 56997
--> https://bugs.winehq.org/attachment.cgi?id=56997
Screenshot of the problem
Any moving sprites in the game cinematics leave behind a solitaire-like smudge.
(Note that the game doesn't run on vanilla wine, it needs staging patches for
the CreateDeferredContext call.)
--
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=43400
Bug ID: 43400
Summary: Staging patchset wined3d-Copy_Resource_Typeless is
missing dependency on wined3d-1DTextures
Product: Wine-staging
Version: 2.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
When applying staging patchset wined3d-Copy_Resource_Typeless with
patchinstall.sh selectively, the final result fails to build with the following
error:
.../dlls/wined3d/cs.c:2253:40: error: ‘WINED3D_RTYPE_TEXTURE_1D’ undeclared
(first use in this function)
else if (op->dst_resource->type == WINED3D_RTYPE_TEXTURE_1D ||
^~~~~~~~~~~~~~~~~~~~~~~
It's because it really depends on wined3d-1DTextures, and it's not installed
using patchinstall.sh, since that dependency isn't specified.
--
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.