http://bugs.winehq.org/show_bug.cgi?id=19376
Summary: Suspend kwin's compositing when starting a 3D
application
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kde(a)martin-graesslin.com
KDE bug https://bugs.kde.org/show_bug.cgi?id=198744 illustrates that some
graphics card drivers are still not able to support 3D applications in a
composited environment correctly. This seems to be a stronger problem for wine
applications (at least in the bug report).
KWin supports suspending compositing via a dbus interface
(http://websvn.kde.org/*checkout*/trunk/KDE/kdebase/workspace/kwin/org.kde.K…).
You can basically check if compositing is active, suspend it when the app is
started and resume when the app is closed. This is for example done by KDE's
powermanagement daemon.
As a shell script it looks like that:
composited='qdbus org.kde.kwin /KWin compositingActive'
if $composited; then qdbus org.kde.kwin /KWin toggleCompositing; fi
wine blablabla
if $composited; then qdbus org.kde.kwin /KWin toggleCompositing; fi
I basically wish with this enhancement report that you add support for
suspending KWin's compositing on an application basis in wine. It shouldn't be
for every app and it shouldn't be activated in general but the user should have
the possibility to just say that one specified app should suspend compositing.
--
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=24951
Summary: Call of Duty / UO: Jerky freelook
Product: Wine
Version: 1.3.6
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gav616(a)gmail.com
At the main menu:
When the cursor is moveed around it 'seems' to be at a very low framerate and
it jerks about.
In-game:
When freelooking around, the game seems to stay at the correct rate but the
mouse movements are jerked and misinterpreted. It looks like the FPS is
dropping to 5 when the jerks occur, but the FPS remains constant through the
jerks.
Audio is not effected.
--
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=40336
Bug ID: 40336
Summary: Freelancer: Background Texture for in-game "NavMap"
spreads across entire screen (Intel only)
Product: Wine
Version: 1.9.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adam(a)aphirst.karoo.co.uk
Distribution: ---
Created attachment 54005
--> https://bugs.winehq.org/attachment.cgi?id=54005
Example of erroneous behaviour
This is essentially a repost of Bug #494 on the Wine-Staging tracker, as it
turns out that it is not unique to the -staging builds.
https://bugs.wine-staging.com/show_bug.cgi?id=494
-----
A feature of the HUD in this game is the "NavMap", a navigation map which
overlays onto the current gameplay and displays a map either of the current
star-system, or of the whole galactic sector, and with some additional relevant
information.
This HUD, like the other gameplay menu-elements, is supposed to simply overlay
onto the screen, being transparent/translucent on the outside. Indeed, one can
also interact with some game/menu elements outside said window even if it is
currently displayed.
However, the observed behaviour (attached) for the "NavMap" is that the
background texture for the "map" portion, a texture of a star-scape, is instead
displayed across the entire screen. The user can still interact with the (now
invisible!) objects behind the texture. Some text in the NavMap window is also
obscured.
This behaviour occurs on a clean install of the game, with the official 1.1
patch, and with Jason's Extended Patch 1.20; also on just the Demo version of
the game.
http://dl.4players.de/f1/freelancer/freelancer_demo.exe
---
I am currently running Wine-Staging 1.9.5 but the bug has been present since at
least as early as 1.7.48.
Intel i5-3540M with HD4000 graphics, 16GB RAM. Arch Linux x86_64, Linux 4.3.6
(but at least as far back as 4.1.4). Intel driver 2.99.917+579+g74cd4d0 (but at
least as far back as 2.99.917+381+g5772556)
---
Michael Müller from the Wine-Staging tracker tested this on other graphics
hardware/stacks and came to the conclusion that the issue is only present on
Intel+Mesa.
--
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=39985
Bug ID: 39985
Summary: Battle.net fails to start with an error dialog
pointing to Qt with wine staging, but not with regular
wine
Product: Wine
Version: 1.9.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: krafczyk.matthew(a)gmail.com
Distribution: ---
When starting Battle.net with wine-staging 1.9.1, the program fails to start
with an error dialog with the following text:
"This application failed to start because it could not find or load the Qt
platform plugin "windows".
Reinstalling the application may fix this problem."
If you then switch to regular wine 1.9.1, the program starts as expected
without the error dialog.
I'm running Arch, and I've installed Battle.net into a 32-bit prefix with the
environment variable WINEARCH=win32
You can download Battle.net from here:
http://www.battle.net/download/getInstallerForGame?os=win&locale=enUS&versi…
--
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=40019
Bug ID: 40019
Summary: wine 1.9.1 staging : it can not run a install exe file
, it reports "Error reading setup initialization file"
Product: Wine-staging
Version: 1.9.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zuogang(a)huawei.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
wine can not run a install exe file , it reports "Error reading setup
initialization file"
on host fedora 23 amd64
[zoge@localhost shm]$ rpm -qf /usr/bin/wine
wine-core-1.9.1-1.fc23.x86_64
wine-core-1.9.1-1.fc23.i686
in kde desktop, right click the exe file , select "open with wine ..."
the exe is downloaded from : http://www.sourceinsight.com/down35.html
--
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=40032
Bug ID: 40032
Summary: Starcraft 2 crashes
Product: Wine-staging
Version: 1.9.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: krafczyk.matthew(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
StarCraft 2 now crashes with the error message
"An error occurred starting StarCraft II. Please try again. (Error 2:
-2147483392)"
This happens for both the 32 bit and 64 bit versions of StartCraft 2 and
happens with and without CSMT. Here is a pastebin from launching the 64bit
version with CSMT: http://pastebin.com/ntk9kM4u
StarCraft 2 works just fine with plain 1.9.2
--
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=39369
Bug ID: 39369
Summary: Alpha Prime: certain sounds muffled when using EAX
Product: Wine-staging
Version: 1.7.40
Hardware: x86
URL: http://www.gamershell.com/download_18730.shtml
OS: Linux
Status: NEW
Keywords: download
Severity: minor
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: ---
When EAX is enabled in staging, certain sounds in the game like footsteps,
shooting sound, activating an object or speech during cutscenes are so quiet
that they're barely audible.
Other sounds like background music, NPC talks are playing normally.
There's is nothing related in the terminal.
alphaprime_demosetup_en.zip
sha1: e2cbf8b2aa4f6de3d93cb48997a2b7eca0460a77
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=40611
Bug ID: 40611
Summary: Wine-stagging: Illegal instruction error under FreeBSD
11-CURRENT
Product: Wine-staging
Version: 1.9.9
Hardware: x86
OS: FreeBSD
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: iron.udjin(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Everything works fine without stagging patch.
With stagging patch when I trying to start Steam or any other program I see:
err:wineboot:start_services_process Unexpected termination of services.exe -
exit code 0
[2016-05-11 00:40:18] Startup - updater built Apr 29 2016 15:19:38
Looks like steam didn't shutdown cleanly, scheduling immediate update check
Illegal instruction
I guess the error is related to sound. When I start winecfg and go to "Audio"
tab, I'm getting the same "Illegal instruction" error.
How can I debug it further?
Do I need to send you "truss" log or WINEDEBUG=all 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=39676
Bug ID: 39676
Summary: The Darkness II shows only black screen when CSMT
enabled
Product: Wine-staging
Version: 1.8-rc1
Hardware: x86
URL: http://store.steampowered.com/app/67370/
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 52901
--> https://bugs.winehq.org/attachment.cgi?id=52901
terminal output
This is the game from bug #30061.
When CSMT is enabled in staging, the game starts but shows only a black screen
(I can hear audio from the intro videos but nothing can be seen).
This happens when the game is started in fullscreen mode. In windowed mode the
game starts properly (CSMT enabled). Switching between fullscreen and windowed
mode is available in the game's display option menu.
This might be interesting from the console log (not present when CSMT is
disabled):
err:d3d:wined3d_debug_callback 0x21be40: "GL_INVALID_VALUE in
glTexSubImage2D(xoffset+width)".
err:d3d_surface:wined3d_surface_upload_data >>>>>>>>>>>>>>>>> GL_INVALID_VALUE
(0x501) from glTexSubImage2D @ ../wined3d/surface.c / 1706
The problem can be reproduced with the demo version on Steam.
wine-1.8-rc1-81-g6790d82 (Staging)
Fedora 23
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NV92
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.0-devel
OpenGL core profile shading language version string: 3.30
--
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=40332
Bug ID: 40332
Summary: Prince of Persioa 2008 crash at intro with
wine-staging csmt
Product: Wine
Version: 1.9.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fin4478(a)hotmail.com
Distribution: ---
Similar bug in wine-staging version than in 36063. Graphics hangs in the intro
sequence when Elika looks up and shuts the mouth of Prince. Sound keeps going
on for a while. To kill the game, press alt+ctrl+f1 and type ps -e to find the
application id. There is no trace in the terminal what happened when launching
the game from a terminal. With wine 1.8.1 the game works ok.
--
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.