https://bugs.winehq.org/show_bug.cgi?id=46077
Bug ID: 46077
Summary: Pathos: screen flickering / texture tearing
Product: Wine
Version: 3.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: orbisvicis(a)gmail.com
Distribution: ---
Created attachment 62694
--> https://bugs.winehq.org/attachment.cgi?id=62694
terminal output
Pathos is an open-source game available at https://pathos.azurewebsites.net
using the Inv framework available at
https://gitlab.com/hodgskin-callan/Invention/wikis/home. Both users attempting
to run the game via wine have reported the same issue on completely different
hardware. The game auto-updates. As far as I know all versions expose the issue
but I can confirm that w2018.1102.2249 is susceptible. There is a lot of detail
in the following reddit thread, including several work-arounds.
https://www.reddit.com/r/pathos_nethack/comments/9nh6qw/pathos_under_wine/
Wine versions:
* multilib (x86_64 + i686) wine 3.17 from fedora 28 with winepulse.drv audio
output and winetricks 20180603
* wine-devel 2.0.170 on Ubuntu
* latest wine from WineHQ repository on Mint 18.3 with winetricks 20180815-next
Game details:
* "It's all .NET Framework 4.5.0 and WPF controls. The main game board is
custom drawn using System.Windows.Media.DrawingContext."
Game installation
$ env WINEARCH=win32 WINEPREFIX=/.../Pathos/pathos.wine.prefix.win32/
winetricks corefonts dotnet452
$ env WINEARCH=win32 WINEPREFIX=/.../Pathos/pathos.wine.prefix.win32/
winetricks win7
$ env WINEARCH=win32 WINEPREFIX=/.../Pathos/pathos.wine.prefix.win32/ wine
PathosSetup.exe
$ env WINEARCH=win32 WINEPREFIX=/.../Pathos/pathos.wine.prefix.win32/ wine
"C:\Games\Pathos\PathosGame.exe"
Nvidia workarounds
+ GPU: NVIDIA Corporation GM206 [GeForce GTX 960]
+ GPU driver NVIDIA 396.54
+ OS: Fedora 28 + XMonad
* leave fullscreen mode
* run a compositor when the game is fullscreen
* disable "allow flipping" in the nvidia-settings OpenGL tab
* winetricks ddr=gdi (but this makes the game stutter and lag)
ATI workarounds
+ CPU: AMD APU A6-6700
+ GPU: AMD RX 570
+ GPU driver: AMDGPU
+ OS: Mint 18.3
* winetricks ddr=gdi (but this makes the game stutter and lag)
Opinions:
Looks like a double-buffering problem.
--
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=33385
Bug #: 33385
Summary: Map is black on resolutions bigger than 640x480 in
Gruntz
Product: Wine
Version: 1.5.28
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: Admc(a)ufurmix.org
Classification: Unclassified
When 800x600 or 1024x768 resolution is set in Gruntz the map is black. Only
Gruntz are visible, this makes game unplayable. Bug occurs both in wine 1.4 and
1.5.28. On 1.2 it works fine, so obviously it's a regression.
Steps to reproduce:
1. Buy Gruntz or download demo -
http://download.cnet.com/Gruntz-demo/3000-2119_4-10026065.html
2. Install it
3. Apply resolution patch (there's a bug in game that prevents changing
resolution in in-game options) -
http://gooroosgruntz.proboards.com/index.cgi?board=GFAQs&action=display&thr…
4. Run game on virtual desktop
5. Start game on any map
6. Map is black, only Gruntz are visible
My graphics card is Nvidia GeForce GTX 550 Ti, I'm using Nvidia proprietary
driver version 319.12
My OS is Kubuntu 12.10, I removed pulseaudio and installed alsa+dmix instad of
it to get working sound in wine.
--
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=43545
Bug ID: 43545
Summary: Path of exile crashes after a few minutes of playing
Product: Wine
Version: 2.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)khelekore.org
Distribution: ---
Created attachment 58945
--> https://bugs.winehq.org/attachment.cgi?id=58945
one of the crashes
Debian sid, running gnome 3 on X.
wine-2.14 (Staging), from deb https://dl.winehq.org/wine-builds/debian/ sid
main
Intel nuc, i7-5557U
Graphics: Mesa DRI Intel(R) Iris 6100 (Broadwell GT3) (0x162b)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.5
Installed path of exile, tried with both 32 bit and 64 bit wine versions on
different WINEPREFIX, game seems to use 32 bit version no matter what.
Start game and play. It will stutter a bit every now and then which is a bit
annoying, but there are other bugs on that.
After a few minutes of playing, hard crash. Changing zone generally makes the
crash appear faster.
What information is missing?
--
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=38054
Bug ID: 38054
Summary: DoDragDrop() should abort when
IDropSource::QueryContinueDrag fails
Product: Wine
Version: 1.7.36
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: litimetal(a)gmail.com
Distribution: ---
Created attachment 50692
--> https://bugs.winehq.org/attachment.cgi?id=50692
IDrop_Example.exe
I've written some test code for DoDragDrop, and if
IDropSource::QueryContinueDrag returned a FAILED value (for example,
0xdeadbeef), DoDragDrop would about in Win8.
But wine will continue to do the job of DoDragDrop, so I'll see a MessageBox I
created in IDropTarget::DragEnter (In [MSDN], this is the 2nd step of
DoDragDrop)
Code sample:
https://gitcafe.com/endle/IDrop_Helper_Example/tree/DoDragDrop_should_stop
The .exe file was created with VS2013 Community
[MSDN]:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms678486%28v=vs.85…
--
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=31802
Bug #: 31802
Summary: World of Warplanes fails to play intro video
Product: Wine
Version: 20050930
Platform: x86-64
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: blakekl10(a)gmail.com
Classification: Unclassified
Created attachment 41840
--> http://bugs.winehq.org/attachment.cgi?id=41840
log from wine.
after launching World of Warplanes, the loading screen appears. Once the
progress bar is full, the screen goes black and the intro movie is supposed to
play. The screen remains black. Attached are the wine logs, X11 logs, and the
World of Warplanes log.
--
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=44834
Bug ID: 44834
Summary: World of Tanks don't unload from memory after exit
Product: Wine
Version: 3.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: reisenfag(a)gmail.com
Distribution: ---
After update World of Tanks to 1.0 version, if quit from game, process
worlrdoftanks.exe, wineserver and other wine's processes not terminating. In
log no errors. Wine prefix is pure, in 32 / 64 same 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.
https://bugs.winehq.org/show_bug.cgi?id=47972
Bug ID: 47972
Summary: Paraworld: segfaults at start
Product: Wine
Version: 4.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ybyt4t(a)gmail.com
Distribution: ---
On start I just get a crash with:
# wine C:/Program\ Files/Sunflowers/ParaWorld/bin/Paraworld.exe
---
0009:err:seh:setup_exception_record stack overflow 1040 bytes in thread 0009
eip 7bc6c30c esp 00230f20 stack 0x230000-0x231000-0x330000
---
I did
---
setcap cap_net_bind_service=+eip /usr/bin/wine-preloader
---
before this, as suggested in #18014, which seemed to fix something, as
otherwise it seems to crashes earlier into the debugger with:
--- (crash without setcap) ---
wine: Unhandled page fault on write access to 0x00aceb99 at address 007075C0
(thread 0009), starting debugger...
---
Not sure about the Paraworld version, probably 1.0 (DVD version, box label
ECD008134M).
Distro: Arch (x86-64)
--
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=13910
Summary: Changing Wine version should generating warning
Product: WineHQ Bugzilla
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: bugzilla-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
We're getting a lot of users changing their reported Wine version in bugs.
Doing so should either be blocked to non-admin users, or generating a warning
page.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=22594
Summary: Request to limit the number of screenshots per app
version
Product: WineHQ Apps Database
Version: unspecified
Platform: Other
URL: http://appdb.winehq.org/objectManager.php?sClass=scree
nshot&sState=queued&sTitle=Screenshot%20Queue
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P3
Component: appdb-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
There is apparently no numerical screenshot limit per app version. On many an
occasion logging into the AppDB can have over a hundred screenshots waiting,
and most of the time it'll be one user that feels it necessary to submit thirty
or so screenshots of his Call of Duty character standing in different angles.
Firstly, it is unnecessary to have so many screenshots for one version of any
app, ten should be more than enough to get an idea and the AppDB shouldn't be a
place for people to submit galleries of their wonderful death match victories.
Secondly, adding or rejecting each screenshot one by one takes a ridiculous
amount of time for the poor admin/maintainer that gets stuck with the task.
If the number of screenshots were limited, a message could be shown to let the
user know that the limit has been reached, and to encourage them to become an
app maintainer if they wish to change the screenshots. This would save us a
lot of time!
--
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.